13139-CONTRACT.PDF

SERIAL 13139-RFP NEW JAIL MANAGEMENT SYSTEM SOLUTION
DATE OF LAST REVISION: May 20, 2015 CONTRACT END DATE: May 31, 2025
CONTRACT PERIOD THROUGH MAY 31,2025
TO: All Departments
FROM: Office of Procurement Services
SUBJECT: Contract for NEW JAIL MANAGEMENT SYSTEM SOLUTION
Attached to this letter is published an effective purchasing contract for products and/or services to be supplied to
Maricopa County activities as awarded by Maricopa County on May 20, 2015 (Eff. 06/01/15)
All purchases of products and/or services listed on the attached pages of this letter are to be obtained from the
vendor holding the contract. Individuals are responsible to the vendor for purchases made outside of contracts.
The contract period is indicated above.
JG/mm
Attach
Copy to: Office of Procurement Services
Arnie Bristil, MCSO
Dave Davis, MCSO

CONTRACT PURSUANT TO RFP
SERIAL 13139-RFP
Contract Synopsis:
Approval Date: May 20, 2015
Contract Start Date: June 1,2015
Contract End Date: May 31, 2025
Contract Term: 10 years, plus option for additional 10 years
Contracted Parties: Maricopa County (County, Owner)
Syscon Justice Systems (Contractor)
Scope Brief:
The County, on behalf of the Maricopa County Sheriff's 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
Part a — Functional Requirements
Part b —Nort-Functional and Technical Requirements
Exhibit C — WorkflowJail Software License Agreement
Exhibit D — Oracle Sub-License Agreement
Exhibit E — Syscon Justice Systems Client Support Agreement
Exhibit F — Travel and Per Diem Policy
Exhibit 0 — MCSO Security Guidelines
Appendix 1 Forms
Appendix 2 — Integration/Interfaces Inventory
Appendix 3 — Waiver of Claims
c6t-

MASTER SERVICE AGREEMENT
SERIAL 13139-RFP
This Contract is entered into this l st day of June, 2015 by and between Maricopa County ("County"), a political
subdivision of the State of Arizona, and Syscon Justice Systems Canada, LTD, a British Columbia corporation
("Contractor") for the purchase of New Jail Management Software services.
1.0 CONTRACT TERM:
1.1 This Contract is for a term of ten (10) years, beginning on the l q day of June, 2015 and ending the
31't day of May, 2025.
1.2 The County may, at its option and with the agreement of the Contractor, renew the term of this
Contract for additional terms up to a maximum of twenty (20) years (or at the County's sole
discretion, extend the contract on a month-to-month basis for a maximum of six (6) months after
expiration). The County shall notify the Contractor in writing of its intent to extend the Contract term
at least thirty (30) calendar days prior to the expiration of the original contract term, or any additional
term thereafter.
2.0 PRICE ADJUSTMENTS:
2.1 Following the Warranty Period and on each Contract anniversary date of the Contract, the Contractor
may request an increase in hourly rates for non-contracted services. Such increase(s) shall be based
upon the prevailing CPI rate using table CUUR0400AAO, West Urban, All Urban Customers. Non-
contracted services are those tasks added to the Contract, post award, through Contract Change
Order(s). Any request for increases in addition to the then prevailing CPI rate must be accompanied
by detailed supporting documentation that explains the necessity of the increase. Maricopa County
shall, in good faith, independently verify each such request and make a determination on the proposed
increase.
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.
3.3 INVOICES:
3.3.1 The Contractor shall submit one (1) legible copy of their detailed invoice before payment(s)
can be made. At a minimum, the invoice must provide the following information:
• Company name, address and contact
• County bill-to name and contact information
• Contract serial number
9,-

SERIAL I3139-RFP
• County purchase order number
• Invoice number and date
• Payment terms
• Date of service or delivery
• Description of service provided (Milestone, Deliverable, Monthly Service Rate
as Described in Exhibit A)
• Copy of signed Acceptance Form (if applicable)
• Travel reimbursements to be invoiced in accordance with Section 3.5 below
• Total Amount Due
3.3.2 Problems regarding billing or invoicing shall be directed to the County as listed on the
Purchase Order.
3.3.3 Payment shall be made to the Contractor by Accounts Payable through the Maricopa
County Vendor Express Payment Program. This is an Electronic Funds Transfer (EFT)
process. After Contract Award the Contractor shall complete the Vendor Registration
Form located on the County Department of Finance Vendor Registration Web Site
(http://www.maricona.ffov/Finance/Vendors.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 financial
institution for access to those details.
3.4 PROJECT PAYMENT TERMS:
Milestones and Deliverables are detailed in Exhibit B. Fees for deliverables, including any third
party products or services to be provided by Contractor, are set out in Exhibit A. Additionally, the
parties have agreed to a monthly service rate and implementation support rate. County will
perform those obligations that are specified as its responsibility in the statement of work or
relevant implementation, acceptance or reliability test plan as may be agreed between the parties.
3.5 TRAVEL AND PER DIEM:
3.5.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 F, 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.
3.5.2 Contractor shall perform the following duties with respect to travel:
3.5.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.5.2.2 Provide monthly travel budget for the following four (4) calendar weeks.
3.5.2.3 Provide monthly invoices with a detail of expense performance to the monthly
travel budget.

SERIAL 13139-REP
3.6 APPLICABLE TAXES:
3.6.1 Payment of Taxes: The Contractor shall pay all applicable taxes.
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 contract, it is the
responsibility of the Contractor to collect and remit all applicable taxes to the proper
taxing jurisdiction or 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
all taxes and include the same in proposal price.
4.0 ORDERING AUTHORITY:
4.1 County shall accompany any request for purchase of materials or services with a valid purchase
order, issued by Office of Procurement Services, or by a Certified Agency Procurement Aide
(CAPA). Purchase Orders shall be issued annually and shall detail the applicable license,
milestone, burn rate and other applicable, agreed to fees for the given year. In the event of a
conflict between any terms and conditions in the purchase order, they are null and void and instead
the terms of this Contract, or the appropriate statement of work executed by both parties, will
apply.
4.2 Maricopa County departments, cities, other counties, schools and special districts, universities,
nonprofit educational and public health institutions may also purchase from under this Contract at
their discretion and/or other state and local agencies (Customers) may procure the products under
this Contract by the issuance of a purchase order to the Respondent. Purchase orders must cite the
Contract number. Any such Customer order is i) conditioned upon mutual agreement of all parties
pursuant to special requirements that may be appended thereto, and ii) will provide that all
purchases and payment transactions will be made directly between Contractor and the requesting
entity.
4.3 All requirements for the competitive award of this Contract have been met. A purchase order for
the products is the only document necessary for Customers to purchase and for the Respondent to
proceed with delivery of materials available under this Contract.
4.4 Any attempt to represent any product not specifically awarded under this Contract is a violation of
the Contract. Any such action is subject to the legal and contractual remedies available to the
County, inclusive of, but not limited to, Contract cancellation, suspension and/or debarment of the
Contractor.
5.0 AVAILABILITY OF FUNDS:
5.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.

SERIAL I3139-RFP
5.2 If any action is taken by any State agency, Federal department or any other agency or
instrumentality to suspend, decrease, or terminate its fiscal obligations under, or in connection
with, this Contract, County may amend, suspend, decrease, or terminate its obligations under, or in
connection with, this Contract. In the event of termination, County shall be liable for payment
only for services rendered prior to the effective date of the termination, provided that such services
are performed in accordance with 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.3 If a decision is made to amend, suspend, decrease or terminate County's obligations under, or in
connection with, this Contract, the Contractor shall be entitled to amend, suspend, decrease or
terminate its obligations to match the County's actions to its obligations. County acknowledges
that any such suspensions, amendments, decreases or terminations may delay or adversely impact
or prevent the delivery of the Contract and that the Contractor shall not be responsible therefor.
6.0 DUTIES:
6.1 The Contractor shall perform all duties stated in Exhibit B, or as otherwise directed in writing by
the Procurement Officer.
6.2 During the Contract term, County shall provide Contractor's personnel with adequate workspace
for consultants and such other related facilities as may be required by Contractor to carry out its
contractual obligations.
7.0 SPECIAL TERMS AND CONDITIONS:
7.1 DEFINITIONS:
All definitions in this section shall apply to all subsequent documents and agreements attached to
this Contract.
1. "Acceptance" shall mean that a Deliverable has passed the acceptance test plans, process
and criteria for acceptance of deliverables as set forth in Sections 7.5 thru 7.7 of the
MSA, Exhibit B, Part 2, Sections 4.2.1 and 8 and as indicated by a signed Deliverable
Acceptance Statement from County sent to Contractor or as deemed by such process.
2. "Application Package" shall mean the Product (including any embedded third party
software programs), the Database and any Custom Modifications.
3. "Business Day" shall mean one regular 8-hour work-day (Monday through Friday) as
defined by MCSO's business calendar.
4. "Business Use" shall mean the procedures for the use of the Product in the manner and
for the purpose of which it was originally intended by Contractor as reflected in its design
and having regard to the business practices of County, both of which are established in
system administration training provided by Contractor.
5. "Contract" means this Master Services Agreement (Serial 13139-RFP) dated June 1,
2015, and all Exhibits and Appendices attached hereto and made a part hereof.
6_ "Conversion" see Migration
7. "Current Release" means the current commercially available version of the Product and
no more than two (2) Major Releases preceding such current commercially available
release.
8, "Custom Modification" shall mean, unless otherwise specifically varied herein, any
changes or modifications made to the Product or Database by Contractor (including, but
not limited to, tables, columns, screens, reports, interfaces to third party hardware or
software) exclusively for the County.
9. "Database" shall mean the relational database management system used in the County
Delivery Platform and Production System_

SERIAL 13139-REP
10. "Day/Days" shall mean, unless noted otherwise, one calendar day.
11. "Defect" means a failure of the Application Package to perform (a) the designed
functionality as set out in the Documentation therefor, or (b) any required functionality as
set out in this Contract, in each case when caused by an error in the Application Package.
12. "Deliverable" means a service, product, or good to be provided by Contractor to County
under this Contract and identified as a numbered Deliverable in the Statement of Work
(SOW) or any approved change order or amendment.
13. "Delivery Platform" shall mean a computer environment at the County location that will
functionally reflect the Production System and contain, at a minimum, a representative
sample of current offender data and whereupon County shall install all Major and
Maintenance Releases, associated patches and Defect corrections; and which will be used
by County for acceptance validation and regression testing (as appropriate) prior to
promotion to the Production System.
14. "Documentation" shall mean all user manuals, reference guides, training materials,
release notes, on line help and other materials in printed or electronic form, which
facilitate use of the Application Package programs.
15. "Enhancement" means modifications to the Product which may increase the speed,
efficiency, or ease of operation or otherwise improve the functions of the Product and
which Contractor elects to incorporate into the standard product line, and for greater
certainty any Maintenance Releases or any Major Releases are Enhancements.
16. "Final Acceptance" has the meaning set forth in Exhibit II, Part 2, Section 8.3.
17. "Gate Review" means the step in a defined process where the parties reach a mutual
agreement on the next step (e.g. decision to move to Final Acceptance versus an
extension of Warranty). This may also be individually and explicitly defined within the
Project Management Plan.
18. "Go-Live Date" means the start-up of production use of the System.
19. "Integration" shall mean provision of custom interfaces and code to allow data
exchange between distinct software applications or databases.
20. "Interface" means the software mechanisms which allow the transfer of electronic data
or software commands between computer systems, computer programs, or computer
program modules which are required to be provided by Contractor under the SOW and,
in all cases, are and become a component of the System forming part of the Application
Package.
21. "Issue" means 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.
22. "Maintenance Release" shall mean the periodic software release that may contain a
rollttp of hot fixes and patches that have been provided in response to specific client
reported errors or defects.
23. "Major Release" shall mean the periodic software release that may incorporate new
features, architecture changes and product components, and for greater certainty no
Maintenance Release shall, by itself, be a Major Release (though a Major Release may
contain the functionality of a Maintenance Release).
24. "Migration" shall mean the transfer of data from a legacy application database to the
Workflowdail database. Migration is interchangeable with the term Conversion.
25. "Migration Services" shall mean those professional services that may be required
(included, but not limited to, installation, configuration, project management, training) by
the County on account of the Major and Maintenance releases.
26. "Onsite" shall mean any activity conducted at County facilities.
27. "PM" shall mean Project Manager.

SERIAL 13139-RFP
28. "Product" shall mean the software application programs known as WorkflowJAIL
inmate management system including Documentation.
29. "Production System" shall mean the computer operating system(s) and Application
Package programs used by County in the live processing of its inmate data.
30. "Remote" shall mean any Contractor Services provided from locations other than
County facilities, including those activities conducted using secure remote internet
connection and software, and teleconferencing equipment as required.
31. "SME" shall mean Subject Matter Expert.
32. "SOW" means the Statement of Work attached hereto as Exhibit B, as the same may be
amended by any approved change order or amendment.
33. "Subtask" means one or more sub-areas of work to be performed under this Contract and
identified as a numbered Subtask in the SOW or any approved change order or
amendment.
34. "Support" shall mean (a) responding to inquiries concerning reported Defect(s) in the
Application Package programs; (b) correction to problems diagnosed as Defects in
Current Release of the Application Package; (c) providing or making available
Enhancements and Maintenance Releases to the Current Release of the
Product/Application Package from time to time as provided to other supported users
thereof, in each case as set out in the Support Agreement attached hereto as Exhibit E. In
the resolution of Defects under (b), Contractor may respond with a written response, CD
ROM or diskette, electronic delivery, supplementary documentation, a temporary means
of circumventing the problem pending a Maintenance Release, or other correctional aids..
35. "System" shall mean the final configuration and setup of the Contractor's software
product, including migrated or converted MCSO data, installation, configuration,
database design, and integrations, so that all elements perform as a single unit in the
manner intended.
36. "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 as more fully described in Section 7.5.
37. "Task" means one or more major areas of work to be performed under this Contract and
identified as a numbered Task in the SOW or any approved change order or amendment.
38. "Test Script" shall mean a series of actions, functions or commands documented for the
purpose of execution during quality assurance testing.
39. "Warranty Period" shall mean the period of forty-five (45) days (as may be extended in
accordance with the terms of this Contract) applicable to the Deliverable, as more
particularly specified in Section 7.7.3.
Notwithstanding the commingled references to "Enhancements' , "Custom Modifications" "Custom
Interfaces" and "Software Customizations" provided in Exhibit B, Part Two, all such references
shall, for the purposes of annual support and maintenance, be deemed one and the same and not be
subject to any support and maintenance charges in addition to those set forth in Exhibit A, and are
also part of the Application Package licensed to the County under the terms of Exhibit C hereof.
Any post award, non-contracted software modifications or Interfaces that may be requested shall be
appropriately designated as either an Enhancement (forming part of Product and without additional
annual support fees) or, a Custom Modification (subject to additional annual support fees).
7.2 PAYMENT RETENTION
7.2.1 The following Retention grid shall apply to the designated payment streams as defined in
Exhibit A Pricing.

SERIAL 13139-RFP
Description Retention Initial Release Final Release
Percentage
Software Licenses 10% Fifty percent (50%) of the amount Final Acceptance
retained to date by County for of all Phase One
Software License at Final Acceptance and Two services
of Phase One and software
Phase One Professional 10% Fifty percent (50%) of the amount Final Acceptance
Services retained to date by County for Phase of all Phase One
One Professional Services at Final and Two services
Acceptance of Phase One and software
Phase Two Professional 20% Not applicable Final Acceptance
Services of all Phase One
and Two services
and software
All other payment terms and conditions shall not be affected by the retention. In the event
of termination or cancellation of this Contract, except where the contract has been
terminated for Contractor's breach or other Contractor-fault termination mechanism,
Contractor shall be paid any funds in the retention account.
7.2.2 The Contractor shall have the right, pursuant to Arizona Revised Statutes, 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 shalt request and
obtain securities forms through County. The County must identify either securities
option or retention option prior to first Application for Payment.
7.2.3 Retained funds shall be released to the Contractor in accordance with the payment
Milestone chart contained within Exhibit A, Pricing. Retained fund remuneration and/or
the Payment Retention percentage may be modified by mutual consent of the Parties at
agreed to intervals.
7.3 BOND REQUIREMENT:
7.3.1 Within ten (10) days of execution of the Contract, the Contractor shall furnish the
Contracting Agency the following bonds, which shall become binding upon the award of
the contract to the Contractor.
7.3.1.1 Performance Bonds in the aggregate amount of two minion US Dollars
($2,000,000) (consisting of a Phase 1 bond in the amount of one million two
hundred thousand US Dollars ($1,200,000), a Phase 2a bond in the amount of
four hundred thousand US Dollars ($400,000) and a Phase 2b bond in the
amount of four hundred thousand US Dollars ($400,000)) shall be provided by
Contractor. Such bonds shall be solely for the protection of the County against
non-performance by the Contractor (subject to the satisfaction or resolution of
any claims for non-performance of the Contract) as provided below.
7.3.1.2 In lieu of the provision of a Payment Bond by Contractor, any Subcontractor
under this agreement will provide the County a waiver of claims to be annexed
hereto as Appendix 3.
7.3.2 Each such bond shall include a provision allowing the prevailing party in a suit on such
bond to recover as a part of his judgment such reasonable attorney's fees as may be fixed
by a judge of the court.
7.3.3 Each bond shall be executed by a surety company or companies holding a certificate of
authority to transact surety business in the State of Arizona issued by the Director of the

SERIAL 13139-RFP
Department of Insurance. The bonds shall not be executed by an individual surety or
sureties. The bonds shall be made payable and acceptable to the Contracting Agency.
The bonds shall be written or countersigned by an authorized representative of the surety
who is either a resident of the State of Arizona or whose principal office is maintained in
this state, as by law required, and the bonds shall have attached thereto a certified copy of
the Power of Attorney of the signing official. In addition, said company or companies
shall be rated "Best-A" or better as required by the Contracting Agency, as currently
listed in the most recent Best Key Rating Guide, published by the A.M. B est Company.
7.3.4 Bond Release-The Parties agree that Performance bonds shall be applicable to and held
for the duration of the currently active Phase of work as described in Exhibit B, Part Two.
Upon successful acceptance of the Deliverables and issuance by MCSO of a Final
Acceptance certificate for the completed Phase, County shall, within thirty (30) days
return to Contractor the corresponding bond.
7.4 SOURCE CODE ESCROW
7.4.1 The Contractor shall provide all source code and any Enhancements to the Contractor's
Commercial Off-the-Shelf (COTS) application software for safekeeping with a mutually
acceptable escrow agent within forty-five (45) days of installation by County of the
Application Package 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 software, subject to
one of the release clauses in Section 7.4.2 being met. Furthermore, the escrowed code
shall include all Custom Modifications 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 7.4.3) to use the source for the Application Package licensed from
Contractor in the versions currently installed on the System or any subsequent versions in
the archive. Contractor will make a deposit with the escrow agent at least once every six
(6) months.
County hereby agrees to pay all fees for a beneficiary of the source code as set out in the
County's escrow agreement with a certified third party.
For greater certainty, upon County taking possession of the source code, Contractor will
have no further obligation to support the Application Package or the System, further
perform under this Contract, nor update the escrow deposit unless some formal
agreement between the parties has been reached.
7.4.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:
7,4.2.1 The sale, assignment, or transfer to any third party of any of Contractor's rights
in the Application Package (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);

SERIAL 13139-RFP
7.4.2.2 If the Contractor should be adjudged bankrupt or should make a general
assignment for the benefit of its creditors, or if a receiver should be appointed on
account of its insolvency and the Contractor does not remedy such appointment
on account of its insolvency within sixty (60) days thereof;
7.4.2.3 If County is currently subscribed to Contractor's Support and Contractor, or any
entity that supports the Application Package, discontinues providing full support
for the Application Package in accordance with its obligations pursuant to any
agreement with County;
7.4.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;
7.4.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; or
7,4,2.6 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 the escrow agreement.
7.4.3 Should County take possession of the source code as a result of an event as specified
above, County hereby agrees as follows:
7.4.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;
7.4.3.2 County agrees to only use source code to, Support (itself or, subject to
confidentiality provisions, by others for its benefit) the Application Package for
use thereof in accordance with the license granted hereunder (i.e., Exhibit C).
There will be source code from other applications in the archive;
7.4.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;
7.4.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
7.4.3.5 County and the Contractor will execute, and deposit into escrow together with
the deposit materials, a confidentiality agreement, mutually agreed upon
between the parties, regarding the use and disclosure of the source code
consistent with this Section 7.4.

SERIAL 13139-RFP
7.4.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 7.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 will be conditioned upon County's
payment to Contractor in full therefor. As part of the escrow release process, County will
be required to certify to the escrow agent that it has paid such license and service fees.
7.5 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.
7.5.1 Acceptance for the Application Package and the System Testing shall be an on-going,
iterative activity which shall be performed throughout the Contract, provided that
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.
7.5.2 The Contractor will perform initial testing from its premises prior to delivery of a
Deliverable. County may ask to see the initial testing results from Contractor, but only
for comparison to the County's Onsite results.
7.5.3 The process for pre-user acceptance testing of Application Package Deliverables shall
include the following steps:
7.5.3.1 Contractor completes an Application Package Deliverable;
7.5.3.2 Contractor configures the Deliverable and/or the Application Package in the
Delivery Platform with assistance from County;
7.5.3.3 Contractor provides a conference room pilot to demonstrate functionality
included in the Application Package including such Deliverable and how it is
intended to be used;
7.5.3.4 County completes additional testing of such Deliverable to validate the
configuration as part of the Application Package in the Delivery Platform; and
7.5.3.5 County provides Contractor with feedback about the current Deliverable, which
Contractor shalt 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).
st,

SERIAL 13139-REP
7.6 CRITERIA FOR DELIVERY AND ACCEPTANCE OF DELIVERABLES:
7.6.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.
7.6.2 County Representative shall review and validate Contractor's Deliverables product prior
to Acceptance. Acceptance criteria for Deliverables shall consist of the following:
7.6.2.1 Specific Deliverables are completed as specified in this Contract and the final
Deliverable has been rendered.
7.6.2.2 Plans, schedules, designs, documentation, and reports are approved and
completed as specified in this Contract.
7.6.2.3 All supporting Documentation is provided and complete.
7.6.2.4 All Deliverables are presented to County in the approved format (or if no such
format is approved, in an industry-standard format).
7.6.2.5 All Deliverables are at the agreed upon acceptable level of quality as defined in
this Contract.
7.6.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 Section
7.4. Subject to the foregoing, County shall retain unlimited rights in any other
Deliverables.
7.7 SOFTWARE UPDATES, WARRANTY, MAINTENANCE & ROADMAP/ENHANCEMENTS:
7.7.1 Contractor shall make available to County at no additional charge all Enhancements to
the Application Package 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 Application Package.
7.7.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.
7.7.3 After the Reliability Test Period has passed as set out in Section 8 of Exhibit B Part 2,
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.
7.8 FORCE MAJEURE
7.8.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 either Party. Such
events, occurrences, or causes will include Acts of God/Nature (including fire, flood,
earthquake, storm, hurricane or other natural disaster), war, invasion, act of foreign
enemies, hostilities (whether war is declared or not), civil war, riots, rebellion, revolution,

SERIAL 13139-RFP
insurrection, military or usurped power or confiscation, terrorist activities,
nationalization, third-party government sanction, lockout, blockage, embargo, labor
dispute, strike, interruption or failure of electricity or telecommunication service.
7.8.2 Each Party, as applicable, shall give the other Party notice of its inability to perform and
particulars in reasonable detail of the cause of the inability. Each Party must use best
efforts to remedy the situation and remove, as soon as practicable, the cause of its
inability to perform or comply.
7.8.3 The Party asserting Force Majeure as a cause for non-performance shall have the burden
of proving that reasonable steps were taken to minimize delay or damages caused by
foreseeable events, that all non-excused obligations were substantially fulfilled, and that
the other Party was timely notified of the likelihood or actual occurrence which would
justify such an assertion, so that other prudent precautions could be contemplated.
7.8.4 Either Party shall reserve the right to terminate this Contract and/or any applicable order
or contract release purchase order upon non-performance by the other Party that extends
for a period of sixty (60) days or longer. To the extent a delay is excused as an event of
Force Majeure hereunder, the time for performance shall be extended correspondingly.
7.9 CONFIDENTIAL INFORMATION
7.9.1 In the course of performing this Contract, either Party (the "Receiving Party") may
receive information or material from the other Party (the "Disclosing Party") that is not
generally known to the public or that, by its nature or the nature of its disclosure ought
reasonably be known to be (or is identified as) the confidential or proprietary information
of the Disclosing Party (collectively, the "Confidential Information"). The parties
acknowledge that this agreement is subject to the Arizona law regarding public records,
A.R.S. §39.121 et. seq. For greater certainty, the Confidential Information of Contractor
includes all computer programs, code, data models, algorithms, know-how, formulas,
processes, ideas, inventions (whether patentable or not), schematics and other technical,
business, financial and product development plans, forecasts, strategies, and information.
All Confidential Information is the sole property of the Disclosing Party, and the
Receiving Party must, in accordance with Arizona law, (a) treat the Disclosing Party's
Confidential Information as confidential and sensitive; (b) not use the Disclosing Party's
Confidential Information for any purpose other than in connection with performance
under this Contract; (c) prevent unauthorized disclosure of any of the Disclosing Party's
Confidential Information, including the contents of this Contract; and (d) at the
conclusion of this Contract after the written direction of the Disclosing Party, either
return all of the Disclosing Party's Confidential Information to the Disclosing Party or
destroy it entirely in such a way that it cannot be used by anyone else (where destruction
includes shredding paper by a bonded, confidential destruction service, or executing a
delete function on computer-stored information and thereafter not recovering or restoring
the same, whether through archives, forensics or otherwise). The Receiving Party will
ensure that its personnel (including all employees, subcontractors and subcontractors'
employees) observe these restrictions.
7.9.2 Notwithstanding the above, the Receiving Party will not have an obligation with respect
to information to the extent that it is: (a) already known to the Receiving Party free of any
restriction at the time it is obtained from the Disclosing Party; (b) subsequently learned
by the Receiving Party from an independent third party free of any restriction and without
breach of this Contract, any agreement with such third party or any other confidentiality
obligation; (c) becomes publicly available through no wrongful act of the Receiving
Party; or (d) independently developed by the Receiving Party without any use of the
Disclosing Party's Confidential Information. Notwithstanding the restrictions set forth
above, the Receiving Party may disclose the Disclosing Party's Confidential Information
to the extent such disclosure is required by a law, or court or regulator of competent
jurisdiction under applicable law, provided that before making any such disclosure the
Receiving Party gives reasonable notice to the Disclosing Party of the potential disclosure

SERIAL 13139-RFP
and provides the Disclosing Party a reasonable opportunity to advise the Receiving Party
of any objections to the proposed release.
7.10 CONFORMANCE OF SERVICES:
7,10.1 The Contractor warrants that all services provided hereunder will conform 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.
7.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. County shall
deliver notice of such failure and the particulars of the failure to Contractor within thirty
(30) days of the delivery of such services. 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,
7,11 INSPECTION OF SERVICES:
7.11.1 The Contractor shall provide arid 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.
7.11.2 County has the right, at its expense, 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.
7.11.3 If any of the services do not conform with Contract requirements, County may require the
Contractor to perform the services again in conformity with Contract requirements, at no
increase in Contract amount. County shall deliver notice of such failure and the
particulars of the failure to Contractor within thirty (30) days of the delivery of such
services. When the defects in services cannot be corrected by re-performance, County
may:
7.11.3.1 Require the Contractor to take necessary action to ensure that future
performance conforms to Contract requirements; and
7.11.3.2 Engage in the dispute resolution procedures set out in this Agreement to
determine a fair price for the defective services.
7.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 terminate the Contract for default in accordance with Section 8.7.
8.0 TERMS and CONDITIONS:
8.1 INDEMNIFICATION:
8.1.1 Contractor shall defend, indemnify and hold harmless County, its agents, representatives,
officers, directors, officials, and employees from and against all claims, damages, losses
and expenses (including but not limited to, court costs and reasonable attorney fees,
expert witness fees) (a) to the extent arising out of the willful misconduct or fraud of
Contractor or those persons for whom Contractor is legally responsible, or (b) for bodily
injury, tangible property damage, or death to the extent arising out of the acts or
omissions of the Contractor or those persons for whom Contractor is legally responsible.

SERIAL 13I39-RFP
8.1.2 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.
8.1.3 The Contractor's indemnification obligations under Section 8.1 will not apply to the
extent the claims, damages, losses or expenses arise from (a) precise compliance by
Contractor (or those for whom it is responsible) with directions given to it by the County
pursuant to this Contract, or (b) the acts or omissions of the County or those persons for
whom County is responsible.
8.1.4 Except in relation to the indemnities specifically provided for hereunder, Contractor will
not be liable to County for any indirect, incidental, special or consequential claims,
damages, losses or expenses of any kind whatsoever and however caused, whether arising
under contract, tort (including negligence) or otherwise, including (without limitation)
loss of production, loss of or corruption to data, loss of profits or of contracts, loss of
business, loss of management or operation time and loss of goodwill or anticipated
savings, even if Contractor has been notified of the possibility thereof or could have
foreseen them. Furthermore, except in relation to such indemnities, Contractor's
aggregate liability for direct damages in respect of this Contract will be limited to the fees
paid or payable for services, to Contractor by County during the twelve (12) months
preceding the circumstances in which such liability arises, and in any event never more in
aggregate for all liabilities in excess of the fees paid or payable to Contractor by County
pursuant to this Contract.
8.1.5 Contractor's obligations under this Section are conditioned on the following: (i) County
promptly notifies Contractor of the claim, damage, loss or expense (as the case may be)
in writing upon County being made aware of same, (ii) County and Contractor shall share
lead authority and control of the defense and (if applicable) settlement thereof, and (iii)
County provides all information and assistance reasonably required by Contractor to
handle the defense or settlement thereof. In the event shared lead authority and control is
exercised under this clause, the Parties will act reasonably and in good faith in a
collaborative and cooperative fashion to minimize the indemnification obligations under
the Claim.
The scope of this indemnification does not extend to the sole negligence of County.
8.2 INFRINGEMENT DEFENSE INDEMNIFICATION
8.2.1 Defense and Indemnity. Contractor shall defend, Participate and Share in the Cost, as
defined below, in the full defense of the County against any Claim, as defined 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 County being made aware of the Claim; (ii)
County gives Contractor lead authority and 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 Application
Package, or any enhancements, 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.
8.2.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

SERIAL I3139-RFP
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.
8.2.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; (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; or (viii) possession or use of a product that is more than three
versions out of date (current version plus two previous versions) after Contractor
has made a new version or update available to County pursuant to its support
and maintenance obligations and the County, pursuant to Section 7.7.1, has
determined not to implement such new version or update, if such Claim would
have been avoided by County's implementation of such new version or update.
"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.
8.2.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 misappropriation of any intellectual property rights of another
party.
8.3 INSURANCE:
8.3.1 Contractor, at Contractor's own expense, shall purchase and maintain the herein
stipulated minimum insurance from a company or companies duly licensed by the State
of Arizona and possessing a current A.M. Best, Inc. rating of B+÷. In lieu of State of
Arizona licensing, the stipulated insurance may be purchased from a company or
companies, which are authorized to do business in the State of Arizona, provided that
said insurance companies meet the approval of County. The form of any insurance
policies and forms must be acceptable to County.
8.3.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.
8.3.3 Contractor's insurance shall be primary insurance as respects County, and any insurance
or self-insurance maintained by County shall not contribute to it.

SERIAL 13139-RFP
8.3.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.
8.3.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.
8.3.6 County reserves the right to request and to receive, within ten (10) working days,
certified copies of any or all of the herein required insurance certificates. County shall not
be obligated to review policies and/or endorsements or to advise Contractor of any
deficiencies in such policies and endorsements, and such receipt shall not relieve
Contractor from, or be deemed a waiver of County's right to insist on strict fulfillment of
Contractor's obligations under this Contract.
8.3.7 The insurance policies required by this Contract, except Workers' Compensation and
Professional Liability, shall name County, its agents, representatives, officers, directors,
officials and employees as Additional Insureds.
8.3.8 The policies required hereunder, except Workers' Compensation and Professional
Liability, 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.
8.3.9 Commercial General Liability:
Commercial General Liability insurance and, if necessary, Commercial Umbrella
insurance with a limit of not less than $2,000,000 for each occurrence, $2,000,000
Products/Completed Operations Aggregate, and $4,000,000 General Aggregate Limit.
The policy shall include coverage for bodily injury, broad form property damage,
personal injury, products and completed operations and blanket contractual coverage, and
shall not contain any provision which would serve to limit third party action over claims.
There shall be no endorsement or modification of the CGL limiting the scope of coverage
for liability arising from explosion, collapse, or underground property damage.
8.3.10 Automobile Liability:
Commercial/Business Automobile Liability insurance and, if necessary, Commercial
Umbrella insurance with a combined single limit for bodily injury and property damage
of not less than $2,000,000 each occurrence with respect to any of the Contractor's
owned, hired, and non-owned vehicles assigned to or used in performance of the
Contractor's work or services under this Contract.
83.11 Workers' Compensation:
8.3.11.1 Workers' Compensation insurance to cover obligations imposed by federal,
provincial and state statutes having jurisdiction of Contractor's employees
engaged in the performance of the work or services under this Contract; and
Employer's Liability insurance of not less than $1,000,000 for each accident,
$1,000,000 disease for each employee, and $1,000,000 disease policy limit.
8.3.11.2 Contractor waives all rights against County 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 pursuant to
this Contract.

SERIAL I3139-RFP
8.3.12 Professional Liability Insurance:
Contractor shall maintain Professional Liability insurance which will provide coverage
for any and all acts arising out of the work or services performed by the Contractor under
the terms of this Contract, with a limit of not less than $1,000,000 for each claim, and
$5,000,000 aggregate claims.
8.3.13 Cyber:
Policy Limits:
8.3.13.1 The policy shall be issued with minimum limits of $100,000.
8.3.13.2 The policy shall include coverage for all directors, officers, agents and
employees of the Contractor.
8.3.13.3 The policy shall include coverage for third party fidelity.
8.3.13.4 The policy shall include coverage for theft.
8.3.13.5 The policy shall contain no requirement for arrest and conviction.
8.3.13.6 The policy shall cover loss outside the premises of the Named insured.
8.3.13.7 The policy shall endorse (Blanket Endorsements are not acceptable) the
Department as Loss Payee as its interest may appear.
8.3.14 Certificates of Insurance:
8.3.14.1 Prior to commencing work or services under this Contract, Contractor shall
furnish the County with valid and complete certificates of insurance, and
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.
83.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 (2) years past
completion and acceptance of Contractor's work or services and as evidenced
by annual Certificates of Insurance.
8.3.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.
8.3.15 Cancellation and Expiration Notice:
Insurance required herein shall not be permitted to expire, be canceled, or materially
changed without thirty (30) days prior written notice to the County.
8.4 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

SERIAL I3139-RFP
For Contractor:
Syscon Justice Systems Canada, Ltd.
ATI'N: The President
6500 River Road, 2nd Floor
Richmond, BC V6X 1X5 Canada
CC: Director, Contracts
8.5 REQUIREMENTS CONTRACT:
8.5.1 Contractor signifies its understanding and agreement by signing this document that this
Contract is a requirements contract. This Contract does not guarantee any purchases will
be made (minimum or maximum). Orders will only be placed when County identifies a
need and issues a purchase order or a written notice to proceed.
8.5.2 County reserves the right to cancel purchase orders or notice to proceed within forty-five
(45) days after issuance. Should a purchase order or notice to proceed be cancelled, the
County agrees to reimburse the Contractor for actual and documented costs incurred by
the Contractor. The County will not reimburse the Contractor for any avoidable costs
incurred after receipt of cancellation, or for lost profits, or shipment of product or
performance of services prior to issuance of a purchase order or notice to proceed.
8.5.3 Purchase orders will be cancelled in writing.
8.6 UNCONDITIONAL TERMINATION FOR CONVENIENCE:
The County reserves the right to terminate the Contract, in whole or in part at any time, when in
the best interests of the County without penalty or recourse. Upon receipt of the written notice,
the Contractor shall promptly stop all work, as directed in the notice, notify all subcontractors of
the effective date of the termination and minimize all further costs to the County. In the event of
termination under this paragraph, all documents, data and reports prepared by the Contractor (for
greater certainty excluding any materials or intellectual property licensed to the County pursuant
to a Contractor's license agreements) shall become the property of and be delivered to the County
upon full payment therefor in accordance with the following sentence. The Contractor shall be
entitled to receive just and equitable compensation for work in progress, work completed and
materials accepted before the effective date of the termination.
8.7 TERMINATION FOR DEFAULT:
8.7.1 In addition to the rights reserved in the Contract, either Party may terminate the Contract
in whole or in part due to the other Party's material breach of any term or condition of the
Contract. The terminating Party shall provide written notice of the termination and the
reasons for it to the other Party, and the other Party shall have thirty (30) days to remedy
such breaches, failing which the termination shall automatically occur on the thirty-first
(31') day unless the terminating Party has in writing granted an extension therefor.
8.7.2 Upon termination under this paragraph, all documents, data and reports prepared by the
Contractor (for greater certainty excluding any materials or intellectual property licensed
to the County pursuant to a Contractor's license agreements) shall become the property of
and be delivered to the County upon payment for all properly completed services and
deliverables.
8.7.3 The County may, upon termination of this Contract, procure, on terms and in the manner
that it deems appropriate, materials or services to replace those under this Contract. The
Contractor's liability to County under this section shall be limited to those amounts and
sums paid by County to Contractor prior to termination.

SERIAL I3139-RFP
8.7.4 The Contractor shall continue to perform, in accordance with the requirements of the
Contract, up to the date of termination, as directed in the termination notice.
8.8 TERMINATION BY THE COUNTY:
If the Contractor should be adjudged bankrupt or should make a general assignment for the benefit
of its creditors, or if a receiver should be appointed on account of its insolvency, the County may
terminate the Contract. If the Contractor should persistently or repeatedly breach this Contract,
thereby prompting multiple notices and cure periods under Section 8.7, or if the breach is
adjudged reasonably by the County to be so serious or grievous that a cure period of thirty (30)
days is not appropriate, the County may terminate the Contract after having given the Contractor
fifteen (15) calendar days' written notice of such repeated, serious or grievous error, during which
the Contractor shall be allowed to develop a plan, acceptable in the sole discretion of the County,
to remedy the cause of such repeated, serious or grievous breaches. If the County accepts such
plan, the termination will be cancelled.
8.9 STATUTORY RIGHT OF CANCELLATION FOR CONFLICT OF INTEREST:
Notice is given that pursuant to A.R.S. §38-511 the County may cancel this Contract without
penalty or further obligation within three (3) 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.
8.10 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 pursuant to the terms of this Contract.
8.11 ADDITIONS/DELETIONS OF SERVICE:
8.11.1 The County reserves the right to add and/or delete materials to a Contract. Any and all
changes to products, services, roles, responsibilities or timelines under this Contract shall
be subject to the Change Control Process.
8.11.2 The County reserves the right of final approval on proposed staff for the Statement of
Work and all services 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 as mutually
agreed to by the parties, unless previously approved by the County. The County agrees
that delays or additional costs arising from required personnel changes (unless the
original personnel has somehow breached this Agreement) will not be Contractor's
responsibility. In the event of a disagreement under this sub-clause 8.11.2, the parties will
pursue the matter in accordance with the escalation procedures set forth in Exhibit B, Part
Two, Section I Project Governance.
8.12 AMENDMENTS:
All amendments to this Contract shall be in writing and approved/signed by both parties. Maricapa
County Office of Procurement Services shall be responsible for approving all amendments for
Maricopa County.

SERIAL I3139-RFP
8.13 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, partnership, principal and agent, or joint venture
between the County and the Contractor.
8.14 SUBCONTRACTING:
The Contractor may not assign this Contract or subcontract to another party for performance of the
terms and conditions hereof without the written consent of the County, which shall not be
unreasonably withheld. All correspondence authorizing subcontracting must reference the
Proposal Serial Number and identify the job project.
8.15 ACCESS TO AND RETENTION OF RECORDS FOR THE PURPOSE OF AUDIT AND/OR
OTHER REVIEW:
8.15.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. The County, Federal or State auditors and any
other persons duly authorized by the Department shall have full access to, and the right to
examine, copy and make use of, any and all said materials. All access to materials will be
subject to Contractor's reasonable confidentiality terms, and the materials examined or
copied may only be used for the purposes of such audit. Such reviews, examinations or
audits may only be conducted on reasonable notice and in a manner that does not unduly
disrupt the Contractor's business.
8.15.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.
8.15.3 If at any time such an audit, examination or review determines that a cost for which
payment has been made is a disallowed cost in contravention of the Maricopa County
Procurement Code or this Contract, the County shall notify the Contractor in writing of
the disallowance and, if the Contractor disagrees, it may engage the dispute resolution
procedure set out in Section 8.7. The course of action to address the disallowance shall be
at sole discretion of the County, and may include either an adjustment to future claim
submitted by the Contractor by the amount of the disallowance, or require reimbursement
forthwith of the disallowed amount by the Contractor by issuing a check payable to
Marieopa County.
8.16 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.
8.17 RIGHTS IN DATA:
Except for any materials licensed to the County in a separate agreement, the County shall own and
have the use of all data and reports resulting from this Contract without additional cost or other
restriction except as provided by law. Each Party shall supply to the other Party, upon request,
any available information that is relevant to this Contract and to the performance hereunder,

SERIAL I3139-RFP
8.18 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.
8.19 VERIFICATION REGARDING COMPLIANCE WITH ARIZONA REVISED STATUTES §41-
4401 AND FEDERAL IMMIGRATION LAWS AND REGULATIONS:
8.19.1 By entering into the Contract, the Contractor warrants compliance with the Immigration
and Nationality Act (INA using E-Verify) and all other federal immigration laws and
regulations related to the immigration status of its employees and A.R.S. §23-214(A). The
Contractor shall obtain statements from its subcontractors certifying compliance and shall
furnish the statements to the Procurement Officer upon request. These warranties shall
remain in effect through the term of the Contract. The Contractor and its subcontractors
shall also maintain Employment Eligibility Verification forms (I-9) as required by the
Immigration Reform and Control Act of 1986, as amended from time to time, for all
employees performing work under the Contract and verify employee compliance using the
E-Verify system and shall keep a record of the verification for the duration of the
employee's employment or at least three years, whichever is longer. 1-9 forms are available
for download at USCIS.GOV .
8.19.2 The County retains the legal right to inspect Contractor and subcontractor employee
documents performing work under this Contract to verify compliance with paragraph
8.19.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.
8.20 CONTRACTOR LICENSE REQUIREMENT:
8.20.1 The Contractor shall procure all permits, insurance, licenses and pay the charges and fees
necessary and incidental to the lawful conduct of his/her business, and as necessary
complete any required certification requirements, required by any and all governmental
or non-governmental entities as mandated to maintain compliance with and be in good
standing for all permits and/or licenses. The Contractor shall keep fully informed of
existing and future trade or industry requirements, Federal, State and Local laws,
ordinances, and regulations which in any manner affect the fulfillment of a Contract and
shall comply with the same. Contractor shall immediately notify both the Office of
Procurement Services and MCSO of any and all changes concerning permits, insurance
or licenses.
8.21 CERTIFICATION REGARDING DEBARMENT AND SUSPENSION:
8.21.1 The undersigned (authorized official signing for the Contractor) certifies to the best of his
or her knowledge and belief, that the Contractor, defined as the primary participant in
accordance with 45 CFR Part 76, and its principals:
8.21.1.1 are not presently debarred, suspended, proposed for debarment, declared
ineligible, or voluntarily excluded from covered transactions by any Federal
Department or agency;
8.21.1.2 have not within three (3) year period preceding this Contract been convicted
of or had a civil judgment rendered against them for commission of fraud or a

SERIAL I3139-RFP
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 statutes or
commission of embezzlement, theft, forgery, bribery, falsification or
destruction of records, making false statements, or receiving stolen property;
8.21.1.3 are not presently indicted or otherwise criminally or civilly charged by a
government entity (Federal, State or local) with commission of any of the
offenses enumerated in paragraph (2) of this certification; and
8.21.1.4 have not within a three (3) year period preceding this Contract had one or
more public transaction (Federal, State or local) terminated for cause of
default,
8.21.2 Should the Contractor not be able to provide this certification, an explanation as to why
should be attached to the Contact.
8.21.3 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.
8.22 PRICES:
Contractor warrants that prices extended to County under this Contract are no higher than those
presently paid by any similarly-situated customer for these or similar services.
8.23 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.
8.24 ORDER OF PRECEDENCE:
In the event of a conflict in the provisions of this Contract and its Exhibits, Appendices, or County
issued Purchase Orders, the following order of precedence shall prevail:
1. Amendment(s) to Master Service Agreement
2. Master Service Agreement
3. Exhibit C WorkflowJAIL Software License Agreement
4. Change Order(s)
5. Exhibit A Price
6. Exhibit B Scope of Work
a. Part One — Statement of Requirements
b. Part Two — Statement of Work
i. Sub a - Functional Requirements
ii. Sub b - Non-Functionalffechnical Requirements
7. Appendix 2 Interface Inventory
8. Exhibit D Oracle Sub-License Agreement
9. Exhibit E Syscon Justice Systems Client Support Agreement
10. Acceptance Document(s)
11. Exhibit G MCSO Security Guidelines
12. Exhibit F Travel and Per Diem Policy
13. County Purchase Order or Work Release
14. Appendix 3 — Waiver of Claims

SERIAL 13139-RFP
8.25 INFLUENCE:
As prescribed in MC1-1202 of the Maricopa County Procurement Code, any effort to influence an
employee or agent to breach the Maricopa County Ethical Code of Conduct or any ethical conduct,
may be grounds for Disbarment or Suspension under MCI -902.
An attempt to influence includes, but is not limited to:
8.25.1 A Person offering or providing a gratuity, gift, tip, present, donation, money,
entertainment or educational passes or tickets, or any type of valuable contribution or
subsidy,
8.25.2 That is offered or given with the intent to influence a decision, obtain a contract, garner
favorable treatment, or gain favorable consideration of any kind.
If a Person attempts to influence any employee or agent of Maricopa County, the Chief
Procurement Officer, or his designee, reserves the right to seek any remedy provided by the
Maricopa County Procurement Code, any remedy in equity or in the law, or any remedy provided
by this contract.
8.26 PUBLIC RECORDS:
Pursuant to the Maricopa County Procurement Code, all Contracts are a matter of public record
and shall be retained by the Records Manager at the Office of Procurement Services. It is the
responsibility of Contractor to request in writing to the Office of Procurement Services a partial
redaction of the Contract and its related proposal documentation. Said request shall include a
justification for redaction and an explanation of the impact a release of the information may have
on Contractor. All requests shall be reviewed by the Chief Procurement Officer for approval.
8.27 INCORPORATION OF DOCUMENTS:
The following are to be attached to and made part of this Contract:
8.27.1 Exhibit A — Pricing Agreement
8.27.2 Exhibit B — Scope of Work
8.27.2.1 Part One - Statement of Requirements
8.27.2.2 Part Two - Statement of Work
8.27.2.1.1 Sub a — Functional Requirements
8.27.2.1.2 Sub b —Non-Functional and Technical Requirements
8.27.3 Exhibit C — WorkflowJail Software License Agreement
8.27.4 Exhibit D — Oracle Sub-License Agreement
8.27.5 Exhibit E — Syscon Justice Systems Client Support Agreement
8.27.6 Exhibit F — Travel and Per Diem Policy
8.27.7 Exhibit G — MCSO Security Guidelines
8.27.8 Appendix I — Forms
8.27.9 Appendix 2— Interface Inventory
8.27.10 Appendix 3 — Waiver of Claims

SERIAL 13139-RFP
IN WITNESS WHEREOF, this Contract is executed on the date set forth above.
AUTHORIZED SIGNATURE
D(2_ -r6.ve, ze, Lo\r& CEO a- 02006\1-1
PRINTED NAME AND TITLE
&ST, , -g1tiek2- Poil0 1_76k fixeR-f PCUrnoiv,0,. gc, 1
ADDRESS
17-w-- )(iced G9_0 IS
DATE
MARICOPA COUNTY
CHAIRMAN, BOARD OF SUPERVISORS DATE
ATTESTED:
CLERK OF THE BOARD DATE
APPROVED AS TO FORM:
LEGAL COUNSEL DATE
RECOMMENDATION FOR AWARD:
DEPUTY CHIEF, TECHNOLOGY MANAGEMENT DATE
BUREAU, MCSO

SERIAL 13139-REP
EXHIBIT A, PRICE AGREEMENT
SERIAL 13 I39-RFP
NIGP CODE: 208-57
CONTRACTOR'S NAME: Syscon Justice Systems
COUNTY VENDOR NUMBER:
ADDRESS: 6500 River Road
Richmond, BC, V6X 1X5 Canada
P.O. ADDRESS: N/A
TELEPHONE NUMBER: 604-606-7650
FACSIMILE NUMBER: 604-606-7654
WEB SITE: www,syscon.net
CONTACT (REPRESENTATIVE): William Hutto
REPRESENTATIVE'S E-MAIL ADDRESS: williarn.hutto@syscon.net
Payment Terms
[ X 1 NET 30 DAYS
1.0 PRICING: All line item costs are individually Not to Exceed Limits (with the exception of Optional
Work which is an Estimate of Work Contemplated, but not yet authorized in the Scope of Work).
Implementation Costs
Description of Item Total Cost
New IMS Software License Costs $ 2,926,080
Software Configuration/Customization Costs $ 1,786,103
Interface Costs $ 1,522,830
Data Conversion Costs $ 500,010
Training Costs $ 308,221
Travel Costs* Invoiced at actual cost $ 834,271
Other Implementation Costs $ 4,908,215
Implementation Support Costs $ 2,097,431
Performance Bond $ 210,000
Gap Analysis $ 90,000
Optional Technology Offerings* $ 629,521
Total Cost
$ 15,183,162
* The value for this line is not included in the Total Cost

SERIAL 13139-RFP
Maintenance and Support
ntract Year Total Cost
-
3 $
4* Partial Year 297 021 00
5 $ 624,763.00
6 S 624,763.00
624,763.00
8 $ 624,763 00
9 624,763.00
0 $ 624,763,00
Total Cost 4,045,599.00
Projected Maintenance and Support In the event of renewal
Contract Year Total Cost
11 643,505.89 CPI Index 3%
12 662,811.07
13 682,695.40
14 $ 703,176.26
15 $ 724,271.55
16 5 745,999.69
17 768,379.69
18 791,431.08
19 815,174.01
20 $ 839,629.23
Total Cost 7,377,073.86
Total Awarded Contract Not to Exceed Values
Software $ 2,926,080.00
Implementation Cost $ 11,332,810.00
Travel $ 834,271.00
Maintenance and Support $ 4,045,599.00
Total 19,138,760.61.00
NOTE: The annual support fees paid by the County include the subscriptions and/or support related to the above
certain embedded third party programs. In the case of JBoss EM' and BPM/Fuse the subscription is based on a
maximum of thirty-two (32) Cores. In the case of BI Publisher the Oracle license and associated annual support is
based on a maximum of eight (8) [Intel-based] Cores. Any change in the County 's hardware environment (I.E.
additional CPU's and/or Cores) may require additional subscription, license or support fees payable to the
respective third party vendor. In such event, the aggregate annual fees payable under this agreement may require
adjustment. Any increase(s) imposed by the respective vendor upon Contractor shall be passed onto the County. All
such requests for 3rd party support or subscription fee increases will be accompanied by detailed supporting
documentation that explain the necessity of the increase, in accordance with section 2,1 of the Contract.

SERIAL 13I39-RFP
Proposed Payment Structures
Item Description Value Timing
Fixed Costs IIIIIIIIIIIMMIIIIMMIIIIIIIMIMIMIMIIIII
Syscon License naligi $ 1,394,163 Contract execution
Pentaho license 1111111111.11111111111111111.1111111111111111111.11111.11 annual subscription imagi January 2016, January 2017, January 2018
Syscon Services Gap Analysis Report 11111111111111111.1=1111111111= S 90,000 Contract execution
11111111111111.1.111 Already delivered
11111111111111111111111111111111111111111111111111.1M111.111111111111111111111 Performance Bond Eggi S 60,000 Contract execution-First year payment
Follow on payments on an annual basis (last
1111111111.11111.11.1111111111111 ear to be In:gated
IIMIIIIIIIMIIIIMIIIIII Implementation Support Monthly implementation III support 5 46,975 Begin on contract IIIIIIIIIIIIIIIIIM execution then monthly for
42 months
MIIIIMIIIIMIMMIIIIIIEIIIIMIIIMIIIIMIIII Oracle maintenance 8,768 Contract execution, then annually with 2.5%
Redhat maintenance Iiiiiiiiii W iaThttaasii $ 43,501 escalator October 2017, then annually with 2.5%
$ escalator
IIIIIIIIIIIIMBIIIMIIIMIIIIIIIIIIIIIIIIIIIM
IIIMIIMIIIIIIMIIMIII.M=IIIIIIIIIII Professional Services Monthly run rate: Phase 1 5 130,279 Begin on contract execution-monthly for 28
months
IIIIIIIIIIIMIIIIIIIIIIIIIIMIIIIIIIMMIIMIIIIIIIIMMIIIIIIIIII Professional Services Monthly run rate: Phase 2 78,004 Beginning approximately Feb 2017-monthly
for 23 months
IIIIIIIIIIII=Illl 1111.111.11111111111111.1
IIIIIIIIIIIIMIIIIIIIIIIMIIIIIIIIIIIIIIIMMIIIIIIIIIIIIIIIIMIII Timing/delivera ble based
costs IIIIIIIIIMIIIIIIMI
Item Description Value Timing
Syscon License Product Drop / $ 278,832 As delivered-estimated November 2015
IIIIIIIIIIIIIIIIIIIIIIIIIII Product Drop 2 UMW As delivered-estimated June 2016
ElMill=11 Product Drop 3 MEM As delivered-estimated November 2016
Product Drop 4 $ 278,832 As delivered-estimated May 2017
Product Drop 5 $ 273,832 As delivered-estimated October 2017
Professional Services IIIIIIIIIIIIMII Milestone payments IIIIIIIIIIIIIIMIIIIIII
.11111111111111111111.11111
IIMIIIIIIIIIIII Description 1111111111111111111MIMI Note these are targeted delivery dates
Milestone 1 Project Kick Off $ 127,981 August 1,2015
Milestone 2 Prepare Phase Complete $ 127,981 September 1,2015
Milestone 3 Configuration Complete 1,1 [112.51 $ 127,481 April 1,2015
Milestone 4 Interface Delivery 1.1 [R2.5] April 1,2015
Milestone 5 Configuration Complete 1.2 [R 3.0] $ 127,981 August 1,2016
Milestone6 Interface Delivery 1.2 [R 3.0] $ 127,981 August 1,2016
Milestone 7 Define Phase Complete $ 127,981 October 1,2016
SI

SERIAL 13I39-RFP
Milestone 8 Configuration Complete 1.3 [R3.5] $ 127,981 February 1,2017
Milestone 9 Interface Delivery and Data $ 127,981 February 1,2017
Conversion Complete 1.3 [R 3.5]
Milestone 10 Configure Phase Complete $ 127,981 February 1,2017
Milestone 11 Validate Stage Complete ("UAT") $ 127,981 June 1,2017
Milestone 12 System in Production 127,981 July 1,2017
Milestone 13 Completion of Warranty $ 127,981 October 1,2017
Milestone 14 Prepare Phase Complete $ 127,981 January 1,2017
Milestone 15 Configuration Complete 2.1 [R40] $ 127,981 August 1, 2017
Milestone 16 Interface Delivery 2.1 [R 4.0] $ 127,981 August 1,2017
Milestone 17 Define Phase Complete $ 127,981 November 1,2017
Milestone 18 Configuration Complete 2.2 [R 4.5] $ 127,981 February 1,2018
Milestone 19 Interface Delivery and Data $ 127,981 February 1,2018
Conversion Complete 12 [R 4,5]
Milestone 20 Configure Phase Complete $ 127,981 February 1,2018
Milestone 21 Validate Stage Complete ("UAT") $ 127,981 June 1,2018
Milestone 22 System in Production $ 127,981 July 1,2018
Milestone 23 Completion of Warranty $ 127,981 September 1,2018
Milestone 24 Prepare Phase Complete $ 127,981 January 1,2017
Milestone 25 Configure Phase Complete 127,981 February 1,2018
: Milestone 26 Validate Stage Complete ("UAT") $ 127,981 June 1,2018
Milestone 27 System in Production $ 127,981 September 1, 2018
Milestone 28 Completion of Warranty $ 127,981 December 1,2018

ATTACHMENT A
NEW JMS COST PROPOSAL - VENDOR INFORMATION AND PRICING
SERIAL 13139-RFP
N1GP CODE: xxxx
CONTRACTOR'S NAME: Syscon Justice Systems
COUNTY VENDOR NUMBER: Pending
ADDRESS: 6500 River Road
Richmond, BC, V6X 1X5 Canada
P.O. ADDRESS: N/A
TELEPHONE NUMBER: 604-606-7650
FACSIMILE NUMBER: 604-606-7654
WEB SITE: www.syscon.net
CONTACT (REPRESENTATIVE): William Hutto
REPRESENTATIVE'S E-MAIL ADDRESS: william.hutto@svscon.net
YES
WILL ALLOW OTHER GOVERNMENTAL ENTITIES TO PURCHASE FROM THIS CONTRACT ES I
PAYMENT TERMS
NET 30 DAYS
1.0 PRICING:
•I :.: : I I .
"DOcrIption 41.0 ' 1: #.1' Co. „
Summary New .IMS Software License Costs $ 2,926,080
Summary New 1MS Software Configuration/Customization 1,786,103
Costs
Summary JMS Interface Costs 1,522,830
Summary New IMS Data Conversion Costs 500,010
Summary of .11vIS Hardware Costs #REF!
308,221
Summary New .11vIS Training Costs
Summary of Travel Costs 834,273
Summary of Maintenance and Support Costs 615,963
Summary of Other Implementation Costs 4,908,215
'Miscellaneous Costs 300,000
Optional Technology Offerings* 629,521
Total Cost #REF!
.
Page 1 of 29

NEW JMS Exhibit A 13139-RFP
COST PROPOSAL - SOFTWARE LICENSE
Unit of Cost per
# Application / Module Description Measure Units Unit Total Cost Comment
During the GAP analysis several architectural changes were made to support reporting and other needs that were not identified during the RFP, the
changes required additional 3rd party licences
During the GAP analysis sessions, MCSO mentioned that they may be able to take advantage of their reputation and status as a public sector entity
to procure software at a better price than available to Syscon. Unless indicated in the comments, MCSO may safely procure any software in this list.
However we recommend that you consult Syscon during the procurement process.
1MS Application Software
adukt i' trent & 10- Ern/in:A-gent,
1, WorkflowlAIL Core functional 1MS $0
Microsoft SQL Server 2014
2. Enterprise Database
r
3. Red Hat Enterprise Linux Server Linux Server
Red Hat JBOSS Enterprise
4. Application Platform Application Server $0
Red Hat .1 BOSS Fuse Service
5. Works Interface Server, $0
6. Red Hat MOSS BPM Suite Business Rules $0
included in Production pricing as
product will be deployed on
7. Neurotechnology Megamatcher Biometrics Server $0
vmware.
8. Biometrics Fingerprint Client License $0
9. Cassandra NOSQL Database Audit Trail Database $0
10. Pentaho Data Integration Data Upload $0
Core Product and Rec
11. Generic Document Management Management $0
12. Nester Autopilot Performance Monitoring $0
13. Hibernate Open Source
14. Vmware Vsphere Enterprise
Selenium (browser automated
15. testing tool) Open Source $0
,
TrainIng -tnyibpprngnt
1. WorkflowlAlL Core functional iMS $0
Microsoft SQL Server 2014
2. Enterprise Database $0
Page 2 of 29

NEW JMS Exhibit A 13139-RFP
COST PROPOSAL - SOFTWARE LICENSE
Unit of Cost per
Application / Module Description Measure Units Unit Total Cost Comment
3. Red Hat Enterprise Linux Server Linux Server $0
Red Hat JBOSS Enterprise
4. Application Platform Application Server $0
Red Hat JBOSS Fuse Service
5. Works Interface Server, $0
6. Red Hat JBOSS BPM Suite Business Rules
included in Production pricing as
7. Neurotechnology Megamatcher Biometrics Server $0 product will be deployed on
8. Biometrics Fingerprint Client License $0 vmware.
9, Cassandra NOSQL Database Audit Trail Database
10. Pentaho Data Integration Data Upload $0
Core Product and Rec
11. Generic Document Management Management $0
12. Nastel Autopilot Performance Monitoring
13. Hibernate $0
14. Vmware Vsphere Enterprise
Selenium (browser automated
15. testing tool) Open Source $0
Training Environment ware sob Total -
fifij*".ttpi ERUNOWN: lit ,:ealtal _
1. WorkflowJAIL Core functional MS Application 1.. 2,415,000.00 $2,415,000 Enterprise perpetual use license
Initial Uccncc . 5ycon s
t-het-MCSO-a-ir-eaity-ha-s-a-
terprise licence for SQL Server
!! . • : . - • - : co-will not need-to incur this
27 441-c-faseft-SQL-SeFveF : : ::: -: -- 2 Core Units g aelfiltienal-c-ost.
3: --------- - Lin ux Server 1 2 sockets 4 1,625.00 $0 Fefleeteel-in-1\4&-S4a-la
Red Hat JBOSS Enterprise Annual subscription; total cost
4. Application Platform Application Server 4 Cores units 6 2,250.00 $0 reflected in M&S tab
Red Hat JBOSS Fuse Service Annual subscription; total cost
S. Works Interface Server, 4 Cores units 2 5,000.00 $0 reflected in M&S tab
Annual subscription; total cost
6. Red Hat MOSS BPM Suite Business Rules 4 Cores units 2 8,333.37 $0 reflected in M&S tab
Page 3 of 29

NEW JMS Exhibit A 13139-RFP
COST PROPOSAL - SOFTWARE LICENSE
Unit of Cost per
Application / Module Description Measure Units Unit Total Cost Comment
7. Neurotechnology Megamatcher Biometrics Server Server 3 834.00 $2,502 Perpetual use license
Perpetual use license. Physical
USB Don& or internet connection
8. Biometrics Fingerprint Client License Fingerprint Cz 45 47.26 $2,127 is required.
9. Cassandra NOSQL Database Audit Trail Database Open Source $0 Open Source, no licence fee
Annual subscription for three (3)
10. Pentaho Data Integration Data Upload 4 Cores 3 42,400.00 $ 127,200 years starting month 6
reflected in- M&S tab
Syscon had thc selection of a
document management on its
GeneFie-Deeuffient-Management (KG
-road map with a scheduled-
-
2015.
11.
Performance Monitoring J2EE
At the request of MCSO, raised
. .
during the Gap Analysis, we are
and transactional Monitoring-
replacing our Performance
MestelAuteleilot combined. Includes Jkool and JMX laer--C-eFe 42.
Monitoring Solution with another
Jboss App Server Plug in Module-
product to meet MCSO specific
for transactional deep dive-
security requirements.
-14419.1444W-41g
4-2-r
13. Hibernate Open Source Open Source 0 0.00 $0 Open Source, no licence fee
44, Vmware Vsphere Enterprise 14 $0
15. Coplink Product Interface See Exhibit 7: JIVIS-25 and JMS-26 Application 1 $27,000 $27,000
See Exhibit 7:1IVIS-40, IFCS-07 to
16. Touchpay 17 Application 1 $48,000 $48,000
17. Livescan See Exhibit 7: Pre-13 (Bioguard) Application 1 $43,200 $43,200
Page 4 of 29

NEW JMS Exhibit A 13139-REP
COST PROPOSAL - SOFTWARE LICENSE
Unit of Cost per
# Application / Module Description Measure Units Unit Total Cost Comment
Selenium (browser automated
18. testing tool) Open Source Open Source 0 0.00 $0 Open Source, no licence fee
Production. :Environment Software Sub-Total $ 2,665,029
:.IMS:AppliCatiorii;SOftWait::SUbjOtar $ 2,665,029
Administrative Software (e.g.. Project Management; Requirements Management; Change Management; Release
Assumed MCSO et al have access
to standard Microsoft productivity
tools (Office, Project, etc.)
3. $0
4. so
5. so
;:A0Mini4tr4tiv.0:$04woisubJ4tar : . $
Report-writing & Query Tools/Software
Included above in Dev / Test /
Training / Production
1. Oracle BI Publisher Reporting & BI Tools Application ll 9,200.001 $36,800 environments
Page 5 of 29

NEW MS Exhibit A 13139-RFP
COST PROPOSAL - SOFTWARE LICENSE
Unit of Cost per
# Application / Module Description Measure Units Unit Total Cost Comment
2. $0
3.
4. $0
5.
sReport-writing & QUery -Tools/Spftware-.Sub-TOtal - $ 36,800
Testing Software
1. $0
$0
4. $o
5. $0
Testing Softare.S.ub-Total.
Operating System Software
1. $0
2. $0
4.
::Oper atidg'SyStern! :SOftWar0,:$ 00.qotal.,;::, $
Other Software (Technical integration tools, APIs, Third -party)
1.
2. $o
$0
4.
•Other Software Sub-Total
Applicable SalesTax 224,252
10. $ 2,926,080
Please itemize software separately for New MS Development & Test Environment; Training Environment; and Production Environment ; where appropriate.
Please identify and provide applicable costs for optional software products that the Vendor may offer. Note these costs will not be included as part of the cost
evaluation of this RFP.
Page 6 of 29

NEW JN'IS ATTACHMENT A-3 13139-RFP
COST PROPOSAL - SOFTWARE CONFIGURATION/CUSTOMi2ATION
—
Number of Cost per
Module Description of Configuration/Customization Hours Hour Total Cost Comment
Software Configuration/Custornization Costs
F-CT--17 The solution shall provide the ability to enter Snd download court date(s) for multiple inmates
1. simultaneously on one screen. 261.36 150 $39,204
F-CT-18 The solution shall maintain inmate prosecution case and charge information, but is not limited
to, the following: Prosecuting Agency OK Prosecuting Agency Case Number, Prosecuting
Attorney Bar Number and Name, Charges Declined/Not Filed, Date Charges Declined/Not Filed,
A.R.S. Charges Added by Prosecutor, A.R.S. Charge Type (Fel, Misd) for Charges Added by
Prosecutor, Count Sequence Number for Charges Added by Prosecutor, Preparatory Offense
Code, and Date of Occurrence or Charge Date or Charge From Date. This ... - is also . - , to functionality _ F - IN
2. 261.86 150 $39,204 39-::
F-CT-21: The solution shall provide triC abil t' to schedu e an itroate court case and identify aria r050 -tel - 59S:6rre.i0.014116-.idilja.:orl 4I4.ript
khethilingteriflicts'bYtekiirpriaritization: -:5Scliechiling:ReqUll'erneftW i : prieritiZehntkres014e.it, lus..tfagi:
oil f. iF,ct Otf_niuMiafl-wil(ritt* call, ,
ertistelef.5.iieeWi4F4.4 .45.:: '
F-CT-23 The solution shall provide the ability to produce a court schedule which includes but is not
limited to: inmate's name, assigned cell location at court building, case number, court room,
court time, and judge, most serious charge, special needs, wheelchairs, keep-sways with same
court date and man warnings, See Scheduling Requirements.
3. 261,36 150 $39,204
f CT 32 - • - - - - - - - - - - -
This data exchange includes but is not limited to the following data elements: Next Court Date, '
• :. - •
Will be addressed as part of interface
4. 26146- ISO 0 quote ......_
F-CT-33 The solution shall provide an authorized user the ability to authorize payment of bail bond TIT.i.i.t0Vii!6?.?.10.4110.0.00...b60:::0.sig§0 . ... .... .. ......... .. .. . ....... :
money from the inmate's trust account, tilW4iftht.serld:ThnififbricoUr'ibYdrifiti!fOr.:
. 52.272 150 $7,841 .W4irkficiw.: , :
F-CT-36 The solution shall determine if the inmate has sufficient funds by comparing the inmate's trust ThIrsi•Oqiiireinerithag:rie*-beott .a'sketf
account with the bail bond amount, fci.befige . and it neit:PriOdinbatfrrla0.10:
6. 52172 150 $7,841 Workflow
P .2ttA7 wants , frih.tk'aii4i1b-oliii'ti-h4 , i6IiItiOni4halt:, , - --- ---.
deduct the b8il _ _ -Vcindiahlo-ant _ from _ the lOmate's trust 'NO account _ _ adjuSt _ the inmate's. _ . bond
tiaidaitiount.,:.-.-- __$C.i linclucleti as part of F,CTi-36
.
KT.;38 1.064.-d .'der.irafialia4611.fiiriiii available the SOlutloii:siiiii: -a1 .7t thdUSer on screen ... - - .. - . ....
4.-lf!- -tiLidifiiil.'Ort 004T-361. -
F-CT-SO The solution shall allow for entry of bail amounts from two or more funding sources. This i'etildiFiment fi6 ::•fii;Verleeri4sked
fcif:?:$1.1ore and rat on Our readinanfor
7. 52.272 150 $7,841 iiidtkflew....:
,F CI 47 Cn:.,i daily .basis, the solution shall produce a Bond Fees ayment report. The solution shall
..•
24/3/15: Removed from scope as per
8. Requirements.- 261.26 460 $0 direction from MCSO
F-CT-50 The solution shall provide an override for bonding fees restricted to authorized user with a text
9. field for additional comments. 52.272 150 $7,841
F-CT-55 The solution shall provide the ability to calculate release trifle based on state, court and county iiiilddeiF.CTt,87,!,f;SN;5;SNA:F..s.*::.:::::::
10. requirements. 609.84 150 $91,476 .1.6ii,F.,$N40:::
F-CT-63 The solution shall provide the ability to maintain a list of out-of-county arraignment dates and
times, to be used when releasing a subject on his/her own recognizance for an out-of-county
11. warrant. 52.272 150 $7,841
Page 7 of 29

NEW JMS ArrACHMENT A-3 13139-RIP
COST PROPOSAL - SOFTWARE CONFIGURATION/CUSTOMIZATION
F CT 64
12. r ecognizance for out of county warrants. 52.272 150 80 24/3/15: Roadmap item
F-CT-87 The solution shall compute an inmate pay and/or good time balance for inmate work performed.
lnoltided on F-CT-55
F-CT-88 The solution shall record canteen discount for an inmate participating in a designated program.
$0 Included in F-TA-20
13. F-CT-93 The solution shall provide the ability to record the entry of a seal or unseal action on the 52.272 150 $7,841
inmate's record and include the following but not limited to:
Current Date/Time (timestamp from the solution)
Staff or Judge authorizing action
Case Number
Action Reason
Preservation of Evidence
14. F-CT-98 The solution may provide the ability to export release and victim information to a notification 261.36 150 $0 Idenfied as a Gap, See Line 40
system.
Agreed to Workaround option 1
15. F CM 4 62.272 80 24/3/15: Removed from scope as per
direction from MCSO
16. F-441;1-4 52.273 168 $0 24/3/15: Removed from scope as per
direction from MCSO
1. ROPiPtileld-fi:Om's .crooe(53%.294)::a$:.rincso
,
includes thiZrettulreMent,.. ,
e_frorr, justist, intcrstatc cornpact Rulo-11 oFdo
2. 24/3/15: Inc.uded in Workflow
19. F-10-36 The solution shall record facility count, number a transfers and releases, medical statistics, 261.36 150 $39,294 0largleatiOnteOulredfrenf'MC501 . is this
visitation statistics, incidents, and recreation offered, accepted and refused (by facility and
inmate).
MCSO , response: This requiremen
rotate manual reports that are
prepared each day by the facilities staff.
in Order to provide these_stat!stits
process „ toberint . (similarto . ,
the-anapshot.process)tnar „ calculates:the
piArrf:sAtOsti:dislAhl...ttchref :tae
Siarifhaty.TrekUltS'for future analysis and
reporting.
Syscon response: the cost of $39 204
that was quoted for F-JO-34 shàutd:stay
aa.quoted-agid.:will'oovenprodutt report
model development as well as any
additional -costs -to expand tile snapshot
process to include this additional data.-
F 10-47 6E1944 $0 Quoted-as-a-GAR
Page 8 of 29

NEW 1M5 ATTACHMENT A-3 13139-RFP
COST PROPOSAL - SOFTWARE CONFIGURATION/CUSTOMIZATION
21. F-PG-29 The solution shall provide a way to track if badges have been issued, are about to expire, or have 261.36 150 $39,204
expired and automatically notify the volunteer.
22. F-RP-14 The solution shall provide equivalents for all existing management reports currently -iri use by 435.6 150 $65,340
the jail. See Exhibit 9 - Report, Queries and Messages and Exhibit 11- Bidder's Library for
additional information.
23. F-SA-52 The solution shall provide the ability for an administrative user to maintain the Case Sub Type 52.272 150 $7,841
code table to be used throughout the solution. .
24, F-SA-57 The solution shall provide the ability for an administrative user to maintain the Time Of Day code 52.272 150 $7,841
table to be used throughout the solution,
25. F-SA-58 The solution shall provide the ability for an administrative user to maintain the Subpoena Service 52.272 150 $7,841
Type code table to be used throughout the solution, .
26. F-SA-59 The solution shall provide the ability for an administrative user to maintain the Warrant 52.272 150 $7,841
Response code table to be used throughout the solution.
27. F-SA-70 The solution shall provide the ability for an administrative user to maintain the Prosecutor code 52,272 150 $7,841
table to be used throughout the solution.
28. F-SA-84 The solution shall provide the ability fer in administrative user to define and modify an expense ' i 24144 2$/3/15;lilftittPlagi:ges:.thafial:'41 :466 .::
type list in the solution and have these be available to staff. fieltl;Withldlop .tOwn values will satisfy
his NEii,iiNthOti i :- - -
29. F-SA-111 The solution shall provide the ability to maintain administrative sealed code tables indicating the :,,F1.3iir 4S-1") 0 .;.20111-0?..iNiOcirit$0017h6 this
reason for action. requirementqls*faf a cotprn...fieliCI.With..- -
diop,doWn vainis lisectforinditatinv-the
- reason _ _ - tile _ record _ was sealed _ _ : _
30. F-SC-5 The solution shall flag and/or bump inmate's conflicting schedules and provide automatic 435.6 150 $65 340 .tnbluiles F-CT 21
notification based on criteria provided by MCSO.
f SC 3G - - - - - - - • .
24/3/15: MCSO agrees requirement will
31. 52,244 45.0 $0 be satisfied with screen Banner data
P-SG-a.7. 24/3/15: Removed from scope as per
32. -- 52.27a ag 69 direction from MCSO
33. F-WK-71 The solution shall be able to send message based on routing technologies approved by AC115 and 435.6 150 $65,340 lilfilSOMitlWfof-Pf.00ILicil•ChAngeSlto
015 policy. 4lIPPOMIlielslendirgV4.- 61C0tviili of
l.ProrlrOti.clirt.i'llekteti.re.:0341lit:: l:
a4erical;i:::A:deiailel*-anatySi.i!Wiii4d::::!:.:
neecl:W.DO.(.Neilitfcep- ,tfef0e*dln -. -r:
iiiIiiii:‘iiOCE[643: ' .. .
34. F-WK-72. The solution shall be able to receive messages based on routing technologies approved by AC115 435.6 150 $65,340 Alisifferritlorikoduet ... . .- ...- . - . changes . - to -
and CJIS policy. i'ii0POrt the sending and receiving iiafri
Y#00.0001...st0.1.goCut.,:inpm.gi.tiv -- :
.#0'riimig:-:ixi:Wiiii0Eiiiii0:i1+16Lild '
ineett.iaiicumfakaken before we doult1::::
revise :60r Prieiht. - .•:,
35. F-WK-74 The solution shall be able to re-transmit messages based on message transaction logs. 435.6 250 $65.340 ThiS:igfik:fh'fife0iiiiikr.i.Ornework
Oeinig'biliii4Tfhtla:WpfktoW:::: ,
36. F-WK-75 The solution shall be able to record all sent and received messages into transaction and audit 435.6 150 $65,340 Thisfa'filetheinessagirig:lfietrieWOrk
logs. .bohg hoit,:zt.rtoOskflows : :.:.!,.:
37. P WE 121 - - — • 261.3G 0 Determined it could be met with
for a reason for removal, product.
Page 9 of 29

NEW .IMS ATTACHMENT A-3 13139-RFP
COST PROPOSAL - SOFTWARE CONFIGURAT/ON/CUSTOMIZATION
38. •F-464 . • - - - $0 Identified as a GAP in GAP Analysis
preference to having the proxy :core asscasment auto answered by the system. Out of the box, Report
' • • • - . . - 24/3/15: Removed from scope as per
-- direction from MCSO
criminal history, including age at first arrest, which is available in the MS.
• : - - -
-
39. F-C1,-45 This requirement was discussed during the SIMS session of the gap analysis. $10,850 Identified as a GAP Ps CAP ArialYsis
The system currently does not automatically return funds to the inmate trust account when a Report
bond is voided.
Originally it was anticipated that this requirement meant that an authorized user could correct 25/5/13.gyecon, cwsflrmwe,. A,.il,l.:..split,tii
mistakes in data entry. If there is a voiding of a bail bond that took funds from the inmates cdst of this requirement and:$1:05Cr It
account then it is assumed that the money would have to automatically be returned to the the MC50 portions of the split
inmates trust account
40. F-C1-98 This requirement was discussed during the SIMS session. .50 ldentifiedais GAP in GAP Analysis
This requirement was not considered mandatory; Syscon's original response was that it would Repent
be an interface but it was not priced for inclusion in the original proposal. No interface is
currently in use as MCSO handles all victim notifications themselves. V:aSaCO ::, .:.chose workaroun : d.M .,„..,:. tiorI for
The Workflow product madman has a full suite of Victim Services functionality, currently Phatel of trie go-five. Syscon:cdrifirms
planned to be deployed i i, the new-1MS in Phase 2. This means that victim information will that the victim data entered in the
require some workaround solution for Phase 1. The following are the options: interim . : .., $OlutionviliTemaimavailOie ...., .,. .: .. .... ,. : .:.,.. .... ::. . In
1) In the phase I project implementation, basic victim information can be identified and the:origihalilocation,in ,the ngein'OnCe:
recorded in Workflow Triggered events may generate notifications to the VANU, and tne,final Solution isimpletherited:(e4.!::
chronological notes (case notes) can be recorded to document all notifications completed. lie case notes will not betranslatedlO.:
2) As an alternative, Syscon has a product VINE interface that can be implemented in Phase 1 to the victim module data points).
perform all of the applicable and relevant victim notifications. Requirements need to be further
defined before the supporting interface requirements can be confirmed. This will be done during
the Define Phase.
The VINE interface is dependent on the MCSO having an established account relationship with
Appriss (VINE). Further information about VINE may be found at www.appriss.com/vine
Note: this gap analysis report provides the product interface cost for VINE, any associated
services will be reflected in a BAFO.
Tentative schedule for Option 1 is Workflow release 33— Project Release 1.3
F-DS-1 This requirement was discussed during the technical requirements session.
To satisfy the requirement Syscon will extend Workflow to allow Alternate IDs (such as TOC ID)
to be configured at the user Level (with an expiry date). Additionally, we will provide the ability
to configure which Alternate IDs get logged to the Audit record. Identified as a GAP in GAP Analysis
41. $63,850 Report
F-DS-8 The Workflow audit trail functionality does not currently provide the ability to capture the TOC
ID on audit trail records, Identified as a GAP in GAP Analysis
As a future roadmap item, Workflow audit trail functionality will be enhanced to include Report
Alternate 105 that get logged to the Audit record.
42. Cost Included In the gap estimate for F-DS-1 $0
Page 10 of 29

NEW iMS ATTACHMENT A-3 13139-RIP
COST PROPOSAL - SOFTWARE CONFIGURATION/CUSTOMIZATION
43. F OS 11 $0 Identified as a GAP in GAP Analysis
Report
. „ . .. .... .. -
2415/15: Removed from scope as per
direction from MCSO
44. 45-1-44 Identified as a GAP in GAP Analysis
5•BEIS4RGI Report
- - - „ 2413/15: Removed from scope as per
valuation of inventory. MCSO staff would like the sew system to h3Ve the same capability. The direction from MCSO
. •
..,
-
, 7 t T . “ .• ' • - ..• .. . • -
Not estimated.
45. F-Fl-7 This requirement was discussed during the Financial gap analysis session. $31,925 Identified as a GAP in GAP Analysis
A Per Diem fee collection against inmates should allow for the collection of fees on a daily basis. Report
It is not currently done but the system needs to have this capability. This collection could be
accomplished on a nightly basis through use of a batch routine or by collecting fees by deducting
a set amount from receipt transactions.
This process will need to deal with exceptions, such as indigent inmates, If unpaid per diems are
accumulated and carry forward between bookings, this capability will need to be further
enhanced.
This gap is tentatively scheduled, upon approval, for Workflow Release 4.5 —Project Release 2.2
46. F-Fl-20 This requirement was discussed during the Financial gap analysis session. It was determined to $0 See ROM-1
be a future requirement. A Kiosk provider has not yet been chosen to enable this functionality.
47. F-FI-23 This requirement was discussed during the Financial gap analysis session. It was determined to -r T A,„;01 ,-,15,,o-,.,,.** ' -.K-F..-.4Ize 1, Al; .. 1
be a future requirement.
Page 11 of 29

NEW JMS ATTACHMENT A-3 13139-RFP
COST PROPOSAL- SOFTWARE CONFIGLIFtATION/CLISTOMIZATION
4/3. F-Fl-30 New requirements to create an A/R for agencies that are billed for services and to capture $219,615 Identified..-44rGAPIfr GAP 'AnalYSis
adjustments and to track what has been paid. Billing data is currently entered into QuickBooks Report- ..
and the invoicing as well as invoice payments are tracked in this accounting system. MC50 staff
would like to see this capability integrated into the Workflow Billing of Services solution. hic50 hopt, g to share same of cost of
Billing reports are generated once a month from RAS in order to provide Finance with the billing blffing.
details for each agency. These reports rely on a nightly job that compiles the billing detail for
each inmate. A single inmate may be billable to as many as 4 separate agencies at one time. The Sysdon response This is a -very
amount charged per agency is decreased based on the number of separate billings active at one demanding requirement which we
time. befieVe-is largely custom .and ,not how
1: Business rules are required in order to determine what agencies need to be billed per inmate. we nave impemented for othefclients.
1: The large volume of billings (5000 -6000 inmates billed out per month) will be a factor in how
and when these rules need to be applied. discOuntbnthispifcedfwbrL
1: The system must allow for adjustments to be applied both at the inmate and agency level
when discrepancies arise.
0 The Workflow product must provide the infrastructure required in order to deal with the
compiled billing records and to produce the required invoices.
El Need to put an accounting application underneath the Workflow Billing of Services solution.
This will allow for a seamless transition between the generation of invoices and the receipt of
payments. GAAP compliant accounting rules will need to be enforced in this solution.
This product extension will be developed, upon approval, and is tentatively scheduled for
Workflow Release 3.5 - Project Release 1.3
F-GN-2 The Workflow application is designed so that data is always live and always available. Data $95,77C cioDtified- -4.5 -a CAP -in GAP An alysLs
archival is not a restive feature of the Workflow application; rather it is a feature of its underlying
technology stack, and a skilled database administrator (MA) can utilize the components of the
Workflow stack or third-party tools to provide data archival capabilities if required. VICSO question: Can the Audit Records
During the Technical Requirements Gap Analysis session MCSO indicated that audit trail was i:.e,:wirOtP-14:,a::;SP7PkOterSCW,dat4base?
significantly high volume and could burden the Workflow database. To address th;s problem his separate Sdif.r.daiabii*iiiild NOT
Syscon will enhance the Workflow audit trail functionality as a future roadmap item to use a No ie in the Workflow database
SQL database which will provide advanced features for managing big data.
This gap is tentatively scheduled, upon approval, for Workflow Release 4,5 - Project Release 2.2 4kscon -reSponse: Having audit data
;tared :n-1 a;Lseparbt,e 0.0tatias4wilOnci.kr
lie situ e COSt whdthèr-g is 35th.
J.at0*..or a Nii$P.L.000180..W.0.40:::.!: ,::,
lave:sphia COneorris.on-the,p-Cifoihiinde::
- -
friplicatiOnS - if SQL IS used as SQL server
fpg.:0t:bave:thes;me.-Opab4iti Os fur
iOtiOrelt igg:,t.laadt:tre-$.141-:-,' this
cc do not coeWeit.ali:hp--:aFatfit r; • - data
.ifiFti:SS'(e.g. if MOO orilyOnOrted
:ifi'6!f.41:tis4 of dpt.ok i.iph as the past
and ire proa4iii:i"..auout-ardhifirit
log ogke#,ertygarj then th.5-',7d.waWo
49.
Page 12 of 29

NEW 1MS ATTACHMENT 4-3 13139-RFP
COST PROPOSAL - SOFTWARE CONFIGURATION/CUSTOMIZATION
PGIV:14, . The-saltition'Sfialf:pratfidethe abty' tiirliSe:a card -reatlefferceptiiring. data , Wom.Wdraoef'S. $3t923 25I3/15::"Thiateqtrirerrient,Wat ..'
license or ID card.: Data should automatically populate fields in the Solutiot . previously missed from tirepricing sheet
arid has crow beenadded In. -
This requirement te ai:Mairt.hipe•
tYpe:Ofreadeb:Wlie ..,.... : :. .. ;......... -reaS F-10-47 _ ,'relate
tcis:FTI.D.or scanning. _
F-GN-22 During the Messaging Gap Analysis session it was agreed that the Warrant checks via ALFTS and $0 Noadditionatost. .:.:: ..: solution - this is
NLETS would be performed using JWI arc/ as a result this would no longer be a requirement for inclUded in tne NA :interface -
the new JNIS. There will be art interface from JMS to 1WI; users will have the ability to perform
warrant checks will be available to users through the JWI.
50.
SI F-GN-32 The concept of self-service kiosks was discussed during the Gap-Analysis. At this time there is ISee RO r.,1 -1
not enough information available to accurately define interface requirements that may be
needed to deploy self-service kiosks. As such this is deemed to be a potential future
requirement. See also NF-AC-1.3.
52. F-GN-36 During on-site gap analysis, it was learned that scheduling maintenance is not something that is $0 Cost not provided
currently performed in the existing 1MS. This was described as a `nice-to-have'. Workflow is able
CO track scheduled maintenance inspections, but creation of the schedule is a gap. The ability to 24/3/15 MCSO agreed to use work
schedule such maintenance is not an ideal fit for an inmate management system; therefore it is around using task list
not planned on the product roadmap.
It is recommended that shift logs be used to track all scheduled maintenance inspections and
occurrences.
53. F-1-113-1 This was originally defined in the RFF' as Challenging or Costly Requirements and was therefore $74,350 ldentified-as it GAP4o.GAP - nalysIS
not quoted In the proposal. It was discussed in the SlM5 gap analysis sessions. Report
The gap analysis has that MCSO requires this functionality and as such is a Gap.
The ability to dynamically associate the proper data elements to each hold type is required by Cross reference to F-HD-2, F-H0-6, F-i-I .-
MCSO. Other requirements in this section are dependent upon this requirement being available 12, F-HD-14
including;
F-HD-2
F-HD-6
F-FID-12
F-HD-14
Holds and out-of-jurisdiction holds functionality will be extended to meet this group of
requirements. The detailed requirements analysis will produce a design specification that will be
developed and is tentatively scheduled for Workflow 3.5 Release —Project Release 1.3
54. F-HD-2 see F-HD-1 $0
55. F-HD-6 see - D-1
56. F-HD-14 see F-HD-1 $0
Page 13 of 29

NEW JIMS ATTACHMENT A-3 13139-REP
COST PROPOSAL - SOFTWARE CONFIGURATION/CUSTOMIZATION
57. F-IN-2 $63,850 Identified as a GAP in GAP Analysis
Report
This requirement was discussed during the Intake gap analysis session.
The pre-booking system will enable users from other agencies to directly access the system, but
does not currently contemplate login by ORI; rather by user name and password. ORI is an
identifier issued to every law enforcement agency by the F9I. The challenge with logging in with
an ORI is that multiple users will be associated to the same ORI.
As part of the pre-booking product development, the detailed requirements and approach will
be identified, resulting in the development of an extension that will enable other agency users to
login in a manner that is easy to configure and maintain by the MCSO.
This extension, if approved, is tentatively scheduled for Workflow Release 4.5 — Project Release
2,2
FIN-39' -:;$0. (nOided .Wilh.f...01-1.5
Itip,,.s.0)..i.i . ..tiortili k_€- ilV. ipta0,..i,i?..iii .4..".a. t.:t. booking ..i!„..:,4. 1)_.er., sting_ ... b uti'.1pAilli"..1.,it...e:d to the
following:, Process Ca oINumberPCN;1thil 8aokeds-A<fi,ll, Date of original Arrest r; r
Stirrtrhorl.: :FihgotOrinVng; i0rigiriatthg ibeeking):Agericy Identifier (ORil -, Soaking Number, -:-:
Ar resting Agency Case N Li in b.s.riior 0 epartmentals.iReport IORINurriber-,:,:- :Booking-A,R:5: :Charge,
Eleigkingt,RI:!:; Charge Type (Fel,: iMisd,Lid,,Rndking--,g.harge :SriqUertee.-:Nciiiiiftef;:;BOOking
Ri.'-ektatOfikOffejisepidt ',,,:ictirn CodefrmiltipiejValues}, Net Referred for Prosecution, and Date
NiAltefeir .iiiii foriProSecUtion4t - , 1
58. F-10-47 $207,700 Weittified as a GAP :in GAP :Analysis
fteport -
Workflow provides the ability to capture information using devices such as barcode readers,
It was learned during the gap analysis session that the intention of this requirement was to CrosiSreference TC.; F GN 13
provide a more robust event tracking system whereby a device is used for recording the security
checks performed by officers. The officer will log on to one of the devices and begin his security IhisliqbtrerMent-t'elateSle-lri.D;Or :.„...,..,-,..,., . - ., _ _ „„.,...........,: .,.. ....„,.....„,
check rounds, scanning the security check point barcodes along his route. The records of his Scanning WhereasiF;GNLISWates : to a
::
scans would show the order in which he walked his route, arid at what time he scanned each :mag stripe type or reader, :
checkpoint. When the officer completes his rounds he can upload the collected information to
JMS.
Workflow will enable users to record the results of security checks and other welfare checks in
the system in Phase 1.
Functionality to support officer security checks as described above lean extension; if approved,
will be tentatively scheduled for Workflow Release 4.5 — Project Release 2,2
59. F PG 10 $0 Cost not provided.
It was learned during the Programs on site gap analysis that it is necessary to traek-beth-the-tinne- 24/3/15: Removed from scope as per
" direction from MCSO
This provides jail staff with the information required to facilitate more timely in and out
F-PG-32 The soltition aliaS pitisilde::a -Waci to nionictir 15-iiekgrarid--'dheck:.01agfesS.:i ,:- MU-be:WO-tern:field
FFPG-,33 , The'sdliitiortS all procidea,way to:sytte ti Rymbve a VOIPfiteertO-tberiext step in the Wilflae:cCiStoMliOld ,
s.cieess, ,:--,- -.,------- -_,. ..„. ...,
g--.PG;i35: The:Solutioh'sh'elPigiiiiiiforth:,0:1•OboitVtd7geort voluoteeliiiiiltietiiii6:: itia.0.-s-Niiort
Page 14 of 29

NEW WS ATTACHMENT A-3 13139-REP
COST PROPOSAL - SOFTWARE CONFIGURATION/CUSTOMIZATION
. F-PR4 This requirement was discessed during the Intake gap analysis sessions. $69,850 Identified as a GAP in GAP Analysis
The system does not currently provide the structure for property to support this concept of Report
scanning or recording the precise location; that is, the chain of possession of property as it is
transported. Rather, Workflow allows property to be tracked by location. It is further not
possible to look up the last known location for a property item. This would need to include chain
of custody through from the point of arrest, (pre-book) through release from jail.
The ability to track the location of property at any given time is what is required. This means that
every possible place that property can be must have the ability to he recorded, MCSO has a
strong interest in the scanning by barcode or possibly REID as an option in the future.
Additionally, the need to identify who had possession of the property at each location (to
support evidentiary chain of custody! is required.
The functional requirements for this level of detailed property tracking; ie. Chain of possession,
need to be gathered. This is an extension that will be designed and developed if MCSO decides
to proceed with this extension and is tentatively planned for Workflow Release 3.5 - Project
Release 1.3
61. F-PR-8 This requirement was discussed during the Intake gap analysis session. $12,770 Identified!at-sa.GAP in GAP ,Annlysis
The original understanding of this requirement was that a grievance can be filed, by an inmate Report
for a loss of property.
During the gap analysis session for Intake, it was learned that a property claim is considered to Includes F- 10 and f-PR-11
be a distinct item that may be linked to a grievance. MCSO need the ability to create a property
claim for an inmate who Is no longer in custody (Inactive).
A new product extension to aliow users to generate property and loss claims that may be linked
to a request / grievance will be developed upon MCSO decision to proceed with this gap. This
extension will include the ability to record lost property and found property that is not
associated to a particular inmate or person. Tentatively scheduled for Workflow Release 3.5 -
Project Release 1.3
62. F-PR-10 included with F-PR-8 Incl id 10R,8 arieffPR- 1 -
63. F-PR-11 included with F-PR-8 Iv.,..1,,,A-'=OR,&.aefd.F-PR-.10
64. fpg: 13 - 44 ideiiitified:4-a GAP46.:GAP:'0405- .:.:..,
IintlifigilW9t0e - . Report
..,,--. ------
2.5/8. 115.eCOtg$I2,170)..rerneved ..„.„: ., .,.....:„ „„. „ ..,.. a 5 F-
PR it libt,teqUitethif FeRftr1 goes
: The-grip is-pr;oeapaQtely.ir-orn-F-P -6.2 t-- ahe.id
approVed. If F PR 1 -41oes.=get approvd, this grip will no longer b: [I._
65. F-RE-9 This requirement was discussed during the Release gap analysis session. $0 Identified as a GAP in GAP Analysis
Report
Currently victim notification sometimes occurs prematurely due to the timing for the release
notification which means the victim has to be notified a second time if something is found that 24/3/15: MCSO agreed to workaround
will keep the inmate detained. MCSO would like a way to inform Victim Services once the option 1 included in F-CT-98
release has been confirmed. This may be considered a new requirement since it relates to Victim
Services.
During the releases session there was a lot of discussion around ensuring that the inmate not be
released until victim notification occurred.
It is recommended that a task be created that will allow VANU to indicate that the notification to
the victim has occurred before the actual release task can be performed.
This could include a Release Dashboard so that all units can see what steps have been completed
prior to the inmate being released.
This small extension is tentatively planned for Workflow 3.5 - Project Release 1.3
Page 15 of 29

NEW ..IMS ATTACHMENT A-3 13139-RFP
COST PROPOSAL - SOFTWARE CONFIGURATION/CUSTOMIZATION
Cost not provided.
24/3/15: MCSO accepts Workaround to
This is a deviation from the fundamental approach to Workflow product security authentication, set account expiration date which will be
66. F-SA-8 See Section 2.15, Non-Functional Requirements. 50 set to TOC expiration date.
The solution Shelf- allow sentence types f0 be user cohfigUjrable and allow fO00: ..ehitrY4t:t.:,
F'..St+-5 sentencing algrinithMteberaSsOciatect with each sentence type: ' 50 Included in F,-CT-55
The solution so o Wallow the end i. cc theabilityrto convert a fine 50 sentenced timei(doOr for
F-SN,43, , clays and:recalculationj. ',Conversion argorkthinjMust -,be user,ciainfiuraOle. ., Ingludediih -,F.-CT-SS:
67. F-SNI-10 During discussions with SIMS it was discussed that the application of work credit based on $45425 Identified as a GAP in GAP Analysis
attendance of work must be automatically applied to the sentence. Report
SIMS still requires the ability to manually adjust credits as well.
The automatic application of work credits based on attendance will be developed and is
scheduled, tentatively, for Workflow Release 3.5 — Project Release 1.3
6B. F-TA-13 This requirement was discussed during the Trust Accounting gap analysis session. $0 Sef.ROM4
No Kiosk provider currently selected. This is a future requirement and Kiosk integration has not
been quoted.
59. F-TA-19 This requirement was discussed during the Trust Accounting gap analysis session. $0 See ROM-1
Kiosk notification is a future requirement and cost has not been quoted.
..,..,.... . ,....... ......... ..........,........
69. F-TA-20 This requirement was discussed during the Trust Accounting gap analysis session. $77,050 Identified:as a GAPArtgAZMalysis
Some programs and kitchen workers may receive a discount on their orders. The discount is Report, • • '
applied to the entire order but does not apply to some items in inventory.
During the session it was learned that the desire is to link programs and work profile to canteen thludes P-CT
so that discounts can be applied automatically.
This enhancement is dependent on tracking those jobs and program assignments that are
eligible for discounts as well as flagging those items in inventory that cannot be discounted, The
system needs to have a mechanism for manually applying a sales discount in order to deal with
exceptions. The discount amount to be applied should be configurable in order to allow for
future changes. An alternative approach would be to display job/program assignments to the
user when processing sales orders and allow them to manually invoke the sales discount.
If this gap is approved, it is tentatively scheduled for Workflow Release 4.5 —Project Release 2.2
70. r gVP 1 - $0 identified as a GAP in GAP Analysis
a-Rew-req4ifeReatr Report
(not currently in attachment DI
24/3/15: Removed from scope as per
direction from MCSO
71, N/A Batch processes to create rightly snapshots for reporting environment. $15,690 Snapshots to support proposed
reporting environment. Data Warehouse
is not included and is estimated
separately on the options tab.
SO
$04-Vores:00 tkni,cogori:iipificiA:Topir.-. $ L786,103
Page 16 of 29

New JMS Exhibit A 13139-RFP
COST PROPOSAL - Interface Design, Build, Test, Implement
Cost
Number per
# Interface Description of Hours Hour Total Cost Comment
Interface Design, Build, Test and Implementation Costs
1. Common JMS Messages See Exhibit 7: JMS-01, JMS-02, MS-03, 1,148 $105 $120,540 Costing revised from orginal based
JMS-04, JMS-18, JMS-19, JMS-20, JMS-41 on number of message types. JMS
18, IMS-19 and JMS 20 are
bridging interfaces that were not
previously costed.
2. iCIS See Exhibit 7: JMS-05 60 $105 $6,300
3. Video Visitation System (WS) See Exhibit 7: JMS-06, JMS-07, JMS-08, 1,450 $105 $152,250 New interfaces between Workflow
JMS-09, JMS-10, JMS-11, JMS-12, JMS-13 and Securus VVS solution will be
designed and implemented.
4. Pre-Booking to JMS See Exhibit 7: JMS-14 320 $105 $33,600 Bridging Interface - was not
previously anted.
5. DOC (AZ Dept. of Corrections) See Exhibit 7: JMS-15 0 $o $0 See Options tab
6. US Social Security Administration See Exhibit 7: JMS-16 80 $105 $8,400 This interface may not be
required. Potential for satisfying
this requirement via a custom
Oracle fil report. Further analysis
required.
7. AZ Dept of Economic Security See Exhibit 7: JMS-17 40 $105 $4,200 This interface may not be
required. Potential for satisfying
this requirement via a custom
Oracle BI report. Further analysis
required.
8. JMS-1FCS See Exhibit 7: JMS-21 0 $ 05 $0 This requirement will be satisifed
by a Workflow custom report.
— 9. Avaya 1VR See Exhibit 7: JMS-23 280 $105 $29,400
Page 17 of 29

New 1MS Exhibit A 13139-RFP
COST PROPOSAL - Interface Design, Build, Test, Implement
10. Mug Shot See Exhibit 7:1MS-24 160 $105 $16,800 One-way interface from 1MS to
the IWS Mugs hot solution
(CRIMES). Access to the mugshort
from Workflow is assumed to be
managed through a direct call to
CRIMES via an existing CRIMES
, API.
11. Mug Shot to 1MS New interface to bring mugshot images 60 $105 $6,300
into Workflow using ImageWare API
12. 1MS to Court Ops See Exhibit 7:1MS-28,1MS-29 320 $105 $33,600 Bridging interface
13. ITS (Inmate Telephone System) See Exhibit 7:1MS-30 160 $105 $16,800
14. MUGSHOT on MCSO.ORG (via See Exhibit 7:1MS-31 160 $105 $16,800
Batch Server - 231)
15. ERR See Exhibit 7:1MS-42,1MS-43, JMS-44 600 $105 $63,000 Also includes interfaces to support
Health Care Scheduling and Proxy
Score (new)
16, Pre-Booking - External Agency See Exhibit 7: Pre-01, Pre-02, Pre-03, Pre- 760 $105 $79,800
RMS's 04
17. MCSO RMS (Records Mgrnt See Exhibit 7: Pre-05 400 $105 $42,000
System)
18. iCIS See Exhibit 7: Pre-06 320 $105 $33,600
19. Phoenix (PPD) See Exhibit 7: Pre-07 60 $105 $6,300
20. Common Case Number (CCN) See Exhibit?: Pre-08 320 $105 $33,600
21. Electronic Health Records (ERR) See Exhibit 7: Pre-09, Pre-10, Pre-11 500 $105 $52,500
22. TouchPay Cashless Kiosks See Appendix 2: Pre-14, IFCS-12, IFCS-13, 120 $105 $12,600
(Intake, Release and Lobby) IFCS-14, IFCS-15, IFCS-16, IFCS-17
23. PHReD See Exhibit 7: 0J-02 120 $105 $12,600
24. Reports See Exhibit 7: RPT-31, RPT-32, RPT-33, RPT- 600 $105 $63,000 To be confirmed as interfaces -
34, RPT-35 remove if not applicable.
25. Justice Web Interface 960 $105 $100,800 Includes comprehensvie analysis
and design to maximize use of
MI.
Page 18 of 29

New WIS Exhibit A 13139-REP
COST PROPOSAL Interface Design, Build, Test, Implement
26. Offender Based Tracking System 320 $105 $33,600
(OBTS)
27. Tantus Interface & Conversion 4,537 $120 $544,440 Conversion Lead removed and
Lead combined with Interface Lead.
28. RPT-01 thru RPT-30 0 $0 $0 Will be handled as custom
_See Exhibit 7: RPT-01 to RPT-30 ,reports.
Interface DeogorpOuildiTest and linpiernent on Total $ 1,522,830
Assumptions:
Page 19 of 29

NEW JMS Exhibit A
COST PROPOSAL - DATA CLEANSING CONVERSION
Cost
Number per
# File Name of Hours Hour Total Cost Comment
Data Cleansing & Conversion Costs
1. Conversion Manager 0 $120 $0 Conversion Lead removed and
combined with Interface Lead.
Productive hours (1158) moved to
Items 2 and 3 below.
2. Legacy Jail Management System 3,363 $105 $353,115 Includes conversion of Audit
(Legacy JMS) History and archived booking
records. Original cost estimate
refined based on understanding of
discrete data elements reviewed
during the gap-analysis
3. Inmate Fund Canteen System 1,399 $105 $146,895 IFC.S data will be convertd in 2
(IFCS) phases (WIMP inPhase 1, all other
IFCS data in Phase 2)
4. Pre-Booking 0 $105 $0 No conversion required per MCSO.
5. Court Operations Systems 0 $105 $0 No conversion required per MCSO.
6. Operations Journal 0 $105 $0 No conversion required per MCSO.
7. SAP Business One Accounting 0 $105 Assume to be manual conversion
System
$0
.Datacteans1ng 8,000460 ptital_r $ 500,010
Page 20 of 29

Exhibit A 13139-RFP
Train'ng
Cost
Number of per Total
# Course/Module Description Hours Hour Cost Comment
Training Casts
1. System Onsite training planning 139 98.58 $13,702.62
2. System Training material development 662 79.83 $52,847.46
3. BI,Reporting, Patch Development Conduct Technical training 380 123.23 $46,827.40
4. System Conduct13 training 810 98.58 $79,849,80
5. System Support go-live training 528 98.58 $52,050.24
6. System Post-production training 506 98.58 $49,881.48
7. System Post-production Technical Training 106 123.23 $13,062.38
8. $0
9. $0
10, $0
$0
$o
$0
$0
$0
$0
Training Total - $ 308,221
Page 21 of 29

NEW 1MS ATTACHMENT A-8 13139-RFP
COST PROPOSAL - TRAVEL
Expense Purpose # Trips # Employees Cost per Employee Total Cost Comment
Travel Costs
Project Team Trips (excluding T3)
Transportation Cost - Flights 391 13 $ 17,294 $ 224,822
Lodging 391 13 $ 13,075 $ 169,975
Meals 391 13 $ 8,542 $ 111,046
Training T3 & Foilow Up Trips
Transportation Cost - Flights 10 3 $ 1,917 5 5,751
Lodging 10 4,233 12,699
Meals 10 3 $ 2,367 7,100
Syscon - Rental Car $800 per month for 42 months $ 33,600 ,,
Trips (Data Conversion and Interfaces)
Transportation Cost - Flights 182 4 $ 26,153 $ 104,652
Lodging 182 4 $ 19,835 $ 79,340
Meals 182 4 $ 12,922 $ 51,688
Tantus - Rental Car 182 4 $ 8,400 5 33,600
$ 834,273
0 Trips Ave Hourly Rate for Travel it Hrs One Way Trip
Total Travel Time (8 hrs round trip} 583 60 0 -
Travel Cost Plus Travel Billable Hours $ 834,273
sQ
Page 22 of 29

NEW JIVIS ATTACHMENT R-10 13139-RFP
COST PROPOSAL - OTHER IMPLEMENTATION COSTS
Cost
Number of per
Activity Description Hours Hour Total Cost Comment
Other Implementation Costs
Ongoing project management and
1. Project Management governance 5,670 $130.60 $740,502
2. Project Administration Project administration 5,292 $98.58 $521,685
3. Prepare Project preparation stage 2,415 $93.25 $225,199
4. Define Product definition 8,601 $95.03 $817,353
5. Configure Product configuration 16,119 $93.95 $1,514,380
6. Validate Product validation 5,320 $90.13 $479,465
7. Deploy Go-live event 1,392 $89.09 $124,020
8. Transition Post-go live and warranty 5,302 $9159 $485,610
Ofgahizatiapal-Gha.hge- Supporting IVICSO through business
9. Management e.hange 2,640 $98.58 $0 Moved to Options
Support and Maintenance for
10. second YCaF .$0 Moved to M&S tab
so
$o
$0
$o
Other Impenientation Cost Total $ 4,908,215
Page 23 of 29

NEW WS ATTACHMENT A-9 13139-RFP
COST PROPOSAL MAINTENANCE and SUPPORT TOTAL
Unit of Cost per
# Application / Module Description Measure Units Unit Total Cost Comment
During the GAP analysis several architectural changes were made to support reporting and other needs that were not identified during the RFP,
the changes required additiona third party licences
During the GAP analysis sessions, MCSO mentioned that they may be able to take advantage of their reputation and status as a public sector
entity to procure software at a better price than available to Syscon. Unless indicated in the comments, MCSO may safely procure any software in
this list. However, we recommend that you consult Syscon during the procurement process.
JMS Application Software Maintenance & Support Costs (All environments, please itemize)
T
Annual for production, dev / test
Core functional 1M5 and all / train environments combined
1. WorkflowJA1L application interfaces Application 1 550,000.00 $550,000 (includes product interfaces) 0.3
Annual for production, dev / test
Syscon assumes that MCSO
3.1rcdy has a enterprise licence
• ... for SQL Server so will not need to
Microsoft SQL ServeP teirlakepewel-RepeeFifig4akitioni). 2 Core Units . 4 40 incur this additional cost,
3. lied Hat Enterprise Linux Server Linuk Server 1 2 sockets 4 1,625.00 40 / train environments combined
Red Hat.1 BOSS Enterprise Annual for production, dev / test
4. Application Platform Application Server 4 Cores units 6 2,250.00 $13,500 / train environments combined
Red HatJBOSS Fuse Service Annual for production, dev / test
5. Works Interface Server, 4 Cores units 2 5,000.00 $10,000 / train environments combined
Annual for production, dev / test
6. Red Hat MOSS BPM Suite Business Rules 4 Cores units 2 8,333.33 $16,667 / train environments combined
7. iVeurotechnoiogy Megamatcher Biometrics Server Server 3 0.00 $0 No cost
8. Biometrics Fingerprint Client License Number of fir 45 0.00 $0 No cost
9. Cassandra NOSQL Database Audit Trail Database Open Source Open Source, no licence fee
Pentaho primary use is for data
conversion during go-live and may
not be required in subsequent
10. Pentaho Data Integration Data Upload 4 Core Units 1 0.00 $0 years.
Page 24 of 29

NEW .IMS ATTACHMENT A-9 131.39-RFP
COST PROPOSAL- MAINTENANCE and SUPPORT TOTAL
At the request of MCSO, raiLed
- - -
Nastel Autopilot Performance Monitoring Per Core replacing our Performance
Mefi-ito44g-Sektt -
product to meet MCSO 5pecific
.34 O security requirements.
## Hibernate Open Source Open Source 0 0.00 $0 Open Source no fee
tt# kiIcawar-e46014efe-Efiteriar-ise 1.44-44a1--Seiwew-a G.414- 44 $4
Selenium (browser automated
## testing tool) Open Source Open Source 0 0.00 $0 Open Source no fee
!Jr08.#00.44giditS0ttui00 ,S(thl-citOti $ 590,167
Administrative Software?e.g.. Project Management; Requirements Management; change Management; Release
Management)
1. SO
2. $0
3. $0
4. $0
5. $0
.AdinifilteatiVe:SaftWai*Stibotar $ -
Report-writing Software Maintenance & Support Costs
Annual for production, dev I test
. Oracle El Publisher Reporting & El Tools 1 Processor a 4 2,024 $8,096 / train environments combined
2. $0 .
3.„.,
So
5. $0
Repcirwriting5OftWare,Sub:Matall 8,096 ,
Testing Software Maintenance & Support Costs
1. $0
2. $0
3. $0
4. $0
5.
Testing $-oftwa?.e::Subl"ota:-: $
Operating System Software Maintenance & Support Costs
1. 50
2.
3. $0
4. $0
5. $0
,:OperaiinghSyteMSOftwai*SlibiTiataf ,L $ -
Other Software Maintenance & Support Costs (Technical integration tools, APIs, Third-party)
Page 25 of 29

NEW .IMS ATTACHMENT A-9
COST PROPOSAL - MAINTENANCE and SUPPORT TOTAL
2. $0
3. $0
4. $0
5. $0
6.
7.
8.
9. $0
10. $0
11. $0
12. $0
13. $0
14. $0
Other Software Sob-Total
Hardware Maintenance & Support Costs (All environments, please itemize)
1. SO
2. $0
SO
4. $0
S. $0
beSiif6kafe:$01:i 4Teitar: $
Other Miscellaneous Maintenance & Support Costs
1. $o
2. $0
3. $0
4. $o
S. $o
OtherMikellinods.M & S-Costs Sub-TE61-
TOX 17,701
Maintenarb Tat* 615,963
Page 26 of 29

New MS Attachment A-11
Cost Proposal - Miscellaneous Costs
Total
# Activity Description Cost Comment
Miscellaneous Costs (Examples)
1. Shipping $0
2. Insurance
Assumption that the bond
will be set at $2,000,000.
Estimated cost is $60,000 per
3. Performance/Payment Bonds $ 210,000 year for 3.5 years
MCSO will pay directly the
4. Source Code Escrow Set-up $.0 costs for setup ($1800)
MCSO will pay directly the
5. Source Code Escrow Annual Fees $0 costs for annual ($1200)
6. Gap Analysis $90,000
7. $0
. $0
9. $0
10. $0
Applicable Sales Tax $0
isc, Cost:Total. $ 300,000
Page 27 of 29

New iMS Attachment A-17
Cost Proposal - Optional Technology Offerings
Activity Number Cost Per Total Cost Comment
age] of Description of Units Unit
Other Implementation Costs
1. Scalability Monitoring Syscon provides monitoring of system, $0 Time 84 Materials
2, Installation Services Syscon installs all hardware, operating systems Time & Materials
Hardware Appliance $0 Time & Materials
Preinstalled copy of Syscon's software that can
. be added tc a rack and supported by Syscon.
Backup & Recover Services $0 Time & Materials
Syscon provides a system backup anti restores
4. the solution for a given backup if needed
Disaster Recovery Service In case of disaster, Syscon provides a fail over $0 Time & Materials
5. solution in the cloud or on remote data site.
Performance Tuning SyscoO monitors anti tunes the solution. Syscon $0 Time & Materials
monitors the performance of all tiers and tunes/
6. ecales them as needed.
Business Intelligence and $0 Time & Materials
7. Analytics Offering Business Intelligence (al) consulting services.
Interface DOC (AZ Dept. of Corrections) See Exhibit 7: .IMS- $12,600 In discussions with MCSO it was determined that this
15 interface was not high priority and has therefore been
8. provided as an option.
Analysis for Kiosk Analysis to provide kiosk furictiorlaiity as $17,604 Analysis of kiosk requirements in relation to the
described in the following document "MCSO requirements listed below in item number ID.
9. Kiosk ROM.doc"
Kiosk Functionality ROM $251,350 Incorporates F-TA-15, F-TA-19, F-FI-20. Only some of the
information listed in requirement F•GN ,32 has been
Identified in the "Kiosk - brainstorming ver2.docx°
document. As a result, this requirement is only partially
included in our Rough Order of Magnitude estimate.
To provide kiosk functionality as described in Further discussion and additional details is required.
10 the following document "IVICSO Kiosk ROM.doc"
Analysis for Data Warehouse $30,720 Assuming the scope of the data warehouse is limited to the
requirements within the RFP we would estimate that it
would cost approximately $30,720 to analyse all the data
warehouse requirements, the related reporting
requirements and prepare a detailed cost quote for the
implementation. Travel and living expenses would be extra,
11.
' Annual subscription
Syscon had the selection of a document management on its
road map with a scheduled completion for end of May
2015.
Generic Document
12. Management Users 1 57,030.00
Organizational Change
9. Management Sucpordn? MCSO through business change 2,640 $98.58 $260,251
'--1-- biliW 606.446.00 *lift**. 629,571
Please describe the type of "Optional" unit being proposed. Example Services may be per hour
while Hardware devices may be number of devices.
Appropriate sales tax as required
Page 28 of 29

NEW JMS ATTACHMENT A-13 13139-RFP
COST PROPOSAL - HOURLY LABOR
Cost
per
# Position/ Role Hour Comment
Hourly Labor Rates
1. Senior Project Manager: $178.00
2. Enterprise Architect: $170.00
3. Database Administrator: $130.00
4. Senior Development Manager: $178.00
5. Project Administrator: $135.00
6. Senior Business Analyst: $178.00
7. Testing Manager: $148.00
. Configuration & Release Manager; $148.00
9. Interface Manager: $150.00
10. Data Conversion Manager: $150.00
14, Training Manager: $411-840
12. Business Analyst $148.00
13. Training / Change Management Lead $148.00
14. Syscon Executive Sponsor $0,00 This role is Steve Long
15, Data Migration/interface Analyst $135.00
Data Migration/Interface
16. developer $135.00
Or-gafkieat-io4a4-C-14.ange-
4-7, Management-Lead
18. Senior Subject Matter Advisor $178.00
19. Syscon Project Director $0.00 This role is Ken Piaggio
20. Technical Analyst $128.00
21. Test Lead $130.00
22. Test Analyst $98.00
23. Training Specialist - $148.00
24. T&M for Client Support $150.00
Page 29 of 29

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

SERIAL 13139-REP
PART ONE STATEMENT OF REQUIREMENTS
1.0 INTENT
The purpose of this Agreement is to contract with a partner who will partner with the Maricopa County
Sheriff's Office (MCSO) to successfully implement a commercial off-the-shelf (COTS) New Jail
Management System solution (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 New JMS Project includes all software, and related services such as system configuration, interfaces,
data migration, training, and other development or implementation tasks. In addition to the project
implementation components listed, Contractor 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. It is an expectation that Contractor shall play a
key role in the change management process portion of the implementation of the New JMS solution.
The JMS solution will replace and enhance 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 (0J), Court Operations, and SAP Business One Accounting Systems. A
fully-integrated solution requiring minimal customization is highly desirable.
Key outcomes expected from the New Jail Management System Project are to:
a) Replace functionality of existing "legacy" detention systems;
h) Provide new and enhanced business functionality as specified, and/or as included in the
Contractor's standard product;
c) Successfully interface with other systems; and
d) Provide software operating environments that are supportable and maintainable.
1.1 NEW JMS GOALS AND OBJECTIVES
Acquisition and implementation of a New JMS 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 systems and related detention interfaces with a state-of-the-art
commercial off-the-shelf (COTS) solution that meets or exceeds needs of the Sheriffs
Office;
(2) Deliver a fully-integrated New JMS solution on time and within budget;
(3) Achieve sufficient knowledge transfer through training and documentation to allow in-
house technical staff to easily support the new system and technologies going forward;
(4) Provide a technologically sound platform for expansion of information services into the
future; and
(5) 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

SERIAL I3139-RFP
• Maximize resource management
• Implement a solution that meets Generally Accepted Accounting Principles 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 New .1MS 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. 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 MC SO 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.
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 MCSO will provide knowledgeable resources regarding data in source applications to be
converted to the New IMS. Knowledge includes data definitions and validation/edit rules
regarding data values that are populated in the legacy application systems.
2.11 MCSO is responsible for providing extracts of source data in file formats agreed to by the Parties
that are required for data conversion and migration.
2.12 MCSO is responsible for all source data cleansing that is required to support the data migration
process, that cannot be addressed automatically though the Transform step of the data migration
process.
2.13 MCSO will provide knowledgeable resources regarding data in external agency applications that
will be interfaced to the New JMS. Knowledge includes data definitions and validation/edit rules
regarding data values that are used in current interfaces. For new interfaces, knowledge includes
definitions and validation/edit rules regarding data values that are populated in the external
application systems.
2.14 MCSO and external agency staff will perform all development and validation required to be
performed on MCSO internal or external agency applications that will be interfaced to the New
SMS. The Contractor will perform all development and validation required to be performed on the
New JMS applications to support the in scope interfaces.
2.15 Interface design work will he a collaborative effort between the Contractor, MCSO and external
agency resources.
2.16 The Contractor, with the help of MCSO, will establish and configure test environments for all
MCSO internal and external agency interfaces in order to support validation of these interfaces.
2.17 The Contractor's work hours must be consistent with MCSO key staff. Sheriff's Office usual
business hours are 8:00AM 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.
2.18 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

SERIAL 13139-RFP
the Change Control Process detailed in Exhibit B, Part 2, Section 9, prior to starting. As required,
formal written amendments to the Contract will be executed for changes to project scope or cost.
2.19 The Contractor and the Sheriff's 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 and
the Contractor's Project Manager, respectively, within two (2) business days of becoming aware
of the problem or issue.
2,20 The Contractor shall begin work as soon as reasonably practicable following the issuance of a
Purchase Order and in accordance with the project schedule.
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. Any unresolved item or deficiency will be documented and escalated as a project issue.
Assumption
3.1 MCSO is responsible for sourcing, installing and configuring hardware.
3.2 MCSO is responsible for installation of all Operating System Software and any 3rd party
software applications required to support the Workflow application. Syscon will provide
configuration documentation as required.
3.3 MCSO is responsible for hardware support.
3.4 MCSO is responsible for network configuration and support_
3.5 Microsoft SQL server will be the database platform for the main Workflow transactional
database,
3.6 The customization cost quoted for requirement F-GN-2 covers the effort to enhance
Workflowjail to write audit trail information to a different database than the main database
for WorkflowJail transactional data. This customization cost will be the same regardless of
whether the Audit database is a MS SQL database or a No SQL database. No SQL is
recommended by Syscon as SQL server does not have the same capabilities for handling big
data as NoSQL. It is confirmed that MCSO will use NoSQL.
3.7 MCSO is responsible for sourcing, installing and configuring third party tools for security
breach detection.
3.8 Syscon will setup the WorkflowJail performance monitoring tools and train MCSO technical
staff on how to use these tools. Syscon will monitor performance during performance testing
and the acceptance test period. Syscon will assist MCSO with identifying key performance
metrics that should be monitored. During the Warranty Period MCSO will be responsible for
monitoring the production environment and Syscon is responsible, with the assistance of
MCSO, for resolving any application performance issues.
3.9 MCSO is responsible for sourcing, installing and configuring third party assistive
technologies required for 508 compliance.
3.10 MCSO is responsible for the overall archiving solution should archiving be required. Syscort
currently believes that there is no need for an archiving solution.
3.11 MCSO is responsible for sourcing, installing and configuring both the backup and recovery
solution; and the disaster recovery solution.
3.12 The WorkflowJail product is HTML5 compliant and can be viewed on a mobile device. The
following modules have been identified as prime candidates for use on, and optimized for use
on, mobile devices: shift logs, incidents, facility counts, inmate calendar, reports, and last
known location. MCSO has indicated that this functionality would not be used until after
Phase 2. As a result, no testing effort for mobile functionality beyond standard product testing
has been included in the implementation costs on Attachment A.
3.13 Syscon will develop up to ten (10) custom Workflow BI reports or dashboards, as identified
by MCSO, as part of the system configuration effort, and use these as examples to train
MCSO on report and dashboard development using Workflow's integrated Oracle BI
solution. All other custom reports will be the responsibility of MCSO.

SERIAL 13139-RFP
Assumption
3.14 The Reporting Environment described in Exhibit B, Part Two, Section 10.7.3 will allow
MCSO to create the Schroeder reports with some manual intervention using data captured in
nightly snapshots. A fully automated solution would likely require a data warehouse solution
with a multi-dimensional database and a thorough analysis of the Schroeder reports and all
the source data used to produce them. A fully automated solution has not been included in
the cost proposal.
3.15 Any changes in duration or phasing not caused by Syscon, which result in additional costs for
Syscon, may result in changes to the implementation costs quoted in Attachment A.
3.16 Phases 2a and 2b will run concurrently and may share Syscon resources.
3.17 Phase 2b will go live one (1) month after the completion of Phase 2a go live.
3.18 Training material that will be tailored/customized for MCSO is the Train the Trainer (T3)
Classroom training material.
3.19 Syscon's Product Computer Based Training (CBT) training material will be updated as
product roadmap functionality is delivered but it will not receive any customization as part of
the project.
3.20 A total of forty (40) T3 training days are included in the price — thirty (30) for Phase 1, five
(5) for Phase 2a, and five (5) for Phase 2b. This is intended to support three (3) full sets of
13 training for Phase 1 and 1 full set of T3 training for each of phases 2a and 2b.
3.21 Each 13 training session will be led by two (2) Syscon trainers, and will include a training
support person from the MCSO project team to help manage scope and facilitate change
management discussions, such as any context specific discussion around MCSO specific
process. For example, if a process change is occurring as a result of the ,INIS implementation,
MCSO will manage the communication of that said process to the MCSO staff and Syscori
will be responsible to train on how the application is used to perform the task.
322 Each T3 training session will be attended by no more than twenty-four (24) MCSO staff
members. This limit is recommended in order to manage the ratio of instructor to students.
Our research suggests a class size of fifteen (15) is optimal for adult learning, however, in the
MCSO case we believe that the volume of students would need to be higher in order to cover
the material and staff in the time available.
3.23 Technical Training includes one workshop per technical training topic: Installation/Patch
Deployment, Reporting, Business Rules, Interface Enterprise Service Bus, Business Process
Orchestration.
3.24 Functional System Administration training includes one (1) workshop per Workflow module.
Multiple workshops can be included in a single day session.
3.25 Follow-Up Training Workshops includes one (1) workshop for each Workflow module.
Multiple workshops can be included in a single day session. Additional workshops will be
added only if required to meet user competency requirements.
3.26 Each go live will be followed by a forty-five (45) calendar day warranty with the option of a
mutually agreed additional forty-five (45) calendar days.
3.27 'As Is' business processes are accurate and complete as of the date created. If 'As Is'
business processes change from the time they are created, this may result in a change request
if this impacts the Syscon project effort. Syscon will verify with MCSO that the 'As Is'
process for the process being developed or configured is accurate prior to beginning the
work. MCSO commits to ensuring that `As Is' processes are accurate by the time the
development/configuration effort is to commence.
3.28 MCSO is responsible for updating 'To Be' business process documents with support from
Syscon.
3.29 MCSO will provide detailed documentation (to the extent that it is available or in existence)
regarding data in the source applications to be converted to the new .IMS. Documentation
should include data definitions, data dictionaries and validation/edit rules regarding data
values that are populated in these systems. In the absence of documentation, MCSO will
make SMEs available to provide the required information.
3.30 MCSO will be responsible for providing extracts of all source data to be converted to the new
IMS, in a file format mutually agreed to by MCSO and Syscon.

SERIAL 13139-REP
Assumption
3.31 MCSO will be responsible for all source data cleansing that is required to support the data
migration process, based on data that does not meet the rules established for loading into the
new JMS and that cannot be addressed automatically though the Transform step of the data
migration process.
332 Data migration will occur over the two implementation phases that
have been defined:
Implementation In -same Legacy System Data Conversion
p ilW .
Jail Management System (JMS)
inmate Fund Canteen System (IFCS) —WIMP data
Inmate Fund Canteen System (IFCS)
SAP Business One Accounting (Manual)
3.33 The Implementation Phasing being proposed will see Working Inmate Management Program
(WIMP) functionally deployed as part of Phase 1, resulting in legacy WIMP data converted
then, while all other data residing in the Inmate Fund Canteen System (IFCS) will be
converted in Phase 2. This approach is based on the assumption that WIMP functionality can
be effectively removed out of IFCS without impacting the ongoing use of the remaining
functionality in IFCS. Should this assumption prove to be incorrect, and WIMP remains
within IFCS until Phase 2, then all IFCS data would be converted as part of Phase 2
implementation.
3.34 Any requirement to convert data from SAP will be handled manually by MCSO.
3.35 If the customization for F-GN-2 is approved by MCSO then the audit history from in-scope
legacy systems (JMS and IFCS) will be migrated to a separate read-only audit trail database.
In other words, audit history will not be converted into the main WorkflowJail transactional
database environment.
336 In addition to data conversion related to the legacy systems discussed above, loading mugshot
data into the New JMS was discussed during the Interface gap analysis meetings. While this
is conceptually a data conversion activity, it is assumed that the MugShot — WorkflowJAIL
interface will be leveraged to perform a bulk load at the time of deployment. This approach
will be confirmed during the Define stage of the project. Should an alternate approach be
agreed to it will he handled through the formal change control process.
3.37 Should any additional requirements to migrate data from source systems not identified as in-
scope, or additional data elements be identified, these will be treated as new scope items and
will be handled through the formal change control process,
3.38 MCSO will provide detailed documentation (to the extent that it is available or in existence)
regarding data in the MCSO internal or external agency applications that will be interfaced to
the new IMS. Documentation should include data definitions, data dictionaries and
validation/edit rules regarding data values that are populated in these systems. In the absence
of documentation, MCSO will make SMEs available to provide the required information.
3.39 Syscon will be responsible for implementing only the WorkflowJAIL portion of the
interfaces. Any interface components deployed (or application changes required) on the
Integration Engine or other systems will be the responsibility of the owners of those systems.
3.40 MCSO will provide test environments for all MCSO internal or external agency systems that
will be interfaced to the New JMS in order to support the validation of these interfaces.
3.41 Non-functional requirement NF-DR-10.1.3 (The solution shall facilitate data exchange of
MCSO Internal data and Core Shared data) will be facilitated by the interfaces that are
identified as in-scope. Should any additional requirements to facilitate data exchange of
MCSO internal data and Core Shared data be identified these will be treated as new scope
items and will be handled through the formal change control process or work will be
performed by MCSO technical resources.

SERIAL 13139-REP
Assumption
3.42 In-scope interfaces will be implemented over the two implementation phases that have been
defined. The phased approach requires that certain "bridging" interfaces be deployed in order
to ensure that each defined implementation phase will be fully able to support MCSO's
requirements. Bridging interfaces will be implemented for one phase, and then
decommissioned in a later phase as additional Workflow.TAIL functionality is deployed, and
legacy systems are decommissioned. The scope of bridging interfaces is based on the current
implementation phasing. Changes to project phasing may impact the scope of bridging
interfaces. Should the complexity or number of bridging interfaces increase or decrease this
will be handled through the formal change control process.
3.43 The level of effort to perform the Design, Configuration, Validation and Deployment of the
in-scope interfaces was based on the Interface complexity as defined by MCSO in Appendix
2. Should the complexity or number of the interfaces increase or decrease during the project
the level of effort may be impacted and this will be handled through the formal change
control process or work will be performed by MCSO technical resources.
3.44 MCSO will be responsible for any source data cleansing/modification that may be required to
support the exchange of data between the new .TMS and MCSO internal or external agency
applications where the particular data condition cannot be addressed automatically through
the ESB framework.
3.45 The Implementation Phasing being proposed will see Working Inmate Management Program
(WIMP) functionally deployed as part of Phase 1, resulting in legacy WIMP functionality
(modules within the legacy Inmate Fund Canteen System — IFCS) being decommissioned
while the remaining IFCS functionality will continue to be used until Phase 2. This approach
negates the need for bridging interfaces to be developed between WorkflowJAIL and WIMP.
This approach is based on the assumption that WIMP functionality can be effectively
removed out of IFCS without impacting the ongoing use of the remaining functionality in
IFCS. Should this assumption prove to be incorrect, and WIMP remains within 1FCS until
Phase 2, then bridging interfaces may be required.
3.46 A number of the Report File Data Exchanges noted in Appendix 2 will be able to be satisfied
through the New ,IMS reporting functionality, and will not need to be routed through the
Integration Engine as is currently noted. This is based on the assumption that these reports are
not directly consumed by a receiving system. This assumption applies to Interface ID RPT-01
through RPT-3() inclusive.
3.47 As WorkflowJail product follows an Agile methodology, requirements may be delivered in a
phased manner in different drops, while still keeping to the overall proposed phase timelines.
Syscon will work collaboratively with MCSO to plan a schedule of mutually agreed drop
dates.
3.48 For all modules and features yet to be built as part of the Workflow product, Syscon will
engage MCSO for input; however, the final approach on how this is implemented in the
Workflow product design rests with Syscon, so long as all Custom Modifications shall meet
the requirements of MCSO.

SERIAL 13139-RFP
•ASSUrr)ption
3.49 The Configuration effort estim ates are based on the following table. The table outlines the
estimated number of rules and business process / task orchestrations to be configured during
the implementation. These estimates are based on the information known at the completion
of the gap analysis.
10
chedules/Moves/
ocations/Housing/ Counts
16
Classification/Case
Management 5 12
Programs 5
Release/Victims 16
SIMS 40
Requests and
Grievances 2 12
pecurity Threat Groups 12
Operations Journal
Expanded Event Log) 5
Discipline 5
Vis its 10
correspondence
Health Information 2
[Total Phase 1 198 60
Phase 2 Trust Accounting 50
Commissary 50 16
[Transportation 10
Pre book 25 16
Facility Issue 5
Total Phase 2 140 120
TOTAL 1238 170
150 Product documentation including but not limited to installation guides, user guides, and
online help will not be customized for MCSO. Training materials will be customized for
MCSO's configuration of the Application Package.
3.51 MCSO will make available production like data in order to support Syscon's development
and testing activities and also MCSO's testing activities (such as UAT and performance
testing).
3.52 All items identified in Exhibit A, Options Tab will be subject to further analysis and a
detailed re-estimation. A detailed explanation of changes will be provided by Syscon to
MCSO. if MCSO chooses not to proceed, the cost will be removed.
3.53 MCSO is responsible for leading all activities related to Organizational Change Management
with assistance and support from Syscon as required.
3.54 With regards to the requirement F-RP-17: "The solution shall provide ad-hoc reporting
capability to provide management statistics including the following but not limited to:
inmate, race, gender, gang status, medical status, cell, facility, movements, all classification
criteria, min/max sentencing predictions, forecasting, total inmate population by cell, area,
facility, etc." Syseon's assumption is that data summarization for statistical analysis will be
the responsibility of MCSO. Syscon's proposed Workflowkil reporting environment will
allow MCSO to perform data summarization using stored procedures and other standard SQL
techniques; however, if there needs to be point-in-time statistical analysis of data which are
not already captured in the nightly snapshots additional snapshots may be required. MCSO
can request additional snapshots from Syscon via the change control process. Alternatively,
MCSO can develop these on their own.

SERIAL I3139-RFP
4.0 REQUIREMENTS
New JMS Solution functional and non-functional requirements are identified below. Any changes to these
requirements shall he documented via the project's formal Change Control Process.
4.1 Functional Requirements
MCSO's Functional Requirements for the New JMS Solution are identified in Exhibit B, Sub a.
These requirements are the result of MCSO's original requirements from the New JMS Solution
Request for Proposal and subsequently updated by mutual agreement between MCSO and
Contractor during the Gap Analysis activities.
These functional requirements serve as the foundation upon which the software will be configured
to MCSO specifications and also used to test the MCSO solution prior to acceptance and
implementation.
4.2 Non-Functional/Technical Requirements
MCSO's Non-functional/Technical Requirements for the New JMS Solution are identified in
Exhibit B, Sub b. These requirements are the result of MCSO's original requirements from the
New JMS Solution Request for Proposal and subsequently updated by mutual agreement between
MCSO 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.
5.0 STAFFING
Contractor shall retain qualified personnel and resources to accomplish SOW requirements. As such, the
Contractor shall continuously maintain an adequate qualified staff with suitable management, professional,
trade, or administrative expertise to assure that work is scheduled, performed, and completed in accordance
with this SOW.
5.1 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.
5.2 The Contractor shall take any and all action necessary to ensure the conduct of its employees is
professional and complies with Contractor and MCSO rules and policies.
5.3 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.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:
6.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. MCSO will review and approve the Quality
Management Plan deliverable signifying agreement to the measures that will be used to determine
customer satisfaction that each deliverable is complete and acceptable and that project work
processes are being followed.

SERIAL 13139-RFP
6.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 stmdards/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 MCSO.
6.3 Quality Control — The purpose of quality control is to verify that project deliverables are of
acceptable quality and that MCSO 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 customer satisfaction, Quality Control activity, frequency or
timing, and who is responsible. Responsibilities for Quality Control will reside both with the
Contractor and MC SO. MCSO reserves the right to approve each deliverable signifying
acceptance/satisfaction.
6.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 MCSO
and comply with requirements and specifications mandated. The Contractor will provide all
deliverables and documentation to MCSO'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 MCSO review
and approval. In addition, MCSO's V&V representative will monitor all aspects of the project to
ensure Contractor obligations are being met.
7.0 MCSO 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
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 MCSO through the life of the Contract.
1;.stimated Estimated
Uinta-hi n lity/ I tu 11511 Concurrent Co iii inejits.
# Users Users
Pre-Booking MCSO Intake 150
Pre-Hooking MCSO Deputies 700
Pre Booking Outside Police Agencies
Intake Processing — 4th Ave & LBJ Intake
Incl. Page 2's & holds
Release Processing — 4th Ave & JBi — Court
Incl. Page 2's & holds Desk & Release Areas
Fingerprint Processing Records & ,A.FIS Division 15
Average Assumes —100
Inmate Kiosks Inmates in Jail Facilities 8,000/Day kiosks available
in. MCSOlads . .
Detention Operations
(e.g., logbook entries, Jail Facilities 1,000
housing queries,
visitation, etc.)
Inmate Property
Tracking Jail Facilities

SERIAL 13139-RFP
Mobile Devices (e.g., Jail Facilities 1,000 150 Now performed
headcount scanning) (TBD) manually
Mobile Devices (e.g. • for urt Security & Transp. Now performed
inmate movements) manually
Depends on the
Mobile / Barcode / Other Other Business Areas purpose; will be
Devices new technology
for Detention
inmate Funds Queries Hearings & Grievances
Inmate Funds Queries Jail Facilities Will decrease as
&/or Processing kiosks installed
Inmate Funds Queries innate Legal Services
&/or Processing
Inmate Funds Queries SIMS
&/or 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.MOverneh Medical Services 25 .:
Inmate Movement Classification 53
Inmate Inmate Movement Movement Jail Jail Facilities Facilities 830 830 30
Scheduling Scheduling Court Court Security Security & & Trait Trait sp. sp. 150 150 50
Scheduling Scheduling Medical Medical Services Services 25 25
Scheduling Scheduling Correctional Correctional Health Health 700 700 100
Scheduling SIMS 35
Scheduling Jail Facilities 1,200 200 Primarily view-
only with queries
Scheduling .......
Scheduling Inmate Programs 75 10
Scheduling Hearings & Grievances 20
Court Case Processing Inmate Legal Services Primarily view-
only with queries
Court Case Processing SIMS 70 25
Sentence Calculation SIMS 70 15
Sentence Calculation LB 75 25
. .ClaSalifieation:VibeeSsing:Jail Intel - Gang Mgm 10 Primarily view
only with queries
Classification Processing Inmate Classification 20 6
Proxy Scoring Inmate Classification 20
Proxy Scoring Inmate Programs 30
Administration of Inmate Programs 30 Day shill only
Inmate Programs
Ancillary Services Laundry 3 Primarily view-
only with queries
Ancillary Services Food Factory/Diets Primarily view-
only with queries
System Administration Technology Bureau 10

SERIAL 13139-RFP
Report Processing 1,500
Document Management All Detention Users 1,500
Business Rules All Detention Users 1,500
Workflows All De ention Users 1,500
8.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 MCSO locations. MCSO and Contractor agrees to utilize technology, such as
GoToMeeting and WebEx, along with conference calls to help control on-site vendor costs related to this
project effort. Vendor staff must be on site for certain events such as, but not limited to: Project Kickoff
meeting; initial system installation and configuration; requirements gathering; business process review;
development of ten (10) major reports; agreed to subset of all interface and conversion development and
testing; all forms of technical system training; T3 training; supporting actual UAT tasks; and, the three (3)
scheduled Go Live events and follow-up support.
Additionally, the Contractor Project Manager will make monthly trips to MCSO 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 performed at the Contractor's office include: all administrative tasks; formal design
development; software development; unit testing; automated testing, via test tools; defect management;
daily PM activities.
Access to MCSO 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
passed the Terminal Operators Certification (TOC) test). MCSO will provide a secure remote access
capability to Contractor. Contractor will always seek approval from MCSO prior to accessing network.
During the course of the project, MCSO 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.
9.0 COUNTY FURNISHED PROPERTY, MATERIAL, EQUIPMENT, OR INFORMATION
MCSO workspace environment shall include desktop workspace, access to the MCSO 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 MCSO or the County. For convenience,
and at its sole discretion, the Sheriff's 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 MCSO'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 Sheriff's 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.

SERIAL 13139-RFP
10.0 EQUIPMENT
In the event that the County options to procure hardware from Contractor in support of this Contract,
Contractor shall ensure that all equipment is supplied in brand new, unused condition. All equipment shall
be supplied from the manufacturer or an authorized EMC resell er with full USA manufacturer warranty and
USA manufacturer technical support.
MCSO Recommended Specifications
The Workflow application will be sealed to meet MCSO forecasted number of users and concurrent users.
Various key resources are considered for the suggested Workflow deployment platform. The following
hardware specifications, based on a conservative extrapolation methodology, allow Contractor to create
some initial hardware specifications that can be refined using capacity tests or conservative extrapolation
methodology considering level of concun -ency, throughput, and behavior of the real business users:
Server Type Number Hardware Configuration
of
Servers
Application 2 Dell R810 or equivalent
2x Intel® Xeon® E5-4603 v2 2.200Hz, 10M
• Cache, 4 Cores(or better)
24 GB RAM
RAID 10, 1TB 7.2K RPM Near-Line SAS 60bps
3.5in
4x1 GB network interfaces
Services I Dell R810 or equivalent
2x Intel® Xeon® E5-4603 v2 2.20GHz, 10M
Cache, 4 Cores(or better)
32 GB RAM
RAID 10, 1TB 7.2K RPM Near-Line SAS 6Gbps
3.5in
4x1 GB network interfaces
SAS 10 CARDs
Business Rules I Dell R810 or equivalent
and 2x Intel® Xeon® E5-4603 v2 2.200Hz, 10M
Enterprise Cache, 4 Cores(or better)
Service Bus 16 GB RAM
RAID 10, ITB 7.2K RPM Near-Line SAS 6Gbps
3.5in
4x1 GB network interfaces
Configuration I Dell R810 or equivalent
Management, 2x Intel® Xeon® E5-4603 v2 2,200Hz, I OM
Biometrics, etc Cache, 4 Cores(or better)
16013 RAM
RAID Ifl, ITB 7.2K RPM Near-Line SAS 6Gbps
3,5in
Reporting and 1 Dell R810 or equivalent
Document 2x Intel® Xeon® E5-4603 v2 2,206Hz, 10M
Management Cache, 4 Cores(or better)
32 GB RAM
RAID 10, 1113 7.2K RPM Near-Line SAS 6Gbps
3.5in
OLTP and 2 DELL R810 or equivalent

SERIAL 13139-RFP
Server Type Number Hardware Configuration
of
Servers
DW/Reporting 2x Intel® Xeone E5-4603 v2 2.20GHz, 10M
Database Cache, 4 Cores(or better)
servers 32 GB RAM
RAID 10, I TB 7.2K RPM Near-Line SAS 6Gbps
3.5 in
4x1 GB network interfaces
SAS JO CARD
Main I DAS DELL MD 1420 or equivalent
Redundant 15 TB RAID 10
Direct
Attached
storage
The hardware configuration of the disaster recovery (DR) environment can be estimated as a percentage of
the above based on MCSO's requirements for DR.

SERIAL 13139-RFP
PART TWO: STATEMENT OF WORK
I. 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 program 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 IvICSO deliverables and services that are dependencies thereof;
B. Proactively identifying, assessing and mitigating risks (both operational and reputational) to MCSO
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 MCSO stakeholders and Contractor at the right
point in time lathe 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.
1.2. Governance Team Structure
The following governance structure is recommended for the MCSO New JMS program —Project Steering
Committee, and Project Delivery, with linkages to existing MCSO or County committees as required:

SERIAL 13139-RFP
'Project Steering Com It -tee
INACSO Syst:on
Executive M('so Proiect F.x.rciativt?. SYsrort P role(' t
SPorkscot Director Sporisot Dirt:t..tor
roject Delivery Team
Figure 1: Governance Structure
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:
Role Responsibility
Syscon The Syscon's Executive Sponsor provides support for the Project Director and Project Manager and has final
Executive approval of all scope changes, and signs off on approvals to proceed to each succeeding project phase. The
Sponsor Executive Sponsor may elect to delegate some of the above responsibilities to the Project Director and is
accountable to the Board of Directors.
Key stakeholder of the Flagship Program
Provides leadership on culture and values
Keeps project aligned with organization's strategy and portfolio direction
Works with other sponsors
Ensures a single point of accountability
Syscon The Project Director is responsible for the relationship between Syscon and lvICSO. This Position has the
Project power to mobilize the resources of the Contractor organization to deliver on all service levels and
Director contractual commitments Duties and responsibilities including:
o Overall ownership of the contract;
o Stewardship of the relationship;
o Strategy planning/direction setting;
o Overall financial management and approval;
o Effective communication of strategy and benefits to business process areas;
o Identifies and escalates potentially significant, sensitive or political issues to Executive
Committee;
o Reviews project status updates;
o Provides monthly project updates to Executive Committee
MCSO The Executive Sponsor provides support for the Project Director and Project Manager and has final approval of
Executive all scope changes (subject to the approval of the Chief Procurement Officer or the County Board of
Sponsor(s) Supervisors), and signs off on approvals to proceed to each succeeding project phase. The Executive
Sponsor may elect to delegate some of the above responsibilities to the Project Director.
Provides leadership on culture and values
Keeps project aligned with organization's strategy and portfolio direction
Works with other sponsors

SERIAL 13139-RFP
Ensures a single point of accountability
Actively supports organizational change and fulfills role as Change Sponsor throughout MCSO
MCSO The Project Director is responsible for the relationship between MCSO and Syscon. Duties and responsibilities
Project include:
Director o Overall ownership of the contract;
o Stewardship of the relationship;
o Strategy planning/direction setting;
o Overall financial management and approval;
o Effective communication of strategy and benefits to business process areas;
o Ensuring that the solution and services delivered under this contract are consistent with
MCSO's program objectives;
o Identifies and escalates potentially significant, sensitive or political issues to Executive
Committee;
o Reviews project status updates;
o Provides monthly project updates to Executive Committee
Project Interprets the strategic direction provided by the Executive Sponsors;
Steering Provides authority on resolution of major project issues / escalated decisions;
Committee Develops a coherent and supportive relationship between the overall business strategy and the program
portfolio;
Approves changes to project scope, schedule and budget / endorsing new projects and associated plans,
schedules and resourcing requirements;
Reviews project performance through the Performance Quality Scorecard monthly;
Governs project management and the implementation of the MCSO New MS;
Decides when independent 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 program
Project Manages the MCSO New JMS program in accordance with the strategy and plans;
Delivery Drives majority of decisions with respect to operations and delivery of the project as specified in the Statement
Team of Work;
Owns the execution of the project activities and management of the associated deliverables;
Provides timely project status reports and dashboards to the Project Directors and the Project Steering
Committee;
Manages organizational change management;
Owns the communications and dissemination strategies;
Develops the overall program plan and roadmap for the MCSO New JMS
Table Project Governance Roles and Responsibilities
1.4. Flagship Client Program
As an exclusive member of the Flagship Client Program, MCSO will enjoy an elevated status and priority as a key
partner in the development and evolution of WorkflowJAIL. The program is intended to provide MCSO with
priority-access to the entire Contractor organization. As a Flagship client, MCSO will have an increased level of
control to manage risk through early identification of issues before they become problems. Syscon will work closely
with MCSO to gain advice and direction on Workflow product roadmap.
Flagship Customer Program Components:
• Key partner in customer product advisory group
• Quarterly or bi-annually product review cycles to include product functionality
requirements, wiretimnes and product demonstrations of new functionality
• Priority provided input to product directions such as features and enhancements
• Active participation in project governance by Syscon Executive Sponsor (CEO) during
implementation; meets hi-annually with client post go-live
• Day-to-day oversight by Syscon's VP of Professional Services (Project Director);
performs operations reviews and will be a member of the Project Steering Committee

SERIAL 13139-RFP
• Scheduled Executive team meetings: Syscon/MCSO integrated into the Governance
process as outlined in section 1.2 to review project progress, product issues, escalations,
etc.
• Documented escalation processes-Executive, Professional Services, Support, R&D,
Support, Account Team
• Priority support for support team
• First right of refusal to be a beta site for new functionality
• Reference site/sponsored conference speaker (with Maricopa's approval)
• Case study-positive public relations to demonstrate innovative approach to JMS
2. Key Personnel
2.1. Syscon Key Personnel Roles and Responsibilities
The table below outlines the key project personnel and their role on the project:
Name Role
Christopher Lai Senior Project Manager
TB!) Project Administrator
Lode Allen Lead Functional Analyst
Gavin Rooke Development Manager
TB!) Technical Analyst
Tatiana Nlotuzka Testing Manager
Susan Dean Subject Matter Expett
Karl Stelting Subject Matter Expett
Lyne Eaker Conversion & Interfac,e Lead
Tyler Irwin Training Lead
Tyler Irwin Organizational Change Management Lead
Sandeep Kumar Configuration and Release Manager
Igor Stelmashenko Enterprise Architect
Jason Xis Database Administrator
Table 2: Syscon Key Personnel
The following table provides a description of the responsibilities of both the key Syscon project personnel and other
anticipated project personnel:
Role Responsibilities
Business Analyst Performs onsite configuration planning activities.
Performs business analysis activities on the project.

SERIAL 13139-RFP
Performs system configuration activities.
Supports training content development and training delivery activities.
Supports development and test activity.
Provides support to the MCSO and Syscon project teams during acceptance testing.
Provides go-live support.
Facilitates post-go-live mentoring sessions.
Configuration and Release Builds Syseon project infrastructure and environments (Development, Test, Interface, Migration,
Manager Delivery, Cloud).
Responsible for Management and Control of all software components specific to the project.
Prepares and validates all installation processes and procedures.
Participates in and supports the onsite installation of the configured system.
Prepares all software release packages and patches.
Maintains all environments throughout the life cycle of the project.
Participates in knowledge transfer to MCSO.
Participates in transitioning activities to Support.
Conversion and Interface Lead Ensures requirements for Interface and Data Conversion (TIC) are met
Manages the budget and control for the TIC activities
Manages the travel approvals for TIC activities
Protects the ITC project scope, timeline, and budget
Manages I/C issues through to resolution
Provides status reports to the Project Administrator who will consolidate and distribute to stakeholders
Data Migration/Interface Analyst Analyzes data migration and interface requirements.
Prepares data mapping and ETL design specifications.
Prepares interface design specifications.
Participates in design reviews with other team members.
Participates in knowledge transfer to IvICSO
Data Migration/Interface Develops and unit tests integration and data migration components (ETL) according to design.
Developer Participates in code reviews with other team members.
Supports end-to-end integration testing, mock conversion testing and user acceptance testing.
Troubleshoots and resolves testing issues as required.
Supports production cutover activities.
Participates in transitioning activities to Support.
Database Administrator Responsible for all Syscon database administration duties and tasking throughout the project,
Supports the set-up and installation of database systems.
Supports the onsite installation of the configured system.
Performs performance tuning and monitoring activities.
Assists in troubleshooting database-related issues as required.
Participates in transitioning activities to Support.
Participates in knowledge transfer to MCSO
Enterprise Architect Responsible for the product architecture.
Works with the project management team to communicate changes to the enterprise architecture.
Works with the technical teams over the life of the pinject.
Supports product architecture-related communications to IVICSO technical team.
Primary point of contact for all product architecture requests.
Regularly consults with project technical analysts on all integration, testing and configuration
management needs.
Supports knowledge transfer activity as required
Organizational Change Supports the MCSO Change Manager for organization change management activities.
Management Lead Supports MCSO in business process change impact analysis and assessment including analysis of `as-is'
processes and 'to be' processes.
Works closely with the training manager to ensure training is conducted to reflect the changes to
processes and procedures.
Project Administrator Tracks and reports progress against plan.
Establishes and maintains document library.
Produces and distributes status reports to stakeholders
Provides administrative support to Sr. PM activities
Prepares and manages invoices for monthly and milestone billings
Manages and tracks travel requests and approvals, as well as expense submissions to MCSO
Maintains and updates actuals against estimates in plan(s) and budget.
Prepares quarterly travel projections

SERIAL I3139-RFP
Senior Project Manager Primary contact throughout the project.
Manages and leads the Project Teams.
Resolves cross-functional issues at the project level.
Responsible for the delivery of the Project Management Plan and associated plans.
Works with the MCSO Project Manager to coordinate and execute the implementation schedule and
associated plans.
Protects project scope, timeline, and budget.
Manages issues through to resolution.
Provides status reports and presents them to various committees and teams on agreed schedule as per the
Communication Plan
Holds regular conference calls with MCSO Project Manager to review status and progress of project and
to identify any outstanding issues.
Manages Change Orders.
Lead Functional Analyst Supports project planning activities.
Works with the Project Manager to coordinate and schedule onsite configuration planning activities.
Performs onsite configuration planning activities.
Oversees business analysis activities on the project.
Oversees system configuration activities.
Supports training content development and training delivery activities.
Supports development and test activity.
Provides support to the MCSO and Syscon project teams during acceptance testing.
Provides go-live support.
Facilitates post-go-live mentoring sessions.
Participates in knowledge transfer to MCSO
Development Manager Reviews and works with the Development team to ensure complete coverage of the project.
Oversees all development activities.
Maintains overall technical solution direction.
Supports the scheduling and resourcing for the project.
Consults with project resources on all development, integration, testing and configuration management
activities.
Works with the Project Manager to monitor progress and address any risks/issues identified throughout
the project.
Supports the project team for go-live.
Subject Matter Expert Provides expertise to the project in the areas of implementation, training, change management and
domain best practices.
Works closely with MCSO to define the solution based on MCSO requirements.
Client advocate to product management group including the gathering and validation of requirements for
the Workflow product team for new functionality.
Provides quality assurance of all project deliverables (documents, product features) to ensure they will
meet needs of MCSO.
Support on-site go live activities.
Technical Analyst Participates in configuration requirements workshops
Prepares specifications for custom reports/dashboards, orchestrations, business rules and complex event
processing (CEP) as applicable
Develops and unit tests custom reports, orchestrations, business rules and CEP as applicable
Troubleshoots and resolves defects related to custom reports, orchestrations, business rules and CEP
Provides training and knowledge transfer to MCSO technical staff as required.
Provides support to the MCSO and Syscon project teams during acceptance testing.
Provides go-live support.
Test Analyst Develops and executes test scripts.
Reviews scripts with Business Analysts, Data Migration Analysts, and Interface Analysts prior to test
execution.
Records test results during testing activities and logs issues as required.
Updates test scripts based on changes to application configuration
Updates test scripts based on approved change requests.
Re-tests resolved issues and updates defect lag as required.
Test Lead Leads all test team tasks including interface development and data migration.
Responsible for the overall quality of the configured system.
Communicates technical issues to the technical analysts, Project Manager and client technical
counterparts.
Serves as testing point of contact with MCSO.
Consults with project resources on all development and integration, testing and configuration
management activities.

SERIAL I3139-RFP
Test Manager Oversees all test team tasks.
Prepares test plan and ensures it is followed throughout the project life cycle.
Supports Project Status and Project Steering Committee meetings.
Works with the product development team to ensure critical issues are addressed
Ensures adequate test resource assignments.
Training Lead Leads all training activities.
Collaborates with the Organizational Change Management Lead
Prepares Training Plan for MCSO project training activities.
Training Specialist Conducts Train-the-Trainer (T3) training sessions.
Tailors Workflow product training materials for project.
Works closely with MCSO trainers.
Collaborates with the Organizational Change Management Lead.
Supports development of Training Plan.
Table 3: Syscon Roles and Responsibilities
2.2. Key MCSO Personnel Roles and Responsibilities
Name Role
Chief Shelly Bunn Executive Sponsors
Chief Lee Ann Bohn Executive Steering Committee
Chief Don Marchand
Dave Davis Project Director
Lori Wolfe Project Managers
Mike Clements
Dot Culhane Core Functional Team
Marty Spidell
Virginia Collins
Various — to be involved based on topic Subject Matter Expert
Daren Wood Technical Manager
Legacy Programmers/System Analysts Core Technical Team
Network & System Administrators
Amy Rex Organizational Change Manager
Bobbie O'Connell JMS Administrator
Table 4: Key MCSO Personnel
Any changes in the above defined personnel are solely the decision of MCSO and County and are not subject to
consultation with or approval by Syscon.
Role Responsibilities
Executive Sponsor See g_overnance section 1.3
Executive Steering Committee See governance section 1.3
Project Director See governance section 1.3
Project Management Office • Leads MCSO project teams
• Resolves cross-functional issues at the project level
• Aligns MCSO tasks to the overall project plan/schedule
• Works with the Syseon Project Manager to coordinate and execute
the implementation schedule and associated plans
• Protects scope, timeline and budget
• Manages issues through resolution and escalates to Project Director
when necessary
• Participates in regular Syscon conference calls/webex sessions as
required
• Manages Scope Change Orders and works with Syscon and Project
Team to recommend acceptance/rejection
• Reports to MCSO Project Director
• Facilitates review, feedback and acceptance of Syseon deliverables
Core Functional Team • Participates in configuration activities
• Supports training content development and training delivery
activities
• Supports customization design and testing activities
• Participates in Acceptance and Reliability Testing
• Provides go-live support
• Ensures MCSO requirements are met
• Supports Organizational Change Management activities
• Acts as Organizational Change Agents

SERIAL 13139-RFT
• Reports functional task status and issues to MCSO project
management
Subject Matter Expert (S1v1E) • Participates in functional configuration work sessions
• Participates in testing activities
• Participates as change agents
• Supports go-live
Technical Manager • Oversees all MCSO development activities
• Assigns required MCSO technical resources
• Plans MCSO technical project tasks and coordinates internally
• Coordinates with the owners of the 1CJIS Integration Engine (IIE)
for interface development and testing
• Ensures adequate knowledge transfer to MCSO
• Reports technical task status and issues to MCSO Project Manager
• Oversees transition to support
Core Technical Team • Participates in data conversion activities (data extracts, mapping
and cleansing)
• Develops assigned reports/dashboards
• Participates in testing
• Participates in knowledge transfer training
• Setup and configures new infrastructure
• Monitors MCSO environments
• Reports status and issues to Technical Manager
Organizational Change Manager • Leads development of the strategy and plan
• Manages the change activities
• Leads design of new roles and processes
• Ensures policies and procedures are updated
• Leads outreach/communication
• Leads user training
• Ensures organizational readiness
• Plans, organizes and leads go-live support activities
jms Administrator • Administers contracts
• Manages project budget
• Processes Contractor invoices
• Participates as a member of the Core Team
Table 5: MCSO Roles and Responsibilities
2.3. Contractor Staffing Plan
The following are the preferred requirements for positions associated with this project in the event of personnel
changes.
I., e -..1 N .+ it ill Vi Fit le liieferred ()cantle:ill ins
Senior Project Manager • 10 years of large-scale program/project management
experience.
• 2 prior MS projects of similar size and scope,
• Successful implementation of the proposed software is
required.
• PMP preferred
Enterprise Architect • 5 years of professional enterprise architectural experience
with the proposed technical environment/infrastructure
Database Administrator • 5 years experience with the proposed database
Senior Development • 5 years experience with the proposed JMS software
Manager
Senior Business • 10 years of large-scale business analyst experience.
Analyst • 3 years experience with the proposed JMS software is
required
'inject Po.,ithni 'referred an Mica! ion s
:3?years of scheduling experience, on large-scale :pinj ects of
similar Sii6andiabOpe:tri:theMCSO'JMS' ;.: ,Opportunity.
FMP preferred.
Testing Manager 3 years' experience with the proposed JMS software
required

SERIAL 13139-RFP
'CónfigwdReleaeMinnie* i*,:ritfi':'!th proposedtoftvreis
:!required.:
Training Manager 3 years' experience with the proposed IMS software is
required
.:,Inteirate.1.(:OnVer*toiii.Viinagee 3: ,:::yeas!: : experience with the PEOPosed :11‘48 software is
required
3. Timeline
The implementation project will be tracked to a forty-two (42) month timeline. The Gantt chart below presents the
major project phases, major project activities and major project milestones. This visual presentation will be
supported by a detailed project schedule/work plan developed during the Prepare stage of each phase of the project,
and maintained/updated throughout the project duration. The plan will identify the tasks, durations and assignments
required to successfully complete the project.
Each phase will include the following:
• Four (4) month user acceptance test ("UAT")
• Thirty (30) day reliability test period commencing immediately after go live of each phase
• After the Reliability Test Period has passed as set out in Exhibit B, Part 2, Section 8.2, the Warranty 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) a mutual agreement to an additional Warranty Period of forty-five (45) days.
3.1. High Level Plan
The diagram below depicts the high level project plan, including functionality planned for Phases I, 2a and 2b:
PNODUCT DEVELOPMENT PLAN
PCost I bes.-rttadales
PHASE
PHASE
2a 1,..1111:0211,[11.1 se,rtas.
PrISAI CONOIMINal.
PHASE
2b
Ste1.1)..7:11.1.1
=au. '
eeta
Workflow mcsoNOMMDenlAtlad 'Moen.
fr
Figure 2: High Level Plan

SERIAL 13139-RFP
3.2. Work Breakdown Structure
The Work Breakdown Structure (WBS) required for meeting the project requirements will be agreed to during the
Prepare stage of the project. The WBS presented below is a draft only and shall be refined during the Prepare phase.
WBS • ;.Task Name
1 :Maricopa County (MCSO) IMS Implementation Project
1.1.1 Project Start-up
1.1.2 Project initiation
1.1.5 Prepare
1.1.5.1 Project Governance
1.1.5.2 Internal Kick-Off Meeting
1.1.5.3 Develop Project Management Plan (PMP)
1.1.5.4 Organizational Change Management Support
1.1.5.5 Implementation Questionnaire
1.1,5.6 Confirm and finalize MCSO Infrastructure requirements
1.1.5.7 Prepare Requirements Traceability Matrix
1.1.5.8 Client Kick-Off Meeting
1,1.59 Build project environments
1.1.5.10 Deliver Product Artifacts/Guides
1.1.5.11 Gate Review (GR1)
1.1.6 Define
1.1.6.1 Project Governance
1.1.6.2 Organizational Change Management Support
1.1.6.3 Maintain Product Change Log
1.1.6.4 Syscon Environment Maintenance
1.1.6.5 Configure CLOUD environment (preliminary configuration)
1.1,6.6 Basic system configuration on-site training
1.1.6.7 Conduct onsite Business Process & Configuration Planning
1.1.6.8 Training - Carry-out onsite training and planning
1.1.6.9 Cut-over Strategy
1.1.6.10 Test Plan development
1.1.6,11 Installation and Configuration ofMCSO Infrastructure and Toots
1.1.6.12 Post On-Site activities
1.1,6.13 Gate Review (GR2)
1.1.7 Configure
1.1.7.1 Project Governance
1.1.7.2 Organizational Change Management Support
1.1.7.3 Syscon Environment Maintenance
1.1.7.4 Maintenance & Operations Plan
1.1.7.5 MCSO Support Transition Plan
1.1.7.6 Configuration Activities
1.1.7.7 Test Plan Execution
1.1.7.8 Create Configuration Specification Document
1.1.7.9 Training activities
1.1.7.10 Client configured product on-site installation for each major release
1.1.7.11 Gate Review (GR3)
1.1.8 Validate
1.1.8.1 Project Governance
1.1.8.2 Organizational Change Management Support
1.1.8.3 Syscon Environment Maintenance
1.1.8.4 MCSO Environment Maintenance
1.1.8.5 User Acceptance Test (Functional, Integration, Performance, Failover, Load, Security)
1.1.8.6 Support Cut-over Plan

SERIAL 13139-RFP
1.1.8.7 Support Go-Live Training
1.1.8.8 Gate Review (GR4)
1.1.9 Deploy
1.1.9.1 Project Governance
1.1.9.2 Organizational Change Management Support
1.1.9.3 Syscon Environment Maintenance
1.1.9.4 Data Migration Production Load (production transition)
1.1.9.5 Interface Production Deployment
1.1.9.6 Onsite Support Go-Live
1.1.9.7 Client Sign-off of Go-Live
1.1.9.8 Gate Review (GR5)
1.1.10 Transition
1.1.10.1 Project Governance
1.1.10.2 Syscon Environment Maintenance
1.1.10.3 Reliability Test Period
1.1.10.4 Post-Production Data migration Support
1.1.10.5 Post-Production Interface Support
1.1.10.6 Warranty
1.1.10.7 Post-Production Training
1.1.10.8 Handover To Support
1.1.10.9 Gate Review (0R6)
1.2.1 Project Start-up
1.2.2 Project initiation
12.3 Prepare
1.2,3.1 Project Governance
1.23.2 Organizational Change Management Support
1.2.3.3 Internal Kick-Off Meeting
1.2.3.4 Develop Project Management Plan (PMP)
1.2.3.5 Implementation Questionnaire
1.2.3.6 Prepare Requirements Traceability Matrix
1.2.3.7 Client Kick-Off Meeting
1.2.3.8 Build project environments
1.2.3.9 Deliver Product Artifacts/Guides
1.2.3.10 Gate Review (GR1)
1.2.4 Define
1.2.4.1 Project Governance
1.2.4.2 Organizational Change Management Support
1.2.42 Maintain Product Change Log
1.2.4.4 Syscon Environment Maintenance
1.2.4.5 Configure CLOUD environment (preliminary configuration)
1.2.4.6 Basic system configuration on-site training
1.2.4.7 Conduct onsite Business Process & Configuration Planning
1.2.4.8 Training - Carry-out onsite training and planning
1.2.4.9 Cut-over Strategy
1.2.4.10 Test Plan development
1.2.4.11 Post On-Site activities
1.2.4.12 Gate Review (GR2)
1.2.5 Configure
1.2.5.1 Project Governance
1.2.5.2 Organizational Change Management Support
1.2.5.3 Syscon Environment Maintenance
1.2.5.4 IMS System Security Policy
1.2.5.5 Deliverable: JMS System Security Policy
1.2.5.6 Maintenance & Operations Plan

SERIAL 13139-RFP
1.2.5.7 Deliverable: Maintenance & Operations Plan
1.2.5.8 MCSO Support Transition Plan
1.2.5.9 Configuration Activities
1.2.5.10 Test Nan Execution
1.2.5.11 Update Configuration Specification Document - as configured
1,2,5.12 Training activities
1.2.5.13 Client configured product on-site installation
1.2.5.14 Gate Review (GR3)
1.2.6 Validate
1.2.6.1 Project Governance
1.2.6.2 Organizational Change Management Support
1.2.6.3 Sysc.on Environment Maintenance
1.2.6.4 MCSO Environment Maintenance
1.2.6.5 User Acceptance Test (Functional, Integration, Performance, Failover)
1.2.6.6 Support Cut-over Plan
Support Go-Live Training
1.2.6.8 Gate Review (GR4)
1.2.7 Deploy
1.2.7.1 Project Governance
1.2.7.2 Organizational Change Management Support
1.2.7.3 Syston Environment Maintenance
1.2.7.4 Data Migration Production Load (production transition)
1.2.7.5 Interface Production Deployment
1.2.7.6 Onsite Support Go-Live Phase 2a
1.2.7.7 Client Sign-off of Go-Live
1.2.7.8 Onsite Support Go-Live Phase 2b
1.2.7.9 Client Sign-off of Go-Live
1.2.7.10 Gate Review (GR5)
1.2.8 Transition
1.2.8.1 Project Governance
1.2.8.2 Syscon Environment Maintenance
1.2.8.3 Reliability Test Period
1.2.8.4 Post-Production Data migration Support
1.2.8.5 Post-Production Interface Support
1.2.8.6 Warranty
1.2.8.7 Post-Production Training
1.2.8.8 Handover To Support
4. Work Plan
4.1. JMS Implementation Phase 1
Phase 1 of the project will replace core functionality in MCSO's current JMS system with the following
WorkflowJAIL modules and interfaces:
4.2. Phase 1: WorkflowJAIL Modules:
1. Admission / Transfer / Release
2. Assessment & Classification
3. Billing of Services
4. Case Management / Re-Entry
5. Counts
6. Court Orders & Legal Documents
7. Discipline
8. Event Log (Shift / Case Notes)
9. Housing Bed Management

SERIAL 13139-REP
10. Inmate Correspondence
11. Inmate Property
12. Movements (Court Operations)
13. Requests and Grievances
14. Security Threat Groups
15. Sentence Accounting
16. Visits
17. Diets 1 (Limited Functionality)
18. Programs
4.3. Phase 1: Interfaces
1. Court / ICIS Systems
2. Inmate Telephone System
3. Jolts
4. Justware
5, Livescan
6. Mercy Maricopa
7. Naphcare EHR
8. PHRED
9. Video Visitation (SECURUS)
10. Coplink
Ii. Mugsbot
12. Justice Web Interface (JWI)
13. IA Pro
14. Offender Based Tracking System (OBTS)
15. IFCS (Bridging Interfaces)
16. Pre-Book (Bridging Interfaces)
17. Court Operations (Bridging Interfaces)
The interfaces listed above will be incorporated into the overall project delivery schedule for Phase 1. Release dates
for each interface will be finalized in the Prepare stage.
4.4. Phase 1: Data Migration
Phase I data conversion will consist of converting the following:
1. JMS data (which includes the operational data store, the offline archived bookings and offline audit history)
2. IFCS WIMP data to the new-JMS environment.
4.5. Phase 1: Software Customizations
Syscon shall provide those Enhancements or Custom Modifications listed, and the documentation to accompany
such enhancements and custom modifications in the Contract, in accordance with the time frames set forth in the
Project Management Plan. When fully installed and accepted, the Software will meet those functional requirements
specified in contract Exhibit B Sub a & b.
The following custom modifications will be included in Phase 1:
Work Package Requirements
Legals F-CT-17, F-CT-18, F-CT-23, F-CT-39, F-CT-50, F-CT-63, F-LID-1, F-HD-2, F-
HD-6, F-HD-12, F-HD-14, F-HD-16, F-IN-39
Sentence Calculation F-CT-55, F-CT-87, F-SN-10, F-SN-5, F-SN-8
Reporting F-J0-36, F-RP-14

SERIAL 13139-RFP
Programs F-PG-29
Non-Functional F-CT-93, F-DS-8, F-SA-52, F-SA-57, F-SA-58, F-SA-59, F-SA-70, F-SA-84, F-
SA-111, F-WK-71, F-WK-72, F-WK-74, F-WK-75, F-DS-1, F-GN-2, F-GN-13
Property F-PR-1, F-PR-8, F-PR-10, F-PR-1 1
Billing of Services F-FI-30
Scheduling F-CT-21, F-SC-5
Nightly Snapshot for F-PG-44, F-RP-3, F-RP-17, F-RP-18, F-RP-19, F-PG-52. F-RP-31, F-RP-32
Reporting Environment
Table 6: Phase I Software Customizations
The above listed customizations will be delivered as part of the product releases for Phase I. Release dates for each
customization will be finalized in the Prepare stage.
For each software customization the Contractor will carry out the following activities:
Requirements Definition
Detailed business analysis is conducted relating to each work package. Analysis will identify more detailed
functional and non-functional requirements.
Functional and non-functional requirements that are identified are documented in a requirements specification
document.
Business Concept Design
The Contractor will design each enhancement and prepare a business concept design ('BCD'). This design will be
consistent with requirements as specified in the requirements specification document.
Development
For each enhancement Syscon shall construct and test the software. This software will be constructed as designed in
the Business Concept Design.
Quality Assurance
For each software customization, the Test Team will create test cases and automated test scripts based on the MCSO
requirements. These test cases and test scripts will be mapped against the client requirements in the Requirements
Traceability Matrix document to ensure each customization has test coverage. Test coverage will include
integration of the customization to the product. The automated test scripts will be used for regression to ensure the
customization pieces do not introduce any issues in the product. Syscon will deliver automated test scripts used
during Syscon's internal system testing in support of user acceptance testing conducted by MCSO.
Delivery & UAT Support
Delivery of each enhancement will follow the adopted Project Schedule and may be adjusted if agreed to by both
MCSO and Syscon. Post-delivery of the customization, Syscon will walk through applicable activities as required to
Define and Configure the software in preparation for the UAT period. Upon completion of the configuration
activities Syscon will update the appropriate configuration specification documents. Syscon will provide assistance
in support of user acceptance testing conducted by MCSO. Scripts will generally include defined input and expected
output results for each function based upon the design Specifications. MCSO will document problems discovered
during testing. MCSO will identify, track, and report problems during user acceptance testing to Syscon.

SERIAL 13139-REP
4.6. Phase 1: Training
During the Define stage of the project, it will be determined which administrative, functional, and technical sessions
should be delivered at each training delivery point in the project schedule. During this planning stage of the project,
decisions regarding the timing of the different training components will be made collaboratively in order to align the
training schedule with MCSO's business transformation, reporting, and interface priorities, in addition to the phases
of the project. The configuration training will provide MCSO staff with sufficient understanding of the system's
configuration to participate actively in the configuration stage of the project. Where possible Syscon will incorporate
two (2) or more workshops during the same travel period.
The table below outlines the project training activities:
Training Activity Description of # of Max. #
Classes Days On of T3's.
Site
Functional Overview The functional overview training will provide the core project team with N/A NIA N/A
a preview of Workflow features and the business processes the system
supports via computer-based training. During these collaborative
sessions, Syscon will work with key stakeholders from various business
units to identify how the system will be configured to MCSO operations.
This functional overview training will be reinforced for project team
members through completion of Syscon's Workflow product computer-
based training modules.
Technical Overview This initial technical training session is focused on hardware installation 1 N/A 10
and set-up information that technical staff members need to create the
client-side project environments. This overview will be covered in one
onsite session.
System Administration Workshop for each of the following: 6 N/A
(Technical)
Installation / Patch Deployment
Reporting
Business Rules
Interface ESB
Business Process Orchestration
Contractor Defined Performance & Monitoring Tools
Contractor Defined Automated Test Software
System Administration One onsite workshop for each module identified in section 4.2 TBD 10 N/A
(Application
Configuration)
Application Training The Workflow training strategy involves tailoring our product T3 3 30 60
training material to reflect the actual business process orchestrations and
configuration of the system for the Maricopa County Sheriff's Office
organiration. Tailoring of T3 Training Material to reflect ivICSO
configuration and logo. Syscon will utilize the Train-the-Trainer (T3)
approach.
Each of the training sessions will be led by two (2) Syscon trainers
Go Live Support Training Support MCSO trainers during the delivery to MCSO end-users during N/A 6 N/A
on-the-job training
Follow Up Training One onsite workshop for each module identified in section 4.2 TBD 5 N/A
Table 7: Phase I Training Summary
4.7. Training Material Customization
The Workflow training strategy includes tailoring of Syscon's product classroom training material to reflect the
business process orchestration and other configuration settings implemented for the Workflow system. These

SERIAL 13139-RFP
configuration-related changes will be made in accordance with the configuration requirements contained within the
project's configuration plan.
Additionally, Syscon will work with MCSO to incorporate key change management messaging into the classroom
training material as part of the project's change management effort. Training material will be customized and
delivered in accordance with a schedule jointly developed and agreed to by both MCSO and Syscon.
4.8. .IMS Implementation Phase 2a
Phase 2 will be broken out into two streams of activity implementing the following modules and interfaces:
4.9. Phase 2a: WorkflowJAIL Modules
1. Trust Accounting
2, Commissary
3. Health / Diets 2
4. Facility Issue (Inmate Property)
4.10. Phase 2a: Interfaces
1. Touchpay
The interfaces listed above will be incorporated into the overall project delivery schedule for Phase 2a. Release dates
for each interface will be finalized in the Prepare stage.
4.11. Phase 2a: Data Migration
Phase 2a data conversion will consist of converting the following:
1. Remaining Inmate Fund Canteen System (IFCS)
Data from SAP Business One Accounting will be manually converted.
4.12. Phase 2a: Software Customizations
The following custom modifications will be included in Phase 2a:
Work Package Requirements
Event Tracking F-.10-47
Financials F-CT-33, F-CT-36„ F-CT-37, F-CT-38, F-CT-45, F-Fl-7, F-TA-20, F-CT-88
Table 8: Phase 2a Software Customizations
The above listed customizations will be delivered as part of the product releases for Phase 2a. Release dates for each
customization will be finalized in the Prepare stage.
4.13. Phase 2a: Training
Training Activity Description # of # of Max.
Classes Days # of
On Site T3's
Functional Overview The functional overview training will provide the core project team N/A N/A N/A
with a preview of Workflow features and the business processes the
system supports via computer-based training. During these
collaborative sessions, Syscon will work with key stakeholders from
various business units to identify how the system will be configured
to MCSO operations. This functional overview training will be

SERIAL 13139-RFP
reinforced for project team members through completion of Syscon's
Workflow product computer-based training modules.
Technical Overview This initial technical training session is focused on hardware 1 N/A 10
installation and set-up information that technical staff members need
to create the client-side project environments. This overview will be
covered in one onsite session.
System Administration Workshop for each of the following: 1 2 N/A
(Technical)
a) Installation / Patch Deployment
b) Reporting
c) Business Rules
d) Interface ESB
e) Business Process Orchestration
System Administration One onsite workshop for each module identified in section TBD 3 N/A
(Application 4.9
Configuration)
Train-the-Trainer (T3) The Workflow training strategy involves tailoring our I 7 24
product T3 training material to reflect the actual business
process orchestrations and configuration of the system for
the Maricopa County Sheriff's Office organization. Tailoring
of T3 Training Material to reflect MCSO configuration and
logo. Syscon will utilize the Train-the-Trainer (T3) approach.
Each of the training sessions will be led by two (2) Syscon
trainers
Go Live Support Support MCSO trainers during the delivery to MCSO end- N/A 2 N/A
Training users during on-the-job training,
Follow Up Training One onsite workshop for each module identified in section TBD 2 N/A
4.9
Table 9: Phase 2a Training Summary
4.14. JMS Implementation Phase 2b
Phase 2b of the project will replace core functionality in MCSO's current JMS system with the following
WorkflowJAIL modules and interfaces:
4.15. Phase 2b: WorkflowJAIL Modules:
1_ Prel3ook
2. Transportation
3. Victims Services
4.16. Phase 2b: Interfaces
I. External Records Management Systems
2. MCSO Records Management Systems
3. ICIS Superior Court
4. Phoenix PD
5. Common Case Number
6. 2-Finger ID
7. EHR — CHS Techcare
The interfaces listed above will be incorporated into the overall project delivery schedule for Phase 2b Release
dates for each interface will be finalized in the Prepare stage.

SERIAL I3139-RFP
4.17. Phase 2b: Data Migration
Currently there is no data migration activity for Phase 2,
4.18. Phase 2b: Software Customizations
The following custom modifications will be included in Phase 2b:
Work Package Requirements
Pre-Book
Table 10: Phase 2b Software Customizations
The above listed customizations will be delivered as part of the product releases for Phase 2b. Release dates for each
customization will be finalized in the Prepare stage.
4.19. Phase 2b: Training
Training Activity Description 14 of # of Max.
Classes Days ft of
On T3' s
Site
Functional The functional overview training will provide the core project team with a N/A N/A N/A
Overview preview of Workflow features and the business processes the system supports
via computer-based training. During these collaborative sessions, Syscon wilt
work with key stakeholders from various business units to identify how the
system will be configured to MCSO operations, This functional overview
training will be reinforced for project team members through completion of
Syscon's Workflow product computer-based training modules.
Technical This initial technical training session is focused on hardware installation and 1 N/A 10
Overview set-up information that technical staff members need to create the client-side
project environments. This overview will be covered in one onsite session.
System Workshop for each of the following: N/A
Administration
(Technical) a) Installation / Patch Deployment
b) Reporting
c) Business Rules
d) Interfne ESB
e) Business Process Orchestration
System One onsite workshop for each module identified in section 4.15 TBD 2 N/A
Administration
(Application
Configuration)
Train-the-Trainer The Workflow training strategy involves tailoring our product T3 1 3 24
(T3) training material to reflect the actual business process orchestrations
and configuration of the system for the Maricopa County Sheriff's
Office organization. Tailoring of T3 Training Material to reflect
MCSO configuration and logo. Syscon will utilize the Train-the-
Trainer (T3) approach.
Each of the training sessions will be led by two (2) Syscon trainers
Go Live Support Support MCSO trainers during the delivery to MCSO end-users N/A 2 N/A
Training during on-the-job training.
Follow Up Training One onsite workshop for each module identified in section 4.15 TBD 1 N/A
Table 11: Phase 2b Training Summary

SERIAL 13139-RFP
4.20. Project Testing Approach
An overarching test strategy document will be mutually produced during the Define stage of the project to ensure all
Parties' expectations are aligned at an early stage. That test strategy document, once approved by all Parties, will
then form the foundation for all test plans produced thereafter.
The Contractor shall be responsible for developing System Testing and Integration plans, and shall provide MCSO
with drafts of these plans in accordance with the agreed upon project schedule. MCSO shall be responsible for
promptly reviewing and updating such plans. Test plans to be provided by the Contractor are:
• Testing the Product in accordance with published functions and features
• Testing the Application Package in accordance with RFP specifications
• Testing the System based on business scenarios
• Testing the System based on usability requirements in accordance with RFP specifications
• Testing the Interfaces based on design and business scenarios
• Security testing based upon agreed requirements in accordance with RFP specifications
• Data Conversion testing
• Integration testing
• Load testing
• Fail-over testing
All test plans are reviewed and any additions or changes requested by MCSO are incorporated as mutually agreed.
The Contractor will map all final RFP specifications to project test cases, via the Requirements Traceability Matrix,
to ensure that the functionality expected by MCSO is achieved.
The Contractor will perform system testing on all areas of the product that have been developed/configured to meet
MCSO requirements at Syscon offices as defined in the test plan.
Configuration and System Testing
During the Configure Stage, the Syscon Test Team will create, update and execute the configuration (includes
configuration, orchestration and reports) related manual test cases and automated test scripts that were created from
the requirements outlined in the Configuration Plan gathered during the Define stage. These tests will be performed
at Syscon by the Syscon Test Team.
System Testing will be performed by running the automated test scripts after the configuration, orchestration and
reports related changes are made. Test scripts that are affected by these changes will need to be updated and in some
cases re-created. These tests will be performed at Syscon by the Syscon Test Team.
During the Validate stage, System Testing utilizing the automated test scripts will be performed onsite by MCSO
with support from the Syscon test team.
These tests will be performed in Phases I and 2.
MCSO Interim Release Testing
Over the course of Phase I, Phase 2a and Phase 2b Syscon will use an iterative approach in releasing configured
software packages. Upon delivery of a configured software package, MCSO testing of WorkflowIAIL shall
commence prior to the start of UAT and shall be an on-going as an iterative activity throughout the Configuration
phase, The timing for completion of MCSO testing activities shall be mutually agreed upon and included in the
Project Plan. During this process MC50 will complete testing to validate the configuration and report to the
Contractor with feedback. Any such feedback will not impede the Contractor's scheduled future product release
dates or project activities during the Configure stage.
The interim testing process, prior to UAT, of software product drops shall include the following steps:
• Contractor completes a product drop;

SERIAL I3139-RFP
• Contractor configures the product drop with assistance from MCSO;
• Contractor provides a "conference room pilot" to demonstrate functionality included in the current
product drop and how it is intended to be used;
• MCSO completes additional testing to validate the configuration; and
• MCSO provides Contractor with feedback about the current product drop, which Contractor shall
consider and, where possible, incorporate into a subsequent product release.
Integration Testing
Integration Testing will be performed by running the test cases and automated test scripts after each module has
been configured or modified to ensure the changes or collection of changes have not introduced any issues in the
product. These integration tests are performed for each area at a time: configuration, orchestration and reports. Test
scripts that are affected by these changes will need to be updated and in some cases re-created. These tests will be
performed at Syscon by the Syscon Test Team. The integration tests are a subset of the system tests.
During the Validate stage, Integration Testing utilizing the automated test scripts will be performed onsite by MCSO
with support from the Syscon test team.
These tests will be performed in Phases I and 2.
Interface Testing
An Interface Test Plan will be developed during the Define Stage for each Phase of the project (Phase 1, Phase 2a
and Phase 2b). The test plans produced will identify the approach to testing each in-scope interface that will be
deployed in that phase. The test activities that will be defined and undertaken will encompass the Workflow trigger
event (if an outbound interface), message creation and routing. Test scripts and supporting test data will be
developed as part of the test planning. Interface testing will be performed by Syscon, with support provided by
MCSO resources familiar with the target applications being interfaced with. Initial testing will be done using
"stubs" to simulate the target systems. Once this unit level testing is completed, end-to-end testing will be
performed. For both the unit and end-to-end testing, existing interface messages will be leveraged where applicable.
Finally, interfaces will be part of the overall integration, system and UAT test events.
Conversion Testin2
A Data Migration Test Plan will be developed during the Define Stage for each data migration activity that will be
conducted (.IMS and 1FCS-WIMP in Phase I, and IFCS in Phase 2). The test activities that will be defined and
undertaken will encompass the complete scope of conversion including the extracts from source, the initial data load
into the ETL tool (Pentaho), all data integrity, transformation and auditabitity processes and procedures, the data
load into workflow as well as the data backup and recovery processes. These tests will be performed by Syscon,
with support provided by MCSO resources familiar with the legacy data being converted. Testing will initially be
performed on a unit-by-unit basis, focusing on verifying that each step of the conversion process is designed and
working to meet the requirements that have been defined. End-to-end testing will follow. For both the unit and end-
to-end testing, a subset of the actual production data from the legacy JMS and IFCS systems will be used in order to
ensure the data scenarios that will be encountered during conversion are part of the testing that is undertaken (note:
if production data cannot be used then Syscon will work with MCSO to create production like-data for these tests).
Finally, dry-runs using the complete production data set from .IMS and IFCS will be performed —these dry-runs will
be a full end-to-end test and verification of the conversion process.
Fail-over Testing
Fail-over testing will be executed during product development at Syscon to ensure the robustness of the application
as a whole. Test cases will then be executed on the configured product on MCSO's environment to prove that the
system is able to continue operations while the cutover mechanisms transfer the application to a back-up system
during critical failures or at the point the system reaches a predetermined performance threshold. Manual test cases
and automation test scripts will be provided to MCSO for review.
During the Validate stage (UAT) the same tests will be performed onsite by MCSO with support from the Syscon
test team. Specific fail over test conditions will be jointly defined by Syscon and MCSO during the Configure stage.

SERIAL 13139-RFP
These tests will be performed in Phases 1 and 2.
Performance Testing
Performance, stress and load are extensively tested during the development of the Workflow product. Once the
product is configured in MCSO's proposed production environment, performance testing is undertaken to make sure
that the solution can support the expected number of users and the active inmate population while maintaining
reasonable response times with no degradation seen in the system over time. This testing aims to run 'real world
scenarios' in the production environment with a user concurrency and the active inmate population as specified in
the Performance Test Plan.
A Performance Test Plan will be written to determine and define the key business transactions to be tested, and the
test approach. Performance, stress and load test scripts will be executed on the MCSO production environment
using load testing software. Since these scripts are linked to Workflow source code, Syseon will only provide the
test plan that details the test methodology. In order to run these scripts on MCSO's environment, Syscon will
provide support to install the client version of the load testing software and provide instruction on how to run
executables to detect any environmental related issues. A formal Performance Test Exit Report will be produced on
completion of the performance testing phase.
These tests will be performed in Phases I and 2.
4.2L Acceptance Testing
On-site Testing shall include three phases: an Acceptance Test period, a Reliability Test period and Warranty.
During the Acceptance Test period, which will align with Syscon's Validate stage of the Implementation process,
Workflow will be delivered and installed in MCSO's environment. The approved Test Plan will serve as the basis
for all Acceptance Testing, including User Acceptance Testing (UAT). Syscon will work with MCSO on-site, to
execute the tests defined within the Test plan, both automated and manual. These tests will include:
• Functional Tests that cover all published functions and features of Workflow
• Functional Tests that cover the software components identified in the RTM specifications (Appendix
2)
• Functional Tests that cover the identified business scenarios
• Functional Tests that cover the User Interface standards for usability
• Automated and Manual tests that cover Security
• Tests that cover the successful migration of data
• Smoke tests that ensure that Workflow works as expected on the MCSO hardware and network
• Stub tests that cover the identified Interfaces
• Automated and Manual tests that cover the integration of all software components identified in the
final RFP specifications
• Automated and Manual fail-over tests
• Performance Tests that cover the specifications relating to load and fail-over
The major activities required to support a successful user acceptance testing period are noted in the section above,
and summarized in the table below with respect to the Syscon and MCSO roles.
Task Syscon Role MCSO Role
MCSO UAT Test Planning C,1 R, A
Creation of Production Like Data' 1,R R, A
Perform Functional Testing C,I R., A
Perform Data Conversion Testing R, A
Perform Interface Testing C,1 R, A

SERIAL 13139-REP
Perform Fail Over Testing R, A
Perform Performance, Stress and Load Testing R, A R, A
Table 12: User Acceptance Activities and Roles
`Syscon will support creation of production-like data through execution of the delivered data conversion processes.
Legend:
R — Responsible - Those who are responsible to do the work to achieve the task and the creation of documents or information, This role includes
facilitation of information gathering and creation of deliverable material or the active support to create the information.
A - Accountable - Those who are ultimately accountable for the correct and thorough completion of the deliverable or task. The responsible
entities have work/tasks approved, or signed off by the individual(s) accountable for each task or deliverable. (Also approver, or final approving
authority)
C Consulted — Those whose opinions are sought through communications or participation in meetings or workshops.
I - Informed - Those who are kept up-to-date on progress, often only on completion of the task or deliverable. Receive communication.
S. Organizational Change Management
The following has been envisioned by the parties as a model for Organizational Change Management through the
life of Implementation. MCSO shall collaborate with Syscon during the Define Phase to further define the scope and
deliverables. Syseon will proceed with activities below with prior approval of MCSO.
Syscon will work with MCSO as the parties jointly explore, understand and document the process changes that
standardizing business practices across all of the MCSO's facilities will involve. Syscon has included services to
support MCSO's change management effort and to incorporate crucial pieces of change messaging provided by
MCSO in the project's T3 training material in order to ensure that staff members are fully aware of impending
changes and their impact.
At a high level, the roles and responsibilities breakdown between MC SO and Syscon will be as follows:
Activity MCSO Syscon
Strategy Development / Planning Lead
Project Management Lead Consult
Communication Lead Support
Process & Roles Redesign Lead Support
Change Outreach Lead Support
Change Readiness Lead Consult
Train-the-Trainer Training Support Lead
End-User Training Lead Support
Implement Knowledge Transfer Support Lead
Implementation Readiness Joint Effort Joint Effort
Implementation Go-Live Support Joint Effort Joint Effort
Transition to Maintenance Joint Effort Joint Effort
Table 13: Organizational Change Management Responsibilities

SERIAL 13139-RFP
5.1. Strategy Development / Planning
MCSO will create the Organizational Change Management Plan, and ensure that the project has strong executive
and management sponsorship. The transformational benefits of the new IMS implementation should be identified in
this plan with a strategy for acceptance of the change across the organization. This plan should align with the project
plan for the IMS implementation, and clearly outline roles and responsibilities for change management.
5.2. Project Management
MCSO will lead the project management activities around change management, creating the MCSO change
management team to support the change management plan. MCSO will consult with Syscon's project team on an
ongoing basis to coordinate activities and ensure appropriate Syseon and MCSO resourcing levels to support
planned change management activities.
5.3. Communication
MCSO Leadership will build trust and commitment to the change through open and frequent communications with
stakeholders through the execution of an MCSO created Communications Plan.
The Communications Plan should define the detailed, key messages, target audiences, vehicles, senders, and timing
of messages.
Syscon will support the execution of stakeholder communications, adding key communications milestones and
events to the project plan. The Communications Plan should be refreshed regularly, allowing for updated
communications requirements to be identified and addressed. It is anticipated that MCSO will leverage Syscon
project SMEs and MCSO communications staff to create communications and deliver messages to stakeholders.
5.4. Process & Roles Redesign
The implementation of a New „NS will redefine how MCSO operates. New ways of working will be defined for a
large number of staff. Systems that employees use for significant portions of their jobs will be decommissioned.
Change of this scale requires not only new processes, but changes in behaviors and mindsets to make the change
sustainable and beneficial to the organization.
MCSO will take the lead in documenting the "To-Be" business process as a result of the IMS implementation, to
processes, roles, and policies. Syscon staff will support this effort through assisting with "As Is" and "To Be"
process analysis and documentation, attending workshops, and creating other content at MCSO's direction. Syseon
staff will also support this effort through insertion of crucial change messaging into T3 and CBT training material.
5.5. Change Outreach
For the change vision to translate across all levels of the organization, it is important to identify the key leaders in
MCSO who will be responsible for driving and monitoring the change across the organization. MCSO should create
a network of Change agents for the project who will serve as early adopters of the transformation; cascade
communications across the organization; liaise with end users and other stakeholders to provide feedback to the
project team on the pulse of the organization; support the assessment of change impacts; and support the
development and implementation of mitigations. Syscon will support this effort by assisting MCSO with answers to
questions about the system, its capabilities, and the planned configuration and assisting with the creation of content
for change messaging.
5.6. Change Readiness
Change Readiness action plans are the tactical checklists of activities for each stakeholder group, derived from the
change management plan. MCSO will be responsible for developing Change Readiness plans and fleshing out the
component activities. Syscon will support this activity by providing input based on lessons learned from other
implementation projects.

SERIAL 13139-RFP
5.7. Train-the Trainer Training
Train-the-Trainer (T3) training is the core functional training offering from Syscon, and will be instrumental in
preparing trainers to perform end-user training as well as preparing SMEs and project team members for
undertaking user acceptance testing tasks. Syscon will deliver this training and will administer assessments to help
gauge the effectiveness of the training activity. MCSO will support T3 Training by managing the scheduling of
training activities, and ensuring that both students and facilities are available in accordance with the schedule.
5.8. End-User Training
End-User training is envisioned as a combination of computer-based training, on-the-job training, and classroom
training, delivered by MCSO staff trainers and Field Training Officers. MCSO will manage the scheduling of
training activities, ensure that both students and facilities are available in accordance with the schedule, and
administer assessments to help gauge the effectiveness of the training activities. Syscon will support this effort.
5.9. Implement Knowledge Transfer
Syscon will lead workshops to transfer knowledge to MCSO staff regarding interface development, maintenance of
business rules, and other topics to optimize MCSO's capabilities of answering user questions and troubleshooting
system problems post go-live. MCSO will support this activity by scheduling the workshops and ensuring that both
students and facilities are available in accordance with the schedule.
5.10. Implementation Readiness
Syscon and MCSO will jointly plan production cut-over and user acceptance testing activities to ensure that process
and procedure changes have been adequately covered and both functional and technical contingencies have been
addressed. The user acceptance testing and cutover plans will be implemented as agreed by both parties in advance
of the go-live event.
5.11. Implementation Go-Live Support
Syscon will support MCSO's production cut-over efforts onsite, and assist in performing the final production data
load as well as executing the other steps of the cut-over plan. Syscon staff will be onsite to help troubleshoot and
triage any production cut-over issues, answer questions, and assist MCSO staff in making any necessary
configuration changes to support production activities.
5.12. Transition to Maintenance
Syscon will work with MCSO to ensure that the transition to maintenance is a smooth one and that procedures for
defect reporting, escalation, and patch deliveries are clear to all parties and that the MCSO team's introduction to
Syscon's support department is facilitated in a timely and informative manner.
6. Milestones
Project milestones are a significant event in the project which may signify the acceptance or verification of
completion of a project phase, task, decision, or deliverable. It is important to note that milestones are not work
activities but rather significant events during the project. The milestones identified below will be incorporated into
the project schedule and completion dates will be confirmed during the prepare stage.
6.1. Phase 1 Milestones
Milestone Deliverables (Section 7) Estimated Completion
Date
Project Kick Off 4
Aug 2015
Prepare Phase Complete 1, 2, 3,4, 5, 6,7, 8, 9, 11, 12, 13, 14,15, 16,25,
36 Sep 2015

SERIAL I3139-RFP
WorkflowJAIL Delivery 1.1 ER 2.5) 26,31 Oct 2015
Configuration Complete 1.1 1112.51 33- Iteration Apr 2016
Interface Delivery 1.1 11ft2.51 TBD Apr 2016
WorliflowJAIL Delivery 1.2 [R 3.01 27,31 Jul 2016
Configuration Complete 1.2 112 3.01 33 - Iteration 2 Aug 2016
Interface Delivery 12 ER 3.0) TBD Aug 2016
Define Phase Complete 10, 17, 19, 18, 20, 21, 23, 34, 36, 37,38 Nov 2016
WorkflowJAIL Delivery 13 [R 3.5] 28,31 Oct 2016
Configuration Complete 1.3 [R 3.51 33 Final Iteration Feb 2017
Interface Delivery and Data Conversion Complete 1.3 [R TBD
3.51 Feb 2017
Configure Phase Complete 17, 22, 29, 30, 31, 32, 33, 35, 36 Feb 2017
Validate Stage Complete ("UAT") 24, 30, 32 Jun 2017
System in Production 36 Jul 2017
Completion of Warranty 36 Oct 2017
Table 14: Phase 1 Milestones
6.2. Phase 2a Milestones
Milestone Deliverables (Section 7) Estimated Completion Date
Prepare Phase Complete 39, 40, 42, 58 Jan 2017
Workflow3AIL Delivery 2.1 [R 4.01 50,53 Apr 2017
Configuration Complete 2.1 ER 4.01 34 - Iteration 1 Aug 2017
Interface Delivery 2.1 FR 4.01 TBD Aug 2017
Workflow3A1L Delivery 2.2 [R 4.51 51, 53 Aug 2017
Define Phase Complete 23,38, 41, 44, 45, 46, 48, 55, 58, 59,60
Nov 2017
Configuration Complete 2.2 IR 4.5) 54 — Final Iteration Feb 2018
Interface Delivery and Data Conversion Complete 2.2 ER 4.51 Till)
Feb 2018
Configure Phase Complete 43, 47, 52, 56, 57, 58 Feb 2018
Validate Stage Complete ("UAT") 43, 44, 45, 49, 57 Jun 2018
System in Production 58 Jul 2018
Completion of Warranty 58 Sep 2018
Table 15: Phase 2a Milestones
6.3. Phase 2b Milestones
Milestone Deliverables (Section 7)# Estimated Completion Date
Prepare Phase Complete 39,40, 42,58 Jan 2017
WorkflowJAIL Delivery 2.1 112 4.01 50,53 Apr 2017
Configuration Complete 2-1 [It 4.01 54 - Iteration 1 Aug 2017
Interface Delivery 2.1 [It 4.01 TBD Aug 2017

SERIAL 13139-RFP
WorkflowJAIL Delivery 2.2 [R 4.5] 51, 53 Aug 2017
Define Phase Complete 23, 38, 41, 44, 45, 46, 48, 55, 58, 59,60
Nov 2017
Configuration Complete 2.2 [IR 4.5] 54— Final Iteration Feb 2018
Interface Delivery and Data Conversion Complete 2.2 IR 4.5] TI3D
Feb 2018
Configure Phase Complete 43, 47, 52, 56, 57, 58 Feb 2018
Validate Stage Complete ("UAT") 43, 44, 45, 49, 57 Jun 2018
System in Production 58 Sep 2018
Completion of Warranty 58 Dec 2018
Table 16: Phase 2b Milestones
7, Deliverables
The tables below identify the deliverables in scope for the implementation project. MCSO plans to store project
deliverables and artifacts in a SharePoint project repository to which Syscon will have access to.
7.1. Phase 1 Deliverables
The following is a list of key project deliverables for Phase 1 o f the implementation project:
Deliverable 4 Deliverable Description Stage
Scope Management The Scope Management Plan defines the types of changes that may be requested Prepare
1 Plan during the project, how they will be assessed, and how they will be authorized.
Project Charter The project charter or project statement is a statement of the scope, objectives, and Prepare
participants in a project. It provides a preliminary delineation of roles and
2 responsibilities, outlines the project objectives, identifies the main stakeholders,
and defines the authority of the project manager.
Work Breakdown The WBS identifies all the deliverables and milestones for the project. These will Prepare
3 Structure (WBS) be reviewed with project stakeholders and approved.
Project Kick Off The Project Kickoff Meeting formally recognizes the start of the project. The Prepare
Meeting project manager uses this meeting to communicate a shared view of the project to
4 ensure all stakeholders are aware of the objectives of the project, expectations of
them, and everyone is aligned on the next steps to complete the project Work Plan
and Control Plan.
Scope Change The Scope Change Management Plan defines the guidelines and procedures the Prepare
5 Management Plan project team will use to manage requests for changes to the scope of the project.
Project Schedule The Project Schedule is a Microsoft Project Plan_ (mpp) file that will detail all the Prepare
6 activities/tasks (with owners), durations, start/end dates, milestones, dependencies,
and status (percentage complete) for the project.
Schedule The Schedule Management Plan outlines the severity levels of any potential Prepare
Management Plan schedule impacts, identify who needs to be involved in assessing and approving
7 any changes, and how any approved schedule changes will be communicated to
project stakeholders.
Cost Management The Cost Management Plan outlines the severity levels of any potential cost Prepare
8 Plan impacts, identify who needs to be involved in assessing and approving any
changes, and how any approved cost changes will be communicated to project
stakeholders,

SERIAL 13139-RF1
Quality Management The Quality Management Plan details our three-tiered approach to Quality Prepare
Plan Management:
• Quality Planning — Exploring what quality policies, processes and
standards should be applied to the project, and planning how we will
meet those standards and policies, and apply thoseprocesses
• Quality Assurance — undertaking the activities necessary to ensure the
9 project will achieve the agreed Quality standards.
• Quality Control — undertaking planned activities to measure and record
outputs, in order to ensure we are meeting the stated Quality objectives.
Test Strategy The Test Strategy describes the overarching test fundamentals for all testing Define
activities of the project. It will outline test activity ownership, scope, roles and
responsibilities, defect severity and priority definitions and entry and exit criteria.
The test strategy document will then form the formal agreement going forward for
10 the basis of all test plan and test exit report documents.
Requirements The Requirements Specifications Management Plan outlines how we intend to Prepare
11 Specifications gather and manage requirements, and outline our processes for establishing and
Management Plan maintaining traceability,
Configuration and The Configuration and Release Management Plan outlines the naming conventions Prepare
Release Management to be used for any project artifacts/documents and detail where the project
Plan document repository can be accessed by the project team to ensure the project
team always have access to the latest version-controlled project documents. It also
12 details how the configuration of the JMS will be managed including the process to
be used for releasing new code/patches into the system configuration and the
documentation that will be produced to support each release.
Project Organizational The Project Organizational Structure details the reporting relationships of Prepare
13 Structure everyone directly involved with the project.
Resource The Resource Management Plan details the required skills and staffing levels for Prepare
14 Management Plan each stage of the project and will include a responsibility assignment matrix
summarizing everyone's assignments.
Communication The Communication Management Plan defines the information and Prepare
Management Plan communication needs of the project and outlines the methods that will be
15 employed to meet these needs. This will include details of meetings and reports
(e.g. status reports) that will be used to communicate with stakeholders.
Risk Management The Risk Management Plan identifies the processes to be used to identify and Prepare
Plan quantify potential risks, define the format of the risk assessment matrix and risk
16 register, define the risk response process should a risk occur, identify who needs to
be involved in assessing and approving any contingency or mitigation action, and
how any approved actions will be communicated to project stakeholders.
17 Product CBT course WorkflowJAIL product computer based training course materials. Define
materials
Interface Control Plan An interface control plan shall be developed that establishes the methodology to Define
be used for developing, controlling, testing, and managing the data interfaces
18 between systems. Where organizations external to MCSO are involved, the plan
will formalize the roles and responsibilities between the two (or more)
organizations for developing and testing the interface components.
Requirements Detailed business analysis is conducted relating to each customization. Analysis Define
19 Specification will identify more detailed functional and non-functional requirements,
Document Functional and non-functional requirements that are identified are documented in a
requirements specification document.
Data Conversion Plan Determine conversion plan; Determine data integration plan; Plan deployment Define
(how will migration be done to support go-live); Develop migration data quality
20 plan; Develop data migration test plan.

SERIAL 13139-RFP
Training Plan The Training Plan document outlines the scope of training activities, lays out the Define
project's training goals and objectives, outlines the project training approach, and
specifies the curriculum details for each of the project's training activities. The
training plan also establishes the roles and responsibilities pertaining to training,
and contains a high-level work plan which identifies the project stage within
which each training element will be delivered.
MCSO Support Team A plan shall be produced that details the knowledge that MCSO staff will need to Configure
Knowledge Transfer support the system. Specific activities and tasks will be outlined that, when
Plan executed, will transfer knowledge from the vendor team to MCSO support staff,
IvICSO support resource requirements will be called out in the plan, along with
associated skill sets and training prerequisites.
IMS System Security Implementation of the New .IMS solution makes the legacy security policy Define
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 (SSO).
Tactical Deployment MCSO with the support of Syscon will create a detailed tactical deployment plan Validate
and Cut Over Plan 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.
Design Document The Contractor will design each enhancement and prepare a conceptual design Configure
document. This design will be consistent with requirements as specified in the
requirements specification document and will be provided to MCSO for review
and feedback.
Workfl owJAIL Delivery of out-of-the-box Workflow Release 2.5 COTS software which includes Define
Product Delivery 1.1 the following:
[Release 2.5]
• Software package
• Installation documentation for all Syscon developed software
• Entity Relationship Diagram
• Data Model Dictionary
WorkflowJAIL Delivery of out-of-the-box Workflow Release 3.0 COTS software which includes Define
Product Delivery 1.2 the following:
[Release 3.01
• Software package
• Installation documentation for all Syscon developed software
• Entity Relationship Diagram
• Data Model Dictionary
WorkflowJAIL Delivery of out-of-the-box Workflow Release 3.5 COTS software which includes Define
Product Delivery 1.3 the following:
[Release 3.5]
• Software package
• Installation documentation for all Syscondeveloped software
• Entity Relationship Diagram
• Data Model Dictionary
UAT Ready Includes Phase 1 software modules, interfaces, software customizations and the Configure
Workflow Product following:
[Release 3.5]
• Installed and Configured Software package at MCSO site
• Workflow Product Documentation
• Installation documentation for all Syscon developed software
• Application Programming Interface (API) guide
• Online Help
• Training documentation
• Product Computer Based Training (CDT) modules
• System Configuration Documentation
• Database ERD Diagram
• Workflow Data Dictionary

SERIAL 13139-RFP
Maintenance & Syscon will assist MCSO with the creation of a maintenance and operations plan Configure
Operations Plan which describes the activities required to effectively operate and maintain the
application system in a day-to-day operational environment. In particular Syscon
will identify key components that should be backed up on a regular schedule along
30 with recommended tool sets. The deliverable plan shall detail plans for operating,
monitoring, performance tuning, identification and training of operators, and
testing the system after changes are made.
Workflow Automated Syscon will provide the Workflow automated test cases or test scripts for Configure
Test Cases execution along with the data input files, drivers, third-party libraries, logs and
31 executables JAR (JAVA Archive) files. These are based on Workflow's web user
interface and are used to simulate the user experience throughout areas of the
application.
Test Exit Reports The Test Exit Report will include references to the scope, testing approach, entry Configure,
and exit criteria as outlined in the Test Strategy document created during the Validate
Prepare Stage plus references to the test plans created during the Define Stage. In
addition, this report will summarize the test results including statistics on the
32 number of manual and automated test cases/scripts that are executed during the
Configure Stage and the outcome of those tests including a list of unresolved
issues if any. This report will be shared with MCSO at the end of the Configure
Stage and Validate Stage.
Configured Software Once each portion of the system configuration is finalized, it is documented in the Configure
Package & system configuration specification, which is delivered to MCSO with the
33 Configuration configured environment.
Specification
Document
Test Plan A formal test document produced by Syscon detailing the scope, approach, roles Define
and responsibilities, defect management and entry and exit criteria for each
34 specific testing phase. The document will describe the plan and approach for the
following; Load, Regression, Unit, System, Functional, Security, High
Availability/Reliability
35 Customized Training Workflow training materials will be tailored to reflect the MCSO implementation. Configure
Materials
Lessons Learned At the conclusion of each phase called out in the project schedule, lessons learned Prepare,
Document shall be documented and distributed to the team. This deliverable will detail what Define,
36 worked well and what did not, and will serve to inform future phases so successes Configure,
can be capitalized upon while challenges and failures can be avoided. Validate,
Deploy,
Transition
37 Requirements The Requirements Traceability Matrix (RTM) is a document that links Define
Traceability Matrix requirements throughout the validation process.
Data Exchange This work activity will deliver the detailed data exchange mapping, designs and Define
Requirements ESE configuration/builds including:Data field mapping between the Workflow
38 and MCSO Intemal/Legacy systems or partner/external stakeholder
systems;Producing the Data Exchange Functional Configuration Specifications
(error handling and message content);Transforniation Business Rules.
7.2. Phase 2a and 2b Deliverables
Deliverable Deliverable Description Stage
39 Work Breakdown The WES identifies all the deliverables for Phase 2a & 2b of the project These will Prepare
Structure (WES) be reviewed with project stakeholders and approved.
40 Project Schedule Update Phase 1 Document as applicable Prepare
41 Test Strategy Update Phase 1 Document as applicable. Define
42 Configuration and Update Phase 1 Document as applicable. Prepare
Release
Management Plan
43 Product CBT WorkflowJAIL product computer based training course materials. Configure
course materials
44 Interface Control Update Phase I Document as applicable. Define
Plan

SERIAL 13139-RFP
45 Data Conversion Determine conversion plan; Determine data integration plan; Plan deployment (how Define
Plan will migration be done to support go-live); Develop migration data quality plan;
Develop data migration test plan.
46 Training Plan Update Phase 1 Document as applicable. Define
47 MCSO Support Update Phase 1 Document as applicable Configure
Team Knowledge
Transfer Plan
JMS System Update Phase I Document as applicable. Define
Security Policy
49 Tactical MCSCI with the support of Syscon will create a detailed tactical deployment plan that Validate
Deployment and will serve as the formula for cutting over to the New JMS solution. The plan will
Cut Over Plan 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 eutover progress.
50 WorkflowJAIL Delivery of out-of-the-box Workflow Release 4.0 COTS software which includes the Define
Product Delivery following:
2.1 [Release 4.0]
• Software package
• Installation documentation for all Syscon developed software
• Entity Relationship Diagram
• Data Model Dictionary
51 WorkflowJAIL Delivery of out-of-the-box Workflow Release 4.5 COTS software which includes the Define
Product Delivery following:
2.2 [Release 4.5]
• Software package
• Installation documentation for all Syscon developed software
• Entity Relationship Diagram
• Data Model Dictionary
52 UAT Ready Includes Phase 2 software modules, interfaces, software customizations and the Configure
Project Release 2.1 following:
[Release 4.5]
• Installed and Configured Software package at IvICSO site
• Workflow Product Documentation
• Installation documentation for all Syscon developed software
• Application Programming Interface (API) guide
• Online Help
• Training documentation
• Product Computer Based Training (CBT) modules
• System Configuration Documentation
• Database ERD Diagram
• Workflow Data Dictionary
53 Workflow Syscon will provide the Workflow automated test cases or test scripts for execution Configure
Automated Test along with the data input files, drivers, third-party libraries, logs and executables JAR
Cases (JAVA Archive) files. These are based on Workflow's web user interface and are
used to simulate the user experience throughout areas of the application.
54 Configured Once each portion of the system configuration is finalized, it is documented in the Configure
Software Package system configuration specification, which is delivered to MCSO with the configured
& Configuration environment.
Specification
Document
55 Test Plan A formal test document produced by Syscon detailing the scope, approach, roles and Define
responsibilities, defect management and entry and exit criteria for each specific
testing phase.
56 Customized Workflow training materials will be tailored to reflect the MCSO implementation. Configure
Training Materials

SERIAL 13139-RFP
57 Test Exit Reports The Test Exit Report will include references to the scope, testing approach, entry and Configure,
exit criteria as outlined in the Test Strategy document created during the Prepare Validate
Stage plus references to the test plans created during the Define Stage. In addition,
this report will summarize the test results including statistics on the number of
manual and automated test cases/scripts that are executed during the Configure Stage
and the outcome of those tests including a list of unresolved issues if any, This report
will be shared with MCSO at the end of the Configure Stage and Validate Stage.
58 Lessons Learned At the conclusion of each phased called out in the project schedule, lessons learned Prepare, Define,
Document shall be documented and distributed to the team. This deliverable will detail what Configure,
worked well and what did not, and will serve to inform future phases so successes Validate,
can be capitalized upon while challenges and failures can be avoided. Deploy,
Transition
59 Requirements The Requirements Traceability Matrix (RTM) is a document that links requirements Define
Traceability Matrix throughout the validation process.
60 Data Exchange Develop Data Exchange Requirements This work activity will deliver the detailed Define
Requirements data exchange mapping, designs and ESB configuration/builds including:Data field
mapping between the Workflow and MCSO Internal/Legacy systems or
partner/external stakeholder systems;Producing the Data Exchange Functional
Configuration Specifications (error handling and message coment);Transformation
Business Rules.
8. Acceptance Process
The Acceptance test process will be applied to each of Phase 1, Phase 2a, and 2b. Such process shall include three
phases: (1) the Acceptance test period ("UAT"), (2) the reliability test period, and (3) Warranty. If at any time
during the acceptance test process, the New iMS solution reveals a severity level 1 or ten (10) or more severity level
2 Defects, the process may be temporarily suspended and the Contractor will be responsible for resolving
outstanding issues. Testing will resume promptly following delivery of the remedy to error. Following five (5)
unsuccessful attempts to complete acceptance testing, the reliability test period, and final acceptance (as defined
below), the Sheriff's Office reserves the right to declare non-performance and seek remedy.
The severity and priority level 1 and 2 definitions and related acceptance criteria are set out in section 8.7
8.1. Acceptance Test Period/User Acceptance Testing (UAT)
The deliverable shall be delivered to MCSO accompanied with applicable documentation listed above for MCSO to
use in Acceptance testing. MCSO will schedule the installation of the Deliverable (and necessary hardware) within
MCSO's Delivery Platform. The Acceptance test period will begin on the earlier 01(a) ten (10) days after delivery
of the relevant materials by Contractor to MCSO, or (b) when MCSO, along with the assistance of the Contractor,
first performs Acceptance testing in accordance with the written test plan, and will end when MCSO successfully
completes the tests defined within that plan, but for greater certainty Contractor will not be liable for any delays
caused by MCSO failing to promptly and diligently implement the Acceptance test plan as agreed by the parties.
Further details for Acceptance testing are set out in Section 4.21. Unless otherwise specified in this Contract,
Acceptance will he deemed if no Defects are reported within the relevant Acceptance test period, or falls within the
mutually agreed exit criteria set forth in the applicable test plan.
8.2. Reliability Test Period
After the Go-Live Date, there will be a thirty (30) day reliability test period during which the newly installed System
will be used on the Production System and its performance monitored. Once the System is declared live and end
users begin use, the thirty (30) day reliability test period will commence. During this period, the System must
perform without any severity level I or ten (10) severity level 2 defects being reported. The foregoing is conditioned
on MCSO providing and maintaining a networking, software and technical environment that meets Contractor's
minimum requirements in the Exhibits to this Agreement or in any relevant Application Package Documentation.
Provided the Deliverables have not materially changed, reliability testing will resume promptly following delivery
and continue only for the period of time remaining in the initial 30 day reliability test period; with a five (5) day
minimum to apply. Upon successful completion of the reliability test period, the Sheriff's Office shall issue a
conditional Acceptance certificate, signifying the start of the Warranty Period

SERIAL 13139-RFP
8.3. Warranty Period
Upon completion of the Warranty Period as defined in Section 7.7.3 of the MSA, the Sheriff's Office shall issue a
Final Acceptance certificate, signifying the closure of the phase or project.
8.4. Criteria for Delivery and Acceptance of Deliverables
The Contractor shall submit all Deliverables to the MCSO Representative. All Deliverables are presented to MCSO
in the approved format (or if no such format is approved, in an industry-standard format). Documentation shall be
delivered in one electronic version with accompanying transmittal letters.
MCSO Representative shall review and validate Contractor's Deliverables product prior to Final Acceptance.
Acceptance criteria for Deliverables shall consist of the following:
• Specific Deliverables are completed as specified in this Contract and the final Deliverable has been
rendered.
• Plans, schedules, designs, documentation, and reports are approved and completed as specified in this
Contract.
• All supporting Documentation is provided and complete.
• All Deliverables are at the agreed upon acceptable level of quality as defined and agreed to in the
Quality Management Plan.
MCSO acknowledges and agrees that the Application Package, the Database, the Documentation, and all
Enhancements are licensed by Contractor as set out in Exhibit C, and that all third party materials are licensed by
Contractor as set out in Exhibit C or D, 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 MCSO's entire right thereto, subject only to the
escrow provisions set out in the MSA (section 7.4). Subject to the foregoing, MCSO shall retain unlimited rights in
any other Deliverables.
8.5. Project Deliverable Acceptance
Following delivery of each Deliverable that is not software MCSO shall have a period of ten (10) business days
("Acceptance Review Period") to test such Deliverable for Acceptance.
If, during the Acceptance Review Period, MCSO determines that the Deliverable does not meet expectations,
MCSO shall notify Contractor in writing. Contractor shall review the written notification and if the request
reasonably represents a change to the Contract, SOW or Deliverable scope, then Contractor shall initiate the Change
Control procedures.
However, if the deliverable is deficient based on (a) the requirements set out in the SOW for such deliverable, or (b)
if no such requirements are set out, Contractor shall utilize current, generally-accepted industry practices or
methodology, to provide a timeline to modify or correct the Deliverable.
Following delivery of each modification, MCSO shall again have the Acceptance Review Period to verify the
modification after which period it is deemed accepted. If no issues are raised within the Acceptance Review Period
the deliverable is deemed accepted.
If the Deliverable or any portion of the Deliverable is used on a Production System or relied upon in subsequent
project activities, then the Deliverable is deemed accepted.
When accepted, MCSO shall deliver a Deliverable Acceptance Statement therefor.

SERIAL 13139-RFP
8.6. Software Deliverable Acceptance Criteria
Following the delivery of the final Application Package Deliverable for each Phase, MCSO shall have a period of
four (4) months to conduct user acceptance testing ("UAT") to verify such Deliverable substantially performs in
accordance with this Contract (the "Acceptance Period").
If, during UAT, MCSO identifies a Defect in such Deliverable, MCSO shall notify Contractor via the Defect
tracking tool and Contractor shall provide a timeline for addressing the resolution of the Defect. Following delivery
of each Defect repair, MCSO will have ten (10) calendar days to confirm it resolves the Defect after which period
the repair is accepted, Any Defects mutually agreed as critical, or blocking VAT progress will be addressed on
priority basis. If MCSO has not identified a Defect but instead a change to the Contract, SOW or Deliverable scope,
then Contractor shall initiate the Scope Change Control procedures set out in section 9.
If the Deliverable or any portion of the Deliverable is used in the Production System then the Deliverable is deemed
accepted. Any issues found subsequent to the VAT Acceptance Period will be resolved during the Warranty Period
or, if not possible, under Support.
Defects are to be considered unique entities and cannot be attached to one another except for reporting purposes. A
resolution of a Defect may introduce new Defects. Those new Defects are considered unique new Defects and will
be managed according to their unique presentation. Acceptance of an Application Package Deliverable cascades
acceptance to all supporting project Deliverables.
8.7. Defect Management
All defects or issues raised during the acceptance testing period will be triaged by Syscon. Syscon's Defect Severity
and Priority definitions are listed below. A project Defect Review Board, comprised of both Syscon and MCSO
representatives will conduct a review of those defects raised during this period and make decisions on their
resolution plan.
The described defect severity and definition found in the table below will apply to all defects until the
completion of the Warranty Period(s) of this project and transition to support and maintenance services.
Severity Description
1 - Blocking System is unusable, major user groups are prevented from using the system. No workaround is
available.
Defects in which a requirement is not met and there is no acceptable workaround. Major module of
2 - Critical the system is unusable and/or groups of users are unable to work. Workarounds may be available.
Defects in which a requirement is not met, but which an acceptable workaround is available.
3 - High Individual functions are affected and/or individual users are prevented from completing tasks.
Defects in which the fault or limitation does not materially affect the operation of the system or in
4 - Moderate which the fault is cosmetic. Individual functions affected but individual users can still complete the
business workflow. Workarounds are available.
Defects in which the stated requirement is met to the specified Acceptance Criteria, though the
5-Minor business expectation is different. Minor fault or Cosmetic Error that has no or little impact to the
system.
9. Scope 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:
A) The party requesting the change will complete the Change Request Form found in Appendix 1:
Forms. When completing the form, the party will include a complete description of the requested

SERIAL 13139-REP
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/MCSO) project team.
B) Submit the Change Request Form to the MCSO Project Manager for logging and distribution to
the appropriate reviewers and approvers.
C) Change Requests will be reviewed by both MCSO and Contractor management teams and either
approved or rejected.
D) MCSO Project Manager will update the Change Request Log noting the approval or rejection
status.
E) All Change Request forms require the signature of the Maricopa County Office of Procurement
Services and the Contractor to be considered binding to this Agreement. Any services provided
under an un-executed Change Request are done at Contractor's risk and may not he compensated
by MCSO.
F) Non-contracted services added to the Contract, post award, shall be subject to this section 9.
Unless otherwise specified in a particular post award change request, all such deliverables will be
subject to the following percentage payments:(a) upon execution of the Change Order or related
SOW (as the case may be) forty percent (40%) of the aggregate value, (h) upon delivery of the
design/requirements document twenty percent (20%) of the aggregate fee, (e) delivery of final
code twenty-five percent (25%) of the aggregate fee, (d) sixty (60) days after final code delivery
fifteen percent (15%) of the aggregate fee.

10. Contractor Solution
10.1. Functional Requirements (Exhibit 13 Sub a)
Prefix Requirements For:
AF AFIS
AG Appeals & Grievances
BR Business Rules
CL Classification
CF Compliance
CT Court
DM Document Management
DS Data Security
Fl Administrative & Financial
GM Gang Management
GN General
HD Holds
HO Housing
ID Inmate Discipline
IN Intake
IS Inmate Services
JO Jail Operations
MV Movements
PG Programs
PR Property & Clothing
RE Release
RP Reporting
SA System Administration
SC Scheduling
SN Sentence Calculation
TA Trust Accounting/Canteen
TR Transportation
VS Visitation
WK Work Flow

SERIAL 13139-RFP
Section/ID Requirement Type Response Note Module Session
AFIS Requirements
F-AF-1 The solution shall generate an electronic feed to the Livescan units in the proper NEST 0 Roadmap Workflow Release 15 INTERFACE [INFORMATION DCI
format, including the logic to determine the proper type of feed to generate. (i.e. Type EXCHANGE HUB}
01 or Type 04).
F-AF-2 The solution shall utilize rules associated to the arresting agency ORI and/or the 0 Roadrnap Workflow Release 3.5 INTERFACE [INFORMATION DC1
existence of a valid Process Control Number (PCN) with a booking to determine EXCHANGE HUB}
whether to send a Type 01, Typo 04 or both to the Livescan units.
F-AF-3 The solution shall receive an electronic feed from the Livescan or AFIS solution to 0 Roadmap Workflow Release 3.5 INTERFACE [INFORMATION DCI
populate the solution with a temporary PCN that indicates the Livescan has begun and EXCHANGE HUI31
whether it is a Type 01 or Type 04 being processed. This feed shall update the solution
with an indication of the type of identification that is in process.
F-AF-4 The solution shall receive an electronic feed from AFIS or ACCH that is used to update I Custom Interface DCI
the following: Process Control Number (PCN) which is assigned at the Livescan, the
State Identifier (SID) number, the Arizona Record Number (ARN), FBI number and
TOC Identifier of the user that performed the identification.
F-AF-5 The solution shall use the newly updated SID, ARN or FBI number to determine if the 3 ADMISSIONS/TRANSF'ERS/REL DCI
person already exists in JMS. If they do exist, the new booking shall be automatically EASE
associated to the existing person record.
F-AF-6 The solution shall assign a unique person identifier that is used to connect all related 3 ADM1SSIONS/TRANSFERS/REL DCI
information about that person. EASE
F-AF-7 The solution shall allow for an authorized user to manually update the SID, PCN, FBI 3 ADMISSIONS/TRANSFERS/REL DC1
Number and TOC ID of the user that conducted the fingerprint identification. EASE
F-AF-8 The solution shall provide a capability to delink a booking that was incorrectly 0 Roadmap Workflow Release 3.5 ADMISSIONS/TRANSFERS/REL DC1
combined to an existing person record. EASE
F-AF-9 The solution shall provide the capability to combine two or more person records 0 Roadmap Workflow Release 3.5 MERGE/PURGE/SEAL DCI
identified as duplicates. All related data shall be combined into the kept person record, [RECORDS MGMTI
including but not limited to: bookings, charges, alias information and scars, marks and
tattoos. Duplicate scars, marks and tattoos or alias information shall be eliminated.
F-AF-I 0 The solution shall eliminate duplicate scars, marks and tattoos or alias information from 0 Roadmap Workflow Release 3.5 MERGE/PURGE/SEAL. DCI
combined person record. [RECORDS MGMT1
F-AF-11 The solution shall automatically trigger a warrant check upon the addition of a SD), 1 Custom Interface DC1
FBI number or additional alias information. See Work Flow Requirements.
AG - Appeals and Grievances Requirements
F-A0-1 The solution shall provide the ability to log and maintain the inmate's grievance, 3 REQUEST AND GRIEVANCES Detention - Hearing
Unit

SERIAL 13139-RFP
F-AG-2 The solution shall provide the ability to record the results of an investigation into a 3 REQUEST AND GRIEVANCES Detention - Hearing
grievance, including any statements by witnesses and/or staff. Unit
F-AG-3 The solution shall provide the ability to schedule the grievance hearing and record the 3 REQUEST AND GRIEVANCES Detention - Hearing
Outcome, including any decision or follow up required. Unit
F-AG-4 The solution shall provide the ability to close the case if the inmate accepts the 3 REQUEST AND GRIEVANCES Detention -Hearing
decision. Unit
F-AG-5 If the inmate does not accept the decision, he/she has 24 hours to file an institutional 3 REQUEST AND GRIEVANCES Detention - Hearing
appeal. The solution shall provide the ability to support the appeal process, including Unit
any escalation to the Bureau commander and any decision or follow up required. See
workflow and business rule requirements.
F-AG-6 If the inmate does not accept the decision, he/she may file an External Grievance 3 REQUEST AND GRIEVANCES Detention - Hearing
Appeal, which is forwarded to the Bureau Hearing Unit Commander. The solution shall Unit
support the logging and forwarding of the appeal to the Unit Commander, The
Commander can recommend stopping the grievance or forwarding to external referee.
See Workflow and Business Rule Requirements.
F-AG-7 The solution shall provide the ability to support referral to an external referee, including 3 REQUEST AND GRIEVANCES Detention - Hearing
the logging and tracking of the referral and any decision rendered. See Workflow Unit
Requirements.
F-AG-8 The solution shall provide the ability to log and maintain a disposition. 3 REQUEST AND GRIEVANCES Detention - Hearing
Unit
F-AG-9 The solution shall provide a way to associate hard copy grievances to the electronic 3 REQUEST AND GRIEVANCES Detention - Hearing
record. See Document Management Requirements. Unit
F-AG-10 The hearing officer shall have electronic access to the grievance package before and 3 REQUEST AND GRIEVANCES Detention - Hearing
during the hearing. Unit
F-AG-11 The solution shall have the ability to log and track a grievance towards an officer with 3 REQUEST AND GRIEVANCES Detention - Hearing
notification to Internal Affairs. See Workflow Requirements. Unit
F-AG-12 The solution shall provide the ability to log and track a grievance type. 3 REQUEST AND GRIEVANCES Detention - Hearing
Unit
F-AG-13 The solution shall provide the ability to create, maintain and select grievance 3 REQUEST AND GRIEVANCES Detention - Hearing
categories/types. Unit
F-AG-14 The solution shall provide the ability to search by the following, but not limited to type, 3 REQUEST AND GRIEVANCES Detention - Hearing
disposition, inmate and officer. Unit
BR - Business Rules Requirements
F-BR-I The solution shall provide the ability for an administrative user to define business rules 3 BRIvIS Non-Functional
using embedded scripts. Requirements
9Q.

SERIAL 13I39-RFP
F-BR-2 The solution shall provide the ability for an administrative user to define business rules 3 BRMS Non-Functional
using third party rules engines. Requirements
F-BR-3 The solution shall provide the ability for an administrative user to implement business 3 BRMS Non-Functional
rules using process data values. Requirements
F-BR-4 The solution shall provide the ability for an administrative user to implement business 3 BRMS Non-Functional
rules using real-time data being processed. Requirements
F-BR-5 The solution shall provide the ability for an administrative user to implement business 3 BRMS Non-Functional
rules using due dates. Requirements
Business Rules for Data Exchanges
F-BR-6 The solution shall allow business rules to manage data exchange escalation and 0 Roadmap Workflow Release 3,5 BRMS/MESSAGING Non-Functional
alerting. Requirements
F-BR-7 The solution shall have the ability to build a composite messaging process needed to 0 Roadmap Workflow Release 3,5 BRMS/MESSAGNG Non-Functional
support inter-agency messaging. Requirements
F-BR4 The solution shall have the ability to build a business rule at a minimum to verify the 0 Roadmap Workflow Release 3.5 BRMSRvIESSAGING Non-Functional
following message elements: Requirements
Message Type
Message Priority
Publication / Subscription access rules against the message contents
F-BR-9 The solution shall provide the ability to perform quality assurance in the data exchange 0 Roadmap Workflow Release 3.5 BRMS/MESSAGING Non-Functional
message prior to sending or receiving. Requirements
F-BR-10 The solution shall initiate any additional message(s) as directed by the message type 0 Roadmap Workflow Release 3.5 BRMS/MESSAGING Non-Functional
and priority rules and support. Requirements
F-BR-11 The solution shall initiate any additional message(s) as directed by the message type to 0 Roadrnap Workflow Release 3.5 BRMS/IVIESSAGING Non-Functional
multiple internal recipients. Requirements
Business Rules to Control Data Integrity
F-BR-I 2 The solution shall provide the ability for an administrative user to implement business 3 BRMS Non-Functional
controls using field definition and values. Requirements
F-BR-I 3 The solution shall provide the ability for an administrative user to implement business 3 BRMS Non-Functional
controls using defined risks function points in a workflow process_ Requirements
F-BR-14 The solution shall provide the ability for an administrative user to implement business 3 BRMS Non-Functional
controls to log and audit data altered within the solution. Requirements
F-BR-15 The solution shall provide the ability for an administrative user to implement business 3 BRMS Non-Functional
controls to log and audit data altered from data exchange. Requirements
F-BR-16 The solution shall provide the ability for an administrative user to implement business 3 BRIMS Non-Functional
controls between data fields to ensure information is captured according to compliance. Requirements
CL - Classification Requirements

SERIAL 1M39-RFP
F-CL-1 The solution shall electronically store the results of local, national and court criminal 3 ASSESSMENTS & Classification
history checks associated to an inmate. CLASSIFICATION
F-CL-2 The solution shall provide the capability to configure interview questions and may be 3 ASSESSMENTS & Classification
able to perform automated scoring and classification associated to the answers of the CLASSIFICATION
questions.
F-CL-3 The solution shall have an override capability for any type of automated classification 3 ASSESSMENTS & Classification
This override should be able to be controlled based on the user's role in the solution. CLASSIFICATION
F-CL-4 This classification override shall be controlled based on the user's role in the solution. 3 ASSESSMENTS & Classification
CLASSIFICATION
F-CL-5 The solution shall support work flow requirements when inmates are referred for a 3 ASSESSMENTS & Classification
psych evaluation. See Workflow Requirements. CLASSIFICATION
F-CL-6 The solution shall store a three (3) element proxy score associated to an inmate 1 GAPDuring ASSESSMENTS & Classification
separately and invoke a formulated calculation to display the 3 elements along with the CLASSIFICATION
calculated Recidivism Risk score, while allowing for additional elements in the future.
: .-: • :.• '' . : .. . , -: -2
erimittal history, inciudiag age at first
providing tho ability to gonorato a
proxy scoro for an inmate. If Mir: gap is
Workflow Release 3.5 Project
Release 1.2Line 38in Attachment A
• , - I , : -
..,,,.., :-.. : :. l• • • li,
F-CL-7 The solution shall allow for configuration of the MCSO levels of classification. 3 ASSESSMENTS & Classification
CLASSIFICATION
F-CL-8 The solution shall support a workflow process for inmates that are being added to or 0 Roadmap Workflow Release 3.0 CASE MANAGEMENT Classification
removed from special housing, such as "Close Custody," and "Administrative
Segregation." This workflow would include review and approval/decline by the special
review committee. See Work-flow Requirements.
F-CL-9 The solution shall maintain a list of facilities and which classifications are allowed at 3 ASSESSMENTS & Classification
each facility. CLASSIFICATION
F-CL-10 The solution shall provide the number of available beds at each facility based on 3 ASSESSMENTS & Classification
classification levels. CLASSIFICATION

SERIAL 13139-RFP
F-CL-11 The solution shall support assignment of an inmate to a facility. 3 ASSESSMENTS & Classification
CLASSIFICATION
F-CL- 2 The solution shall automatically alert the user on the screen if the assignment exceeds 3 ASSESSMENTS & Classification
capacity/availability for the facility, and shall allow for an override to retain the CLASSIFICATION
assignment,
F-CL-13 The solution may automatically recommend a facility based on classification and 0 Roadmap Workflow Release 3.0 ASSESSMENTS & Classification
availability but shall allow for overrides to the facility. CLASSIFICATION
F-CL-14 The solution shall be able to support the entry of comments on an inmate. These 3 ASSESSMENTS & Classification
comments should be able to be categorized by subjects such as, but not limited to Gang CLASSIFICATION
Affiliation, Classification, Man Warnings, Escapes, Assaults on Inmates, Assaults on
Officers and General.
F-CL-I 5 Comments on the inmate (F-CL-13) shall be searchable, e.g., to find all current inmates 3 ASSESSMENTS & Classification
with a specific gang affiliation, classification, man warning, etc. CLASSIFICATION
F-CL-16 The solution shall support automated triggers for reviewing an inmate's classification to 3 ASSESSMENTS & Classification
determine if it should be modified. These triggers include but are not limited to: date of CLASSIFICATION
last classification, new Identification information, Disciplinary Action Report, new
charges to an inmate, communications from an inmate (such as a Tank Order) and
requests from Correctional Health Services. See Workflow Requirements.
F-CI.-17 The solution shall support automated messaging and workflow with transportation and 0 Roadmap Workflow Release 3.5 ASSESSMENTS & Classification
housing when inmates are to be moved within a current facility or to a new detention CLASSIFICATION
center. See Workflow Requirements,
F-CL-18 The solution may provide the ability to capture an electronic signature for an inmate. 3 ASSESSMENTS & Classification
CLASSIFICATION
F-CF-1 The solution shall track and maintain Legal Liaison requests by date, requestor, type, 3 REQUEST AND GRIEVANCES Document
and status. Management
F-CP-2 The solution shall assign a unique tracking number for each new request. 3 REQUEST AND GRIEVANCES Document
Management
F-CP-3 The solution shall be able to associate correspondence and other relevant documents to 3 REQUEST AND GRIEVANCES Document
the unique tracking number. Management
F-C?.4 The solution may provide a way to electronically request and/or alert other MCSO 3 MESSAGING Document
units when information is being requested from the Compliance Division. See Management
workflow Requirements.
F-CP-5 The solution shall provide the ability to enter and maintain court names and associated 3 COURT ORDERS/LEGAL Document
codes. DOCUMENTS Management

SERIAL 13139-RFP
F-CP-6 The solution shall provide consolidated booking and release date information. 3 REPORTING/13I/WORD Document
PROCESSING Management
F-CP-7 The solution shall provide the ability to redact information digitally, 0 Roadmap Workflow Release 3.0 DOCUMENT MANAGEMENT Document
Management
F-CF-S The solution shall provide the ability to log a request response. 0 Roadmap Workflow Release 3.0 DOCUMENT MANAGEMENT Document
Management
F-CP-9 The solution shall provide the ability for the Compliance Division to generate reports. 3 REPORTING/BYWORD Document
See Reporting Requirements. PROCESSING Management
F-CF-I 0 The solution shalt provide the ability to provide a statement of certification for 0 Roadmap Workflow Release 3,0 DOCUMENT MANAGEMENT Document
documents and reports. Management
Court Record Processing
F-CT- I The solution shall provide the ability for an authorized user to process imported case 1 Custom Interface COURT ORDERS/LEGAL DCI
and charge data from the court's case management solution. DOCUMENTS
F-CT-2 The solution shall provide the ability to inquire on an inmate's court record and display 3 COURT ORDERS/LEGAL SIMS
the inmate's name, court information, and charge information. DOCUMENTS
F-CT-3 The solution shall provide the ability to inquire on an inmate's court record based on 3 COURT ORDERS/LEGAL SIMS
booking number or case number. DOCUMENTS
F-CT-4 The solution shall provide the ability to modify case numbers. 3 COURT ORDERS/LEGAL SIMS
DOCUMENTS
F.-CT-5 The solution shall provide the ability to modify, delete, and add charges to an inmate's 3 COURT ORDERS/LEGAL SIMS
individual case(s) based on role and security privileges. DOCUMENTS
F-CT-6 The solution shall provide the ability to add or modify court actions for each individual 3 COURT ORDERS/LEGAL SIMS
ease and the individual charges assigned to the case. DOCUMENTS
F-CT-7 The solution shall provide the ability to update charge actions for all assigned charges 3 COURT ORDERS/LEGAL SIMS
individually or cumulatively. DOCUMENTS
F-CT-8 The solution shall provide the ability to maintain a historical record of all modifications 0 Roadmap Workflow Release 2.5 COURT ORDERS/LEGAL SIMS
to inmate case and charge records, DOCUMENTS
F-CT-9 The solution shall provide the ability for an administrative user to add, change, delete 3 COURT ORDERS/LEGAL SIMS
and rearrange the court schedule. See Scheduling Requirements. DOCUMENTS
F-CT-I0 The solution shall provide the ability to maintain inmate's court record for the following 0 Roadmap Workflow Release 2.5 COURT ORDERS/LEGAL SIMS
but not limited to: work release, work furlough, or weekend programs. DOCUMENTS
(?

SERIAL 13139-REP
F-CT-1 I The solution shall provide the ability to record the work program for a sentenced 0 Row,!map Workflow Release 2,5 COURT ORDERS/LEGAL SIMS
inmate for the following but not limited to: DOCUMENTS
Assigned reporting days (consecutive and concurrent)
Number of weekends sentenced
Prosecutor
Sentencing Judge
F-CT-I2 The solution shall provide the ability to maintain a record of the following but not 3 COURT ORDERS/LEGAL SINIS
limited to: inmate related court proceedings, including the time, date, place, type of DOCUMENTS
proceeding, and the results.
F-CT-13 The solution shall provide the ability to enter the following but not limited to: court 3 COURT ORDERS/LEGAL SIMS
orders to include the order type, date received, case number, free text notes field, and DOCUMENTS
approval or denial of the order.
F-CT-14 The solution shall provide the ability to attach a court order to an inmate record (PDF, 3 COURT ORDERS/LEGAL SIMS
scanned image, etc.). See Document Management Requirements. DOCUMENTS
F-CT-15 The solution shall provide the ability to scan court paperwork and attach to inmate's 3 COURT ORDERS/LEGAL SIMS
booking record. See Document Management Requirements. DOCUMENTS
F-CT-I 6 The solution shall provide the ability to report the number of days an inmate has served 3 COURT ORDERS/LEGAL SIMS
in custody based on the following but not limited to: court case number, booking DOCUMENTS
number, housing location, and other user defined criteria. See Reporting Requirements.
F-CT-I 7 The solution shall provide the ability to enter and download court date(s) for multiple a Custom Interface/Enhancement COURT ORDERS/LEGAL srms
inmates simultaneously on one screen. Line 1 DOCUMENTS
in Attachment A Cost Proposal
F-CT-18 The solution shall maintain inmate prosecution case and charge information, but is not 1 Enhancement COURT ORDERS/LEGAL SIMS
limited to, the following: Prosecuting Agency ORL Prosecuting Agency Case Number, Line 2 DOCUMENTS
Prosecuting Attorney Bar Number and Name, Charges Declined/Not Filed, Date in Attachment A Cost Proposal
Charges Declined/Not Filed, ARS, Charges Added by Prosecutor, A.R.S. Charge
Type (Eel, Misd) for Charges Added by Prosecutor, Count Sequence Number for
Charges Added by Prosecutor, Preparatory Offense Code, and Date of Occurrence or
Charge Date or Charge From Date.
F-CT-19 The solution shall maintain inmate court case and charge information, but is not limited 3 COURT ORDERS/LEGAL SIMS
to, the following: Other Court Case Number, Justice of the Peace (JP) Court Case DOCUMENTS
Number, Superior Court Case Number, Sentence Status, Disposition AR. S.,
Disposition Type (AC, CD, GO etc), Disposition A.R.S. Count Sequence Number,
Date of Disposition ARS, ORI of Court Submitting Disposition, Length of
Confinement, Type of Confinement, Length of Probation, County Supervising
Probation.
Court Calendar Processing
F-CT-20 The solution shall provide the ability to inquire on an inmate court case and associated 3 COURT ORDERS/LEGAL SIMS / Scheduling
scheduling information. See Scheduling Requirements. DOCUMENTS
F-CT-21 The solution shall provide the ability to schedule an inmate court case and identify and 1 Enhancement to prioritize by court COURT ORDERS/LEGAL SIN1S / Scheduling
resolve scheduling conflicts by court prioritization. See Scheduling Requirements SC- included as part of P-CT-23 DOCUMENTS
5,

SERIAL 131394FP
F-CT-22 The solution shall provide the ability to produce an on-line list of inmates scheduled to 3 COURT ORDERS/LEGAL SIMS / Scheduling
appear in court for a given day and any scheduling conflicts. Conflicts include multiple DOCUMENTS
courtrooms for the same time, medical appointments, and other scheduled
appointments. See Scheduling Requirements.
F-CT-23 The solution shall provide the ability to produce a court schedule which includes but is 1 Enhancement for court cell location COURT ORDERS/LEGAL SIMS / Scheduling
not limited to: inmate's name, assigned cell location at court building, case number, DOCUMENTS
court room, court time, and judge, most serious charge, special needs, wheelchairs, Line 3
keep-aways with same court date and man warnings. See Scheduling Requirements, in Attachment A Cost Proposal
F-CT-24 The solution shall provide the ability to produce a daily court schedules with sorting 3 COURT ORDERS/LEGAL SEvIS / Scheduling
capabilities including but not limited to: by cell assignment, court room, court time, DOCUMENTS
booking number, last name and man warnings. Set Scheduling Requirements and
Reporting Requirements.
F-CT-25 The solution shall provide the ability to print and display schedules that include but are 3 COURT ORDERS/LEGAL SIMS I Scheduling
not limited to: a warning when inmates with man warnings and active keep-away DOCUMENTS
notations are scheduled for court.
F-CT-26 The solution shall provide the ability for an administrative user to control the following 3 - COURT ORDERS/LEGAL SIMS
tables, including but not limited to: courtroom, time, and judge. DOCUMENTS
F-CT-27 The solution shall provide a work program display with the following information, 3 PROGRAMS & SERVICES SIMS
including but not limited to: the inmate's booking number, housing facility, housing
unit, name, date of birth and an optional pull down photo ID
F-CT-28 The solution shall provide the ability to print a date range work release schedule. See 0 Roadmap Workflow Release 2.5 PROGRAMS & SERVICES SIMS
Reporting Requirements.
Initial Appearance Processing
F-CT-29 The solution shall provide the ability to dynamically create and update the initial 3 COURT ORDERS/LEGAL SIMS
appearance list based on new bookings and subjects that bond out, DOCUMENTS
F-CT-30 The solution shall provide the ability to place an inmate into the next day's initial 3 COURT ORDERS/LEGAL SIMS
appearance if they are booked after the designated initial appearance court time. DOCUMENTS
F-CT-31 The solution shall provide the ability to manually adjust the order for initial appearance 3 COURT ORDERS/LEGAL SIMS
based on case notoriety or severity of charges. DOCUMENTS
F-CT-32 The solution shall provide the ability to electronically exchange the court event I Custom Interface COURT ORDERS/LEGAL SIMS
information. This data exchange includes but is not limited to the following data DOCUMENTS
elements: Next Court Date, Page 2's, Amended Orders, and Bond amount on a per-
charge basis.
Bail Bond
F-CT-33 The solution shall provide an authorized user the ability to authorize payment of bail 1 EnhancementLine S in Attachment A COURT ORDERS/LEGAL SIMS
bond money from the inmate's trust account. Cost Proposal DOCUMENTS

SERIAL 13139-RFP
F-CT-34 The solution shall provide an authorized user the ability to record the bond type 3 COURT ORDERS/LEGAL S IMS
including but not limited to: surety bond, cash bond, inmate cash bond, self bond. DOCUMENTS
F-CT-35 The solution shall be capable of processing an unlimited number payments of bail 3 COURT ORDERS/LEGAL SIMS
bonds per shift. DOCUMENTS
F-CT-36 The solution shall determine if the inmate has sufficient funds by comparing the I Enhancement COURT ORDERS/LEGAL SIMS
inmate's trust account with the bail bond amount. DOCUMENTS
Line 6
in Attachment A Cost Proposal
F-CT-37 If the inmate wants to self-bond and there are sufficient funds available, the solution I Enhancement COURT ORDERS/LEGAL SIMS
shall deduct the bail bond amount from the inmates trust thud account and adjust the DOCUMENTS
inmate's bond paid amount. included as part of F-CT-36
F-CT-38 If there are not sufficient funds available the solution shall alert the user on the screen. 1 Enhancement COURT ORDERS/LEGAL SIMS
DOCUMENTS
included as part of F-CT-36
F-CT-39 The solution shall allow for entry of bail amounts from two or more funding sources. I Enhancement COURT ORDERS/LEGAL SIMS
DOCUMENTS
Line 7
in Attachment A Cost Proposal
F-CT-40 The solution shall be capable of printing a report of the inmates that have paid their bail 0 Roadmap Workflow Release 2.5 REPORTING/BYWORD SIMS / Reporting
bond to all Courts for that day. PROCESSING
F-CT-4I The solution shall produce an inmate self-bond report that will include the inmates 0 Roadrnap Workflow Release 2.5 REPORTING/BYWORD SIMS / Reporting
booking no., name, charging county, and the bail bond amount posted. This will be PROCESSING
used to verify the bond amount and reconcile with the court clerks.
F-CT-42 The solution shall produce a bond receipt form with all required data and the designated 0 Roadmap Workflow Release 2.5 REPORTING/BYWORD S IMS / Reporting
number of copies, PROCESSING
F-CT-43 The solution shall produce a returned bond receipt form with all required data and the 0 Roadmap Workflow Release 2.5 REPORTING/131/WORD SIMS I Reporting
designated number of copies. PROCESSING
F-CT-44 The solution shall produce a printable bond audit trail for all activity for a specific day, 3 REPORTING/BYWORD SIMS / Reporting
all activity for a date range, or all activity for a specific inmate. See Reporting PROCESSING
Requirements.

SERIAL 13139-RFP
F-CT-45 The solution shall provide an authorized user the ability to void all bond types, 1 GAP This requirement was discussed COURT ORDERS/LEGAL SINIS
during the SIMS session of the gap DOCUMENTS
analysis. The system currently does not
automatically return funds to the
inmate trust account when a bond is
voided. Originally it was anticipated
that this requirement meant that an
authorized user could correct mistakes
in data enny. If there is a voiding of a
bail bond that took funds from the
inmates account then it is assumed that
the money would have to automatically
be returned to the inmates trust
account. This functional need has not
been required by any client previously
and was therefore not on the roadmap.
Syscon has agreed to split the cost of
this gap enhancement to incorporate it
in to the product roadmap. The ability
to update the inmate trust account in
the event of a voided bail bond will be
available via data entry if this gap does
not get approved. This gap, if
approved, is tentatively scheduled for
Workflow Release 4,5 - Project
Release 2.2Line 39in Attachment A
Cost Proposal
F-CT-46 The solution shall provide an authorized user the ability to authorize an in-custody or 0 Roacirnap Workflow Release 2.5 COURT ORDERS/LEGAL SIMS
not-in-custody bond surrender, a bond paid prior to IA, as well as initiate IA Court DOCUMENTS
notification.
F-CT 17 Enhancement GOURT-OR,DERSEGAL
DOCUMENTS
Line 8
F-CT-48 The solution shall calculate the required bail amount that includes bonding fees and 0 Roadmap Workflow Release 2.5 COURT ORDERS/LEGAL SIMS
dollar for days. [NOTE: The courts allow an inmate to do jail time instead of making DOCUMENTS
payments for a fine, known as "dollar for days."]
F-CT-49 The solution shall provide a report that will include the inmate's booking number, 0 Roadmap Workflow Release 2.5 COURT ORDERS/LEGAL SEMS
name, and amount of bond fees paid for the inmates that have paid their bond fees for DOCUMENTS
that day. A total amount of bond fees paid will also be printed on the report. See
Reporting Requirements.
F-CT-50 The solution shall provide an override for bonding fees restricted to authorized user Enhancement COURT ORDERS/LEGAL SIMS
with a text field for additional comments. DOCUMENTS
Line 9
in Attachment A Cost Proposal
F-CT-5I The solution shall provide a bond audit trail that also includes the add Mona! comments I 3 COURT ORDERS/LEGAL SIMS
text field. DOCUMENTS

SERIAL 13139-RFP
F-CT-52 The solution shall record all court fine payment processing information required for an 0 Roadmap Workflow Release 2.5 COURT ORDERS/LEGAL SIMS
inmate release. DOCUMENTS
F-CT-53 The solution shall record all child support payment processing information required for I Custom Interface DC1
inmate release from Clerk of Court data exchange.
Release Processing
F-CT-54 The solution shall provide the ability to create a pre-facility release checklist, 3 ADNIISSION/TRANSFER/RELEA Release / SIMS
automatically indicate steps completed for an inmate and ability to cancel and void. SE
See Workflow Requirements.
F-CT-55 The solution shall provide the ability to calculate release time based on state, court and I Enhancement SENTENCE/TIME SIMS
county requirements. ACCOUNTING
Line 10
in Attachment A Cost Proposal
See CT-87, SN-5, SN-8, SN-15, SN-16
F-CT-56 The solution may provide the ability to review release date from a inmate Kiosk. 1 Custom Interface N/A
F-CT-57 The solution shall provide the ability to generate a report of inmates with sentence end 3 REPORTING/BYWORD SIMS / Reporting
dates during a specified period. See Reporting Requirements. PROCESSING
F-CT-58 The solution shall provide the ability to filter a release report based on inmate type and 3 REPORTING/BI/WORD STMS / Repotting
highest charge type. See Reporting Requirements. PROCESSING
F-CT-59 The solution shall provide the ability to automate the process of a subject release via a I Custom Interface DCI
promise to appear (PTA) including complete warrant check. See Workflow
Requirements.
F.-CT-60 The solution shall provide the ability to maintain a list of subjects released on PTA and a Based on our discussions with SIMS it ADMISSIOWTRANSFER/RELEA SIMS
was agreed that this requirement could SE
be removed. Typically the agency .
doesn't collect further information
once an inmate is released.
F-CT-61 3 See above EVENT LOGS SIMS
F-CT-62 The solution shall provide the ability to record pending charges information. 3 COURT ORDERS/LEGAL SIMS
DOCUMENTS
F-CT-63 The solution shall provide the ability to maintain a list of out-of-county arraignment 1 Enhancement COURT ORDERS/LEGAL SIMS
dates and times, to be used when releasing a subject on his/her own recognizance for an DOCUMENTS
out-of-county warrant. Line 11
in Attachment A Cast Proposal
3 Enhancement 344,48.
his/her-own recognizance for out of county warrants. DOCUMENTS

SERIAL 13139-RIP
F-CT-65 The solution may provide the ability to record details on telephone communication 3 COURT ORDERS/LEGAL SIMS
regarding out-of-county warrants (i.e., record details of the requesting officer and the DOCUMENTS
court date provided).
F-CT-66 The proposed solution shall provide the ability to interface with the court solution to 1 Custom Interface DCI
send release activity information in real time.
F-CT-67 The proposed solution shall provide the ability to interface with the State solution to I Custom Interface DCI
receive notice of inmates about to complete their sentences.
F-CT-68 ' The solution shall provide the ability to specify the release type. 3 ADM1SSION/TRA.NSFER/RELEA Release
SE
F-CT-69 The solution shall provide the ability to cancel an inmate physical release and generate 3 ADMISSION/TRANSFER/RELEA Release / Workflow
workflows to re-process inmate. See Workflow Requirements. SE
F-CT-70 The solution shall provide the ability to integrate the processes of the release 3 ADMISSION/TRANSFER/RELEA Release / Workflow
authorization and scheduling, as well as synchronize (such as clear the inmate SE
calendar). See Workflow and Scheduling Requirements.
F-CT-71 The solution shall provide the ability to record court order of the inmate transfers to 3 COURT ORDERS/LEGAL SIMS
other institutions or to other agencies, including inactives (inmate temporarily out of DOCUMENTS
custody). See Billing Requirements.
Work Program Administration
F-CT-72 The solution shall provide the ability to document and prioritize internal/external work 0 Roadmap Workflow Release 2.5 PROGRAMS & SERVICES SIMS
project requests.
F-CT-73 The solution shall provide the ability to create and store work programs. 0 Roadmap Workflow Release 2.5 PROGRAMS & SERVICES MIS
F-CT-74 The solution shall provide the ability to schedule the work program including programs 0 Roachuap Workflow Release 2.5 PROGRAMS & SERVICES SlIvIS
that do not have a specified "end date."
F-CT-75 The solution may provide the ability for the integration of a third party work program 0 Roadmap Workflow Release 2.5 PROGRAMS & SERVICES srms
application.
F-CT-76 The solution shall provide a list of work inmate applicants for review and assignment. 0 Roachnap Workflow Release 2.5 PROGRAMS & SERVICES SIMS
F-CT-77 The solution shall provide the ability to assign an individual inmate or groups of 0 Roadmap Workflow Release 2.5 PROGRAMS & SERVICES SIMS
inmates to a work program. See Scheduling Requirements.
F-CT-78 The solution shall provide a waiting list for a work assignment when the assignment is 0 Roadrnap Workflow Release 2.5 PROGRAMS & SERVICES SIMS
fully staffed.
F-CT-79 The solution shall provide the ability to flag inmates who do not meet work eligibility 0 Roadrnap Workflow Release 2.5 PROGRAMS & SERVICES SIMS
criteria.

SERIAL 13139-RFP
F-CT-80 The solution shall provide the ability to record the user responsible for scheduling the 0 Roadmap Workflow Release 2.5 PROGRAMS & SERVICES SIMS
inmates work for the day. See Workflow Requirements.
F-CT-81 The solution shall integrate with classification information that facilitates the 0 Roadinap Workflow Release 2.5 PROGRAMS & SERVICES SIMS
assignment of an inmate to the most appropriate work programs.
F-CT-82 The solution shall have capability to produce a list of inmates with work program- Roadrnap Workflow Release 2.5 PROGRAMS & SERVICES SIMS
related skill sets, e.g., kitchen, landscaping, janitorial, etc.
Actually capturing inmate skills and
matching them to work programs was
removed from this requirement. There
are three codes that are currently used
to define an inmate's eligibility for
work Cie. E (On Facility), 0 (No Food
Handling), K (Kitchen Cleared)).
MCSO needs the ability to store these
codes against an inmate
F-CT-83 The solution shall provide the ability to capture work program coordinator phone and 0 Roadmap Workflow Release 2.5 PROGRAMS & SERVICES SIMS
email contact information, as well as program staff contact, eligibility and applicable
updates information.
F-CT-84 The solution shall track any housing change required as a condition of work 0 Roadmap Workflow Release 2.5 PROGRAMS & SERVICES SIMS
participation.
F-CT-85 The solution shall provide an electronic scheduling solution to include work programs 0 Roadmap Workflow Release 2.5 PROGRAMS & SERVICES SIMS
within a facility or outside of a facility, telephonic hearings with reminders. See
Scheduling Requirements and Business Rules Requirements.
F-CT-86 The solution shall provide the ability to track inmate movement during a work program. 0 Roach-nap Workflow Release 2.5 PROGRAMS & SERVICES SlivIS
F-CT-87 The solution shall compute an inmate pay and/or good time balance for inmate work I Enhancement - included as part of PROGRAMS & SERVICES SIMS
performed. custom Sentence Calculation F-CT-55
This requirement was refined during
discussions with SlivIS to provide
automatic adjustment of work credit
based on actual attendance of work
performed. There currently is no pay
for inmates who perform work.
F-CT-88 The solution shall record canteen discount for an inmate participating in a designated I PROGRAMS & SERVICES SIIVIS
program. This is included in GAP defined for F-
TA-20
F-CT-89 The solution shall integrate work programs and movement with the facility count 0 Roadmap Workflow Release 2.5 PROGRAMS & SERVICES SIMS
function.

SERIAL 13139-REP
F-CT-90 The solution may provide the ability for a work program display using the inmate's ID Readmit) Workflow Release 2.5 PROGRAMS & SERVICES SIMS
and to include the following but not limited to: The inmate's employer name and
address
Scheduled work hours
Scheduled return days and times
Payment rate (if option is used by facility)
Calculated jail remittance rate (if payment method is used by facility)
Current payment status (if payment method is used by facility)
Inmate Record Processing
F-CT-91 The solution shall provide the ability to flag an inmate booking record as sealed and/or 3 MERGE/PURGE/SEAL Non-Functional
expunged. [RECORDS lvIGMT1 Requirements
F-CT-92 The solution shall provide the ability to designate which users are able to unseal a 3 MERGE/PURGE/SEAL Non-Functional
record, [RECORDS MGMT] Requirements
F-CT-93 The solution shall provide the ability to record the entry of a seal or unseal action on the I Enhancement MERGE/PURGE/SEAL Non-Functional
inmate's record and include the following but not limited to: [RECORDS MGMTI Requirements
Current Date/Time (timestatnp from the solution) Line 13
Staff or Judge authorizing action in Attachment A Cost Proposal
Case Number
Action Reason
Preservation of Evidence
F-CT-94 The solution shall provide the ability to send an electronic message to a designated user 3 MESSAGING/MOVEMENTS Non-Functional
(such as the probation officer, county attorney, judge, and jail administrator) when a Requirements /
work program sentence inmate fails to report to the facility while serving their SIMS
sentence. See Workflow Requirements.
F-CT-95 The solution shall provide the ability to inquire on the inmate work release schedules. 0 Roadmap Workflow Release 2.5 PROGRAMS & SERVICES SEAS
See Scheduling Requirements.
E-CT-96 The solution shall provide the ability to update the inmate work release schedules. See 0 Roadrnap Workflow Release 2.5 PROGRAMS & SERVICES SIMS
Scheduling Requirements.
F-CT-97 The solution shall provide the ability to record DNA collection details including but not 0 Roadmap Workflow Release 2.5 CASE MANAGEMENT SIMS
limited to: the dateitime of collection, the user member collecting the sample, and the
date the sample is sent to the state crime lab. See Workflow Requirements.
F-CT-9S The solution may provide the ability to export release and victim information to a I MSCO chose workaround option 1 for N/A
notification system. Phase 1 of the go-live. Syscon
confirms that the victim data entered in
the interim solution will remain
available in the original location in the
system once the final solution is
implemented (e.g. the case notes will
not be translated to the victim module
data points).
See F-RE-9
mantic:tom Syseon's response was that
is currently in use as MCSO handles
all victim notifications themselves.

SERIAL 13139-REP
Appriss (VINE). Further information
about VINE may be found at
.rv.wwrappFiss7seim4ine
Tentative schedule for Option 1 is
Workflow rause. 3.5 Project Release
44
the impact of bringing full victims
capabilities in to Phase
original VINE interface cost, as well as
ESBEE3434:114E-13ERA
w1.14-be-neeeasaPf,
Line 40
in Attachment A Cost Proposal
DM - DOCUMENT MANAGEMENT Requirements
F-DM- The solution shall provide the ability for a user to redact an inmate's documents, DOCUMENT MANAOEMENT
manage related redacted documents and export redacted documents. (Documents Third Costly Requirements
represent all word processor, spreadsheet, presentation, e-mails and multimedia file Party
types)

SERIAL 13139-RFP
F-DM-2 The solution shall provide the ability for a user to attach an inmates documents, 3 REPORTING/DI/WORD
manage related documents and export documents. (Documents represent all word PROCESSING
processor, spreadsheet, presentation, PDF's, e-mails and multimedia file types)
F-DM-3 The solution shall provide the ability for an administrator to export with redaction by 0 Roadmap Workflow Release 3,5 DOCUMENT MANAGEMENT
using a public record template.
F-DM-4 The solution shall provide the ability to access a user defined form list based on role. 0 Third Party REPORTING/I31/WORD
PROCESSING
F-DM-5 The solution shall provide the ability for an administrative user to archive and mark 0 Roadmap Workflow Release 3.5 DOCUMENT MANAGEMENT
'read only "specific judicial/detention/commitment related documents.
F-DM-5 The solution shall provide the ability to search documents by the full-text. 0 Roadmap Workflow Release 3.5 DOCUMENT MANAGEMENT
F-DM-7 The solution shall provide the ability for a user to view all inmates 3 REPORTING/BYWORD
judicial/detention/commitments (from the inmate profile), unless it is a sealed PROCESSING
judicial/detention/commitment.
F-DM-8 The solution shall provide the ability for a user to attach documents to a specific 3 REPORTING/BYWORD
judicial/detention/commitment/writ file at the conclusion of document generation with PROCESSING
date, time, document type, and creator.
F-DM-9 The solution shall provide the ability for a user to select a 3 REPORTING/BYWORD
judicial/detention/commitment/public record template and create a series of documents PROCESSING
contained within the solution to distribute to appropriate parties via e-mail, e filing, or
printing.
F-DM-1 0 The solution shall provide the ability for a user to create, define and print forms with 3 REPORTING/BYWORD
field placeholder insertion using the solution (mail merge). Forms produced in the PROCESSING
following categories: Inmate Forms (General forms to inmates about their
judicial/detention/commitment) - Inmate Summary Information Forms (requires ability
to produce information about the inmate from the database solution) - Other party
forms (e.g. tank order. Requires ability to specify types of other parties to receive the
form.) - Agency Forms (forms to State and County agencies) - Court Forms (forms to
be filed with the court)
F-DM-1 l The solution shall provide the ability for an administrative user to generate both 3 .REPORTING/BI/WORD
'Standard' forms and "User-Specific" forms. Allow the staff to define standard forms PROCESSING
for all users. Allow users to copy and modify these forms and to create forms of their
own.
F-DM-I2 The solution shall provide the ability for an administrative user to manage and organize 3 REPORTING/BYWORD
electronic content classifications such as judicial/detention/commitments. PROCESSING
F-DM-I 3 The solution shall provide the ability for an administrative user to enter who, what, 0 Roadmap Workflow Release 3.5 DOCUMENT MANAGEMENT
where, barcodes and when file information into the solution and later retrieve the file
information.
F-DM-I4 The solution shall provide the ability for an administrative user to design and produce 3 REPORTING/BYWORD
labels with multidimensional barcode(s) for all physical file folder(s). PROCESSING

SERIAL 13139-RFP
F-DM-I5 The solution shall provide the ability for an administrative user to produce a 3 REPORTING/BYWORD
multidimensional barcode for each physical storage box used in offsite storage tracking. PROCESSING
F-DM-I 6 The solution shall provide the ability for an administrative user to produce and attach 0 Third Party DOCUMENT MANAGEMENT
multiple file labels to a multi-volume judicial/detention/commitment denoting the
proper tracking of file folders.
F-DM-17 The solution shall provide the ability for an administrative user to enter the physical 0 Third Party DOCUMENT MANAGEMENT
judicial/detention/commitment file (by box number, etc.) into the solution and later
retrieve the physical judicial/detention/commitment file information.
F-DM-18 The solution shall provide the ability for an administrative/authorized user to delete or 3 MERGE/PURGE/SEAL
seal selected documents associated to a selected inmates [RECORDS MGMT]
judicial/detention/commitments.
F-DM-19 . . — -- 0 During gap analysis it was decided to DOCUMENT MANAGEMENT
have all data online and have a
separate reporting database which is a
snapshot of the OLTP database.
Roadmap Workflow Release 3.5
F-DM-20 The solution shall provide the ability to scan documents to be managed within the 3 DOCUMENT MANAGEMENT
DOCUMENT MANAGEMENT module.
F-DM-21 The solution shall provide the ability to house and retrieve all warrants in the DOCUMENT MANAGEMENT
DOCUMENT MANAGEMENT module.
Check-in/Check-out
F-DM-22 The solution shall provide the ability for users to check-in/check-out documents. 0 Third Party DOCUMENT MANAGEMENT
F-DM-23 The solution shall provide the ability for administrators to lock documents to prevent 0 Third Party ' DOCUMENT MANAGEMENT
further changes.
F-DM-24 The solution shall provide the ability for users to display all versions of documents, 0 Third Party DOCUMENT MANAGEMENT
including amended, that are available for check-out.
F-DM-25 The solution shall provide the ability for users to download a particular document Third Party DOCUMENT MANAGEMENT
version.
F-DM-26 The solution shall provide the ability for users to add comments to any particular 0 Third Party DOCUMENT MANAGEMENT
document version upon check-in,
F-DM-27 The solution shall provide the ability for users to use a 3rd-party document version 0 Third Party DOCUMENT MANAGEMENT
control software.

SERIAL 13139-RFP
F-DM-28 The solution shall provide the ability for administrators to restrict access to documents 0 Third Party SECURITY MODEL/LDAP
from either a single user or groups of users .
F-DM-29 The solution shall provide the ability for administrators to place a legal hold on 0 Third Party REPORTING/BI/WORD
documents which allows an authorized user view privileges without modification (no PROCESSING
purge/archive until the legal hold is released).
DS - Data Security Requirements
F-DS-I The solution shall provide an AUDIT trail of all activity in the solution. This AUDIT I GAPThis AUDIT
trail will log the T Address, Routing Indicator, TOC ID, Operator ID, date, and time requirement was discussed during the
for all transactions and/or data entered into or data taken out of the solution. The technical requirements session. To
AUDIT shall include inquiries and views as well as adds changes or deletes, satisfy the requirement Syscon will
extend Workflow to allow Alternate
IDs (such as TOC JD) to be configured
at the user level (with an expiry date).
Additionally, we will provide the
ability to configure which Alternate
IDs get logged to the Audit record.
Syscon will also extend Workflow
audit functionality to log the ID of the
device that did the transaction. MCSO
confirmed that digital certificates could
be used in place of FP Addresses.This
gap is tentatively scheduled, upon
approval, for Workflow Release 4.0 —
Project Release 2.1Line 41 in
Attachment A Cost Proposal See F-
DS-8
F-DS-2 The solution shall provide the ability to generate/print the AUDIT trail of all solution 3 AUDIT
transactions based on User ID/personnel information.
F-DS-3 The solution shall provide the ability to log date, time, and user ID associated with file 3 AUDIT
maintenance transactions (e.g., create, read, add, update, delete transactions).
F-DS-4 The solution shall provide the ability to log date, time, and user ID associated with any 0 Roadmap Workflow Release 3.5 AUDIT
report sent to a printer.
F-DS-5 The solution shall provide the ability to log date, time, and user ID associated with any 0 Roadmap Workflow Release 3.5 AUDIT
message sent or received through the solution.
F-DS-6 The solution shall provide the ability to log date, time, and user ID associated with 3 AUDIT
unsuccessful sign-on attempts.
F-DS-7 The solution shall provide the ability to generate/print an AUDIT trail of all solution 0 Roadmap Workflow Release 3.5 AUDIT
transactions based on workstation ID.

SERIAL 13139-RFP
F-DS-8 The solution shall provide the ability to capture the following information for all I GAPThe AUDIT
AUDIT trail records: record changed, user ID, TOC ID, date/time of change, initial Workflow audit trail functionality does
field value, final field value, not currently provide the ability to
capture the TOC ID on audit trail
records. As a future roadmap item,
Workflow audit trail functionality will
be enhanced to include Alternate Ins
that get logged to the Audit
record.Cost included in the gap
estimate for F-DS- I Line 42 in
Attachment A Cost Proposal
F-DS-9 The solution shall provide the ability to control access and distribution of inmate 3 AUDIT
information in accordance with all applicable laws and regulations.
F-DS-1 0 The solution shall provide the ability to control access and distribution of inmate 3 AUDIT
information in accordance with all applicable ACJIS and CJIS policies.
F DS 1 1 4, GAPDuring the -
-- ::: ; e :- - Technical Requiroments Gap Analysis
Journal Entries, Gang Intel. session IvICSO acknowledged the
complexity of mooting this requiremoot
and noted that it may not be desirable
given the cost. Syscon arid-MCSO
: . • :.- .-.:4. .: ;„; ,-; — -
sensible changes required to moot this
• ; : : . : : . - ;. : J !,
FT - Administrative and Financial Requirements -
F P1 1 • - GAP TRUST ACCOUNTING
the Trust Accounting and Financials
gap analysis sessions.
The current IFICS system uses -Current
: : - .. :• l: • ...
: ::.. • • 11 t t• .,. :
Line 14

SERIAL 13139-RFP
F-FI-2 The solution shall support cash audits as well as users, permissions and procedures used 0 Roadmap Workflow Release 4.0 TRUST ACCOUNTING
for balancing a cash repository.
F-Fl-3 The solution shall provide the inmate's account balance in real-time. This will require 0 Roadmap Workflow Release 4.0 TRUST ACCOUNTING
an interface to the MCSO's financial services vendor. See Appendix 2 - Interface
Requirements.
F-Fl-4 The solution shall provide the ability to display inmate's trust account and transaction 0 Roadmap Workflow Release 4.0 TRUST ACCOUNTING
history by name or booking number. This will require an interface to the MCSO' s
financial services vendor. See Appendix 2 - Interface Requirements.
F-Fl-5 The solution shall provide the ability to enter arresting agencies to include but not 0 Roadmap Workflow Release 4.0 TRUST ACCOUNTING
limited to agency name, agency type, fee types, fee amounts, etc.
F-FI-6 The solution shall provide the ability to create detailed billings for federal, state, and 0 Roadrnap Workflow Release 4.0 TRUST ACCOUNTING
other agencies/entities.
F-FI-7 The solution shall provide the ability to assess fees for an inmate and/or arresting 1 GAP TRUST ACCOUNTING
agency/hold agency. Fee schedule shall allow for a one time fee or recurring fees and
shall calculate the fee(s) based on a date range. This requirement was discussed during
the Financial gap analysis session.
A Per Diem fee collection against
inmates should allow for the collection
of fees on a daily basis. It is not
currently done but the system needs to
have this capability. This collection
could be accomplished on a nightly
basis through use of a batch routine or
by collecting fees by deducting a set
amount from receipt transactions.
• This process will need to deal with
exceptions, such as indigent inmates.
• If unpaid per dims are accumulated
and carry forward between bookings,
this capability will need lobe further
enhanced.
This gap is tentatively scheduled, upon
approval, for Workflow Release 4.5 —
Project Release 2.2
Line 45
in Attachment A Cost Proposal
F-FI-8 The solution shall provide the ability to create an unlimited number of fee types with an 0 Roadmap Workflow Release 4.0 TRUST ACCOUNTING
associated fee amount that are user configurable.
F-Fl-9 The solution shall provide the ability to maintain from and through effective dates for 0 Roadmap Workflow Release 4.0 TRUST ACCOUNTING
all fee types to support annual rate changes.
F-Fl-10 The solution shall provide the ability to record details of persons depositing money in 0 RoadmaP Workflow Release 4.0 TRUST ACCOUNTING
an inmate account.

SERIAL 13139-RFP
F-Fl-1 I The solution shall provide the ability to correct inmate trust account transaction errors. 0 Roadmap Workflow Release 4.0 TRUST ACCOUNTING
F-FI-12 The solution shall provide the ability to record details about the person posting bail. 3 TRUST ACCOUNTING
F-FI-13 The solution shall provide the ability to record bail payments for one or multiple 3 ' TRUST ACCOUNTING
different charges/cases.
F-F1-14 The solution shall provide the ability to record bond postings and the name of the 3 TRUST ACCOUNTING
bonding company.
F-Fl-15 The solution shall provide the ability to print a bail/bond receipt. 3 TRUST ACCOUNTING
F-Fl-16 The solution shall provide the ability to print a receipt when accepting payment for bail, 3 TRUST ACCOUNTING
deposits/debits to an inmate trust account, or programs.
F-Fl-17 The solution shall provide the ability to notify release personnel that a bail/bond has 3 TRUST ACCOUNTING
been posted.
F-F1-18 The solution shall provide the ability to record the payment of fines/restitution. 3 TRUST ACCOUNTING
F-Fl-19 The solution may support digital signatures for the release of money to the inmate or an 3 TRUST ACCOUNTING
approved third party.
F-FI-20 The solution may provide the ability for an inmate to review debits/deposits to his/her 1 GAP TRUST ACCOUNTING
account via kiosk functionality.
This requirement was discussed during
the Financial gap analysis session, It
was determined to be a future
requirement. A Kiosk provider has not
yet been chosen to enable this
functionality.
Line 46
in Attachment A Cost Proposal
F-FI-21 The solution shall provide the ability to establish a payment/fee schedule for programs 0 Roadmap Workflow Release 4.0 TRUST ACCOUNTING
(Work Release, Work Furlough, Electronic Monitoring, or any future programs).
F-F1-22 The solution shall provide the ability to record fees/payments made for programs 0 Roadmap Workflow Release 4.0 TRUST ACCOUNTING
(Work Release, Work Furlough, Electronic Monitoring, or any future programs).
Recording a payment should debit the inmate account. This will require an interface to
the MCSO's financial services vendor.
F-FI-23 The solution shall provide the ability to notify users of missed payments for programs 1 GAP TRUST ACCOUNTING
(Work Release, Work Furlough, Electronic Monitoring, or any future programs). This requirement was discussed during
the Financial gap analysis session. It
was determined to be a future
requirement.
Line 47
in Attachment A Cost Proposal
F-FI-24 The solution shall provide the ability to record inmate co-payments. This will require 0 Roadmap Workflow Release 4.0 TRUST ACCOUNTING
an interface to the MCSO's financial services vendor. See Appendix 2 - Interface
Requirements.

SERIAL 13139-RFP
F-FI-25 The solution shall provide the ability to print inmate trust account disbursement checks 0 Roadrnap Workflow Release 4.0 TRUST ACCOUNTING
automatically for an inmate for release or transfer to another facility.
F-FI-26 The solution shall provide the ability to print a receipt when accepting payment for bail, 0 Roadmap Workflow Release 4.0 TRUST ACCOUNTING
deposits/debits to an inmate trust account, or programs.
F-PI-27 The solution shall provide the ability to interface to Maricopa County Financial System I Custom Interface TRUST ACCOUNTING
for all bonds and fines. See Appendix 2 - Interface Requirements.
F-FI-28 The solution shall provide the ability to perform automated and manual bank I Custom Interface to Bank TRUST ACCOUNTING
reconciliations.
F-FT-29 4 Same requirement as F-F!-7 TRUST ACCOUNTING
- ,- : . • z - e i : . - •• ., ..., : 7.
F-Fl-30 The solution shall provide the ability to support jail billing functions. See Exhibit 11 - I GAP BILLING OF SERVICES
Bidder's Library for information about Detention Services and Related Costs
(06/17/2013). Billing reports are generated once a
month from .IMS in order to provide
Finance with the billing details for
each agency. These reports rely on a
nightly job that compiles the billing
detail for each inmate. A single inmate
may be billable to as many as 4
separate agencies at one time. The
amount charged per agency is
decreased based on the number of
separate billings active at one time.
* Business rules are required in order to
determine what agencies need to be
billed per inmate.
• The large volume of billings (5000 —
6000 inmates billed out per month)
will be a factor in how and when these
rules need to be applied.
• The system must allow for
adjustments to be applied both at the
inmate and agency level when
discrepancies arise.
• The Workflow product must provide
the infrastructure required in order to
deal with the compiled billing records
and to produce the required invoices.
The following are the components of
MCSO's billing practices that differ
from other clients using our existing
billing functionality:
Our current billing system is based
primarily on a linkage to the inmate's
imprisonment status and legal
documents in order to define the start
and end of the billing period by
agency. These linkages are defined in
maintenance and are triggered in real

SERIAL 13139-REP
time via data entry, In MCSO, there is
a decision tree hierarchy. Also,the
number of possible concurrent billable
agencies (4) and the large number of
exceptions make this more complex
than any other billing routine currently
using our systems.
In addition, none of our current clients
using our billing functionality actually
deal with the receipt of invoice
payments They simply generate
invoices from the system and the
payments are received and accounted
for by the County, not by the Jail. This
will require us to add an accounting
component (general ledger) to a
module that historically only generated
invoices.
The approach to implementing Billing
of Services functionality will be
confirmed through the definition of
detailed requirements and the
development of the related product
design. The related cost estimate will
also be reviewed and confirmed at this
point. Syscon reserves to right to
modify the price based on the outcome
of the detailed requirements and design
step. This gap, should it be approved,
is tentatively scheduled for Workflow
Release 3.5— Project Release 1.3. If it
is determined that the scope of what is
required extends beyond the current
understanding this timeline may need
to be adjusted.
Line 48
in Attachment A Cost Proposal
F-FI-31 The solution shall provide the ability for the inmate's account balance to be linked to 1 Touchpay Interface TRUST ACCOUNTING
the inmate's active booking number and displayed in solution. This will require an
interface to the MCSO's financial services vendor. See Appendix 2 - Interface
Requirements.
F-FI-32 The solution shall support audit procedures used for balancing the cash repository. 0 Roadmap Workflow Release 4.0 TRUST ACCOUNTING
F-FT-33 The solution shall provide the abi ty to query by the following, but not limited to name, 0 Roadmap Workflow Release 4.0 TRUST ACCOUNTING
account, type, agency_
GM - Gang Management Requirements

SERIAL 13139-RFP
F-GM-I The solution shall facilitate searching of in scope systems for pertinent information on 3 All Detention
an inmate. They are searching for monikers (nicknames, usually gang related), photos,
visitors who may be visiting several different inmates, and persons who may be
depositing funds in several different inmate accounts.
F-GM-2 The solution shall have the capability to present alerts when a previous person of 3 ADMISSION/TRANSFER/R.ELEA Detention
interest is booked again. See Business Rules Requirements. SE
F-GM-3 The solution may have the capability to store visitor photos. 3 VISITATION Detention
F-GM-4 ----- ::-: - : -. .:- ,,-.: ; :::... : 4 Roadmap Workflow Mose 2.5 COURT ORDERS/LEGAL Detention
DOCUMENTS
E-GM-5 The solution shall provide specific fields for tracking keep-aways. 3 HOUSING BED Detention
MANAGEMENT/MOVEMENTS
F-GM-6 The solution shall provide specific fields for tracking gang affiliation (ability to store 0 Roadmap Workflow Release 2.5 GANGS/SECURITY THREAT Detention
gang information and when it was created), GROUPS
F-GM-7 The solution shall have the capability to store inmate probation officer and attorney 3 COURT ORDERS/LEGAL Detention
information. DOCUMENTS
F-GM-8 The solution shall provide the capability of recording and tracking any activity for 3 GANGS/SECURITY THREAT Detention
known or suspected gang members. GROUPS
F-GM-9 The solution may provide an interface with any state or national gang databases, such I Custom Interface, not included in Detention
as GangNet, pricing
GN - General Requirements
F-GN-1 The solution shall provide a way to query relevant data. 3 ALL Non-Functional
Requirements

SERIAL 13139-RFP
F-GN-2 The solution shall provide a way to access archived data. 1 Sec Attchment C Challenging or Detention
Costly Roquiroments
GAPThe Workflow application is
designed so that data is always live and
always available. Data archival is not a
native feature of the Workflow
application; rather it is a feature of its
underlying technology stack, and a
skilled database administrator (DBA)
can utilize the components of the
Workflow stack or third-party tools to
provide data archival capabilities if
required.During the Technical
Requirements Gap Analysis session
MCSO indicated that audit trail was
significantly high volume and could
burden the Workflow database, To
address this problem Syscon will
enhance the Workflow audit trail
functionality as a future roadmap item
to use a No SQL database which will
provide advanced features for
managing big data. This gap is
tentatively scheduled, upon approval,
for Workflow Release 4.5- Project
Release 2.2Line 49 in Attachment A
Cost Proposal
F-GN-3 The solution shall provide printing capability. 3 ALL Non-Functional
Requirements
F-GN-4 The solution shall associate data such as, but not limited to alias, visits, bookings, 3 ALL Non-Functional
previous SSNs, previous addresses, and drivers license to the inmate record. Requirements
F-GN-5 The solution shall provide the ability to log events with a date and time stamp. 3 ALL Non-Functional
Requirements
F-GN-6 The solution shall provide the ability to remove users from the alert list and allow the 0 Roadmap Workflow Release 3.5 ADMISSIONTTRANSFER/RELEA Non-Functional
entry for a reason for removal. SE Requirements
F-GN-7 The solution shall provide the ability to incorporate photographs from scanning devices 3 BIOMETRICS Non-Functional
or third party applications. [FINGERPRINT/IMAGING] Requirements
F-GN-8 The solution shall provide the ability to have electronic notification of alerts when a 3 ADMISSION/TRANSFER/RELEA Non-Functional
inmate is taken into custody. SE Requirements
F-GN-9 The solution shall provide the ability to electronically communicate with other law 1 Custom Interface DCI
enforcement agencies regarding inmate arrest information.
F-ON-10 The solution shall provide the ability for a user to perform text entry and the 1 Custom Interface Del
ACTIS/CJIS messaging to other jurisdictions for notification of the arrest, to inquire on
bond amounts, court dates, inmate transportation, inmate mug shots, etc. See Appendix
2 - Interface Requirements.

SERIAL 13139-RFP
F-ON-I 1 The solution shall provide JMS information access through Justice Web Interface I Custom Interface DCI
andfor alternative methods, See Appendix 2 - Interface Requirements.
F-GN-12 The solution shall provide JIMS inquiry capability that cart be utilized on mobile 3 ALL Non-Functional
devices. Requirements
F-ON-13 The solution shall provide the ability to use a card reader for capturing data from a I Enhancement ALL Non-Functional
driver's license or ID card. Data should automatically populate fields in the solution. Requirements
See Exhibit A Line 49.5
F-ON-14 The solution may provide the ability to enter rich text (bold, underline, italics, font, 3 ALL Non-Functional
size, font color, etc.) for all user defined free text narratives. Requirements
F-ON-15 The solution shall provide a single user interface which allows users to view, edit, hide 0 Roadmap Workflow Release 3,5 ALL Non-Functional
or delete information on an inmate record at any time based on security privileges. Requirements
F-ON-16 The solution shall provide the ability to configure data entry questionnaire screens and 3 ASSESSMENTS & Classification
to define questions and responses. CLASSIFICATION
F-GN-17 The solution may provide the ability to capture electronic signatures and provide the 3 Reporting/BYWord Processing Document
specifications for the supported equipment, Management
F-GN-18 The solution shall provide the ability to capture single or two fingerprint images and 3 BIOMETRICS Intake
attach to an inmate record, See Appendix 2- Interface Requirements, [FINGERPRINT/IMAGING]
F-ON-19 The solution may provide multi-level sorting feature for data elements when displaying 3 Non Functional
reports at the user level and store sorting preferences for reports at the user level.
F-GN-20 The solution shall provide end user definable data validation to safeguard against the 3 ALL Non-Functional
entry of incorrect data. Requirements
F-GN-21 -,.: ; . -• ; : t.:. -:.; - : ...: : -•...-..--:: .-,—.,-;- -, -: , , Enhancement COURT ORDERS/LEGAL SIMS
bond through a bonding company. DOCUMENTS
During on-site analysis, it was
determined that this requirement
should be removed, as it is not possible
to get this information from the
bonding company.
F-GN-22 The solution shall provide the ability to automatically query the RMS, ACIC/NCIC and I Custom Interface DC1
alert the user if there are warrants outstanding for the inmate.
During the Messaging Gap Analysis
session it was agreed that the Warrant
checks via ALETS and NLETS would
be performed using JWI and as a result
this would no longer be a requirement
for the new JMS.
The ability to perform warrant checks
will be available to users through the
JWI.
tR.

SERIAL 13139-RFT
F-GN-23 The solution may provide the ability to provide a printable face sheet containing inmate 3 ADMISSION/TRANSFER/RELEA • Reporting
information: photograph, charges, alerts, demographic data, etc. SE
F-GN-24 The solution shall provide the ability to display the inmate's name and photo ID along 3 ADMISSION/TRANSFER/RELEA Intake
with the arrest, booking and court information. SE
F-GN-25 The solution shall provide the ability to record, review, and edit current and past inmate 3 ADMISSION/TRANSFER/RELEA Intake
addresses. SE
F-GN-26 The solution shall provide the ability to record, review, and edit current and past 3 ADMISSION/TRANSFER/RELEA Intake
employment. SE
F-GN-27 4 During on-site analysis, it was COMMUNITY SIMS
history, determined that this requirement can
be removed as the specific nature of
the need for this requirement was not
clear. It is not information that is
tracked, currently.
F-ON-28 The solution shall provide the ability to record, review, and edit subject family contact 3 ADMISSION/TRANSFER/RELEA Intake
information, SE
F-GN-29 The solution shall provide the ability to record details of contacts or attempted contacts 3 EVENT LOGS Detention
with outside parties,
F-GN-30 The solution shall provide the ability to capture information regarding warrants checks 3 EVENT LOGS Detention
or database searches conducted prior to an inmate's release.
F-GN-3I The solution shall provide the ability to search using either a keyword or partial 3 ALL Non-Functional
keyword on the inmate's name or booking number and limit displayed information Requirements
based on uses security level and machine location.
F-GN-32 The solution shall provide an interface to a kiosk for inmates to view data such as, but 1 Custom Interface GAP DCI
not be limited to court information, bait information, account balance, charges, inmate
calendar, visiting schedule, grievance responses, inmate request responses, disciplinary The concept of self-service kiosks was
hearing results, program schedule, etc discussed during the Gap-Analysis. At
this time there is not enough
information available to accurately
define interface requirements that may
be needed to deploy self-service
kiosks, As such this is deemed to be a
potential future requirement. See also
NE-AC-1,3.
Line 51
in Attachment A Cost Proposal
F-GN-33 The solution shall provide the ability to request notification if a query is received on a 0 Roadmap Workflow Release 3.5 ALL Nan-Functional
particular inmate. Requirements

SERIAL 13139-1RFP
F-GN-34 The solution shall provide shift summary statistics based on business rules containing 3 REPORTING/BYWORD Reporting
information including but not 'limited to count, transfers, releases, medical, visitation, PROCESSING
incidents and recreation.
F-GN-35 The solution shall provide the ability to log events with a date and time stamp. See Jail 3 EVENT LOGS Non-Functional
Operations Requirements. Requirements
F-GN-36 1 The solution may provide the ability to schedule and track jail maintenance inspections 0 GAP The EVENT LOGS Detention
(locks, doors, radios), command inspections, and other inspections, ability to schedule such maintenance is
not an ideal fit for an inmate
management system; therefore it is not
planned on the product
roadmap.During on-site gap analysis, it
was learned that scheduling
maintenance is not something that is
currently performed in the existing
JMS. This was described as a `nice-to-
have'. Workflow is able to track
scheduled maintenance inspections, but
creation of the schedule is a gap, It is
recommended that shift logs be used to
track all scheduled maintenance
inspections and occurrences. Shift
logs is already available, hence it is a
3.Line 52in Attachment A Cost
Proposal
Cost not provided
3/24/15 MCSO agreed to use work
around using task list
F-GN-37 The solution may provide the ability to generate alerts for the following, but not limited 3 COURT ORDERS/LEGAL Detention
to co-defendants and witnesses, DOCUMENTS
F-GN-38 The solution shall be able to maintain log of PREA incidents. 3 DISCIPLINE Detention - Hearing
Unit
F-GN-39 The solution shall be able to tog and track use of force incidents. 3 DISCIPLINE Detention - Hearing
Unit
F-GN-40 The solution shall be able to assign a unique tracking number to use of force incidents. 3 DISCIPLINE Detention - Hearing
Unit
F-GN-41 The solution shall record relevant information for use of force incidents, 3 DISCIPLINE Detention - Hearing
Unit
F-GN-42 The solution shall share PREA and use of force incidents data electronically with 1 Custom Interface DCI
MCSO's Internal Affairs software (IA Pro). See Appendix 2- Interface Requirements.
External Forms

SERIAL 13139-RFP
F-GN-43 The solution shall provide the ability to incorporate photographs from scanning devices 3 BIOMETRICS Non-Functional
or third party applications. [FINGERPRINT/IMAGING] Requirements
F-GN-44 The solution shall provide the ability to have an email confirmation of alert when a 0 Roadmap Workflow Release 3.5 MESSAGING Non-Functional
subject is taken into custody. Requirements
F-GN-45 The solution shall provide the ability to electronically communicate with other law I Custom Interface DC1
enforcement agencies regarding inmate arrest information based on security privileges.
F-GN-46 The solution shall provide the ability for a user to perform text entry and the 1 Custom Interface DCI
ACES/CJIS messaging to other jurisdictions for notification of the arrest, to inquire on
bond amounts, court dates, inmate transportadon, inmate mug shots, etc.
F-GN-47 The solution shall provide JMS information access through Justice Web' Interface I Custom Interface DCI
and/or alternative methods.
F-GN-48 The solution shall provide JMS inquiry capability that can be utilized by mobile devices 3 ALL Non-Functional
unique to the individual, device and function. Requirements
F-GN-49 The solution may provide the ability to enter rich text (bold, underline, italics, font, 3 ALL Non-Functional
size, font color, etc.) for all user defined free text narratives. Requirements
F-ON-50 The solution shall have full color capability. 3 ALL Non-Functional
Requirements
F-ON-51 The solution's user interface may be windows like in function and form. 3 ALL Non-Functional
Requirements
HD - Holds Requirements

SERIAL 13I39-RFP
F-HD-1 The solution shall provide the ability for authorized users to maintain hold reason SIMS
options, including which fields are displayed for each hold reason. Gestly-Requirements
GAP
This was originally defined in the RFP
as Challenging or Costly Requirements
and was therefore not quoted in the
proposal. It was discussed in the SIMS
gap analysis sessions.
The gap analysis has that MCSO
requires this functionality and as such
is a Gap.
The ability to dynamically associate
the proper data elements to each hold
type is required by MCSO. Other
requirements in this section are
dependent upon this requirement being
available including;
F-HD-2
F-HD-6
F-HD-14
Holds and out-of-jurisdiction holds
functionality will be extended to meet
this group of requirements. The
detailed requirements analysis will
produce a design specification that will
be developed and is tentatively
scheduled for Workflow 3.5 Release. —
Project Release 1.3
Line 53
in Attachment A Cost Proposal
F-HD-2 The solution shall provide the ability to create a hold on an inmate and capture the dependent on GAP being addressed for COURT ORDERS/LEGAL SIMS
agency requesting the hold, the charge, and the reason for the hold including but not F-HD-1 DOCUMENTS
limited to: charge, sentenced, warrant, additional hold, booking number, as well as all
other available information relating to the hold such as hold charge(s), hold agency, bail
amount, expiration date, and hold disposition. See Business Rules and Workflow
Requirements.
F-HD-3 The solution shall provide the ability for an authorized user to clear a hold and record COURT ORDERS/LEGAL SIMS
reasons for the release. DOCUMENTS
F-HD-4 The solution shall provide the ability to alert designated users if there are outstanding COURT ORDERS/LEGAL SIMS
holds against The inmate. See Workflow [Messaging] Requirements. DOCUMENTS
F-HD-5 The solution shall provide the ability for an authorized user to reconcile holds for 3 COURT ORDERS/LEGAL SIMS
release through workflow. See Workflow Requirements. DOCUMENTS
QA

SERIAL 13I39-RFP
F-IID-6 The solution shall provide the ability to enter multiple hold reasons per inmate, and the 3 dependent on GAP being addressed for COURT ORDERS/LEGAL SIMS
fields needed for the selected hold reason. F-HD-I DOCUMENTS
F-HD-7 The solution shall provide the ability to record Individual release hold resolution and 3 COURT ORDERS/LEGAL SIMS
reasons such as, but not limited to fugitive from justice and interstate compact prior to DOCUMENTS
overall inmate release.
F-HD-8 The solution shall support user definable release types, such as but not limited to: PTA, 3 COURT ORDERS/LEGAL SIMS
Child Support, out-of-county warrant citation, ROR, bail, bond, transfer to DOC, and DOCUMENTS
transfer to another agency, extradition, fugitive from justice, and release of probation or
parole hold.
F HD 91 •,_ .
only-to.-that.agerio in-Attachment A Cost Proposal S•g
F-HD-10 The solution shall support messaging if the holding agency is to pick up the inmate and 3 Roadmap Workflow Release 3.5 MESSAGING SIMS
track status if agency has responded or not responded. See Messaging requirements.
F-HD-11 The solution shall provide the ability to record whether a hold hats 'do not extradite or 3 COURT ORDERS/LEGAL SIMS
'extradite' status for the inmate. DOCUMENTS
F HD 2 4. COW-R-T-ORDERS,ELEreAL, SIMS
- : : = --: • :-: DOCUMENTS/TASK
MANAGEMENT
......k : - -..!
,
F-HD-13 The solution shall provide the ability to alert a designated group of users that an inmate 3 MESSAGING SIMS
with other holds is NOT released from the facility, even if the inmate has accrued
sufficient jail time to satisfy the sentence.
F-HD-14 The solution shall provide the ability for the user to configure the hold fields, I Part of Enhancement COURT ORDERS/LEGAL SIMS
DOCUMENTS
Is addressed with GAP for F4-1D-1 .
F-HD45 The solution shall provide the ability to define hold disposition values. 3 COURT ORDERS/LEGAL SIMS
DOCUMENTS
HO - Housing Requirements
F-HO-1 The solution shall provide the ability to track housing and facility attributes, including, 3 HOUSING BED MANAGEMENT Detention
but not limited to: facility, building, dorm, pod, cell, bed and intended classification.

SERIAL 13139-REP
F-HO-2 The solution shall assign and track all inmate cell and bed assignments, including 3 HOUSING BED Detention
external locations with the ability to view historical data. MANAGEMENT/MOVEMENTS
F-HO-3 The solution shall provide a housing roster by facility, building, dorm, pod and S 3 HOUSING BED MANAGEMENT Detention
Comments (Special Accommodations).
F-I-10-4 The solution shall be able to provide alerts and warnings for inappropriate housing 3 HOUSING BED MANAGEMENT Detention
including, but not limited to the following: keep-aways, gender. NOC, or classification.
F-HO-5 The solution shall track the real-time capacity for each housing unit. 3 HOUSING BED MANAGEMENT Detention
F-HO-6 The solution shall provide alerts if an assignment will exceed the capacity, based on 3 HOUSING BED MANAGEMENT Detention
business rules.
F-HO-7 The solution shall store and retrieve historical housing assignments. 3 HOUSING BED MANAGEMENT Detention
F-H0-13 The solution shall record results of physical counts for pods, dorms, facilities, and 3 COUNTS Detention
enterprise wide,
F-HO-9 The solution shall record information restricting inmate movement. 3 HOUSING BED MANAGEMENT Detention
F-HO-10 The solution shall locate an available facility/bed that matches both the inmate 3 HOUSING BED MANAGEMENT Detention
characteristics and the bed characteristics according to business rules including, but not
limited to: classification, medical, mental health, security, etc,
F-HO-11 The solution shall hold beds for inmates according to business rules (including, but not 0 Roadmap Workflow Release 2.5 HOUSING BED MANAGEMENT Detention
limited to. out to hospital, etc.).
F-H0-12 The solution shall record, approve, and track an inmate's keep-away requests, 3 REQUEST AND GRIEVANCES Detention
F-HO-13 The solution shall provide the ability to interface with an electronic tracking system for 1 Custom Interface, not included in DC1
inmate movements. pricing
F-HO-I4 The solution shall record date and time of any inmate movement. 3 HOUSING BED Moves-Transfers
MANAGEMENT/MOVEMENTS
F-HO-15 The solution shall be able to accommodate mass movements, i.e. several inmates going 3 MOVEMENTS Moves-Transfers
out to court
F-1-10-15 The solution shall provide logging functionality and query capability of one time and 3 HOUSING BED MANAGEMENT Detention
recurring daily activities and transactions of the housing unit.
F-HO-17 The solution shall provide shift summary statistics based on business rules containing 0 Roadmap Workflow Release 2,5 REPORTING/BYWORD Reporting
information including but not limited to: count, transfers, releases, medical, visitation, PROCESSING
incidents and recreation. See General Requirements.

SERIAL I3139-RFP
FED-18 The solution shall be able to track and maintain work release and work furlough 0 Roadmap Workflow Release 2.5 PROGRAMS & SERVICES Detention
inmates (partial custody),
F-HO-19 The solution shall record if a cell is of 1 ne due to maintenance. 3 HOUSING BED MANAGEMENT Detention
F-110-20 The solution shall provide the ability to assign inmate housing by batch processing. 0 Roadmap Workflow Release 2.5 HOUSING BED MANAGEMENT Detention
F-HO-21 The solution may use Correctional Health Services (CHS) interface data for housing I Custom Interface DC1
assignment purposes.
F-HO-22 The solution shall provide the ability to change housing unit attributes on a temporary 3 HOUSING BED MANAGEMENT Detention
basis.
F-HO-23 The solutions shall provide the ability to flag an inmate under disciplinary action. 3 DISCIPLINE Detention
F-HO-24 The solution shall provide the ability to track Seriously Mentally III (SMI) and 3 ADMISSION/TRANSFER/RELEA Detention
associate to an inmate record. SE
F-HO-25 The solution may provide the ability to automatically release a bed once an inmate is 3 HOUSING BED MANAGEMENT Detention
ready to be released or transferred (assigned a temporary tank).
F-HO-26 The solution shall provide the ability to put full housing unit on restriction. 3 EVENT LOGS Detention
F-140-27 The solution shall provide the ability to create notifications/alerts to move SMIs out of 3 HOUSING BED MANAGEMENT Detention
housing if the temperature hits a certain degree,
ID - Inmate Discipline Requirements
F-ID-I The solution shall provide the ability to log the inmate's event that is resulting in a 3 DISCIPLINE Detention
disciplinary action.
F-ID-2 The solution shall be able to log and track disciplinary action. 3 DISCIPLINE Detention
F-ID-3 The solution shall provide the ability to record the results of an investigation into a 3 DISCIPLINE Detention
disciplinary action.
F40-4 The solution shall provide the ability to schedule the disciplinary hearing. 3 - DISCIPLINE Detention
F-ID-5 The solution shall provide the ability to record the results of the disciplinary hearing. 3 DISCIPLINE Detention
F40-6 The solution shall provide the ability to record and track any follow up required from 3 DISCIPLINE Detention
the hearing.
F-ID-7 The solution shall provide the ability for an authorized user to review past history 3 DISCIPLINE Detention
discipline violations.

SERIAL 13139-RFT
F-ID-8 The solution shall provide the ability to record the sanction imposed and status, 3 DISCIPLINE Detention
Examples include, but are not limited to, Full Restriction, Disciplinary Segregation,
Written Warning, Medical No Sanction, Dismissal, No Action, and/or Loaf (meal
restriction).
F-ID-9 The solution shall be able to record a sanction or action for each violation. 3 DISCIPLINE Detention
F-ID-10 The solution shall provide the ability to enter and track appeals. 0 Roadmap Workflow Release 2.5 DISCIPLINE Detention
F-ID-11 The solution shall provide the ability to log and maintain a disposition. 3 DISCIPLINE Detention
F-ID-I 2 The solution shall provide the ability to review a summary of an incident and/or action. 3 DISCIPLINE Detention
F-ID-1 3 The solution shall provide the ability to log and maintain comments and/or write ups 3 DISCIPLINE Detention
that an officer has created regarding an inmate disciplinary action.
F-ID- 4 The solution shall be able to log and track a disciplinary action type, 3 DISCIPLINE Detention
IN - Intake Requirements
Arrest
F-IN-1 The solution shall receive and process an electronic transaction from Law Enforcement 1 Custom Interface DCI
Records Management solutions to establish inmate information. See Appendix 2 -
Interface Requirements,
F-IN-2 The solution shall provide the ability for direct user entry of inmate information. I GAP This ARRESTS & WARRANTS(PRE- Intake
requirement was discussed during the BOOK)
Intake gap analysis session. The pre-
booking system will enable users from
other agencies to directly access the
system, but does not currently
contemplate login by °RI, rather by
user name and password. OR] is an
identifier issued every law enforcement
agency by the FBI. The challenge with
logging in with an ORI is that multiple
users will be associated to the same
ORI. As part of the pre-booking
product development, the detailed
requirements and approach will be
identified, resulting in the development
of an extension that will enable other
agency users to login in a manner that
is easy to configure and maintain by
the MCSO. This extension, if
approved, is tentatively scheduled for
Workflow Release 4.5Line 57in
Attachment A Cost Proposal
F-IN-3 Inmate information shall include, but is not limited to, the following: inmate 0 Roadmap Workflow Release 4.0 ARRESTS & WARRANTS Intake
demographics, alias names, dates of birth, and SSNs, scars, marks and tattoos, property, (PRE-BOOK)
co-defendant information, arrest details, hold information, charge information, bond
information, sentencing information, Department Report (DR) Information AKA
incident Report, Form IV information (AZ Court required document that includes
questions and probably cause descriptions).

SERIAL 13139-RFP
F-IN-4 The solution shall be able to automatically generate Bonds based on preset criteria, 0 Roadmap Workflow Release 4.0 ARRESTS & WARRANTS Intake
such as Courts and Charges. (PRE-BOOK)
F-IN-5 The solution shall perform validation and response notification of success or errors 0 Roadmap Workflow Release 4.0 ARRESTS & WARRANTS Intake
encountered for both the electronic transaction and the direct user entry. (PRE-BOOK)
F-IN-6 The solution shall provide the ability for external agencies to enter information. 0 Roadmap Workflow Release 4.0 ARRESTS & WARRANTS Intake
(PRE-BOOK)
F-IN-7 The solution shall provide the ability to access and enter data remotely. 0 Roadmap Workflow Release 4.0 ARRESTS & WARRANTS Intake
(PRE-BOOK)
F-IN-8 The solution shall automatically associate arrest and charge by date and display specific 3 COURT ORDERS/LEGAL Intake/SIMS
applicable drop down options. DOCUMENTS
Book the inmate
F-IN-9 The solution shall provide the ability to place multiple tirnestamps (e.g., arrival 3 ADMISSION/TRANSFER/RELEA Intake / Workflow
timestamp) on the inmate record based on when they arrive at Central Intake and as SE
they go through the intake process. See Workflow Requirements.
F-IN-10 The solution shall transmit basic inmate information to Maricopa County's Electronic I Custom Interface DC1
Health Records solution (EHR) to establish their place on the queue for medical
evaluation. See Appendix 2 - Interface Requirements.
F-IN-11 The solution shall receive an electronic notification of acceptance or denial from the I Custom Interface DCI
EHR solution. See Appendix 2 - Interface Requirements.
F-1N-12 The solution shall generate a unique Booking Number (identifier) associated with the 3 ADMISSION/TRANSFER/RELEA Intake
inmate and arrest information. SE
F-IN-13 The solution shall track the receipt of the inmate's property. See the Property 3 PROPERTY Intake
Requirements.
F-1N-14 The solution shall transmit basic booking information to the Maricopa County Mugshot 1 Custom Interface DCI
solution. See Appendix 2- Interface Requirements.
F-IN-15 The solution shall have the ability to receive Mugshot photos to store with the inmate 1 Custom Interface DCI
record.
F-IN-16 The solution shall establish an inmate fund account and record money received during 3 TRUST ACCOUNTING BUDGET/FINANC
the intake process. See Trust Accounting/Canteen Requirements. E
F-IN-17 The solution shall refund any inmate funds obtained in pre-booking if ultimately denied 3 TRUST ACCOUNTING BUDGET/FINANC
later in the pre-booking process. E
F-IN-18 The solution may transmit Booking information and Mugshot photos to the existing I Custom Interface Intake / DC1
solution (Bioguard). See Appendix 2 - Interface Requirements.

SERIAL I3139-RFP
F-IN-19 The solution shall support the ability to do a final acceptance or denial of the inmate 0 Roadmap Workflow Release 4.0 ARRESTS & WARRANTS Intake
into the Jail. (PRE-BOOK)
F-IN-20 For accepted inmates, the solution shall interface with the Maricopa County Common I Custom Interface DC1
Case Number generating solution to receive and store a Common Case Number for all
new charges. This number is used as an identifier throughout the criminal justice
process. See Appendix 2 - Interface Requirements.
F-IN-21 For accepted inmates, the solution shall transmit inmate and booking information to the 1 Custom Interface DCI
Maricopa County Court solution (ICIS). See Appendix 2 - Interface Requirements.
F-IN-22 For accepted inmate, the solution shall transmit a final booking transaction to the 1 Custom Interface DCI
initiating Law Enforcement's Records Management solution.
Inmate Identification
F-IN-23 The solution may track the inmate's cell location throughout the Intake process. See 3 ADMISSION/TRANSFER/RELEA Intake
Inmate Movement and Count Requirements. SE
F-IN-24 The solution shall automatically trigger a Warrants check. I Custom Interface Del
F-IN-25 The solution shall transmit an electronic transaction to the existing solution (Livescari). 1 Custom Interface Del
See Appendix 2- Interface Requirements.
F-IN-26 The solution shall receive and store the Livescan Process Control Number (PCN) from I Custom Interface DCI
the Arizona AFIS system. See Appendix 2- Interface Requirements.
F-1N-27 The solution shall track DNA sampling and date taken on an inmate's record. 3 ADM1SSION/TRANSFERJRELEA Intake
SE
F-IN-28 The solution shall provide the ability to electronically generate an auto populated 3 REPORTING/BI/WORD Reporting
selective service form. PROCESSING
F-1N-29 The solution shall display inmate photo on inquiry. 3 BIOMETRICS Intake
[FINGERPRINT/IMAGING]
Initial Court Appearance
F-IN-30 The solution shall provide alerts when an inmate is nearing the 24 hour time period for 0 Roadmap Workflow Release 4.0 ARRESTS & WARRANTS Intake / Workflow
date and time of arrest to the initial court appearance. (PRE-BOOK)
F-IN-31 The solution shall track and provide an alert from the time the inmate was accepted into 3 ADMISSION/TRANSFER/RELEA Intake ! Workflow
the jail to when they get access to a cell with a bed. SE
F-IN-32 The solution shall capture the Condition of Release information and next court 3 ADMISSION/TRANSFER/RELEA Intake / SIMS
appearance. SE
Process Based on Condition of Release

SERIAL 13I39-RFP
F-IN-33 The solution shall process the inmate release during the Intake process. See Release 3 ADMISSION/TRANSFER/RELEA intake / Release
Requirements. SE
F-134-34 The solution shall process inmates who will be kept in custody. See Classification 3 ADMISSION/TRANSFER/RELEA Intake
Requirements and Movement (Transportation) Requirements. SE
F-IN-35 The solution shall provide a state of the art positive ID process facilitating initial 3 BIOMETRICS Intake
classification. [FINGERPRINT/IMAGING]
F-IN-36 The solution shall provide the ability to immediately display prior booking information 3 ADMISSION/TRANSFERRELEA Intake
during the intake process. SE
General
F4N-37 The solution shall maintain inmate identification information, including but not limited 3 "name of business" as offender not ADMISSION/TRANSFER/RELEA Intake
to the following; Name of Individual as Offender or , t.-- : ,. S . - . required. SE
Alias (multiple values), Sex, Race, Height, Eye Color, Hair Color, Sears/Marks/Tattoos
and Other (multiple values), Birth Date (multiple values), Place of Birth, U.S. Citizen,
Social Security Number (multiple values), State Identification Number (Sir)),
Department of Corrections Inmate Number, FBI Number,
F-IN-38 The solution shall maintain inmate arrest information, including but not limited to, the 0 Roadmap Workflow Release 4.0 ARRESTS & WARRANTS Intake
following: Process Control Number (PCN), Juvenile Arrested as Adult, Date of Crime, (PRE-BOOK)
Effective Dates of Crime, Date of Original Arrest or Summons Fingerprinting,
Originating (Arresting) Agency Identifier (ORI), Booking Number, Arresting Agency
Case Number or Departmental Report (DR) Number, A.R.S, Charge, A.R.S. Charge
Type (Fel, Misd, x), Initial Charge Sequence Number, Preparatory Offense Code,
Victim Code (multiple values), Not Referred for Prosecution, and Date Not Referred
for Prosecution.
F-IN-39 The solution shall maintain inmate booking information, including but not limited to, 1 Enhancement Intake
the following: Process Control Number (PCN), Juvenile Booked as Adult, Date of
Original Arrest or Summons Fingerprinting, Originating (Booking) Agency Identifier Included with enhancement for F-CT-
(ORI), Booking Number, Arresting Agency Case Number or Departmental Report 18
(DR) Number, Booking A.R.S. Charge, Booking A.R.S. Charge Type (Pal, Misd, a), (Line 2
Booking Charge Sequence Number, Booking Preparatory Offense Code, Victim Code in Attachment A Cost Proposal)
(multiple values), Not Referred for Prosecution, and Date Not Referred for Prosecution.
F-IN40 The solution shall provide the ability to restrict the use of charge codes based on the 3 COURT ORDERS/LEGAL Intake
date of offense and charge code effective date. If the expired charge code is a DOCUMENTS
disposition the disposition may only be added if the dispostion date falls within the
effective and expired dates for that charge code. If the expired charge code is a
modification, (e.g., the first code was entered in error), the modification may only be
added if the offense date falls within the effective and expired dates for that charge
code. See Business Rules requirements.
F-IN41 The solution shall provide the ability to track and review the history of all charges on 0 Roadmap Workflow Release 3.0 COURT ORDERS/LEGAL. Intake
an inmate's booking from inception through disposition, i.e., including but not limited DOCUMENTS
to the following: original booking charge, charges filed by the County Attorney, charge
modifications, charge at disposition, etc., as well as the Booking Charge Sequence
Number and the date each entry was made.
IS'- Inmate Services Requirements

SERIAL 13139-RFP
Inmate Laundry
F-IS-I The solution shall provide a listing of clothing needed for inmates for each living unit 0 Roadmap Workflow Release 4.5 CLOTHING ISSUE N/A
Size and quantity to be calculated from data entered in property module during intake.
F-IS-2 The solution shall be capable of adjusting inventory stock based on commodities used. 0 Roadmap Workflow Release 4.5 CLOTHING ISSUE N/A
F-IS-3 The solution shall be capable of adjusting inventory stock based on clothing replaced 0 Roadmap Workflow Release 4.5 CLOTHING ISSUE N/A
due to normal wear or other factors.
F45-4 The solution shall be capable of establishing schedules for cleaning of non-routine 0 Roadmap Workflow Release 4.5 CLOTHING ISSUE N/A
items such as blankets.
F-IS-5 The solution shall have the ability to determine the number of uniforms that must be 0 Roadmap Workflow Release 4.5 CLOTHING ISSUE N/A
transported to a pod based on color, size and the current number of inmates assignment
to a unit or floor.
F-IS-6 The solution shall have the ability to update inmate institutional history and document 0 Roadmap Workflow Release 4,5 CLOTHING ISSUE N/A
uniform exchange either individually or in mass by indicating that an entire pod has
exchanged their uniforms.
Dietary and Meal
F-IS-7 The solution shall track/display/print the quantity of meals that are served to inmates by 0 Roadmap Workflow Release 3.5 DIETARY/MEAL PLANNING N/A
date, quantity of meals.
F-IS-8 The solution shall provide the ability to display/print dietary related documents and 0 Roadmap Workflow Release 4.5- not DIETARY/MEAL PLANNING N/A
labels including the Pic Sheet. required for Phase 1
F 1S9 0 Roadmap Q1/2015 DIETARY/MEAL PLANNING NAA
During gap analysis discussion it was
removed.
F-IS- 1 0 The solution shall have the ability to capture dietary needs electronically. Roadmap Workflow Release 3.5 DIETARY/MEAL PLANNING N/A
F-IS-11 The solution shall have the ability to capture special meal requirements (including 0 Roadmap Workflow Release 3.5 DIETARY/MEAL PLANNING N/A
religious diets) and schedule the start and end date.
F-IS-I 2 The solution may have the ability to indicate special serving times for religious 0 Roadmap Workflow Release 3.5 DIETARY/MEAL PLANNING N/A
holidays.
F-IS-13 The solution shall have the ability to trigger workflow process to obtain approval from 0 Roadmap Workflow Release 3.5 DIETARY/MEAL PLANNING N/A
clergy, security, or medical personnel for special diets.

SERIAL 13139-RFP
F-IS-14 The solution shall have the ability to generate a report and print labels for the Food 0 Roadmap Workflow Release 3,5 DIETARY/MEAL PLANNING N/A
Factory indicating the number of meals of each type that are required for a given
unit/pod/facility.
F-IS-15 The solution shall have the ability to generate the "Record of Meals Served r form 0 Roadmap Workflow Release 3.5 DIETARY/MEAL PLANNING N/A
which indicates what meals need to be delivered to a particular unit/pod/facility.
F-IS-16 The solution shall have the ability to electronically document destroyed meals. 0 Roadmap Workflow Release 4.5 - not DIETARY/MEAL PLANNING N/A
required for Phase 1
F-IS-17 The solution shall have the ability to document inmate meal refusal. 0 Roadmap Workflow Release 3.5 DIETARY/MEAL PLANNING N/A
F-IS- 18 The solution shall have the ability to provide daily inmate counts. 0 Roadmap Workflow Release 3.5 DIETARY/MEAL PLANNING N/A
Strategic and Tactical Analysis
F-IS-19 The solution shall have the ability to provide summary data capabilities to specifically 3 REPORTING/BYWORD Reporting
authorized users in order to extract information from defined query sets for external PROCESSING
analysis. See Reporting Requirements.
F-IS-20 The solution shall provide the ability to collect and provide statistical information about 3 REPORTING/BI/WORD Reporting
the performance, capacity, and accuracy of the data itself and the management PROCESSING
operations of the solution. See Reporting Requirements.
Departmental Phone
F-IS-21 .— .. . 0 Soo Attchmont C Challenging or NA
unit communication. Costly Requirements
Inmate Library
F-IS-22 The solution shall provide a way of identifying inmates that require foreign language 3 ADMISSION/TRANSFER/RELEA Intake
interpreter. SE
F-IS-23 The solution shall provide a way to maintain inmate library request information, 3 REQUEST AND GRIEVANCES Programs
Inmate Legal Services
F-IS-24 The solution shall have the ability to categorize an inmate as pro per and/or pro se. 3 ADMISSION/TRANSFER/RELEA Intake
SE
F-1S-25 The solution may have the ability to alert a user when accessing an inmate with special 3 ADMISSION/TRANSFER/RELEA Intake
needs such as a foreign language interpreter, SE
F-IS-25 The solution may have the ability to log and maintain legal services requests 3 REQUEST AND GRIEVANCES Programs
F-IS-27 The solution may have the ability to track legal services provided. 3 EVENT LOG

SERIAL 13139-REP
F-IS-28 The solution may be able to associate letters and documents prepared on behalf of an 3 REPORTING/III/WORD Document
inmate or for the court to a specific service request. PROCESSING Management
F-18-29 The solution may have the capability to track Inmate Services correspondence to and 0 Roadmap Workflow Release 3,5 INMATE CORRESPONDENCE N/A
from an inmate.
F-IS-30 The solution shall have the ability to display fund balance and create statements. See 3 TRUST ACCOUNTING Budget / Finance
Trust Accounting Requirements,
F4S-31 The solution shall provide the ability to run a litigation report. See Reporting 3 REPORTING/BYWORD Reporting
Requirements, PROCESSING
F-1S-32 The solution shall provide the ability to calculate fees based on a defined set of business 3 BILLING OF SERVICES Budget / Finance
rules,
F48-33 The solution shall be able to automatically deduct funds based on a defined set of 3 TRUST ACCOUNTING Budget / Finance
business rules and calculations.
Correctional Health
F-35-34 The solution shall provide the capability to present alerts such as safe cell, send to 3 ADMISSION/TRANSFER/RELEA Detention - housing
clinic. SE
F-15-35 The solution shall provide the ability to flag an inmate as Seriously Mentally Ill (SMI). 3 ADMISSION/TRANSFERJRELEA Detention - housing
SE
F-IS-36 The solution must be able to report SMI's via a daily workflow to the Hearing Unit. 3 REPORTING/Ell/WORD Detention - hearing
PROCESSING Unit
F-15-37 The solution may provide the proxy score via interface to TechCare. 1 Custom Interface or embedded in IMS, ASSESSMENTS AND DCYCLASSIFICAT
not included in pricing (assume JMS CLASSIFICATION ION
will provide the proxy score)
F-IS-38 The solution shall have an inmate scheduling module. 3 MOVEMENTS Scheduling
F-15-39 The solution shall have the ability to record multiple dietary restrictions. 0 Roadmap Workflow Release 3,5 D1ETARY/MEAL PLANNING N/A
F-15-40 The solution may provide the ability to alert the housing unit and food factory of a 0 Roadmap Workflow Release 3.5 MESSAGING N/A
special diet required for medical procedure.
F-15-41 The solution shall provide the ability to record and maintain physician orders such as 3 ADMISSION/TRANSFER/RELEA Intake
blankets, wheelchairs, lower bunks. SE
F-IS-42 The solution may provide the ability to send and receive physician orders electronically 1 Custom Interface DCYCLASSIFICAT
for approval purposes. ION
F-IS-43 The solution shall provide the ability to record a start and end date and time for 3 ADMISSION/TRANSFER/RELEA Intake
physician orders. SE

SERIAL 13139-RFP
F-IS-44 The solution may be able to record and maintain release instructions such as ensuring 3 ADMISSION/TRANSFERJRELEA Release
inmates get medthervices, juveniles on medication may talk to parents, special SE
condition instructions, etc.
F-IS-45 The solution shall provide the ability to alert/notify for work clearance. 0 Roadmap Workflow Release 2.5 PROGRAMS & SERVICES Programs
F-IS-46 The solution may have the ability to record and maintain Health Needs Requests 3 REQUEST AND GRIEVANCES Programs
(IINRs).
Work Release/Work Furlough
F-IS-47 The solution shall have the ability to assign an inmate as on Work Furlough or Work 0 Roadmap Workflow Release 2.5 PROGRAMS & SERVICES Detention - housing
Release.
F-IS-48 The solution shall have the ability to record, track and maintain entry and exit of an 0 Roadmap 'Workflow Release 2_5 PROGRAMS & SERVICES Detention - housing
inmate assigned to Work Furlough or Work Release.
F-IS-49 The solution may have the ability to automatically trigger an incident report according 3 EVENT LOGS
to specific business rules and workflow.
F-IS-50 The solution may have the ability to automatically notify the court of non-compliance. 3 MESSAGING Detention - housing
F-IS-5I The solution shall have the ability to generate work assignments. 0 Roadmap Workflow Release 2,5 PROGRAMS & SERVICES Detention - housing
F-IS-52 The solution shall have the ability to generate rosters. 0 Roadmap Workflow Release 2.5 PROGRAMS & SERVICES Detention - housing
Self-Surrenders
F-IS-53 The solution may have the capability to log and maintain self-surrenders that are 0 Roadmap Workflow Release 3,0 ARRESTS & WARRANTS (PRE- Detention - housing
refused. BOOK)
F-IS-54 The solution shall have the capability to record and maintain whether an inmate is a 0 Roadmap Workflow Release 3,0 ARRESTS & WARRANTS (PRE- Detention - housing
self-surrender. BOOK)
F-IS-55 The solution shall record and maintain date and time of self-surrender. 0 Roadmap Workflow Release 3,0 ARRESTS & WARRANTS (PRE- Detention - housing
BOOK)
—
F-IS-56 The solution may have the ability to report self-surrenders by court. 0 Roadmap Workflow Release 3.0 ARRESTS & WARRANTS (PRE- Detention - housing
BOOK)
F-IS-57 The solution may have the ability to report rejected self-surrenders by reason back to 0 Roadmap Workflow Release 3.0 ARRESTS & WARRANTS (PRE- Detention - housing
the court. BOOK)
Central Mailroom

SERIAL 13139-RFP
F-IS-58 The solution may have the ability to track incoming mail. 0 Roadmap Workflow Release 3.5 INMATE CORRESPONDENCE Detention - Housing
F-15-59 The solution may have the ability to track the source of inmate fund deposits such as 3 TRUST ACCOUNTING Budget/Finance
received and deposited by Central Mailromn.
F-IS-60 The solution shall track "return to sender' mail issued by mailroom by date and return 0 Roadmap Workflow Release 3,5 INMATE CORRESPONDENCE Detention - Housing
addressee.
JO - Jail Operations Requirements
F-JO-1 The solution shall provide the ability to log events with a date and time stamp including 3 EVENT LOGS Operations Journal
duration (from/through).
F JO 2 P.LENT--LOGS- Operations Journal
F-JO-3 The solution shall log the arrival of meals in the housing unit 3 EVENT LOGS Operations Journal
F-J0-4 The solution shall log the time a meal distribution to inmates in the housing unit. 3 EVENT LOGS Operations Journal
E-10-5 The solution shall log the security walks and send alerts when it is time. 3 EVENT LOGS Operations Journal
F-JO-6 The solution shall log the inmate requests for additional hygiene items. 3 - REQUEST AND GRIEVANCES Operations Journal
F-JO-7 The solution shall log the dayroom access, including beginning and end time. 3 EVENT LOGS Operations Journal
F-JO-8 The solution shall log the recreation access, including beginning and end time. 3 EVENT LOGS Operations Journal
F-JO-9 The solution shall log inmate medical appointments (internal and external). 3 MOVEMENTS Operations Journal
F-JO-10 The solution shall log inmate releases (kick outs). 3 ADMISSION/TRANSFER/RELEA Operations Journal
SE
F-J0-11 The solution shall log the PREA inspections. 3 EVENT LOGS Operations Journal
F-JO-I2 The solution shall log the canteen arrival, 3 EVENT LOGS Operations Journal
The solution shall log the canteen distribution. 3 EVENT LOGS Operations Journal

SERIAL 13139-RFP
F-JO-13 The solution shall tog the arrival and distribution of library delivery. 3 EVENT LOGS Operations Journal
F-JO-14 The solution shall log the time of the safety inspections. 3 EVENT LOGS Operations Journal
F-10-15 The solution shalt log the time of hygiene distribution. 3 EVENT LOGS Operations Journal
F-JO- I 6 The solution shall record the time for all call for programs. 3 PROGRAMS & SERVICES Operations Journal
F-J -17 The solution shall record the time of the grievance walks. 3 EVENT LOGS Operations Journal
F-JO-I8 The solution shall log the individual special management (e.g., close custody) inmate 0 Roadmap Workflow Release 3.5 CASE MANAGEMENT Operations Journal
hour outs.
F-JO-I9 The solution shall tog the housecleaning (showers or dayroom). 3 EVENT LOGS Operations Journal
F-J0-20 The solution shalt log when other staff are in the housing unit. 3 EVENT LOGS Operations Journal
F-JO-2I The solution shall log the time of the PREA announcements. 3 EVENT LOGS Operations Journal
F-J0-22 The solution shall log the inmate visitations. 3 VISITATION Operations Journal
F-J0-23 The solution shalt log the cell searches. 3 EVENT LOGS Operations Journal
F-JO-24 The solution shalt log the distribution of laundry. 3 EVENT LOGS Operations Journal
F-J0-25 The solution shall record and log the suicide watches. 3 EVENT LOGS Operations Journal
F-J0-26 The solution shall record the distribution of laundry/clothing to inmates. 3 EVENT LOGS Operations Journal
F-J0-27 The solution shall record the Laundry/clothing assigned per active booking number. 0 Roadmap Workflow Release 4.5 CLOTHING ISSUE N/A
F-J0-28 The solution shall track special diet requests for each inmate. 3 DIETARY/MEAL PLANNING NIA

SERIAL 13139-RFP
F-70-29 The solution shall record the approval/denial of special diet requests for the inmate. 3 DIETARY/MEAL PLANNING N/A
F-70-30 The solution shall report the special diet requests by cell/pod/dorm/facility. 3 DIETARY/MEAL PLANNING N/A
F-.10-31 The solution shall record and track daily jail statistics. 3 REPORTING/BYWORD Reporting
PROCESSING
F40-32 The solution all record and track weekly jail statistics. 3 REPORTING/BYWORD Reporting
PROCESSING
F-J0-33 The solution shall record and track monthly jail statistics. a REPORTING/BYWORD Reporting
PROCESSING
F-30-34 The solution shall record and track annual jail statistics. 3 REPORTING/BYWORD Reporting
PROCESSING
F40-35 The solution shall record facility count. 3 Counts
F-J0-36 The solution shall record facility count, number of transfers and releases, medical 1 Enhancement REPORTING/BYWORD Reporting
statistics, visitation statistics, incidents, and recreation offered, accepted and refused PROCESSING
(by facility and inmate). Line 19
in Attachment A Cost Proposal
F40-37 The solution shall provide an event or shift log as a means of recording shift activity. 3 EVENT LOGS Operations Journal
F-10-38 The solution shall record shift start and end times. 3 EVENT LOGS Operations Journal
F-J0-39 The solution shall provide the ability to capture shift inventory items such as, but not 3 EVENT LOGS Operations Journal
limited to guns, ammo, radios, handcuffs, keys, pepper spray, etc.
F-70-40 The solution shall provide message and notification forwarding to next shift. 3 EVENT LOGS Operations Journal
F-JO-41 The solution shall provide the ability to ensure that defined entries cannot be edited 3 EVENT LOGS Operations Journal
after entry based on business rules. See Business Rules requirements.
F-J0-42 The solution shall provide the ability to link comments and events. 3 EVENT LOGS Operations Journal
F-J0-43 The solution shall provide the ability to search and query entries based on filter such as, 3 All Operations Journal
but not limited top Booking Number, Facility, Officer, Activity Type, Body of Text.
F-70-44 The solution shall provide the ability to implement predefined logging (templates). 3 EVENT LOGS Operations Journal

SERIAL 13139-RFP
F-JO-45 The solution shall log duration of events. 3 EVENT LOGS Operations Journal
F-J0-46 The solution shall log general distribution not associated with specific individual. 3 EVENT LOGS Operations Journal
F-1047 The solution may provide the ability to automate the capture the date, time and person I GAP EVENT LOGS Operations Journal
ID of an event such as an observation task via reader.
Workflow provides the ability to
capture information using devices such
as barcode readers.
It was learned during the gap analysis
session that the intention of this
requirement was to provide a more
robust event tracking system whereby
a device is used for recording the
security checks performed by officers.
The officer will log on to one of the
devices and begin his security check
rounds, scanning the security check
point barcodes along his route. The
records of b is scans would show the
order in which he walked his route, and
at what time he scanned each
checkpoint When the officer
completes his rounds he can upload the
collected information to TIVIS.
Workflow will enable users to record
the results of security checks and other
welfare checks in the system in Phase
I. This extension, if approved, will be
tentatively scheduled for Release 4.5 —
Project Release 2.2
Line 58
in Attachment A Cost Proposal
_, - I) N/A
Costly Requirement;
F-J0-49 The solution shall provide the ability to log a cross gender announcement by dateitime. 3 EVENT LOGS Operations Journal
F-J0-50 The solution shall provide open entry capability for non standard visits such as, but not 3 EVENT LOGS Operations Journal
limited to the annual tire marshal visit.
F-JO-51 The solution shall provide the ability for an officer identify to himself and unit upon 3 SECURITY MODEL/LOAF Non-Functional
sign in. Requirements /
Operations Journal
F-30-52 The solution shall provide inquiry capabilities that bring up all entries on an inmate. 3 ALL Reporting
F-J0-53 The solution shall provide the ability to log and track suicide observations. 3 EVENT LOGS Operations Journal

SERIAL 13I39-RFP
F-JO-54 The solution shall provide the ability to log overages/shortages from canteen to inmate. 3 COMMISSARY Canteen/OJ
F-J0-55 The solution may provide the ability to generate a cell search query to determine a 3 REPORTING/BYWORD Reporting
random cell search list. PROCESSING
F-10-56 The solution shall provide the ability to alert and log temperature readings for housing 3 EVENT LOGS Operations Journal
units.
MV - Movements Requirements
F-MV-1 The solution shall monitor and track inmate movement between the jail facilities. 3 MOVEMENTS Transportation 1
F-MV-2 The solution shall provide real time recording of an inmate's departure or arrival at any 3 MOVEMENTS Transportation /
number of user defined locations throughout MCSO facilities.
F-MV-3 The solution shall provide the capability for inmate tracking or interface with a 3 ' Transportation I
commercial off the shelf application.
F-MV-4 The solution shall provide the ability to detect an inmate's keep-away prior to the 3 MOVEMENTS Transportation /
inmate moving to that location.
F-MV-5 The solution shall record and maintain the history of all inmate movements (inmate, 3 MOVEMENTS Transportation /
date and time, location).
F-MV-6 The solution shall provide the ability to record the movement of a group of inmates. 3 MOVEMENTS Transportation /
F-MV-7 The solution shall allow for the time between when an inmate departs one location and 3 MOVEMENTS Transportation /
arrives at the destination, known as "on the move" or "in transit'.
F-MV-8 The solution shall provide a single and/or group workflow message to the arrival 3 MESSAGING Transportation /
location for any transported inmate. Workflow
F-MV-9 The solution shall provide the ability to display and/or print movement documents 3 REPORTING/BYWORD Transportation /
including, but not limited to: departure location; destination location; and anticipated PROCESSING Reporting
arrival time.
F-MV-10 The solution shall provide the ability to record the non-scheduled movement of 3 MOVEMENTS Transportation/
inmates. Note: if inmate is not checked out from the prior location then the solution
shall provide an alert that an inmate has not been checked out at the time of check in at
the new location.
F-MV-11 The solution shall provide the ability for the facility to define all inmate locations and 0 Roadmap Workflow Release 4.0 MOVEMENTS Transportation /
specify transit times from one location to another.
F-MV-12 The solution shall provide the ability to query and print an inmate's movement 3 REPORTING/131/WORD Reporting/Moves
information. PROCESSING
F-MV-13 The solution shall ensure that all movement is integrated with the count feature to 3 COUNTS Transportation /
facilitate accurate count of inmates at all locations.

SERIAL 13139-RFP
F-MV-14 The solution shall provide the ability to produce, view and/or print reports to include 3 REPORTING/BYWORD Reporting/Moves
movement schedules. PROCESSING
_
F-MV-15 The solution shall pull information about an inmate's appointments to create 3 MOVEMENTS Workflow/Moves
corresponding workflows based on appointment type. See Business Rules
Requirements.
F-MV-I6 The solution may allow for entry of movement reason to accommodate mass movement 3 MOVEMENTS Transportation
such as court transport.
F-MV-17 The solution may have the ability to maintain an attribute status regarding an inmate's 3 ALL Programs/Moves
specific custody status such as, but not limited to, attending a religious program, in a
medical appointment, etc.
F-MV-I 8 The solution shall provide the ability to receive inmate medical transportation requests 1 Custom Interface Transportation /
electronically via CRS data exchange. Reporting
F-MV-I9 The solution shall provide a daily transportation list for court, medical appointments, 3 REPORTING/BE/WORD Transportation
religious program attendance, etc. electronically, PROCESSING
F-MV-20 The solution shall provide the ability for transportation staff to enter a trip requested by 0 Roadmap Workflow Release 4.0 TRANSPORTATION Transportation
equipment services into the transportation function.
P-MV-21 The solution shall provide the ability for the transportation staff to check in inmates for 0 Roadmap Workflow Release 4,0 TRANSPORTATION Transportation
a scheduled trip.
P-MV-22 The solution shall provide the ability to print individual movement documents for 3 REPORTING/131/WORD Moves/Reporting
inmates. The movement document will include a photograph, demographic detail, PROCESSING
classification and movement information. The movement document should also
include 'Precautionary information" - SRT, Medical, restraining order, "keep-away".
E-MV-23 The solution shall be configurable by facility. 3 MOVEMENTS Non-Functional
Requirements
P-MV-24 The solution shall provide the ability to display movement information on mobile 3 MOVEMENTS Non-Functional
devices. Requirements
F-MV-25 The solution shall provide the ability to print court cards individually and in batch, 3 MOVEMENTS Non-Functional
Requirements
F-MV-26 The solution shall provide the ability to enter a movement reason code. 3 MOVEMENTS Transportation
F-MV-27 The solution shall provide the ability to accommodate the tracking of movement to 3 MOVEMENTS Transportation
locations and/or facilities that are external such as hospitals.
PG - Programs Requirements
ALPHA
F-PG-1 The solution shall be able to create and maintain eligible inmate lists. 0 Roadmap Workflow Release 3.0 PROGRAMS & SERVICES Programs

SERIAL 13139-RFT
F PG-2 0 During on site gap analysis this PROGRAMS & SERVICES Progr-ams
longer necerzary
F-PG-3 The solution shall be able to track and report inmate discipline history while in 3 PROGRAMS & SERVICES Programs
program.
F-PG-4 The solution shall be able to track needs assessment history. 3 ASSESSMENTS & Programs
CLASSIFICATION
F-PG-5 The solution shall be able to track beginning and end dates of each ALPHA program. 0 Roadmap Workflow Release 3.0 PROGRAMS & SERVICES Programs
F-PG-6 The solution shall provide alerts for scheduling conflicts. 3 PROGRAMS & SERVICES Programs /
Scheduling
Worship and Faith Based
F-PG-7 The solution shall be able to track inmate requests for participation. 3 PROGRAMS & SERVICES Programs
F-PG-/1 The solution shall be able to differentiate between Worship and Faith Based programs, 3 PROGRAMS & SERVICES Programs
F-PG-9 The solution shall be able to enroll an inmate into a program. 3 PROGRAMS & SERVICES Programs
F-PG-I0 The solution shall be able to create and manage program rosters. 3 PROGRAMS & SERVICES Programs
F-PG-II The solution shall be able to create and manage a wait list, 3 PROGRAMS & SERVICES Programs
F-PG-I3 The solution shall be able to programmatically calculate recidivism based on specific 3 Reporting/BI/Word Processing Reporting
pre-defined criteria.
F-PG-I4 The solution shall provide a way to differentiate between all-call and other services. 3 PROGRAMS & SERVICES Programs
F-PG-I5 The solution may provide a way to maintain religious preference, 3 PROGRAMS & SERVICES Intake/ Programs
F-PG-16 The solution shall provide a way to track religious based inmate grievances. 3 REQUEST AND GRIEVANCES Detention - Hearing
Unit / Programs
F-PG-17 The solution shall provide a way to designate multiple dietary restrictions (may have 0 Roadmap Workflow Release 3,5 DIETARY/MEAL PLANNING N/A
religious diet but he diabetic).
MASH
F-PG-18 The solution shall provide the capability to enter notes/comments specific to programs. 3 PROGRAMS & SERVICES Programs
F-PG-19 The solution shall provide an alert when an inmate requests program participation. 0 Roadmap Workflow Release 3.5 PROGRAMS & SERVICES Programs
F-PG-20 The solution shall be able to display and maintain inmate restrictions. 0 Roadmap Workflow Release 3.5 PROGRAMS & SERVICES Programs

SERIAL 13139-RFP
Education
F-PO-21 The solution shall track and manage educational services, including creating and 3 PROGRAMS & SERVICES Programs
storing electronic education records.
F PG 22 The solution shall record Education tecting results (e.g. TABS ncoros) and make This requirement can be removed a.,-, PROGRAMS & SERVICES Pregmins
available to all programs authorized users. part of F PG 24
F-PG-23 The solution shall provide electronic notification to Education Services when a juvenile 3 MESSAGING Workflow
(under the age of 18) or a special education inmate (up to age 22) is booked into one of
the IVICSO jails. See Workflow Requirements.
F-PG-44 - 7. ._77-...-77 7 7-,-77-:... Custom Inderface - Programs
tracking,
F-PG-25 The solution shall provide access to hearing information and results real time. 3 PROGRAMS & SERVICES Programs
F-PG-26 The solution shall provide system wide access to the inmate's schedule (control shall be 3 MOVEMENTS Scheduling
able to know who is going to school and in school, and the school shall know if a
student has a medical or court appointment). See Scheduling Requirements,
F-PG-27 The solution may provide electronic attendance tracking. 3 PROGRAMS & SERVICES Programs
Volunteer
F-PG-28 The solution shall provide a way to track volunteers, including demographic 3 FOUNDATION (MASTER Programs
information. INDICES)
F-PG-29 The solution shall provide a way to track if badges have been issued, are about to I Enhancement PROGRAMS & SERVICES Programs
expire, or have expired and automatically notify the volunteer.
Line 21
in Attachment A Cost Proposal

SERIAL 13139-RFT
F-PG-30 The solution shall provide a way to schedule volunteers and track hours worked by I Roadmap Workflow 3,0 PROGRAMS & SERVICES Programs
logging hours in and hours out of facilities. GAPh was learned during the
Programs on-site gap analysis that it is
necessary to track both the time to
process a volunteer in and out of a
facility as well as the productive actual
"volunteer" time. This provides jail
staff with the information required to
facilitate more timely in and out
processing when issues occur. The
volunteer hours are also reported to the
federal government Workflow does
not track staff or volunteer scheduling
or movement. It would be difficult for
Workflow to identify the time to
process a volunteer in and out of a
facility as it is not designed to track
staff scheduling or movement. It was
discussed that this may be something
that the ADP staff solution may
provide. The hours that volunteers are
associated to a program schedule can
be tracked and reported.
Not Quoted
F-PG-3 I The solution shall provide a way to schedule events. 3 PROGRAMS & SERVICES Programs
F-PG-32 The solution shall provide a way to monitor background check progress. 3 Enhancement Custom field Programs
F-PG-33 The solution shall provide a way to systematically move a volunteer to the next step in 3 Enhauvement-Custom field Programs
the process.
F-PG-34 The solution shall provide a way to distinguish between volunteers and contractors. 3 FOUNDATION (MASTER Programs
INDICES)
F-PG-35 The solution shall provide the ability to report volunteers by schedule. 3 Enhancement FOUNDATION (MASTER Programs
Agreed that this could be accomplished INDICES)
by way of a report
Adult Inmate Programs
F-PG-36 The solution shall provide the ability to maintain a list of programs available to 3 PROGRAMS & SERVICES Programs
inmates.
F-PG-37 The solution shall provide the ability to assign inmates to programs. 3 PROGRAMS & SERVICES Programs
F-PG-38 The solution shall provide the ability to create and maintain a waiting list for individual 3 PROGRAMS & SERVICES Programs
programs.
F-PG-39 The solution shall provide the ability to generate a roster for each program. 3 PROGRAMS 8c SERVICES Programs
F-PG-40 The solution shall provide automated time and attendance/participation tracking in each 3 PROGRAMS & SERVICES Programs
program by, but not limited to, program, inmate, instructor, class, date, facility.

SERIAL 13139-RFP
F-PG-41 The solution shall provide the ability to review and approve/deny inmate requests for 3 PROGRAMS & SERVICES Programs
program participation.
F-PG-42 The solution shall maintain program and session characteristics (e.g. facility location, 3 PROGRAMS & SERVICES Programs
instructor/facilitator, room location, capacity).
F-PG-43 The solution shall keep a history of programs the inmate has participated in with the 3 PROGRAMS & SERVICES Programs
outcome.
F-PG-44 The solution shall provide the ability to calculate recidivism rates bases on business 0 REPORTING/BI/WORD Programs
rules and parameters on inmate populations that have completed and/or participated in Roadmap Q4/2015 - This date has been PROCESSING/DATA
programs. changed to reflect the anticipated WAREHOUSE
availability of data warehouse
functionality.
Roadmap Workflow Release 3.5
F-PG-45 The solution shall provide an automated notification that an inmate has been moved so 3 ALL Programs
they have correct bed numbers for identification purposes.
F-PG-46 The solution shall be able to provide inmate eligibility based on a defined set of 3 PROGRAMS & SERVICES Programs
business rules.
F-PG-47 The solution shall be able to schedule each program. 3 PROGRAMS & SERVICES Programs
F-PG-48 The solution shall be able to schedule inmate participation. 3 PROGRAMS & SERVICES Programs
F-PG-49 The solution shall be able to discern between mandatory and voluntary programs. 3 PROGRAMS & SERVICES Programs
F-PG-50 The solution shall be able to determine inmate eligibility based on proxy score calculate 0 Roadmap Workflow Release 3.5 PROGRAMS & SERVICES Programs
based on a defined business rules.
F-PG-51 The solution shall be able to archive rosters. 0 PROGRAMS & SERVICES Programs
Gestly-Requirements
Archiving is not a need anymore
F-PG-52 The solution shall be able to track rosters back to recidivism. 0 Roadmap Q412015 - This date has been PROGRAMS & SERVICES Programs
changed to reflect the anticipated
availability of data warehouse
functionality.
Roadmap Workflow Release 3,5
F4G-53 The solution shall provide a way to alert for violent tendencies, keep-aways, and other 3 PROGRAMS & SERVICES Programs
defined characteristics.
F'-PG-54 The solution shall provide a way to electronically omit/ the housing unit that an inmate 0 Roadmap Workflow Release 3.5 PROGRAMS & SERVICES Programs
is enrolled in a program and provide ongoing scheduling information.
F-PG-55 The solution shall provide a way to communicate program assignment information to 3 PROGRAMS & SERVICES Programs
staff, inmate, housing unit and transportation.

SERIAL 1M39-RFP
F-PG-56 The solution shall provide a way to present alerts when an inmate's classification 3 PROGRAMS & SERVICES Programs
changes, housing changes or disciplinary action has occurred.
F-PG-57 The solution shall be able to track beginning and end dates of each program. 3 PROGRAMS & SERVICES Programs
F-PG-58 The solution shall be able to display an inmate's probation officer information (if an 3 CASE MANAGEMENT Programs
inmate has been in custody for 60 days, they are assigned an internal probation officer,
as opposed to a field probation officer),
F-PG-59 The solution shall be able to track participation in all programs electronically by, but 3 PROGRAMS & SERVICES Programs
not limited to, program, instructor, class, inmate.
F-PG-60 The solution shall provide the ability to log, track and report on program status for man 3 PROGRAMS & SERVICES Programs
inmate such as, but not limited to completed, dropped, released.
PR - Property and Clothing Requirements
F-PR-1 The solution shall record and maintain an inventory of inmate's property/clothing such I GAPThis PROPERTY Intake
as, but not limited to, property, type, attributes, location, staff comments, chain of requirement was discussed during the
possession. Intake gap analysis sessions The
system does not currently provide the
structure for property to support this
concept of scanning or recording the
precise location, ie. chain of
possession, of property as it is
transported. Rather, Workflow allows
property to be tracked by location, It is
further not possible to look up the last
known location for a property item.
This would need to include chain of
custody through from the point of
arrest, (pre-book) through release from
jail The ability to track the location of
property at any given time is what is
required. This means that every
possible place that property can be
must have the ability to be recorded,
MCSO has a strong interest in the
scanning by bareode or possibly RFID
as an option in the future. Additionally,
the need to identify who had
possession of the property at each
location (to support evidentiary chain
of custody) is required. The functional
requirements for this level of detailed
property tracking; ie. Chain of
possession, need to be gathered This
is an extension that will be designed
and developed if MCSO decides to
proceed with this extension and is
tentatively planned for Workflow
Release 3.5 — Project Release 1.3Line
60in Attachment A Cost Proposal
F-FR-12 is alternative

SERIAL 13139-RFP
F-PR-2 The solution shall create a list of property/clothing received from an inmate at intake. 3 PROPERTY Intake
F-PR-3 The solution shall print an inmate property/clothing receipt which shall include but not 3 REPORTING/El/WORD Intake
be limited to, inmate's name, booking number, property list/description, arresting PROCESSING
officer/agency, storage location, bamode, booking date/time.
F-PR-4 The solution shall record the status of the inmate property/clothing (storage location, 3 PROPERTY Intake
released, taken for evidence).
F-PR-5 The solution shall provide the ability to add/remove/release impounded items to/from 3 PROPERTY Intake
an inmate's property/clothing inventory.
F-PR-6 The solution shall provide the ability to approve/deny an inmate's request for release of 3 REQUEST AND GRIEVANCES Intake
property/clothing to a third party.
F-PR-7 1- The solution shall provide the ability to release an inmates property/clothing to a third 3 PROPERTY Intake
party and record details from the third party's identification (e.g. driver's license
number).
F-PR-8 The solution shall record the replacement value of property/clothing or compensation in 1 GAPThis PROPERTY Intake
case of loss (at time of loss or claim form being filed). requirement was discussed during the
Intake gap analysis session. The
original understanding of this
requirement was that a grievance can
be filed, by an inmate for a loss of
property. During the gap analysis
session for Intake, it was learned that a
property claim is considered to be a
distinct item that may be linked to a
grievance. MCSO need the ability to
create a property claim for an inmate
who is no longer in custody (inactive).
A new product extension to allow users
to generate property and loss claims
that may he linked to a request /
grievance will be developed upon
MCSO decision to proceed with this
gap. This extension will include the
ability to record lost property and
found property that is not associated to
a particular inmate or person.
Tentatively scheduled for Workflow
Release 3.5— Project Release I.3Line
61in Attachment A Cost Proposal
See also F-PR-10 and F-PR-I 1
F-PR-9 The solution shall provide the ability to record the Facility and locker number where 3 PROPERTY Intake
property/clothing is stored.
F-PR-10 The solution shall provide the ability to create a list of lost and found property/clothing 1 See F-PR-8 PROPERTY Intake
items.

SERIAL 13139-REP
F-PR-I 1 The solution shall provide the ability to track inmate claims for lost property/clothing. See F-PR-8 REQUEST AND GRIEVANCES Intake
F-PR-12 The solution may provide the ability to provide support for RFID or Barcode 1 GAPThis Intake
technology to track inmate property/clothing and/or impounded property, requirement was discussed during the
Intake gap analysis session. The
Workflow solution does have the
ability to support the use of barcode
scanning for the purposes of tracking
property. There is a gap, however, in
enabling the property screens to
facilitate the use of scanners. This
extension will provide the ability to
fully process the property using
scanning technology. This gap is
priced separately from F-PR-I in the
event that the gap in F-PR-1 does not
get approved. If F-PR-I does get
approved, this gap will no longer be in
effect. Line 64th Attachment A Cost
Proposal
F-PR-13 The solution may provide the ability to store and retrieve a signed electronic copy of 3 REPORTING/131/WORD Reporting
the inmate's property disposition requests. PROCESSING
F-PR-14 The solution shall provide the ability to track in-cell property per inmate. 3 PROPERTY Intake
RE - Release Requirements
F-RE-1 The solution shall provide for notifications when an inmate is scheduled for release 3 ADMISSION/TRANSFER/RELEA Workflow / Release
based on business rules. SE
F-RE-2 The solution shall provide an automatic search for open holds, warrants, and detainers 3 ADMISSION/TRANSFER/RELEA Release
prior to release. SE
F-RE-3 The solution shall provide a report of those inmates scheduled for release. 3 Reporting/BT./Word Processing Reporting / Release
F-RE-4 The solution shall provide a means to check for disposition on all pending charges for 3 COURT ORDERS/LEGAL Release
an inmate, DOCUMENTS
F-RE-5 The solution shall provides biometric fingerprint check to verify the identity of all 3 BIOMETRICS Release
inmates prior to release. [FINGERPRINT/IMAGING)
F-RE-6 The solution shall provide the ability to record that an inmate's property and/or clothing 3 PROPERTY Release
were returned.
F-RE-7 The solution shall provide the means to verify the inmate fund account balance prior to 3 TRUST ACCOUNTING Release /
release. Budget/Finance
,
F.-RE-8 The solution shall be able to interface with the Financial system to notify that an inmate 3 TRUST ACCOUNTING Release/Budget/Fina
is scheduled for release (Financial System will generate debit card with remaining fund nce / Workflow
balance).

SERIAL 13139-RFP
F RE 9 I The solution shall notify VANU when an inmate is scheduled to be released per GAPThis MESSAGING Wer-leglow
workflow requirements.
Release gap analysis session. Currently
prematurely duo to the timint for the
release notification which means the
victim has to be notified a second time
if something is found that will keep the
inmate detained. MCSO would like a
way to inform Victim Services once
the release has been confirmed. This
may be considered a new requirement
since it rotates to Victim Services.
During the releases session there was a
lot of discussion around ensuring that
the inmate net he released until victim
notification occurred. It is
that will allow VANU to indicate that
the notification to the victim has
See also F-CT-98
F-RE-10 The solution shalt automatically update the bed/cell/dorm/facility status to indicate a 3 ADMISSION/TRANSFERIRELEA Release
vacancy as an inmate goes through the release process. SE
F-RE-11 The solution shall automatically update the facility count to indicate an inmate has been 3 ADMISSION/TRANSFER/RELEA Release
released. SE
F-RE-12 The solution shall record the condition and reason for release, including but not limited 3 ADM1SSION/TRANSFER/RELEA Release
to: bonded out, released to own recognizance, released to electronic monitoring, SE
released to other agency, released to DOC.
F-RE-13 The solution shall provide an alert if the inmate is to receive electronic monitoring prior 3 ADMISSION/TRANSFER/RELEA Release
to release. SE
F-RE-14 The solution shall provide an alert if there is a "file stop" prior to release, to notify the 3 ADMISS1ON/TRANSFER/RELEA Release / SIMS
requesting authority. SE
F-RE-15 The solution may provide the ability to capture a photograph at release. 3 BIOMETRICS Release
[FINGERPRINT/IMAGING]
F-RE-16 The solution shall record the date and time of inmate release as well as 3 ADMISSION/TRANSFER/RELEA Release
officer/supervisor authorization. SE
F-RE-17 The solution shall provide an alert to transportation that an inmate is pending release 3 MESSAGING Release/ Workflow

SERIAL 13139-RFP
F-RE-I8 The solution shall abide by special business rules associated with release of juveniles. 3 ADMISSION/TRANSFER/RELEA Release
SE
F-RE-I9 The solution shall provide the ability to query DNA and fingerprint data by facility and 3 REPORTING/BYWORD Reporting / Release
unit sortable by projected release date. PROCESSING
F-RE-20 The solution shall provide the ability to query upcoming releases by date, facility and 3 REPORTING/BI/WORD Reporting / Release
inmate of those that have refused fingerprints and DNA. PROCESSING
F-RE-21 The solution shall provide the ability to present an alert if DNA is needed. 3 MESSAGING Workflow / Release
RP - Reporting Requirements
F-RP-1 The solution shall control access to MCSO standard reports based on solution security 3 REPORTING/BYWORD Reporting
access rules. PROCESSING
F-RP-2 The solution shall control the creation of MCSO end-user reports based on solution 3 REPORTING/RI/WORD Reporting
security access rules. PROCESSING
F-RP-3 The solution shall provide the ability to produce jail-cost modeling analysis reports. 0 Roadtnap Q4/20 t 5 - This date has been REPORTING/BI/WORD Reporting
changed to reflect the anticipated PROCESSING
availability of data warehouse
functionality.
F-RP-4 The solution shall provide the ability to create custom MCSO end-user reports on all 3 REPORTING/BYWORD Reporting
data fields stored in the solution. PROCESSING
F-RP-5 The solution shall provide the capability to create an audit report from the solution 3 REPORTING/BYWORD Reporting
history logs containing information regarding what information was last opened or PROCESSING
edited within the Solution.
F-RP-6 The solution shall produce reports in multiple formats (e.g. PDF, fiat file, excel). 3 REPORTING/BYWORD Reporting
PROCESSING
F-RP-7 The solution shall provide the capability to schedule specific reporting jobs. 3 REPORTING/BYWORD Reporting
PROCESSING
F-RP-8 The solution shall provide the capability to direct a report output to the following but 3 REPORTING/BYWORD Reporting
not limited to: file location, ftp, e-mail, or designated printer. PROCESSING
F-RP-9 The solution shall provide the capability to sort end-user reports by MCSO Division. 3 REPORTING/I31/WORD Reporting
PROCESSING
F-RP-10 The solution shall display and report workflow status by queue, assigned user, date 3 REPORTING/BYWORD Reporting
range, past due tasks, formation status by workflow, date range. PROCESSING
F-RP-11 The solution shall provide the capability to create end-user defined key performance 3 REPORTING/BYWORD Reporting
indicators reports by date range, PROCESSING

SERIAL 13139-RFP
F-RP-12 The solution shall provide a user with the appropriate solution security, the ability to 3 REPORTING/BYWORD Reporting
create ad-hoc reports from all data stored within in the solution using third party PROCESSING
commercial off the shelf tools.
F-RP-13 The solution shall provide an online screen to allow the authorized users the ability to 3 REPORTING/BI/WORD Reporting
print statistical reports. PROCESSING
F-RP-14 The solution shall provide equivalents for all existing management reports currently in 1 Enhancement REPORTING/BI/WORD Reporting
use by the jail. See Exhibit 9 - Report, Queries and Messages and Exhibit 11 - Bidder's PROCESSING
Library for additional information. Line 22
in Attachment A Cost Proposal
F-RP-15 The solution may be capable of producing graphical summaries (pie charts, line graphs) 3 REPORTING/BYWORD Reporting
for statistical reports. PROCESSING
F-RP-I6 The solution shall provide standard date range filters for all reports (daily, weekly, 3 REPORTING/BYWORD Reporting
monthly, yearly, from-to range). PROCESSING
F-RP-17 The solution shall provide ad-hoc reporting capability to provide management statistics 0 Roadmap Q4/2015 - This date has been REPORTING/BYWORD Reporting
including the following but not limited to: inmate, race, gender, gang status, medical changed to reflect the anticipated PROCESSING
status, cell, facility, movements, all classification criteria, mitt/max sentencing availability of data warehouse
predictions, forecasting, total inmate population by cell, area, facility, etc. functionality.
F-RP-1S The solution shall provide statistical reports for the following but not limited to: arrests 0 Roadrnap Q4/2015 - This date has been REPORTING/BYWORD Reporting
and bookings by agency, type, date, time, charge, city of residence, percent of inmates changed to reflect the anticipated PROCESSING
in custody by (defined field), number of bookings by shift, by facility, by ethnicity, availability of data warehouse
ranges for booking recaps, arrest recaps, etc. functionality.
F-RP-19 The solution shall provide dashboards with metrics of interest to the command staff. 0 Roadmap Q4/20I5 - This date has been REPORTING/BYWORD Reporting
The solution shall provide summary statistical information about the performance, changed to reflect the anticipated PROCESSING
capacity, and other key performance indicators in an easy visual display. availability of data warehouse
functionality.
F-RP-20 The solution shall provide for report group notifications and electronic mailings to 3 REPORTING/BYWORD Reporting
specified users. PROCESSING
F-RP-21 The solution shall provide a printout of an inmate record summary. This includes basic 3 REPORTING/BI/WORD Reporting
information about an inmate and all transactions / events and forms for that inmate. PROCESSING
F-RP-22 The solution shall provide a release summary that can to be printed. See Exhibit II - 3 REPORTING/BYWORD Reporting
Bidder's Library. PROCESSING
F-RP-23 The solution shall provide a list of current inmates with key identifying data that can be 3 REPORTING/BI/WORD Reporting
printed. PROCESSING
F-RP-24 The solution shall have an inmate database that can be queried, filtered, sorted, and 3 REPORTING/BYWORD Reporting
allow results to be printed. PROCESSING
F-RP-25 The solution has restrict access to the report generator and individual reports via 3 REPORTING/131/WORD Reporting
permission-based by user or user group. PROCESSING

SERIAL 13139-RFP
F-RP-26 The solution's report generator shall allow users to include in a report any data entered 3 REPORTING/BYWORD Reporting
into the jail management solution. PROCESSING
F-RP-27 The solution shall provide the user control over layout decisions such as field 3 REPORTING/BYWORD Reporting
arrangement, column width, label text, font size, line spacing, etc. PROCESSING
F-RP-28 The solution shall provide the ability for data on reports to be grouped or sorted by any 3 REPORTING/BYWORD Reporting
data element. PROCESSING
F-RP-29 The solution shall provide the ability for multiple data filters to be applied using and/or 3 REPORTING/BYWORD Reporting
logic. PROCESSING
F-RP-30 The reporting solution may include "Google-like" searching of case narratives and all 3 REPORTING/BYWORD Reporting
other narrative fields. PROCESSING
F-RP-31 The solution shall allow for statistical analysis and comparison of data over time 0 Road/nap Q4/2015 - This date has been REPORTING/BYWORD Reporting
periods between demographic groups, etc. changed to reflect the anticipated PROCESSING
availability of data warehouse
functionality.
F-RP-32 The solution shall allow for statistical analysis and comparison of data calculated at a 0 Roadinap Q4/2015 - This date has been REPORTING/BYWORD Reporting
point in time and stored, changed to reflect the anticipated PROCESSING
availability of data warehouse
functionality.
F-RP-33 The solution shall provide the ability for reports to be exported to PDF or Excel. 3 REPORTING/BYWORD Reporting
PROCESSING
F-RP-34 When creating a standard report, the user shall have the ability to choose which users 3 REPORTING/BYWORD Reporting
can access, run, or modify the report. PROCESSING
F-RP-35 The solution shall provide the capability for recurring reports to be scheduled and 3 REPORTING/BYWORD Reporting
uploaded to a file share or e-mailed to specified users on specific days and times. PROCESSING
F-RP-36 A user with sufficient permission shall be able to generate a variety of reports including 3 REPORTING/III/WORD Repotting
at least the following but not limited to: • Custom inmate summary forms with PROCESSING
agency-defined fields selected for inclusion- Current inmate rosters, broken down
by held for agency, cell block, gender, or any other data element- Rosters of
inmates currently in or out of the facility- Lists of occupied cells or available cells.
Professional-looking lists of recent bookings to post on agency Web site or to provide
to media outlets- Arrest reports for a specified time period. Statistical
comparisons of inmates held year-to-date compared to previous years. Annual
report of inmates held for outside agencies, by agency* Analysis of inmate days
based on holding status, age, gender, race, ethnicity, a combination of these factors, or
any other data elements
F-RP-37 The solution shall print bar code labels for arm bands, property tags/labels, and folder 3 REPORTING/BYWORD Reporting
labels. The contractor shall describe the solution's capabilities in this regard and PROCESSING
specify the requisite equipment (software, services and hardware), as separately priced
items, to enable this functionality.

SERIAL 13I39-RFP
F-RP-38 Users shall be able to retrieve data easily without regard to the sub-system involved, 3 REPORTING/El/WORD Reporting
including data stored on interfaced solutions. PROCESSING
F-RP-39 The solution shall provide the capability to search using "wild card" characters as well 3 REPORTING/BI/WORD Reporting
as other partial search capabilities. PROCESSING
F-RP-40 The solution shall include other methods to limit the number of records that are 3 REPORTING/BYWORD Reporting
returned from a search. PROCESSING
F-RP-4 I The solution may provide secondary searches on previous search returns. 3 REPORTING/B I/WORD Reporting
PROCESSING
F-RP-42 The solution shall provide the ability to select a specific record from the list to "drill 3 REPORTING/BE/WORD Reporting
down" to successively greater levels of detail. PROCESSING
F-RP-43 The solution shall support cross-table or cross-database searches. 3 REPORTING/I31/WORD Reporting
PROCESSING
F-RP-44 The solution shall provide the ability to hide data fields from unauthorized 3 Reporting
users/workstations.
F-RP45 The solution shall have the ability to provide summary data capabilities to specifically 3 REPORTING/BI/WORD Reporting
authorized users in order to extract information from defined query sets for external PROCESSING
analysis.
F-RP-46 The solution shall provide the ability to collect and provide statistical information about 3 REPORTING/BYWORD Reporting
the performance, capacity, and accuracy of the data itself and the management PROCESSING
operations of the solution.
F-RP-47 The solution shall provide the ability to run a litigation report. 3 REPORTING/BYWORD Reporting
PROCESSING
F-RP-48 The solution shall provide the ability to report by workflow including, but not limited to 3 REPORTING/BYWORD Reporting
status, task, content and category. See Workflow Requirements PROCESSING
F-RP-49 The solution may provide the ability to manually enter statistics to be displayed on a 3 REPORTING/BYWORD Reporting
dashboard. PROCESSING
F-RP-50 The solution shall provide the ability to create a new entry on an ad hoc report. 3 REPORTING/BYWORD Reporting
PROCESSING
SA - System Administration Requirements
User Aceottnt Management
F-SA-I The solution shall provide the ability for an administrative user and/or end-user to 3 SECURITY MODEL Non-Functional
change passwords. Requirements

SERIAL 13139-RFP
F-SA-2 The solution shall provide electronic alerts to any user whose password is about to 3 SECURITY MODEL Non-Functional
expire, e.g., first notice at 30 days prior to expiration, second notice a ten days prior to Requirements
expiration, etc.
F-SA-3 The solution shall provide the ability for an administrative user to add, change, or 3 SECURITY MODEL Non-Functional
inactivate user logon accounts. Requirements
F-SA-4 The solution shall provide the ability for an administrative user to change a user's name, 3 SECURITY MODEL Non-Functional
Requirements
F-SA-5 The solution shall provide the ability for an administrative user to manage a user's TOC 3 SECURITY MODEL Non-Functional
ID. Requirements
F-SA-6 The solution shall provide the ability to maintain and validate against a user's TOC ID 3 SECURITY MODEL Non-Functional
for expiration date. Requirements
F-SA-7 The solution shall provide electronic alerts to any user whose TOC ID is about to 3 SECURITY MODEL Non-Functional
expire, e.g., first notice at 30 days prior to expiration, second notice a ten days prior to Requirements
expiration, etc.
F-SA-8 The solution shall prohibit any user with an expired TOC ID from accessing the system 0 GAP SECURITY MODEL Non-Functional
until such time as their TOC ID credentials are again current. Requirements
This is a deviation from the
fundamental approach to Workflow
product authentication. See Section
2.15, Non-Functional Requirements.
The ability to expire an account based
on the deactivation date which is
manually set to the TOC ID will be
available with Workflow 3.5
Line 66
- • r....---, s , 1:1.. ;
MCSO agreed to work around
F-SA-9 The solution shall prohibit any user who has resigned, or who is no longer a valid user 3 SECURITY MODEL Non-Functional
for some other reason, from accessing the system. Requirements
F-SA-10 The solution shall provide the ability for an administrative user to manage a user's 3 SECURITY MODEL Non-Functional
Routing Indicator(s). Requirements
F-SA-1 I The solution shall provide the ability for an administrative user to allocate to each user 3 SECURITY MODEL Non-Functional
a unique ID. Requirements
F-SA-I 2 The solution shall provide the ability for an administrative user to view the unique user 3 N/A
ID, however it is never exposed to the end user.
Roles and Users
_

SERIAL 13139-REP
F-SA-1 3 The solution shall provide the ability for an administrative user to manage business 3 SECURITY MODEL Non-Functional
process-specific roles. Requirements
F-SA-I4 The solution shall provide the ability for an administrative user to manage business 3 SECURITY MODEL Non-Functional
global roles (such as MCSO, MCSO Detention Units, Court, Adult Probation etc.). Requirements
F-SA-1 5 The solution shall provide the ability for an administrative user to manage role-based 3 SECURITY MODEL Non-Functional
access control. Requirements
F-SA-16 The solution shall provide the ability for an administrative user to manage the manual 3 SECURITY MODEL Non-Functional
role assignment to a user. Requirements
Role Management
F-SA-1 7 The solution shall provide the ability for an administrative user to define roles within 3 SECURITY MODEL Non-Functional
the database, Requirements
F-SA-l8 The solution shall provide the ability for an administrative user to assign workflow 3 SECURITY MODEL Non-Functional
privileges to roles. Requirements
E-SA-1 9 The solution shall provide the ability for an administrative user to assign users to one or 3 SECURITY MODEL Non-Functional
multiple roles. Requirements
F-SA-20 The solution shall provide the ability for an administrative user to remove temporary 3 SECURITY MODEL Non-Functional
role assignments. Requirements
F-SA-2 I The solution shall provide the ability for an administrative user to assign temporary 0 Roadinap Workflow Release 3,5 SECURITY MODEL Non-Functional
roles to users. Requirements
F-SA-22 The solution shall provide the ability for an administrative user to assign temporary 0 Roadmap Workflow Release 3.5 SECURITY MODEL Non-Functional
role-based access control. Requirements
F-SA-23 The solution shall provide the ability for an administrative user to restrict access to 3 SECURITY MODEL Non-Functional
specific transaction(s) using the user roles and authentication process. Requirements
F-SA-24 The solution shall provide the ability for an administrative user to separate internal and 3 SECURITY MODEL Non-Functional
external users to ensure explicit data privacy. Requirements
Group profiles
F-SA-25 The solution shall provide the ability for an administrative user to manage access 3 SECURITY MODEL Non-Functional
controls through a group profile. Requirements
F-SA-26 The solution shall provide the ability for an administrative user to manage user 3 SECURITY MODEL Non-Functional
privileges through a group profile, Requirements
F-SA-27 The solution shall provide the ability for an administrative user to manage group 3 SECURITY MODEL Non-Functional
security profile. Requirements

SERIAL 13I39-RIP
F-SA-28 The solution shall provide the ability for an administrative user to manage group 0 Roadmap Workflow Release 3.5 SECURITY MODEL Non-Functional
profiles for work stations (machinesttenninals). Requirements
Administrative Business Requirements
F-SA-29 The solution shall provide the ability for an administrative user to maintain the 3 ADMIN CONSOLE Non-Functional
Document Type code table to be used throughout the solution. Requirements
F-SA-30 The solution shall provide the ability for an administrative user to maintain the Case 3 ADMIN CONSOLE Non-Functional 1
Status Type code table to be used throughout the solution. Requirements
F-SA-31 The solution shall provide the ability for an administrative user to maintain the 3 ADMIN CONSOLE Non-Functional
Immigration Status code table to be used throughout the solution. Requirements
F-SA-32 The solution shall provide the ability for an administrative user to maintain the 3 ADMIN CONSOLE Non-Functional
Identifier Type code table to be used throughout the solution. Requirements
F-SA-33 The solution shall provide the ability for an administrative user to maintain the Hair 3 ADMIN CONSOLE Non-Functional
Color code table to be used throughout the solution. Requirements
F-SA-34 The solution shall provide the ability for an administrative user to maintain the Gender 3 ADMIN CONSOLE Non-Functional
code table to be used throughout the solution. Requirements
F-SA-35 The solution shall provide the ability for an administrative user to maintain the Form 3 ADM1N CONSOLE Non-Functional
Type code table to be used throughout the solution. Requirements
F-SA-36 The solution shall provide the ability for an administrative user to maintain the Facility 3 ADMIN CONSOLE Non-Functional
code table to be used throughout the solution. Requirements
F-SA-37 The solution shall provide the ability for an administrative user to maintain the Eye 3 ADMIN CONSOLE Non-Functional
Color code table to be used throughout the solution. Requirements
F-SA-38 The solution shall provide the ability for an administrative user to maintain the 3 ADMIN CONSOLE Non-Functional
Expungement Type code table to be used throughout the solution. Requirements
F-SA-39 The solution shall provide the ability for an administrative user to maintain the Marital 3 ADMIN CONSOLE Non-Functional
Status code table to be used throughout the solution. Requirements
F-SA-40 The solution shall provide the ability for an administrative user to maintain the Event 3 ADMIN CONSOLE Non-Functional
Result code table to be used throughout the solution. Requirements
F-SA-41 The solution shall provide the ability for an administrative user to maintain the Unit 3 ADMIN CONSOLE Non-Functional
Type code table to be used throughout the solution. Requirements
F-SA-42 The solution shall provide the ability for an administrative user to maintain the 0 Roadmap Workflow Release 3.5 ADMIN CONSOLE Non-Functional
Document Instruction Type code table to be used throughout the solution. Requirements
F-SA-43 The solution shall provide the ability for an administrative user to maintain the 3 ADMLN CONSOLE Non-Functional
Disposition Type code table to be used throughout the solution. Requirements

SERIAL 13139-RFP
F-SA-44 The solution shall provide the ability for an administrative user to maintain the 3 ADMIN CONSOLE Non-Functional
Disposition code table to be used throughout the solution. Requirements
F-SA-45 The solution shall provide the ability for an administrative user to maintain the Country 3 ADMIN CONSOLE Non-Functional
code table to be used throughout the solution. Requirements
F-SA-46 The solution shall provide the ability for an administrative user to maintain the 3 ADMIN CONSOLE Non-Functional
Conservatorship Type code table to be used throughout the solution. Requirements
F-SA-47 The solution shall provide the ability for an administrative user to maintain the Keep- 3 ADMIN CONSOLE Non-Functional
away Reason Type code table to be used throughout the solution. Requirements
F-SA-48. The solution shall provide the ability for an administrative user to maintain the City 3 ADMIN CONSOLE Non-Functional
code table to be used throughout the solution. Requirements
F-SA-49 The solution shall provide the ability for an administrative user to maintain the 3 ADMIN CONSOLE Non-Functional
Citizenship code table to be used throughout the solution. Requirements
F-SA-50 The solution shall provide the ability for an administrative user to maintain the Charge 3 ADMIN CONSOLE Non-Functional
code table to be used throughout the solution. Requirements
F-SA-51 The solution shall provide the ability for an administrative user to maintain the Case 3 ADMIN CONSOLE Non-Functional
Type code table to be used throughout the solution. Requirements
F-SA-52 The solution shall provide the ability for an administrative user to maintain the Case I Enhancement ADMIN CONSOLE Non-Functional
Sub Type code table to be used throughout the solution. Requirements
Line 23
in Attachment A Cost Proposal
F-SA-53 The solution shall provide the ability for an administrative user to maintain the Sealed 3 ADMIN CONSOLE Non-Functional
code table to be used throughout the solution. Requirements
F-SA-54 The solution shall provide the ability for an administrative user to maintain the Record 3 ADMIN CONSOLE Non-Functional
Type code table to be used throughout the solution. Requirements
F-SA-55 The solution shall provide the ability for an administrative user to maintain the Unit 3 ADMIN CONSOLE Non-Functional
code table to be used throughout the solution. Requirements
F-SA-56 The solution shall provide the ability for an administrative user to maintain the Title 3 ADMIN CONSOLE Non-Functional
code table to be used throughout the solution. Requirements
F-SA-57 The solution shall provide the ability for an administrative user to maintain the Time Of 1 Enhancement ADMIN CONSOLE Non-Functional
Day code table to be used throughout the solution. Requirements
Line 24
in Attachment A Cost Proposal
F-SA-58 The solution shall provide the ability for an administrative user to maintain the I Enhancement ADMIN CONSOLE Non-Functional
Subpoena Service Type code table to be used throughout the solution. Requirements
Line 25
in Attachment A Cost Proposal

SERIAL 13139-RFP
F-SA-59 The solution shall provide the ability for an administrative user to maintain the Warrant I EnhancementLine 26in Attachment A ADMIN CONSOLE Non-Functional
Response code table to be used throughout the solution. Cost Proposal Requirements
F-SA-60 The solution shall provide the ability for an administrative Wel' to maintain the State 3 ADMIN CONSOLE Non-Functional
code table to be used throughout the solution. Requirements
F-SA-61 The solution shall provide the ability for an administrative user to maintain the Charge 3 ADMIN CONSOLE Non-Functional
Severity code table to be used throughout the solution. Requirements
F-SA-62 The solution shall provide the ability for an administrative user to maintain the 3 ADM1N CONSOLE Non-Functional
Sentence Type code table to be used throughout the solution. Requirements
F-SA-63 The solution shall provide the ability for an administrative user to maintain the Role 3 ADMIN CONSOLE Non-Functional
code table to be used throughout the solution. Requirements
F-SA-64 The solution shall provide the ability for an administrative user to maintain the 3 ADMIN CONSOLE Non-Functional
Response code table to be used throughout the solution. Requirements
F-SA-65 The solution than provide the ability for an administrative user to maintain the 3 ADMIN CONSOLE Non-Functional
Language code table to be used throughout the solution, Requirements
F-SA-66 The solution shall provide the ability for an administrative user to maintain the Referral 3 ADMIN CONSOLE Non-Functional
Type code table to be used throughout the solution, Requirements
F-SA-67 The solution shall provide the ability for an administrative user to maintain the Cost 3 ADMIN CONSOLE Non-Functional
Type code table to be used throughout the solution. Requirements
F-SA-68 The solution shall provide the ability for an administrative user to maintain the Race 3 ADMIN CONSOLE Non-Functional
code table to be used throughout the solution. Requirements
F-SA-69 The solution shall provide the ability for an administrative user to maintain the Purge 0 Roadmap Workflow Release 3.5 ADMIN CONSOLE Non-Functional
File code table to be used throughout the solution. Requirements
F-SA-70 The solution shall provide the ability for an administrative user to maintain the 1 Enhancement ADMIN CONSOLE Non-Functional
Prosecutor code table to be used throughout the solution. Requirements
Line 27
in Attachment A Cost Proposal
F-SA-71 The solution shall provide the ability for an administrative user to maintain the 3 ADMIN CONSOLE Non-Functional
Probation code table to be used throughout the solution. Requirements
F-SA-72 The solution shall provide the ability for an administrative user to maintain the 3 ADMIN CONSOLE Non-Functional
Probation Juvenile code table to be used throughout the solution. Requirements
F-SA-73 The solution shall provide the ability for an administrative user to maintain the 3 ADM1N CONSOLE Non-Functional
Probation Adult code table to be used throughout the solution. Requirements
F-SA-74 The solution shall provide the ability for an administrative user to maintain the 0 Roadmap Workflow Release 3.5 N/A
Available Printer code table to be used throughout the solution.

SERIAL 13139-RFP
F-SA-75 The solution shall provide the ability for an administrative user to maintain the Print 0 Roadmap Workflow Release 3.5 N/A
User Id code table to be used throughout the solution,
F-SA-76 The solution shall provide the ability for an administrative user to maintain the Phone 3 ADMIN CONSOLE Non-Functional
Type code table to be used throughout the solution. Requirements
F-SA-77 The solution shall provide the ability for an administrative user to maintain the Person 3 A_DMIN CONSOLE Non-Functional
Type code table to be used throughout the solution. Requirements
F-SA-78 The solution shall provide the ability for an administrative user to maintain the Person 3 ADMIN CONSOLE Non-Functional
Flag code table to be used throughout the solution. Requirements
F-SA-79 r The solution shall provide the ability for an administrative user to maintain the 3 ADMIN CONSOLE Non-Functional
Relationship code table to be used throughout the solution. Requirements
F-SA-80 ,.. The solution shall provide the ability for an administrative user to create and modify 3 ADMEN CONSOLE Non-Functional
case status by case type in the solution and have these available for use in the case Requirements
status drop down lists.
F-SA-3I The solution shall provide the ability for an administrative user to define and modify 3 ADMIN CONSOLE Non-Functional
contact information type list within the solution and have these be available to other Requirements
users for use when he or she needs to enter a person's contact information.
F-SA-82 The solution shall provide the ability for an administrative user to maintain the Average 0 Roadmap Workflow Release 3.5 ADMIN CONSOLE Non-Functional
Housing Cost code table with information by Jurisdiction Type and Fiscal Year to be Requirements
used throughout the solution.
F-SA-83 The solution shall provide the ability for an administrative user to define and modify 3 ADMIN CONSOLE Non-Functional
case type workflow stages in the solution and have these be available to staff. Requirements
F-SA-84 The solution shall provide the ability for an administrative user to define and modify an 3 Enhancement ADMIN CONSOLE Non-Functional
expense type list in the solution and have these be available to staff. Requirements
Line 28
in Attachment A Cost Proposal
MCSO Agreed to workaround -
custom field
F-SA-85 The solution shall provide the ability for an administrative user to define and modify a 3 ADMIN CONSOLE Non-Functional
representation status type list within the solution and have these be available to other Requiiements
users for use when he or she needs to update the person's representation status.
F-SA-86 The solution shall provide the ability for an administrative user to define and modify a 3 ADMIN CONSOLE Non-Functional
picture source type list within the solution and have these be available to other users for Requirements
use when he or she needs to enters an image file is associated to person record.
F-SA-87 The solution shall provide the ability for an administrative user to define and modify a 3 ADMIN CONSOLE Non-Functional
person's property type list within the solution and have these be available to other users Requirements
for use when he or she needs to enters a person's property information.
F-SA-88 The solution shall provide the ability for an administrative user to create and modify 3 ADMIN CONSOLE Non-Functional
case type descriptions in the solution and have these available for use in the case type Requirements
drop down lists.

SERIAL 13139-RFP
F-SA-89 The solution shall provide the ability for an administrative user to define and modify 3 ADMIN CONSOLE Non-Functional
name Context type list within the solution and have these be available to other users for Requirements
use when he or she needs to enter a person's name information.
F-SA-90 The solution shall provide the ability for an administrative user to create and modify 3 ADMIN CONSOLE Non-Functional
case person role codes in the solution and have these available for use in the case Requirements
person role code drop down lists,
F-SA-91 The solution shall provide the ability for an administrative user to create and maintain 0 Roadmap Workflow Release 3.5 ADMIN CONSOLE Non-Functional
complex documents, forms, clauses and documentation packages recalling these items Requirements
based on business rules at run time.
F-SA-92 The solution shall provide the ability for an administrative user to maintain the Inmate 3 ADMIN CONSOLE Non-Functional
Security Type code table to be used throughout the solution. Requirements
F-SA-93 The solution shall provide the ability for an administrative user to create and maintain 0 Roadmap Workflow Release 3,5 DOCUMENT MANAGEMENT Document
documentation packages of materials based on case type and event; such as appeals, Management
death penalty and murder cases to be recalled by a user at the time of document
generation.
F-SA-94 The solution shall provide the ability for an administrative user to maintain the Custody 3 ADMIN CONSOLE Non-Functional
Status code table to be used throughout the solution. Requirements
F-SA-95 The solution shall provide the ability for an administrative user to define and modify a 3 ADMIN CONSOLE Non-Functional
person's identifier type list (Driver's License, SID, FBI Number, LOIS, etc...) within Requirements
the solution and have these be available to other users for use when he or she needs to
enters a person's identifier information.
F-SA-96 The solution shall provide the ability for an administrative user to maintain the Access 3 ADMIN CONSOLE . Non-Functional
Type code tables to be used throughout the solution. Requirements
F-SA-97 The solution shall provide the ability for an administrative user to maintain the Case 3 ADMIN CONSOLE Non-Functional
Flag code table to be used throughout the solution. Requirements
F-SA-98 The solution shall provide the ability for an administrative user to maintain the Inmate 3 ADMIN CONSOLE Non-Functional
Event Type code table to be used throughout the solution. Requirements
F-SA-99 The solution shall provide the ability for an administrative user to maintain the Inmate 3 ADMIN CONSOLE Non-Functional
Class Type code table to be used throughout the solution. Requirements
F-SA-100 The solution shall provide the ability for an administrative user to maintain the Answer 3 ADMIN CONSOLE Non-Functional
Choice Delimiter code table to be used throughout the solution. Requirements
F-SA-I01 The solution shall provide the ability for an administrative user to maintain the Agency 3 ADMIN CONSOLE Non-Functional
code table to be used throughout the solution. Requirements
F-SA-102 The solution shall provide the ability for an administrative user to maintain the Address 3 ADMIN CONSOLE Non-Functional
Type code table to be used throughout the solution. Requirements
F-SA-103 The solution shall provide the ability for an administrative user to define and modify 3 ADMIN CONSOLE Non-Functional
contact address type list within the solution and have these be available to other users Requirements
for use when he or she needs to enter a person's contact address.

SERIAL 13I39-RFP
F-SA-104 The solution shall provide the ability for an administrative user to maintain the Activity 3 ADMIN CONSOLE Non-Functional
Type code table to be used throughout the solution, Requirements
F-SA-105 The solution shall provide the ability for an administrative user to either view online or 3 REPORTING/131/WORD Non-Functional
print the selected inmate's case lifecycle workflow status. PROCESSING Requirements
F-SA-106 The solution shall provide the ability for art administrative user to configure subject line 0 Roadmap Workflow Release 3.5 MESSAGING Non-Functional
and location information for solution generated messages by inmate message type. Requirements
F-SA-107 The solution shall provide the ability for an administrative user to create, maintain, and 3 ADMIN CONSOLE Non-Functional
retire charge codes used in the solution. Requirements
F-SA-108 The solution shall provide the ability for an administrative user to create, maintain, and 3 ADMIN CONSOLE Non-Functional
retire bond and fine codes used in the solution. Requirements
F-SA-109 The solution shall provide the ability for an administrative user to create and maintain 3 ADMIN CONSOLE Non-Functional
automated template documents without IT assistance or programming / scripting skills. Requirements
F-SA-I10 The solution shall provide the ability for an administrative user to create, maintain, and 3 ADMIN CONSOLE Non-Functional
retire bond company used in the solution. Requirements
F-SA-111 The solution shall provide the ability to maintain administrative sealed code tables 3 MCSO agreed to workaround - custom ADM1N CONSOLE Non-Functional
indicating the reason for action. field Requirements
Exhibit A Line 29
F-SA-112 Archive dates may be based on parameters established in tables maintained by the 0 Archive is no longer a requirement ADMIN CONSOLE NA
System Administrator.
F-SA-113 The solution shall provide the ability for an administrative user to Import the 'Current 3 ADMIN CONSOLE Non-Functional
ARS Code' from ACM into Charge code table to be used throughout the solution. Requirements
F-SA-114 The solution shall provide the ability for an administrative user to Import the 3 ADMIN CONSOLE Non-Functional
'Historical ARS Code" from ACIC into Charge code table to be used throughout the Requirements
solution.
F-SA-115 The solution shall provide the ability for an administrative user to maintain the bail 3 ADM1N CONSOLE Non-Functional
information within the Bail Schedule table to be used throughout the solution. Requirements
F-SA-116 The solution shall provide the ability for an administrative user to maintain the bond 3 ADMIN CONSOLE Non-Functional
information within the Bond Schedule code table to be used throughout the solution. Requirements
F-SA-117 The solution shall provide the ability for an administrative user to maintain the billing 3 ADMIN CONSOLE Non-Functional
information within the Billing Charge code table to be used throughout the solution. Requirements
Dynamic Forms
F-SA-118 The solution shall provide the ability for an administrative user to manage selectable 3 N/A
options dependent on other fields on the same form.
F-SA-119 The solution shall provide the ability for an administrative user to manage field 3 N/A
visibility dependent on other fields on the same form.

SERIAL 13I39-RFP
F-SA-120 The solution shall provide the ability for an administrative user to manage field 3 N/A
protection dependent on other fields on the same form.
F-SA-121 The solution shall provide the ability for an administrative user to manage selectable 3 N/A
options dependent on other data fields on a different form.
F-SA-l22 The solution shall provide the ability for an administrative user to manage field 3 N/A
visibility dependent on other data fields on a different form.
F-SA-123 The solution shall provide the ability for an administrative user to manage field 3 N/A
protection dependent on other data fields on a different form.
Data Bindings
F-SA-124 The solution shall provide the ability for an administrative user to manage automatic 3 N/A
persistence of data.
F-SA-125 The solution shall provide the ability for an administrative user to manage API calls. 3 N/A
F-SA-126 The solution shall provide the ability for an administrative user to manage computed 3 N/A
values.
F-SA-127 The solution shall provide the ability for an administrative user to access external 3 N/A
databases.
F-SA-128 The solution shall provide the ability for an administrative user to manage associated 3 N/A
data fields on forms to databases.
F-SA-129 The solution shall provide the ability for an administrative user to manage and process 3 N/A
run-time information in the database,
Form Layout
F-SA-130 The solution shall provide the ability for an administrative user to design forms 3 N/A
manually.
F-SA-131 The solution shall provide the ability for an administrative user to design forms that 3 N/A
have been arranged automatically,
F-SA-132 The solution shall provide the ability for an administrative user to manage forms that 3 N/A
support multiple layout schemes.
F-SA-133 The solution shall provide the ability for an administrative user to plug in user-created 3 N/A
layout schemes.
F-SA-134 The solution shall provide the ability for an administrative user to manage parameter 3 N/A
based blank forms using system code tables.
External Forms

SERIAL 13139-RFP
F-SA-135 The solution shall provide the ability for an administrative user to import forms created 3 N/A
using other design tools.
F-SA-136 The solution shall provide the ability for an administrative user to use web forms hosted 3 N/A
in other applications.
SC - Scheduling Requirements
F-SC-1 The solution shall have a scheduling/re-scheduling component to provide tracking of all 3 MOVEMENTS Scheduling
inmate events and activities, including but not limited to transfers to court, programs,
visitation (RCC, Attorney), healthcare appointments, non scheduled events and work
assignments (work hours, specific detail, furlough, release).
F-SC-2 The solution shall prioritize inmate appointments based on MCSO's designated priority 0 Dependent on Enhancement identified MOVEMENTS Scheduling
levels. in F-SC-5
F-SC-3 The solution shall automatically check for and advise of any scheduling conflicts. 3 MOVEMENTS Scheduling
F-SC-4 The solution shall allow scheduling conflicts to be resolved via manual override by 3 MOVEMENTS Scheduling
authorized user and include a scheduling notification.
F-SC-5 The solution shall flag and/or bump inmate's conflicting schedules and provide 1 Enhancement MOVEMENTS Scheduling
automatic notification based on criteria provided by MCSO.
Line 30
in Attachment A Cost Proposal
See also F-CT-21
F-SC-6 The solution shall be able to schedule or override single or recurring events (such as 3 PROGRAMS & SERVICES Scheduling
religious services, etc) for the facility or housing areas.
F-SC-7 The solution shall provide the ability to query/view schedules for the entire tbciiity, 3 PROGRAMS & SERVICES Scheduling
program, or specific inmates by day, week, month or year.
F-SC-8 The solution shall provide the ability to print schedules for the entire facility and/or 3 REPORTING/El/WORD Reporting
specific inmates by day, week, month or year. PROCESSING
F-SC-9 The solution shall interface with the health care scheduling solution (CHS in and out). I Custom Interface DCI
See Appendix 2 - Interface Requirements.
F-SC-10 The solution shall have the capability to schedule group appointments for inmates. 3 ADMISSION/TRANSFEPJRELEA Scheduling
SE
F-SC-11 The solution shall have the ability to set up recurring appointments with start and/or 3 ADMISSION/TRANSFER/RELEA Scheduling
end dates. SE
PROGRAMS
F-SC-12 The solution shall provide the ability to automatically cancel future inmate 3 ADMISSION/TRANSFER/RELEA Scheduling
appointments based upon the inmate's release and send automated cancellation SE
notifications.
F-SC-13 The solution shall allow reporting on scheduling information based on criteria including 3 REPORTING/IN/WORD Reporting
but not limited to inmate, facility, type, location, date/time, special needs, interpreter, PROCESSING
language and demographic information.

SERIAL 13139-RFP
F-SC-I4 The solution shall provide the ability to generate a court schedule with sorting ability 3 REPORTING/BI/WORD Reporting
by data elements that include, but are not limited to, inmate name, housing location, PROCESSING
ease number, booking number, court room, court time, judge, most serious charge,
keep-aways, cell assignment, assigned officer, multiple dates,
F-SC-15 The solution shall provide an alert when inmates with active keep-away notations are 3 REPORTING/BYWORD Reporting
scheduled OD all printed and displayed schedules. PROCESSING
F-SC-16 The solution shall provide the ability to update court related data (appearance time, 3 COURT ORDERS/LEGAL Scheduling / SIMS
court room, judge) based on user permissions. DOCUMENTS
F-SC-17 The solution shall provide the ability to flag an inmates court record when the inmate is 3 COURT ORDERS/LEGAL Scheduling / SIMS
to be dressed out. DOCUMENTS
F-SC-I 8 The solution shall maintain a historical record of all inmate scheduling. 3 MOVEMENTS Scheduling
F-SC-19 The solution shall provide the ability to schedule court appearances of inmates. 3 COURT ORDERS/LEGAL Scheduling / SIMS
DOCUMENTS
F-SC-20 The solution shall provide the ability to schedule transportation of inmates including 0 Roadmap Workflow Release 4.5 TRANSPORTATION Transportation
special accommodations.
F-SC-21 The solution shall provide the ability to mass schedule single and recurring events for 3 MOVEMENTS Scheduling
groups of inmates at one time, PROGRAMS
F-SC-22 The solution shall provide the option of scheduling recurring events as daily, weekly, 3 MOVEMENTS Scheduling
in-weekly, monthly, and other combinations as found in typical calendaring PROGRAMS
applications including multiple dates and no end date.
F-SC-23 The solution may provide the ability to identify events that require the transportation of 0 Roadmap Workflow Release 4.5 TRANSPORTATION Transportation
an inmate(s) based on MCSO business rules.
F-SC-24 The solution shall provide the ability to schedule transfers in both active and inactive 3 MOVEMENTS Scheduling
status to external agencies.
F-SC-25 The solution shalt provide the ability to create and maintain a master inmate daily 3 Reporting/BI/Word Processing Reporting
schedule, including alerts and restrictions information.
F-SC-26 The solution may include the ability to require acknowledgements and/or dispositions 3 COURT ORDERS/LEGAL Scheduling
of specific schedule activities. DOCUMENTS
F-SC-27 The solution may include the ability to make acknowledgements and/or enter 3 COURT ORDERS/LEGAL Scheduling
dispositions of specific schedule activities, DOCUMENTS
F-SC-28 The solution may provide the ability to create new types of events to be scheduled at 3 MOVEMENTS Scheduling
the time of scheduling that can be searched and reported on.
F SC 29 - 0 See Attchment C Challenging OF MOVEMEN:f-S NIA
Gestl=f Reeli:nr-etnents
•:. -; ., : i i., :-.;

SERIAL 13139-RFP
F-SC-30 The solution may provide the ability to attach files to a scheduled event. 3 REPORTING/Ell/WORD Document
PROCESSING Management
F-SC-31 The solution may provide the ability to highlight and/or create notifications based on 0 Roadmap Workflow Release 3.5 MESSAGING Workflow
MCSO business rules if a previously scheduled event has been changed or canceled.
F-SC-32 The solution shall provide the ability to integrate with Court Systems. See Appendix 2- 1 Custom Interface DCI
Interface Requirements.
F-SC-33 The solution may provide the ability to receive Court Event Forms electronically. 1 Custom Interface DCI
F SC 34 The solution may provide the ability to record whether an inmate fulfilled an obligation 0 , , ,i • " e .... %-,,, . -.- Programs
or Rot and the reason,
net-be-applisable4-aeeessary,
F-SC-35 The solution may provide the ability to create a report of inmates who did not attend a 3 REPORTING/B1/WORD Reporting
scheduled event, PROCESSING
F-SC-3,6 The solution shall provide the ability for the user to be alerted when an inmate needs an 3 Eithatwemeat MOVEMENTS Scheduling
interpreter and/or other special needs information before the appointment is confirmed.
F SC 37 K, - --.. , .• 1 , : - 4- Enhanseinentlt was agreed during the MOVEMENTS Scheduling
scheduling session that this
requirement could be removed as
MCSO would have no way of knowing
when an interpreter would be available.
F-SC-38 The solution may provide the ability to display an inmate's availability to external 3 MOVEMENTS Scheduling
parties similar to free/busy calendar functions,
F-SC-39 The solution may provide the ability to schedule simultaneous appointments for the 3 COURT ORDERS/LEGAL Scheduling
same inmate. The solution is to display a warning message if the locations are in DOCUMENTS
conflict.
F-SC-40 The solution shall provide the ability to define an appointment templates subject line 3 Reporting/BI/Word Processing Reporting /
and location information, Scheduling
F-SC-41 The solution shall have the ability to receive an unlimited number of court dates for an 3 COURT ORDERS/LEGAL SIMS/Scheduling
inmate and add it to the schedule. DOCUMENTS
F-SC-42 The solution shall provide the ability to schedule telephonic hearings. 3 COURT ORDERS/LEGAL SIMS/Scheduling
DOCUMENTS
F-SC-43 The solution shall provide the ability to schedule video visitation. 1 Custom Interface DC1
F-SC-44 The solution may provide the ability to schedule appointments with Correctional Health 3 partial, may require interface with CHS MOVEMENTS DC1
Services (CHS). to fully complete
F-SC-45 The solution shall provide the ability to prioritize calendar entries. 0 Dependent on Enhancement identified MOVEMENTS Scheduling
in F-SC-5

SERIAL 13139-RFP
F-SC-46 The solution shall provide the ability to override calendar entries according to role. 3 MOVEMENTS Scheduling
F-SC-47 The solution shall provide functionality to send an alert to a visitation kiosk. 1 Custom Interface DC t
SN - Sentence Calculation Requirements
F-SN-1 The solution shall allow the end user to record all the judgment and sentence related 3 COURT ORDERS/LEGAL SIMS
data received from the court. DOCUMENTS
F-SN-2 The solution shall allow the end user the ab lity to apply multiple sentences that can be 3 COURT ORDERS/LEGAL SlIvIS
run concurrent or consecutive. DOCUMENTS
F-SN-3 The solution shall allow the end user the ability to maintain multiple inmate sentence(s) 3 COURT ORDERS/LEGAL SIMS
and related conditions. DOCUMENTS
F-SN-4 The solution shall allow the end user the ability to apply a specific sentence type to a 3 COURT ORDERS/LEGAL SIMS
court case or multiple court cases. DOCUMENTS
F-SN-5 The solution shall allow sentence types to be user configurable and allow for the entry 1 Enhancement SENTENCE & TIME SIMS
of a sentencing algorithm to be associated with each sentence type. Included with enhancement for F-CT- ACCOUNTING
55
F-SN-6 The solution shall allow for the addition of unlimited sentence types. 3 COURT ORDERS/LEGAL SIMS
DOCUMENTS
F-SN-7 The solution shall allow the end user the ability to apply a sentence for 3 COURT ORDERS/LEGAL SIMS
consecutive/concurrent years, months, days or hours. DOCUMENTS
F-SN-8 The solution shall allow the end user the ability to convert a fine into sentenced time 1 Enhancement SENTENCE & TIME SIMS
(dollar for days and recalculation), Conversion algorithm must be user configurable. Included with enhancement for F-CT- ACCOUNTING
55
F-SN-9 The solution shall allow the end user the ability to attach a release condition to a 3 COURT ORDERS/LEGAL SIMS
sentence, such as but not limited to: report to Parole, Probation, Program. Release DOCUMENTS
condition should be user configurable and may or may not allow the release of an
inmate.
F-SN-10 The solution shall allow the end user the ability to calculate day for day work credits 1 GAPDuring PROGRAMS & SERVICES SIMS
based on a sentence. Solution should track the number of days worked and provide a discussions with SliVIS it was
means to manually apply to the sentence, affecting the release date, discussed that the application of work
credit based on attendance of work
must be automatically applied to the
sentence. SIMS still requires the ability
to manually adjust credits as well.The
automatic application of work credits
based on attendance will be developed
and is scheduled, tentatively, for
Workflow Release 3.5— Project
Release 1.3Line 67in Attachment A
Cost Proposal
?Q.

SERIAL 13139-RFP
F-SN-I I The solution shall allow the end user the ability to note when an inmate is ineligible to 0 Roadmap Workflow Release 2.5 PROGRAMS & SERVICES SIMS
receive day for day work credits, but continue to record the number of days worked.
F-SN-12 The solution shall allow an authorized user the ability to remove good time work credit 3 SENTENCE & TIME SIMS
from a previously entered sentence, ACCOUNTING
F-SN-13 The solution shall allow the end user the ability to record multiple codes that may make 0 Roadmap Workflow Release 2,5 PROGRAMS & SERVICES SIMS
an inmate eligible or in-eligible for certain release programs. Codes should be user
configurable and allow for unlimited code types.
F-SN-I 4 The solution shall allow an authorized user the ability to record, edit, and review 3 COURT ORDERS/LEGAL SIMS
sentence information, including custody, fines, restitution, modifiable sentence and DOCUMENTS
program recommendation.
F-SN-15 The solution shall allow the end user the ability to calculate an inmate's release date, 1 Enhancement SENTENCE & TIME SIMS
including multiple release dates, concurrent and consecutive sentences, incorporation of ACCOUNTING
good time earning business rules and quality control. See Business Rules Included with enhancement for F-CT-
Requirements . 55
F-SN-I 6 The solution shall allow the end user the ability to automatically recalculate release 1 Enhancement SENTENCE & TIME SIMS
date(s) based on varying events, such as program completion, disciplinary action, and ACCOUNTING
amended sentences, Provide the ability to manual override sentences through sentence Included with enhancement for F-CT-
validation workflow. See Workflow Requirements. 55
F-SN- 7 The solution shall allow the end user the ability to add notes to a sentence calculation 3 COURT ORDERS/LEGAL SIMS
and track changes made to notes. DOCUMENTS
F-SN-I 8 The solution shall allow the end user the ability to keep a viewable history of all 0 Roadmap Workflow Release 3.5 COURT ORDERS/LEGAL SIMS
changes made to a sentence and/or sentence calculation. DOCUMENTS
F-SN-19 The solution shall allow the end user the ability to print a calculation sheet specifying 3 REPORTING/BYWORD Reporting
an inmate release date and summarizing his/her sentences, good time earning rate, PROCESSING
program completions, and other events affecting sentence calculation based on public
record release rules,
F-SN-20 The solution shall allow the end user the ability to create a list of inmates with the 3 REPORTING/BYWORD Reporting
completed percentage of sentence. See Reporting Requirements. PROCESSING
F-SN-2l The solution shall allow the end user the ability to send an electronic notification prior 3 MESSAGING Workflow / SIMS
to the release of an inmate who has qualifying charges requiring that a victim
notification must be made. The number of days prior to release shall be user
configurable.
F-SN-22 The solution shall provide the ability to record sentencing information including but not 3 COURT ORDERS/LEGAL SIMS
limited to: Type of sentence (Regular Time, Hours, Week End, Work Release) DOCUMENTS
Special sentencing instructions
Sentence effective date
Release Time
Fees

SERIAL 13139-REP
TA - Trust Accounting Requirements
Inmate Account Processing
F-TA-1 The solution's inmate trust fund module shall automatically set up an inmate account at 0 Roadmap Workflow Release 4.0 TRUST ACCOUNTING Budget / finance
booking.
F-TA-2 The solution shall be capable of posting inmate's personal funds to the inmate's 0 Roadmap Workflow Release 4.0 TRUST ACCOUNTING Budget / Finance
personal account when the inmate is initially booked into the jail.
F-TA-3 Transactions affecting the account (e.g. canteen purchases, trust deposits, fees, etc.) 0 Roadmap Workflow Release 4.0 TRUST ACCOUNTING Budget) Finance
shall automatically be tracked by the solution in a seamless manner during each
inmate's entire incarceration period.
F-TA-4 The solution's inmate trust module shall allow account deposits via kiosks located on 1 Custom Interface Budget / Finance
Jail premises (Intake and Visitor Center), via web access and via an IVR solution using
a phone. See Appendix 2 - Interface Requirements.
F-TA-5 The solution shall support an automated edit from validating that the inmate account I Custom Interface Budget / Finance
has been established and can accept deposits. See Interface Requirements.
F-TA-6 The solution shall be capable of printing a receipt for any money received for the 0 Roadmap Workflow Release 4.0 TRUST ACCOUNTING Budget / Finance
inmate's account.
F-TA-7 The solution's receipt shall include, at a minimum, a unique receipt tracking number, 0 Roadmap Workflow Release 4.0 TRUST ACCOUNTING Budget / Finance
date of the receipt, the inmate's name, date of birth, booking number, the amount
deposited, and the method received.
F-TA-8 The solution shall be capable of printing a statement listing all inmate personal account 0 Roadrnap Workflow Release 4.0 TRUST ACCOUNTING Budget / Finance
activity by activity types any time during an inmate incarnation.
F-TA-9 At the time of release, the solution shall be capable of recording the release of unused 1 Custom Interface TRUST ACCOUNTING Budget I Finance
funds via debit card.
F-TA-10 The solution shall print a release receipt for the returned funds for signing by the inmate 0 Roadmap Workflow Release 4.0 TRUST ACCOUNTING Budget I Finance
signifying the funds were received.
F TA Ii The solution may reduce the inmate's personal funds to zero and create an account (3 - Budget,' Finance
archive date when an inmate's account is closed. Costly Requirement
Archiving is no longer required.
F-TA-12 The solution may support digital signatures for the release of money to the inmate or an 0 Roadmap Workflow Release 4.0 TRUST ACCOUNTING Budget / Finance
approved third party.
Inmate Canteen Processing
F-TA-13 The solution shall provide the capability of printing canteen order forms based on 0 Roadmap Workflow Release 4.0 COMMISSARY Canteen
housing assignment and/or assigned canteen day.
?Qi

SERIAL 13139-RFP
F-TA-14 The solution shall provide an order entry screen so that inmate canteen orders can be 0 Roadmap Workflow Release 4.0 COMMISSARY Canteen
entered by Canteen administrative staff from pre-printed order forms.
F-TA-15 The solution shall provide the capability for inmates to enter their own canteen orders I This requirement was discussed during Canteen
from a designated Kiosk in the facility, the Trust Accounting gap analysis
session.
No Kiosk provider currently selected.
This is a future requirement and Kiosk
integration has not been quoted,
Line 68
in Attachment A Cost Proposal
F-TA-16 The solution shall provide for electronic inmate signature on canteen orders. 0 Roadmap Workflow Release 4.0 COMMISSARY Canteen
F-TA-17 Canteen orders entered shall edit for compliance with, but not limited to sex, diet, 0 Roadmap Workflow Release 4.0 COMMISSARY Canteen
indigent, religious, culture, housing assignment, disciplinary and medical restrictions
for inmates.
F-TA-I 8 The solution shall verify that the inmate has adequate funds for the canteen order at 0 Roadmap Workflow Release 4.0 COMMISSARY Canteen
time of posting the initial order.
F-TA-19 When the inmate's account has insufficient funds to cover the order, the solution shall 1 This requirement was discussed COMMISSARY Canteen
have the ability to transmit NSF to kiosk for inmate notification, during the Trust Accounting gap
analysis session.
Kiosk notification is a future
requirement and cost has not been
quoted,
Line 69
in Attachment A Cost Proposal

SERIAL 13139-REP
F-TA-20 I The solution shall have ability to discount the inmate order based on business rules. See 1 GAPThis COMMISSARY Canteen
I Business Rules requirements. requirement was discussed during the
Trust Accounting gap analysis session.
Some programs and kitchen workers
may receive a discount on their orders.
The discount is applied to the entire
order but does not apply to some items
in inventory. During the session it was
learned that the desire is to link
programs and work profile to canteen
so that discounts can be applied
automatically. This enhancement is
dependent on tracking those jobs and
program assignments that are eligible
for discounts as well as flagging those
items in inventory that cannot be
discounted. The system needs to have
a mechanism for manually applying a
sales discount in order to deal with
exceptions. The discount amount to be
applied should be configurable in order
to allow for future changes.An
alternative approach would be to
display job/program assignments to the
user when processing sales orders and
allow them to manually invoke the
sales discountlf this gap is approved, it
is tentatively scheduled for Workflow
Release 4.5— Project Release 2.2Line
64in Attachment A Cost Proposal
See Also F-CT-88
F-TA-21 The solution shall enforce the maximum order limits dictated by business rules. See 0 Roadmap Workflow Release 4.0 COMMISSARY Canteen
Business Rules requirements.
F-TA-22 Indigent orders shall be rejected by the solution when the inmate has an account 0 Roadmap Workflow Release 4.0 COMMISSARY Canteen
balance exceeding the predetermined limit set by the System Administrator.
F-TA-23 The solution shall reduce the inmate's account balance by the amount of the canteen Roadmap Workflow Release 4.0 COMMISSARY Canteen
order as it is input by line item.
F-TA-24 The solution shall be capable of displaying a list of all items for a specific inmate's 0 Roaclmap Workflow Release 4.0 COMMISSARY Canteen
canteen order using the booking number, unique canteen order number and date.
F-TA-25 The Canteen Administrative staff shall be able to select from the list those items where 0 Roadmap Workflow Release 4.0 COMMISSARY Canteen
credit is due and/or credit the entire canteen order for the inmate.
1-TA-26 The Canteen Administrative staff shall be able to perform a reverse on a credit. Roadrnap Workflow Release 4.0 COMMISSARY Canteen

SERIAL 13139-RFP
F-TA-27 The Canteen Administrative staff shall be able to perform a reverse on a refund. 0 Roadmap Workflow Release 4.0 COMMISSARY Canteen
F-TA-28 The solution shall support fulfillment and payment for inmate orders for magazine and 0 Roadmap Workflow Release 4.0 COMMISSARY Canteen
newspaper subscriptions and book purchases that are not inventory items, including
postage and handling fees.
F-TA-29 The solution shall provide a pick list for each inmate order. 0 Roadmap Workflow Release 4.0 COMMISSARY Canteen
F-TA-30 The solution shall provide the ability to create and print Pick Lists in an order Roadmap Workflow Release 4.0 COMMISSARY Canteen
determined by administrative user.
F-TA-31 A detailed receipt including the items, quantity and cost shall be printed for each inmate 0 Roadmap Workflow Release 4,0 COMMISSARY Canteen
order, including items not fulfilled as "0" quantity.
F-TA-32 The solution shall print a manifest for each location/facility/unit by date detailing the 0 Roadmap Workflow Release 4.0 COMMISSARY Canteen
canteen orders included for distribution.
F-TA-33 Canteen Administration staff shall have the ability to refund a fulfilled order which 0 Roadmap Workflow Release 4.0 COMMISSARY Canteen
returns the money to the inmate's account,
F-TA-34 Canteen Administration staff shall have the ability to refund a partial order which Cl Roadmap Workflow Release 4.0 COMMISSARY Canteen
returns the partial amount to the inmate's account.
F-TA-35 The solution shall be capable of automatically generating a unique tracking/sequence 0 Roadmap Workflow Release 4.0 COMMISSARY Canteen
number for each canteen order.
F-TA-36 The solution shall provide the ability to restrict canteen orders/purchases and allow for 0 Roadrnap Workflow Release 4.0 COMMISSARY Canteen
the manual override of the restriction (i.e., deny canteen orders for inmates who have
lost canteen privileges).
F-TA-37 The inmate accounting module shall provide the inmate account balance in real time. 0 Roadmap Workflow Release 4.0 COMMISSARY Canteen
F-TA-38 The solution shall provide the ability for a user to enter a reason code for non-delivery. 0 Roadmap Workflow Release 4.0 COMMISSARY Canteen
F-TA-39 The solution shall provide the ability to create and maintain vending inventories and 0 Roadmap Workflow Release 4.0 COMMISSARY Canteen
reports.
Inventory Processing
F-TA-40 The solution shall provide an online screen to allow the Canteen Administrator to 0 Roadmap Workflow Release 4.0 COMMISSARY Canteen
perform maintenance on the canteen items available to the inmates. Maintenance
includes but is not limited to the following: adding new items, deleting items, changing
item descriptions, changing item unit pricing, adding special item and restriction
designations, unit of measure for disbursement.
F-TA-41 The solution shall keep a running inventory and has capacity for tracking of inventory 0 Roadmap Workflow Release 4.0 COMMISSARY Canteen
adjustments, including sales and non-sales adjustments.

SERIAL 13139-RFP
F-TA-42 The solution shall provide a method for recording manual changes to stock items which 0 Roadmap Workflow Release 4.0 COMMISSARY Canteen
include a reason for adjustment. The reasons for the changes shall be table driven.
F-TA-43 The solution shall record all changes to stock and reasons for each change. 0 Roadmap Workflow Release 4.0 COMMISSARY Canteen
F-TA-44 The solution shall provide entry for stock item variables including but not limited to: 0 Roadrnap Workflow Release 4.0 COMMISSARY Canteen
item name, supply vendor, item unit sales price, re-order quantity, sales restriction
(male, female, discipline), case order quantity (unit of measure), case order cost.
F-TA-45 The solution shall provide calculation capabilities for translating order receiving 0 Roadmap Workflow Release 4.0 COMMISSARY Canteen
quantities to disbursement inventory unit quantities.
F-TA-46 The solution shall provide harcleopy purchase orders to be issued to vendors. 0 Roadmap Workflow Release 4.0 COMMISSARY Canteen
. ; . 4 COMMISSARY Canteen
orders. The issuing of electronic
purchase orders is a gap that has been
defined as a future requirement and has
been removed an a requirement.
F-TA-48 The solution shall provide a warning mechanism to alert canteen staff when item stock 0 Roadmap Workflow Release 4.0 COMMISSARY Canteen
falls below a designated minimal level.
F-TA-49 The solution shall provide a process for recording of items given to inmates that are 0 Roadmap Workflow Release 4.0 COMMISSARY Canteen
indigent.
F-TA-50 The solution shall provide a method for recording and tracking of gratis transactions for 0 Roadmap Workflow Release 4.0 COMMISSARY Canteen
each inmate trustee.
F-TA-5 I The solution shall deduct gratis transactions from the canteen inventory without 0 Roadmap Workflow Release 4.0 COMMISSARY Canteen
deducting any funds from the inmate trust account.
F-TA-52 The solution shall provide an online transaction to allow staff to conduct a physical 0 Roadmap Workflow Release 4.0 COMMISSARY Canteen
inventory of all items in stock.
F-TA-53 The solution shall provide an over/short transaction to allow staff to record physical 0 Roadmap Workflow Release 4.0 COMMISSARY Canteen
inventory discrepancies_
F-TA-54 The solution shall establish, maintain and track inventories at multiple warehouse 0 Roadmap Workflow Release 4.0 COMMISSARY Canteen
locations (front, back and vending).
Administration
F-TA-55 The solution shall provide an on-line audit trail including a transaction amount for all 0 Roadmap Workflow Release 4.0 TRUST ACCOUNTING Budget / Finance
money movement with a reason for movement.
F-TA-56 The solution shall provide a text field for additional comments for audit trails. 0 Roadmap Workflow Release 4.0 TRUST ACCOUNTING Budget / Finance

SERIAL 13139-RFP
F-TA-57 The solution shall be capable of printing the audit trail for all inmate account activity 0 Roadmap Workflow Release 4.0 TRUST ACCOUNTING Budget / Finance
for: a specific day, a date range, and a specific inmate.
F-TA-58 The solution shall generate a daily sales receipts report detailing all canteen sales for 0 Roadmap Workflow Release 4.0 COMMISSARY Canteen
the day by facility and in total.
F-TA-59 The solution shall generate a Canteen Operations Annual Statement summarizing daily 0 Roadmap Workflow Release 4.0 COMMISSARY Canteen
sales and inventory totals using date parameters.
F-TA-60 The solution shall provide a receipt for inmate authorized release of funds with a 0 Roadmap Workflow Release 4.0 TRUST ACCOUNTING Budget / Finance
signature line and/or electronic means of signature. The receipt shall include but is not
limited to the following: inmate's booking number, inmate's full name, authorized
vendor's name, amount released.
F-TA-6I The solution shall be capable of tracking and totaling posted orders on a daily basis to 0 Roadmap Workflow Release 4.0 COMMISSARY Canteen
facilitate reconciliation.
F-TA-62 The solution shall be capable of identifying dormant accounts and dollar amounts to be 0 Roadmap Workflow Release 4.0 TRUST ACCOUNTING Budget! Finance
transferred to the Arizona Department of Revenue.
F-TA-63 The solution shall be capable of printing notifications to be mailed to inmates with 0 Roadmap Workflow Release 4.0 TRUST ACCOUNTING Budget / Finance
unclaimed property.
F-TA-64 The solution shall be capable of tracking the mailing of notifications. 0 Roadmap Workflow Release 4.0 TRUST ACCOUNTING Budget / Finance
F-TA-65 The solution shall provide the ability to record details of persons depositing money in 0 Roadmap Workflow Release 4.0 TRUST ACCOUNTING Budget / Finance
an inmate account.
F-TA-66 The solution shall provide a capability for inmate account balances to accompany them 0 Roadmap Workflow Release 4.0 TRUST ACCOUNTING Budget / Finance
on transfer to another facility according to business rules. See Business Rules
Requirements.
F-TA-67 System Administrators shall be allowed to create new categories of fees and change the 0 Roadmap Workflow Release 4.0 TRUST ACCOUNTING Budget / Finance
dollar amount of all fees.
F-TA-68 The solution shall allow for a maximum order per item limit to be controlled by the G Roaclmap Workflow Release 4.0 COMMISSARY Canteen
System Administrator.
F-TA-69 The solution shall allow for a maximum dollar value limit to be controlled by the 0 Roadmap Workflow Release 4.0 COMMISSARY Canteen
System Administrator.
F-TA-70 The solution shall allow for an indigent account balance value designation to be 0 Roadmap Workflow Release 4.0 TRUST ACCOUNTING Budget! Finance
controlled by the System Administrator.
F-TA-7 I The inmate accounting module shall follow generally accepted accounting principles. 0 Roadmap Workflow Release 4.0 TRUST ACCOUNTING Budget / Finance

SERIAL 13139-RFP
• • ••: :: .., tt 0 See Anchmont C Challenging OF NIA
Costly-Regoireinents
Archiving is no longer required.
F-TA-73 The solution shall support external deductions against inmate accounts that are 0 Roadinap Workflow Release 4.0 TRUST ACCOUNTING Budget / Finance
processed by other business units.
F-TA-74 The solution shall support all mandated and non mandated inmate account deductions. 0 Roadmap Workflow Release 4,0 TRUST ACCOUNTING Budget / Finance
F-TA-75 The solution shall provide the ability to configure payment priority. 0 Roadmap Workflow Release 4.0 TRUST ACCOUNTING Budget / Finance
F-TA-76 The solutions shall provide the ability to transfer money from one booking number to a 0 Roadmap Work/low Release 4.0 TRUST ACCOUNTING Budget / Finance
new booking number according to business rules, See Business Rules requirements.
F-TA-77 The solution shall provide the ability to create canteen usage reports by item with date 0 Roadmap Workflow Release 4.0 COMMISSARY Canteen
parameters.
TR - Transportation Requirements
F-TR-I The solution shall provide the ability to assign an inmate to a transportation group 0 Roadmap Workflow Release 4.5 TRANSPORTATION Transportation
based on workflow tasks.
F-TR-2 The solution shall provide the ability to document attributes of a transportation unit 0 Roadmap Workflow Release 4.5 TRANSPORTATION Transportation
such as but not limited to:
Driver, Vehicle Capacity Information, Vehicle Identifiers, Inmate Security
Classification, Adult or Juvenile Transportation Unit, Male or Female Transportation
Unit, ADA — Wheelchair
F-TR-3 The solution shall provide the ability to alert staff if they attempt to assign an inmate to 0 Roacimap Workflow Release 4.5 TRANSPORTATION Transportation
a transportation unit that cannot accommodate the inmate's needs such as keep-aways
and man warning, based on user defined business rules.
F-TR-4 I. The solution shall provide the ability to generate a report listing inmates assigned to a 0 Roadmap Workflow Release 4,5 TRANSPORTATION Transportation
particular transport unit during a specified date and time.
F-TR-5 The solution shall provide the ability for transportation staff to print the documents that 0 Roadmap Workflow Release 4,5 TRANSPORTATION Transportation
need to be taken as part of the transportation trip.
F-TR-6 The solution shall provide the ability for the transportation staff to create incidents such G Roadmap Workflow Release 4.5 TRANSPORTATION Transportation
as but not limited to: contraband, accidents.
F-TB.-7 The solution shall provide the ability to create workflows for transportation related 0 Roadmap Workflow Release 4.5 TRANSPORTATION Transportation
activities such as but not limited to Court Transportation, Extradition, Funeral, and
Bereavement.
F-TR-8 The solution shall provide the ability to invoice for transportation related services. 0 Roadmap Work-flow Release 4.5 TRANSPORTATION Transportation
VS.- Visitation Requirements

SERIAL 13139-RFP
F-VS-1 The solution shall provide the ability to search visitor information by inmate and visitor 3 VISITATION Visits
using parameters such as history, date, etc.
F-VS-2 The solution shall be able to log a visitation request, with visitor submitting a form with 3 VISITATION Visits
their identifying information and inmate booking number.
F-VS-3 The solution shall provide solution-wide lookup capability to determine the inmate 3 VISITATION Visits
housing location.
F-VS-4 The solution shall provide the capability to see the inmate's schedule to determine if 3 VISITATION Visits
he/she is available for a visit. See Scheduling requirements.
F-VS-5 The solution shall provide the ability to log the following, but not limited to visitor 3 VISITATION Visits
name, date of birth, driver's license number and address if the visitor has not already
been entered into the database.
F-VS-6 The solution shall be able to retrieve the information on a visitor to determine if he/she 3 VISITATION Visits
is already in the database.
F-VS-7 The solution shall provide the ability to log visitor contact information. 3 VIS 1TATION Visits
F'-VS-8 The solution shall be able to perform a warrant check to determine if there are any open I Custom Interface DC1
warrants on the visitor.
F-VS-9 The solution shall be able to check if the visitor is a convicted felon, and therefore not I Custom Interface DC1
eligible to visit.
F-VS-10 The solution shall allow a visit to be scheduled and prioritized according to business 3 VISITATION Visits
rules.
F-VS-1 I The solution shall send a notification to the inmate's housing unit letting them know 3 MESSAGING Visits
that a visit has been scheduled.
F-VS-12 The solution shall log the outcome of the scheduled visit, whether it occurred, and the 3 VISITATION Visits
date and time.
F-VS-I 3 The solution shall provide the ability to enter special contact information. 3 VISITATION Visits
F-VS-14 The solution shall provide the ability to flag visitors who are uriwanted/barmed, the 3 VISITATION Visits
reason, duration, and authorizer.
WK - Workflow Requirements
Types of Task Allocation Assignment
F-WK-1 The solution shall provide the ability to assign tasks by user. 3 TASK MANAGEMENT Workflow
F-WK-2 The solution shall provide the ability to assign tasks to a group of users by functional 3 TASK MANAGEMENT Workflow
area.
F-WK-3 The solution shall provide the ability to assign tasks by role. 3 TASK MANAGEMENT Workflow
F-WK-4 The solution shall provide the ability to assign tasks by workload type. 3 TASK MANAGEMENT Workflow

SERIAL 13139—RFP
F-WK-5 The solution shall provide the ability to assign tasks on a push-driven basis based on 3 TASK MANAGEMENT Workflow
business rules.
F-WK-6 The solution shall provide the ability to assign tasks using a manual intervention. 3 TASK MANAGEMENT Workflow
Manual or User-Initiated Tasks
F-WK-7 The solution shall provide the ability for manual task status changes. 3 TASK MANAGEMENT Workflow
F-WK-8 The solution shall provide the ability for a manual business rule execution. 3 TASK MANAGEMENT Workflow
Due Dates
F-WK-9 The solution shall provide the ability for a user to assign multiple due dates in the same 3 TASK MANAGEMENT Workflow
workflow process.
F-WK-I 0 The solution shall provide the ability for a user to assign a static due date. 3 TASK MANAGEMENT Workflow
F-WK-11 The solution shall provide the ability for a user to assign dynamic due date. 3 TASK MANAGEMENT Workflow
F-WK-12 The solution shall provide the ability for a user to assign a process start time. 0 Roadmap Workflow Release 3.5 Workflow
F-WK-13 The solution shall provide the ability for a user to assign tasks based on target end time. 3 TASK MANAGEMENT Workflow
F-WK-14 The solution shall provide the ability for a user to assign user-defined dates. 3 Workflow
To-Do List
F-WK-15 The solution shall provide the ability for a user to filter with all tasks. 3 TASK MANAGEMENT Workflow
F-WK-16 The solution shall provide the ability for a user to filter with overdue tasks. 3 TASK MANAGEMENT Workflow
F-WK-17 The solution shall provide the ability for a user to filter daily, weekly and monthly 3 TASK MANAGEMENT Workflow
overdue tasks.
F-WK-18 The solution shall provide the ability for a user to build sort filters for tasks. 3 TASK MANAGEMENT Workflow
Watch List
F-WK-l9 The solution shall provide the ability for a user to create a watch list using all tasks. 3 TASK MANAGEMENT Workflow
F-WK-20 The solution shall provide the ability for a user to create a watch list using overdue 3 TASK MANAGEMENT Workflow
tasks.
F-WK-21 The solution shall provide the ability for a user to create a watch list using daily, 3 TASK MANAGEMENT Workflow
weekly and monthly overdue tasks.
F-WK-22 The solution shall provide the ability for a user to create a watch list using user defined 3 TASK MANAGEMENT Workflow
filters.
Workflow Reports

SERIAL 13I39-RFP
F-WK-23 The solution shall provide the ability for a user to create a workflow report of all 3 REPORTING/BYWORD Reporting
overdue tasks. PROCESSING
F-WK-24 The solution shall provide the ability for a user to create a workflow report of all daily, 3 REPORTING/BYWORD Reporting
weekly and monthly overdue tasks. PROCESSING
F-WK-25 The solution shall provide the ability for a user to create a workflow report of all stalled 3 REPORTING/BYWORD Reporting
tasks. PROCESSING
Woridlow Step(s) Management
F-WK-26 The solution shall provide the ability for a user to pause or resume workflow steps. 0 Roadmap Workflow Release 3.5 ALL Workflow
F-WK-27 The solution shall provide the ability for a user to restart workflow steps. 0 Roadroap Workflow Release 3.0 Workflow
F-WK-2S The solution shall provide the ability for a user to delete workflow steps. 3 ALL Workflow
F-WK-29 The solution shall provide the ability for a user to abort workflow steps. 3 ALL Workflow
F-WK-30 The solution shall provide the ability for a user to manually override workflow steps 3 ALL Workflow
data.
Workflow Monitoring
F-WK-31 The solution shall provide the ability for a user to monitor the status of all workflow 3 REPORTING/BYWORD Workflow
instances in a single view. PROCESSING
F-WK-32 The solution shall provide the ability for a user to monitor the status of individual 3 REPORTING/BYWORD Workflow
workflow instances. PROCESSING
F-WK-33 The solution shall provide the ability for user workflow monitoring in a graphical 3 REPORTING/BYWORD Workflow
dashboard format. PROCESSING
F-WK-34 The solution shall provide the ability for a user to drill down from the monitoring 3 REPORTING/BYWORD Workflow
dashboard to see a specific workflow instance in a particular status. PROCESSING
F-WK-35 Workflow projection capabilities - Based on the calculated execution time and the 0 Roadrnap Workflow Release 3.5 REPORTING/BYWORD Workflow
step/task standard durations (norms, the workflow engine 'projects the completion PROCESSING
time).
Workflow Statistics
F-WK-36 The solution shall provide the ability for a supervisor to monitor user workload and 3 REPORTING/BYWORD Workflow
produce a statistical report. PROCESSING
F-WK-37 The solution shall provide the ability for a user to derive cycle time statistics between 3 Workflow
workflow steps.
F-WK-38 The solution shall provide the ability for a supervisor to monitor workflow instance 3 REPORTING/BYWORD Workflow
aging statistics. PROCESSING

SERIAL I3139-RFP
F-WK-39 The solution shall provide the ability for a supervisor to monitor workflow route 3 REPORTING/BYWORD Workflow
statistics. PROCESSING
F-WK-40 The solution shall provide the ability for a supervisor to monitor workflow step 3 REPORTING/BYWORD Workflow
statistics. PROCESSING
F-WK-41 The solution shall provide the ability for a supervisor to monitor workflow user 3 REPORTING/BYWORD Workflow
statistics, PROCESSING
F-WK42 The solution shall provide the ability for a supervisor to monitor workflow role 3 REPORTING/BYWORD Workflow
statistics. PROCESSING
Audit Trails
F-WK-43 The solution shall provide the ability to capture the audit trail for all workflow events. 3 AUDIT Non-Functional
Requirements
F-WK-44 The solution shall provide the ability to capture the audit trail for all user inputs on 3 ' AUDIT Non-Functional
forms. Requirements
F-WK-45 The solution shalt provide the ability to capture the audit trail for all user 3 AUDIT Non-Functional
assignments/releases. Requirements
F-WK-46 The solution shall provide the ability to capture the audit trail for all escalation actions. 0 This will be progressive with each AUDIT Non-Functional
release Requirements
F-WK-47 The solution shall provide the ability to capture the audit trail for all notifications. 0 Roadmap Workflow Release 3.5 N/A
F-WK-48 The solution shall provide the ability to capture the audit trail for all each successful 0 Roadma.p Workflow Release 3.5 N/A
rule execution.
Resource Organization
F-WK-49 The solution shall provide the ability for both central and distributed resource 3 ALL Workflow
ownership and administration of documents, tasks and workflow_
F-WK-50 The solution shall provide the ability for organization hierarchies of documents, tasks 3 REPORTING/BYWORD Workflow
and workflows. PROCESSING
Search and Query for Workflows
F-WK-5 I The solution shall provide the ability for users to search for tasks by task name. 3 TASK MANAGEMENT Workflow
F-WK-52 The solution shall provide the ability for users to search for tasks by workflow name. 3 TASK MANAGEMENT Workflow
F-WK-53 The solution shall provide the ability for users to search for tasks by status. 3 TASK MANAGEMENT Workflow
F-WK-54 The solution shall provide the ability for users to search for tasks by start time, 3 TASK MANAGEMENT Workflow

SERIAL 13139-RFP
F-WK-55 The solution shall provide the ability for users to search for tasks by due time. 3 TASK MANAGEMENT Workflow
F-WK-56 The solution shall provide the ability for users to search for tasks by end time. 3 TASK MANAGEMENT Workflow
F-WK-57 The solution shall provide the ability for users to search for tasks by participant names, 3 TASK MANAGEMENT Workflow
F-WK-58 The solution shall provide the ability for users to run ad-hoc queries based on arbitrary 3 TASK MANAGEMENT Workflow
process data,
F-WK-59 The solution shall provide the ability for users to create ad-hoc queries to support full 3 REPORTING/BI/WORD Non-Functional
SQL syntax. PROCESSING Requirements
F-WK-60 The solution shall provide the ability for users to store queries that can be saved for 3 REPORTING/BI/WORD Non-Functional
reuse. PROCESSING Requirements
Task Information
F-WK-61 The solution shall provide the ability to notify user what the requirements are to 3 TASK MANAGEMENT Workflow
complete tasks.
F-WK-62 The solution shall provide the ability to notify user what optional actions may be 3 TASK MANAGEMENT Workflow
applied but not required to complete tasks,
F-WK-63 The solution shall provide the ability to make tasks disappear automatically when 3 TASK MANAGEMENT Workflow
designated by an administrator as obsolete.
F-WK-64 The solution shall provide the ability for a user to see the current workflow status. 3 TASK MANAGEMENT Workflow
Messaging
F-WK-65 The solution shall provide the ability to move information in a structured XML format. 3 MESSAGING Non-Functional
Specifically, the solution shall support the import and export of data according to the Requirements
state data dictionary, which is based on the Global Justice XIVIE Data
Model(GJXDM)/National Information Exchange Model(NIEM),
F-WK-66 The integration model should also support the development of Web services against the 3 MESSAGING Non-Functional
JMS. Requirements
F-WK-67 The solution shall support interfaces to federal, state, and local applications. It shall 3 MESSAGING Non-Functional
support real-time data transfer, as well as batch mechanisms for data transfer, including Requirements
file transfer protocol (FTP).
F-WK-68 The solution shall support MCSO standard messaging protocols that are sufficiently 3 MESSAGING Non-Functional
documented in non-functional requirements so that the messaging interfaces can be Requirements
used by future applications.
E-WK-69 The solution shall integrate with the existing ACJIS and CJIS messaging systems. See I Custom interface DC1
Appendix 2 - Interface Requirements.

SERIAL 13139-RFP
F-WK-70 The solution shall be able to search historical CJIS inmate information from other 1 Custom interface DC1
institutions.
F-WK-71 The solution shall be able to send message based on routing technologies approved by 1 Enhancement MESSAGING DCI
ACJIS and CRS policy.
Line 33
in Attachment A Cost Proposal
F-WK-72 The solution shall be able to receive messages based on routing technologies approved I Enhancement MESSAGING DC1
by ACJIS and CJIS policy.
Line 34
in Attachment A Cost Proposal
F-WK-73 The solution shall be able to send secure messages between users or groups of users 3 MESSAGING DCI
within MCSO.
F-WK-74 The solution shall be able to re-transmit messages based on message transaction logs. 1 Enhancement MESSAGING DC1
Line 35
in Attachment A Cost Proposal
F-WK-75 The solution shall be able to record all sent and received messages into transaction and 1 Enhancement MESSAGING DCI
audit logs.
Line 36
in Attachment A Cost Proposal
Workflow System Administration
Woridlow Graphical Designer
F-WK-76 The solution shall provide the ability for an administrative user to design workflows 3 TASK MANAGEMENT Workflow
graphically.
F-WK-77 The solution shall provide the ability for an administrative user to display a top-level 3 TASK MANAGEMENT Workflow
workflow status diagram.
F-WK-78 The solution shall provide the ability for an administrative user to display a detailed 3 TASK MANAGEMENT Workflow
technical workflow diagram.
F-WK-79 The solution shall provide the ability for an administrative user to drag-and-drop 3 TASK MANAGEMENT Workflow
workflow components.
F-WK-80 The administrative user can model workflows with minimal technical training, 3 TASK MANAGEMENT Workflow
F-WK-81 The solution shall provide the ability for an administrative user to drag-and-drop 3 REPORTING/BI/WORD Document
document template components. See Document Management Requirements. PROCESSING Management
F-WK-82 The solution shalt provide the ability for an administrative user to split(s) and/or re- 3 TASK MANAGEMENT Workflow
join(s) a workflow branch.

SERIAL 13139-RFP
F-WK-83 The solution may provide the ability for an administrative user to integrate with 3 PROGRAMS & SERVICES Programs
individual and/or group calendars to drive participant selection.
F-WK-84 The solution shall provide the ability for an administrative user to prevent workflow 0 Roadrnap Workflow Release 3.0 TASK MANAGEMENT Workflow
step creation based on validation rules.
F-WK-85 The solution shall provide the ability for an administrative user to alter workflow steps 0 Roadrnap Workflow Release 3.5 N/A
based on related content data.
F-WK-86 The solution shall provide the ability for an administrative user to alter workflow 0 Roadmap Workflow Release 3.5 - N/A
instances without negatively impacting in-process transactions.
E-WK-87 The solution shall provide the ability to define user or group based routing on workflow 3 TASK MANAGEMENT Workflow
variables and status.
F-WK-88 The solution shall provide the ability to support attachment(s) that are referenced by all 3 REPORTING/BYWORD Document
workflow instances. PROCESSING Management
F-WK-89 The solution shall provide the ability to support attachment(s) that are specific to a 3 REPORTING/131/WORD Document
workflow step. PROCESSING Management
F-WK-90 The solution shall provide assigned unique ids to all workflow instances and steps. 3 TASK MANAGEMENT Workflow
F-WK-91 The solution shall provide the ability to define target dates and times based on the 3 TASK MANAGEMENT Workflow
assigned to user or group.
F-WK-92 The solution shall provide the ability to define target day, dates and times can change in 0 Partial: Due dates for tasks can be TASK MANAGEMENT Workflow
mid-stream depending on work/low variables and status. changed by a user manually. Auto
change based on variables will be
available in Workflow 3.5
F-WK-93 The solution shall provide the ability to support multiple user roles in a workflow. 3 TASK MANAGEMENT Workflow
F-WK-94 ( The solution shall provide the ability to check for sufficient user rights to execute 3 SECURITY MODEL Workflow
workflow actions.
Workflow Engine
F-WK-95 The solution shall provide a task-driven workflow engine. 3 TASK MANAGEMENT Workflow
F-WK-96 The solution shall provide a goal-driven workflow engine. 3 TASK MANAGEMENT Workflow
F-WK-97 The solution shall provide a workflow to have multiple concurrent statuses. 3 TASK MANAGEMENT Workflow
F-WK-98 The solution shall provide a workflow to here-routed manually. 3 TASK MANAGEMENT Workflow
F-WK-99 The solution shall provide a workflow to be automatically re-routed based on time. 3 TASK MANAGEMENT Workflo

SERIAL 13139-REP
F-WK-100 The solution shall provide subsequent workflow steps activated automatically upon 3 TASK MANAGEMENT Workflow
completion of previous steps
F-WK-101 The solution shall provide a subsequent workflow activated based on time. 0 Roadrnap Workflow Release 15 TASK MANAGEMENT Workflow
F-WK-102 The solution shall provide a subsequent workflow to be activated without requiring 3 TASK MANAGEMENT Workflow
completion of previous steps.
F-WK-103 The solution shall provide a workflow system calendar that distinguishes work days, 0 Roadmap Workflow Release 3.5 TASK MANAGEMENT Workflow
holidays/vacation, and work day start/end times.
F-WK-104 The solution shall provide a workflow engine to use business rules to initiate 3 TASK MANAGEMENT Workflow
workflows.
F-WK-1 05 ' The solution may provide a third party or external workflow engine to be integrated. 3 TASK MANAGEMENT Workflow
Workflow Use
' F-WK-106 The solution shall provide the ability to maintain separate to-do and watch lists for each 3 TASK MANAGEMENT Workflow
user.
F-WK-107 The solution shall provide the ability to filter and search for user-specific to-do and 3 TASK MANAGEMENT Workflow
watch lists.
F-WK-10S The solution shall provide the ability to track and display workflow step status, active 3 TASK MANAGEMENT Workflow
step and current workflow required actions.
F-WK-109 The solution shall provide the ability to add comments to workflow instances, and to 3 ALL Workflow
reference external content.
F-WK-110 The solution shall provide the ability to maintain audit trails for change tracking to 0 Roadrnap Workflow Release 3.5 AUDIT Non-Functional
workflows. Requirements
F-WK-111 The solution shall provide the ability to acknowledge receipt or confirmation delivery 3 TASK MANAGEMENT Workflow
to assigned user or group as part ofa defined workflow.
F-WK-112 The solution shall provide the ability to allow manual override of workflow steps. 3 TASK MANAGEMENT Workflow
Workflow Messaging
F-WK-113 The solution shall provide the ability for an administrative user to define notification 3 MESSAGING Workflow
alerts to user or a group of users responsible for workflow steps.
F-WK-114 The solution shall provide the ability for an administrative user to define workflow 3 MESSAGING Workflow
notification mechanisms that integrate with desktop office products.
F-WK-115 The solution shall provide the ability for an administrative user to define unlimited 3 TASK MANAGEMENT Workflow
recurring notifications.

SERIAL I3139-RFP
F-WK-116 The solution shall provide the ability for an administrative user to define recurring 3 TASK MANAGEMENT Workflow
notifications with maximum occurrence count.
F-WK-117 The solution shall provide the ability for an administrative user to define a single 3 TASK MANAGEMENT Workflow
notification within a defined time period.
F'-WK-118 The solution shall provide the ability for an administrative user to define when a user 3 TASK MANAGEMENT Workflow
may or may not switch notifications off.
F-WK-119 The solution shall provide the ability for an administrative user to define notification 0 Roadmap Workflow Release 3.5 TASK MANAGEMENT Workflow
and escalation paths for overdue workflow actions.
F-WK-120 The solution shall provide the ability for an administrative user to define reminder 0 Roadmap Workflow Release 3.5 TASK MANAGEMENT Workflow
notifications as scheduled task deadlines approach.
F-WK-121 The solution shall provide the ability to remove individuals from the alert list and allow 3 Enhancement TASK MANAGEMENT Workflow
the entry for a reason for removal.
Can be met with product
Workflow Management
F-WK-122 The solution shall provide the ability for an administrative user to define authorized 3 TASK MANAGEMENT Workflow
super-users to manage workflow processes.
F-WK-123 The solution shall provide the ability for an administrative user to save and rename 3 TASK MANAGEMENT Workflow
workflows.
F-WK-124 The solution shall provide the ability for an administrative user to control and interact 0 Roadmap Workflow Release 3.5 Workflow
with workflow instances: creation, activation, suspension, termination.
F-WK-125 The solution shall provide the ability for an administrative user to define notification 3 Workflow
features based on workflow versions.
F-WK-126 The solution shall provide the ability for an administrative user to define who can 3 TASK MANAGEMENT Workflow
delegate rights to users for workflow steps.
Workflow Reporting
F-WK-127 The solution shall provide the ability for an administrative user to report on the status of 3 REPORTING/BYWORD Workflow
a content data for a workflow process. PROCESSING
F.-WK-128 The solution shall provide the ability for an administrative user to report on the status of 3 REPORTING/BYWORD Workflow
all workflow instances. PROCESSING
F-WK-129 The solution shall provide the ability For an administrative user to report by workflow 3 REPORTING/BYWORD Workflow
content data type, content data or categories of content data types. PROCESSING
Versioning

SERIAL 13139-RFP
F-WK-130 The solution shall provide the ability for an administrator to force running instances to 0 See Attcturient C Challenging or N/A
always be upgraded to the latest version. Costly Requirements
As discussed during the gap sessions, a
change to a business process would be
handled as a new business process that
users will have access to from that
point in time. Existing instances of the
process will continue to run on the old
model. Overall, versioning of
processes will be handled within
Workflow (as two separate versions of
the process) rather than being a part of
JBOSS's process versioning. This
approach will also provide better
control for MCSO to roll out process
changes as part of a defined change
management process.
See Attchment C Challenghig or N/A
staying with old version. Costly Requirements
See comment in F-WK-130
F-WK-132 The solution shall provide the ability for an administrator to force end users to choose 0 See Attchment C Challenging or N/A
which-instances-to-upgrade, Costly Requirements
See comment in F-WK-130
F-WK-133 0 : N/A
Costly Requirements
See comment in F-WK-130
F-WK-134 The solution shall provide the ability for an administrator to force end user to choose to 0 See comment in F-WK-130 N/A
upgrade all running instances.
F-WK-135 - : - : . : - .- .. : : . : .- . . : : : • . I.-- - - -: : : : - - - .. - , „ .... 3 See Attclunent C Challenging or N/A
reactivated as the active version. Gost-ly-R-equireinetitsSee comment in
F-WK-130
Simulation/Validation
F-WK-136 The solution shall provide the ability for an administrator to check for infinite loops. 3 TASK MANAGEMENT Workflow
F-WK-137 The solution shall provide the ability for an administrator to check for circular 3 TASK MANAGEMENT Workflow
references.
F-WK-138 The solution shall provide the ability for an administrator to check for ability to 3 TASK MANAGEMENT Workflow
complete the process.

SERIAL 13139-RFP
F-WK-139 The solution shall provide the ability for an administrator to check for uses 3 TASK MANAGEMENT Workflow
permissions for the ability to complete task.
F-WK-140 The solution shall provide the ability for an administrator to perform what-if analyses. 3 TASK MANAGEMENT Workflow
Workflow Initiation
F-WK-141 The solution shall provide the ability for a workflow administrator to make workflows 3 TASK MANAGEMENT Workflow
to be initiated programmatically.
F-WK-142 The solution shall provide the ability for a workflow administrator to make workflows 3 TASK MANAGEMENT Workflow
to be excluded from manual initiation.
F-WK-143 The solution shall provide the ability for a workflow administrator to make workflows 3 TASK MANAGEMENT Workflow
to be initiated only by select users.
F-WK-144 The solution shall provide the ability for a workflow administrator to make workflows 3 TASK MANAGEMENT Workflow
to be initiated only by authenticated users.
F-WK-145 .- : : . 1 • - - .. : : i : • 14 F,oe Attchmont C Challenging or N/A
Co.-.tly Roquiromonta-
As part of the discussions, this was
deemed as not needed.
F-WK-146 The solution shall provide the ability for a workflow administrator to make workflows 3 TASK MANAGEMENT Workflow
to be initiated through a link on an external web page.

SERIAL 13139-RFP
10.2. Technical and Non-Functional Requirements
10.2.1. Documentation
The application shall include documentation for the following:
o Installation
o Configuration (Web Help, User Manuals, Hint Text)
o Application Programming Interface (service contract APIs)
o Entity Relationship Diagrams (exposed for reporting or interfaces)
o Data Model Dictionary (exposed for reporting or interfaces)
As the application increases in breadth and depth of functionality the documentation to support the
application will be updated and provided with subsequent releases of the Workflow application.
10.2.2. Installation
The Workflow application includes installation documentation for alt components developed by Syscon.
Syscon does not provide installation instructions or configuration settings for third-party components
(Application Server, Database, etc.) as the vendor of these components provides the installation and
configuration instructions. Syscon will provide any special configuration notes, if required_
10.2.3. Configuration
The Workflow configuration options are
Configuration Option Description
Custom Fields Allows an administrator to add a new field and define its data type (e.g., text, numeric) and add it to one of
the predefined Workflow data objects. After a custom field is configured, it will be displayed on Workflow
application pages and can be used as a source of data that is retrieved for reports,
Business Process Allows an administrator to configure a sequence of Workflow application pages that business users will
access to perform a task. Additionally, you can define which tasks should spawn in the task pool for later
completion as part of a business process.
Reports & Dashboard Allows an administrator to create simple or complex reports using 131 Publisher reporting capabilities, which
are embedded in the Workflow application.
User Administration Allows an administrator to create, modify, and deactivate user accounts and to define role-based access
permissions within the application.
List of Values (LOV) Allows an administrator to define the values to be listed in various Workflow application drop-down menus.
Labels Allows an administrative user to define all labels on all pages within the Workflow application, This
configuration is performed in a fiat file, not via a user interface.
Templates Allows an administrative user to define the templates used for reporting events that occur, empowering your
organization to consistently collect and present data in a standard way.
Some configurable features may not be configured via the front end of the application. For example, data
exchange routes may be defined within an XML file, but not via the front end. Additionally system backups
can be managed via various database and operating system tools, but not via the Workflow application itself.
10.2.4. Application and Configuration Knowledge Base

SERIAL 13139-RFP
The Workflow application includes Web Help, User Manuals and, where appropriate, Hint Text.
o Web Help is provided so that users can access the help functionality from within the browser
online.
o User Manuals are exports of the Web Help that can be reviewed in an offline capacity and can be
printed.
o Hint Text is provided within the application on specific components to guide the user where
appropriate. Hint text is not provided where the label of the components is sufficient to
understand the business context.
10.2.5, Application Programming Interface
The Workflow application includes documentation for the Application Programming Interface (API) for all
of its business service contracts in the form of Java Does. The Java Does will be updated with each release
of the Workflow application.
10.2.6. Entity Relationship Diagram
The Workflow application includes documentation in the form of Entity Relationship diagrams for all
views that are externalized for the purpose of reporting or interfaces. The entity relationship diagrams will
be updated with each release o f the Workflow application.
10.2.7. Data Model Dictionary
The Workflow application includes documentation in the form of a data model dictionary for all views that
are externalized for the purpose of reporting or interfaces. The data model dictionary will be updated with
each release of the Workflow application.
The data model dictionary includes fields by view, and a summary field list by view, including field
descriptions.
10.2.8. Non-Functional and Technical Requirements Matrix (Exhibit 13 Sub b)
Additionally, Syscon shall provide an application system that meets all of the following Technical and
Non-Functional requirements:

SERIAL 13139-RFP
Column Header Column Description
Section/ID Identifies the Attachment Section Requirement ID with the detailed requirement information.
Requirements Identifies the detailed requirement information from the Attachment E Document.
Response Compliance statements are limited to the following three choices:
1. COMPLY - The solution meets or exceeds the specified requirement.
2. COMPLY WITH CLARIFICATION — The solution does not meet the exact stated requirement; however, it meets a
substantial portion of or meets the intent of the requirement. Contractor must provide a detailed explanation when using this
statement. Alternate proposal items would fall under this category of compliance if they meet the intent of the REP.
3. EXCEPTION - The solution does not meet the specified requirements. Contractor must provide a detailed explanation
when using this statement.
Note This column is to be used to clarify any Response, and is required for Responses 2. COMPLY WITH CLARIFICATION or 3.
EXCEPTION.
Section/ID Requirements Response Note
Accessibility
NE-AC-1.1 The solution shall be accessible via web browser. COMPLY
NE-AC-1.2 The solution shall be accessible via mobile devices. COMPLY
NE-AC- I .3 The solution shall provide specific information that is COMPLY
accessible via kiosk devices.
NE-AC-1.4 The solution shall be accessible via IVR. COMPLY
Auditability
NE-AU-2.1 The solution shall provide search capability to view the COMPLY
audit information by source system, target system, date
and time, or other defined set of parameters.
NE-AU-2.2 The solution shall maintain audit records as either: active, COMPLY WITH The Workflow application is designed so that data
archived, or purged (removed from the active database but CLARIFICATION is always live and always available. Data archival
available for query and reporting) based on end user is not a native feature of the Workflow application;
configurable time period, rather it is a feature of its underlying technology
stack, and a skilled database administrator (DI3A)
can utilize the components of the Workflow stack
or third-party tools to provide data archival
capabilities if required.
NE-AU-2.3 The solution shall maintain an audit log of end-user COMPLY
activity information for technical troubleshooting and
problem identification purposes.

SERIAL 13139-RFP
NF-AU- The solution shall maintain an audit log for the following COMPLY
.2.4.1 events and activities but not limited to; Authentication
success or failure.
NF-AU-.2.4.2 The solution shall maintain an audit log for the following COMPLY
events and activities but not limited to: Authorization
success or failure,
NF-AU-.2.4.3 The solution shall maintain an audit log for the following COMPLY
events and activities but not limited to: Validation
success or failure.
NF-AU-.2.4.4 The solution shall maintain an audit log for the following COMPLY
events and activities but not limited to: Data
Transformation success or failure.
NF-AU-.2.4.5 The solution shall maintain an audit log for the following COMPLY
events and activities but not limited to: Mapping success
or failure.
NF-AU-.2.4.6 The solution shall maintain an audit log for the following COMPLY
events and activities but not limited to: Query/Look-up
success or failure.
NF-AU-.2.4.7 The solution shall maintain an audit log for the following COMPLY
events and activities but not limited to; Routing success
or failure.
NF-AU-.2.4.8 The solution shall maintain an audit log for the following COMPLY
events and activities but not limited to: Message out of
sequence error.
NF-AU-.2.4.9 The solution shall maintain an audit log for the following COMPLY
events and activities but not limited to: Database
connection success or failure,
NF-AU-.2.4.10 The solution shall maintain an audit log for the following COMPLY
events and activities but not limited to: Communication
failure, (e.g., database connectivity, web service
connectivity, FTP connectivity),
NF-AU-2.5 The solution shall record the following field and data COMPLY
attributes for an audit log event:
• Type of record (i.e. inmate person, case, booking, etc.)
• Date and Time
• Source system or user name
• Data Record Information including but not limited to:
record returned, records added, records updated, search
criteria, search results, and related unstructured data.
• Routing Indicator
• Machine IP Address
• Interface name
• Log Message
• Log level
NF-AU-2.6 The solution shall protect audit log information from COMPLY
unauthorized access.
NF-AU-2.7 The solution shall have the ability to backup the audit log COMPLY
for long term storage.

SERIAL 13139-RFP
NF-AU-2.8 The solution shall maintain an audit log record for the COMPLY
following data exchange activities to support the
accountability, reconstruction of events and problem
identification:
• Request received
• Request sent
• Request delivered
• Request not delivered
• Request pending for replay
• Request for replay failed
• Response received
• Response not received
• Response sent
• Response delivered
• Received acknowledgement
. Sent acknowledgement
NF-AU-2.9 The solution shall record the following attributes for each COMPLY
activity to provide the current status of a transaction:-
Type of record (i.e. inmate person, case, booking, etc.).
Date and Time. Source system or user name. Interface
name. Message identifier. Transaction identifier • Audit
message
NF-AU-2.10 The solution shall provide an audit alert to MCSO COMPLY WITH The Workflow application does not provide any
Security Officer when a suspected security breach occurs. CLARIFICATION security breach detection or notification
capabilities. Syscon recommends third party
monitoring tools for this purpose. During the
Technical Requirements Gap Analysis session we
discussed the difficulty of monitoring for security
breaches as most breaches that can be detected
programmatically should also be preventable
programmatically and hence the monitoring is
redundant. For adhoc monitoring the Workflow
audit trail can be queried for specific activities.
Availability, End User Availability (Planned Outage),
Failure Rate, Operational Continuity
NF-AV-3.0 The Jail Management system shall be available to users 7 COMPLY
days a week 24 hours a day.
NF-AV-3.1.1 The Contractor shall describe how it will achieve the COMPLY
Planned Outage % of Availability, Downtime per Year,
Downtime per Month and Downtime per week
requirements stated in the table above for the JMS
solution.
NF-AV-3.I.2 The Contractor shall describe how they Will achieve the COMPLY
Planned Outage % of Availability, Downtime per Year,
Downtime per Month and Downtime per week
requirements stated in the table above for the Third Party
components and Web Services included in the proposed
solution.
NF-AV-3.1,3 The Contractor shall describe how they will achieve the COMPLY
Planned Outage % of Availability, Downtime per Year,
Downtime per Month and Downtime per week
requirements stated in the table above for the Jail
Management Reporting Services included in the proposed
solution.
NF-AV-3.2.1 The Contractor shall describe how it will achieve the COMPLY
Unplanned Outage % of Availability, Downtime per Year,
Downtime per Month and Downtime per week
requirements stated in the table above for the JMS
solution.

SERIAL 13139-RFP
NF-AV-3.2.2 The Contractor shall describe how they will achieve the COMPLY
Unplanned Outage % of Availability, Downtime per Year,
Downtime per Month and Downtime per week
requirements stated in the table above for the Third Party
components and Web Services included in the proposed
solution,
NF-AV-3.2.3 The Contractor shall describe how they will achieve the COMPLY
Unplanned Outage % of Availability, Downtime per Year,
Downtime per Month and Downtime per week
requirements stated in the table above for the Jail
Management Reporting Services included in the proposed
solution.
NF-AV-3.3.1 The Contractor shall describe how it will achieve the COMPLY
Operational Continuity % of Availability, Downtime per
Year, Downtime per Month and Downtime per week
requirements stated in the table above for the JMS
solution.
NF-AV-3.3.2 The Contractor shalt describe how they will achieve the COMPLY
Operational Continuity % of Availability, Downtime per
Year, Downtime per Month and Downtime per week
requirements stated in the table above for the Third Party
components and Web Services included in the proposed
solution.
NF-AV-3.3.3 The Contractor shall describe how they will achieve the COMPLY
Operational Continuity % of Availability, Downtime per
Year, Downtime per Month and Downtime per week
requirements stated in the table above for the Jail
Management Reporting Services included in the proposed
solution.
NF-AV-3.3.4 The Contractor shall provide end users the ability to track COMPLY WITH The Workflow application uses database
solution uptime and transaction response times for both CLARIFICATION technologies (Oracle DB, Microsoft SQL) that
pre-formatted and ad-hoe queries, come with the ability to. track database uptirrte and
transaction response times for both pre-formatted
and ad-hoc queries.
Capacity Limits, Number Of Users, Concurrent Users,
Event Volumes, Prioritization Of System Functions
NF-CL-4. 1.1 The Contractor shall describe how the Jail Management COMPLY
solution will accommodate the forecasted number of users
in the table above while maintaining required operational
performance levels.
NF-CL-4.l.2 The Contractor shall describe how the Third Party . COMPLY
Components and Web Services solution will
accommodate the forecasted number of users in the table
above while maintaining required operational
performance levels.
NF-CL-4.1 .3 The Contractor shall describe how the Jail Management COMPLY
Reporting Service solution will accommodate the
forecasted number of users in the table above while
maintaining required operational performance levels.
NF-CL-4.1.4 The Contractor shall describe how the Jail Management COMPLY
Reporting Service solution will accommodate the number
of users exceeding those specified in the table above
while maintaining required operational performance
levels.
NF-CL-4.2.1 The Contractor shall describe how the Jail Management COMPLY
solution will accommodate the forecasted number of users
concurrently while maintaining required operational
performance levels.

SERIAL I3139-RFP
NF-CL-4.2.2 The Contractor shall describe how the Third Party COMPLY
Components and Web Services solution will
accommodate the forecasted number of users concurrently
while maintaining required operational performance
levels.
NF-CL-4.2.3 The Contractor shall describe how the Jail Management COMPLY
Reporting Service solution will accommodate the
forecasted number of concurrent users while maintaining
required operational performance levels.
NF-CL-4.2.4 The Contractor shall describe how the Jail Management COMPLY
Reporting Service solution will accommodate the number
of concurrent users exceeding the total number of users
today while maintaining required operational performance
levels.
NF-CL-4.3.1 The Contractor shall describe how the Jail Management COMPLY
solution will successfully accommodate the Booking
volumes specified in the table above.
NF-CL-4.3.2 The Contractor shall describe how the Jail Management COMPLY
solution will successfully accommodate the Daily
Population volumes specified in the table above.
NF-CL-4.3.3 The Contractor shall describe how the Jail Management COMPLY
solution will successfully accommodate the Inmate
Transportation volumes specified in the table above.
NF-CL-4.3.4 The Contractor shall describe haw the Jail Management COMPLY
solution will successfully accommodate the tamales
Released volumes specified in the table above.
NF-CL-4.3.5 The Contractor shall describe how the Jail Management COMPLY
solution will successfully accommodate the Population
High Count volumes specified in the table above.
NF-CL-4.3.6 The Contractor shall describe how the Jail Management COMPLY
solution will successfully accommodate the Average
Length of Stay volumes specified in the table above.
NF-CL-4.3.7 The Contractor shall describe how the Jail Management COMPLY
solution will successfully accommodate the Workload
volumes specified in the table above.
NF-CL-4.3.8 The Contractor shall describe how the Jail Management COMPLY
solution will successfully accommodate volumes
exceeding those specified in the table above, while
maintaining all required operational performance levels.
NF-CL-4.4.I The Contractor shall describe how the proposed solution COMPLY
allows the System Administrator to manage solution
process priorities including routine settings and how
exception priorities can be controlled and managed.

SERIAL 13139-REP
NF-CL-4.4.2 The Contractor shall provide system performance COMPLY WITH The live production Workflow environment will
measures that allow monitoring, by both MCSO and the CLARIFICATION not be monitored by Syscon as we see this as an
Contractor, of System capacity, performance, and usage. MCSO responsibility. During the Acceptance Test
period Syscon will assist MCSO with identifying
performance measures that allow monitoring.
During the Technical Requirements Gap Analysis
session MCSO mentioned that a Cloud based
monitoring tool would not be acceptable. There are
several on premise solutions available that should
meet MCSO's needs such as Dell Foglight or
Nastel.
NF-CL-44.3 The Contractor shall describe the scalability of the COMPLY
solution and the ability to accommodate growth.
Configuration Management
NF-CM-5.I The Contractor shall ensure that the solution as a whole COMPLY
continues to function reliably and remain secure when
individual components are changed.
NF-CM-5.2 The Contractor shall implement a change control process COMPLY
with approval stages required to change a configuration
item attributes.
NF-CM-53 The Contractor shall provide a running record of current COMPLY
module configurations and the history of changes in the
form of a report.
NF-CM-5A The Contractor shall maintain IvICSO system COMPLY
configurations as Contractor supplied updates are
provided and/or applied.
NF-CM-5.5 The Contractor shall conduct regression testing for COMPLY
existing MCSO system configurations as Contractor
supplied updates are made.
NF-CM-5.6 The Contractor shall follow Information Technology COMPLY
Infrastructure Library (ITIL) Change Management Best
Practices. This includes the following but is not limited
to: change management dashboard, request for change
(RFC), RFC screening, change management review,
minor change, change advisory board, CAB/EC approval
review, change approved, and regression testing, detailed
release notes.
NF-CM-5.7 The Contactor shall implement a change control process . COMPLY
with approval stages required to maintain at least three
separate distinct environments such as:
development/testing, training and production.
Performance, Total Response Time, Utilization
NF-PF-6.1.1 The Contractor shall describe how the proposed solution COMPLY The Workflow application will meet the
will meet the performance requirements specified above performance requirements specified in Table 23
for the Jail Management System and how performance Performance Response Time.
will be tested and validated during the implementation.
Response time includes, but is not limited to application
loading, screen open and refresh, functions, calculations,
imports, and exports.
NF-PF-6.1.1.1 The Contractor shall describe how the proposed solution COMPLY The Workflow application will meet the
will meet the performance requirements specified above performance requirements specified in Table 23
for the Jail Management System: Query by Name and/or Performance Response Time.
Booking Number and how performance will be tested and
validated during the implementation. Response time
includes, but is not limited to application loading, screen
open and refresh, functions.

SERIAL 13139-R1P
NF-PF-6.1.1.2 The Contractor shall describe how the proposed solution COMPLY The Workflow application will meet the
will meet the performance requirements specified above performance requirements specified in Table 23
for the Jail Management System: Inmate Record Update Performance Response Time.
and how performance will be tested and validated during
the implementation. Response time includes, but is not
limited to application loading, screen open and refresh,
functions.
NF-PF-6.1.1.3 The Contractor shall describe how the proposed solution COMPLY The Workflow application will meet the
will meet the performance requirements specified above performance requirements specified in Table 23
for the Jail Management System: Jail Operation Journal Performance Response Time.
Logging and how performance will be tested and
validated during the implementation. Response time
includes, but is not limited to application loading, screen
open and refresh, functions.
NF-PF-6.1 .1.4 The Contractor shall describe how the proposed solution COMPLY The Workflow application will meet the
will meet the performance requirements specified above performance requirements specified in Table 23
for the Jail Management System: Ad-hoc Query Performance Response Time.
Transactions and how performance will be tested and
validated during the implementation. Response time
includes, but is not limited to application loading, screen
open and refresh, functions.
NF-PF-6.1.2 The Contractor shall describe how the proposed solution COMPLY The Workflow application will meet the
will meet the performance requirements specified above performance requirements specified in Table 23
for the Third Party Components and Web Services and Performance Response Time.
how performance will be tested and validated during the
implementation.
NF-PF-6.1.3 The Contractor shall describe how the proposed solution COMPLY The Workflow application will meet the
will meet the performance requirements specified above performance requirements specified in Table 23
for the Jail Management Reporting Service and how Performance Response Time,
performance will be tested and validated during the
implementation. Query and Reporting times include, but
are not limited to initial and subsequent loads.
Utilization
NF-UT-6.2.1 The Contractor shall describe how they will monitor and COMPLY WITH The live production Workflow environment will
tune the solution in order to maintain optimal CLARIFICATION not be monitored by Syscon as we see this as an
performance through a 24 hour period. MCSO responsibility. Performance will be
assessed during the Acceptance Test period and
required performance tuning will be completed.
During the Technical Requirements Gap Analysis
session MCSO mentioned that a Cloud based
monitoring tool would not be acceptable. There are
several on premise solutions available that should
meet MCSO's needs such as Dell Foglight or
Nastel.
Security
' NF-SE-7.1.1 The solution shall provide the ability to comply with COMPLY WITH The Workflow application is currently only
ACJIS and CJIS policies requiring two factor CLARIFICATION designed to authenticate based on username and
authentications, password, however, two factor authentication will
be delivered as a roadmap item.This requirement
was identified as being not high priority for phase
1 go-live, and is therefore tentatively scheduled for
Workflow release 4.5 — Project Release 2.2
NF-SE-7.1.2 The solution shall provide the ability to comply with COMPLY
MCSO policies requiring a secure authentication and
strong passwords.

SERIAL 13139-RFP
NF-SE-7.1.3 The solution shall block a user for access after 3 COMPLY
unsuccessful attempts. Requiring a system administrator
to reset the user's account.
NE-SE-7.1,4 The solution shall uniquely identify and authenticate each COMPLY
user by password.
NF-SF-7.1.5 The solution shall provide the ability for a system EXCEPTION The Workflow application provides the ability to
administrator to define a user session time out based on set one session time out for all users,
security group and role,
There is no ability to set a user session timeout
based on role.
NF-SE-7.1.6 The solution shall provide the ability to define password COMPLY WITH The Workflow application provides the ability to
security requirements by module, security group and role. CLARIFICATION define a password policy for all users and role-
based access control for user groups. There is no
ability to define the password security for a
specific module or group of users.
During the Technical Requirements Gap Analysis
session MCSO stated that the Pre-book users are
the main user group that needs to be handled
differently. A gap has been identified to address
Pre-book. Refer to functional requirement F-IN-2.
Further analysis is required to understand the Pre-
book security requirements.
NF-SE-7.2.1 The solution shall provide the ability to comply with COMPLY Workflow is designed based on 30 years of
ACJIS and CJIS policies for end user agency industry experience and is expected to comply
authorization. with ACJIS and CJIS policies for end user agency
authorization
NF-SE-7,2.2 The solution shall provide the ability to comply with COMPLY WITH The Workflow application is currently only
MCSO policies end user authorization including but not CLARIFICATION designed to authorize based on user, role and
limited to the following: group, location, role, TOC, TCP facility. However, device-based authorization will
IF, Routing Indicator, etc. See MCSO End User Security be delivered as a roadmap item. This item is
Responsibilities, tentatively scheduled for Workflow release 3.5 —
Project Release 1.3
NF-SE-7.2.3 The solution shall provide the ability to comply with COMPLY Workflow is designed based on 30 years of
ACES and CMS policies for external agency interface industry experience and is expected to comply
authorization. with ACES and CJIS policies for external agency
interface authorization.
NF-SE-7.2.4 The solution shall capture all elements required for the COMPLY Workflow is designed based on 30 years of
Access Request and Authorization. See Forms Library: industry experience and is expected to be able to
Access Request & Authorization. capture all elements required for the Access
Request and Authorization.
NF-SE-7.3.1 The solution shall provide a mechanism to authenticate COMPLY
users or systems involved in a data exchange.
NF-SE-7.3.2 The solution shall provide a mechanism that encrypts and COMPLY
decrypts data of all incoming/outgoing messages using at
least 256 Bit Encryption level. All hardware utilized by
the solution shall support this encryption.
NF-SE-7.3.3 The solution shall provide a mechanism that encrypts and COMPLY
decrypts according to NLST and FIPS Justice Standards.
' NF-SE-7.3.4 The solution shall provide the Dynamic Data COMPLY
Classification to filter sensitive fields from being sent to
the justice partners that are not entitled to receive the data.

SERIAL 13139-RFP
NF-SE-7.3.5 The solution shall meet or exceed minimum Security COMPLY
standards detailed in MCSO's Information Security
Policy including but not limited to login requirements,
password requirements, inactivity timeouts, and user
revocation.
NF-SE-7.4.1 The solution shall produce immediate security alert COMPLY WITH The Workflow application does not provide any
notifications upon detection of a security policy violation. CLARIFICATION security policy violation detection or notification
capabilities. Syscon recommends third party
monitoring tools for this purpose. During the
Technical Requirements Gap Analysis session we
discussed the difficulty of monitoring for security
policy violations as most policy violations that can
be detected programmatically should also be
preventable programmatically and hence the
monitoring is redundant. For adhoc monitoring the
Workflow audit trail can be queried for specific
activities.
NF-SE-7.4,2 The solution shall have the ability to produce a report COMPLY Workflow provides for this feature as part of its
documenting all security related items in the system per shift log and case note functionality.
shift, per day, and per month.
NF-SE-7.4.3 The Contractor shalt document all security alerts and COMPLY WITH The security reporting requirements will be
security reports and ensure that they fulfill MCSO CLARIFICATION reviewed during the Define phase of the project.
Security Policy standards. Syscon recommends third party monitoring tools
for this purpose. Any reports or alerts delivered by
Syscon will be properly documented,
NF-SE-7.4.4 The solution shall allow MCSO to configure the COMPLY WITH Syscon recommends third party monitoring tools
distribution of the security alert notifications. CLARIFICATION for this purpose.
Supportability
NF-SI.3-81 Configurability COMPLY
The solution shall provide an administrative user the
ability to configure the system with minimal Contractor
services support after initial training and knowledge
transfer has been completed. Configuration shall include
but not limited to such operations as: GUI formatting,
drop down value lists, data exchanges, user
administration, reports, system backups.
NF-SU-8.2 Testability COMPLY The Workflow application is regression test and
The solution shall provide certified test tools and scripts verified prior to delivery to the client using third
to verify solution stability and functionality, party tools and quality assurance best practices.
The solution shall be regression tested with tools and Syscon does not bundle the tools with the
scripts to verify solution stability and functionality prior Workflow application.
to code delivery to customer.
NF-SU-8.3 Upgradeability COMPLY
The solution shall be able to receive third party Contractor
updates without modifying the Contractor application's
configuration. (For Example Windows Updates,
Database Contractor Updates, etc.)
NF-SU-8.4 Platform Escrow COMPLY
The Contractor shall be willing to put the delivered
application version source code, third party
binaries/libraries, current build procedures, and
development and release management virtual machine
images into escrow. This shall provide risk mitigation in
case the Contractor goes out of business, ensuring that
MCSO has to access the source code and all supporting
objects to maintain the solution.

SERIAL 13139-RFP
NF-SU-8.5 Provide Installation Procedures COMPLY
The Contractor shall provide application installation
procedures for their solution and related components.
NF-SU-8.6 Concurrency COMPLY
The application shall ensure data integrity and quality
control through concurrency mechanisms such as
pessimistic or optimistic data locking.
NF-SU-8.7 Thin Client COMPLY
The solution shall provide a thin browser based
application.
The solution shall provide a mobile based application.
NF-SU-8.8 Maintainability COMPLY
The Contractor shall describe the architectural, design and
coding standards employed and what exclusions have
been created in the development of the solution.
Usability Requirements, User Interaction, User
Navigation
NF-U-91 .l The solution shall provide both online and electronic COMPLY
versions of training material, and have a learning curve
less than three days.
NF-U-9. I 2 The Contractor shall provide both online and electronic COMPLY
versions of their user manuals to provide new users and
trainees with the initial information they need to use the
solution.
NF-U-9.1.3 The Contractor shall provide updates to the user manuals COMPLY
for new users and trainees with the initial information
they need to use the solution.
NF-U-9.1.4 The Contractor shalt provide on-site "train the trainer" COMPLY WITH IVICSO has as many as 170 individuals on staff
training at a sufficient level to prepare MCSO trainers to CLARIFICATION between Subject Matter Experts, Field Training
conduct end user training. MCSO trainers shall pass a Officers, and Civilian Trainers who will require
Contractor proficiency exam from the on-site "train the Train-the-Trainer level training as part of the
trainer" prior to being certified as a trainer. project. In Syscon's original response, the number
of T3 trainers that were contemplated was less
than 24 individuals, with an assumption that one
full course of 13 training would be necessary, with
all trainers attending the same classes. As a result,
more training classes will need to be planned,
which will have an impact on the costs associated
with training services and related expenses.
NF-U-9.1.5 The Contractor shall provide on-site or web based training COMPLY
for future versions of solution.
NF-U-9.1.6 The Contractor shall describe the ongoing training COMPLY
programs available for the proposed solution and related
components.
NF-U-9.1.7 The solution shall provide novice users the ability to COMPLY
perform complex tasks such as booking an inmate within
15 minutes.
NF-U-9.1.8 The solution shall provide novice users the ability to COMPLY
perform tasks such as a booking search within 2 minutes,
NFU-9.1.9 The solution shall provide experienced users the ability to COMPLY
perform tasks such as inmate court scheduling within 2
minutes.

SERIAL 13139-RFP
NF-U-9 2.1 The solution shall have a common vernacular, consistent COMPLY
graphical user interface, and good workflow. The
Contractor shall describe the proposed solution with
regard to user navigation.
, NF-U-9.2.2 The user will need to be able to point, click, or touch a COMPLY
point on the Jail Management System screen, and data
associated with the inmate will need to be displayed.
NF-U-9.2.3 It is important for the user to be able to access the various COMPLY
information they require in a quick, consistent and
intuitive way. For instance drop down lists and predictive
text need to be available to identify data types.
NF-U-9.2.4 The solution shall provide the user the ability to get key COMPLY
information within three clicks from any screen.
NF-U-9.2.5 The solution shall provide the user the ability to navigate COMPLY
and perform all system function with only a keyboard
shortcuts and function keys.
NF-U-9.2.6 It is desirable that the solution shall meet 100% of the COMPLY WITH The Workflow application is rendered using a
compliance requirements stated in Section 508 of the CLARIFICATION standard interne browser,
Americans with Disabilities Act of 1990.
In order to meet section 508 compliance third-
party tools can be employed to provide the user
experience needed for someone who requires
assistive technologies.
The browser natively supports keyboard
navigation to "Tab" from one element (field,
button, etc.) to another within the browsers
rendered content.
Other assistive technology is available via third
party tools such as:
• Jaws Screen Reader
• Colorblind Assistant
• Window-Eyes
Data Requirements, Logical Data Groupings, Data
Retention, Data Structures And Relationships, Data
Conversion, Data Dictionary
NF-DR-10.1.1 The solution shall process and store IvICSO Internal COMPLY
Information data elements in logical data groupings
including but not limited to Inmate Support Services data,
Inmate data, Visitor data, Fiscal data, Operations data,
Administrative data, and Inmate Tracking data.
NF-DR-10,1.2 The solution shall process and store Core Shared COMPLY
Information data elements in logical data groupings
including but not limited to Court Information data,
Medical Information data, Booking Information data,
Person Information data, Person History data, Custody
Information data, and Release Information data.
NF-DR-10.1.3 The solution shall facilitate data exchange of MCSO COMPLY
Internal data and Core Shared data.
NF-DR-10.1.4 The Contractor shall describe how the solution will COMPLY Workflow is designed based on 30 years of
support the MCSO Information Model presented in the industry experience and is expected to comply
Conceptual Design. with the MCSO information model
—NF-DR-10.2.1 The solution shall maintain data in a format that is COMPLY Workflow is designed based on 30 years of
acceptable by legal entities such as CJIS, ACJIS, MCSO, industry experience and no problems are
and County of Maricopa. anticipated with the data format of other legal
entities.

SERIAL 13139--RFP
NF-DR-l0.2.2 The solution shall provide the ability for an administrative COMPLY WITH Workflow does not provide for a client to change
user to manage the logical data groupings and define CLARIFICATION the data model for any of its logical groupings.
when they are active and available for a determined Workflow does support a feature called "Client
period of time based on business rules. Custom Fields" that allow a client to add new
fields to a logical grouping of data already part of
the Workflow model. This feature allows for the
fields to be expired but that expiration is not based
on a business rules engine.
NF-DR-10.2.3 The solution shall provide the ability for an administrative COMPLY WITH Workflow does not provide the ability to define
user to manage the logical data groupings to be in archival E CLARIFICATION the data archival storage based on business rules
storage for a determined period of time based on business however the underlying database technologies
rules. support these requirements.
NF-DR-10.2.4 The solution shall provide the ability for an administrative EXCEPTION Workflow does not provide the ability to manage
user to manage the logical data groupings to be in purging and sealing based on business rules.
purged/sealed storage for a determined period of time
based on business rules.
NF-DR-10.2.5 The solution shall provide the ability for an administrative COMPLY WITH Data is always live there is no archived data so it is
user to retrieve archived records at will, over a period of CLARIFICATION always retrievable.
time as per legal requirements. A change in database
structure or database Contractor during that period shall
not affect data retrieval.
NF-DR-102.6 The solution shall provide the ability for the archived COMPLY WITH Data is always live there is no archived data so it is
information to be viewable through the current CLARIFICATION always viewable
application.
NF-DR-10.2.7 As per the prioritization of solution tasks requirement, the COMPLY WITH Data is always live there is no archived process.
archiving process needs to have a lower priority to ensure CLARIFICATION
that it does not affect system performance during peak
periods.
NF-DR-10.2.8 The solution shall provide the 256 bit encryption level of COMPLY
data in transit.
Mt-DR-10.2.9 The solution shall provide the 256 bit encryption level of COMPLY
data at rest in the database.
NF-DR-10.2.10 The solution shall provide the 256 bit encryption level of COMPLY
data in use by the application.
NF-DR-I 0.2.11 The solution shall provide the 256 bit encryption level of COMPLY
data at rest in a backup before writing out to tape.
NF-DR-10.3. I The solution shall identify the main data inputs and COMPLY
outputs of the proposed JivIS solution in both diagram and
narrative format. The main data inputs and outputs
include but are not limited to the following: conceptual
design, interface documentation and user interactions.
NF-DR-10.3.2 The solution shall identify where the data is stored and COMPLY
inter-functional flows associated with the solution.
NF-DR-l0.3.3 The solution shall provide logical entity relationship COMPLY
diagram for the proposed Jail Management System.
NF-DR-10.4.1 The solution shall utilize the existing MS system data COMPLY
contained in automated files to populate the new solution
databases. See Legacy System and Data Overview.
NF-DR-10.4.2 The solution shall utilize the existing OJ system data COMPLY
contained in automated files to be used to build the new
solution databases. See Legacy System and Data
Overview.

SERIAL I3139-RFP
NP-DR-10.4.3 The solution shall utilize the existing IFCS system data COMPLY
contained in automated files to populate build the new
solution databases. See Legacy System and Data
Overview.
NF-DR-10.4.4 The solution shall utilize the existing Pm-Booking system COMPLY
data contained in automated files to populate the new
solution databases. See Legacy System and Data
Overview.
NF-DR-10.4.5 The solution shall utilize the existing Court Operations COMPLY
Transport system data contained in automated files to
populate the new solution databases. See Legacy System
and Data Overview,
NF-DR-10.4.6 The solution may utilize the existing SAP Business One COMPLY
system data contained in automated files to populate the
new solution databases. See Legacy System and Data
Overview.
NF-DR-10.4.7 The solution shall convert essential data identified by COMPLY
MCSO. Essential data elements required for the execution
of the new JMS which is missing or not available in
current MCSO databases will be recorded manually or
defaulted to MCSO agreed to values.
NF-DR-10.4.8 The solution shall identify and prevent duplicates from COMPLY
the source data and prevent from occurring in the new
solution databases.
NF-DR- l 0.4.9 The solution shall ensure the record integrity of the COMPLY
current system data will be protected and validated
throughout conversion so that it will be reliable for inmate
processing after the conversion.
NF-DR-10.4.10 The solution shall provide the audit system history loaded COMPLY
into a relational database format and made available for
inquiry in new screens that will be included or added to
Solution.
NF-DR-10.4.11 The Solution shall include a process to identify, research, COMPLY
track and remove duplicates/potential duplicate data
identified by matching key identifiers extracted from the
external system.
NF-DR-10.4.12 The solution shall use automated EfL tools to perform COMPLY
data conversion tasks.
NF-DR-10.4.13 The Contractor shall perform data conversion to the point COMPLY
where there is a predictable, successful outcome for each
legacy system in sufficient time to validate, prior to
system cut-over for go-live.
NF-DR-10.5.1 The Contractor shall provide a searchable, comprehensive = COMPLY
data dictionary covering all data elements in the entire
database.
NF-DR-10.5.2 The data dictionary shall include a listing of all fields by COMPLY
table, and a summary field list by table, including both
tong and short field descriptions.
NF-DR-10.5.3 The Contractor shall update the data dictionary as changes COMPLY
occur (including changes in data sources and/or within the
database) (e.g., new codes, new data elements, changes to
reference files, etc,),

SERIAL 13I39-RFP
NF-DP.-I0.5.4 The Contractor shall accommodate routine changes, COMPLY
refinements, and additions to the data without causing any
degradation in the performance and/or functionality of the
system.
Design Constraints
NF-DC-11.1 The solution shall use the National Information Exchange COMPLY
Model (NIEM) format for communication between
systems.
NF-DC-11.2 The solution shall enable loose coupling of business COMPLY
services by designing data exchanges that are:
• Are independent of the state or condition of systems.
• Are independent of the underlying implementation of
endpoints,
NE-DC-11.3 The solution shall enable authorized users to work off-line EXCEPTION Workflow does not provide the ability to enter data
and upload data entered and transactions performed later, offline and upload it into the application. During
the Technical Requirements Gap Analysis session
MCSO stated that with the exception of Pre-book,
this functionality is not required until after the
project is complete. Syscon will work
collaboratively with MCSO to define the specific
requirements for Pre-book.
NE-DC-11.4 The solution shall be implemented using a database that COMPLY
will run on the existing either (IBM AIX or Microsoft)
operating system architecture,
NF-DC-11.5 The solution shall be implemented on either (IBM AIX) COMPLY
Unix or Microsoft Windows Server operating system,
NE-DC-11,6 The solution may utilize the existing VMware COMPLY
infrastructure within the Sheriff's Office or the Contractor
shall propose an alternative.
NF-DC-I 1.7 The solution shall utilize the existing ICJ1S Integration COMPLY
Engine (HE) infrastructure within the Marieopa County
for all external system interfaces and messaging.
NE-DC-11.8 The solution shall provide the ability to send and receive COMPLY
messages using the existing ACES and CBS protocol
standards and equipment interfaces.
. NE-DC-11,9 The solution may specify the hardware refresh cycle COMPLY WITH
required to maintain performance per hardware type. CLARIFICATION
• NE-DC-11.10 The solution shall be implemented using at least, but not COMPLY
limited to, three (3) separate environments for
development/testing, training and production.

SERIAL 13139-RFP
NF-DC-11.11 The Contractor shall use professionally and technically COMPLY
sound standards, techniques, and tools including, but not
limited to: t Standards and techniques for controlling data
synonyms, aliases, and versions.- Standards for data
characteristics.. Data element design standards and data
element domain standards for logical and physical data
design, and standards for data management.- Data design
standards to ensure modularity, extensibility, and
flexibility, and to ensure the efficient and consistent use of
the data by the information system.. Standards for
effective data searching and cross-referencing
techniques,* Standards to control data redundancy..
Standards for data views, including internal, conceptual,
and external views.. Standards for data administration and
database administration.. Metrics, tests-of-correctness,
and objective measurements of data quality.. Quality
assurance inspection checkpoints within the system
development life cycle.. Formal software testing
methodology.
Support And Maintenance
NF-SM-12.1 Support Services Available and Included COMPLY WITH Reliability Test Period: After successful
With purchase of the baseline solution, the Contractor CLARIFICATION completion of the go-live cutover period, there will
shall provide support services and maintenance updates. be a thirty (30) day reliability test period during
Warranty shall begin after unit and user acceptance testing which the newly installed system will be in
have passed mutually agreed upon acceptance thresholds production and its performance monitored. Once
(including 30 days with no rebooting of the solution). See the system is declared live and end users begin
RFP Section 3.3 and 3.4 for additional Acceptance and use, the thirty (30) day reliability test period will
Warranty provisions, commence During this period, the system must
perform without any severity 1 or severity 2
defects being reported. Provided the deliverables
have not materially changed, reliability testing will
resume promptly following delivery and continue
only for the period of time remaining in the initial
30 day reliability test period; with a five (5) day
minimum to apply.
NF-SM-12.2 Warranties, Guarantees, Provisions for Buy-Outs COMPLY
The Contractor shall provide a solution warranty and
guarantee of continued solution support or other
acceptable provisions defined by the contract or in-case of
the potential buy-out of the Contractor.
NF-SM-12.3 The Contractor shall describe their support and COMPLY
maintenance program and include service desk reporting
capability, typical response times and overall support
management process.
NF-SM-12.4 Product Lifecycle ManagementThe Contractor shall COMPLY
employ industry standard solution lifecyde management
methods and procedures to ensure a quality and timely
deliverable. The Contractor shall describe how they will
support:• Planning and Organization Management
Control. Acquisition and Implementation Management
Control. Delivery and Support Management and Control.
Monitoring Management ControlReference documents:
Business Analysis Body of Knowledge* (BABOKt
Guide), Project Management Body of Knowledge
(PMBOK Guide), Information Technology Infrastructure
Library ono.
14F-SNI-12.5 Brealcifix, Patch Notification, and Issue Resolution COMPLY
The Contractor shall have a method for communicating
bre,aldfix, patch release, or issue resolution to MCSO
technology support team at MCSO. This shall include
communications such as e-mail notification, newsgroup,
blogs, standard mail, or telephone,

SERIAL 13139-RFP
NF-SM-12.6 Backup and Recovery COMPLY
The Contractor shall architect the backup and recovery
based upon continuous data protection, full system
backups, and incremental backups.
NF-SM-12.7 Backup and Recovery COMPLY Syscon performs backup and recovery test as part
The Contractor shall test the backup and recovery of development however Syscon does not perform
processes for the entire Jail Management System this at the client site or for a specific client.
annually.
NF-SM-12.8 Database Tuning and System Optimization COMPLY
The Contractor shall perform database tuning and system
optimization based on availability performance
requirements.
NF-SM-12.9 Help Desk Availability Window COMPLY WITH Syscon provides 7 1'24 live answer support and
The Contractor shall offer a 24 hour x 7 days per week - CLARIFICATION dispatch for all PI incidents. Case logging is
help desk window for addressing ,IMS related questions available 7 4'24 via the web portal. P2-P4 incident
and issues. The Contractor shaft describe how they will: are supported during business hours M-F 0600-
• Track calls 1800 PST
• Report resolutions
• Report against all agreed upon SLA's
NF-SM-I2,10 User Groups and Product Enhancement Forums COMPLY
The Contractor may offer user group meetings or solution
enhancement forums enabling the MCSO to share
experiences with the Contractor's customer base.
NF-SM-12.11 The Contractor shall conduct user training for COMPLY WITH Syscon will provide Technical training and Train
functionality upgrades/enhancements whenever CLARIFICATION the Trainer training for all updates provided within
applicable. This training will be conducted within a the Warranty Period. We will also provide all
window of sixty (60) State business days which extends training materials required to support the T3
from 30 business days prior to 30 business days following program,
installation eta upgrade Or enhancement.
NF-SM-I 2.12 The Contractor shall resolve all software support requests EXCEPTION Please refer to section 1.2 of Exhibit E Client
as follows:PriorityLevel Nature of Customer Software Support Agreement for a complete description of
Issue Initial ResponseTime UpdateInterval Resolution the Case resolution matrixTriorityLevel Nature of
TimeCritical Production system down or critical Customer Software Issue Initial ResponseTime
component of solution not working 30 Minutes Once Per UpdateInterval Resolution TimeP1-30 Mins- Once
Hour 4 HoursHigh System is up but functionality is lost. 1 Per 2 Hr-24 HrsP2-2 Hr- 120 Bra.- 8 Hrs.P3-4 firs-
Hour Every 2 Hours 8 Hoursrvfedium User and 30 Days-Weekly P4-8 Hs-within 2 releases - via
configuration issues/ questions. 4 Hours 1 BusinessDays 5 web portal
Business DaysLow Trouble calls that have no foss of
functionality 8 Hours 5 BusinessDays 10 Business Days
NF-SM-12.13 The Contractor shall resolve all hardware support requests EXCEPTION Although Syscon has provided hardware
as follows: recommendations it is our expectations that
Maricopa will use existing channels to procure the
Priority hardware and that all hardware support will come
Level Nature of Customer Hardware Issue Initial directly from the hardware vendor.
Response
Time Update
Interval Resolution Time
Critical Production system down or critical component of
solution not working 30 Minutes Once Per Hour 4 Hours
High System is up but functionality is lost. I Hour Every
2 Hours 8 Hours
Medium User and configuration issues/ questions. 4
Hours 1 Business
Days 5 Business Days
Low Trouble calls that have no loss of functionality 8
Hours 5 Business
Days 10 Business Days
NF-SM-12.14 The Contractor shall track and report the status of help COMPLY
desk requests to designated MCSO staff.

SERIAL 13139-REP
NF-SM-12.15 The Contractor shall provide end users the ability to COMPLY
submit on-line questions and problem tickets, and to track
the resolution status on-line.
Implementation
NF-I-13.1 Installation Services Available and Included COMPLY
The Contractor shall provide configuration and
installation services included in the purchase of the
baseline solution and selected optional modules.
NF-I-13,2 Solution Environment Services Available and Included COMPLY
The Contractor shalt provide configuration and
installation services for at least, but not limited to, three
separate environments for development/testing, training
and production.
NF-I-13.3 Quality Assurance and Control and System Start-up COMPLY
Testing
The Contractor shall provide quality control and quality
assurance services included in the purchase of the baseline
solution and selected optional modules. This shall include
services but not limited to: unit tests, integration tests, and
system tests, and participation in acceptance testing.
NF-I-13.4 User Training and Technical Knowledge Transfer (Train COMPLY
the trainer)
The Contractor shall provide user, administrative, and IT
support training services included with the purchase of the
solution and selected optional modules.
NF-I43.5 Implementation TimelineThe Contractor shall have a COMPLY
track record of successfully implementing their solution
verifiable by supplied client references.
NF-I-13.6 The Contractor shall provide MCSO with detailed, COMPLY
comprehensive updates, as needed, to any existing
documentation provided to the Contractor by MCSO.
NF-I- 13.7 The Contractor shall describe their process to turnover the COMPLY
solution to MCSO at the end of the contract or upon
termination of the contract.
81-

SERIAL 13139-REP
10.3. Future Work
Optional work estimates for functionality (as identified in Exhibit A) will be handled on a 1-by-I basis. For each
component, there will be agreement on how the effort will move forward, following generally recognized software
development methodologies (waterfall method). MCSO will have approval of each step of development process
(Analysis and Development/Implementation), Syscon (or sub-contractor) will provide an estimate of hours for each step
and will only proceed upon approval. MCSO will reserve the right to cancel each process (discretely) and will only pay
for the approved work done to that point. MCSO will also have the right to amend the scope of each phase of effort
prior to the approval of the final design and development work.
10.4. Future Support
10.4.1. Release Management
Syscon's Release Management Policy defines standards & rules for managing releases (such as numbering and
frequency) and instructions for deploying releases in order to comply with the Policy.
Release management involves contributions from many departments across the company. The Syscon Product
Management team, in liaison with Configuration Management, agrees to the exact content and rollout plan for
each release. Implementation Services provides design, development and testing resources to deliver system
modifications. Each new release is implemented into operational environments using the controlling processes
of Configuration Management. Project Management helps to communicate and manage expectations of our
clients during the planning and rollout of new releases.
The current policy will govern WorkflowJAIL (hereinafter referred to as Workflow), The Policy defines two
categories of Syscon product releases, both of which follow a regular schedule for planning and
implementation:
• Major releases add new features and content to the application. These are planned to occur annually,
typically in the autumn. The content of major releases is controlled by the Product Roadmap, which
is the prioritized list of commitments & objectives for the Workflow product. Each proposed product
modification goes through a qualification process of client consultation, market research and impact
analysis before being committed for an upcoming target release. Depending on the number of new
features under consideration, an additional sub-major release may be planned to make this content
available to our client base.
• Maintenance releases do not add new features or content, but are typically intended to solve minor
problems encountered via product support. In most years we plan for a minimum of two (2) and a
maximum of four (4) maintenance releases.
Syscon will not plan maintenance releases in isolation from major releases, as it is not uncommon for
new functionality in a major release to make intervening fixes to problems redundant.
On occasion, we will release hot-fix updates strictly for the resolution of incidents reported through
the I Ielpd esk.
Planning of product releases under this Policy typically includes stages for each of the following:
• Product Change Requests: Processed by the Syscon product management team, with each accepted
modification targeted for a specific upcoming release (to control the distribution and frequency of
system change).
• Rollout planning: Syscon follows an internal project plan to complete each release and "put it on the
shelf'. To distribute the release, we develop subsequent plans with each of our clients that take into
account client priorities, availability & business deliverables.
• Release design, build and configuration: Each system modification follows our standard
development methodology with consolidation of the modifications committed for each release.

SERIAL I3139-RFP
• Release acceptance: Testing the components of each release to pre-defined acceptance criteria, in a
controlled test environment.
• Impact Assessment: Communication planning, preparation and related training.
• Product Release and Installation: Syscon will provide troubleshooting support for product release
installations.
The Syscon Configuration Management Team, together with our Support Team will message clients in
advance of the release of the update to advise the following:
• planned release date;
• scope of the release;
• any additional information that may be pertinent to environmental or other requirements of the
change.
The Support Team provides the Installation Package for deployment into the client test environment once the
release has been classified as GA (General Availability). It is highly recommended that a full back-up is
completed at both the database and application server level prior to installation of a release. After the update is
applied, this back-up could be used to roll-back to the previous version if ever required.
Once the update has been verified in the test environment, MCSO will schedule a production rollout to deploy
the update into the training and production environment.
Syscon strongly recommends that the updates are reviewed, tested and applied within six months of each
release. Syscon will support up to three major releases of the product under the standard support and
maintenance agreement (e.g. the current release plus the previous two major releases). Syscon will not be
responsible for the applications' performance to required specifications if a client is not on a currently
supported product release unless extended support is purchased.
Our support policy for older products is based on the underlying technology being supported. As a company,
we will continue to maintain and support all versions of our application as long as the Support and
Maintenance Agreement (or Extended Support Agreement) is in place. If a third party vendor makes a
substantial technology or environment change, or stops supporting some legacy environment, Syscon will
provide an update path for MCSO (e.g. server operating system, workstation operating system change).
While we will provide Training documents with our updates, it will be the responsibility of MCSO to rollout
any User Training to the staff that are using the solution. All the product code releases detailed in this section
are provided free of charge to MCSO whilst support and maintenance payments remain up to date. Post the
Warranty Period, if MCSO require assistance from the Syseon Professional Services team during the
implementation of a release, this effort will be provided on either a time and materials basis or on a fixed-price
basis.
Currently, the Syseon maintenance program provides unlimited phone, email and remote support for the JMS.
Updates are provided together with the full documentation package as a part of the offering. There are not
currently any further offerings for enhanced levels of maintenance support in place.
10.4.2. Legislative Change
Where legislative change cannot be accommodated through configuration, the Syscon Professional Services
organization is available to support future development as required. If the change was unique to the MCSO
solution, there would be a charge. Once the scope of the change is determined, Syscon will create a Change
Request (CR) which would get reviewed and costed. Our Change Request process has dedicated Project
Managers who will drive the change through the system to ensure a timely response.
Agreed product enhancements arising out of client projects are handled by Syseon product management in the
same way as internal feature specifications in the product roadmap. Out of recognition that there is no better
validation of required product functionality than an actual operational need at a client agency, the philosophy

SERIAL 13139-RFP
of Syscon product management is to make every effort to designate client enhancements as product as opposed
to custom, through study of the market and business case for reusability. In support of this goal, product
requirements for supplemental features and conflgurability may be incorporated in the specification.
Enhancements fallowing this approach will be fully supported under standard product support and maintenance
agreements. Enhancements are planned and scheduled for Workflow development teams following a cycle of
estimation in collaboration with MCSO project management.
While we anticipate that most client enhancements can be certified as product under the above approach, it
remains possible that certain client enhancements may not meet this threshold and will be classified as custom.
Custom modifications will reside in the Workflow product code stream but subject to conditions which fall
outside the standard Support and Maintenance agreement. Future support of a CR feature is driven by the
product/custom designation, as it governs how modifications to Workflow licensed software are
accommodated in upgrades and patches (see also Section 6, Question l). Product modifications will be
covered under standard support and maintenance agreements, under which Syscon commits to regression
testing of all product features for each major release and maintains backward-compatibility for the previous
two major releases. Custom modifications are not covered under standard support and maintenance
agreements, and carry an additional cost to maintain, which can be expressed as an annual fee to cover
integration testing against new product versions and upgrades, or time-and-materials cost for integration testing
and modification for each subsequent upgrade.
10.4.3. Maintenance Program
Syscon's Maintenance Program includes free provision of all Code Release Packages, whether major
functional release or a regular maintenance release. These Code Release Packages include the code and the
following documentation:
• summary of the changes,
• complete Release Notes including installation (and roll-back) instructions
• Training Documents (as required)
Our Support Team Project Manager is responsible for the overall project management of the application
release cycle. This Project Manager will initiate communication with our client base in advance of every
release and advise on the:
• planned release date
• scope of the release
• additional information that may be pertinent to environmental or other requirements of the change
Syscon can provide Project Management, Testing, Training and Technical Support services for a fixed price.
If required, our Project Manager will scope the services and supply a quote for such services. However, we
believe that at the end of the implementation project, MCSO staff should be capable of being self-sufficient at
deploying patches or major/maintenance releases.
10.44. Upgrade Management
Post the Warranty Period, the code for any upgrades will be included as part of the annual maintenance fee.
Syscon professional services are not included post the Warranty Period.
All software that is provided as part of an upgrade will have been through rigorous internal testing by the
Syscon product group including the execution of our suite of automated test cases to ensure that the upgrade
does not break any code or functionality that was previously functioning. Once the upgrade, together with
supporting materials such as release notes and training material, has been signed-off by the Syscon Quality
Assurance Manager, the upgrade release package is provided to the Support Project Manager who will supply
the upgrade release to the MCSO technical team. Syscon will provide your Technical Team with all of the key
documents necessary to assess the impact of the upgrade.

SERIAL 13139-RFP
If MCSO require the support of Syscon professional services resources to support the upgrade, these will be
provided on a fixed-price basis or on a time and materials basis. The price will vary depending on the scope of
the Upgrade and the services required. However, Syscon has made the assumption that the MCSO technical
team will have been suitably trained during the implementation process that they will be capable of installing
the upgrade in any required MCSO environments (e.g. Test, Training and Production) with limited remote
support from Syscon staff; are capable of the required testing; and will use the provided training materials to
complete your end-user training as required.
10.43. Software Warranty
After successful completion of the go-live cutover period, there will be a thirty (30) day Reliability Test Period
during which the newly installed system will be in production, being used by end users, and performance being
monitored. After the Reliability Period has passed, the Warranty Period will begin for a period of forty-five
(45) days at which time a Gate Review will be held by all parties, and depending on the status of the
outstanding issues, an additional Warranty Period of forty-five (45) days may be added.
At the end of the Warranty Period, the project will move to Transition Stage where it will transition from the
Project Team to the Support Team.
10.4.6. Other Maintenance and Support
After successful completion of the go-live eutover period, there will be a thirty (30) day Reliability Test Period
during which the newly installed system will be in production, being used by end users, and performance being
monitored. After the Reliability Period has passed, the Warranty Period will begin for a period of forty-five
(45) days at which time a Gate Review will be held by all parties, and depending on the status of the
outstanding issues, an additional Warranty Period of forty-five (45) days may be added.
At the end of the Warranty Period, the project will move to Transition Stage where it will transition from the
Project Team to the Support Team.
10.5. Implementation and Management Approach
103.1. Implementation and Management Approach
The Syscon implementation model for its Workflow.IAIL product (hereinafter referred to as Workflow) includes six (6)
stages, each involving engagement and collaboration between Syseon and MCSO. The diagram below shows each of
the six stages and the activities that occur within each. The activity streams are color-coded for easy identification of
which tasks are related and typically involve the same project personnel. This implementation model will be followed
for each of the two implementation phases described above (recognizing some of the deliverables from Phase 1 will be
reusable in Phase 2a and 2b, such as some of the planning documents that make up the Project Management Plan).
Activities related to Change Management that are shown reflect Syscon's original proposed approach. They have been
left as is acknowledging that MCSO is now leading Organizational Change Management and may choose to follow a
different approach and/or modify the activities shown below.

SERIAL 13139-RFP
Configure Valid te Transition.
• CreVePropict • Monger and manage • Monitor and manage . Monitor and manage • •••et• and manage • Monitor and rrerssge
Management Plan Platiea PrDieD Prolezt Polar Peel V=
• Prolertkekeer . Transtron to Support
• Crete orgeninfland • Corrnuneatectrang • Ira& charges(ongo'ngl • SaPlaart production cm- • Close proierr.
• leadership alignment change managemwe ▪ implement Maga i • Communicate (ongongl. aver
and stakeholder Plan tradcing
• Cream rernmuneeton • Suppatt user aarditaise • Support production
engagement Pam testng • Perform frig. pro • •rarstionto
• Cregeorgarinatene • literal'. and agree • Conftureeprifeation, data low
change management mange Marls tusinessades anti
somcegy • motardechangentowol orchestrations . • !rn Waren data
• Creaxectrargetraddrg • Creriteconfiguragian : migration • Support integration rut- • Support production
▪ Frapareard darner Plan =eta/cation oaer
lmpiementavon Suvev • Design anti build reports
. Pan configuraren Suppart interfivetesting eral-tn-enci • Support prodlit-tron cle- • &gown production
Developsystern • DOM migration weafp's aves • Denby patithesto
• died preliminary Svsom panNi.ridain plan Rod demo rictiveprodurriari
erssionments Mrs
• Support erarimrarems • Preprrepost-gote'n
• Plan data nitration • Design interfaces • Depby patolv trailing
• Compiateand return • Deriver overvieW data • Buitl interfaces • Conduct pose-go-We
limplementar:ion Survey mtrarien aiggoach aid lre ming J
SOWS . Conduct G o-Lioe trairrire • _date Vaildreethei troduction :
• entail configured bad
applicatimil [Berg • Verrly macho
• Nan ntertecrm envirenraenta • Perfarmturational
• Deriver everview on
mearfaceapproacti and • 'Calor produatramrp . Perfoon teitiss eats:ration • ReportlxtrdrAttiOn issueg
PrOect Management nang mderial testing • Perform usmtategftre
Orgartemtionai • Support 9rscon • Conduct TS ueTang Paicern systarntesting tarngat patches '
O Change Management anvaterients . Conduct Parterre:9mM
o configuratem • Awistwitti Mtn:strum • Vera. conitguratice teiting
igannMg 'overrate= data • Perform security Mafia
Data M igrat ion mt ration, reports
o integration . • Perform endeo-erd data
mtrationti="ng
instaattion / Crep/oyme • Defiresinice data • Perform end-mend
marlOirg interfecatestite
O Training • Dial andtest rePari3 • Perform user accesstarge,,
Tasting testtig
• Plan for productiPnarg-
Client o/er
GR = Gate Review
Figure Error! No text of specified style in document-3 Syseon Jail Management System Implementation Model
10.5.2. Syseon Jail Management System Implementation Model
10.5.2.1. Stage 1 — Prepare
During the Prepare stage of the implementation project, the framework and infrastructure needed to guide and support
project activities are put in place.
• Leadership alignment
• Create Prolect and stacehofder • Prepare and deiVer • Complete wid return
; Management Pim implementatkin • Build preliminary
engegement *mon enyircnrrients Irripbmentatbn
; • Proiect kick-off • Create dr gankational Survey 1, Si:maw
changemanagernent
strategy
Organizational
0 Project Management 0 Change Management 0 Configuration 0 Installation J De picoyment Client
Figure Error! No text of specified style in document.-4 Prepare Stage Diagram
The first task in the Prepare stage is to initiate the project. A Project Charter will be produced, which defines the
purpose and management objectives of the project, defines the limits of the project manager's authority, and identifies

SERIAL 13139-RFP
any known assumptions and constraints that could affect the project. This document will also identify all the
stakeholders and organizations that may be affected by the project.
Table Error! No text of specified style in document.-17 Prepare Stage Activities
Activity Owners Description
A Project Management Plan (PM?) is drafted describing how all of the different aspects of the project
will be controlled The PMP includes the following elements:
Project Charter
Scope Management Plan
Work Breakdown Structure
Change Management Plan
Project Schedule
Schedule Management Plan
Cost Management Plan
Create Project Management Plan Syscon Quality Management Plan
Test Strategy
Requirements Specifications Management Plan
Configuration and Release Management Plan
Project Organizational Structure
Resource Management Plan
Communication Management Plan
Risk Management Plan
Although the P/vIP is approved during the project's Prepare stage, the specific content related to the
plans it includes is created in the Define stage. For example, the Risk Management Plan is created in
the Prepare stage, but the Risk Register will be created in the Define stage.
A formal project kick-off occurs with the Syscon team and also with the key project stakeholders from
MCSO (including the MCSO Core Team). It is essential that all stakeholders attend this meeting, even
MCSO if their specific involvement in the project is many months away (e.g. MCSO live support team). The
Project Kick-Off Syscon Syscon project team also engages in team-building exercises that maximize the 'one-team' spirit,
which will result in improved project outcomes.
A Project Governance structure is put in plaim.
It is essential that MCSO leadership are completely aligned with the goals and objectives of this
project if the project is lobe successful. The Organizational Change Management Team will:
Leadership Alignment and IVICSO Define Stakeholder Approach
Stakeholder Engagement Syscon Wen* Stakeholders and Key users
Complete Stakeholder Impact analysis
Mobilize change network
Create Organizational Change MCSO The objective of the strategy is to ensure the acceptance of change across the organization. The
Management Strategy Organizational Change Strategy shalt ensure the alignment of the MCSO towards program objectives,
covering all relevant stakeholders across contributing initiatives.
The Implementation Survey is used to facilitate understanding of basic terminology and business
Prepare and deliver Syseon processes in use by MCSO personnel. Syscon tailors the generic version of this survey to reflect the
Implementation Survey scope of the MCSO project and delivers it to a designabacIMCSO contact via email.
Syscon establishes the system environments for internal development and test use throughout the
Build Preliminary Syscon Syscon implementation life cycle. This also includes a cloud-based environment that is used in the early
Environments stages of the project (Define and Configure) to iteratively demonstrate progress to ivICSO core project
team members,
Complete and Return An MCSO contact returns the completed Implementation Survey to a designated Syscon contact via
Implementation Survey MCSO email. Syscon uses the survey response to create an initial configuration of the Workflow system that
reflects MCSO business processes and language.

SERIAL 13139-REP
The final step of this stage is a Gate Review conducted jointly with Syscon and MCSO project teams. This Gate Review
is key to ensuring that all stakeholders agree that the project is ready to proceed to the Define stage. During this
activity, lessons learned will be documented and shared with all stakeholders to ensure that any learning is incorporated
into future project activities, as appropriate. The Project Steering Committee will provide final approval to proceed to
the Define stage.
10.5.2.2. Stage 2— Define
The Workflow Commercial Off-The-Shelf (COTS) product is highly configurable. In addition to standard
configuration (e.g. localization and preferences), Workflow allows clients to define the orchestration (ordering) of tasks
in each business process. The use of a business rules engine facilitates the system's ability to meet project requirements
without the need for costly customization.
During the Define stage of the project, the detailed configuration, interface, data migration, and training requirements
are captured in order to establish the scope of the project activities.
Deftne S a e
• Monitor and manage • Create change organtraional rnanagement • Plan configuratbn • • Plan data migration • Plan iiterfaces
project Plan • Deveiop system Deliver overview on • Deliver overvievv on
• Creztecommunicattini configuration plan data ro igraion interface approach
approach and tools and tools
Wan
• ident ry and agree
change agents
• Mobitzechange
network
• creue change
tracking pan
• Support Svscon
• AsSistwith erivionments • • Complete Plan trakfrig • Cr etre test plan • Provision Site
infrastructure configuration training intratructure
plarimng
Organizational
O Project Management 0 Change M anagement 0 Configuration Data Migration 0 integration
O insialiation / Deployment 0 Training Testing 0 Client
Figure Error! No text of specified style in document-5: Define Stage Diagram
At the beginning of this stage, a team of Syscon resources will be onsite for a series of in-depth meetings to map out the
configuration, interface, data migration, and training components of the MCSO solution. Through this analysis process,
MCSO resources will be exposed to the configurability of the Workflow system. The Syscon project team for this
planning exercise will consist of Functional Analysts, Subject Matter Experts, Technical Analysts, Training Specialists,
and Project Managers. These individuals work with their MCSO counterparts to ensure that the requirements and
approach are documented, and that stakeholder approval is obtained, establishing the detailed scope of the
implementation project.
Syscon will deploy development and test environments (for interface and data migration development activity) for
internal use at their offices, and will also deploy a cloud-based environment for the MCSO project team. This cloud-
based environment will be used during the Configuration stage of the project until the configured system is deployed.
Table Error! No text of specified style in document.-18 Define Stage Activities
Activity Owners Description

SERIAL 13139-RIT
Activity Owners Description
Monitor and manage Project During the monitor and manage project activity, the project management team will ensure that activities stay on
project Management Teem track, facilitate open cross-team communication, and manage any project schedule and deliverable changes that
result from the outcome of planning activities.
The organizational change strategy identifies how acceptance of the new .IMS solution will be obtained across
Create organizational MCSO business units. It outlines how MCSO business functions will be aligned towards business objectives,
change management plan MCSO and ensures that all relevant stakeholders are considered acTOSS contributing
The organizational change management plan details the activities required to deliver the strategy.
Create communication
plan lvICSO Refer to section 5
Identify and agree change MCSO
Refer to section 5
agents
Mobilize change network MCSO Refer to section 5
Create change tacking
MCSO Refer to section 5
plan
During the configuration planning, the Workflow system functionality will be demonstrated, and the activities
required to configure it for MCSO use will be identified.
Plan configuration Syscon
The configuration planning activity will result in an updated requirements traceability matrix for the project It
will also facilitate discussion and action planning related to perceived feature gaps in the Workflow
functionality and the resolution of any identified implementation challenges.
The configuration plan will identify all of the configuration items, and will identify the order in which their
Develop system respective areas of the system will be configured. It will document roles and responsibilities for the
configuration plan Syscon configuration tasks, and detailed requirements for some specific elements of the configuration (such as sentence
calculation rules, reports, and business process orchestration). The system security policy and the system
configuration required to support it will also be documented in this stage.
During the data migration planning, the requirements for migrating MCSO' s legacy data into the Workflow
application are identified. Syscon analysts will work with the MCSO technical team to review and further
define the data migration strategy for the project
Plan data migration Syscon
The data migration plan outlines the requirements, approach, tools, roles, responsibilities, and the work plan for
accomplishing the project data migration tasks.
Deliver overview on data
migration approach and Syscon The data migration approach and tools overview wilt provide MCSO staff with the information they need in
order to successfully participate in project data migration tasks.
tools
Doting the interface planning, the requirements for interfacing Workflow with identified sub-systems are
identified. Syscon analysts will work with the MCSO technical team to review and further define the interface
strategy for the project.
Plan interfaces Syscon
The interface management plan will outline the sub-systems that require interfacing, requirements, approach,
tools, roles, responsibilities, and the work plan for accomplishing the project interface work.
Deliver overview on
interface approach and Syseon The interface approach and tools overview will provide MCSO staff with the information they need in order to
tools successfully participate in project interface development, testing, and deployment tasks.
Support Syscon The support Syseon environments activity is where Syscon configuration management staff members support
environments Syscon the project team in the deployment of configuration data and ensure that project environments are available for
use.
Syscon Assist MCSO with In order to assist with infrastructure planning, Syscon will collaborate with MCSO on an Enterprise
infrastructure planning MCSO Architecture Design, which will define the overall form and function of systems (business and 11) across the
MCSO environment (including partners and organizations forming the extended enterprise). The design will

SERIAL 13139-RFP
Activity Owners Description
provide the framework, standards, and guidelines for project-level architectures
The training planning activity will confirm assumptions about the number of staff requiring training, the staff
breakdown across system binational areas required for training. The number and type of training classes
Plan training Syscon required will be finalized as part of this activity.
The training plan will document how training will be delivered throughout the remainder of the project, will
outline the training work plan, and identify training-related roles and responsibilities.
Complete configuration Syscon The configuration training will provide MCSO staff with enough understanding of the system's configuration
training to participate actively in the configuration stage of the project.
The test plan will detail the approach and tools that will be used to complete the following testing activities:
Load
Regression
System
Create test plan Syscon Functional
Security
High Availability / Reliability
The test plan will also document the proposed approach to defect management
Provision site MCSO The provision site infrastructure activity is where MCSO will acquire and install the hardware and software
infrastructure inflastnicture required to set up local Workflow system environments.
The final step of this stage is a Gate Review conducted jointly with Syscon and MCSO project teams. This Gate Review
is key to ensuring that all stakeholders agree that the project is ready to proceed to the Configure stage. During this
activity, lessons learned will be documented and shared with all stakeholders to ensure that any learning is incorporated
into future project activities, as appropriate. The Project Steering Committee provide final approval to proceed to the
Configure stage.
103.2.3. Stage 3 — Configure
During the Configure stage, Syscon and MCSO jointly execute the plans that were agreed to in the Define stage.
• coorgure application, • Data mgraion • Design interfacim
buginess orchearaions rutin, and analysis and desgn • Build interfaces
• Create configuration
specification
• Dmg- n and build
reports
• inaaa configured • Talor product tranirg • Verify configuration • Define sowee data
applicatbn n diem maerial interfaceg data fna,Ping
environments • ConductT3 training mgration, reports • Build and test reports ;
Org an ttationa I
O Project Management 0 Change Management 0 Configuration Data Migration 0 /Meg nation
O Installation / Deployment 0 Training Testing 0 Client
Figure Error! No text of specified style in document.-6: Configure Stage Diagram

SERIAL 13I39-RFP
This stage of the project is conducted according to an iterative approach that enables Syscon and MCSO to
collaboratively refine the system's configuration using the cloud-based Workflow deployment. This approach ensures
that the MCSO project team is engaged throughout the system's configuration activities, minimizing the risk that there
are issues with the configuration once the Acceptance Testing activities begin in the Validate stage. As configuration
completes for major product releases, Syscon will deliver the documented configuration specification document and the
configured software package for installation at MCSO.
Table Error! No text of specified style in document.-19 Configure Stage Activities
Activity Owners Description
Dining the monitor and manage project activity, the project management team will ensure that activities stay on
track facilitate open cross-team communication, and manage any project schedule and deliverable changes that
Project result from the configuration, training interface, and data migration activities.
Monitor and manage
Management
project Team During this stage of the project, the Support Transition Plan is developed to identify how training and knowledge
transfer activities will be conducted.
Prepare MCSO' s first-line support team for supporting end-users of the Workflow system,
Prepare Syscon's Support staff to support MCSO once the project's Transition stage has completed.
Communicate changes MCSO Refer to section 5
Implement change
MCSO Refer to section 5
tacking
During the configuration activity, Syscon configuration specialists will work with the MCSO core project team to
complete identification of the configuration values required to complete the Workflow system configuration. The
Configure application, application set-up, reports, business rules, and business process orchestrations are implemented according to the
business rules, and Syscon requirements and order precedence defined in the system configuration plan.
orchestrations
Once each portion of the system configuration is finalized, it is documented in the system configuration
specification, which is delivered to MCSO with the configured environment.
Data migration analysis During the data migration analysis and design activity, the Syscon project team performs data migration analysis,
and design Syscon determine data security controls, and design data migration environments and procedures. For more Mfonnation
about the data migration approach for the project, please reference Question 8 in this section.
Design interfaces Syscon During the design interfaces activity, the Syscon project team performs interface analysis and creates a design for
each interface under development
Build interfaces Syscon During the build interfaces acvtivity, the Syscon project team builds the interfaces, according to the documented
design specifications.
Install configured
application in client Syseon Dining the installation activity, Syscon technical staff members install the configured Workflow system onsite at
MCSO in preparation for the Validate stage of the project
environments
Tailor product training Syston During the tailor product training material activity, Syscon's Workflow product training material is tailored to reflect
material the system configuration, and also to include established change management messaging.
Conduct T3 training Syscon During the Conduct T3 training activity, Syscon trains MCSO staff miners in accordance with the defined training
plan for the project.
Verify configuration,
interfaces, data Syscon Throughout the Configure stage, Syscon test resources verify the configuration, interfaces, data migration, and
migration, reports reports at defined intervals prior to deployment according to manual and automated test scripts.
Define source data MC SO During the Define source data mapping activity, MCSO works with the Syscon project team to map the legacy
mapping system data to the workflow application data staging specifications.
Configure and test Iii addition to the reports that Syscon will create for the project, MCSO may have additional reporting needs.
reports MCSO During the build and test reports activity, MCSO project team members will build and test additional moons, with
support from the Syscon team if required.
Activity will be scheduled in iterations, according to the work plans identified in the planning documentation, and at the
completion of each iteration, changes/configurations will be bundled and deployed to the MCSO cloud environment for

SERIAL 13139-RFP
validation by MCSO in joint progress review sessions. Upon completion of a major product release and its
corresponding configuration activity the configured software will also be delivered for deployment at MCSO
The final step of this stage is a Gate Review conducted jointly with Syscon and MCSO project teams. This Gate Review
is key to ensuring that all stakeholders agree that the project is ready to proceed to the Validate stage. During this
activity, lessons learned will be documented and shared with all stakeholders to ensure that any learning is incorporated
into future project activities, as appropriate. The Project Steering Committee provide final approval Co proceed to the
Validate stage.
10.5.2.4. Stage 4 — Validate
During the Validate stage, Syscon project team members support MCSO while they execute the defined acceptance
testing test suite in order to validate the configured Workflow system in the MC SO test environment.
• Track changes
• Monitor and manage (orlgobg3 • Support usa- • support end-to-end
project • Comm unicate ecceptancetatrig interfacetestirg
Congo-MO
• Perform end-to-end ;
• Conduct Go-Live • Perform functional data migralon testing
trainng bmting • Perform endto-end
• Perform iltegration interfaceterting
testing : • Perform user
• Perform Ng ern acceptancetestkig
testng • Planfor production
• Conduct performance cut-ever
testrig
• Perform mcurtry
timtkig
Organizational
O Project Management 0 Change Management 0 Configuration Data Migration
O lnstaitation j Deployment 0 Training Testing 171 Client
Figure Error! No text of specified style in document.-7: Validate Stage Diagram
Table Error! No text of specified style in document-20 Validate Stage Activities
Activity Owners Description
Monitor and manage Project During the monitor and manage pmject activity, the project management team will ensure that activities stay on
project Management Imelc, facilitate open cross-team communication, and manages any project schedule and deliverable changes that
Team result front the verification and validation activities
Track changes MCSO Refer to section 5
Communicate MCSO Refer to section 5
During the support user acceptance testing activity, Syscon triages and resolves reported issues. Each issue is
assessed to detell 'line whether it is a configuration issue, a training issue, or a product defect and is then
appropriately msolved.
Support user acceptance
Sysc,on
testing
As defects are discovered, they will be fixed, bundled into a patch releasr, and installed in the UAT environment
After each patch deployment, a regression test suite is run to ensure that the defect resolution patch has not
introduced new problems into the environment.

SERIAL 13 139-RFP
Activity Owners Description
Implement data During the implement data migration activity, Syseon will develop data migration procedures, extract data, confirm
migration Syscon data integrity, transform data, and perform dry runs of data loads. The data migration will be tested by Syscon staf
who will also support MCSO project testing of the data migration output
Support end-to-end During the support end-to-end interface testing task, Syscon will work with the IvICSO project team as they perform
Syscon
interface testing user acceptance testing on the delivered interface functionality.
Support environments Syscon Throughout the Validate stage, Syscon configuration management staff members maintain Syscon's internal project
environments to support the work of the project team.
Deploy patches Syscon As software problems are identified and reported, those issues are fixed by Syscon product team members.
Celia:led code is deployed in patches.
During the conduct go-live training activity, Syscon business analysts and trainers support MCSO staff as they train
Conduct go-live training MCSO the end-users to use the Workflow solution, This support is given onsite during the initial stages of end-user
training, and as MCSO trainers become more comfonable with the system and the training material, this support
will transition to being provided remotely.
Perfonn functional MCSO Dining the functional testing activity, the *stem's functionality will be tested to confimi that it is functioning in
testing (Syscon Support) accordance with the published ftmctions and features of the application. This testing method uses a combination of
automated and manual tests
During the integration testing activity, the different software modules, configured to MCSO requirements, are tested
Perform integration MCSO together to ensure that the orchestrations and business workflows are correct and that the entire application is
testing (Syscon Support) behaving as intended. Interfaces will also be tested to ensure that data is flowing correctly between the different
systems. This interface testing may be simulated (e.g. with stubs) and sample or mocked-up data may be used.
IvICSO During the system testing activity, the entire system will be tested against the system test cases, which provide fiat
Perform system testing
(Syscon Support) coverage and have traceability to the project requirements.
In parallel with user acceptance testing activities, load and stress testing will be completed on the proposed live
production environment Load testing tools will be used to determine system performance under normal and
Conduct performance MCSO anticipated peak load conditions. Certain high volume business scenarios will be selected to be tested as part of this
testing activity.
testing (Syscon Support)
These tests will measure system availability against the documented performance expectations. For more
information about the proposed performance testing approach, please see question 10 in this section.
MCSO During the security testing activity, Syscon will complete security testing on the proposed live production
Perform security testing environment in order to test authentication and authorization functionality, to ensure that unauthorized access to
(Syscon Support)
confidential data in the system is prevented.
Perform end-to-end data MCSO During the end-to-end data migration testing activity, MCSO staff members will validate that legacy data has been
migration testing correctly loaded into the Workflow system.
Perform end-to-end During the end-to-end interface testing activity, MCSO staff members will validate that the interfaces are sharing
MCSO
interface testing data with 3rd party systems in a way that meets the stated requirements..
Perform user acceptance Dating the user acceptance testing activity, participants will simulate real-life business scenarios to test that the
MCSO
testing application behaves as anticipated and is capable of supporting MCSO business processes.
During the plan for production cut-over activity, Syscon will support MCSO in planning the production cut-over
and creating a detailed go-live plan and checklist. This plan will ensure that all parties have clarity regarding the
Plan for production cut- tasks, schedules, roles, and responsibilities for the project go-live. (Attachment, C, Appendix 3, Section 7, Question
MCSO 2 Example Plan)
over
During this activity, the support transition plan is reviewed and the activities related to preparing the MCSO team to
support end users post-go-live are executed with Syscon's support.
The final step of this stage is a Gate Review conducted jointly with Syscon and MCSO project teams. This Gate Review
is key to ensuring that all stakeholders agree that the project is ready to proceed to the Deploy stage. Project artifacts
(e.g. test exit reports, defect log) are reviewed and the project team provides a joint recommendation to the Project
Steering Committee regarding whether or not the system is ready for deployment. The Project Steering Committee
provide final approval to proceed to the Deploy stage.

SERIAL 13139-RFP
During this activity, lessons learned will be documented and shared with all stakeholders to ensure that any learning is
incorporated into future project activities, as appropriate.
10.5.2.5. Stage 5— Deploy
During the Deploy stage, a subset of the Syscon project team will be on-site to assist with the successful transition of
the project to the live production environment. The focus of this stage is to successfully bring the new system online in
the production environment.
• Monitor and manage • Support production • Perform fn e4 • Support ntegration • Support production
project cut-oyer production data lead cut-aiter cut-cwer
• Prepwepost-go-41/e • VaIdatofrial
training production data load
O Project Management 0 Configuration Data M igration 0 Integration 0 insthVation / Deployment
O Training U Client
Figure Error! No text of specified style in document.-8: Deploy Stage Diagram
Utilizing the cut-over plan to execute this stage of the project, the production data load is completed and then the system
is subjected to a series of validation checks to ensure readiness. For example, during this activity, inmate counts are
generally verified against the legacy system in order to ensure that all of the data has been moved to production
successfully, with only explainable variations.
Table Error! No text of specified style in document.-21 Deploy Stage Activities
Activity Owners Description
During the monitor and manage project activity, the pmjeet management team will ensure that
activities stay on track, facilitate open cross-team communication, and manage any project schedule
Project Management and deliverable changes dun result flOui the production cut-over activities.
Monitor and manage project
Team
The project management team works with the project team to effect a smooth production cut-over by
ensuring that activities are performed in line with the established cut-over plan and that any issues are
promptly triaged and resolved.
During the production cut-over, and for several days afterward, a subset of the Syscon project team
Support production cut-over Syscon will be onsite to help support the MCSO team during live production use of the system Syscon staff
will help to triage issues and ensure that reported problems am promptly reported back to the Syscon
product and project teams for resolution.
Perform final production data Syscon During the support final production data load activity, Syseon will perform the production data
load migration and produce summary data migration reconciliation report.
During the production cut-over, and for several days afterward, a subset of the Syscon project team
Support integration cut-over Syscon will be onsite to help support the MCSO team during live production use of the interfaces. Syscon
staff will help to triage issues and ensure that reported problems are promptly reported back to the
Syscon product and project teams for resolution.
During the prepare post go-live training activity, plans are finalized for the schedule and focus of post
Prepare post go-live training Syscon go-live follow-up trainingjmentoring. Syscon business analysts work with the MCSO project core
team to develop the post go-live training agenda.

SERIAL 13139 -RFP
Activity Owners Description
Validate final production data MCSO During the perform final production data load activity, MCSO staff members execute validate key
load production data expectations.
The final step of this stage is a Gate Review conducted jointly with Syscon and MCSO project teams. This Gate Review
is key to ensuring that all stakeholders agree that the project is ready to proceed to the Transition stage. The production
data load is reviewed by MCSO core project team members, and the project team provides a joint recommendation to
the Project Steering Committee regarding whether or not the system is ready to go live. The Project Steering
Committee provide final approval to take the system live and to proceed to the Transition stage.
During this activity, lessons learned will be documented and shared with all stakeholders to ensure that any learning is
incorporated into future project activities, as appropriate.
10.5.2.6. Stage 6 — Transition
During the Transition stage, the project team supports live use of the system. Also in this stage is the thirty (30) day
reliability test period.
Tra risitiort stage
• Monitor and manage • Support production
prOjea • Support production • Dap by patches to
• Trartstion to Support • Transtion to Support resolve production
• Close project es
• Report production
iSSUe5
. • Verify pachm • Perform user
acceptancetestkig of
patches
o Project Management 0 Configuration Data M igration 0 Installation / Deployment 0 Training
Testing ("-- Client
Figure Error! No text of specified style in document-9: Transition Stage Diagram
Upon successful completion of the reliability test period, the project moves into the Warranty Period. During this
period, Syscon will provide second and third-tier support for triaging and fixing any application defects that are
discovered, in accordance with the established service level agreement.
Table Error! No text of specified style in document.-22 Transition Stage Activities
Activity Owners Description
Project Management During the monitor and manage project activity, the project management team will ensure that
Monitor and manage project Team activities stay on track, facilitate open cross-team communication, and manages any project schedule
and deliverable changes that result from the transition activities.
During the transition to support activity, Syscort project team members transition the configuration,
Transition to Support Syscors business rules, and orchestration work done for the project to the Support team for ongoing support
and maintenance of the product
Support production Syscon During the support production activity, Syscon provides second and third-level support to MCSO for
issues related to the interfaces.
Transition to Support Syscon During the transition to support activity, Syscort =salons the interface development work that they

SERIAL 13139-RFP
Activity Owners Description
completed for the project to the Support department to ensure that Syscon can support the interfaces
developed as part of the project
Support production Syscon During the support production activity, Syscon configuration management resources support the
Syscon product and project teams in the resolution of reported issues.
Deploy patches to resolve As software problems are identified and reported, those issues are fixed by Syscon project team
Syscon
production issues members. Corrected code is deployed in patches by the responsible organization.
During the conduct post-go-live training activity, Syscon provides onsite follow-up training and
Conduct post-go-live training Syscon mentoring sessions to help evaluate the effectiveness of end-user training and to actively help to
resolve any post-go-live concerns on the part of end users.
Report production issues MCSO On an ongoing basis, MCSO support staff will triage and then either resolve issues reported from encl-
osers, or escalate those issues to Syscon's support department if they are software problems,
Perform user acceptance testing For each patch deployment of fixes and new features from the Syscon product team, MCSO will
MCSO perform user acceptance testing of the patch prior to loading the modified code into the MCSO
of patches
production environment.
The final step of this stage in Phase I of the project is a Gate Review conducted jointly with Syscon and MCSO project
teams. The project team provides a joint recommendation to the Project Steering Committee regarding whether or not
the system is stable enough to refocus the project team on Phase 2 activities.
The final step of this stage in Phase 2b will occur at the successful close Warranty Period, when formal project closure
will occur.
10.5.3. Configuration Approach
During the Define stage of the project, Syscon business and technical analysts will conduct onsite configuration
planning sessions with MCSO core team members that cover each functional business area. The purpose of these
workshops is to produce an initial definition of MCSO-specific configuration based on the MCSO's business processes.
Each Configuration workshop must have MCSO participants with adequate subject matter expertise, who are
knowledgeable in the business areas affected.
MC50 Configuration Workshops
Rosiness MCSO
Protest Workflow
Analysis Orchestration
inputs i 1 1.01 Al;; .Ni01. 1 outputs
e,reet,c,, Fte
Requirements System NICSO
Traceability Conflguration Training
Syscon Business Analysts and Default Workflow"' Matrfa Document Documents
MCSO Core Team Members Product Configuration
Cade Business Report
Tables Rules Models
Figure Error! No text of specified style in docurnent.40 MCSO Configuration Workshop
Throughout the workshops, some of which may occur concurrently, Syscon will provide knowledge transfer to the
MCSO core team to optimize configuration understanding. Workshop output consists of a series of documents:
ao_

SERIAL 13 I39-RFP
• Session Notes which record MCSO decisions and any project action items or issues discovered during the
workshop. These notes are distributed to all participants following the session.
• Updated Requirements Traceability Matrix, outlining how Workflow meets each requirement
• Updated Configuration Plan document
These sessions will also clarify the actions required by MCSO core project team members to work with the business to
gather the required configuration information. With Syscon's support, the MCSO team will need to populate
configuration spreadsheet templates with configuration data and return them to Syscon for loading into the Workflow
system. The configuration templates, after submission to Syscon, will form the basis of the reference data to be
configured in MCSO' s installation of Workflow.
Where it is practical, and where the necessary configuration values are already known, they will be documented in the
meeting notes and no further action will be required. In some cases, additional analysis will be required in order to
determine how the system will meet the requirement, and in those cases, Syscon staff will complete that analysis post-
session and incorporate the results into the session notes prior to their submission.
Workflow is highly configurable, and every effort will be made to find a configuration solution to any identified issues.
Configuration options in Workflow product include:
• Code tables: standard code sets, formatting, priority sequencing, system values, profiles, location
preferences
• Business processes: orchestration of Workflow screens into user workflows and task pool. Changes to
business process orchestrations will be documented in the Configuration Plan.
• Business rules: set-up of the Workflow business rules engine to support business functions such as sentence
calculation.
• Reports: Optimizing use of the integrated Workflow reporting and business intelligence tool (Oracle BI
Publisher), ideally using existing operational and 'Schroeder' reports.
In the event that either during or following the workshops it is deemed that an MCSO requirement cannot be met by the
Workflow system either out-of-the-box or through configuration, or that MCSO would prefer that the Workflow
product meet that requirement in a different way from how it is met out of the box, a project issue will be logged and
managed through the product change request process.
Once all of the configuration workshops have taken place and all of the follow-on analysis and documentation activities
are complete, Syscon will submit the updated configuration plan to MCSO for review and approval.
During the Configure stage of the project, Syscon will implement and test the approved configuration in iterations,
which will be demonstrated to the MCSO project team to elicit feedback and show progress. Also during this stage, the
Workflow product training material is tailored to match the MCSO-specific product configuration. After all of the
configuration has been established, the configuration specification document is prepared through a combination of
manual documentation activities and generating a report from Workflow that contains many of the configuration details.
The report portion of this document is provided by the COTS product and can be used to maintain documentation of any
configuration changes introduced over time. This report can be re-run by MCSO staff each time the configuration is
changed.
Following the completion of configuration milestones in the Configure stage Syscon will deliver a configured software
package for install onsite at MCSO facilities. The system and its configuration are banded over to the MCSO project
core team, and any additional changes that are deemed necessary to the configuration during or subsequent to the
Validate stage will be performed by MCSO staff in MCSO environments.
10.5.4. Data Migration Approach
Based on our prior experience on major data migration and PAS implementation projects we recommend undertaking a
multi-step iterative process that leverages the standard ETL tools and incorporates the following major work
components:
84-

SERIAL I3139-RFP
Data Migration
Data Migration Data Migration Data Migration
Analysis and
Planning Implementation V Closeout
Design
Figure Error! No text of specified style in document.-11 Data Cleansing and Migration high level approach
Data Migration Planning Phase:
The Data Migration Planning phase is broken down into five (5) major tasks. The Conversion Manager, in
collaboration with the Data Migration team, will determine the order in which these tasks will be performed.
Table Error! No text of specified style in document.-23 Data Migration Planning Phase
Major Task Description
Project Planning Establish the Conversion Scope (source systems and data within those systems); Identify Risks, Constraints, Dependencies and
Assumptions; Develop Risk Mitigation Plan; Identify Data Migration Acceptance/Success Criteria
Determine Data Determine Business Requirements; Determine Technology and IT Infrastructure Requirements; Determine Data Security and
Migration Requirements Privacy Requirements during ETL process
ACCOS Current Identify and collect misting data-related artifacts (sources, documentation, business area subject matter experts); Identify current
Environment data maintenance processes; Blueprint current state of data and data architecture
Develop Data Migration Determine conversion plan; Determine data integration plan; Plan deployment (how will migration be done to support go-live);
Plan Develop migration data quality plan; Develop data migration test plan
Confirm and Assign Confirm migration roles and responsibilities; Identify and assign resources to migration roles; Confirm MCSO resources to
Roles & Responsibilities support migration and data cleansing
Data Migration Analysis and Design Phase:
The Data Migration Analysis and Design phase is broken down into four (4) major tasks.
Table Error! No text of specified style in document.-24 Data Migration Analysis and Design Phase
Major Task Description
Perform Data Migration Analyze current source data; Evaluate data quality; Perform data profiling
Analysis
Determine Data Secutity Determine enterprise management and operational security controls
Contents
Design Data Migration Design load/staging area(s); Correlate migration data (source/staging/WV); Determine ETL configuration; Migration Data
Environments Mapping
Design Data Migration Design data extract processes; Design data transformation/validation processes and rules; Design data quality I4wediation
Procedures processes (involving MCSO data cleansing); Review and update Data Migration test plan; Design data load plan; Design data
integrity and auditability processes and procedures; Develop data backup and recovery plan
Data Migration Implementation Phase:
The Data Migration Implementation phase is broken down into six (6) major tasks.
Table Error! No text of specified style in document.-25 Data Migration Implementation Phase
High-Level Task Description
Develop Data Migration Configure ETL; Develop and test data extract processes; Develop and test transformation/validation processes; Develop and test
Procedures data load processes; Confirm data integrity processes
Extract Data Create load environment; Extract source data/populate load area; Integrate/merge load data; Validate loaded data; Produce
summary Load Reconciliation Report
Confirm Data Integrity Confirm data integrity and identify non-confirming source data, MCSO to cleanse data according to Data Remediation Plam Re-
load and validate cleansed data; Produce summary Data Integrity and Reconciliation Report

SERIAL 13139-RFP
Transform Data Transfomi clafft; Validate transformed data; Produce summary Data Transformation Reconciliation Report
Load Data Perform dry-run data load into Workflow and validate results. Data Conversion Trial Run Report
Perform Production Based on the overall MS/ Workflow Deployment/Go-Live Plan and Data Migration Plan, =cute the Production Data
ETL Migration and produce Summary Data Migration Reconciliation Report. Obtain sign-off
Data Migration Closeout Phase:
The Data Migration Closeout phase consists of one (1) major task as noted below:
Table Error! No text of specified style in document.-26 Data Migration Closeout Phase
High-Level Task Description
Pot-Migration Operate new JMS environment and remediate issues related to data migration as required. Release ETL environments and ensure
temporary data stores are properly archived and/or scrubbed
The major activities required to support a successful data migration are noted in the section above, and summarized in
the table below with respect to the Syscon and MCSO roles. Based on MCSO's experience with the current legacy
applications from which source data will be migrated, it is important to highlight key roles that we will look to MCSO
for including provisioning of legacy data documentation (e.g. data dictionaries, current data validation rules etc.) as well
as investigation and data cleansing of source data that fails to meet the rules established for loading into the new .IMS/
Workflow.
Table Error! No text of specified style in do c ment.-27 Data Migration Activities and Roles
Task Syscon Role MCSO Role
Project Planning B. A
Determine Data Migration Requirements R, A
Access Current Environment A, C
Develop Data Migration Plan R, A
Define and Assign Roles & Responsibilities R, A
Perform Data Migration Analysis R, A
Determine Data Security Controls R, A
Design Data Migration Environments R, A
Design Data Migration Procedures R., A
Develop Data Migration Procedures k, A
Extract Data C, I R, A
Transform Data R, A C, I
Investigate and Cleanse Source Data R, A
Load Data R, A C. I
Document Data Migration Results R, A C, I
Legend:
R — Responsible - Those who are responsible to do the work to achieve the task and the creation of documents or
information. This role includes facilitation of information gathering and creation of deliverable material or the active
support to create the information.
A - Accountable - Those who are ultimately accountable for the correct and thorough completion of the deliverable or
task. The responsible entities have work/tasks approved, or signed off by the individual(s) accountable for each task or
deliverable. (Also approver, or final approving authority)
C - Consulted — Those whose opinions are sought through communications or participation in meetings or workshops.
I - Informed - Those who are kept up-to-date on progress, often only on completion of the task or deliverable. Receive
corn municati on.
The specific Phases of the Data Migration Activity and how they Map to the overall implementation model is reflected
in the table below:

SERIAL 13139-RFP
Table Error! No text of specified style in document.-28 Data Migration Activity Map
Data Migration Phase Syscon Jail Management System Implementation Model Stage
Data Migration and Planning Define Stage
Data Migration Analysis and Design Define Stage
Configure Stage
Data Migration Implementation Validate Stage
Deploy Stage
Data Migration Closeout Transition Stage
10.6. Integration and Interface Development
10.6.1.. Interface Analysis Approach
Our approach and methodology that we will use to analyze the existing interfaces, develop the custom
interfaces and test the required internal MCSO and external agency interfaces is based upon the foundation
and capabilities of the Enterprise Service Bus (ES B) that is part of the Workflow product framework. The
ESB enables integration between Workflow and client source systems (internal or external). This
standardized tool ensures a consistent interface approach is followed and aids in reducing the costs to link to
MCSO's legacy systems where required. The Workflow native "out of the box" interface capability promotes
easy connectivity and data exchange through devices such as standardized APIs. ESB technology provides
industry standard communication options (one way, producer, consumer, bi-directional, stateless, state full,
etc.). Within this construct, Syscon also supports the National Information Exchange Model (NIEM) to
achieve standard data exchange formats that are reusable for different agencies.
During the Gap Analysis MCSO indicated that it is their preference to minimize the impact to external
systems by integrating Workflow with the ICES Integration Engine (IIE) using the same message formats as
the legacy systems do today. MCSO indicated that NIEM would be desirable only for net new interfaces with
external agencies where the external partner supports NIEM. Such interfaces would also go through IIE.
Interfaces between Workflow and internal systems will not be required to use NIEM formats.
Java EJB — This component contains the predefined Workflow Services and Data Transfer Objects that are
part of the Workflow application.
EMI Interface Adaptor — This component is pre-built and contains the standard component libraries required
to connect to the Java Ms.
Routing and Transformation — This component provides the routing rules and technical transformations
required to exchange messages between the adaptors on each side of the ESB.
Service Interfaces - This component contains the custom Java code that will apply any required Business
Rules to the data, associated data mapping and any required data transformations required for each system to
consume the messages. Syscon proposes to develop as much reusable code as possible to speed up
development.
M Queue (System) Adaptor — This will be a common component that will act as a consumer or producer for
the MQueue messages. There will be multiple instances of this adapter, as it will be configured differently
based on the specific interface and/or external system requirement It will provide the connectivity to the
MCSO MQ Backbone.
Based on the use of the ESB and this set of pre-built adaptors for Workflow, our approach ensures that the
following requirements outlined in Exhibit B, Sub b; Non-Functional Technical Requirements are met:
Requirement Requirement IDs
Accessibility NF-AC-1,3, NF-AC-1,4
Note: Solution accessibility via kiosk devices and IVR will be facilitated through the
FSB. Only the specific kiosk and IVR interfaces identified in the Interface tab of
Attachment A have been included in our cost proposal
Auditability NF-AU-21, NF-AU-24.7, NF-AU-2.4.13, NF-AU-2.4.9, NF-AU-2.4,10, NF-AU-2.5,

SERIAL I3139-RFP
NF-AU-2.8, NF-AU-2.9,
Security NF-SE-73.1, NF-SE-73.2, NF-SE-7,3.3,
Data Requirements, Logical Data Groupings, NF-DR-10,1 .3
Data Retention, Data Structures And
Relationships, Data Conversion, Data
Dictionary
Design Constraints NF-DC-112, NE-DC-11.7, NE-DC-11.8,
Syscon shall provide the following approach and major tasks to analysis, design, development and testing of
the internal MCSO and external agency interfaces required for the new RAS implementation:
Task Description
_ .
Project Planning This task is the initiation step to finalize in detail the Interface development approach and
schedule. Output from this activity will be incorporated into the Project Management Plan.
Business Architecture This task supports the following work steps including:
Reviewing/Confirming Business Process Designs (Workflow Configuration/Orchestration)
and identifying how those may impact the interface design, in particular data mapping and
Creating the Interface Test Approach and Plan.
These steps identify the specific data exchanges required and the test strategy and plan for
Unit Testing, System Testing, Integration Testing and User Acceptance Testing.
Business Architecture Confirmed This milestone will ensure the business agrees with information to be exchanged.
Information Exchange Strategy This activity will incorporate several steps including:
Developing a High Level Data Exchange Model;
Confirming Legacy Interfaces to be incorporated Into Workflow, and
Documenting the Data Exchange Mapping and Detailed Processes.
These steps address the context view of all the data exchanges required to implement the
solution and a final confirmation of the interfaces to be built.
This work activity will also confirm the MQ Message Broker requirements including:
Availability, Security and Capacity; and
Network Requirements
A detailed Test Plan will also be created to support the testing requirements.
Develop Data Exchange Requirements This work activity will deliver the detailed data exchange mapping, designs and ESB
configuration/builds including:
Data field mapping between the Workflow and MCSO Internal/Legacy systems or
partner/external stakeholder systems;
Producing the Data Exchange Functional Configuration Specifications (error handling and
message content);
Transformation Business Rules;
Configuring the ESB/Data Transformation Tools;
Configuring the MQueue Adapter for each interface; and
Unit Testing the configured IESB/Data Exchange
Confirm Interface Requirements Have Been Met This milestone will ensure the business agrees with the documented and built interfaces.
Test Interfwes This work activity will:
Create Test Scripts;
Create Test Data,
Test the end-to-end Interfaces for Data Exchange; and
Conduct MCSO User Acceptance Testing

SERIAL 13139-RFP
Deploy to Production - Milestone This milestone will ensure the interfaces are deployed to the Production environment and
activated in concert with the overall Workflow deployment plan and approach,
10.6.2. Decommissioned Interfaces
Based on the Workflow product framework and the phased implementation approach defined, the following
Interfaces will be replaced by the integrated system (Note: Interface IDs denoted by an asterisk (*) will be
required to be deployed for the new-JMS in Phase I, and will be decommissioned in Phase 2 (i.e. they are
bridging interfaces required to support the phased implementation approach):
Interface 0 Interface/Data Exchange Systems Involved
JMS-14* Prebooking to 3MS (Same as Pre-12) Pre-book to SMS
JMS-185 Inmate into to IFCS - Release (same as IFCS-01) .IMS to IFCS
JMS-19* Inmate into to IFCS — Housing (same as IFCS-02) JMS to IFCS
JMS-20* Inmate into to IFCS - LEJIS number (same as IFCS-03) JMS to IFCS
JMS-21* JMS to IFCS ASP/ADOC transfer information (same as JMS to IFCS and IFCS to JMS
IFCS-04)
JMS-22 3MS to Inmate Programs - Programs Data JMS to Inmate Programs and Inmate
Programs to JMS
JMS-27 Operations Journal (Of) (Same as 0J-01) JMS to 0.1
.1MS-28* Court Operations (same as CT OP-01) JMS to Court Ups
JMS-29* Court Transportation (same as CT OP-02) JMS to Transportation
JMS-32 WIMP (Working Inmate Mgmt Program) (same as JMS to IFCS (WIMP)
IFCS-I 8)
JMS-33 WIMP (Working Inmate Mgrnt Program) (same as JivIS to IFCS (WIMP)
IFCS-19)
JMS-34 WIMP (Working Inmate Mgmt Program) (same as JMS to IFCS (WIMP)
IFCS-20)
JMS-35 WIMP (Working Inmate Mgmt Program) (same as NIS to IFCS (WIMP)
IFCS-2 I)
JMS-36 WIMP (Working Inmate Mgmt Program) (same as JMS to 1FCS (WIMP)
IFCS-22)
JIVIS-37 WIMP (Working Inmate Mgmt Program) (same as .IMS to IFCS (WIMP)
IFCS-23)
.1MS-38 WIMP (Working Inmate Mgmt Program) (same as JMS to IFCS (WIMP)
IFCS-24)
JIVIS-39 WIMP (Working Inmate Mgmt Program) (same as JMS to IFCS (WIMP)
IFCS-25)
Pre-I2* Prebooking to JMS (same as JMS-14) Prebook to JMS
IFCS-01* Inmate into to 1FCS - Release (same as IMS-18) JMS to IFCS
IFCS-02* Inmate into to IFCS — Housing (same as ,TMS-19) 1MS to IFCS
IFCS-03* Inmate into to IFCS LEJIS number (same as 3MS-20) JMS to IFCS
IFCS-04* JMS to IFCS ASP/ADOC transfer information (same as JMS to IFCS and IFCS to .IMS

SERIAL 13139-RFP
JMS-21)
1FCS-05 SAP Business One Accounting System (same as SAP- IFCS to SAP
1)
IFCS-06 SAP Business One Accounting System (same as SAP- SAP to IFCS
2)
IFCS-17 Touchpay Release Cards (Placeholder 3/3) IFCS to Touchpay
1FCS-18 WIMP (Working Inmate Mgmt Program) (same as IMS- IMS to IFCS (WIMP)
32)
WCS-19 WIMP (Working Inmate Mont Program) (same as JMS- JMS to IFCS (WIMP)
33)
IFCS-20 WIMP (Working Inmate Mgmt Program) (same as IMS- JMS to IFCS (WIMP)
34)
IFCS-21 WIMP (Working Inmate Mgmt Program) (same as JMS- JMS to IFCS (WIMP)
35)
IFCS-22 WIMP (Working Inmate Mgmt Program) (same as .IMS- IMS to IFCS (WIMP)
36)
IFCS-23 WIMP (Working Inmate 1VIgmt Program) (same as IMS- IMS to IFCS (WIMP)
37)
IFCS-247 WIMP (Working Inmate Mgmt Program) (same as IMS- .IMS to IFCS (WIMP)
38)
IFCS-25 WIMP (Working Inmate Mont Program) (same as JMS- IMS to IFCS (WIMP)
39)
0J-01 Operations Journal (OI) (Same as IMS-27) IMS to 01
CT OP-01* Court Operations (same as IMS-28) ,IMS to Court Ops
CT OP-02* Court Transportation (same as JNIS-29) IMS to Transportation
SAP-01 SAP Business One Accounting System (same as IFCS- IFCS to SAP
5)
SAP-02 SAP Business One Accounting System (same as 1FCS- SAP to IFCS
6)
Report Files
In APPENDIX 2, INTEGRATION/INTERFACES, MCSO has included a list of Report File Data Exchanges.
RPT-01 to RPT-35 from this list appear to be true reports and not interfaces with other systems. Syscon
believes that many of these reports will be satisfied by existing features in the Workflow product such as
product reports, query screens or orchestrations. For those reports that cannot be satisfied by existing product
features, custom reports can be developed using Oracle BI.
10.6.3. Interface Tools
Syscon will be using the following tools for interface Development:
Red Hat 3130 ss Enterprise Application Platform (EAP) v6
Red Hat JBo ss Fuse Service Works v6 Enterprise Service Bus (ESB)
To prepare MCSO technical staff to develop interfaces in the future, Syscon has developed the following
approach:
expose the EJB Services, Service APIs and Service Adaptors;

SERIAL 13139-RFP
The details of the specifications will be published;
Knowledge transfer in the form of integrating MCSO staff into the interface development team will be
provided; and
Additional interface development training is available for MCSO Staff from Red Hat directly for a fee, as
required. Refer to the Red Hat training website for more information:
http://www.redhat.com/en/servicesitraining.
10.7. Reporting and Query Development
10.7.1. Analysis of Existing Reports and Queries
Syscon has determined through a high-level analysis of the existing reports and queries that many of MCSO's
reporting requirements could in fact be met by other means already contemplated in the new solution (e.g. task
pooling, alerts/notifications, query screens, dashboards, orchestrations, or interfaces). For this reason, reporting
will be considered in the context of the overall solution and the reporting analysis undertaken during the
Configuration stage for each phase. This allows the MCSO project team resources time to understand how the
new application works and what options are available to satisfy the reporting requirements.
The vast majority of the reports and queries can be developed by MCSO technical staff after training from
Syscon. Syscon will develop up to 10 (ten) custom Workflow B1 reports as part of the system configuration
effort, and use these reports as examples to train MCSO on report development using Workflow's integrated
Oracle BI solution.
To facilitate this approach, Syscon project team members will work with MCSO to develop a consolidated
report and query inventory that will be maintained throughout the life of the project. This inventory will
include the following:
• Name and Description of the report
• Business area
• User Group required by
• Distribution needs (e.g. scheduled to printer, ad-hoe as needed, etc)
• Priority
• Phase of the project required for
• Product functionality satisfied by (if applicable)
• Team responsible for building (MCSO or Syscon)
10.7.2. Development and Testing of Reports
The Workflow architecture is designed to provide client agencies with the greatest possible flexibility for
creating new reports or modifying existing reports on their own without intervention from Syscon. The
technical architecture contains a data persistence layer in which captured inmate information is held within
Workflow data tables, as well as views (queries across data tables) which aggregate the data in useful
combinations. These views are the basis of report models within the business architecture, which are
constructed within the Workflow integrated reporting tool (Oracle BI Publisher) to assemble data elements in
pre-defined sets for reporting purposes. Report models are the intersection between Workflow data storage and
the integrated reporting tool.
The Syscon product development team maintains the standard set of Workflow report models to contain all
data elements necessary to support report selection, variables and output. Report models are updated with
every major release to reflect the enhanced functional capabilities of the system. The design of report content
and layout is conducted entirely within Oracle B1 Publisher. Initially, operational report design will be a
collaborative effort with Syscon and MCSO personnel, for training, but the intermediate goal is MCSO self-
sufficiency in the use of the integrated reporting tool, to create and modify reports against the report models
contained in the MCSO Workflow implementation. Syscon need be involved only if a report model does not
contain a data element required for a specific report.

SERIAL 13139-RFP
All Syscon-developed reports will be tested as part of Syscon's system testing activities, prior to delivery to
MCSO. Both Syscort and MCSO-developed reports will be validated by MCSO subject matter experts during
the end-to-end functional testing during the Validation stages of the project.
10.7.3. WorkflowJAIL Reporting Environment
The diagram below outlines the proposed architecture for the WorkflowJAIL reporting environment and the
process by which data will flow from the online application to the reporting environment. It also illustrates
how nightly snapshots will be created that MCSO can leverage for their statistical reporting needs without the
need for a full-fledge enterprise data warehouse with a multi-dimensional database.
A. The WorkflowJAIL application writes transactions directly to the WorkflowJAIL OLTP production
database.
B. The WorkflowJAIL reporting database can be configured by MCSO to be a near-real time copy of the
WorkflowJAIL OLTP production database. This can be achieved through the use of SQL Server's Log
Shipping feature which can send all database transactions to the reporting database asynchronously in near
real-time.
Using this approach, the WorkflowJAIL reporting database will be the primary source for Workflow BI reports
which will reduce the load on the OLTP application.
C. Syscon will develop a custom batch process that will create a "snapshot" of key inmate and booking
information. This process will be scheduled to run nightly at a pre-determined time. This process will be
similar to the "snapshot" that currently exists in MCSO's legacy environment. The snapshot data will be
stored in SQL server tables and added to nightly. The nightly snapshot will include the following
information:
Date of the Snapshot
Booking information (Booking Number, Booking Date, Booking Time)

SERIAL 13139-REP
Release information (Release Date, Release Time, Release Status)
Housing Information
Arrest information (multiple per booking)
Charge information (multiple per booking) including Charge Status and Arresting Agency
Sentence information (multiple per booking) including disposition
MCSO can leverage this nightly snapshot data for statistical reporting. The creation of statistical reports, the
Schroeder reports, or any additional data summarization required to support statistical reporting will be
MCSO's responsibility.
10.7.4. Report Writing and Query Tools
Workflow utilizes Oracle Business Intelligence (BI) Publisher as a reporting tool for product, ad-hoc and
statistical reporting. The Training Plan allocates time for Syscon resources to train MCSO technical staff to
develop reports and queries through familiarity with B1 Publisher functions, product report models and the
existing library of reports developed by Syscon business analysts.
MCSO may wish to use other business intelligence solutions with Workflow to create reports. Although they
are not currently integrated into the Workflow product, products such as Microsoft SQL Server Reporting
Services and Crystal Reports can be used to create additional reporting by accessing the Workflow database
views. Oracle B1 is a mandatory product component of Workflow at this time because of the tight integration
with Workflow's dashboards, onboard reporting, and screen reporting functionality, but other reporting
solutions can be used alongside it at the County's discretion.
10.7.5. Maintenance of Custom Reports and Queries
Syscon's product management aims to support the objective that most if not all custom reports and queries will
not be affected by system upgrades and patch releases under regular maintenance agreements.
The product specification includes report data models as part of system integration with Oracle B1 publisher.
These report models provide access from the report design tool to specific data elements from data storage
within Workflow services. Client-specific or ad-hoc reports, new or modified, that adhere to the product report
models should not be affected by system upgrades.
System modification to fully meet functional or reporting requirements of a specific client, for instance the
introduction of additional data elements, is not uncommon in our implementation experience. We typically
examine each client change request against our own market research to determine the likelihood that the
request may be applicable to other correctional agencies, and very frequently we find a business case justifying
the modification as a product enhancement, in which case any change to the report model(s) will be subject to
continuing product support.
10.8. Training Support
10.8.1. Description of Training
Syscon's training offering includes administrative, functional, and technical types of training sessions
delivered at key project milestones; including post go-live to ensure a successful transition of ownership of the
system from "project" status, to MCSO. Syscon has developed a training plan that incorporates a variety of
approaches and learning styles; from instructor-led, train-the-trainer to computer-based training. The training
approach for each training component in this proposal has been selected based on the amount of information
and content necessary to deliver as well as the size and scope of the audience to whom it is being delivered in
order to implement WorkflowJAIL (hereinafter referred to as Workflow) in the proposed schedule.
During the Define stage of the project, it is determined which administrative, functional, and technical sessions
should be delivered at each training delivery point in the project schedule. During this planning stage of the
project, decisions regarding the timing of the different training components will be made collaboratively in

SERIAL 13139-RFP
order to align the training schedule with MCSO's business transformation, reporting, and interface priorities, in
addition to the phases of the project.
Syscon will supply all syllabi and materials, as well as an evaluation tool for gauging the level of learning and
retention, for all participants in project training activities.
a. MCSO Project Core Team
Selection of a core project team of 45 participants aligns well with Syscon's training philosophy,
which favors the "train-the-trainer" approach for end user training. In Syscon's experience, the
most effective training arrangement is to select certain staff members as designated "key trainees"
who, after receiving training, are qualified to train remaining end users. These individuals can
serve as the first level of contact for the user community's trouble calls, are often effective and
engaged members of the organization's Change Network, and typically become the power users
of the system.
Syscon's training approach incorporates early system exposure for the core project team by
providing functional and technical overviews of the system through computer-based training
modules. Building on that introduction, Syscon project team members will provide in-depth
demonstrations of each module's functionality for the core project team during the project's
Define stage. Project team members will have access to Syscon's computer-based product
training material throughout the implementation project, and can access that training material to
develop in-depth knowledge of the system's functionality. Project team members will continue to
develop detailed understanding of the functionality through active participation in the
configuration of the Workflow solution during the Configure stage of the project.
Syscon's training approach integrates with organizational change management effort through
aligning the training material with business transformation activities to ensure that the T3 training
material is customized to deliver key change messaging as well as information about the system
functionality. Because of the iterative nature of Syscon's instructional design process, new
information can be incorporated as it is discovered through change management activities
throughout the Configure and Validate stages of the project.
MCSO's staff trainers will receive an in-depth, hands-on training session for each functional area
of the installed Workflow solution after the configured system is delivered, in preparation for the
Validate stage of the project. These train-the-trainer (T3) training sessions will arm trainers with
the system knowledge necessary to train your end-users. Each session will be offered to your
trainers and may also be attended by other members of the project core team. For instance, team
members who will be participating in user acceptance testing will benefit from participating in
some or all of these T3 training sessions. Syscon recommends that MCSO structure the project
team so that there is some overlap between staff members who will perform user acceptance
testing of the system during the Validate stage of the project and staff members who will deliver
the Go-Live training to end-users. This is to ensure that the trainers obtain the depth of
knowledge to appropriately address end-user concerns during go-live training, and acquire a
sense of ownership that facilitates effective participation in change management initiatives.
i. Technical Staff
Technical Staff will receive training related to interface development, report
development, system management and system administration tools. Please note
that Syscon's Workflow product is a COTS solution, and apart from interfaces
and configuration tasks such as business rules, business process re-
orchestration, and report development, software development activities on the
part of MCSO are not anticipated.
The desired skillsets for each of the technical roles that Syscon will train as part
of the technical training for the project are outlined below:

SERIAL 13139-RFP
Solid understanding of basic software development and deployment concepts
intermediate-level understanding of Java
Hands-on experience with and knowledge of Drools and Java Business
Process Management (ISPM)
Database Ailministrators
Experience installing, maintaining and administering the RDBMS (SQL
Database) on a Linux or Unix platform.
Experience with database back up and recovery
Experience with database performance tuning and optimization
Experience with Unix shell scripting
System Administrators
Experience installing, maintaining and administering enterprise or large-scale
software solutions.
Server system administration experience on a Unix or Linux platform
Experience installing, maintaining and administering application servers
such as WebLogic, Tomcat, Apache or JBoss.
Experience with Unix shell scripting
Interface Developers
Solid understanding of Web Services and SOA concepts
Experience developing ESB integration on an Enterprise Service Bus platform
Experience with Java EE dev elopment
Experience with JBoss ESB an asset
Repott Develoners
Intermediate-level understanding of SQL and report development tools
Basic understanding of XML
Proficiency with Microsoft Office Word and Excel
Hands on experience with Oracle BI Publisher
End Users
The 13 training approach provides end-users with instructor-led, hands-on training from
their peers, and the opportunity to give voice to any go-live concerns they have, in a
forum where those concerns can be swiftly addressed in a way that the answers can also
benefit other learners. Changes in user workflow can also be more easily explained
through this delivery model because the training material is structured in a role-based
format, ensuring that the specific training needs of the audience can be accommodated;
the facilitator will be a member of MCSO's staff and therefore innately knowledgeable
of the job functions performed by the training participants.
10.8.2. Training Plan
Syscon's training plan for the MCSO implementation project includes the following core training activities,
which will be planned collaboratively with MCSO project team members during the Define stage of the project:
Activity Name Description
Technical Overview This initial technical training session is focused on hardware installation and set-up infomtation that technical
staff members need to create the client-side project environments.
The functional overview training will provide the core project team with a preview of Workflow features
and the business processes the system supports. During these collaborative sessions, Syscon will work
Functional Overview with key stakeholders from various business units to identify how the system will be configured to MCSO
operations. This functional overview training will be reinforced for project team members through
completion of Sysoon's Worldlowproduct computer-based training modules.
System Administration Training topics include software installation, patch deployment, reporting, interfaces, business process
(Technical) orchestration, and business rules.

SERIAL I3139-RFP
System Administration Training topics include configuration of custom fields, user security, and configuration of the module-
(Functional) specific application firictionality.
Train " the Trainer training is delivered in a number of in-person, hands-on classroom sessions. The
training material that Syscon provides for training will be provided to MCSO to modify and maintain
Train-The-Trainer (T3) as required and can be re-used for subsequent staff training sessions by MCSO trainers. The training
material is provided in both MS Word and PDF file formats, and is role-based in order to ensure that
users get the right level of content for their role for each module in the Workflow solution. These
training sessions will be led by a qualified Syscon trainer who has mastered the course content,
Follow-up training is recommended in order to solidify MCSO staff members' understanding of the application
Follow-up Training functionality in a more global sense once the initial pressure of go-live has eased. This training involves an
in-depth look at the features and functionality of the Workflow system on a module by module basis
using a CBT approach.
1Vlentoring is delivered post go-live through a combination of job shadowing and workshops, where Syscon staff
Mentoring members review your organization's implementation of the Workflow solution, and thmugh scheduled
workshop sessions, help to answer questions that have arisen about the system.
These training offerings will be delivered through a combination of instructor-led training, workshops, and
computer-based training. These training delivery models are described below:
Delivery Model Description
Instructor Led Training Instructor-led training is facilitated by a Syscon trainer who is knowledgeable and experienced in the subject
matter and in the delivery of training to adult learners. Insttuctor-led sessions follow a detailed course
syllabus, and use a combination of lecture, demonstration, and hands-on exercises to embrace different
learning styles. .
Computer Based Training Computer-based training content is delivered in electronic format, and will be available to MCSO for each
Workflow functional area. Students engaged in computer-based training can proceed at their own pace
and can access training remotely. All necessary steps to administer CBT training can he performed
by MCSO staff members (e.g. creation of logins, password administration, and viewing of progress
and assessment results).
Workshop Workshops are facilitated by Syscon subject matter experts for small groups of participants, and focus on specific
areas of the overall Workflow solution. Workshops are an interactive learning environment where
participants accomplish a number of training activities according to a defined workshop agenda, These
sessions are less formal than instructor-led training, but the smaller class size and focused agenda mean that
participants receive an in- depth, hands-on learning experience.
The table below outlines the components of Syscon's training offering, the stage of the project at which the training
session(s) are meant to be offered, the intended audience, and the delivery method. Each training session will be
conducted at a location that is mutually agreed with MCSO in the project training plan.
Training Activities Delivery Method Intended Audience Project Stage
Functional Overview Computer Based All Learners Define (Core Project Team)
Validate (End Users)
Technical Overview Workshop Core Project Team Configure
Technology Bureau
Business Areas
System Administration Workshop Core Project Team Configure/Transition (exact timing for
(Technical) Technology Bureau each element tbd)
System Administration Workshop Core Project Team Configure
(Functional) Business Areas
Train the Trainer Instructor-Led 13 Trainers Configure
Cm-Live Training Instructor-Led End Users Validate
Follow-up Training Computer-Based End Users Transition
Mentoring Workshop Core Project Team Transition
Select End Users
Minimum hardware requirements for each training PC are as follows:
o OS — Windows 7+
o Main Memory - 2 gigabyte (GB) RAM (32-bit) or 2 GB RAM (64-bit)
o Hard Drive Capacity: 60 gigabyte (GB)

SERIAL 13I39-RFP
o CPU: 1.5 gigahertz (GHz) or faster 32-bit (x86) or 64-bit (x64) processor 1 x 1.5 GHz
Syscon will develop separate training plans for each major functional area, which must be presented to the MCSO
Project Manager, or designee for approval prior to class scheduling and commencement. It is anticipated that
training will be required for functional areas and user groups described in the chart below. During the project, the
Sheriff's Office may identify additional areas for which training may be required.
unction:Ai .I.reas to be Trained I so. G rotip(s) Est. 14
Trainees
Hardware Installation & Set-Up Technical Staff 3
Software & System Tools - Overview of baseline Project Team Core 45
products, including navigation, configuration, system Group
/module integration points, business process reengineering,
change management tools, etc.
System Administrators - All functions & tools Technical Staff 10
associated with the new JMS solution, including interface development
and query/report writing tools
System Administrators -Create profiles, add users, Business Areas 15
reset passwords, etc.
Basic Operational Skills.- LogonAogoff, menus, ALL USERS 4,000+
interface capabilities, edits, system queries, ad-hoc reporting, analysis
toots, dashboards, help features, and other basic functions for all
components of the solution
Document Management ALL USERS 4,000+
Business Rules All Jail Facility 1,500
Users
Workflows All Jail Facility 1,500
Users
Pre-Booking Arresting Officers, 4,000
All Jail Facility
Users
Inmate Scheduling All Jail Facility 2,000
Users, Correctional Health,
Court Users, Others?
Inmate Movements & Transportation All Jail Facility 1,800
Users, Court Security &
Transp., Medical Services,
others?
Intake Processing All Jail Facility 1,500
Users
Fingerprint Processing Records & AFIS 45
Property Tracking All Jail Facility 1,500
Users

SERIAL 13139-RFP
Visitation Processing All Jail Facility 1,500
Users
Release Processing All Jail Facility 1,500
Users
• Classification, Housing, & Gang Management Classification, Jail 40
Intel
Proxy Scoring Classification, 110
Inmate Programs, Jail
Stats
Administration of Inmate Programs Inmate Programs 75
Grievance Processing & Inmate Discipline All Jail Facility 1,500
Users, Hearing &
Grievances
Canteen — Order Processing & Inventory Canteen Operations 15
Inmate Funds Processing Financial Services 10
Court Case Processing SIMS 70
Special Management (Psych, SMI, Restrictions, Alerts, All Jail Facility 1,500
etc.) Users
New Employees — Major Detention Functions Detention Academy
Mobile Devices (new functionality) As Needed ?? (TBD)
Inmate Kiosks (new functionality) All Detention Users 1,500
Other Training (identified during implementation) TBD TED
10.8.3. Development of Training Materials
Syscon will create a training plan for the MCSO Workflow implementation project that includes a detailed
breakdown of the training planned for each user group and the functional areas in which each user group will
receive training. Syscon has discovered through over thirty years of industry experience that the most
effective way to deliver end-user training in preparation for go-live is in a role-based way, and that is reflected
both in the training plan template that we use as well as the training material. Syscon anticipates that the
training needs of the project will be carefully considered and planned during the initial project stages.
Training must be developed, provided, and/or presented by qualified instructors. Instructors shall ensure that
knowledge transfer occurs successfully, defined as follows:
Ninety-five percent (95%) of trainees meeting course prerequisites have a basic understanding of the
material covered and are capable of performing the various functions unassisted after the training session.
Proficiency and successful knowledge transfer shall be demonstrated by a score of 90% or higher on a
mutually agreed upon evaluation method, typically a multiple-choice test or examination, conducted after
completion of the training session.
10.9, Other Contractor Service Requirements
10.9.1. Technical Personnel Recommendations for MCSO
In order to support the Workflow application, Syscon recommends technical personnel be well versed in the
disciplines described in the following table.

SERIAL 131394BP
Role Training/Skill Set
General/ Ali IT Personnel
Windows or Linux operating system administration training, which would enable the
staff member to perform the following tasks:
Analyze system logs
Perform backups and recovery
Apply updates and configuration changes
Configure network infrastructure
Tune operating system performance
Add or update user account information
Respond to questions from the user base
Install and configure hardware
Database Administrator Advanced database administration training for SQL Server, which would enable the staff
member to perform the following tasks:
Install and upgrade database
Allocate / maintain database storage
Secure the database
Monitor and optimize database performance
Backup and recovery database
Archive data
Contact vendor database for support
Application Administrator .1BossaRE application configuration administration training, which would enable the staff
member to perform the following tasks;
Install, update, and maintain server
Apply application patches
Perform application server clustering
Secure application server deployment
Tune application performance
Report Administrator Oracle WebLogic and Business Intelligence Publisher administration training, which
would allow the staff member to perform the following tasks:
Install, update, and maintain the reports server
Apply report patches
Perform application server clustering
Secure application server deployment
10.9.2. Additional Vendor Services
Vendor Service Description
Scalability Monitoring Syscon provides monitoring of system performance and response times for the MCSO Workflow
implementation and integrated components
Installation Services Syscon installs all hardware, operating systems and software in addition to the Workflow
application.
Hardware Appliance Preinstalled copy of Syscon's software that can be added to a rack and supported by Syscon.
Backup & Recover Services Syscon provides a system backup and restores the solution for a given backup if needed
Disaster Recovery Service In case of disaster, Syscon provides a fail over solution in the cloud or on remote data site.
Performance Tuning Syscon monitors and tunes the solution, removing the need for third party tools or extra personnel.
Syscon monitors the performance of all tiers and tunes/ scales them as needed,
Business Intelligence and Analytics Offering Business Intelligence (31) consulting services.

SERIAL 13139-RFP
EXHIBIT C, WORKFLOWJAIL SOFTWARE LICENSE AGREEMENT
SERIAL 13139—RFP
INMATE MANAGEMENT SYSTEM
SOFTWARE LICENSE AGREEMENT
CONTRACT IDENTIFIER: NEW ,IMS SYSTEM SOLUTION
CONTRACT AGREEMENT NUMBER: 13139-RFP
This Software License Agreement made as of the 1St day of June, 2015.
BETWEEN
SYSCON JUSTICE SYSTEMS CANADA LTD.
6500 River Road, VI Floor
Richmond, BC
V6X 1X5
("Syscon")
AND
MARICOPA COUNTY
320 WEST LINCOLN
PHOENIX, ARIZONA
85003
("Client")
FOR GOOD AND VALUABLE CONSIDERATION, the receipt and sufficiency of which is hereby acknowledged,
Syscon and Client hereby agree as follows:

SERIAL 13139-RFP
SOFTWARE LICENSE AGREEMENT
1. SCOPE
1.1 This Software License Agreement applies to the Product modules (in object code form) known
commercially as the WorkflowJAIL inmate management system and any Enhancements or Custom
Modifications thereto, all as described in the License Details (defined below), together with related
documentation provided by Syscon (collectively, the "Licensed Software").
1.2 Any software other than the Licensed Software (as hereinafter defined) provided by Syscon to Client shall
be governed by separate license or sublicense agreement. Without limiting the generality of the foregoing,
the Licensed Software uses (a) RedHate Moss® Enterprise Application Platform which is provided under
the terms of the J13oss Enterprise Middleware End User License Agreement available from
http://www.redhat.corn/f/pdfflicenses/GLOBAL EULA RHEL English 20101110.pdf, (b) RedHat JBoss
Fuse which provided under the terms of the Red Hat Jboss Apache-Based End User License Agreement
available from http://www.redhat.conri/licensesiiboss apache eula.pdf, and (c) Oracle BI Publisher which
has been sublicensed by Syscon to Client on separate terms as set out in Exhibit D to the Master Services
Agreement.
1.3 Any and all services relating to the support and maintenance of the Licensed Software (referred to in the
Master Services Agreement as "Support") shall be governed by a separate client support agreement
between Client and Syscon or its nominee (the "Support Agreement").
1.4 All other services including (without limitation) configuration, modification, implementation, integration,
testing, consulting, management, acceptance testing, and training to be provided by Syscon to Client shall
be governed by a separate professional services agreement between Client and Syscon or its nominee, such
as the Master Services Agreement.
2. DEFINITIONS As used in this Agreement:
2.1 "Enterprise Use" means internal use of the Licensed Software by an unlimited number of concurrent users
consisting of the employees, agents and representatives of the Marieopa County Sheriff's Office (MCSO)
and agencies contracted by the Client for the purpose of actively and directly supervising Inmates for an
unlimited number of Records. For greater certainty,
(a) Enterprise Use does not permit use by any third party, or any departments or organizations of
Maricopa County other than the MCSO, or their employees, agents or representatives, unless they
have been contracted by Client for the purpose of actively and directly supervising Inmates, and
(b) Enterprise Use is unlimited as it relates to the number of concurrent users or the number of
Records, as contrasted against other types of licensing offered by Syscon for the Licensed
Software which may limit use of the Licensed Software to a maximum number of concurrent or
named users, or for a maximum number of Records
2.2 "Inmate" means an individual who is or was under the active or direct supervision of Client, or an agency
contracted by Client for such purpose as a result of a court order or other criminal justice process, whether
such individual was or is in custody, under community supervision or otherwise supervised for criminal
justice purposes;
2.3 "License Details" means the specific terms identified in Exhibit A to this License; and
2.4 "Licensed Software" has the meaning set out in Section 1 above.
2.5 "Master Services Agreement" means the agreement between Syscon and Client dated for reference June
I, 2015 for professional services relating to the provision of a jail management system under which this
Agreement is delivered.
2.6 "Phase Acceptance" means the acceptance by Client of an enumerated phase of the project being delivered
by Syscon pursuant to the terms of the Master Services Agreement in accordance with the acceptance
se,

SERIAL 13139-RFP
procedures set out therein, wherein it is expected that Syscon will deliver one or more modules of the
Licensed Software;
2.7 "Records" means the data or other records relating to Inmates;
2.8 "Support Agreement" has the meaning set out in Section 1.3 above.
3. GRANT OF LICENSE
3,1 License Grant. Subject to the terms and conditions of this Agreement, Syscon hereby grants to Client a
non-exclusive, non-transferable license of indefinite term to hold, install, access and use the Licensed Software, in
object code form only, for Enterprise Use only (and for greater certainty not for resale, re-license or other form of
distribution). This Agreement does not confer any right to Client to sublicense any of its rights to the Licensed
Software.
3.2 No Sale. The parties acknowledge and agree that nothing in this Agreement constitutes a sale of any
software owned or licensed by Syscon, and further that this Agreement does not convey to Client, or to any person,
any ownership right, interest or title in or to the Licensed Software, or to any intellectual property therein, and that
Client will not obtain any rights to any software (including the Licensed Software) other than those expressly set out
in this Agreement. Without limiting that, the Licensed Software qualifies as "commercial items," as that term is
defined at Federal Acquisition Regulation ("FAR") (48 C.F.R.) 2.101, consisting of "commercial computer
software and "commercial computer software documentation" as such terms are used in FAR 12.212. Consistent
with FAR 12.212 and DoD FAR Supp. 227.7202-1 through 227.7202-4, and notwithstanding any other FAR or
other contractual clause to the contrary in any agreement into which this Agreement may be incorporated, if Client is
a government end user, Client will acquire the Licensed Software with only those rights set forth in the Agreement.
Use of the Licensed Software agreement by Client that the Licensed Software is "commercial computer software"
and "commercial computer software documentation," and constitutes acceptance of the rights and restrictions herein.
If Client needs for rights not conveyed under the terms of this Agreement, it must negotiate with Syscon to
determine if there are acceptable terms for transferring such rights, and a mutually acceptable written addendum
specifically conveying such rights must be appended to this Agreement.
3.3 License Restrictions. At all times, Client will not, and will not permit any other party to, directly or
indirectly:
(a) make the Licensed Software or any portion thereof available to anyone other than Client and its
internal personnel for the purposes of Enterprise Use, nor license, sublicense, sell, resell, publish, republish,
transfer, assign, distribute, rent, lease, time-share, copy or otherwise commercially exploit the Licensed
Software in any way except as expressly permitted by this Agreement;
(b) without restricting any licenses granted under escrow release provisions pursuant to the Master
Services Agreement, alter, reverse engineer, disassemble, decompile, translate or otherwise attempt to
extract the source code or methodology from the Licensed Software or any part thereof;
(c) copy, transfer, display or use the Licensed Software or any portion thereof except as expressly
authorized in this Agreement, except that Client shall be entitled to make a reasonable number of copies of
the Licensed Software for archive and back-up purposes provided that Client (i) ensures that all such copies
include screen displays of Syscon's proprietary or intellectual property notices as recorded on the original
copy provided by Syscon, and (ii) affixes a label to each drive, stick, disc, diskette, tape or other housing
for the medium on which each copy is recorded that sets out the same proprietary or intellectual property
notices as appear on the Licensed Software;
(d) permit any other systems owned by or providing services to Client to write to the Licensed
Software database;
remove any copyright or other proprietary notices on or in the Licensed Software or any part
thereof (and, to the extent this Agreement permits Client to make copies of the Licensed Software, Client
shall reproduce such notices as they appear on the Licensed Software); or

SERIAL 13139-RFP
(0 store the physical media on which the Licensed Software is delivered or onto which archival
copies of the Licensed Software are permitted hereby other than in a locked, secure location, and will only
permit access thereto to those of Client's personnel who have been made aware of these limitations and
who are legally obligated to comply therewith.
3.4 Complete Software. Client agrees that its license hereunder is neither contingent on the delivery of any
future functionality or features nor dependent on any oral or written public comments made by Syscon regarding
future functionality or features of the Licensed Software except as may be otherwise set out in a separate written
agreement between the parties. To the extent, pursuant to the Support Agreement, Syscon delivers any
enhancements or modifications to the Licensed Software, the same will form part of the Licensed Software for all
purposes.
4. CHARGES AND PAYMENTS
4.1 License Fees, Taxes and Payments. The Master Services Agreement fully sets out the terms of payment
for the license granted hereunder.
4.2 Reports and Auditing. At all times during the course of this Agreement and for a period of three years
thereafter, (a) Client will keep accurate records with respect to the usage of the Licensed Software so as to
enable verification that the Enterprise Use and restrictions set out in this Agreement have been complied
with, and (b) Client will make available such records to Syscon (or its advisors) upon its request from time
to time in order to verify compliance with this Agreement, provided that if any such records contain
confidential information Client may require that the auditing party or its advisors execute a commercially-
reasonable non-disclosure agreement with respect thereto. If such audit reveals non-compliance with the
terms of this Agreement, Syscon will invoice, and Client will immediately pay, for such unlicensed use in
accordance with Syscon's then-current pricing, without otherwise limiting or restricting Syscon's rights and
remedies at under this Agreement, the Support Agreement, the Master Services Agreement, at law or in
equity.
5. IP; CONFIDENTIALITY
5.1 Warranty of Title. Syscon warrants that it has all rights necessary to make the grant of license herein by
having all right, title and interest in and to the Licensed Software or as licensee of all such necessary rights from the
owner thereof.
5.2 Retention of Rights by Syscon. All proprietary and intellectual property rights, titles and interests
including copyright in and to the original and copies of the Licensed Software shall be and remain that of Syscon or
its licensors (as the case may be). Client has no proprietary or intellectual property rights, titles or interests in or to
the Licensed Software, or any portion thereof, except for the limited license granted herein and Client shall not, at
any time, whether before or after the termination of this Agreement, contest or aid others in contesting, or doing
anything which otherwise impairs the validity of any proprietary or intellectual property rights, titles or interests of
Syscon or its licensors in and to the Licensed Software or any portion thereof.
5.3 Confidentiality. Client acknowledges and agrees that some aspects of the Licensed Software, its
documentation and its database schema, tables and organization represent the Confidential Information of Syscon,
and will be governed by the provisions of the Master Service Agreement relating to the protection of Syscon's
Confidential Information at all times.
6. LIMITED WARRANTY AND LIMITATION OF LIABILITY
6.1 Limited Warranty of the Licensed Software — Syscon warrants that, for a period of forty-five (45) days
from the date of Phase Acceptance by Client (unless extended for an additional forty-five (45) days through mutual
consent of the parties), the Licensed Software being accepted as part of such Phase Acceptance shall conform, as to
all substantial operational features, to Syscon's current published specifications when installed and be free from
defects that substantially affect system performance. Syscon's sole obligation and liability hereunder shall be to use
reasonable efforts to remedy any such functional non-conformance which is reported to Syscon in writing by Client
within this Warranty Period for such particular Phase Acceptance. If Syscon is unable to remedy such non-
conformance using reasonable efforts, Syscon shall be entitled to, in its sole discretion, refund to Client the license
fees paid by Client to Syscon under the terms of the Master Services Agreement for the elements of the Licensed

SERIAL 13139-RFT
Software that are the subject of such Phase Acceptance and this Agreement shall automatically be terminated as it
relates to such Licensed Software, but for greater certainty (a) other Licensed Software that were not the subject of
such Phase Acceptance shall not be affected and (b) such termination shall not affect any rights or remedies
available to Client under the terms of the Master Services Agreement or the Support Agreement.
6.2 SPECIFIC EXCLUSION OF OTHER WARRANTIES — EXCEPT AS SET OUT IN SECTIONS 5.1 AND
6.1, THE LICENSED SOFTWARE IS PROVIDED "AS-IS" AND SUCH REPRESENTATIONS AND
WARRANTIES ARE IN LIEU OF ALL OTHER WARRANTIES AND CONDITIONS, AND THERE ARE NO
OTHER WARRANTIES, REPRESENTATIONS, CONDITIONS, OR GUARANTEES OF ANY KIND
WHATSOEVER, EITHER EXPRESS OR IMPLIED BY LAW (IN CONTRACT OR TORT) OR CUSTOM,
INCLUDING, BUT NOT LIMITED TO THOSE REGARDING MERCHANTABILITY, FITNESS FOR
PURPOSE, CORRESPONDENCE TO SAMPLE, TITLE, DESIGN, CONDITION, OR QUALITY, NOR ARE
ANY WARRANTIES GRANTED BY SYSCON'S LICENSORS. wrmour LIMITING THE ABOVE,
SYSCON AND IT'S LICENSORS DO NOT WARRANT THAT THE OPERATION OF THE LICENSED
SOFTWARE SHALL BE FREE FROM INTERRUPTION OR ERRORS WHICH DO NOT ADVERSELY
IMPACT THE PRODUCT'S WRITTEN WARRANTED FUNCTIONALITY.
63 RESTRICTIONS ON WARRANTY - SYSCON SHALL HAVE NO OBLIGATION TO REPAIR OR
REPLACE THE PRODUCT (A) DAMAGED BY ACCIDENT (OTHER THAN SYSCON) OR OTHER
EXTERNAL CAUSE; (B) DAMAGED THROUGH THE FAULT OR NEGLIGENCE OF ANY PARTY OTHER
THAN SYSCON; (C) USED IN OTHER THAN ITS NORMAL AND CUSTOMARY MANNER; (D)
SUBJECTED TO MISUSE; (E) SUBJECTED TO MODIFICATIONS BY THE CLIENT OR BY ANY PARTY
OTHER THAN SYSCON WITHOUT THE PRIOR WRITTEN CONSENT OF SYSCON; OR (F) USED IN A
HARDWARE, OPERATING SYSTEM AND SOFTWARE ENVIRONMENT NOT MEETING THE
REQUIREMENTS OF THE LICENSED SOFTWARE AS SET OUT IN THE DOCUMENTATION THEREFOR
OR THAT HAS NOT BEEN CORRECTLY INSTALLED, PROCURED, CONFIGURED, SUPPORTED,
LICENSED AND MAINTAINED.
6.4 NO INDIRECT DAMAGES - IN NO EVENT SHALL SYSCON OR ITS LICENSORS BE LIABLE TO
CLIENT OR TO ANY OTHER PARTY FOR INDIRECT, INCIDENTAL, CONSEQUENTIAL, SPECIAL OR
PUNITIVE DAMAGES OR LOSSES (WHETHER ARISING IN CONTRACT, IN TORT OR OTHERWISE) IN
CONNECTION WITH THE LICENSE OF THE LICENSED SOFTWARE OR THIS AGREEMENT, NOR
(WITHOUT LIMITING THE GENERALITY OF THE FOREGOING) FOR DAMAGES FOR LOST PROFITS,
LOST SAVINGS, LOSS OF OR CORROUPTION OF DATA, LOSS OF CONTRACTS, OR LOSS OF
OPERATION TIME, IN EACH CASE EVEN IF CAUSED BY SYSCON'S NEGLIGENCE AND EVEN IF
SYSCON HAS KNOWLEDGE OF THE POSSIBILITY OF SUCH POTENTIAL LOSS OR DAMAGE.
6.5 LIMITS ON LIABILITY - IF FOR ANY REASON, SYSCON OR ITS LICENSORS BECOME LIABLE
TO CLIENT OR ANY OTHER PARTY FOR DIRECT OR ANY OTHER DAMAGES FOR ANY CAUSE
WHATSOEVER, AND REGARDLESS OF THE FORM OF ACTION, INCURRED IN CONNECTION WITH
THIS AGREEMENT OR THE LICENSE OF THE LICENSED SOFTWARE, THEN (A) THE AGGREGATE
LIABILITY OF SYSCON AND ITS LICENSORS FOR ALL DAMAGES, INJURY, AND LIABILITY
INCURRED BY CLIENT AND ALL OTHER PARTIES IN CONNECTION WITH THE PRODUCT, SHALL BE
LIMITED TO AN AMOUNT EQUAL TO THE CHARGES AND FEES PAID AS LICENSE FEES TO SYSCON
UNDER EXHIBT A OF THE MASTER SERVICES AGREEMENT FOR DAMAGES; AND (B) CLIENT MAY
NOT BRING OR INITIATE ANY ACT OR PROCEEDING AGAINST SYSCON OR ITS LICENSOR ARISING
OUT OF THIS AGREEMENT OR RELATING TO THE LICENSED SOFTWARE MORE THAN TWO YEARS
AFTER THE CAUSE OF ACTION HAS ARISEN.
6.6 SEPARATE ENFORCEABILITY - SECTIONS 6.2, 6.3, 6.4 AND 6.5 ARE TO BE CONSTRUED AS
SEPARATE PROVISIONS AND SHALL EACH BE INDIVIDUALLY ENFORCEABLE.
7. TERMINATION
7.1 Termination - This Agreement and the license granted hereby shall terminate in each of the following
events;
(a) at the option of either party if the other party becomes insolvent or bankrupt or makes an
assignment for the benefit of creditors, or if a receiver or trustee in bankruptcy is appointed for the other

SERIAL 13139-RFP
party, or if any proceeding in bankruptcy, receivership, or liquidation is instituted against the other party
and is not dismissed within 30 days following commencement thereof; or
(b) at the option of either party if the other party materially defaults in the performance or observance
of any of its obligations hereunder and fails to remedy the default within 30 days after receiving written
demand therefor;
(c) notwithstanding (b), immediately upon Syscon's notice to Client if Client breaches sections 3.3,
5.2 or 5.3 hereof; or
(d) without limiting (b), if payment of any applicable license fee pursuant to the terms of the Master
Services Agreement is not made when due, provided that Syscon has first given Client not less than thirty
(30) days written notice of its intention to rely on this clause, which notice may not be given with respect of
any particular invoice for license fees until thirty (30) days following the due date of the particular invoice;
provided that this right of termination shall be in addition to all other rights and remedies available to the parties for
default or wrong-doing by the other.
7.2 Suspension of Obligations — Notwithstanding Section 7.1, if Client should default in the performance or
observance of any of its obligations hereunder, then, in addition to all other rights and remedies available to Syseon,
Syscon may suspend performance and observance of any or all of its obligations under this Agreement, without
liability, until Client's default is remedied.
73 Return of the Licensed Software — Without limiting Section 7.1 of the Master Services Agreement, this
Agreement is terminated by either party, Client shall immediately return to Syseon the Licensed Software and all
copies thereof and certify, in writing, to Syscon that Client has done so and complied with Section 5.3.
8. GENERAL
8.1 Complete Agreement. This Agreement, including the Appendices hereto, constitutes the complete and
exclusive statement of the agreement between Syscon and the Client with respect to the license of the Licensed
Software supersedes all oral or written proposals, prior agreements and other prior communications between the
parties relating thereto. In the event of a conflict between the terms of this Agreement and the Appendices hereto,
the terms of this Agreement shall prevail. The parties acknowledge that they shall have entered into other
agreements concurrently herewith.
8.2 Notices. All notices and requests in connection with this Agreement shall be delivered to the respective
parties in writing and shall be deemed to he given on the day following the day such notice is delivered to the
receiving party at the address set out for notice from time to time pursuant to the terms of the Master Services
Agreement (or, if the Master Services Agreement has expired sooner, the Support Agreement).
8.3 Governing Law. This Agreement and performance hereunder shall be governed by the law of the
jurisdiction selected in the Master Services Agreement.
8.4 Severability. If any provision of this Agreement shall be held to be invalid, illegal or unenforceable under
any applicable statute or rule of law, the validity, legality and enforceability of the remaining provisions shall in no
way be affected or impaired thereby.
8.5 Non-Assignment. Client may not assign its rights, duties or obligations under this Agreement, without the
prior written consent of Syscon. Without limiting that, Client's obligation to pay any fees or charges due hereunder
is not assignable.
8.6 Non-Waiver. The waiver or failure of either party to exercise, in any respect, any right provided for herein
shall not be deemed a waiver of any further right hereunder.
8.7 Relationship. The parties acknowledge that each is an independent contractor in a licensor-licensee
relationship and nothing herein constitutes a joint venture, partnership, agency or other relationship between the
parties and neither party has the right to bind nor act for the other as agent or in any other capacity.

SERIAL 13139-RFP
8,8 Enurement. All covenants, representations, warranties and agreements of the parties contained herein
shall be binding upon and shall enure to the benefit of the parties and their respective successors and permitted
assigns.
8.9 Survival. Sections 1,2, 3.2, 3.3, 3.4, 4.2, 5.2, 5.3, 6.2,6.3, 6.4, 6.5, 6.6, 7.3 and 8 shall survive termination
and expiration of this Agreement.
8.10 Export Control. The Licensed Software uses software and technology that may be subject to export
controls under applicable laws. Client acknowledges and agrees that the Licensed Software shall not be transferred
or otherwise exported or re-exported, except in accordance with all applicable laws regarding the export of
controlled technologies.
8.11 Interlocutory Remedy. Each party acknowledges that irreparable harm to the other party not compensable
by monetary damages would result from its breach of any obligations under Sections 3 and 5. Accordingly, each
party agrees that remedies for any such breach may include, in addition to other available remedies and damages,
injunctive or other equitable relief from any court of appropriate jurisdiction as a matter of right and without the
necessity of establishing the inadequacy of monetary damages. No party will raise the adequacy of monetary
damages as a defence to any such application for such injunctive relief.
8.12 Acceptance and Counterparts. This Agreement may be executed in counterparts (including by electronic
transmission), each of which will constitute an original and all of which taken together will constitute one and the
same instrument.

SERIAL 13139-RFP
SCHEDULE A
LICENSE DETAILS
Description of Licensed Software (sections 1.1, 3.1): Syscon's Inmate management system with the
following modules:
PHASE 1:
Product modules:
Admission / Transfer! Release Assessment & Classification Billing of Services
Case Management / Re-Entry Counts Court Orders & Legal Documents
Discipline Event Log (Shift / Case Notes) Housing Bed Management
Inmate Correspondence Inmate Property Movements (Court Operations)
Requests and Grievances Security Threat Groups Sentence Accounting
Visits Diets 1 (Limited Functionality) Programs
Custom Modifications/Interfaces:
Court! ICIS Systems Inmate Telephone System Jolts
Justware Livescan Magellan-Mercy Maricopa
Naphcare HER PHRED Video Visitation (SECURUS))
Coplink Mugshot Justice Web Interface (JWI)
IA Pro Offender Based Tracking System IFCS (Bridging Interfaces)
(OBIS)
Pre-Book (Bridging Interfaces) Court Operations (Bridging Interfaces)
PHASE 2A:
Product modules:
Trust Accounting Commissary
Health / Diets 2 Facility Issue (Inmate Property)
Custom modifications/Interfaces:
Touchpay Phase 2a: Data Migration
PHASE 2b:
Product modules:
PreBook Court-Operation&
Transportation Victims Services
Custom Modifications/Interfaces:
External Records Management MCSO Records Management ICIS Superior Court
_ Systems System
Phoenix PD Common Case Number 2-Finger ID
HER-CHS Techcare

SERIAL 13139-RFP
EXHIBIT D - ORACLE SUB-LICENSE AGREEMENT
ORACLE® SUB-LICENSE AGREEMENT
THIS AGREEMENT is made as of the 1st day of June 2015 between Maricopa County (the "Client") and SYSCON
JUSTICE SYSTEMS CANADA LTD. having an office at 6500 River Road, 2nd Floor, Richmond, BC V6X 1X5
("Syscon").
WHEREAS:
A. Oracle Corporation has granted Syscon the right to distribute certain software owned or licensed by Oracle
to end users as part of an application package consisting of the Oracle software coupled with Syscon's software on
the prescribed terms set out in this Agreement;
B. The Client wishes to acquire a license to use the Oracle Programs to be used in conjunction with the Syscon
Programs.
NOW THEREFORE, in consideration of the foregoing and of other good and valuable consideration, the receipt and
sufficiency of which is hereby acknowledged, the parties agree as follows:
1. DEFINITIONS AND EXHIBITS
1.1 Defined Terms Terms defined in the OMS Agreement have the meaning assigned to them in the OMS
Agreement.
L2 Additional Definitions In this Agreement, the following terms have the meaning assigned to them as
follows:
(a) "Agreement Details" means the specific terms identified in Exhibit A to this Agreement;
(b) "OMS Agreement" means the agreement between the Client and Syscon more particularly described in the
Agreement Details as it may be amended from time to time;
(c) "Oracle" means Oracle Corporation or its subsidiaries, affiliates or licensors, as the case may be;
(d) "Oracle Programs" means the computer software described in the Agreement Details, including
documentation;
(e) "Syscon Programs" means Product licensed or to be licensed to the Client pursuant the OMS Agreement,
1.3 Exhibits The following exhibits, as they may be amended from time to time, form part of and are
incorporated into this Agreement by reference:
(Y-

SERIAL I3139-RFP
Exhibit Description
A Agreement Details
2. LICENSE
2,1. License Syscon hereby grants to the Client a non-transferable and non-exclusive right and license to use
the Oracle Programs in object code form only and only in conjunction with the Syscon Programs for the Client's
internal business operations.
2.2 Restrictions on License Nothing in this Agreement permits the Client to:
assign, give or transfer any of its rights in the Oracle Programs, or any partial interest, to any third party;
(ii) use the Oracle Programs for rental, timesharing, subscription services, hosting or outsourcing;
(iii) remove or modify any program markings or any notice of Oracle's proprietary rights; or
(iv) publish the results of any benchmark tests run on the Oracle Programs,
2.3 No Reverse Engineering The Client will not reverse engineer, disassemble or decompile the Oracle
Programs (or any portion thereof) or develop derivative works thereof and will not copy (except for archival and
backup purposes), transfer, display or use the Oracle Programs except as expressly authorized in this Agreement.
2.4 Additional License Terms Additional license terms relating to the Oracle Programs or any third party
technology appropriate or necessary for use with the Oracle Programs may be specified in the documentation
accompanying the Oracle Programs.
2.5 Ownership of Oracle Programs All proprietary and intellectual rights, title and interest including copyright
in the original and all copies of the Oracle Programs and the documentation and any changes or modifications to the
programs shall be and remain that of Oracle. The Client has no proprietary or intellectual property rights, title or
interest in or to the Oracle Programs, or any portion thereof, except as granted herein. All designs, structure,
schema, code or other aspects of the Oracle Programs are proprietary and confidential to Oracle.
2.6 Ceasing Use In the event of this Agreement expiring or terminating, the Client will discontinue the use of
the Oracle Programs and will destroy or return to Syscon all copies of the Oracle Programs.
3. DISCLAIMER AND LIMITATION OF' LIABILITY
3.1 Limits on Replacement Syscon shall have no obligation to repair or replace the Oracle Programs if:
damaged by accident other than by Syscon of other external cause;
damaged through the fault or negligence of any party other than Syscon;
used in other than its normal and customary manner;
subjected to misuse; or
subjected to modifications by the customer or by any party other than Syseon without the prior written
consent of Syseon or Oracle.
3.2 Disclaimer TO THE EXTENT PERMITTED BY LAW, NEITHER SYSCON NOR ORACLE WILL BE
LIABLE TO THE CLIENT OR TO ANY OTHER PARTY FOR DAMAGES, WHETHER DIRECT OR
INDIRECT, INCIDENTAL, SPECIAL, PUNITIVE OR CONSEQUENTIAL OR FOR ANY LOSS OF PROFITS,
REVENUE, DATA OR DATA USE ARISING FROM THE USE OF THE ORACLE PROGRAMS.
3.3 Limit of Liability If, for any reason, Syscon or Oracle becomes liable to the Client or to any other party
for damages, regardless of the form of action, incurred in connection with this Agreement or the use of the Oracle
Programs, then the aggregate liability of Syscon and Oracle shall be limited to the fees and other charges, if any,
paid to Syscon for the Oracle Programs which gave rise to the claim for damages.
GENERAL TERMS
4.1 Effective Date This Agreement will come into effect upon when signed by both parties and a fully signed
copy has been delivered to Syscon
ge_

SERIAL 13 I39-RFP
4.2 Complete Agreement This Agreement and the OMS Agreement constitute the complete and exclusive
statement of the agreement between Syscon and the Client with respect to the Oracle Programs and supersedes all
oral or written proposals, prior agreements and other prior communications between the parties.
4.3 Third Party Beneficiary The Client hereby acknowledges and agrees that Oracle is a third party
beneficiary of this agreement and the provisions of this agreement are made expressly for the benefit of Oracle in
addition to Syscon.
4.4 Audit Rights At all times during the course of this Agreement and for a period of three years thereafter,
(a) Client will keep accurate records with respect to the usage of the Oracle Programs so as to enable verification
that the License Details and restrictions set out in this Agreement have been complied with, and (b) Client will make
available such records to the other party (or its advisors) upon its request from time to time in order to verify
compliance with this Agreement, provided that if any such records contain confidential information Client may
require that the auditing party or its advisors execute a commercially-reasonable non-disclosure
agreement with respect thereto.
4.5 Survival Sections 2.2 to 2.6, inclusive, shall survive the termination or expiry of this Agreement.

SERIAL 13139-RFP
SCHEDULE A
Agreement Details
1. Description of the Client: Maricopa County, a political subdivision of the State of Arizona, 320
W Lincoln, Phoenix, AZ 85003
2. Description of the OMS Agreement (sub-section 1.2(a)) :Master Services Agreement (Serial
13139-RFP) dated for reference June 1, 2015.
3. Description of the Oracle Programs (sub-section 1.2 (d)):
DESCRIPTION QTY/CPU 1 TERM2 LICENSE TYPE 3
BI Publisher 8 perpetual CPU/cores
Annual ESL Sublicense Supporet: Annual (Included in Exhibit A)
Notes:
1. The Oracle Programs are licensed according to the number of Intel-based cores.
2. The term of the license is subject to the provisions for termination set out in this Agreement.
3. This sublicense is an Embedded Software License ("ESL"), which refers to the restricted type of license
whereby the Oracle Programs may only be used in conjunction with the Syseon Programs and cannot be
modified by the Client or used with any third party application.
4. Annual technical support services for ESL sublicenses are provided by Syscon.

SERIAL 13139-RI}'
EXHIBIT E — CLIENT SUPPORT AGREEMENT
SERIAL 13139—RFT
SYSCON JUSTICE SYSTEMS
CLIENT SUPPORT AGREEMENT
CONTRACT IDENTIFIER: NEW .TMS System Solution
CONTRACT AGREEMENT NUMBER; I3139-RFP
This Agreement made the 20th day of May, 2015 but made effective as of June I, 2015 (the "Effective Date")
BETWEEN
SYSCON JUSTICE SYSTEMS
6500 River Road
Richmond, B.C.
V6X 1X5
("Syscon")
AND
MARICOPA COUNTY
320 West Lincoln
Phoenix, AZ
85003
(the "Client")
WHEREAS
A. The Client and Syscon entered into a Master Services Agreement pursuant to which Client and Syscon agreed
that Syscon would provide Support as defined therein (and capitalized terms not defined herein will have the
meaning set out in such Master Services Agreement); and
B. Client wishes to have Syscon provide Support pursuant to the terms and conditions of this Agreement.
NOW THEREFORE, In consideration of the mutual covenants contained herein, the parties agree as
follows:
1.0 SERVICES
1.1 Syscon shall provide Support to the Client by telephone, e-mail, Web portal (as appropriate)
during the times as recited in Schedule B.

SERIAL I3139-RFP
1.2 In the provision of Support, Syscon shall adhere to the following response standards:
PiIi0 i.i.tV:(0r,:g0641:
........
Lk? ..„. . ... t ciMiidititill" t W
P1 P1 P.2
Initial Response Within 30 Minutes Initial Response: Within 30 minutes initial Response Within 2 business
Response Type: Phone Response Type: Phone hours
Resolution Within 24 hours Resolution: Within 24 hours' Response Type Phone
.ta. Work effort: 24 x 7 Work effort 24 x 7 Resolution Within 5 days'
Update Interval: Every 2 hours Update Interval: Every 2 hours Work effort: 12 hours/day, Mon - Fri
Update Interval Weekly
P1 P2 P7
Initial Response: Within 30 Minutes tnitial Response: Withui 2 business Initial Response Within 2 business
Response Type: Phone hours hours
Resolution: Within 24 hours* Response Type Phone Response Type Phone
Work effort 24 x 7 Resolution: Within 5 days* Resolution Within 5 days"
Update Interval Every 2 hours Work effort 12 houts/day, Mon - Fri Work effort 12 hours/day, Mon - Fri
D.
Update Interval: Daily Update Interval: Daily
P2 P4 P4
Initial Response Within 2 business loitlal Response Within 4 business Initial Response: Within 8 business Initial Response: Within 8 business
hours hours hours hours
Response Type Phone Rasponre Type Email / Phone Response Type: Email / Phone Response Type: Email / Phone
Resolution Within 5 days* Resolution: Within 30 days* Resolution Reasonable effort to Resolution: Reasonable effort to
Work effort 12 hours/day, Mon - Fri Work effort 8 hours/day, Mon - Fri resolve in next release resolve in next release'
Update Interval: Daily Update Interval: Weekly Work effort 8 hours/day, Moo - Fri Work effort: 8 hours/day, Mon - Fri
Update Interval: On demand Update Interval: On demand
P4 P4
Initial Response Within 4 business Initial Response: Within 4 buseless Initial Response With 8 business Initial Response Within 8 business
ours hours hours hours
Response Type: Email / Phone Response Type Email / Phone Response Type: Email / Phone Response Type Email/ Phone
Resolution Within 30 days* Resolution: Within 30 days' Resolution r Reasonable effort to Resolution: Reeser -table effort to
Work effort 8 hours/day, Mon - Fri Work effort: 8 hours/day, Mon - Fri resolve in next release reselvo in next release.
Update Interval: Weekly Update Interval Weekly Work effort 8 hours/day, Man - Fri Work effort: 8 hours/day, Mon - Fri
Update Interval On demand Update Interval On demand
-
*Note: Time to resolution is time to resolving the defect or wont:dying an acceptable workaround while the Application release is created.
1.3 Unless otherwise specifically provided in Schedule A and/or B hereof, support services provided
under this Agreement are limited to Support of the Application Package Programs (as defined in
Master Services Agreement, Section 7.1) to the exclusion of any other third party software
Systems.
1.4 Syscon shall endeavour to assist with all inquiries made to Support personnel. However, if the
inquiry is not related to a problem with the Application Package Programs, Syscon shall be
entitled to charge the Client on a time and materials basis at the rates set forth in Schedule B
(hereinafter "T&M"). In the case that the solution to the said inquiry made to Support personnel
requires T&M, Support will close the ease and advise MCSO. These additional services and
charges must be authorized (in advance) by the appropriate Client representative having authority
to approve additional expenditures under this Agreement. The names and titles of such authorized
parties are listed in Schedule B.
2.0 COMPENSATION
2.1 For the Support services provided pursuant to this Agreement, the Client shall pay Syscon the fees
specified in Exhibit A . For all other services (including, but not limited to, support related to
Database recovery, remedy to failures due to operator errors, Professional Services) to the Client,
Syscon shall charge the Client on a fixed price or T&M basis. These additional services and
charges must be authorized (in advance) by the appropriate Client representative having authority

SERIAL 13139-RFP
to approve additional expenditures under this Agreement. The names and titles of such authorized
parties are listed in Schedule B.
2.2 In the event that the Client is in breach of its covenants contained in Article 3 and, as a result,
additional services are rendered by Syscon to the Customer, Syscon shall charge the Client for
such services on a T&M basis.
2.3 Syscon shall invoice the Client for the Fees annually in advance. Any expenses referred to in
Section 3.3 shall be invoiced monthly. All such invoices shall be payable within 30 days of the
date of each such invoice.
3.0 CLIENT RESPONSIBILITIES
3.1 Without cost to Syscon, the Client shall provide to Syscon full co-operation and assistance to
enable Syscon to provide the Support contemplated hereby. In particular, and without limiting the
generality of the foregoing, the Client shall:
3.1.1 establish and maintain an internal support desk whereby all end user reported defects in
the Application Package Programs would be first diagnosed and confirmed as bona fide
defects before logging a support call with Syscon. All Support calls must be channelled
through certain individuals designated by the Client. The designated individual(s) are set
out in Schedule B;
3.1.2 provide and maintain, at all times, a separate, functional Delivery Platform (whereby all
software deliverables provided by Syseon to Client shall be validated and tested) and,
subject to Client procedures and requirements established to maintain security, grant
Syscon access thereto;
3.1.3 perform any and all Database administrative duties as may be required for the continuing
operation, speed and optimal performance of the Product that includes, without
limitation, backup and recovery, monitoring table space and disk usage levels;
3.1.4 supply all pertinent data and information (including Database dumps, as requested);
3.1.5 make available such employees of the Client as Syscon may reasonably request;
3.1.6 report problems or faults within such time, on such forms and with such degrees of
particularity as Syscon may, from time to time, request.;
3.1.7 in the event of an emergency or crisis, and at the specific request of the Client, provide
Syscon with electronic or other access to the Production System for purposes of applying
a Database or data corruption fix on the understanding that, except for wilful negligence
on the part of Syscon, Syscon assumes joint liability resulting from such emergency or
crisis access.
3.1.8 ensure that its personnel are fully trained in the use and operation of the Product or any
Custom Modifications; and
3.1.9 use the Product in accordance with the procedures for the use of the Product in the
manner and for the purpose of which it was originally intended by Syscon as reflected in
its design and having regard to the business practices of Client, both of which are
established in system administration training provided by Syscon under the Master
Services Agreement.
3.2 Client understands and agrees that all Defect corrections, Major Releases and Maintenance
Releases (and any related Database scripts) should be promptly implemented in the Production
System. The Client acknowledges that its failure to so implement such Defect corrections, Major
or Maintenance Releases may render the Product unusable or non-conforming to Documentation.
The Client agrees to install and put into production use (a) corrections to Client specific Defects
within thirty (30) days of delivery by Syscon and, (b) Major Releases and Maintenance Releases
within such reasonable time as Syscon may specify. Failure by the Client to install and put into
production use (or request Syscon to do so on a T&M basis) all such corrections and releases
within the prescribed period will entitle Syscon to charge the Client for all additional services
required as a result of such failure.

SERIAL 13139-REP
3.3 In no event shall the Support services be construed as a source of training or a source of
consulting. Misuse of the Support services may result in direct billing, on a T&M basis, for any
such training or consulting services.
3.3.1 Client acknowledges and agrees that maintenance of all computer hardware,
communications equipment and/or software, cabling, peripherals and any other hardware
equipment necessary and required for the operation of the Application Package Programs,
shall be the exclusive obligation of the Client. In particular, and without limiting the
generality of the foregoing, Syscon shall not be held responsible for the provision of any
assistance (under the terms of this Agreement) required as a result of any;
3.3.2 modification, change or upgrade to any hardware or software (other than any
modification, change or upgrade made by Syscon to the Application Package Programs);
or
3.3.3 damage to the Application Package Programs by accident or other external cause, the
fault or negligence of any party other than Syscon, or use by Client in other than its
normal and customary manner; or
3.3.4 as a result of any modification made by Client or any party other than Syscon, even if
Syscon has knowledge of the possibility of such potential loss or damage. If, as a result
of one or more of the foregoing circumstances Client requires assistance, Syscon shall
agree to provide such assistance on a T&M basis.
4.0 WARRANTIES AND LIMITATION OF LIABILITY
4.1 Syscon warrants that it shall perform the Support in accordance with the standard of care and
diligence normally practised by software firms performing services of a similar nature and with
the performance criteria set forth in Section 1.2.
4.2 THE FOREGOING WARRANTY IS IN LIEU OF ALL OTHER WARRANTIES OR
CONDITIONS. SYSCON MAKES NO OTHER WARRANTY OR CONDITION, EXPRESS
OR !IMPLIED, AND THERE ARE EXPRESSLY EXCLUDED ALL IMPLIED OR
STATUTORY WARRANTIES OR CONDITIONS OF MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE AND THOSE ARISING BY STATUTE OR OTHERWISE IN
LAW OR FROM A COURSE OF DEALING OR USAGE OF TRADE. THE FOREGOING
WARRANTY IS IN LIEU OF ALL LIABILITIES OR OBLIGATIONS FOR DAMAGES
ARISING OUT OF OR IN CONNECTION WITH THE PERFORMANCE, DELIVERY OR USE
OF THE SUPPORT OR ANY PRODUCT DEVELOPED BY THE PROVISION OF THE
SUPPORT.
4.3 IN NO EVENT WHATSOEVER SHALL SYSCON BE LIABLE FOR INDIRECT,
CONSEQUENTIAL, EXEMPLARY, INCIDENTAL, SPECIAL, OR OTHER DAMAGES
INCLUDING BUT NOT LIMITED TO LOST PROFITS, LOST DATA, LOST BUSINESS
REVENUE, FAILURE TO REALIZE EXPECTED SAVINGS, OTHER COMMERCIAL OR
ECONOMIC LOSS OF ANY KIND OR ANY CLAIM AGAINST THE CLIENT BY ANY
PARTY ARISING OUT OF OR IN CONNECTION WITH THE PERFORMANCE OF,
DELIVERY OF OR USE OF THE SUPPORT OR ANY PRODUCT DEVELOPED BY THE
PROVISION OF THE SUPPORT OR ANY BREACH OF THIS AGREEMENT, EVEN IF
SYSCON HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
4.4 Syscon's liability arising out of this Agreement shall not exceed the amount paid by the Client to
Syscon under this Agreement. The limitations of liability contained in this Agreement shall not
apply to claims for injury to persons or damages to property caused by the negligence or fault of
Syscon.
4.5 No action, regardless of form or theory of liability, arising out of this Agreement may be brought
by the Client against Syscon more than two (2) years after the date of the occurrence giving rise to
the claim.
5.0 PROPERTY RIGHTS
5.1 Any ideas, concepts, know-how, techniques or software acquired or developed during the term of
this Agreement (including, but not limited to, Major Releases, Maintenance Releases, written
materials, programs, documentation and designs) are and shall remain the exclusive property of

SERIAL I3139-RFP
Syscon or its licensors (as the case may be). All physical media provided pursuant to this
Agreement shall be and remain the property of the Client. This Agreement does not grant the
Client any proprietary or intellectual property rights, title or interest in or to the Application
Package Programs or any portions thereof, except as granted herein and Client shall not, at any
time, whether before or after the termination of this Agreement, contest or aid others in contesting,
or doing anything which otherwise impairs the validity of any proprietary or intellectual property
rights, title or interest of Syseon in and to the Product, Custom Modifications or any portion
thereof. Except as required by auditors or law, Client shall not, at any time, whether before or
after termination of this Agreement, disclose, furnish, or make accessible to anyone any
confidential information received from Syseon, which confidential information is deemed to
include the Product and any Custom Modifications.
6.0 TERM, DEFAULT AND TERMINATION
6.1 Unless and until terminated in accordance with the provisions of this Master Services Agreement:
(i) the term of this Agreement will commence on the Effective Date and will continue until June
3e, to coincide with the Client fiscal year end and, (ii) thereafter, this Agreement will
automatically renew for the period of July I' through May 31' each year. Syseon will offer
subsequent renewals so long as Client is not in breach of Section 4.2 and provided all sums and
amounts due under Exhibit A are paid when due.
6.2 Client reserves the right to terminate this Agreement without penalty or future liability at its fiscal
year end due to lack of appropriations. In the event of termination, the Client agrees that any and
all sums and amounts reimbursable under the terms of this Agreement, including expenses
incurred by Syscon, prior to the notification of termination under this Section 6.2 shall be payable
by Client forthwith.
6.3 If, after termination of this Agreement, Client requests Support, Syseon may agree to provide such
Support and Client shall pay for same forthwith on a T&M basis at Syseons then current rates.
6.4 In the event that either party (the "Defaulting Party") shall neglect, fail or refuse to perform under
any of the provisions of this Agreement, then the other party (the "Non-Defaulting Party") may
deliver to the Defaulting Party notice of intention to terminate this Agreement which notice shall
specify the alleged neglect, failure or refusal and, if within 30 days after the date of delivery of
such notice, the Defaulting Party shall not have fully cured all the defaults indicated therein, or
presented a plan acceptable to the Non-Defaulting Party to cure such defaults, then upon
expiration of such 30 days, the Non-Defaulting Party may, at its option, elect to terminate this
Agreement.
6.5 Notwithstanding Clause 6.4, if the Client fails to pay Syscon as required by this Agreement,
Syscon shall not be required to provide Support services forthwith after delivery of written notice
to that effect to the Client, and may pursue any other remedies which it may have at law or under
this Agreement.
7.0 GENERAL TERMS
7.1 Notices: All notices required by this Agreement shall be delivered to Syscon and to the Client at
their respective addresses noted below or to such other address as the party to receive such notice
or request so designates by written notice to the other. Such notices shall be deemed given on the
date of delivery.
Syscon: The Client:
Syscon Justice Systems Canada Ltd. Maricopa County
6500 River Road, 2"d Floor 320 West Lincoln
Richmond, BC V6X 1X5 Phoenix, AZ 85003
Attention: Support Manager Attention: Chief Procurement Officer
Fax: 604-606-7654 Fax: (602) 258-1573
7.2 Currency: All references to dollars in this Agreement shall be deemed to be US currency.
7.3 Assignment. Neither party may assign its rights, duties or obligations under this Agreement,

SERIAL I3139-RFP
without the prior written consent of the other party, which consent shall not be unreasonably
withheld.
7.4 Enurement: Subject to the limitation set forth in Section 7.5 this Agreement shall enure to the
benefit of and be binding upon the parties and their respective successors and permitted assigns.
7.5 Support Restrictions: Nothing herein shall permit Client to reverse engineer, disassemble or
decompile the Application Package Programs (or any portion thereof). In addition, it is expressly
understood that Client shall not amend, change or alter any application/module libraries or
database schema including, but not limited to, table structure, indexes, views, referential
constraints or synonyms, without Syseon's written permission. To the extent Syscon permits
Client to modify, amend, change or alter any part of the Application Package Programs, Syscon
shall have no obligation to cure any Defects resulting from any such modification, amendment or
change.
7.6 De-Support: Syscon shall provide Support for the current release of the Application Package
Programs and no more than two (2) Major Releases preceding the current release (for the purposes
of this paragraph only, the "Current Release"). In the event Client is unable or unwilling to
maintain a Current Release of the Application Package Programs on its Production System Syscon
may provide Client with twelve (12) months advance written notice of its intention to de-support
such obsolete version(s) at the end of such twelve (12) month period. Client acknowledges that
Support will be limited to commercially reasonable efforts to the extent that Client elects not to
maintain a Current Release of the Application Package programs.

SERIAL 13139-REP
SYSCON JUSTICE SYSTEMS
CLIENT SUPPORT AGREEMENT
SCHEDULE A
APPLICATION PACKAGE PROGRAMS
PHASE I:
Product modules:
Admission / Transfer / Release Assessment & Classification Billing of Services
Case Management / Re-Entry Counts Court Orders & Legal Documents
Discipline Event Log (Shift / Case Notes) Housing Bed Management
Inmate Correspondence Inmate Property Movements
Requests and Grievances Security Threat Groups Sentence Accounting
Visits Diets I (Limited Functionality) Programs
Custom Modifications/Interfaces:
Court / ICIS Systems Inmate Telephone System Jolts
Justware Livescan Magellan Mercy Maricopa
Naphcare HER PHRED Video Visitation (SECURUS))
Coplink Mugshot Justice Web Interface (JWI)
IA Pro Offender Based Tracking System IFCS (Bridging Interfaces)
(OBTS)
Pre-Book (Bridging Interfaces) Court Operations (Bridging Interfaces)
PHASE 2A:
Product modules:
Trust Accounting Commissary
Health / Diets 2 Facility Issue (Inmate Properly)
Custom modifications/Interfaces:
Touchpay Phase 2a: Data Migration
PHASE 2b:
Product modules:
PreBook Court Operationa
Transportation Victims Services
Custom Modifications/Interfaces:
External Records Management MCSO Records Management ICIS Superior Court
Systems System
Phoenix PD Common Case Number 2-Finger ID
HER-CHS Tcchcare
EMBEDDED THIRD PARTY PROGRAMS:
• JBoss EAP
• JBOSS Fuse
• JBoss BPM Suite
• Oracle BI Publisher

SERIAL 13139-RFP
SYSCON JUSTICE SYSTEMS
CLIENT SUPPORT AGREEMENT
SCHEDULE 11
COVERAGE
1. Support service is for the following periods (Sec 2.1):
Syscon Helpdesk provides 7 day by 24 hour live answer support and dispatch for all Priority 1 incidents.
Case logging is available 7*24 via the web portal. P2-P4 incident are supported during the business hours M-
F 06004800 PST.
2. The telephone number is 1-888-479-7266 or support@syscon.net (Sec II)
3. Designated Individuals (Sec. 4.1.1):
NAME TELEPHONE E-MAIL ADDRESS
6. The following person(s) are authorized to approve additional expenditures (Sec. 3.1) under this Agreement:
NAME TITLE TELEPHONE E-MAIL
Any and all services that may be provided outside of the scope of this Agreement, (as referenced in Sec. 2.1, 2.2,
2.3, 44 3.2, 3.3, 3.1, 1.2, 1.3, 1.1 and 6.3 8.3) including any request for Support outside of the hours listed on this
Schedule 13, shall be provided on a T&M basis at rates current when such services are performed as identified in
Exhibit A and will be billed annually in arrears. The current rate is $150.00 per hour.

SERIAL 13139-RFP
EXHIBIT F, 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 determine 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
airfares related to transportation to or from an alternate site.
3.3. The County will not (under no circumstances) reimburse for Contractor guest commercial air travel.
4.0 Rental vehicles may only be used if such use would result in an overall reduction in the total cost of the trip, not
for the personal convenience of the traveler. Multiple vehicles for the same set of travelers for the same travel
period will not be permitted without prior written approval by the County Contract Administrator.
4.1. Purchase of comprehensive and collision liability insurance shall be at the expense of the contractor. The
County will not reimburse contractor if the contractor chooses to purchase these coverage.
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.

SERIAL I3139-RFP
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 Hit is less expensive than shuttle service to and from the airport.
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 15% of project price unless otherwise specified in individual
contracts

SERIAL 13 I39-RFP
EXHIBIT G - SECURITY GUIDELINES
1.0 BACKGROUND CHECKS
1.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 Sheriffs Office or other Jaw
enforcement agency approved by MCSO. The process may also include completion the Arizona
Department of Public Safety (DPS) Terminal Operator Certification (TOC) Level "D."
1.2 Contractor and Subcontractor staff shall clear the FBI background check prior to performing 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.
1.3 Forms required for the background check and Courtesy ID are provided in Appendix I.
Application forms 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 Project Manager or designee who will then forward the forms for processing.
1.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.
2.0 FACILITY SECURITY GUIDELINES AND MCSO COURTESY IDENTIFICATION CARD
2.1 All Contractor and Subcontractor personnel who require physical access to MCSO facilities shall
comply with facility security guidelines. If appropriate, Contractor personnel shall complete the
Sheriff's Office Application For Courtesy Identification and Prison Rape Elimination Act (PREA)
Acknowledgement forms (Appendix 1) prior to performing any services, or gaining access to any
Sheriff's Office facility. 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 Manager 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.
2.2 Applicants must meet the following conditions to be approved by the Sheriff or his designee for
access to Sheriffs Office jail facilities:
2.2.1 Be at least eighteen (18) years of age. There shall be no exceptions.
2.2.2 At least twelve (12) months must have elapsed since serving a term of probation or
parole.

SERIAL 13139-RFP
2.23 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.
2.14 If an ex-offender served a jail or prison term as a result of a felony conviction, access will
be denied.
2.3 Contractor or Subcontractor personnel who are approved after a criminal history check may be
issued a Sheriff's Office Courtesy Identification Card. The card shall remain the property of the
Sheriff's Office and may be revoked if the following rules and regulations are not adhered to:
2.3.1 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.
2.3.2 All personnel are required to submit to a search for contraband, if asked.
2.3.3 Contractor personnel are prohibited from duplicating the card.
2.3.4 Contractor personnel who lose their access cards shall immediately report the loss to the
MCSO Technology Bureau Project Manager or Jail Commander.
2.3.5 Allowing another person to use the Courtesy ID Card is prohibited.
2.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
Project Manager within twenty-four hours. Access to MCSO facilities may be subsequently
suspended or revoked at the discretion of the Technology Bureau Project Manager, Facility
Commander, or designee.
2.5 All concerns regarding contractor personnel should be forwarded to the MCSO Technology
Bureau Project Manager. The services of any contractor may be reduced, postponed or
discontinued for any of the following reasons:
2.5.1 Violating facility security guidelines.
2.5.2 Participating in unlawful or immoral conduct.
2.5.3 Showing signs 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.
2.5.4 Reporting to work with any odor of intoxicating beverage on their breath or while under
the influence of any intoxicating beverage to any degree.
2.5.5 Behaving in a mariner which threatens the safety and security of the jail, staff, or inmate.
2.5.6 Unauthorized contact with inmates.
2.5.7 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.
2.5.8 Possession of any weapon on or near County property,
2.5.9 Failure to follow the directions of Sheriffs Office staff.
2.5.10 Being in an unauthorized area.
2.5.11 Possession of tobacco products, alcohol, and weapons are strictly prohibited on jail
premises.
2.5.12 Under no circumstances will cell phone cameras be used without the express permission
of the Jail Commander or designee.
2.5.13 Under no circumstances will MP3 players, radios, I-Pods or similar devices be permitted
in a jai] facility.
2.5_14 Contractor or Subcontractor personnel shall NOT talk to or associate with any inmate for
any reason without prior authorization.
2.6 The Sheriff's 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 Project Manager or designee. Failure to follow security guidelines
may result in revocation of the Courtesy ID.

SERIAL 13139-RFP
3.0 CRIMINAL JUSTICE INFORMATION SERVICES (CRS) SECURITY POLICY
3.1 The US Department of Justice, Federal Bureau of Investigation, Criminal Justice Information
Services Division Criminal Justice Information Services (CDS) Security Policy, Version 5.3
dated 8/4/2014 (doe ID CJISD-ITS-DOC-08140-5.3). Is herein incorporated by reference into
this Agreement and is made a part thereof.
3.2 A Senior Corporate Official of Contractor shall complete, execute and return to County the form
Appendix H, Security Addendum, contained therein.
3.3 Complete document text can be located at htto://www.fbi.gov/about-uskils/clis-security-oolicv-
resource-center

SERIAL 13139-RFP
APPENDIX I - FORMS
Table of Contents:
1.0 Change Order Form
2.0 Acceptance Form
3.0 TOC Clearance Form
4.0 Background Check and Identification Request
5.0 MCSO Non-Disclosure Agreement
6.0 CBS Security Addendum
7.0 Client Support Designees

SERIAL I3139-RFP
1.0 FORM OF CHANGE ORDER
Capitalized terms used in this Change Order without definition have the meanings given to such terms in one or more of the
Software License, Customer Support, Project Charter or SOW documents.
THIS CO IS SUBJECT TO A COMPLETED SOW [comment only if 26K and fixed bidl
REQUESTOR INFORMATION:
Request Date: Return Date:
Requested By: Organization:
Prepared By: Other Tracking It's:
Change Type — Check one:
Requirements Design Training
Schedule QA/Test Custom Change
Change Payment Type & Source:
Fixed Price Time and Materials
Contract Amendment
CHANGE INFORMATION:
PROPOSED CHANGE SUMMARY DESCRIPTION:
2 JUSTIFICATION AND IMPACT OF PROPOSED CHANGE:
3 EXPECTED DURATION:
4 DURATION VISIBILITY AND SCHEDULE IMPACT ON PROGRAM OF WORKS:
5 DELIVERABLES/TASKS:
6 PRICE AND PAYMENT SCHEDULE FOR PROPOSED CHANGE:
Fixed Price Response:
Syscon can complete the requested change for a fixed price of <Price>. Local taxes will be applied where
applicable.
Payment schedule breakdown as follows;
(9

SERIAL 13139-REP
1. Execution of the Change Order (40%1 <123>
2. On delivery of design and / or requirements document [20%] <123>
3. On delivery of final codei25%) <123>
60 days post-delivery or move to production (whichever is
4. <123>
earlier)[15%1
Total cost: $ <123>
The price is valid for 30 days
7-1411,4 Response:
This project will be invoiced at the agreed upon rate of $<x,xxx,xx> for each hour expended. A schedule of
hours will be provided upon agreement of this change order, setting out the estimated number of hours
associated to each deliverable. <CLIENT> acknowledges estimates will be provided for tracking purposes only
and to assist with <CLIENT> budgeting and Syscon's resource scheduling purposes. Upon completion of
approximately 50% of the agreed estimated hours, Syscon shall re-estimate the remaining effort and review
with <CLIENT>.
Currently Syscon has estimated that it will take <hours> (<numeric>) hours to complete the above described
work. The estimated hours do not include contingency. Syscon recommends that <CLIENT> add +20%
contingency to the requested budget.
Syscon will continue to provide the services beyond the total of the estimated hours unless instructed in
writing to cease activity by <CLIENT>.
7 STAFF AND PERSONNEL HOURS; REIMBURSABLE EXPENSES:
9 ALTERNATIVES:
For each Change Order, the Syscon Project Manager will submit the Change Order to <CLIENT> Project
Manager at which time a control number will be assigned so that the Change Order can be tracked to
completion. All Change Orders will be reviewed by the applicable stakeholders and approval to proceed will
require sign off by Syscon and the Project Oversight Committee.
When approved by the Project Oversight Committee and accepted by Syscon, each Change Request becomes a

SERIAL 13139-RFP
Change Order.
APPROVAL: (<CRent>)
Signed: Signed:
Name: <Name of Approver> Name: <Name of Approver>
Project Sponsor Title: Senior User
Date: Date:
Signed: Signed:
Name: Name:
Title:
Date: Date:
ACCEPTED: (Syscon)
Signed: Signed:
Name: Name:
Project Manager VP Professional Services
Date: Date:
Signed:
Name: Dr. Steve Long
title: CEO
Date:

SERIAL 13139-REP
2.0 ACCEPTANCE FORM
MAR ICOPA COUNTY
ACCEPTANCE CERTIFICATE
PROJECT INFORMATION
CONTRACTOR: Syscon Justice Systems
PROJECT NAME:
PHASE #: N/A
PHASE TITLE: N/A
DATE OF ACCEPTANCE:
The task/deliverables set out in the Statement of Work: «Reference», dated «DATE>> (the "SOW"), are in respect of
<insert Summary Description>
Project deliverables under the SOW consist of a «List High Level Scope, deliverables, etc». The system was promoted
to production on «DATE». The warranty concluded on «DATE».
The software changes delivered pursuant to the SOW are subject to an annual technical support fee for such programs
in the amount of $000.00. The annual fee will be pro-rated from the «DATE» end-of-Warranty Period to the annual
support agreement «DATE» anniversary date.
«CLIENT» agree that all project deliverables satisfy the applicable acceptance criteria set forth in section «#» of the
SOW and hereby certifies its Acceptance.
Notes & Decisions

SERIAL 13139-RFP
CLIENT APPROVER INFORMATION:
Signed: Signed:
Name: Name:
Title: Project Sponsor Title: Project Manager
Date: Date:
CONTRACTOR CERTIFICATION:
By its signature below, Syscon certifies to the <<CLIENT>> that as of the date of this
task/deliverable acceptance certificate, it has satisfied the conditions related to completion of
the tasks and delivery of the deliverables set forth above and that the work performed in
respect of such deliverables has been completed in accordance with the SOW.
Signed: Signed:
Name: Name:
Project Manager Title: V.P. Professional Services
Date: Date:

SERIAL 13139-RFP
3.0 TOC Clearance Form
t Acrobat Document i H:\Contt Fires\21:1.3 ContractA1313g-RFP MAS)Conbact Creation \Final Contract‘13139-RFP New JAAS SYSJ l=@1 h
MARICOPA COUNTY SHERIFFS OFFICE
APPLICATION FOR TOC CERTIFICATION/BACKGROUND INFORMATION
Please complete the following information In order for the isilancopa County Sheriff's Office
(MCSO) to complete a non-criminal justice TOC Certification and clearance necessary prior to
conducting work on behalf of Marioopa County.
Name: DOB:
ADDRESS:
CITY: STATE: ZIP: PLACE OF BIRTH:
HEIGHT: WEIGHT: EYES: RACE: SEX:
SOC. SEC. NUMBER*: DRIVER'S LIC: EXPIRE=
EMPLOYER:
ADDRESS:
CITY: STATE: ZIP: BUS PHONE:
POSITION TITLE:
POSMON DUTIES:
JUSTIFICATION FOR ZONE 1/2 ACCESS:
JUSTIFICATION FOR PHYSICAL ACCESS:
*Pursuant to ARS § 11441, providing your Social Security number is mandatory. It will be
used for background investigation purposes.
igcSo cONFOIMAL. v22

SERIAL l3139-RIP
Acrobat Document in MContract Filr_s \2013 Contracts‘13139-RFP NS \Contract CreationVinal Contract\13139-RFP New JMS Sys— L
Fie Edit View Window
ri7EI L
Common
MARICOPA COUNTY SHERIFF'S OFFICE
APPLICATION FOR TOC CERTIFICATION/BACKGROUND INFORMATION
Have you ever had your drivers license suspended or revoked? if yes, explain.
2. Other than minor traffic offenses or parking violations, have you ever been convicted of
any crime including, but not limited to, offenses involving illegal drugs or driving under
the influence? if yes, please explain and give dates and jurisdictions as qapropriate.
3. Have you ever used any other name for any purpose (including maiden name)? If yes,
explain (including where, when, etc.).
4. Have you ever been censured or disbarred or had any professional license or certificate
suspended or revoked? If yes, explain.
5. List all previous addresses where you have lived during the past five years.
MCS0 CONFIDENTIAL v2_2

SERIAL 13139-RFP
Aanttat Document in HAContract Files‘2013 ContractA13139-RFP MS \Contract Czeationlfinal ContractV13139-RFP New WS Sys-.
Edit View 14rsntIow•Help
3 •Comment
WAIVER OF LIABILITY AND RELEASE
NON-EMPLOYEE
In consideration of the Maricopa County Sheriffs Office (MCSO) processing of my TOC
Certification and background check I hereby agree to
the following terms and conditions:
The tenTis °background investigation" as used Ui this document, refers to any and all
information and sources of information thal MCSO, in its sole discretion, may deem necessary
to obtain or contact in the furtherance of this criminal background check.
I authorize any person or entity contacted by MCSO agents or employees during the
course of my background investgation, to furnish to such officers, agents, or employees
any information they may have which is reasonably related to the completion of this
backgrourid check.
2. I hereby release from liability and promise to hold hannless under any and all causes of
legal action, all persons or entities who shalt in good faith furnish any information or
records to the officers, agents or employees of MCSO Who conduct my background
investigation and agree to release the Maricopa County Sheriffs Office, its officers,
agents and employees from all liability for ads necessary to conduct and finalize the
investigation.
This release from liability given by me to all persons or entities mentioned above, shot apply to
any right of action of any nature whatsoever that might accrue to myself, my heirs, or my
personal representative
READ CAREFULLY BEFORE SIGNING
SIGNATURE OF APPLICANT
SIGNATURE OF vvrrNEss DATE
ACKNOWLEDGED before me this day of
NOTARY PUBLIC
My Commission Expires:
NI150 CONFIDENTIAL v2.2

SERIAL I3139-RFP
4.0 MARICOPA COUNTY SHERIFF'S OFFICE
APPLICATION FOR COURTESY IDENTIFICATION
NAME: DATE OF BIRTH:
ADDRESS:
CITY: STATE ZIP:
HEIGHT: WEIGHT: EYES: HAIR: SEX:
SSN: DRIVER'S LICENSE: EXPIRE:
EMPLOYER:
TIME WITH COMPANY:
ADDRESS:
CITY: STATE: ZIP: PHONE:
APPLICANT'S TITLE:
JUSTIFICATION FOR GENERAL ACCESS:
JUSTIFICATION FOR JAIL ACCESS:
I authorize the Maricopa County Office to conduct a Criminal History/ Records Check and Warrants Check for the
purpose of issuing a Sheriff's Office Courtesy Identification Card. I understand that this card be issued to me, it will
be displayed ONLY when I am in a Sheriffs Office building or facility. I further understand that the card will be
used to enter the Sheriff's building or facilities for official purpose related to my employment only.
SIGNATURE OF APPLICANT DATE

SERIAL 13139-REP
5.0 Maricopa County Sheriff's Office
Non-Disclosure/Confidentiality Agreement
Any information obtained by a contractor, vendor or private provider ('contractor') in the course
of conducting business with the Maricopa County Sheriffs Office ('Sheriffs Office') is
potentially roprietary to the Sheriffs Office and/or confidential. This statement sets forth the
Sheriffs Office requirements of the contractor with respect to such information.
The contractor shall establish and maintain procedures and controls that are adequate to assure
that no information contained in its records and/or obtained from the Sheriffs Office or from
others in carrying out is functions (services) under the Agreement shall be used by or disclosed
by it, its agents, officers, or employees, except as required to efficiently perform duties under the
Agreement. Prior to commencing work under the Agreement, the contractor shall apprise the
Sheriffs Office of its proposed procedures and controls, and the Contractor must receive the
Sheriffs Office written approval thereof before commencement. If, at any time during the
duration of the Agreement, the Sheriffs Office determines that the procedures and controls in
place are not adequate, the contractor shall institute any new and/or additional measures
requested by the Sheriffs Office within 15 days of the written request to do so.
Contractor requests for information contained in the Sheriffs Office records shall be referred to
the Sheriffs Office for review and approval, prior to any dissemination. The contractor also
agrees that any information pertaining to individual persons shall not be divulged other than to
employees or officers of the contractor as needed for the performance of duties under the
Agreement or procurement process, unless otherwise agreed to in writing by the Sheriffs Office.
have read, agree with these conditions as a requirement of doing business with the Sheriffs
Office, and that I represent that I am authorized to bind my company to this agreement.
Date:
Company Name
Phone:
Printed Authorized Representative Name
Fax:
Title
Email:
Signature

SERIAL 13139 -RFP
6.0 CAS Security Addendum
FEDERAL BUREAU OF INVESTIGATION
CRIMINAL JUSTICE INFORMATION SERVICES
SECURITY ADDENDUM
CERTIFICATION
hereby certify that I am familiar with the contents of (1) the Security Addendum, including
its legal authority and purpose; (2) the NCIC Operating Manual; (3) the CJIS Security Policy; and (4)
Title 28, Code of Federal Regulations, Part 20, and agree to be bound by their provisions.
I recognize that criminal history record information and related data, by its very nature, is
sensitive and has potential for great harm if misused. I acknowledge that access to criminal history
record information and related data is therefore limited to the purpose(s) for which a government
agency has entered into the contract incorporating this Security Addendum. I understand that misuse
of the system by, among other things: accessing it without authorization; accessing it by exceeding
authorization; accessing it for an improper purpose; using, disseminating or re-disseminating
information received as a result of this contract for a purpose other than that envisioned by the
contract, may subject me to administrative and criminal penalties. I understand that accessing the
system for an appropriate purpose and then using, disseminating or re-disseminating the information
received for another purpose other than execution of the contract also constitutes misuse. I further
understand that the occurrence of misuse does not depend upon whether or not I receive additional
compensation for such authorized activity. Such exposure for misuse includes, but is not limited to,
suspension or loss of employment and prosecution for state and federal crimes.
Printed Name/Signature of Contractor Employee Date
Printed Name/Signature of Contractor Representative Date
Organization and Title of Contractor Representative

SERIAL 13139-RFP
7.0 CLIENT SUPPORT AGREEMENT
SCHEDULE B
SYSCON JUSTICE SYSTEMS
CLIENT SUPPORT AGREEMENT
SCHEDULE B
COVERAGE
1. Support service is for the following periods (See 2.1):
Syscon Helpdesk provides 7 day by 24 hour live answer support and dispatch for all Priority I incidents.
Case logging is available 7*24 via the web portal. P2-P4 incident are supported during the business hours M-
F 0600-1800 PST.
2. The telephone number is 1-888-479-7266 or support@syscon.net (Sec 1.1)
3. Designated Individuals (Sec. 4.1.1):
NAME TELEPHONE E-MAIL ADDRESS
6. The following person(s) are authorized to approve additional expenditures (Sec. 3.1) under this Agreement:
NAME TITLE TELEPHONE E-MAIL

SERIAL 13139-RFP
APPENDIX 2 - INTERFACE INVENTORY

SERIAL 13139-RFP
ID Primary Direction Systems
Interface/Dal Description Stakeholder Compl Trans TIE? Trigger Frequency Volume IN OU IN 44z. Involved Comment
a Exchange exity ID/Queue Logic T OUT
JMS-01 MCAO CAIS Booking information - County Atty High BOOK CHEW Yes When a 1 set of all 1800/wk X IMS to CATS
including demographics, ARST AKAS booking is transactions approx
alias, etc - Used to establish SMTS HOLD completed per booking 18,000
the booking and charge 1DNO COST and data is individu
information as a case by the LINK CHR1 sent from al
County Attorney CHRB DRNO Prebooking transacti
BOND to IMS ORS
AHAU
IMS-02 MCAO CATS Release information - 48hr County Atty Low RLSE Yes When an 1 per release 1150/wk X IMS to CATS
release candidates report inmate
release is
being
processed
and/or
completed
in JMS
IMS-03 ICS Scheduled Court Events - Superior High SCEV Yes When court 1 per X iCIS to IMS Was
Used to update court events Courts events are Superior implemented
into the JMS. completed Court event but is currently
in iCIS scheduled turned off due
to [imitations in
the current
JMS. The new
JMS would
need to be able
to have multiple
future superior
court events
stored for each
inmates court
Case.
)MS-04 iCIS Booking and Form IV data - Superior Low COST Yes When X JMS to iCIS
Used to setup the docket for Courts inmate info
the Initial Appearance court linked
event. Also includes initial (SID/FBI
appearance court related set) or
releases when
released
JMS-05 iCIS APD APETS (Adult Adult Med Daily File Yes Daily X JMS to ICES
Probation Enter. Tracking Probation (/t-PD)
System) - Booking and
Release Data
IMS-06 Video Scheduled Visit - Used to Visitation Low V212 Yes When a 3175/wk X VVS to JMS
Visitation get visit start time and booth new
System (VVS) visitation is
requested
on VVS

SERIAL 13139.-RFP
ID Primary Direction Systems
Interface/1Dat Description Stakeholder Comp' Trans TIE? Trigger Frequency Volume IN OU IN & Involved Comment
a Exchange exity 113/Queue Logic T OUT
JMS-07 Video End/Cancel Visit - Used to Visitation Med V2I 3 Yes When 3100/wk X VVS to AVIS
Visitation end or cancel a scheduled either party
System (VVS) visit ends
session
JMS-08 Video Various error codes - Visitation Med VXXX Yes When 5/wk X VVS to ,TMS
Visitation Transmitting various error errors
System (VVS) codes occur
JMS-09 Video Request a visit - Visitor Visitation Low 0212 Yes When visit 3175/wk X 'MS to VVS
Visitation requesting a visit requested
System (VVS) on JMS
JMS-10 Video Visit Maintenance - Visitor Visitation Low 0213 Yes When 175/wk X JMS to VVS
Visitation requesting a visit visits are
System (VVS) cancelled
JMS-11 Video Enable Visitation Booth - Visitation Low D261 Yes When 1/wk X JMS to VVS
Visitation Allows users to Enable booths go
System (VVS) Visitation Booths into
operation
IMS-12 Video Disable Visitation Booth - Visitation Low D262 Yes When 5/wk X JIMS to VVS
Visitation Allows users to Disable booths go
System (VVS) Visitation Booths out of
operation
JMS-13 Video Disabled Booth Report - Visitation Low D263 Yes As Needed 5/wk X JWIS to VVS
Visitation Request Disabled Booth
System (VVS) Report
JMS-14 Prebooking to Validated booking data from IMS High JIYIS Queue Yes Booking 1 per 300/day X Prebooking Internal - may
JMS Pre-Booking -All inmate final booking to JMS and go away with
See demographic, SMT, arrest, acceptance 'MS to integrated
PreBooking charges, aliases, holds, DR in Prehooking solution
Tab numbers, sentence info - ?rebooking
goes onto TMS queue
JMS-15 DOC (AZ Listing of Convicted Felons DOC High Data File No Monthly 2500/mo X ADOC to
Dept. of - Listing of Convicted JMS
Corrections) Felons for Visitation
Exception list
JMS-16 US Social Website FTP Upload - US SSA Med Data File No Quarterly X JMS to SSA
Security Identify persons not entitled FTP upload
Administratio to benefits of Data
n
JMS-17 AZ Dept of CD hand delivered quarterly AZ DES Med Data File No Quarterly via X JMS to DES
Economic - Identify persons not CD of
Security entitled to benefits Monthly
Data
JMS-18 Inmate into to Release info to IFCS - Inmate Low RELE Yes Release 1 time per X JMS to IFCS Internal - may
IFCS - Release notice sent to IFCS Funds completed booking go away with
Release to prepare to close inmate in JMS integrated
See IFCS tab acct solution
c Q

SERIAL 13139-RFP
JMS-I9 Inmate into to Housing info to IFCS - Inmate Low HOUS Yes Housing As needed X JNIS to IFCS Internal - may
IFCS - Housing assignment/move Funds transaction go away with
Housing info to IFCS in 3MS integrated
See IFCS tab solution
r IMS-20 . Inmate into to LEJIS info to IFCS - LEJIS Inmate Low LNBR Yes LEJIS As needed X JMS to IFCS Internal - may
IFCS - LEJIS information sent to IFCS Funds number go away with
number received in integrated
See IFCS tab ,TMS solution
JIVIS-21 JMS to IFCS ASP/ADOC transfer Inmate Med IFITR/2005 - Yes Daily Files Daily X JMS to IFCS Internal - may
See IFCS tab information Funds DES006OT and IFCS to go away with
and JNIS integrated
DES006UT solution
1MS-22 ,IMS to Inmate Programs Data Inmate Med INMPG Yes Daily Files Daily X JMS to Internal - may
Programs Programs Inmate go away with
Programs integrated
and Inmate solution
Programs to
JMS
IlvIS-23 Avaya IVR Realtime inquiry for inmate Friends/F'ami High Yes X MS to IVR IVR System is
bond/charges/location - ly of Inmates being upgraded,
Legal Aide/Friends/Family
call for information about an
inmate.
JMS-24 Mug Shot Various information to IWS rws Med BOOK HOUS Yes Various X JMS to
Mugshot server from 3MS Mugshot RELE triggers: Mugshot
(BOOK/HOUS/RELE) - system Booking,
Booking/Housing/Release Housing
information to MUGSHOT assignment
server = /move,
Release
IMS-25 CopLink Data feeds from IMS — MCSO and High 2 Data Files Yes Daily X JMS to
Inmate data, including outside law COPLINK
Booking & Release, enforcement
Visitors, etc. - Data agencies
Repository used by law
enforcement officers in the
field, and as a tool for
investigators
JMS-26 CopLink Data feeds from JMS — MCSO and High 2 Data Files Yes Monthly 450,0001 X IMS to
Inmate data, including outside law (during mo COPLINK
Booking & Release, enforcement Purge/Archi
Visitors, etc. from JMS agencies ve process)
IMS-27 Operations Inmate names, locations, Detention 1Vied BOOK, Yes X JMS to OJ Internal - may
Journal (0.1) Inmate (LFJIS #), Projected Officers HOUS, go away with
See 03 Tab Release and Release info RELE, LNBR integrated
from IMS - Uses standard solution
IMS transactions to IFCS

SERIAL 13139-RFP
ID Primary Direction Systems
Interface/DM Description Stakeholder Comp! Trans HE? Trigger Frequency Volume IN OU IN St Involved Comment
a Exchange exity ID/Queue Logic T OUT
MS-28 Court Inmate appointments, Court Transportatio High TAX120, Yes Multiple Daily set of X 1MS to Court Internal - may
Operations cards, Wheelchair ii, Court 1ARI6ORP, Daily Files files Opt go away with
See Court Ops notifications, Keepaway Security IAR127, processed integrated
Tab info, transportation See Court IAR200RQ, just after solution
warnings, and inmates with Opt Tab IAR200RP, midnight
multiple appts IARI 70RP
JIvIS-29 Court Inmate appointments, Court Transportatio High IAR127, Yes Multiple Daily set of X JMS to Internal - may
Transportation cards, Wheelchair n, Court IAR135RP, Daily Files files Transportatio go away with
See Court Ops notifications, Keepaway Security IAR140RP, processed n integrated
Tab info, transportation See Court TARISORF, just after solution
warnings, and inmates with Ops Tab TAR15ORP, midnight
multiple appts IARI60RP,
IARI 70RP,
IAR2OORP,
IAR2OORQ,
IAXI20S
,IMS-30 ITS (Inmate Identifying data for inmate, GTL - ITS Ivied Yes Full Roster data file -4 X JMS to ITS
Telephone includes location info - listing with times a day (GTL)
System) Inmates make out-going location 4
calls from their housing unit times a day
locations, some are not
audited (e.g., attorney calls)
/MS-31 MUGSHOT 1VIIJGSHOT on MCSO.ORG MCSO.ORG Med No Scheduled 4 times a day X IMS to
on (via Batch Server - 231) - process; MCSOS-231
MCSO.ORG Send list of inmate info for I :00am,
(via Batch bookings so far today - sent 6:00am,
Server -231) 4 times a day_ Each file Noon,
contains prior info for day + 6;00pm
bookings since last run.
JMS-32 WIMP Inmate booking info SIMS - Low BOOK Yes Booking I per 300/day X JMS to IFCS Internal - may
(Working Workbox final booking (WIMP) go away with
Inmate Mgmt acceptance integrated
Program) solution
See IFCS Tab
JMS-33 WIMP Inmate work SIMS - Low STAT Yes When data X JMS to IFCS Internal - may
(Working furlough/release info Workbox changes (WIMP) go away with
Inmate Mgmt integrated
Program)See solution
1FCS Tab
MS-34 WIMP Inmate LEJTS number STIvIS - Low LNBR Yes When data X JMS to IFCS Internal - may
(Working Workbox changes (WIMP) go away with
Inmate Mgmt integrated
Program) solution
See IFCS Tab
JMS-35 WIMP Inmate work assignment SIMS - LOW CLFG Yes When data X IMS to IFCS Internal - may
(Working info Workbox changes (WIMP) go away with
Inmate Mgint integrated
Program) solution
, See 1FCS Tab

SERIAL I3139-RFP
IMS-36 WIMP Inmate special sentence SEVIS - Low SCUD Yes When dam X J1VIS to IFCS • Internal - may
(Working program update Workbox changes (WIMP) go away with
Inmate Mgmt integrated
Program)
See IFCS Tab solution
IMS-37 WIMP Inmate classification info SIMS - Low CLAS Yes When data IMS to IFCS Internal - may
(Working Workbox changes (WIMP) go away with
Inmate Molt integrated
Program) solution
See IFCS Tab
JMS-38 WIMP Inmate open holds/charges SIMS - Low OHOC Yes When data X TMS to IFCS Internal - may
(Working flags Workbox changes (WIMP) go away with
Inmate Mgmt integrated
Program) solution
See IFCS Tab
JMS-39 WIMP Inmate scars/marks/tattoos SIMS - Low SMTS Yes When data X 1MS to IF'CS Internal - may
(Working info Workbox changes (WIMP) go away with
Inmate IvIgrnt integrated
Program) solution
See IFCS Tab
JMS-40 TouchPay Realtime inquiry for inmate Touchpay Med BKTP Yes Deposit on 1 per deposit 1000/mo X Touchpay to
Lobby Kiosks still in jail (JMS) - As part of kiosk request iMS
inmate deposits from RAS to
external persons - verify that Touchpay
inmate still in jail (don't take
deposit if released)
JMS-41 ELM Booking and housing related EHR High BOOK NOUS Yes When a 1 set of all 1800/wk X JMS to EHR Transactions
information VALO RELE Booking is transactions approx are "forked" by
completed per booking 18,000 IIE
individu
al
transacti
ens
JMS-42 EHR EFIR General Medical ERR Med EH EHOO Yes When a 1 per health 1800/wk X EHR to JMS
1)0401)044 health review
1)111)1 review is
completed
JMS-43 ERR EHR Medical Clearance for ERR Med ER EHOO Yes When a as X El-ER to JMS
Work D040 1)044 health needed
DUD1 review is
completed
IMS-44 EHR EIIR Diets EHR Med EH E1100 Yes When a as X EHR to JMS
1)040 D044 health needed
DUDI review is
completed

SERIAL I3139-RFP
II) Primary Direction Systems
Interface/Dot Description Stakeholder Compl Trans HE? Trigger Frequency Volume IN OUT IN & Involved Comments
a Exchange exity 11)/Queue Logic OUT
Pre-OI External Initial Booking/Arrest Peoria - High queue specific Yes RMS Sends Possibly 10/day X Agency
Agency transaction -Used to Currently; data multiple from RMS to
RMS's establish booking in MCSO, iterations per Peoria Prebooking
PreBooking, PreBooking PPD, booking
sends a reply transaction Glendale PD
indicating Success or Error - future
conditions - Uses PB Arrest
queue (all agencies)
Pre-02 External Arrest Report - PreBooking PRI) PACE - High queue specific Yes When final 1 per X Prebooking
Agency sends an Arrest Report Currently; Acceptance booking to Agency
RMS's (XML) to the RMS for MCSO, Completed RMS
storage in the arresting PPD,
agencys system. Glendale PA
- future
Pre-03 External Form IV Report - PPD PACE - Low queue specific Yes When final 1 per X Prebooking
Agency PreBooking sends a Form IV Currently; Acceptance booking to Agency
RMS's Report (XML) to the RMS MCSO, Completed RMS
for storage in the arresting PPD,
agency's system. Glendale PD
- future
Pre-04 External Final Acceptance transaction PPD PACE - Med queue specific Yes When final 1 per 25/day X Prebooking
Agency - PreBooking sends the Currently; Acceptance booking to Agency
RMS's Arrest information to the MCSO, Completed RMS
originating RMS at final PPD,
acceptance so that any Glendale PD
changes made during the - future
PreBooking process can be
applied by the originating
RMS.
Pre-05 MCSO RMS Booking/Arrest Data - RMS Intergraph High Yes As MCSO I per 50/clay x FBRJRMS
(Records sends initial BOOKING data FBRJRMS arrests/boo booking to
Mgrnt to Prebooking. Booking is kings occur Prebooking
System) completed in Prebooking and to RMS
updated charge info is sent
back to RMS.
Pre-06 iCIS Validated Form IV data and Superior Med Superior Yes When final I per 300/day X Prebooking
booking info - Booking info, Court Court Acceptance booking to iCIS
like JMS, plus Form IV info Completed
to Courts (iCIS) - County
Charges only - goes to
Superior Court queue
Pre-07 Phoenix Validated Form IV data and PPD Med PPD Yes When final 1 per 300/day X Prebooking
(PFD) booking info - Booking info, Acceptance booking to PPD
like 1MS, plus Form IV info Completed
to PPD - city charges only -
goes to PPD queue

SERIAL 13139-RFP
III Primary Direction Systems
Interface/Dat Description Stakeholder Compi Trans HE? Trigger Frequency Volume IN OU IN & Involved Comment
a Exchange exity ID/Queue Logic T OUT
Pre-08 Common CCN Request / Reply.. Used All County Low Yes When CCN 1 per 250/day X Prebooking Primary ID
Case Number to request and receive a CCN Justice charge is booking to CCN used by all
(CCN) to store on new charges Partners booked Prebooking justice partners
during the intake/booking ACKs to in data
process. CCN exchanges.
' Pre-09 Electronic Inmate ready at intake - CRS- Med EHO I Yes When I per 300/day X Prebooking
Health Inmate in Intake area ready TechCare Officer booking to ERR and
Records for medical screening - £1-ER designates El-ER to
(ERR) responds as ACCEPTED or inmate as PreBooking
DENIED "arrived'
Pre-10 Electronic Booking number assignment CHS - Low E1102 Yes Triggered 1 per 300/day X Prebooking
Health transaction - When inmate TechCare when ERR booking to ERR
Records ACCEPTED, assign a response to
(ERR) booking number and relate to E1101 is
ERR ACCEPT
Pre-11 Electronic Prebooking final acceptance CHS - Low E1103 Yes Final 1 per 300/day X Prebooking
Health to EAR - Inform EMR that TechCare Acceptance booking to El-lit
Records inmate accepted into Jail in
(EHR) Prebooking
Pre-12 Prebooking to Validated booking data from JMS High JMS Queue Yes Booking I per 300/day X Prebooking Internal - may
JMS Pre-Booking -Alt inmate final booking to JMS and go away with
demographic, Scars, Marks acceptance JMS to integrated
and Tattoos, arrest, charges, in Prebooking solution
aliases, holds, DR numbers, Prebooking
sentence info - goes onto
JMS queue
Pre-I3 BioGuard Booking number and Intake Med When final 1 per 300/day X BioGuard to
demographics and Warning Acceptance booking Prebooking
comments -Ensures the Completed
finger getting released is the
same finger that was booked.
Pre-14 TouchPay Receive deposit amount Touchpay TP12 Yes Inmate I per deposit. 250/day X Touchpay to
Cashless from Touchpay - (to Booking request Prebooking
Intake Kiosks Prebooking) proc

SERIAL 13139-RFP
ID Primary Direction Systems
InterfacelDat Description Stakeholder Compl Trans IIE? Trigger Frequency Volume IN OUT IN & Involved Comment
a Exchange exity ID/Queue Logic OUT
IFCS-01 Inmate into to Release info to IFCS - Inmate Med RELE Yes Release 1 time per X JMS to IFCS Internal - may
IFCS - Release notice sent to IFCS Funds completed booking go away with
Release to prepare to close inmate in JMS integrated
See JIVIS tab acct solution
IFCS-02 Inmate into to Housing info to IFCS - Inmate Med HODS Yes Housing As needed X IMS to ircs Internal - may
IFCS - Housing assignment/move Funds transaction go away with
Housing info to TFCS in IMS integrated
See IMS tab solution
IFCS-03 Inmate into to LETTS info to IFCS - LEJIS Inmate Med LNBR Yes LEJLS As needed X JMS to IFCS Internal - may
IFCS - LEES information sent to IFCS Funds number go away with
number received in integrated
See .IMS tab IMS solution
IFCS-04 JIAS to IFCS ASP/ADOC transfer Inmate !Vied IFITR/2005 - Yes Daily Files Daily X JMS to IFCS Internal - may
See )MS tab information Funds DES0060T and IFCS to go away with
and JMS integrated
DES006UT solution
IFCS-05 SAP Business Inmate Account, Ledger and MCSO High Yes Daily X IFCS to SAP Internal - may
One Cash Storage Location Finance go away with
Accounting activity - Used to keep the integrated
System accounting system in sync solution
See SAP Tab with Inmate fund account
activity,
IFCS-06 SAP Business Check Number, Voided MCSO High Yes As needed X SAP to IFCS Internal - may
One Checks and AP Reversal Finance go away with
Accounting activity - Used to store the integrated
System check numbers in the Inmate solution
See SAP Tab Fund module, as well as
voiding checks or reversing
AP transactions. ,
IFCS-07 TouchPay Realtime inquiry for inmate Touchpay Med TP01 Yes Deposit on 1 per deposit X Touchpay to
account open in LFCS (IFCS) kiosk request IFCS
- Is inmate account available IFCS to
for deposit? Touchpay
IFCS-GE TouchPay Realtime inmate deposit Touchpay Med TP02 Yes Deposit on 1 per deposit X Touchpay to
(IFCS) - Deposit $$ on kiosk request IFCS
inmate account
IFCS-09 TouchPay Deposits Range Inquiry - Touchpay Med TPG3 Yes Touchpay 1 or more I /day X Touchpay to
This is used by Touchpay to verify proc per day IFCS to
reconcile transactions before Touchpay
Deposit- to make sure
everything is in IFCS

SERIAL 13139-RFP
ID Primary Direction Systems
Interface/Dat Description Stakeholder Comp! Trans HE? Trigger Frequency Volume IN 01) IN & Involved Comment
a Exchange exity ID/Queue Logic T OUT
IFCS-10 TouchPay Bank Deposit - Total deposit Touchpay Med TP04 Yes Touchpay 1 per day 1/day X Touchpay to
amount and range of deposits deposit to IFCS to
included - used by Finance hank Touchpay
to reconcile deposit process
IFCS -11 TouchPay Void Bank Deposit - Undo Touchpay Med TP05 Yes Touchpay As needed <1/day X Touchpay to
prior bank deposit undo IFCS to
deposit Touchpay
IFCS-12 TouchPay Create Inmate Account Inmate Med PB10 Yes Inmate 1 per deposit 250/day X Touchpay to :
Cashless (from Prebooking) - Create Intake Booking request IFCS to
Intake Kiosks IFCS Inmate Account - pmc Touchpay
Required for Deposit
IFCS-13 TouchPay Cashless inmate inquiry (like Touchpay Med TP11 Yes Inmate I per deposit 250/day X Touchpay to
Cashless TP01) - Is inmate account Booking request 1FCS to
Intake Kiosks available for deposit? proc Touchpay
IFCS-14 TouchPay Deposit from intake/booking Toucbpay Med TP12 Yes Inmate I per deposit 250/clay X Touchpay to
Cashless (like TP02) - Deposit $$ on Booking request 1FCS to
Intake Kiosks inmate account proc Touchpay
1FCS-15 Touchpay Reserved for Touchpay Inmate Med TP20 Yes Inmate 1 per release 250/day X IFCS to
Release Cards Release Card process - in Release Release request Touchpay to
development proc 1FCS
IFCS-16 Touchpay Reserved for Touchpay Touchpay Med TP21 Yes Inmate 1 per release 250/day X 1FCS to
Release Cards Release Card process - in Release request Touchpay to
development proc IFCS
IFCS-17 Touchpay Reserved for Touchpay Touchpay Med TP22 Yes Inmate I per release 250/day X IFCS to
Release Cards Release Card process - in Release request Touchpay to
development proc IFCS
IFCS-18 WIMP Inmate booking info SIMS - Low BOOK Yes Booking 1 per 300/day X JMS to IFCS Internal - may
(Working Workbox final booking (WIMP) go away with
Inmate Mgmt acceptance integrated
Program) solution
See JNIS Tab
IFCS-19 WIMP Inmate work SIMS - Low STAT Yes When data x JMS to IFCS Internal - may
(Working furlough/release info Workbox changes (WIMP) go away with
Inmate Mgrnt integrated
Program) solution
See J/vIS Tab

SERIAL 13I39-RFP
ID Primary - Direction Systems
Interface/Dat Description Stakeholder Cornpl Trans HE? Trigger Frequency Volume EN OU IN & Involved Comment
a Exchange exity ID/Queue Logic T OUT
IFCS-20 WIMP Inmate LEJIS number SIMS - Low LNI3R Yes When data X JMS to IFCS Internal - may
(Working Workbox changes (WIMP) go away with
Inmate Mgmt integrated
Program) solution
See JMS Tab
IFCS-21 WIMP Inmate work assignment info SIMS - Low CLFG Yes When data X IMS to IFCS Internal - may
(Working Workbox changes (WIMP) go away with
Inmate Mgint integrated
Program)See solution
JMS Tab
IFCS-22 WIMP Inmate special sentence SIMS - Low SCUD Yes When data X /MS to IFCS Internal - may
(Working program update Workbox changes (WIMP) go away with
Inmate Mgmt integrated
Program) solution
See JMS Tab
IFCS-23 WIMP Inmate classification info SIMS - Low CLAS Yes When data X JMS to IFCS Internal - may
(Working Workbox changes (WIMP) go away with
Inmate Mgrnt integrated
Program) solution
See JMS Tab
IFCS-24 WIMP Inmate open holds/charges SIMS - Low ()HOC Yes When data X JMS to IFCS Internal - may
(Working flags Workbox changes (WIMP) go away with
Inmate Mgmt integrated
Program) solution
See JMS Tab
IFCS-25 WIMP Inmate scars/marks/tattoos S1MS - Low SMTS Yes When data X JMS to IFCS Internal - may
(Working info Workbox changes (WIMP) go away with
Inmate Mgmt integrated
Program) solution
See JMS Tab
Primary Direction Systems
ID Interface/Dat Description Stakeholder Compi Trans 11E? Trigger Frequency Volume IN OU IN & Involved Comment
a Exchange exity 1D/Queue Logic T OUT
0J-01 Operations Inmate names, locations, Detention Ivied BOOK, Yes X JMS to 0.1 Internal - may
Journal (0.1) LEJIS #, Projected Release Officers 1-10US, go away with
See JMS Tab and Release info from JIYIS - RELE, LNBR integrated
Uses standard IMS solution
transactions to IFCS
0J-02 PHReD Personnel info from PHReD Detention Low No When new X PHReD to
by serial number - Fills in Officers DO info 0.1
DO info when serial number added -
entered new hires,
etc.

SERIAL 13139-RFP
ID Primary Direction
IIIIMHIMIIIIIIIIIIIIII Interface/Dat Description Stakeholder Compl Trans NE Trigger Frequency Volume 0 U IN & IBMIIIIIIIIIIIIIII Involved Comment
a Exchan e exi ID/ note Lo ic
CT OP- Court Inmate appointments, Court Transportatio IAX120, set of ilivIS to Internal - may
01 Operations cards, Wheelchair n, Court IARI6ORP, Daily files Court Ops go away with
See XVIS Tab notifications, Keepaway Security TAR! 27, processed integrated
info, transportation TAR200RQ, just after solution
warnings, and inmates with IAR200RP, midnight
multiple appts IAR I 7ORP
CT OP- Court Inmate appointments, Court Transportatio TART 27, Multiple Daily set of .TMS to Internal - may
02 Transportation cards, Wheelchair rt IAR135RP, Transportati go away with
See AVIS Tab notifications, Keepaway IAR14ORP, processed on integrated
info, transportation IAR150RF, just after solution
warnings, and inmates with IAR150RP, midnight
multiple appts IAR16ORP,
IARI7ORP,
IAR2OORP,
FAR2OORQ,
IAX120S
SAP-01 SAP Business Inmate Account, Ledger and MCSO Daily IFCS to SAP Internal - may
One Cash Storage Location Finance go away with
Accounting activity - Used to keep the integrated
System accounting system in sync solution
See IFCS Tab with Inmate fund account
activity.
IIIII 11111
SAP-02 SAP Business Check Number, Voided MCSO As needed SAP to IFCS internal mal y-may h
One Checks and AP Reversal Finance
Accounting activity - Used to store the integrated
System check numbers in the Inmate solution
See SAP Tab Fund module, as well as
voiding checks or reversing
AP transactions.
ID Primary Direction Systems
IIIIIIIIIII
Interface/Dat Description Stakeholder Compi Trans Trigger Frequency Volume Ill OU IN & Involved Comment
a Exchan e ex' ID/Queue IN Lo ie T OUT
RFT-01 1111 IMS Alphabetic Mini Roster ow DER010.0T Daily File Daily .IMS to CT-IS Tnreehpedeesas etoarbee
that
somewhere so
CHS folks can
RPT-02 III JbMFS Allpittya i betic Mini Roster Low DER015.0T Daily File Daily J1VIS to CHS Trehpe,sortse access artheat
put
somewhere so
CRS folks can
1111 access

SERIAL 13139-RFP
ID Primary Direction Systems
Interface/bat Description Stakeholder Compl Trans IIE? Trigger Frequency Volume IN OU IN & Involved Comment
a Exchange exity ID/Queue Logic T OUT
RPT-03 CBS JMS Manday Jail CBS Low DER060.0T Yes Monthly Monthly X JMS to CBS These are
Population File reports that
need to be put
somewhere so
CBS folks can
access
RPT-04 CBS JIVIS Inmate Release CHS Low DER170.01 Yes Daily File Daily X JMS to CHS These are
reports that
need to be put
somewhere so
CHS folks can
access
RPT-05 CBS r DAS Medical Status List CBS Low BKR020 Yes Daily File Daily X .11vIS to CBS These are
Update reports that
need to be put
somewhere so
CBS folks can
access
RPT-06 CHS .1MS Medical Compliance CHS Low BKR060 Yes Daily File Daily X IMS to CBS These are
by Facility reports that
need to be put
somewhere so
CBS folks can
access
RPT-07 CBS JWIS Medical Status List CBS Low BKR030.0T Yes Weekly Daily X JMS to CBS These are
Update - weekly File reports that
need to be put
somewhere so
CBS folks can
access
RFT-08 CHS JMS Prisoner Roster - CHS Low DER015.M Yes Daily Ele Weekly X IMS to CHS These are
Durango reports that
need to be put
somewhere so
CBS folks can
access
RFT-09 CBS JMS Prisoner Roster - CHS Low DER015.N Yes Daily File Daily X JMS to CBS These are
Estrella reports that
need to be put
somewhere so
CBS folks can
access
RPT-10 CBS JMS Prisoner Roster - CBS Low DER015.0 Yes Daily File Daily X JMS to CHS These are
Madison reports that
need to be put
somewhere so
CHS folks can
access

SERIAL 13139-RFP
ID Primary Direction Systems
Interface/Dat Description Stakeholder Compl Trans IIE? Trigger Frequency Volume IN OU IN & Involved Comment
a Exchange exity ID/Queue Logic T OUT
RPT-I I CRS /MS Prisoner Roster- Tent CHS Low DEMIST' Yes Daily File Daily X /MS to CHS These are
reports that
need to be put
somewhere so
CHS folks can
access
RPT-12 CHS /MS Prisoner Roster - C115 Low DER015.Q Yes Daily File Daily X JMS to CHS These are
Towers reports that
need to be put
somewhere so
CHS folks can
access
RPT-I3 CHS IMS Prisoner Roster- Misc CHS Low DER015.R Yes Daily File Daily X /MS to CHS These are
reports that
need to be put
somewhere so
CHS folks can
access
RPT-I4 CHS .1MS Alphabetic Mini CHS Low DER008.A Yes Daily File Daily X /MS to CHS These are
Roster Durango reports that
need to be put
somewhere so
CHS folks can
access
RPT-15 CHS /MS Alphabetic Mini CHS Low DER008.B Yes Daily File Daily X JMS to CHS These are
Roster Estrella reports that
need to be put
somewhere so
CHS folks can
access
RPT-16 CHS IMS Alphabetic Mini CHS Low DER008.D Yes Daily File Daily X JMS to CHS These are
Roster Tents reports that
need to be put
somewhere so
CHS folks can
access
RPT-17 CHS JMS Alphabetic Mini CHS Low DER008.E Yes Daily File Daily X JMS to CHS These are
Roster Towers reports that
need to be put
somewhere so
CHS folks can
access
RPT-18 CHS JMS Alphabetic Mini CHS Low DER008.6 Yes Daily File Daily X .IMS to CHS These are
Roster Misc reports that
need to be put
somewhere so
CHS folks can
access

SERIAL 13139-REP
ID Primary Direction Systems
Interface/Oat Description Stakeholder Compl Trans HE? Trigger Frequency Volume IN OU IN & Involved Comment
a Exchange exity ID/Queue Logic T OUT
RPT-i 9 CHS iMS Alphabetic Mini CHS Low DER008.H Yes Daily File Daily X IMS to CHS These are
Roster 4th Ave reports that
need to be put
somewhere so
CHS folks can
access
APT-20 CHS 1MS Alphabetic Mini CHS Low DER008„I Yes Daily File Daily X JMS to CHS These are
Roster LB' reports that
need to be put
somewhere so
CHS folks can
access
RPT-2I CHS State Hospital - Booking CHS Med Yes Daily File Daily X JMS to iCIS
and Release Data
RPT-22 ICJIS Bookings and Releases ICHS Mled Yes Daily File Daily X
RPT-23 ICES Monthly Summary of ICJIS Med Yes Monthly Monthly X IMS to
Felony Booking Stats File ICJIS
RPT-24 JCJIS ICISF/2005 ICJIS Med Yes Daily File Daily @ X /MS to
2;00am ICJIS
RPT-25 ICJIS ICIST/2007 ICJIS /vied Yes Daily File Daily @ X JMS to
5:00pm ICJIS
RPT-26 AHCCCS data Booking and Release info AHCCCS Data File Yes Daily at 400/clay X AVIS to
feed (last 24 hours) -Identify 4:00pm AHCCCS
persons to remove from
AHCCCS roles and to ADD
back into rotes
RPT-27 Diamond Pharmacy data feed FARM Yes X J.MS to
Pharmacy Diamond
Data
APT-28 ASH Data Booked for certain ARS ASU I Yes X JlviS to ASU
Feed codes
RPT-29 County Bond Receipt info County Low BFRC Yes As bonds 50/day X JNIS to
Finance Bond Finance created Finance
Receipt Image Clerk of
Court
APT-30 County Voided Bond Receipt info County Low BONZ YAs voids <5/day X IMS to
Finance Bond Finance created Finance
Receipt VOID Clerk of
Court
APT-31 Scars, Marks and Tattoos - Low VAL02 Yes X IMS to
Behavioral Health Data Magellan

SERIAL I3139-RFP
ID Primary Direction Systems
Interface/Dat Description Stakeholder Compl Trans TIE? Trigger Frequency Volume IN OU IN & Involved Comment
a Exchange exity ID/Queue Logic T OUT
RPT-32 Charge info - Behavioral Med VAL03 Yes NIS to
Health Data Magellan
RPT-33 TRIS/Justware Booking, Unsentenced Indigent Med Yes X
Inmate, Bonds & Release Representati
Data on, Public
Defender
RPT-34 IRIS/Justware Defendant Roster Public Med Yes
Defender
RPT-35 JOLTS JOLTS (Juvenile On-Line Juvenile Ivied Yes
Tracking System)

SERIAL 13139-RFP
APPENDIX 3 - WAIVER OF CLAIMS
SERIAL 13139—RFP
Attached hereto is the waiver of claims required by the County pursuant to section 7.3.1.2 of this Master Services
Agreement.

SERIAL 13139-REP
WAIVER OF CLAIMS 13139-RFP
TO: MARICOPA COUNTY ("County")
AND TO: SYSCON JUSTICE SYSTEMS CANADA LTD. ("Syscon")
FROM: TANTUS SOLUTIONS GROUP INC. ("Tantus")
WHEREAS Syscon and County are negotiating a Master Services Agreement dated for reference June 1, 2015 (the
"MSA") under which the County will engage Syscon to replace its current Jail Management System ("JMS") and other
legacy detention systems with a comprehensive new JMS (the "Project") on the terms and conditions to be set out in
the MSA;
AND WHEREAS Tantus intends to be a subcontractor to Syscon pursuant to the terms of a Subcontracting Agreement
between Syscon and Tantus to be entered into by them (the "Subcontract"), under which Tantus will provide interface
and data conversion products and services (the "Subcontracted Work") in respect of the Project on the terms and
conditions to be set out in the Subcontract;
AND WHEREAS, pursuant to the terms of the MSA, Syscon (as between Syscon and the County) will be responsible
for the full delivery of the Project, and the County will pay Syscon solely for the delivery thereof, notwithstanding that
Syscon will have subcontracted the Subcontracted Work to Tantus, and Syscon will be responsible for paying Tantus
for the Subcontracted Work, pursuant to the terms of the Subcontract;
NOW THEREFORE, for good and valuable consideration (including the direct and indirect benefit to be received by
Tantus from MCSO and Syscon in connection with the Subcontracted Work and its involvement in the Project),
acknowledged by Tantus as received and sufficient, and intending to be legally bound, Tantus agrees with the County
and Syscon that:
(a) as between Syscon and the County, Syscon shall have the sole responsibility (and for greater
certainty, the County shall have no responsibility) to pay Tantus for its performance or delivery of all aspects
of the Subcontracted Work;
(b) Tantus (and its personnel) shall act only as subcontractor through Syscon in respect of the Project and
nothing in the MSA or the Subcontract will be deemed to create a direct contractual relationship between
Tantus (or such personnel) and the County; and
(b) if Syscon should for any reason fail to pay Tantus, or any person acting for or through Tantus, in
accordance with the terms of the Subcontract, or should Tantus, or any such person, otherwise have any claim,
action, demand or complaint for payment for its supply of labor or materials in connection with the Project
(each a "Claim"), Tantus hereby irrevocably releases, disclaims and forever discharges the County from any
and all such Claims, and agrees that any and all such Claims shall be solely made against Syscon and governed
by the terms of the Subcontract.
DATED this 20th day of May 2015,
I am signing this Waiver of Claims on behalf of Tantus as a
duly authorized representative of Tennis with the full
authority to hind Tantus to the terms hereof_
Name: Glenn De Roy
Title: Chief Executive Officer