Extracted text (via pymupdf)
2265405 characters
MOTOROLA, MOTO, MOTOROLA SOLUTIONS, and the Stylized M Logo are trademarks or registered trademarks of Motorola Trademark Holdings,
LLC and are used under license. All other trademarks are the property of their respective owners. © 2024 Motorola Solutions, Inc. All rights reserved.
Maricopa County, AZ
Contract Documentation
CAD/RMS AND MOBILE SYSTEMS SUPPORT AND MAINTENANCE
230055-RFP
Table of Contents
Page 1
Table of Contents
Section 1....................................................................................................................................2
Contract – CAD/RMS AND MOBILE SYSTEMS SUPPORT AND MAINTENANCE 230055-
RFP ............................................................................................................................................2
Section 2..................................................................................................................................29
Exhibit A: Vendor Information...............................................................................................29
Section 3................................................................................................................................ 3-1
Exhibit A-1: Pricing Information.......................................................................................... 3-1
Section 4....................................................................................................................................5
Exhibit B: System Description ................................................................................................5
Section 5..................................................................................................................................74
Exhibit B-1: Interface Functional Design Documents .........................................................74
Section 6..................................................................................................................................75
Exhibit C: Statement of Work ................................................................................................75
Section 7................................................................................................................................148
Exhibit C-1: Project Schedule..............................................................................................148
Section 8................................................................................................................................175
Exhibit D: PremierOne Training Plan..................................................................................175
Section 9................................................................................................................................201
Exhibit E: Master Customer Agreement & Addenda .........................................................201
Section 10............................................................................................................................ 10-1
Exhibit F: CAD Functional Response Matrix.................................................................... 10-1
Section 11............................................................................................................................ 11-1
Exhibit G: RMS Functional Response Matrix................................................................... 11-1
Section 12............................................................................................................................ 12-1
Exhibit H: Exhibit Reserved............................................................................................... 12-1
Section 13..................................................................................................................................2
Exhibit I – Service Level Agreement .......................................................................................2
Section 14............................................................................................................................ 14-1
Exhibit J: Motorola Proposal (Reference Document)...................................................... 14-1
Page 2
Section 1
Contract – CAD/RMS AND
MOBILE SYSTEMS SUPPORT
AND MAINTENANCE 230055-
RFP
CONTRACT CAD/RMS AND MOBILE SYSTEMS SUPPORT
AND MAINTENANCE 230055-RFP
This contract (“Contract”, “Agreement”) is entered into this 11th day of September, 2024 by and between
Maricopa County (“County”, “Customer”), a political subdivision of the State of Arizona, and Motorola
Solutions, Inc., a Delaware corporation (“Contractor”, “Motorola”) for the purchase of Computer Aided
Dispatch (CAD), Records Management System (RMS), Mobile Systems, Field Based Reporting (FBR),
Civil Process, Support, Maintenance and related services.
1.0
CONTRACT TERM
This contract is for a term of ten years, beginning on the 11th day of September 2024 and ending
the 31st day of August 2034.
2.0
OPTION TO RENEW
The County may, at its option and with the concurrence of the Contractor, renew the term of this
contract up to a maximum of ten additional year(s), (or at the County’s sole discretion, extend the
contract on a month-to-month basis for a maximum of six months after expiration). The
Contractor shall be notified in writing by the Office of Procurement Services of the County’s
intention to renew the contract term at least 60 calendar days prior to the expiration of the original
contract term. The Contractor reserves the right to renegotiate pricing at the time of each
renewal. Renewals are subject to price adjustments as outlined in Section 4 of this contract.
Page 3
3.0
CONTRACT COMPLETION
In preparation for contract completion, the Contractor shall make all reasonable efforts for an
orderly transition of its duties and responsibilities to another provider and/or to the County. This
may include, but is not limited to, preparation of a transition plan and cooperation with the County
or other providers in the transition. The transition includes the transfer of all records and other
data in the possession, custody, or control of the Contractor that are required to be provided to
the County either by the terms of this agreement or as a matter of law. The provisions of this
clause shall survive the expiration or termination of this agreement.
4.0
PRICE ADJUSTMENTS
Any requests for reasonable price adjustments must be submitted 60 calendar days prior to the
start of the sixth year of the initial contract term. Requests for adjustment in cost of labor and/or
materials must be supported by appropriate documentation. The reasonableness of the request
will be determined by comparing the request with the Consumer Price Index or by performing a
market survey. If County agrees to the adjusted price terms, County shall issue written approval
of the change and provide an updated version of the contract. The new change shall not be in
effect until the date stipulated on the updated version of the contract. If County does not agree to
the adjusted price terms beyond the sixth year of the initial term, this Agreement shall terminate.
5.0
INFLATION ADJUSTMENT
For multi-year agreements, at the end of the fifth year of the original contract term and each
subsequent renewal term thereafter, a CPI percentage change calculation shall be performed
using the U.S. Department of Labor, Consumer Price Index, all Items, Unadjusted Urban Areas
(CPI-U). Should the annual inflation rate increase greater than 4% during the previous year,
Motorola shall have the right to increase all future maintenance prices by the CPI increase
amount exceeding 4%, not seasonally adjusted shall be used as the measure of CPI for this price
adjustment. The adjustment calculation will be based upon the CPI for the most recent twelve
(12) month increment beginning from the most current month available as posted by the U.S.
Department of Labor (http://www.bls.gov) immediately preceding the new maintenance term. For
purposes of illustration, if in Year 5 the CPI reported an increase of 8%, Motorola may increase
the Year 6 price by 4% (8% - 4% base). Any pricing change would be documented in a change
order executed with the Customer.
6.0
PAYMENTS
6.1
As consideration for performance of the duties described herein, County shall pay
Contractor the sum(s) stated in Exhibit A-1 – Pricing Sheet.
6.2
Payment shall be made per the payment terms in Exhibit A upon the County’s receipt of a
properly completed invoice. Late payments will be subject to interest charges at the
maximum rate permitted by law, commencing upon the due date.
6.3
INVOICES
6.3.1
The Contractor will invoice Customer at the frequency set forth in the applicable
Addendum or Ordering Document electronically via email, and Customer agrees
to receive invoices via email at the email address set forth in an Ordering
Document. The Contractor shall submit one legible copy of their detailed invoice
before payment(s) will be made. Incomplete invoices will not be processed. At a
minimum, the invoice must provide the following information:
•
Company name, address, and contact information
•
County bill-to name and contact information
•
Contract serial number
Page 4
•
County purchase order number
•
Project name and/or number
•
Invoice number and date
•
Payment terms
•
Date of service or delivery
•
Quantity
•
Contract item number(s)
•
Description of purchase (product or services)
•
Pricing per unit of purchase
•
Extended price
•
Total amount due
6.3.2
Labor, services, and maintenance must be billed as a separate line item.
6.3.3
Problems regarding billing or invoicing shall be directed to the department as
listed on the purchase order.
6.3.4
Payment shall only be made to the Contractor by Accounts Payable through the
Maricopa County Vendor Express Payment Program. This is an electronic funds
transfer (EFT) process. After contract award, the Contractor shall complete the
Vendor Registration Form accessible from the County Department of Finance
Vendor
Registration
Web
Site
https://www.maricopa.gov/5169/Vendor-
Information.
6.3.5
Discounts offered in the contract shall be calculated based on the date a properly
completed invoice is received by the County.
6.3.6
EFT payments to the routing and account numbers designated by the Contractor
shall 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.
6.4
CRITERIA FOR DELIVERY AND ACCEPTANCE OF DELIVERABLES
6.4.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.
6.4.1.1 County
Representative
shall
review
and
validate
Contractor’s
Deliverables product prior to Acceptance. Acceptance criteria for
Deliverables shall consist of the following:
6.4.1.1.1 Specific Deliverables are completed as specified in this
Contract and the final Deliverable has been rendered.
6.4.1.1.2 Plans, schedules, designs, documentation, and reports are
approved and completed as specified in this Contract.
6.4.1.1.3 All supporting Documentation is provided and completed.
6.4.1.1.4 All Deliverables are presented to County in the approved
format (or if no such format is approved, in an industry-
standard format).
Page 5
6.4.1.1.5 All Deliverables are at the agreed upon acceptable level of
quality as defined in this Contract.
6.4.2
SOFTWARE/SYSTEM ACCEPTANCE PROCESS
6.4.2.1 The acceptance process and criteria set out in this section shall apply
strictly to the initial implementation project and will not apply post
warranty.
6.4.2.2 Acceptance for the Products 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.
6.4.2.3 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.
6.4.2.4 System testing shall be performed in accordance with Exhibit C -
Statement of Work.
6.5
SOFTWARE UPDATES, WARRANTY, MAINTENANCE & ROADMAP
6.5.1
Contractor shall make available to County at no additional charge updates,
upgrades and releases to the Products as they are released and in accordance
with Exhibit I – Service Level Agreement and the Subscription Software
Addendum in Exhibit E, 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 updates, upgrades and
releases to the Products and support them 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 Products
6.5.2
To ensure that Documentation is consistent with the operating environment,
Contractor shall provide release notes concurrently with every update, upgrade
and release to the Products where the functionality documented has materially
been changed, or the cumulative effect of previous updates, upgrades and
releases has rendered the functionality documented to have materially changed.
6.6
INTENTIONALLY OMITTED.
6.7
APPLICABLE FEES AND TAXES
6.7.1
Fees. For purposes of this Contract the definitions of Products and Services are
as defined in Exhibit E. Fees and charges applicable to the Products and
Services (the “Fees”) will be as set forth in Exhibit A-1 or the applicable purchase
order, and such Fees may be changed by Motorola with a minimum ninety (90)
days’ notice, except that Motorola will not change the Fees for Products and
Services as set forth in Exhibit A-1 or the Fees for Products and Services
purchased by Customer during the term of an active purchase order. Changes in
the scope of Services described in a change order may require an adjustment to
Page 6
the Fees due under such purchase order. If a specific invoicing or payment
schedule is set forth in Exhibit A-1 or a purchase order, such schedule will apply
solely with respect to Exhibit A-1 or such purchase order. Unless otherwise
specified in the applicable change order, the Fees for any Services exclude
expenses associated with unusual and costly Site access requirements (e.g., if
Site access requires a helicopter or other equipment), and, with Customer’s prior
written approval, Customer will reimburse Motorola for these, or other expenses
incurred by Motorola in connection with the Services.
6.7.2
Taxes. The Fees do not include any excise, sales, lease, use, property, or other
taxes, assessments, duties, or regulatory charges or contribution requirements
(collectively, “Taxes”), all of which will be paid by Customer, except as exempt by
law, unless otherwise specified in a purchase order. If Motorola is required to pay
any Taxes, Customer will reimburse Motorola for such Taxes (including any
interest and penalties) within thirty (30) days after Customer’s receipt of an
invoice, therefore. Customer will be solely responsible for reporting the Products
for personal property tax purposes, and Motorola will be solely responsible for
reporting taxes on its income and net worth. It is the responsibility of the
Contractor to determine any and all applicable taxes and include those taxes in
all invoices to be paid by the County. The legal liability to remit the tax is on the
entity conducting business in Arizona. Tax is not a determining factor in contract
award.
6.7.3
Tax Indemnification: Contractor and all subcontractors shall pay all Federal,
State, and local taxes applicable to their 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
workers’
compensation. Contractor may be required to establish, to the satisfaction of
County, that any and all fees and taxes due to the municipality or the State of
Arizona for any license or transaction privilege taxes, use taxes, or similar excise
taxes are currently paid (except for matters under legal protest).
7.0
AVAILABILITY OF FUNDS
7.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. The Contractor shall be under no
obligation to provide goods and/or services unless the availability of funds has been
confirmed.
7.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 and equipment delivered prior to
the effective date of the termination, provided that such services and equipment are 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
30 days in advance.
Page 7
8.0
INTENTIONALLY OMITTED.
9.0
INTENTIONALLY OMITTED.
10.0
DUTIES
10.1
The Contractor shall perform all duties stated in Exhibit C – Scope of Work, or as
otherwise mutually agreed in writing and signed by both parties.
10.2
During the contract term, County may provide Contractor’s personnel with adequate
workspace for consultants and such other related facilities as may be required by
Contractor to carry out its contractual obligations.
11.0
TERMS AND CONDITIONS
11.1
INDEMNIFICATION
11.1.1
To the fullest extent permitted by law, the contractor shall defend, indemnify, and
hold harmless the County (as Owner), its agents, representatives, officers,
directors, officials, and employees from and against all claims, damages, losses,
and expenses (including, but not limited to attorneys' fees, court costs, expert
witness fees, and the costs and attorneys' fees for appellate proceedings) arising
out of, or alleged to have resulted from, the gross negligence or negligent acts, or
omissions of the contractor, a subcontractor, anyone directly or indirectly
employed by them, or anyone for whose acts they may be liable, relating to the
performance of this contract.
11.1.2
Contractor's duty to defend, indemnify, and hold harmless the County, its agents,
representatives, officers, directors, officials, and employees shall arise in
connection with any claim, damage, loss, or expense that is attributable to bodily
injury, sickness, disease, death, or injury to, impairment of, or destruction of
tangible property, including loss of use resulting therefrom, caused by negligent
acts, or omissions, in the performance of this contract, but only to the extent
caused by the negligent acts or omissions of the contractor, a subcontractor,
anyone directly or indirectly employed by them, or anyone for whose acts they
may be liable, regardless of whether or not such claim, damage, loss, or expense
is caused in part by a party indemnified hereunder.
11.1.3
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 section.
11.1.4
The scope of this indemnification does not extend to the sole negligence of
County.
11.2
INTELLECTUAL PROPERTY INFRINGEMENT
11.2.1
Intellectual Property Infringement. Contractor will defend County against any
third-party claim alleging that a Contractor-developed or manufactured Product or
Service (the “Infringing Product”) directly infringes a United States patent or
copyright (“Infringement Claim”), and Contractor will pay all damages finally
awarded against County by a court of competent jurisdiction for an Infringement
Claim, or agreed to in writing by Contractor in settlement of an Infringement
Claim. Contractor’s duties under this Section – Intellectual Property Infringement
are conditioned upon: (a) County promptly notifying Motorola in writing of the
Infringement Claim; (b) Contractor having sole control of the defense of the suit
and all negotiations for its settlement or compromise; and (c) County cooperating
Page 8
with Contractor and, if requested by Contractor, providing reasonable assistance
in the defense of the Infringement Claim.
11.2.2
If an Infringement Claim occurs, or in Contractor’s opinion is likely to occur,
Contractor may at its option and expense: (a) procure for County the right to
continue using the Infringing Product; (b) replace or modify the Infringing Product
so that it becomes non-infringing; or (c) grant County (i) a prorated refund of any
amounts prepaid for the Infringing Product (if the Infringing Product is a software
Product, i.e., Licensed Software or Subscription Software) or (ii) a credit for the
Infringing Product, less a reasonable charge for depreciation (if the Infringing
Product is Equipment, including Equipment with embedded software.
11.2.3
In addition to the other damages disclaimed under this Agreement, Contractor
will have no duty to defend or indemnify County for any Infringement Claim that
arises from or is based upon: (a) Customer Data, Customer-Provided Equipment,
Non-Motorola Content, or third-party equipment, hardware, software, data, or
other third-party materials; (b) the combination of the Product or Service with any
products or materials not provided by Contractor; (c) a Product or Service
designed, modified, or manufactured in accordance with County’s designs,
specifications, guidelines or instructions; (d) a modification of the Product or
Service by a party other than Contractor; (e) use of the Product or Service in a
manner for which the Product or Service was not designed or that is inconsistent
with the terms of this Agreement; or (f) the failure by County to use or install an
update to the Product or Service that is intended to correct the claimed
infringement. In no event will Contractor’s liability resulting from an Infringement
Claim extend in any way to any payments due on a royalty basis, other than a
reasonable royalty based upon revenue derived by Contractor from County from
sales or license of the Infringing Product.
11.2.4
This Section – Intellectual Property Infringement provides County’s sole and
exclusive remedies and Contractor’s entire liability in the event of an Infringement
Claim. For clarity, the rights and remedies provided in this Section are subject to,
and limited by, the restrictions set forth in Section 11.3 (LIMITATION OF
LIABILITY).
11.3
LIMITATION OF LIABILITY
11.3.1
DISCLAIMER OF CONSEQUENTIAL DAMAGES. EXCEPT FOR PERSONAL
INJURY OR DEATH, CONTRACTOR, ITS AFFILIATES, AND ITS AND THEIR
RESPECTIVE OFFICERS, DIRECTORS, EMPLOYEES, SUBCONTRACTORS,
AGENTS,
SUCCESSORS,
AND
ASSIGNS
(COLLECTIVELY,
THE
“MOTOROLA PARTIES”) WILL NOT BE LIABLE IN CONNECTION WITH THIS
AGREEMENT
(WHETHER
UNDER
CONTRACTOR’S
INDEMNITY
OBLIGATIONS, A CAUSE OF ACTION FOR BREACH OF CONTRACT, UNDER
TORT THEORY, OR OTHERWISE) FOR ANY INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, PUNITIVE, OR CONSEQUENTIAL DAMAGES OR
DAMAGES FOR LOST PROFITS OR REVENUES, EVEN IF CONTRACTOR
HAS BEEN ADVISED BY COUNTY OR ANY THIRD PARTY OF THE
POSSIBILITY OF SUCH DAMAGES OR LOSSES AND WHETHER OR NOT
SUCH DAMAGES OR LOSSES ARE FORESEEABLE.
11.3.2
DIRECT DAMAGES. EXCEPT FOR PERSONAL INJURY OR DEATH, THE
TOTAL AGGREGATE LIABILITY OF THE MOTOROLA PARTIES, WHETHER
BASED ON A CLAIM IN CONTRACT OR IN TORT, LAW OR EQUITY,
RELATING TO OR ARISING OUT OF THE AGREEMENT WILL NOT EXCEED
THE FEES SET FORTH IN THE ORDERING DOCUMENT UNDER WHICH THE
CLAIM
AROSE.
NOTWITHSTANDING
THE
FOREGOING,
FOR
ANY
Page 9
SUBSCRIPTION SOFTWARE OR FOR ANY RECURRING SERVICES, THE
MOTOROLA PARTIES’ TOTAL LIABILITY FOR ALL CLAIMS RELATED TO
SUCH PRODUCT OR RECURRING SERVICES IN THE AGGREGATE WILL
NOT EXCEED THE TOTAL FEES PAID FOR SUCH SUBSCRIPTION
SOFTWARE OR RECURRING SERVICE, AS APPLICABLE, DURING THE
CONSECUTIVE TWELVE (12) MONTH PERIOD IMMEDIATELY PRECEDING
THE EVENT FROM WHICH THE FIRST CLAIM AROSE.
11.3.3
ADDITIONAL EXCLUSIONS. NOTWITHSTANDING ANY OTHER PROVISION
OF THIS AGREEMENT, CONTRACTOR WILL HAVE NO LIABILITY FOR
DAMAGES ARISING OUT OF (A) CUSTOMER DATA, INCLUDING ITS
TRANSMISSION TO CONTRACTOR, OR ANY OTHER DATA AVAILABLE
THROUGH THE PRODUCTS OR SERVICES; (B) CUSTOMER-PROVIDED
EQUIPMENT, NON-MOTOROLA CONTENT, THE SITES, OR THIRD-PARTY
EQUIPMENT, HARDWARE, SOFTWARE, DATA, OR OTHER THIRD-PARTY
MATERIALS, OR THE COMBINATION OF PRODUCTS AND SERVICES WITH
ANY
OF
THE
FOREGOING;
(C)
LOSS
OF
DATA
OR
HACKING,
RANSOMWARE, OR OTHER THIRD-PARTY ATTACKS OR DEMANDS; (D)
MODIFICATION OF PRODUCTS OR SERVICES BY ANY PERSON OTHER
THAN
CONTRACTOR;
(E)
RECOMMENDATIONS
PROVIDED
IN
CONNECTION WITH OR BY THE PRODUCTS AND SERVICES; (F) DATA
RECOVERY SERVICES OR DATABASE MODIFICATIONS; OR (G) COUNTY’S
OR ANY AUTHORIZED USER’S BREACH OF THIS AGREEMENT OR MISUSE
OF THE PRODUCTS AND SERVICES.
11.3.4
Voluntary Remedies. Contractor is not obligated to remedy, repair, replace, or
refund the purchase price for the disclaimed issues in Section 11.3.3 –
Additional Exclusions above, but if Contractor agrees to provide Services to
help resolve such issues, County will reimburse Contractor for its reasonable
time and expenses, including by paying Contractor any Fees set forth in an
Ordering Document for such Services, if applicable.
11.3.5
Statute of Limitations. County may not bring any claims against a Motorola Party
in connection with this Agreement or the Products and Services more than one
(1) year after the date of accrual of the cause of action.
11.4
INSURANCE
11.4.1
Contractor, at Contractor’s own expense, shall purchase and maintain, at a
minimum, the herein stipulated insurance from a company or companies duly
licensed by the State of Arizona and possessing an AM Best, Inc. category 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.
11.4.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.
11.4.3
In the event that the insurance required is written on a claims-made basis,
Contractor warrants that any retroactive date under the policy shall precede the
effective date of this contract and either continuous coverage will be maintained,
or an extended discovery period will be exercised for a period of two years
beginning at the time work under this contract is completed.
Page 10
11.4.4
Contractor’s General Liability and Automobile Liability insurance shall be primary
insurance as respects County, and any insurance or self-insurance maintained
by County shall not contribute to it.
11.4.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.
11.4.6
The insurance policies required by this contract, except Workers’ Compensation
and Errors and Omissions/Cyber Liability, shall include County, its agents,
representatives, officers, directors, officials, and employees as additional
insureds.
11.4.7
The policies required hereunder, except Workers’ Compensation and Errors and
Omissions/Cyber 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.
11.4.8
If available, the insurance policies required by this contract may be combined
with Commercial Umbrella Insurance policies to meet the minimum limit
requirements. If a Commercial Umbrella insurance policy is utilized to meet
insurance requirements, the Certificate of Insurance shall indicate which lines the
Commercial Umbrella Insurance covers.
11.4.8.1 Commercial General Liability
Commercial General Liability (CGL) insurance and, if necessary,
Commercial Umbrella insurance with a limit of $2,000,000 for each
occurrence, $4,000,000 Products/Completed Operations Aggregate, and
$4,000,000 General Aggregate Limit. The policy shall include coverage
for premises liability, bodily injury, broad form property damage, personal
injury, products and completed operations and blanket contractual
coverage, and shall not contain any provisions which would serve to limit
third party action over claims. There shall be no endorsement or
modifications of the CGL limiting the scope of coverage for liability
arising from explosion, collapse, or underground property damage.
11.4.8.2
Automobile Liability
Commercial/Business Automobile Liability insurance with a combined
single limit for bodily injury and property damage of $2,000,000 each
occurrence with respect to any of the Contractor’s owned, hired, and
non-owned vehicles assigned to or used in performance of the
Contractor’s work or services or use or maintenance of the premises
under this contract.
11.4.8.3
Workers’ Compensation
11.4.8.3.1
Workers’ compensation insurance to cover obligations
imposed by Federal and State statutes having jurisdiction
of Contractor’s employees engaged in the performance of
the work or services under this contract; and Employer’s
Liability insurance of $1,000,000 for each accident,
Page 11
$1,000,000 disease for each employee, and $1,000,000
disease policy limit.
11.4.8.3.2 Contractor, its subcontractors, and sub-subcontractors
waive all rights against this contract and its agents,
officers, directors, and employees for recovery of damages
to the extent these damages are covered by the workers’
compensation and Employer’s Liability, or Commercial
Umbrella Liability insurance obtained by Contractor, its
subcontractors, and its sub-subcontractors pursuant to this
contract.
11.4.8.4
Errors and Omissions/Professional Liability Insurance
Technology Errors & Omission insurance: Such insurance shall cover
any and all errors, omissions, or negligent acts in the delivery of
products, services, and/or licensed programs under this contract.
x
Each claim $5,000,000
Aggregate $5,000,000
In the event that the Technology Errors & Omission insurance required
by this contract is written on a claims-made basis, contractor warrants
that any retroactive date under the policy shall precede the effective
date of this contract and, either continuous coverage will be
maintained, or an extended discovery period will be exercised for a
period of two years, beginning at the time work under this contract is
completed.
11.4.8.5 Cyber, Network Security, and Privacy Liability
Cyber, Network Security and Privacy Liability Insurance with a limit of
$5,000,000 per claim / $5,000,000 Aggregate. The policy shall include,
but not be limited to; coverage for all directors, officers, agents and
employees of the Contractor, losses with respect to network risks
(such as data breaches, unauthorized access or use, and ID theft of
data), invasion of privacy (regardless of the type of media involved in
the loss of private information), crisis management, identity theft
response costs, breach notification costs, credit remediation, and credit
monitoring, defense, and claims expenses, regulatory defense costs
plus fines and penalties, cyber extortion, electronic data restoration
expenses (data asset protection), network business interruption,
computer fraud coverage, funds transfer loss, third-party fidelity, theft,
no requirement for arrest and conviction, and loss outside the premises
of the named insured.
11.4.9
Certificates of Insurance
11.4.9.1
Prior to contract award, Contractor shall furnish the County with valid
and complete Certificates of Insurance, or formal endorsements as
required by the contract in the form provided by the County, issued by
Contractor’s insurer(s), as evidence that policies providing the required
coverage, conditions and limits required by this contract are in full force
and effect. Such certificates shall identify this contract number and title.
11.4.9.2
In the event any insurance policy(ies) required by this contract is (are)
written on a claims-made basis, coverage shall extend for two years
Page 12
past completion and acceptance of Contractor’s work or services and
as evidenced by annual certificates of insurance.
11.4.9.3
If a policy does expire during the life of the Contract, a renewal
certificate must be sent to County at expiration.
11.4.9.4
Certificates of Insurance shall identify Maricopa County as follows:
Maricopa County
c/o Risk Management
301W. Jefferson St, Suite 910
Phoenix, AZ 85003
11.4.10 Cancellation and Expiration Notice
Applicable to all insurance policies required within the insurance requirements of
this contract, Contractor’s insurance shall not be permitted to expire, be
suspended or be canceled without 30 days prior written notice to Maricopa
County. Contractor must provide to Maricopa County, within two business days
of receipt, if they receive notice of a policy that has been or will be suspended or
canceled, has expired, or will be expiring. Such notice shall be sent directly to
Maricopa County Office of Procurement Services and shall be mailed, or hand
delivered to 301 W. Jefferson, Suite 700, Phoenix, AZ 85003, or emailed to the
procurement officer noted in the solicitation.
11.5
FORCE MAJEURE
11.5.1
Neither party shall be liable for failure of performance, nor incur any liability to the
other party on account of any loss or damage resulting from any delay or failure
to perform all or any part of this contract, if such delay or failure is caused by
events, occurrences, or causes beyond the reasonable control and without
negligence of the parties. Such events, occurrences, or causes include, but are
not limited to, acts of God/nature (including fire, flood, earthquake, storm,
hurricane, or other natural disaster), war, invasion, act of foreign enemies,
hostilities (whether war is declared or not), civil war, riots, rebellion, revolution,
insurrection, military or usurped power or confiscation, terrorist activities,
nationalization, government sanction, lockout, blockage, embargo, labor dispute,
strike, and interruption or failure of electricity or telecommunication service, and
pandemic.
11.5.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.
11.5.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.
11.6
ORDERING AUTHORITY
Any request for purchase shall be accompanied by a valid purchase order issued by a
County department or directed by a Certified Agency Procurement Aid (CAPA) with a
purchase card for payment.
Page 13
11.7
PROCUREMENT CARD ORDERING CAPABILITY
County may opt to use a procurement card (Visa or Master Card) to make payment for
orders under this contract.
11.8
INTERNET ORDERING CAPABILITY
It is the intent of Maricopa County to use the Internet to communicate and to place orders
under this contract.
11.9
PURCHASE ORDERS
11.9.1
Customer affirms they have signatory authority to execute this contract. The
contract price of $24,341,461, not including taxes and fees, is fully identified,
including all subsequent years of contracted services, if applicable. The
Customer will pay all valid invoices per the terms of the contract as received from
Motorola and any changes in scope will be subject to the change order process
as described in this Agreement.
11.9.2
Motorola acknowledges the Customer may require the issuance(s) of a purchase
order or notice to proceed as part of the Customer’s procurement process.
However, Customer agrees that the issuance or non-issuance of a purchase
order or notice to proceed does not preclude the Customer from its contractual
obligations as defined in this Agreement.
11.10
BACKGROUND CHECK
Respondents may be required to pass multiple background checks (e.g. Sheriff’s Office,
County Attorney's Office, Courts, as well as Maricopa County general government) to
determine if the respondent is acceptable to do business with the County. This applies to,
but is not limited to, the company, subcontractors, and employees, and the failure to pass
these checks shall deem the respondent non-responsible.
11.11
SUSPENSION OF WORK
The procurement officer may order the Contractor, in writing, to suspend, delay, or
interrupt all or any part of the work of this contract for the period of time that the
procurement officer determines appropriate for the convenience of the County. No
adjustment shall be made under this clause for any suspension, delay, or interruption to
the extent that performance would have been so suspended, delayed, or interrupted by
any other cause, including the fault or negligence of the Contractor. No request for
adjustment under this clause shall be granted unless the claim, in an amount stated, is
asserted in writing as soon as practicable after the termination of the suspension, delay,
or interruption, but not later than the date of final payment under the contract.
11.12
STOP WORK ORDER
11.12.1 The procurement officer may, at any time, by written order to the Contractor,
require the Contractor to stop all, or any part, of the work called for by this
contract for a period of 90 calendar days after the order is delivered to the
Contractor, and for any further period to which the parties may agree. The order
shall be specifically identified as a stop work order issued under this clause.
Upon receipt of the order, the Contractor shall immediately comply with its terms
and take all reasonable steps to minimize the incurrence of costs allocable to the
work covered by the order during the period of work stoppage. Within a period of
90 calendar days after a stop work order is delivered to the Contractor, or within
Page 14
any extension of that period to which the parties shall have agreed, the
procurement officer shall either:
11.12.1.1cancel the stop work order; or
11.12.1.1.1 terminate the work covered by the order as provided in the
Termination for Default or the Termination for Convenience
clause of this contract.
11.12.1.1.2 The procurement officer may make an equitable adjustment
in the delivery schedule and/or contract price, and the
contract shall be modified, in writing, accordingly, if the
Contractor demonstrates that the stop work order resulted in
an increase in costs to the Contractor.
11.13
TERMINATION FOR CONVENIENCE
Maricopa County may terminate the resultant contract for convenience by providing 60
calendar days advance notice to the Contractor. Should the County elect to terminate,
the effects of termination shall be in accordance with Section 11.15 EFFECT OF
TERMINATION OR EXPIRATION of this Agreement.
11.14
TERMINATION FOR DEFAULT
11.14.1 Either party may, by written Notice of Default to the other, terminate this contract
in whole or in part if the other Party breaches a material obligation under the
Agreement, to include but not limited to:
11.14.1.1 deliver the supplies or to perform the services within the time
specified in this contract or any extension;
11.14.1.2 make progress, so as to endanger performance of this contract; or
11.14.1.3 perform any of the other provisions of this contract.
11.14.2 The right to terminate this contract under these subparagraphs may be exercised
if there is a failure to cure within 30 business days (or more if authorized in
writing by both Parties) after receipt of a Notice to Cure specifying the failure.
11.15
EFFECT OF TERMINATION OR EXPIRATION
Except as otherwise required by applicable law or by a court order from a court with
competent jurisdiction, upon termination for any reason or expiration of this Agreement or
a purchase order, County and the Authorized Users will return or destroy (at Contractor’s
option) all Motorola Materials and Motorola’s Confidential Information in their possession
or control and, as applicable, provide proof of such destruction, except that Equipment
purchased by County should not be returned. Except for Termination for Default per
Section 11.14 above, notwithstanding the reason for termination or expiration, County
must pay Contractor:
11.15.1 For goods and services delivered up to the point of termination.
11.15.2 As it applies to the Subscription Based Services, if: (a) Customer chooses early
termination at any time within years one through five of the term of this
Agreement or (b) Motorola terminates this Agreement for cause during these
years, then Customer shall pay to Motorola, within thirty (30) calendar days after
such termination, an amount equal to 50% of the annually recurring charges as
Page 15
set forth in the pricing schedule for the period remaining in years 1 through 5 of
the term of this Agreement.
11.15.3 Notwithstanding anything to the contrary, any up-front fees set forth in a pricing
schedule are non-refundable. Up-front fees are the payments for the PremierOne
Hardware and System Software, Organizational Change Management and
Implementation Services as identified in Exhibit A-1 PRICING INFORMATION
and PAYMENT MILESTONES.
11.16
PERFORMANCE
It shall be the Contractor’s responsibility to meet the proposed performance
requirements. Maricopa County reserves the right to obtain services on the open market
in the event the Contractor fails to perform, and is terminated for uncured breach, the
reasonable price differential may be charged against the Contractor.
11.17
CONTRACTOR EMPLOYEE MANAGEMENT
11.17.1 Contractor shall endeavor to maintain the personnel proposed in their proposal
throughout the performance of this contract.
11.17.2 If Contractor personnel’s employment status changes, Contractor shall provide
County a list of proposed replacements with equivalent or greater experience.
11.17.3 Under no circumstances shall the implementation schedule to be impacted by a
personnel change on the part of the Contractor.
11.17.4 Contractor shall not reassign any key personnel identified in their proposal
without the express consent of the County.
11.17.5 County reserves the right to immediately remove from its premises any
Contractor personnel it determines to be a risk to County operations.
11.17.6 County reserves the right to request the replacement of any Contractor personnel
at any time, for any reason.
11.18
WARRANTY OF SERVICES
11.18.1 Subject to the disclaimers and exclusions below, Contractor represents and
warrants that (a) Services will be provided in a good and workmanlike manner
and will conform in all material respects to the descriptions in the applicable
purchase order; and (b) for a period of ninety (90) days commencing upon the
Service Completion Date (as defined in Exhibit E) and upon written approval by
both parties for one-time Services, the Services will be free of material defects in
materials and workmanship. Other than as set forth in subsection (a) above,
recurring Services are not warranted but rather will be subject to the
requirements of the applicable Addendum or the applicable purchase order.
Contractor provides other express warranties for Contractor-manufactured
Equipment, Contractor-owned software Products, and certain Services. Such
express warranties are included in the applicable Addendum or applicable
purchase order. Such representations and warranties will apply only to the
applicable Product or Service that is the subject of such Addendum or such
purchase order.
11.18.2 Warranty Claims; Remedies. To assert a warranty claim, County must notify
Contractor in writing of the claim prior to the expiration of any warranty period set
forth in this Contract or the applicable Addendum or the applicable purchase
Page 16
order. Unless a different remedy is otherwise expressly set forth for a particular
warranty under an Addendum, upon receipt of such claim, Contractor will
investigate the claim and use commercially reasonable efforts to repair or replace
any confirmed materially non-conforming Product or re-perform any non-
conforming Service. Such remedies are County’s sole and exclusive remedies for
Contractor’s breach of a warranty. Contractor’s warranties are not assignable or
transferrable.
11.18.3 Pass-Through Warranties. Notwithstanding any provision of this Agreement to
the contrary, Contractor will have no liability for third-party software or hardware
provided by Contractor; provided, however, that to the extent offered by third-
party providers of software or hardware and to the extent permitted by law,
Contractor will pass through express warranties provided by such third parties.
11.18.4 WARRANTY DISCLAIMER. EXCEPT FOR THE EXPRESS AND PASS
THROUGH
WARRANTIES
IN
THIS
AGREEMENT,
PRODUCTS
AND
SERVICES PURCHASED HEREUNDER ARE PROVIDED “AS IS” AND WITH
ALL FAULTS. WARRANTIES SET FORTH IN THE AGREEMENT ARE THE
COMPLETE WARRANTIES FOR THE PRODUCTS AND SERVICES AND
CONTRACTOR DISCLAIMS ALL OTHER WARRANTIES OR CONDITIONS,
EXPRESS
OR
IMPLIED,
INCLUDING
IMPLIED
WARRANTIES
OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, AND
QUALITY. CONTRACTOR DOES NOT REPRESENT OR WARRANT THAT
USE OF THE PRODUCTS AND SERVICES WILL BE UNINTERRUPTED,
ERROR-FREE, OR FREE OF SECURITY VULNERABILITIES, OR THAT THEY
WILL MEET COUNTY’S PARTICULAR REQUIREMENT.
11.19
INSPECTION OF SERVICES
11.19.1 The Contractor shall provide and maintain an inspection system acceptable to
County covering the services under this contract. Complete records of all
inspection work performed by the Contractor shall be maintained and made
available to County during contract performance and for as long afterwards as
the contract requires.
11.19.2 County has the right to inspect and test all services called for by the contract, to
the extent practicable at all times and places during the term of the contract.
County shall perform inspections and tests in a manner that will not unduly delay
the work.
11.19.3 If any of the services do not conform to contract requirements, County may
require the Contractor to perform the services again in conformity with contract
requirements, at no cost to the County. When the defects in services cannot be
corrected by re-performance, County may:
11.19.3.1 require the Contractor to take necessary action to ensure that future
performance conforms to contract requirements; and
11.19.3.2 reduce the contract price to reflect the reduced value of the services
performed.
11.19.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:
11.19.4.1 by contract or otherwise, perform the services and charge to the
Contractor, through direct billing or through payment reduction, any
Page 17
cost incurred by County that is directly related to the performance of
such service; or
11.19.4.2 terminate the contract for default.
11.20
USAGE REPORT
The Contractor shall furnish the County a quarterly usage report, upon request,
delineating the acquisition activity governed by the contract. The format of the report shall
be approved by the County and shall disclose the quantity and dollar value of each
contract item by individual unit of measure.
11.21
STATUTORY RIGHT OF CANCELLATION FOR CONFLICT OF INTEREST
Notice is given that, pursuant to A.R.S. § 38-511, the County may cancel any contract
without penalty or further obligation within three years after execution of the contract, if
any person significantly involved in initiating, negotiating, securing, drafting, or creating
the contract on behalf of the County is at any time, while the contract or any extension of
the contract is in effect, an employee or agent of any other party to the contract in any
capacity or consultant to any other party of the contract with respect to the subject matter
of the contract. Additionally, pursuant to A.R.S. § 38-511, the County may recoup any fee
or commission paid or due to any person significantly involved in initiating, negotiating,
securing, drafting, or creating the contract on behalf of the County from any other party to
the contract arising as the result of the contract.
11.22
RESERVED
11.23
SUBCONTRACTING
11.23.1 Neither party may assign to another Contractor or subcontract to another party
for performance of the terms and conditions hereof without the written consent of
the other Party, which shall not be unreasonably withheld. All correspondence
authorizing subcontracting must reference the bid serial number and identify the
job or project.
11.23.2 The subcontractor’s rate for the job shall not exceed that of the prime
Contractor’s rate, as bid in the pricing section, unless the prime Contractor is
willing to absorb any higher rates. The subcontractor’s invoice shall be invoiced
directly to the prime Contractor, who in turn shall pass-through the costs to the
County, without mark-up. A copy of the subcontractor’s invoice must accompany
the prime Contractor’s invoice.
11.24
AMENDMENTS
All amendments to this contract shall be in writing and approved/signed by both parties.
Maricopa County Office of Procurement Services shall be responsible for approving all
amendments for Maricopa County.
11.25
ADDITIONS/DELETIONS OF REQUIREMENTS
The County in agreement with the Contractor reserves the right to add and/or delete
materials and services to a contract. If a service requirement is deleted, payment to the
Contractor will be reduced proportionately to the amount of service reduced in
accordance with the bid price. If additional materials or services are required from a
contract, prices for such additions will be negotiated between the Contractor and the
County.
Page 18
11.26
RIGHTS IN DATA
11.26.1 Subject to Section 10 of Exhibit E, the County shall have the use of data and
reports resulting from a contract without additional cost or other restriction except
as may be established by law or applicable regulation. Each party shall supply to
the other party, upon request, any available information that is relevant to a
contract and to the performance thereunder.
11.26.2 Data, records, reports, and all other information generated for the County by a
third party as the result of a contract are the property of the County and shall be
provided in a format designated by the County or shall be and remain accessible
to the County into perpetuity.
11.27
ACCESS TO AND RETENTION OF RECORDS FOR THE PURPOSE OF AUDIT
AND/OR OTHER REVIEW
11.27.1 In accordance with Section MC1-372 of the Maricopa County Procurement Code,
the Contractor agrees to retain (physical or digital copies of) all books, records,
accounts, statements, reports, files, and other records and back-up
documentation relevant to this contract for six years after final payment or until
after the resolution of any audit questions, which could be more than six years,
whichever is longest. 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. Contractor shall
not be obligated to disclose any information that it treats as confidential or
proprietary in the ordinary course of its business without a signed nondisclosure
agreement between the parties.
11.27.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.
11.28
AUDIT DISALLOWANCES
If at any time it is determined by the County that a cost for which payment has been
made is a disallowed cost, the County shall notify the Contractor in writing of the
disallowance. The course of action to address the disallowance shall be at sole discretion
of the County, and may include either an adjustment to future invoices, request for credit,
request for a check, or a deduction from current invoices submitted by the Contractor
equal to the amount of the disallowance, or to require reimbursement forthwith of the
disallowed amount by the Contractor by issuing a check payable to Maricopa County.
11.29
STRICT COMPLIANCE
Acceptance by County of a performance that is not in strict compliance with the terms of
the contract shall not be deemed to be a waiver of strict compliance with respect to all
other terms of the contract.
11.30
VALIDITY
The invalidity, in whole or in part, of any provision of this contract shall not void or affect
the validity of any other provision of the contract.
Page 19
11.31
SEVERABILITY
The removal, in whole or in part, of any provision of this contract shall not void or affect
the validity of any other provision of this contract.
11.32
RELATIONSHIPS
11.32.1 In the performance of the services described herein, the Contractor shall act
solely as an independent Contractor, and nothing herein or implied herein shall at
any time be construed as to create the relationship of employer and employee,
co-employee, partnership, principal and agent, or joint venture between the
County and the Contractor.
11.32.2 The County reserves the right of final approval on proposed staff. Also, upon
request by the County, the Contractor will be required to remove any employees
working on County projects and substitute personnel based on the discretion of
the County within two business days, unless previously approved by the County.
11.33
NON-DISCRIMINATION
Contractor agrees to comply with all provisions and requirements of Arizona Executive
Order 2009-09, including flow down of all provisions and requirements to any
subcontractors. Executive Order 2009-09 supersedes Executive Order 99-4 and amends
Executive Order 75-5 and is hereby incorporated into this contract as if set forth in full
herein. During the performance of this contract, Contractor shall not discriminate against
any employee, client, or any other individual in any way because of that person’s age,
race, creed, color, religion, sex, disability, or national origin. (Arizona Executive Order
2009-09
can
be
downloaded
from
the
Arizona
Memory
Project
at
https://azmemory.azlibrary.gov/nodes/view/44845?keywords=
11.34
WRITTEN CERTIFICATION PURSUANT to A.R.S. § 35-393.01
If vendor engages in for-profit activity and has 10 or more employees, and if this
agreement has a value of $100,000 or more, vendor certifies it is not currently engaged
in, and agrees for the duration of this agreement to not engage in, a boycott of goods or
services from Israel. This certification does not apply to a boycott prohibited by 50 U.S.C.
§ 4842 or a regulation issued pursuant to 50 U.S.C. § 4842.
11.35
CERTIFICATION REGARDING DEBARMENT AND SUSPENSION
11.35.1 The undersigned (authorized official signing on behalf of the Contractor) certifies
to the best of his or her knowledge and belief that the Contractor, its current
officers, and directors:
11.35.1.1 are not presently debarred, suspended, proposed for debarment,
declared ineligible, or voluntarily excluded from being awarded any
contract or grant by any United States department or agency or any
state, or local jurisdiction;
11.35.1.2 have not within a three-year period preceding this contract:
11.35.1.2.1 been convicted of fraud or any criminal offense in
connection with obtaining, attempting to obtain, or as the
result of performing a government entity (Federal, State or
local) transaction or contract; or
Page 20
11.35.1.2.2 been convicted of violation of any Federal or State antitrust
statutes or conviction for embezzlement, theft, forgery,
bribery, falsification or destruction of records, making false
statements, or receiving stolen property regarding a
government entity transaction or contract;
11.35.1.3 are not presently indicted or criminally charged by a government entity
(Federal, State or local) with commission of any criminal offenses in
connection with obtaining, attempting to obtain, or as the result of
performing a government entity public (Federal, State or local)
transaction or contract;
11.35.1.4 are not presently facing any civil charges from any governmental entity
regarding obtaining, attempting to obtain, or from performing any
governmental entity contract or other transaction; and
11.35.1.5 have not within a three-year period preceding this contract had any
public transaction (Federal, State or local) terminated for cause or
default.
11.35.2 If any of the above circumstances described in the paragraph are applicable to
the entity submitting a bid for this requirement, include with your bid an
explanation of the matter including any final resolution.
11.35.3 The Contractor shall include, without modification, this clause in all lower tier
covered
transactions
(i.e.,
transactions
with
subcontractors
or
sub-
subcontractors) and in all solicitations for lower tier covered transactions related
to this contract. If this clause is applicable to a subcontractor or sub-
subcontractor, the Contractor shall include the information required by this clause
with their bid.
11.36
VERIFICATION REGARDING COMPLIANCE WITH A.R.S. § 41-4401 AND FEDERAL
IMMIGRATION LAWS AND REGULATIONS
11.36.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. I-9 forms are
available for download at www.uscis.gov.
11.36.2 The County retains the legal right to inspect documents of Contractor and
subcontractor employees performing work under this contract to verify compliance
with paragraph 11.36.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
Page 21
Contractor. All costs necessary to verify compliance are the responsibility of the
Contractor.
11.37
CONTRACTOR LICENSE REQUIREMENT
11.37.1 The Contractor shall procure all permits, insurance, and licenses, and pay the
charges and fees necessary and incidental to the lawful conduct of his/her
business, and as necessary complete any requirements, by any and all
governmental or non-governmental entities as mandated to maintain compliance
with and remain in good standing. The Contractor shall keep fully informed of
existing and future trade or industry requirements, and Federal, State, and local
laws, ordinances, and regulations which in any manner affect the fulfillment of a
contract and shall comply with the same. Contractor shall immediately notify both
Office of Procurement Services and the department of any and all changes
concerning permits, insurance, or licenses.
11.37.2 Contractor furnishing finished products, materials, or articles of merchandise that
will require installation or attachment as part of the contract shall possess any
licenses required. Contractor is not relieved of its obligation to obtain and
possess the required licenses by subcontracting of the labor portion of the
contract. Contractors are advised to contact the Arizona Registrar of Contractors,
Chief of Licensing, to ascertain licensing requirements for a particular contract.
Contractor shall identify which license(s), if any, the Registrar of Contractors
requires for performance of the contract.
11.38
INFLUENCE
11.38.1 As prescribed in MC1-1203 of the Maricopa County Procurement Code, any
effort to influence an employee or agent to breach the Maricopa County Ethical
Code of Conduct or any ethical conduct, may be grounds for disbarment or
suspension under MC1-902.
11.38.2 An attempt to influence includes, but is not limited to:
11.38.2.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 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.
11.38.3 If a person attempts to influence any employee or agent of Maricopa County, the
chief procurement officer, or his designee, reserves the right to seek any remedy
provided by the Maricopa County Procurement Code, any remedy in equity or in
the law, or any remedy provided by this contract.
11.38.4 ABSOLUTELY NO CONTACT BETWEEN THE RESPONDENT AND ANY
COUNTY PERSONNEL, OTHER THAN THE OFFICE OF PROCUREMENT
SERVICES, IS ALLOWED DURING THE SOLICITATION PROCESS UNLESS
THE COMMUNICATION IS IN REGARD TO PRE-EXISTING BUSINESS WITH
THE COUNTY. ANY COMMUNICATIONS REGARDING THE SOLICITATION,
ITS PARTICIPANTS, OR ANY DOCUMENTATION PRIOR TO THE CONTRACT
AWARD MAY BE GROUNDS FOR DISMISSAL OF THE RESPONDENT FROM
THE EVALUATION PROCESS.
Page 22
11.39
CONFIDENTIAL INFORMATION
11.39.1 Any information obtained in the course of performing this contract may include
information that is proprietary or confidential to the Parties. This provision
establishes the Party’s obligation regarding such information. The Recipient shall
establish and maintain procedures and controls that are adequate to assure that
no information contained in its records and/or obtained from the Discloser or from
others in carrying out its functions (services) under the contract shall be used by
or disclosed by it, its agents, officers, or employees, except as required to
efficiently perform duties under the contract or as otherwise required by
applicable law. The Recipient procedures and controls, at a minimum, must be
the same procedures and controls it uses to protect its own proprietary or
confidential information. If, at any time during the duration of the contract, the
Discloser determines that the procedures and controls in place are not adequate,
the Recipient shall institute any new and/or additional measures requested by the
County within 15 business days of the written request to do so. Any requests to
the Recipient for Discloser proprietary or confidential information shall be referred
to the Discloser for review and approval, prior to any dissemination. Confidential
Information. “Confidential Information” means any and all non-public information
provided by one Party (“Discloser”) to the other (“Recipient”) that is disclosed
under this Agreement in oral, written, graphic, machine recognizable, or sample
form, being clearly designated, labeled or marked as confidential or its equivalent
or that a reasonable businessperson would consider non-public and confidential
by its nature. With respect to Motorola, Confidential Information will also include
Products and Services, and Documentation, as well as any other information
relating to the Products and Services. Subject to applicable public records laws,
the nature and existence of this Agreement are considered Confidential
Information of the Parties. In order to be considered Confidential Information,
information that is disclosed orally must be identified as confidential at the time of
disclosure and confirmed by Discloser by submitting a written document to
Recipient within thirty (30) days after such disclosure. The written document must
contain a summary of the Confidential Information disclosed with enough
specificity for identification purpose and must be labeled or marked as
confidential or its equivalent.
11.39.2 Obligations of Confidentiality. During the Term and for a period of three (3) years
from the expiration or termination of this Agreement, Recipient will (a) not
disclose Confidential Information to any third party, except as expressly permitted
herein; (b) restrict disclosure of Confidential Information to only those employees
(including, employees of any wholly owned subsidiary, a parent company, any
other wholly owned subsidiaries of the same parent company), agents or
consultants who must access the Confidential Information for the purpose of, and
who are bound by confidentiality terms substantially similar to those in, this
Agreement; (c) not copy, reproduce, reverse engineer, de-compile or
disassemble any Confidential Information; (d) use the same degree of care as for
its own information of like importance, but at least use reasonable care, in
safeguarding against disclosure of Confidential Information; (e) promptly notify
Discloser upon discovery of any unauthorized use or disclosure of the
Confidential Information and take reasonable steps to regain possession of the
Confidential Information and prevent further unauthorized actions or other breach
of this Agreement; and (f) only use the Confidential Information as needed to
fulfill its obligations and secure its rights under this Agreement.
Page 23
11.39.3 Exceptions. Recipient is not obligated to maintain as confidential any information
that Recipient can demonstrate by documentation (a) is publicly available at the
time of disclosure or becomes available to the public without breach of this
Agreement; (b) is lawfully obtained from a third party without a duty of
confidentiality to Discloser; (c) is otherwise lawfully known to Recipient prior to
such disclosure without a duty of confidentiality to Discloser; or (d) is
independently developed by Recipient without the use of, or reference to, any of
Discloser’s Confidential Information or any breach of this Agreement.
Additionally, Recipient may disclose Confidential Information to the extent
required by law, including a judicial or legislative order or proceeding.
11.39.4 Ownership of Confidential Information. All Confidential Information is and will
remain the property of Discloser and will not be copied or reproduced without the
express written permission of Discloser (including as permitted herein). Within
ten (10) days of receipt of Discloser’s written request, unless otherwise required
by applicable law, Recipient will return or destroy all Confidential Information to
Discloser along with all copies and portions thereof, or certify in writing that all
such Confidential Information has been destroyed. However, Recipient may
retain (a) one (1) archival copy of the Confidential Information for use only in
case of a dispute concerning this Agreement and (b) Confidential Information that
has been automatically stored in accordance with Recipient’s standard backup or
recordkeeping procedures, provided, however that Recipient will remain subject
to the obligations of this Agreement with respect to any Confidential Information
retained subject to clauses (a) or (b). No license, express or implied, in the
Confidential Information is granted to the Recipient other than to use the
Confidential Information in the manner and to the extent authorized by this
Agreement. Discloser represents and warrants that it is authorized to disclose
any Confidential Information it discloses pursuant to this Agreement.
11.40
PUBLIC RECORDS
Under Arizona law, all offers submitted and opened are public records and must be
retained by the County at the Maricopa County Office of Procurement Services. Offers
shall be open to public inspection and copying after contract award and execution, except
for such offers or sections thereof determined to contain proprietary or confidential
information by the Office of Procurement Services. If an offeror believes that information
in its offer or any resulting contract should not be released in response to a public record
request, under Arizona law, the offeror shall indicate the specific information deemed
confidential or proprietary and submit a statement with its offer detailing the reasons that
the information should not be disclosed. Such reasons shall include the specific harm or
prejudice which may arise from disclosure. The records manager of the Office of
Procurement Services shall determine whether the identified information is confidential
pursuant to the Maricopa County Procurement Code.
11.41
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, expressed, or implied.
11.42
UNIFORM ADMINISTRATIVE REQUIREMENTS
By entering into this contract, the Contractor agrees to comply with all applicable
provisions of Title 2, Subtitle A, Chapter II, Part 200—UNIFORM ADMINISTRATIVE
REQUIREMENTS, COST PRINCIPLES, AND AUDIT REQUIREMENTS FOR FEDERAL
AWARDS contained in Title 2 C.F.R. § 200 et seq.
Page 24
11.43
GOVERNING LAW
This contract shall be governed by the laws of the State of Arizona. Venue for any actions
or lawsuits involving this contract will be in Maricopa County Superior Court, Phoenix,
Arizona.
11.44
FORCED LABOR
11.44.1 By submitting a bid for this solicitation and/or entering into a contract as a result
of this solicitation, Contractor agrees to comply with all applicable portions of
Arizona
Revised
Statutes
Section
35-394. Contracting;
procurement;
prohibition;
written
certification;
remedy;
termination;
exception;
definitions et. seq.
11.44.2 Contractor certifies that is does not currently, and agrees for the duration of the
contract that it will not, use:
11.44.2.1 the forced labor of ethnic Uyghurs in the People’s Republic of China;
11.44.2.2 any goods or services produced by the forced labor of ethnic Uyghurs
in the People’s Republic of China and
11.44.2.3 any contractors, subcontractors or suppliers that use the forced labor
or any good or services produced by the forced labor of ethnic Uyghurs
in the People’s Republic of China.
11.44.3 If Contractor becomes aware during the term of the Agreement that Contractor is
not in compliance with this paragraph, the Contractor shall notify the County
within five business days after becoming aware of the noncompliance. If the
Contractor fails to provide a written certification to the County that the Contractor
has remedied the noncompliance within 180 days after notifying the County of its
noncompliance, then the Agreement terminates, except that if the Agreement
termination date occurs before the end the 180-day period, the Agreement
terminates on the Agreement termination date.
11.45
UNIQUE ENTITY IDENTIFIER (UEI) AND SYSTEM FOR AWARD MANAGEMENT
REGISTRATION
All
contractors
that
receive
funding
must
have
a
UEI
number
through
https://sam.gov/content/entity-registration. Contractor must also remain current with the
System for Award Management www.sam.gov throughout the term of the contract.
11.46
RELIGIOUS ACTIVITIES
The contractor agrees that costs, planned or claimed, including costs incurred, shall not
include any expense for any religious activity.
11.47
POLITICAL ACTIVITY PROHIBITED
None of the funds, materials, property, or services contributed by the County or the
contractor under the agreement shall be used in the performance of this agreement for
any partisan political activity, or to further the election or defeat of any candidate for
public office.
Page 25
11.48
EQUAL EMPLOYMENT OPPORTUNITY
11.48.1 The contractor shall not discriminate against any employee or applicant for
employment because of race, age, disability, color, religion, sex, or national
origin. The contractor shall take affirmative action to ensure applicants are
employed and that employees are treated during employment without regard to
their race, age, disability, color, religion, sex, or national origin. Such action shall
include but is not limited to the following: employment, upgrading, demotion or
transfer, recruitment, or recruitment advertising, lay-off or termination, rates of
pay or other forms of compensation, and selection for training, including
apprenticeship.
11.48.2 Contractor shall comply with the following provisions:
11.48.2.1 Title VI and VII of the Civil Rights Act of 1964, as amended (42 U.S.C.
§§ 2000a, et seq.);
11.48.2.2 The Rehabilitation Act of 1973, as amended (29 U.S.C. §§ 701, et
seq.);
11.48.2.3 The Age Discrimination in Employment Act of 1967, as amended
(29U.S.C. §§ 621, et seq.);
11.48.2.4 The Americans With Disabilities Act of 1990 (42 U.S.C. §§ 12101, et
seq.); and Arizona Executive Order 2009-09, as amended, et seq.
which mandates that all persons shall have equal access to
employment opportunities.
11.48.2.5 Contractor understands that the United States has the right to seek
judicial enforcement of this assurance.
11.49
CERTIFICATION REGARDING LOBBYING
11.49.1 Contractor certifies, to the best of their knowledge and belief, that:
11.49.1.1 No federal appropriated funds have been paid or will be paid, by or on
behalf of the contractor, to any person for influencing or attempting to
influence an officer or employee of any agency. This applies to a
Member of Congress, an officer or employee of Congress, or an
employee of a Member of Congress in connection with the awarding
of any federal contract, the making of any federal grant. Including the
making of any federal, loan the entering into of any cooperative
agreement, and the extension, continuation, renewal, amendment, or
modification of any federal contract, grant, loan, or cooperative
agreement.
11.49.2 If any funds other than federal appropriated funds, have been paid or will be paid
to any person for influencing or attempting to influence an officer or employee of
any agency, member of Congress, an officer or employee of Congress, or an
employee of a member of Congress in connection with this federal contract,
grant, loan, or cooperative agreement, the undersigned shall complete and
submit Standard Form-LLL, “Disclosure Form to Report Lobbying,” in accordance
with its instructions.
Page 26
11.49.3 Contractor shall include Lobbying Certification language in the award documents
for all subcontractors (including sub-grants, and contract under grants, loans, and
cooperative agreements) and that all sub-recipients shall certify and disclose
accordingly.
11.49.3.1 The Lobbying Certification is a material representation of fact upon
which reliance was placed when this transaction is made or entered
into. Submission of this certification is prerequisite for making or
entering into this transaction imposed by section 1352, Title 31, U.S.
Code. Any successful proposer(s) who fail to file the required
certification shall be subject to a civil penalty of not less than
$10,000.00 and not more than $100,000.00 for each such failure.
11.50
CLEAN AIR ACT & CLEAN WATER ACT
Contractor must comply with all applicable standards, orders, or requirements issued
under section 306 of the Clean Air Act (42 U.S.C. 1857(h), section 508 of the Clean
Water Act (33 U.S.C. 1368) Executive Order 11738, and Environmental Protection
Agency regulations (40 CFR part 15).
11.51
ENERGY POLICY AND CONSERVATION ACT
Contractor must adhere to the standards and policies relating to energy efficiency, which
are contained in the State energy conservation plan issued in compliance with the Energy
Policy and Conservation Act (Pub. L. 94-163, 89 Stat.871).
11.52
RESERVED
11.53
ORDER OF PRECEDENCE
In the event of a conflict in the provisions of this contract and Exhibit E the terms of this
Contract shall prevail. In the event of a conflict in the remaining provisions of this
Contract and the provisions of the attached exhibits as referenced in Section 11.54 the
remaining provisions of this Contract shall prevail. Conflicts between the remaining
Exhibits (except Exhibit E) shall be resolved in the order presented below.
11.54
INCORPORATION OF DOCUMENTS
11.54.1 The following are to be attached to and made part of this Contract:
11.54.1.1
Exhibit A – Vendor Information
11.54.1.2
Exhibit A-1 – Pricing Information
11.54.1.3
Exhibit B – System Description
11.54.1.4
Exhibit B-1 – Interface Functional Design Documents
11.54.1.5
Exhibit C – Statement of Work (SOW)
11.54.1.6
Exhibit C-1 – Project Schedule
11.54.1.7
Exhibit D – Training Plan
11.54.1.8
Exhibit E – Master Customer Agreement (MCA) and addenda
Page 27
11.54.1.9
Exhibit F – CAD Functional Response Matrix
11.54.1.10 Exhibit G – RMS Functional Response Matrix
11.54.1.11 RESERVED
11.54.1.12 Exhibit I – Service Level Agreement (SLA)
11.54.1.13 Exhibit J – Motorola Proposal (Reference Document)
11.55
NOTICES
All notices given pursuant to the terms of this contract shall be addressed to:
For County:
Maricopa County
Office of Procurement Services
301 W. Jefferson Street
Suite 700
Phoenix, Arizona 85003
For Contractor:
Motorola Solutions, Inc.
500 W. Monroe St.
Chicago, IL 60661
Page 28
IN WITNESS WHEREOF, this contract is executed on the date set forth above.
CONTRACTOR
AUTHORIZED SIGNATURE
PRINTED NAME AND TITLE
ADDRESS
DATE
MARICOPA COUNTY
CHAIRMAN, BOARD OF SUPERVISORS
DATE
ATTESTED:
CLERK OF THE BOARD
DATE
APPROVED AS TO FORM:
DEPUTY COUNTY ATTORNEY
DATE
$ " %$ # " $
"! "$ "# $ $" $'"
"& #
$$"
!$ "
Use or disclosure of this proposal is subject to the restrictions on the cover page.
Page 29
Section 2
Exhibit A: Vendor Information
VENDOR INFORMATION
SERIAL 2300225-RFP
NIGP CODE: 83845
COMPANY NAME:
Motorola Solutions, Inc.
DOING BUSINESS AS (dba):
N/A
MAILING ADDRESS:
500 W Monroe St. Chicago Il 60661
REMIT TO ADDRESS:
13108 Collections Center Dr Chicago Il 60693
TELEPHONE NUMBER:
847-576-5000
FAX NUMBER:
WWW ADDRESS:
https://www.motorolasolutions.com
REPRESENTATIVE NAME:
Robin Ginther
REPRESENTATIVE TELEPHONE NUMBER:
785-822-2237
REPRESENTATIVE EMAIL ADDRESS
robin@motorolasolutions.com
YES
NO
REBATE
WILL ALLOW OTHER GOVERNMENTAL ENTITIES TO
PURCHASE FROM THIS CONTRACT:
WILL ACCEPT PROCUREMENT CARD FOR PAYMENT:
PAYMENT TERMS: NET 30 DAYS
Except for a payment that is due on the Effective Date, Customer will make payments to Motorola within thirty
(30) days after the date of each invoice. Customer will make payments when due in the form of a check, cashier’s
check, or wire transfer drawn on a U.S. financial institution. If Customer has purchased additional Professional or
Subscription services, payment will be in accordance with the applicable addenda. Payment for the System
purchase will be in accordance with the following milestones in Exhibit A-1.
Not to Exceed. Except as otherwise agreed to via written amendment signed by the parties, in no event shall the
amount owed under this Agreement exceed $25,000,000.
Page 3-1
Section 3
Exhibit A-1: Pricing Information
EXHIBIT A-1 PRICING INFORMATION and PAYMENT MILESTONES
Pricing Information
Payment
Milestones
Year 1
Year 2
Year 3
Year 4
Year 5
Year 6
Year 7
Year 8
Year 9
Year 10
Total
Capitalization of
System
PremierOne
Hardware and
System Software
$819,125
$819,125
Organizational
Change
Management
$227,410
$227,411
$454,821
Implementation
Services
$839,830
$1,439,831
$2,279,661
Remote Admins
$272,210
$159,306
$164,085
$169,007
$174,078
$938,686
Total
Implementation
$1,886,365
$1,667,242
$272,210
$159,306
$164,085
$169,007
$174,078
$4,492,293
Payment
Milestones
Year 1
Year 2
Year 3
Year 4
Year 5
Year 6
Year 7
Year 8
Year 9
Year 10
Total
Page 3-2
System
Maintenance and
Subscription Fees
Subscription
Software
PremierOne CAD,
PremierOne
Records,
CommandCentral
Aware
$1,700,095
$1,819,329
$1,816,746
$1,812,007
$1,807,142
$1,802,146
$1,797,016
$1,791,748
$1,786,339
$1,780,784
$17,913,352
10-21 Police Phone
$61,466
$74,427
$75,915
$77,434
$78,982
$80,562
$82,173
$83,817
$85,493
$87,203
$787,472
App Armor
$89,638
$104,213
$107,339
$110,559
$113,876
$117,292
$120,811
$124,435
$128,168
$132,013
$1,148,344
Total Annual
Maintenance and
Subscription Fees
$1,851,199
$1,997,969
$2,000,000
$2,000,000
$2,000,000
$2,000,000
$2,000,000
$2,000,000
$2,000,000
$2,000,000
$19,849,168
TOTAL Contract
$24,341,461
Estimated Sales
Taxes* (to be
added to each
invoice)
$229,648
$171,825
$172,000
$172,000
$172,000
$172,000
$172,000
$172,000
$172,000
$172,000
*8.6% Calculated on Hardware and Subscription Software
Credits Due to Descoped Items/Services During Implementation. In the event an item or service(s) is/are descoped during the implementation of the project,
Motorola will provide to the County the value of such item or service(s), at which time the County may elect to purchase another item or service(s) to which the
value of the descoped item or service(s) will be applied.
Page 3-3
Payment Milestone Criteria
Payment Milestone
Payment Criteria
PremierOne Hardware and System Software
Acceptance certificate affirming successful “power on” test, availability of application, demonstration of
synchronization of primary and disaster recovery and failover/fail back.
Organizational Change Management
Milestone 1: Delivery of Change Management Dashboard and Stakeholder Analysis Report
Milestone 2: Implementation of Change Management Plan (Post Train-the-Trainer training.
Implementation Services
Year 1 - Due upon Year 1 Subscription Software Payment
Year 2 - Due upon Year 2 Subscription Software Payment
Remote Admins
Year 3: Due upon live-cut. The Remote Admins will participate in finalizing the software testing and
completion of the project, (including bug fixes, etc.) and first year of application support following go-
live, (in accordance with Exhibit I - Service Level Agreement).
Years 4-7: Due in advance of each year. Application support of the PremierOne CAD and PremierOne
Records application support in accordance with Exhibit I - Service
Subscription Software
PremierOne CAD,
PremierOne Records,
CommandCentral Aware
Year 1: PremierOne CAD/Mobile Provisioning Complete, e911 TDD CAD Interface Available, State
Query Interface Available
PremierOne Suite configuration for PremierOne Records to receive Calls for Service from PremierOne
CAD
PremierOne Suite configuration to create Incident/Report/Case folder in PremierOne Records
Arizona IBRS Available and Validated
AZ Crash Report available
CommandCentral Aware credentials provided, CommandCentral Aware subscription enabled
10-21 Police Phone
Year 1: 10-21 Police Phone App Available
App Armor
Year 1: App Armor App Available
Subscription Software Years 2-10
Due in advance at conclusion of previous year subscription period
Page 3-4
Options Available for Purchase During Deployment Phase
Option Description
Price
(1) 3-day, 30-hr CAD End User Training Class
$15,269
Up to 40 field/module changes in Records (ACT)
$2,210
(1) 8-hr day of remote UAT support
$2,128
(1) 4-day on-site UAT support (Application Specialist)
$15,804
(1) 8-hr day on-site RMS Training with travel
$7,060
NIST CyberSecurity Framework (CSF) Security Program Risk
Assessment
$148,418
Cybersecurity Services (Managed Detection and Response) Year
1
$243,154
(1) 8-hr day on-site RMS Training with travel
$7,060
Per each additional 8-hr day on-site RMS Training (same week as
8-hr day with travel)
$2,668
“Motorola Solutions reserves the right to re-price any optionally priced items not executed
during the first two years of the contract term.”
Page 5
Section 4
Exhibit B: System Description
4.1
System Overview
Motorola Solutions is pleased to present the following system for the Maricopa County Sheriff’s Office
(hereinafter referred to as “MCSO”). Our system is based on our interpretation of the requirements
presented in your Request for Proposal and responses to questions you have provided.
Motorola Solutions’ offering consists of server hardware, server networking hardware, system software,
PremierOne application and client software, CommandCentral Responder, Command Central
Community, interfaces and services (as stated in the Statement of Work).
The PremierOne Bridge subscription allows MCSO to leverage our proven on-premise PremierOne
solutions and step into the cloud at a pace you are comfortable with, beginning with cloud-connected
innovations like CommandCentral Capabilities that enhances your on-premise systems. The
PremierOne Bridge investment provides perpetual hardware and software and subscription licenses for
the duration of the subscription. Since functionality available on-premises may be different or
unavailable when migrating to the CommandCentral cloud suite, MCSO has the flexibility to choose
when the cloud migration transition occurs. When agreed upon, a System Description for the cloud
migration will be provided.
4.1.1
Participating Agencies
The designated agencies participating in the system are:
x
Maricopa County Sheriff’s Office
4.1.2
Basis for System Sizing
Motorola Solutions uses Call for Service (CFS) and client quantities as the parameters to establish the
tiers of infrastructure sizing. Based on the counts provided by MCSO, the system has been sized as
follows:
x
Up to 2 million CAD Calls for Service per year
x
Up to 250 PremierOne CAD clients
x
Up to 1000 concurrent PremierOne Mobile clients
x
Up to 1000 concurrent PremierOne Records clients
For optimal system performance, the following counts and recommendations for data retention should
not be exceeded. Five (5) years of PremierOne CAD data retention (2 years of live online data and 3
years of archived data).
4.1.3
Application Software and System Components
This System is comprised of the following component and Subsystem elements:
CAD Subsystem
x
PremierOne CAD
Page 6
x
PremierOne Mobile
x
Automatic Resource Location (ARL) via:
-
PremierOne Mobile with Mobile Mapping
Records Subsystem
x
PremierOne Records with IBR submission
-
PremierOne Records supports the submission of Federal UCR, Arizona IBR IEPD 1.0,
Federal Use of Force Flat File and Bulk Load Technical Specification 4.5, Arizona Crash 01-
2704A R01/10, and supplementals ALISS AZCR1.xsd, Arizona Citation ATTC Adopted
8.25.2021 – Defendant Page Printout
x
PremierOne Mobile Records
x
PremierOne Records Convert-on-Demand Tool
Subscription Components:
x
CAD Web Client for PremierOne CAD
x
CommandCentral Responder for PremierOne Records Field Interview Module
-
Citations Module
x
Rave Mobile AppArmor
x
10-21 Police Phone Plus App
System Components
x
System Interfaces as described in Section 4.1.5 and Exhibit B-1: PremierOne System Interfaces
Page 7
The following represents a logical illustration of the system components.
Figure 1-1: Representative System Diagram
System Application Client Software Licensing
The following table summarizes the number of PremierOne client application software licenses for all
agencies listed in Participating Agencies.
Table 1-1: System Licensing
System Client Licenses
Quantity
Type
PremierOne CAD Dispatch Client with Mapping
Up to 250 Concurrent Users based
on System Hardware Sizing
Site License
PremierOne CAD Web Client
Agency-wide
Site License
PremierOne Mobile (Windows, iOS or Android)
Up to 1000 Concurrent Users based
on System Hardware Sizing
Site License
PremierOne Records
Up to 1000 Concurrent Users based
on System Hardware Sizing
Site License
PremierOne Records Mobile
Up to 1000 Concurrent Users based
on System Hardware Sizing
Site License
Page 8
System Client Licenses
Quantity
Type
CommandCentral Responder for PremierOne
Records
750 Named Users
Subscription
AppArmor Platform
Agency-wide
Agency
Subscription
10-21 Police Phone
1000 Named Users
Subscription
4.1.4
System Integrations
The table below lists the integrations included in our system.
Table 1-2: System Integrations
Integration Name
DR Y/N?
RapidSOS
Y
ASTRO Radio Console
Y
ASTRO Radio Location
Y
ASTRO Radio PTT
Y
ASTRO Radio Services
Y
RAVE
Y
CommandCentral
Y
PremierOne CAD RDW Query (for Patrol Activity Log)
Y
Rave Mobile AppArmor
Y
4.1.5
System Interfaces
The table below lists the interfaces included in our system.
Interface Functional Descriptions are included to describe the purpose of the Interface, supported use
cases, technical requirements and applicable data elements or dependencies. Any changes or
deviations from the Interface Functional Description will result in a Change Order for additional scope
and may require additional development effort and costs. PremierOne Interface Specifications have
been provided in Exhibit B-1 in PDF Format.
The Interfaces listed in table 1-3 will be configured in the designated Testing/Training environment to
facilitate interface testing through the use of file inputs and/or outputs written to designated file locations
to simulate the import/export of the required data elements. Testing of interfaces will not occur via live
connections to third-party testing environments and/or connections with the exception of the State
Query interface, which will support a test instance via a live connection. It may be determined that
some interfaces may not support a testing/training instance.
Table 1-3: System Interfaces
MCSO Interface Name
Motorola Interface Description
Document
Interface Type
DR Y/N
Palo Verde Nuclear Plant
1_Palo Verde Nuclear Plant Alarms
Incident Create
Inbound
Y
E911 ANI ALI
2_e911 TDD CAD Interface
Inbound
Y
Page 9
AXON (Evidence.com)
3_Axon (Evidence.com) CFS Law Data
Feed
CAD Data Feed
Y
ASAP
4_ASAP Alarm Bidirectional Interface
Bidirectional
Y
SMTP
5_SMTP Notification Interface
Outbound
Y
RapidSOS Alerts
6_RapidSOS_Digital_Alerts_CAD Incident
Create Interface
Incident Create
Inbound
Y
eCitation to Court
7_eCitation Submission to Court PDF
Printout and XML File Outbound
Outbound
Y
Inmate Booking
8_PremierOne Records - MCSO Pre-
Booking
Bi-directional
Y
Livescan
9_Idemia Livescan Bidirectional Interface
Bi-directional
Y
Evidence.com Records
10_Axon (Evidence.com) - Records Case
Folder Link Creation
Inbound
Y
MCSO Connect – Law
Enforcement Submittals
and Court Packets
11_Prosecutor Bi-Directional Interface
Bi-directional
Y
LeadsOnline Pawn
12_LeadsOnline Pawn Inbound Interface
Inbound
Y
TraQ (QueTel)
13_QueTel Evidence TraQ
Outbound
Y
OnBase Document
Management
14_OnBase (Hyland) Case Management
Bi-Directional Interface
Bi-directional
Y
Track Kit
15_Track-Kit Sexual Assault Kit Tracking
Bi-directional Interface
Bi-directional
Y
ReportBeam Crash
16_ReportBeam Crash Inbound Interface
Inbound
Y
Coplogic DORS
17_Coplogic DORS (LexisNexis) Case
Report Inbound Interface
Inbound
Y
LiveScan Mugshots
18_Idemia Mugshot Import Interface
Inbound
Y
LinX
19_LinX (Peraton) Records Outbound
Interface
Outbound
Y
Carfax
20_CARFAX - Crash Report Outbound
Interface
Outbound
Y
LexisNexis Crashlogic
21_LexisNexis Crash Report Multi-Output
Interface
Inbound
Y
RaidsOnline Community
Crime Map
22_RaidsOnline Records Data Feed
Outbound
Y
ABC15 Crime Data Report
23_ABC15 Crime Data Records Data Feed
Outbound
Y
Spot Crime
24_Spot Crime Records Data Feed
Outbound
Y
State Query (CommSys -
includes NCIC)
25_State Query Interface
Query
Y
Jail Mugshot Shields
26_Jail Mugshot External Query
Query
Y
Legacy Query for Arizona
TraCS (Records)
27_Legacy External Query Outbound
Query
Y
CivilServe
28_SoftCode CivilServe Query Interface
Query
Y
AJACS - State of Arizona
Citation Interface
29_AJACS - State of Arizona Citation
Outbound Interface
Outbound
Y
Page 10
Imagetrend ePCR
30_Imagetrend Elite - CFS Fire and ePR
Data Feed Interface
Outbound
Y
Carfax Query
31_CarFax Query Outbound Interface
Query
Y
eTrace (ATF)
32_ATF ETrace Direct Firearm Tracing
Hybrid Bidirectional Interface
Bi directional
Y
FBI LEEP (Law
Enforcement Enterprise
Portal)
33_FBI LEEP Case Report Outbound
Interface
Outbound
Y
Idemia Ident 2.0 (Field
Fingerprint Tool)
34_Idemia Ident 2.0 Query Inbound
Interface
Query
Y
ISO Claimsearch
(insurance claims
35_ISO Claimsearch Query Outbound
Interface
Query
Y
eWarrant
36_Warrant Bidirectional Interface
Bi directional
Y
INTEL Techniques Query
Interface
37_INTEL Techniques Query Outbound
Interface
Query
Y
NamUs Interface (missing
persons data)
38_NamUs Missing Persons Case Report
Outbound Interface
Outbound
Y
GTL Interface
39_GTL Video Visitation Bidirectional
Interface
Bi directional
Y
OffenderWatch
40_OffenderWatch Outbound Interface
Outbound
Y
Shield-JMS
41_Shield JMS (Tribridge Offender360)
External Query Interface
Query
Y
Accurint LexisNexis
42_Accurint LexisNexis Query Interface
Query
Y
EIPro
43_EIPro-Calls for Service Data View
Data View
Y
NewWorld Legacy Data
External Query
Query
Y
Hexagon Legacy Data
External Query
Query
Y
Active Directory Interface
44_Active Directory Interface
Query
Y
4.2
Application Descriptions
The following sections provide brief descriptions of PremierOne CAD, Mobile, Records, CAD Web
Client, CommandCentral Responder applications and other system applications. The PremierOne
equipment contains Commercial Off-the-Shelf (COTS) products, therefore software development is not
provided.
4.2.1
PremierOne CAD
Motorola Solutions has designed PremierOne CAD to be the central convergence point for
communications from multiple sources and systems, mission-critical information, and resource
management.
The user interface offers quick access to information via a location-based, Esri-standard GIS map.
Users perform commands and functions using a mouse, command lines, function keys, shortcuts, or
user definable right-click menus. The GPS-aided resource management tool displays the location and
identity of GPS-equipped vehicles or devices enabling a coordinated response while further supporting
officer safety.
Page 11
Users can create incidents from public telephone calls, from information received from an officer or
another public safety agency, or through an alarm interface. Once the user enters basic details of the
incident into the system, users may dispatch field personnel to handle the incident. Users may update
incidents with additional details such as information about the handling of the incident. Once the user
has completed the incident in an appropriate fashion, the user then can close the incident.
Field personnel may use PremierOne CAD to retrieve details about incidents or to make incident
updates. Additionally, supervisory personnel may use the PremierOne CAD to monitor the operations of
the communications center, the handling of incidents, and field unit statistics.
PremierOne CAD functions as a standalone product but also seamlessly integrates with Motorola
Solutions’ PremierOne Mobile and Records applications. PremierOne CAD may also be integrated with
other Motorola Solutions and third-party systems.
Users that can benefit from accessing PremierOne CAD and Mobile include but are not limited to
Dispatchers, PSAP Supervisors, Patrol Officers, and Call Takers.
4.2.1.1
PremierOne CAD Concepts
User Input
Users may operate PremierOne CAD either with or without a mouse. While all commands and actions
within the application can be accessed with the mouse, users also may drive PremierOne CAD almost
exclusively from the keyboard. A few PremierOne CAD functions, such as selecting units from a map,
must be performed with a mouse.
Work and Status Monitors
Users perform the majority of actions within PremierOne CAD’s work monitor. Status monitors present
summary information about incidents or units. A user may have one or more status monitor windows
available at the workstation.
Security and Roles
PremierOne CAD recognizes authorized users and provides access to individually authorized functions
at the time of sign-on. To facilitate these responsibilities, access rights and permissions are associated
with the various functions available within PremierOne CAD. A role is a set of specified privileges,
which provide access to data, commands, forms, devices, and functions. Each user and device is
assigned to one or more of the default of MCSO-created roles.
Units, Incidents, and Dispatching
A unit within PremierOne CAD represents the resources, which are dispatched or monitored by the
communications center personnel. All units in the system are identified with a unit id, which is typically
the radio call sign for the unit. Users can initiate incidents from the command line or from the incident
initiation form. The system provides a user with four methods to begin the incident dispatching process.
These four methods include:
x
Dispatch incident function key
x
Incident dispatch command
x
Dispatch form
x
Drag and drop feature within status monitors and map
Page 12
Incident Management
In addition to initiating and dispatching incidents, users can manage existing incidents through the
various incident management features of PremierOne CAD:
x
Updating existing incident information
x
Associating incidents
x
Disassociating incidents
x
Cloning incidents
x
Closing incidents
x
Reopening incidents
x
Displaying a summary list of incidents
x
Searching for incidents
Unit Management
Users have the ability to monitor and maintain the current activities for each unit through the various
unit management features:
x
View and update unit assignment data
x
Make unit status changes
x
Manipulate a unit’s call stack
x
Transfer units
x
View a unit’s history
x
Move units from one station or area to another station or area
x
View the current activities for a unit
x
Assign crews
x
Clear units from an incident
x
Manipulate units that are assigned to incidents
x
Move resources to cover depleted stations or areas
x
Alter a unit’s capabilities based on the personnel assigned to that unit
Federal, State and Local Queries
PremierOne allows users to submit requests for information to external databases. These external
queries can involve local agencies, as well as state and federal agencies. External databases all have
their own data formats and respond to submitted queries with one or more responses.
Maps
PremierOne mapping utilizes products from Environmental Systems Research Institute (Esri) for geo-
processing. The display of maps is an integrated component within PremierOne. The map may be
configured to automatically display when the user signs on to the workstation. A number of commands
and functions allow the user to manipulate the map and make updates in response to user actions. The
map may be configured to display an icon at this location to assist the call taker in determining the
location at which an emergency response is required. The system also attempts to find the nearest
address/common place to the caller coordinates.
Page 13
Mail & Messaging Services
The mail and messaging functionalities of PremierOne CAD allow users to exchange and distribute
electronic mail and messages within the dispatch center and to units equipped with MDTs.
4.2.2
PremierOne Mobile with Mobile Mapping
PremierOne Mobile provides public safety personnel the ability to assess and prepare for a situation
while enroute to the scene. Users access information via screen configurations that provides navigation
throughout the PremierOne Mobile application.
Table 1-4: PremierOne Mobile Mapping Capabilities
PremierOne Mobile - Available Clients:
Windows
Android
iOS
Operating System
Windows 10+
Android 10+
iOS 13 - 17
Cloud Enabled
Ɣ
Ɣ
Ɣ
Silent Dispatch
Ɣ
Ɣ
Ɣ
Incident & Unit Management
Ɣ
Ɣ
Ɣ
Real-Time Status Monitors
7
5
5
Field Initiation for Traffic Stops & Other
Incidents
Ɣ
Ɣ
Ɣ
Database Querying
Ɣ
Ɣ
Ɣ
Unit Location Tracking
Ɣ
Ɣ
Ɣ
Premise & Hazard Details with Images
Ɣ
Ɣ
Ɣ
Geofencing with Entry & Exit Alerts
Ɣ
Ɣ
Ɣ
4G/5G & LTE Network Capability
Ɣ
Ɣ
Ɣ
CJIS Security Support with FIPS 140-2
Encryption & Auditing
Ɣ
Ɣ
Ɣ
Barcode Scan
Ɣ
Ɣ
Ɣ
Voice Entry for Comments
Ɣ
Ɣ
Actionable URL in Comments
Ɣ
Ɣ
Ɣ
Messaging
Ɣ
Ɣ
In-Progress
BOLOS
Ɣ
Ɣ
In-Progress
Advanced Mapping, BOLOs, Premise &
Hazards
Ɣ
Advanced Configurations
Ɣ
The integrated map provides the user the ability to display call location, drive directions, premise
hazards and the location of other units. PremierOne Mobile leverages the same common map platform
used in PremierOne CAD, which is managed and provisioned from a centralized location and deployed
to all systems remotely.
PremierOne Mobile obtains location information from a collocated GPS receiver. The PremierOne
Mobile Windows Client supports either the Trimble ASCII Interface Protocol (TAIP) or National Marine
Electronics Association (NMEA) standard. The PremierOne Mobile client application can send its
location to PremierOne CAD via a cellular data modem. The vehicle location information is used by
Page 14
PremierOne CAD to support location dependent features including: Mapping, Track-It, Follow-It, and
Recommendations.
4.2.3
PremierOne Records
PremierOne Records is Motorola Solutions’ next generation law enforcement records management
system (RMS), based on over 30 years of industry RMS experience, PremierOne Records was
designed from the ground up with the current and future needs of public safety agencies in mind. A
fundamental goal of PremierOne Records is to provide the greatest level of flexibility. Working with the
Advanced Configuration Tool (ACT) of PremierOne Records allows agencies to add and hide fields,
change field labels, make fields required, alter output format, and determine the information that is
made available to users and roles.
Users that can benefit from accessing PremierOne Records include but are not limited to Patrol
Officers, Records Specialists, Records Supervisors, Retention Specialists, Detectives and
Investigators.
4.2.3.1
PremierOne Records Concepts
Records Clients
PremierOne Records provides the same functionality, fields, data, and security to both the officer in the
field using a Records Mobile Client and the records bureau user accessing the system through a LAN-
connected desktop computer.
x
Standard Client – Used for workstations that are connected to the network, such as those on a
LAN or WLAN. This self-updating client can be launched from a web browser and can be run
without a local installation, thus reducing installation and maintenance costs.
x
Records Mobile Client – Used in situations where network connectivity is not assured or
nonexistent, such as with mobile units on a wireless network for field based reporting (FBR).
Over-the-wire update and caching services assure that all clients are kept up to date with
application updates, changes to forms, code tables, etc., reducing maintenance costs.
Navigation
PremierOne Records was designed with a physical law records department in mind. Users can find
information in PremierOne Records in the same areas where you would expect to find them physically
in your department. PremierOne Records provides easy and quick access throughout the application.
Users can navigate using familiar point-and-click access to modules, similar to a browser. As with a
browser, forward and back keys are provided as well as the ability to open additional tabs, allowing
multiple modules to be open at a time.
Records Command Line
A command line window can be opened using a hotkey that allows authorized users to perform typical
actions such as add, edit and navigation functions without using the mouse. The command line auto-
fills both commands and parameters requiring just a few keystrokes to create a new record or access
any record in the system. The Records command line window can be displayed even with the other
PremierOne Records windows minimized giving the user a cleaner more efficient client. This is
especially important for Records Bureau or other data entry users as they can create or edit records
much faster, with fewer keystrokes and mouse clicks. This feature is also available in the Records
Mobile client allowing patrol officers and other Mobile users to quickly create records without using a
mouse. For paper-based agencies that print and use paper copies of records, the command line can be
combined with a low cost bar code scanner to greatly improve efficiencies. A bar code can be printed at
Page 15
the bottom of each document that when scanned immediately retrieves the record with no other user
intervention. This feature is especially beneficial for document approval or other manual or automated
workflow processing.
Motorola Solutions Documents
Users perform the majority of data entry within Motorola Solutions Documents, a forms tool based on
patented technology. This technology leverages decades of experience with law enforcement records
management systems and is designed to improve data entry efficiency, accuracy, and reduce the
learning curve for new users. Specially designed functionality such as tabs, search while you type, and
‘To do’ items are designed to reduce the effort required to fully document each event.
x
Tabs: To facilitate data entry, tabs combine like data types such as victim, offense, or property.
Within each data type, a user may enter as many of that data type as necessary.
x
Required Fields: Within any document in PremierOne Records, some fields are required to be
filled in before the document can be saved to the database. Required information helps to
preserve the integrity of the document as a whole to make it a valid document. Fields may be
required based on business rules established by an agency or because the agency requires
data to be collected for reporting purposes. The system may also require certain data fields be
completed to assure accurate and complete IBR or UCR submissions.
x
Single select code Fields: Single select code tables allow users to enter only those codes that
have been created for a given field.
x
Search while you type: This functionality displays only the entries in a list that match the text
that you type. Search-as-you-type considers all the words in a phrase, not just the first word at
the beginning of the phrase.
x
Multi-select Code Tables: As with single select code tables, multi-select code tables only allow
for the acceptable range of data values to be entered.
x
Pull Forward: You can use Pull Forward to search for and find existing data, and then pull that
data into Motorola Solutions Documents.
x
To Do List: Motorola Solutions Documents also check to ensure all required fields have been
filled out and are valid. If you omit a required field or have incorrect information, an error
message will appear in the Help window of the document. These error messages, or the to-do
list, are hyperlinks. They bring the cursor directly to the field that requires attention on the form
you are currently working in. Documents that are not complete may be saved as a draft, but the
data is not present in the database directly.
x
Only display necessary fields: This feature of Motorola Solutions Documents only displays
those fields necessary to complete the document. When a user enters data that then requires
further information, fields for entering the additional data become available. Until those fields are
needed, they remain hidden.
x
Photos: Drag and drop Motorola Solutions Documents windows also support drag-and-drop
functionality for images.
x
Auto save: PremierOne Records can be configured to automatically backup or save a
document prior to document submission. The document is saved in draft form until it has been
submitted.
x
Document Locking: A locking message displays if another user tries to access a document
that is open and locked. Document locks expire when the opened document is closed, or after a
configured time (default is 12 hours), whichever comes first. Other users attempting to open a
locked document will get a read-only version of the document that displays the document lock
message in the lower right corner. Users cannot make edits to the read-only document.
Page 16
x
Searching: Free text searching in PremierOne Records provides default basic search and field
display functionality as well as advanced search functionality for custom search. Agencies can
specify and configure which module data fields are available for searching. Additionally,
PremierOne Records has a free text and advanced free text search capability, which functions
similarly to web text searches; Users can enter a word or phrase in the free text search field and
search across the entire data store for records that match the text or phrase.
4.2.4
PremierOne Reporting Services
4.2.4.1
SQL Server Reporting Services (SSRS)
SQL Server Reporting Services (SSRS) provides a set of on-premises tools and services that create,
deploy, and manage paginated reports including .RTF and RDLC reports. Paginated reports are ideal
for fixed-layout documents optimized for printing, such as PDF and Word files. The SSRS solution
flexibly delivers the right information to the right users. Users can consume the reports in a web
browser on their computer or mobile device, or via email.
SSRS Reports and Services
A standard reports library is included in the product, these reports will be loaded to MCSO system(s)
and be used during the Reporting Workshops. The Workshops will provide the attendees with the
knowledge on how to create custom reports against the PremierOne databases utilizing Microsoft’s
SSRS software.
4.2.4.2
Intelligent Data Discovery Services (IDD)
Intelligent Data Discovery (IDD) utilizes Microsoft SQL Server Reporting Services (SSRS) that allows
for reporting and dashboard generation. These services help you optimize the value of existing tools
and data resources and helps you move from reactive to proactive decision-making with actionable
intelligence. IDD supports:
x
WEB-BASED DASHBOARDS AND SCORECARDS - Graphically display aggregated
information so users can quickly analyze real-time details to identify trends, metrics and
historical performance
x
ROBUST REPORTING – Enable analysts and power users to build, modify, deploy and
distribute self-service reports to anyone in their organization
x
ANALYTICS – Gain actionable insights and drive smarter decisions with data analysis and
management
x
AD-HOC QUERIES – Perform quick searches and “what-if” analysis
x
NOTIFICATIONS – Alert users when provisionable criteria is met
x
CONFIGURABILITY – Tailor for a specific environment with parameters, drill-down, mapping,
filtering and more
x
SCALABILITY – Integrate data from additional systems, such as city operations, fire, law and
workforce management, for easy access
IDD Services include instruction in the use of advanced SQL Server Reporting Services (SSRS)
features, which will allow for the connection, extraction, and display of data from CAD in the tailored
standard IDD and customized dashboards. IDD’s use of Microsoft’s SSRS employs the data to
generate and securely share online dashboards and reports, initiate searches and mine data.
Page 17
A single copy of each of the Standard IDD dashboards will be tailored per the provisioning of the
system(s) and delivered to the site, IDD is limited to data existing in the system datasets. A map view of
the data, such as location of Incidents, may be produced as part of the report output without interactive
mapping ability. Total system capacity for IDD is dependent upon the total number of concurrent reports
being requested from the RDW server and DHStore Analysis. Final system capacity is dependent upon
final design and report types being generated on a concurrent basis.
4.2.4.2.1
CAD IDD Dashboards and Services
x
Three (3) Tailored Standard Dashboards
-
Roll Call Briefing Dashboard
-
Intelligent Resource Deployment Dashboard
-
COMPSTAT Dashboard
x
View Only CAD IDD bundle
-
Unit Status
-
Unit History
-
Map
-
Incident Search
-
Drill-through to Incident Details and Officer Activity Reports
x
Three (3) days of PremierOne CAD Intelligent Data Discovery (IDD) Workshop, after completion
of requirements.
x
Two (2) MCSO Defined Dashboards (defined and scoped during the IDD Workshop and limited
to data existing in the system CAD dataset, built as a remote effort by Motorola).
4.2.4.2.2
Records IDD Dashboards and Services
x
Three (3) Tailored Standard Dashboards
-
Master Index Search Dashboard
-
Records CompStat Dashboard
-
Records Major Crimes Dashboard
x
Three (3) days of PremierOne Records Intelligent Data Discovery (IDD) Workshop, after
completion of requirements.
x
Two (2) MCSO Defined Dashboards (defined and scoped during the IDD Workshop and limited
to data existing in the system Records dataset, built as a remote effort by Motorola).
4.2.5
CommandCentral Platform Integration
The CommandCentral platform provides a suite of systems to address the end-to-end public safety
workflow. The platform is designed to:
x
Simplify technology complexity with unique workflow integrations and seamless data sharing.
x
Provide modern user experiences built around the outcomes that matter.
x
Enhance decision-making and speed up processes with advanced analytics, A.I. and machine
learning.
Page 18
4.2.5.1
CAD Web Client for PremierOne CAD
CommandCentral CAD Web Client augments PremierOne CAD systems, providing secure view access
to your agency’s CAD information from anywhere. Users can view this data on any internet-connected
device and enable non-traditional users to work from locations that have not previously had access to
jurisdictional CAD information. The CAD Web Client provides a view of pending/active incident
information, unit information, and mapped location of incidents and responding units. Users can switch
easily from light to dark mode and use pop-out screens to personalize their view.
4.2.5.2
CommandCentral Responder for PremierOne
CommandCentral Responder works seamlessly with PremierOne Records Management System (RMS)
to provide an electronic citation experience. CommandCentral Responder captures electronic
signatures, expedites data entry, performs records searches, captures images, and streamlines the
entire citation workflow by eliminating the need for wet signatures and the subsequent paper shuffle.
This solution will increase accuracy, legibility and expedite citation and image submission to Court
Management Systems. Your officers can resolve more incidents; spend less time on routine
documentation and return to patrol faster.
CommandCentral Responder is a cloud-based application that enables law enforcement officers to
access PremierOne Records to view or update information using smartphone or tablet devices.
Individual modules enable officers to add, modify, and view different types of information. Motorola
Solutions is proposing CommandCentral Responder with Citation.
Figure 1-2: Sample CommandCentral Responder Home Screen
Records Search
Field personnel can use CommandCentral Responder to search PremierOne RMS for Person and
Vehicle records. Users can search records by manually entering the search criteria (e.g. names or
license plate numbers) and by scanning driver’s license or vehicle registration barcodes. Search results
can be used to populate related person or vehicle sections of the Citations, Forms, or both.
CommandCentral Responder does this by searching the CommandCentral Cloud service - searching
against a Cloud cache (copy) of persons and vehicles uploaded by the PremierOne Records system
(and continually synchronized from on-premises system to the Cloud).
Page 19
Figure 1-3: Sample CommandCentral Responder Search Screens
Citation Functionality
CommandCentral Responder provides field personnel with a simple workflow for writing, issuing, and
recording citations. The citation forms within CommandCentral Responder guide the user on what
information to include, and alert them if a field needs to be populated to issue the citation.
After a user completes and signs a citation, CommandCentral Responder enables printing from
supported mobile printers and synchronizes standard fields, person information, and vehicle information
with PremierOne RMS.
Field personnel can use completed citations as a reference to populate new citations. They can also
search and retrieve copies of citations in the PremierOne RMS application for future needs, such as
court or investigative activities.
Page 20
Figure 1-4: Sample CommandCentral Responder Citation Screens
Configuration
During the deployment process, Motorola Solutions will configure CommandCentral Responder with
your agency’s required fields for citations, including the fields, field labels, field type, validation rules,
and cross-field validation (e.g., driver speed must exceed the posted speed limit). Parts of the citation
user interface can also be configured, including the field display order, field groups, and field-group
display rules. Sections can be shown or collapsed on the UI, and dynamically removed based on user
inputs in a citation form.
In addition to configuring the citation fields and interface in CommandCentral Responder, Motorola
Solutions will also customize the format of printed citations during the deployment process.
Workflow
The workflow for CommandCentral Responder helps officers issue accurate citations by enforcing
agency rules for issuing citations and by connecting each citation to PremierOne Records. This
workflow automatically validates citations as they are built, eliminating the need for manual citation
reviews by records personnel.
CommandCentral Responder supports a predefined process for issuing citations, with steps from
creating a citation through issuing, printing, and submitting to the RMS. It includes the following steps:
x
Create new Citation.
x
Enter required data manually, or by scanning barcodes or using search results.
x
Issue Citation:
-
CommandCentral Responder automatically performs data validation and identifies any
missing required fields or errors that require to be resolved before issuing.
Page 21
-
CommandCentral Responder allows for capture of signature of the offender, officer or both.
-
CommandCentral Responder generates a serial number for the Citation.
The serial number is generated by combining a number that is unique to the device installation and a
count of how many serial numbers have been generated by the device installation. The device
installation number is not shared between devices belonging to the same user. It is shared between
users in the same agency on a given device. The device installation number is maintained by the
application; it is reset to a new unique number if the application is uninstalled and reinstalled on a
device.
The format of the serial number can be configured during the deployment process by defining a format
consisting of a text prefix, a fixed length encoding (using letters and numbers) of the device installation
number, a fixed length encoding (using letters and numbers) of the count and a text suffix.
The serial number is therefore guaranteed to be unique, but it cannot be selected from a predefined
batch of numbers.
-
CommandCentral Responder allows for printing of the Citation on supported mobile printers.
CommandCentral Responder supports specific printers: Brother PocketJet 763MFI, Brother
PocketJet 662 (supported with Responder on Android devices), or Zebra printers with Zebra
Link-OS.
-
Add any desired Officer Notes or other fields required by the agency.
-
Submit the Citation:
CommandCentral Responder automatically performs data validation and identifies any missing required
fields or errors that require to be resolved before submitting.
CommandCentral Responder submits the citation information to CommandCentral Cloud service.
CommandCentral Cloud service automatically synchronizes the Citation with on-premises PremierOne
Records system.
Note - Automatic Citation transmission to a designated Court Citation System is supported as a part of the
PremierOne Records solution (provided an interface to your Court system is deployed as part of PremierOne
Records).
Note - Further Citation workflow can be managed in PremierOne Records after submission from
CommandCentral Responder.
4.2.6
AppArmor
AppArmor Safety is Motorola’s Premium Safety App offering: a comprehensive mobile safety app for
your residents that provides a highly configurable and branded experience, filled with proactive and
reactive safety features. Each safety app is completely custom branded and submitted under your
agency’s AppStore account.
The platform is powered by a cloud-based console which houses a content management system, mass
notification options, reporting functions, and location services features.
Popular Features
x
Unlimited Push Notifications: Mass notification system with delivery times of 1-5 seconds.
Can be segmented into channels. Notifies even when app is not running.
x
Friend Walk: User sends real-time location to a contact or local security/police force.
Emergency button in case of a crisis. Brings peace of mind to end user.
Page 22
x
Mobile BlueLight/Panic Button: Simultaneous emergency call and location share. User
location sent to cloud dashboard. A blue light in your pocket.
x
Reporting Capabilities: Users can report suspicious activity, crime, facilities outages and
more, all in real time.
x
Content Management: Ability to dynamically add and remove content such as emergency plans,
important phone numbers, interactive maps, and other resources in real-time.
Rave’s Resident Engagement & Safety Platform combines our robust critical communication solutions
to provide seamless engagement and communication with your community.
x
Custom Branded App: A comprehensive mobile safety app for your residents that provides an
entirely customizable and branded experience, filled with proactive and reactive safety features.
x
Mass and Targeted Communications via Cloud-Based Notifications: With just three clicks
send mass notifications and/or targeted messages to connect and inform your community.
x
Incident Task Management: Leveraging real-time communication tools and provides a
practical approach to collaborative incident management that supports organizations during
events that require team, department and cross disciplinary communications, as well as
situational awareness.
x
Enhanced 911 Capabilities: Provides 911 teams and first responders with critical capabilities
needed to increase situational awareness, handle emergencies quickly and improve outcomes
with personal and facility safety profiles, enhanced location data sharing and outbound chat
communications.
4.2.7
10-21 Police Phone
10-21 Police Phone is a cloud-based software-as-a-service (SaaS) application for law enforcement that
simplifies communication between first responders and your citizens. It allows law enforcement
personnel to make calls from their personal or department issued cell phones that indicate they are
placed from local, not blocked, phone numbers without revealing their actual phone numbers –
increasing collaboration and solidifying trust. The public isn’t able to call personnel back directly at the
displayed number but enables a callback requestion notification.
10-21 Police Phone and 10-21 CallManger are integrated with CommandCentral Admin for Single Sign
On (SSO) using the officer’s or admin’s CC login.
Capabilities supported with 10-21 include:
x
Follow-Up Text - sends an SMS to the citizen after the call letting them know the call was from a
law enforcement officer.
x
Cloud Contacts - stores a separate address book for citizen numbers, separate from personal
ones
x
History - retains call history / call detail records for later reference in police reports
x
Identity - incoming caller ID shows citizen’s name and outbound caller ID shows LAW
ENFORCEMENT
x
Click-to-call – PremierOne Mobile (iOS/Android) can recognize 10-21 Police Phone as a
phone/calling option on their mobile device and directly open the 10-21 app from a phone
number deeplink.
Additionally, supervisors benefit from administrative controls through 10-21 CallManager. 10-21
administrators gain clear insight into call history and community callback requests, to assess
promptness and improve transparency with the community.
Page 23
4.2.8
ASTRO 25 Radio Integrations
Figure 1-5: Radio Integration Diagram
4.2.8.1
MCC 7500 Console Integration
The MCC 7500 console integration enables the Channel Grouping feature from CAD.
The Channel Grouping feature is available when system CAD is integrated to the MCC 7500 Radio
Console. From a window within the CAD client, the user can use predefined groups or create and
maintain their own groups. Groups can be activated as multi-selects on the radio console at the
discretion of the user. When the group is utilized, the CAD client will show the status and will allow the
user to transmit on all the selected talkgroups. The user can make a priority transmission or may
request the use of the talkgroups by alerting the other users with an audible notification. CAD can also
be provisioned to automatically load a particular channel group based on the geographical location of
an incident.
4.2.8.2
ASTRO 25 APX Subscriber Push-to-Talk (PTT) and Emergency Button Activation
Monitor
An emergency situation can be triggered either by the Radio Emergency button or the Emergency icon
on the PremierOne Mobile client.
A radio PTT status monitor window displays an identification of the source of a configurable number of
the most recent radio transmission. The information shown to identify the radio varies depending on
how the radio has been identified within the system. If the radio has been associated with a unit, a
vehicle, or a person, the system identifies that unit, vehicle, or person as the source of the
transmission. If an association has not been made, the system displays the ID of the radio.
Any radio that is in emergency status will be displayed in a distinctly different manner in the CAD’s work
monitor window. Every time a unit keys up a radio that is in emergency status, the display in the PTT
window will show the unit is in emergency status.
Page 24
Radio Channels that are to be monitored by CAD and have their status displayed on the PTT Status
monitor must be selected by the CAD User using the CT command. This allows for a dispatcher to
select only those channels that need to be monitored and may be associated with a dispatcher’s
coverage area.
Once the channels are selected, enabling the PTT Status Monitor will ensure that all radio traffic on that
channel is monitored and displayed.
RadioServices: Radio Proxy server
The system’s element providing the main radio infrastructure interface is the RadioServices server. This
stand-alone Server provides proxy functions from the Radio Infrastructure to the CAD system.
RadioServices can support ASTRO 25 Integrated Voice and Data (IV&D) Conventional as well as
Trunking systems. There are three supported interface protocols from the ASTRO systems: CADI,
ATIA, and eCADI.
The RadioServices Server provides four types of data from the Radio system to the CAD system.
These include specific radio-initiated events as follows:
x
Non-PTT Events (such as affiliation and disaffiliation)
x
PTT Events
x
Emergency status
x
Unit Status Change
4.2.8.3
ASTRO 25 Responder Location Integration
The core features of ASTRO 25 Responder Location are integrated with PremierOne CAD:
x
ASTRO 25 Subscriber Responder Location
The CAD system Subscriber radio Responder Location features are included in this system.
The Responder Location Feature allows the CAD system to obtain the location of APX subscriber
radios via the ASTRO 25 infrastructure. This capability allows dispatchers and supervisors to monitor
the location of personnel who are using ASTRO subscribers. Radios with Location on PTT can be
configured to send their location after each PTT during group calls and during emergency calls.
Location data is embedded directly in the voice stream and sent continuously without impacting voice
quality. Location services are enabled on a per subscriber basis allowing agencies to limit its use to
portable radios or other specific groups.
4.2.8.3.1
ASTRO 25 Location Accuracy
There are a number of factors that impact the accuracy of ASTRO location updates. Some are
fundamental aspects of the Global Positioning System design such as the need to “see” satellites.
Others are a result of the ASTRO system implementation and configuration settings. These settings
can be adjusted for a specific implementation, but always involve a trade-off between competing
system characteristics.
GPS Signal Availability
The ASTRO subscriber’s GPS antenna must be able to receive GPS signals from five or more satellites
to derive a location accurately. Operation in buildings, tunnels, urban canyons, or densely forested
areas can reduce GPS location accuracy or prevent the subscriber from determining its location
altogether.
Page 25
Temporary Signal Loss
ASTRO subscribers cache their last known location. In the event that an ASTRO subscriber loses GPS
fix, it will send its last known location in response to a location query or scheduled location update. The
subscriber will send its last known location for up to 100 seconds after losing GPS fix. The accuracy of
the location updates sent during temporary signal loss is a function of the subscriber speed.
GPS Acquisition Time
When ASTRO subscribers are powered on, they require a finite amount of time to establish their
location accurately. This is referred to as Time to First Fix (TTFF). In the Cold Start scenario, a
subscriber is turned on after a prolonged period of time and does not have an accurate estimate of its
position or time. TTFF in this case is <60 seconds 95% of the time. In a Warm Start scenario, the
subscriber is turned on and has an accurate location and time estimate. TTFF in this case is <10
seconds 95% of the time. This can result in a delay between subscriber power up and the first accurate
location update. For example, if an officer turns on a portable radio when exiting the vehicle, the
Responder Location CAD feature may not receive an accurate location update for over a minute.
GPS Sleep Cycle
APX subscribers use a sleep cycle to conserve battery life when GPS signal lock cannot be achieved.
When the GPS receiver enters sleep cycle it powers down for 90 seconds then wakes and searches for
GPS signal lock for 180 seconds. If it is able to achieve GPS signal lock it will remain awake, otherwise
it will return to sleep for another 90 seconds. This behavior can result in a delay between the time when
a subscriber moves into a location with GPS signal (e.g. goes outside) and its first location update.
Voice Priority
ASTRO IV&D subscribers give priority to voice transmissions. If a user is talking on their radio or
receiving a transmission from another user, their radio cannot originate or receive data traffic. This
voice preference results in data packets being queued within the radio for transmission when the radio
is not participating in a voice service. Packets are discarded if they are older than the 12-second queue
dwell timer. This can cause a variable arrival rate of location update reports at PremierOne.
Open Mic on Emergency
ASTRO subscribers can be configured to transmit audio after the Emergency Button is pressed. This
will prevent the subscriber from transmitting location updates until the radio de-keys.
Use existing ASTRO As-Is
The proposed system will utilize the existing ASTRO 25 infrastructure. The current system is currently
configured with IMW.
4.2.9
Multi-Agency Search
The Multi-Agency Search feature provides a robust search interface enabling participating agencies
that use PremierOne Records to share Persons, Vehicles, and Case Report data between them. This
collaborative tool empowers agencies to:
x
Control Data Sharing: Agencies have the discretion to select the specific types of information
that are available for sharing.
x
Manage Sharing Partners: Each agency can manage its list of trusted agencies with which to
share data, ensuring that data-sharing arrangements are mutually agreeable and maintain data
integrity.
Page 26
x
Enhance Search Capabilities: Participating agencies that have opted in will gain the ability to
conduct searches across a broader regional data set, which can foster a cooperative
environment among agencies, streamline investigative processes, and ultimately enhance
public safety operations through more effective data utilization.
4.3
PremierOne Disaster Recovery (DR)
DR / Failover System - Suite
Motorola Solutions’ offering includes a Secondary Disaster Recovery (DR) system for CAD, Mobile and
Records. The Disaster Recovery systems include hardware and software for geographically distinct
recovery data centers, the software required to replicate data between the primary and recovery data
centers, and scripted processes to transfer operation between the data centers. This system provides
continued availability of the system in the event the primary data center becomes unavailable.
The system CAD DR replication and failover processes utilize SQL Always On replication groups.
Records uses VMware site replication. The failover processes for these products utilize separate,
application specific, scripts that are specifically suited to each application’s server and database design.
4.3.1
PremierOne CAD Disaster Recovery
CAD DR Implementation (ON PREMISE)
During normal operation PremierOne clients connect to the system servers in the primary data center.
CAD data, such as active incidents, are stored in a storage area network (SAN) collocated in the
primary data center.
Data updated in the primary SAN array is asynchronously updated in the recovery data center’s SAN.
PremierOne Disaster Recovery utilizes Microsoft SQL Always On to facilitate data replication between
the primary and recovery data centers. This technology allows the system’s servers in the recovery
data center to remain on thus reducing failover time. All changes replicate in real time using
asynchronous replication. Data in PremierOne databases are replicated from primary to secondary
databases at the SQL database level using Always On Availability Groups (AAG). SQL Server instance
disaster recovery is implemented with SQL Always On Failover Clusters.
Page 27
Figure 1-7: PremierOne CAD DR Replication
SQL Always On replication can be configured as Synchronous or Asynchronous. Synchronous
replication is used between the two database servers on the primary side. This ensures no data loss in
the event of a local failover from the primary CAD Server to the collocated High Availability CAD
Server. (Please note that only one replication partner is supported for automatic failover.)
Asynchronous replication is used between the primary and both secondary DR side database servers
for performance and latency reasons.
Differences in Synchronous and Asynchronous replication are described in the following table:
Table 1-5: Synchronous and Asynchronous Differences
Issue
Asynchronous
Synchronous
Data Loss
Asynchronous mode may or may not lose
some committed transactions in the event of
an unplanned failover to the secondary site.
However, a rapidly restartable data image is
ensured because the remote database is
always in an I/O consistent state. Applying
the most recent transaction logs allows
recovery from the point of the outage.
Each I/O update operation waits until
completion is confirmed at both the primary
and mirrored sites. Any incomplete
operation is rolled back at both locations. As
a result, the remote copy is always an exact
mirror image of the primary.
Page 28
Issue
Asynchronous
Synchronous
Distance
Asynchronous mode can span virtually any
distance because there is a higher tolerance
in latency delay involved in confirming
transactions at the remote site. Latencies of
over 200 ms cannot be supported. Remote
sites can be up to thousands of miles from
the primary site, ensuring that the replicated
copy of data is safely outside any likely
disaster zone.
Synchronous replication is impacted by
propagation latency. That is, the time spent
waiting for updates to travel to the remote
site and confirmations to come back.
Synchronous replication is only used for
collocated PremierOne CAD servers.
Performance
The performance impact on the host is
minimal.
Synchronous mode has significantly more
performance impact than asynchronous
mode because a write from the host must
wait for an acknowledgment from the
secondary storage system.
Recovery Point
Objective (RPO)
High flexibility: unique capabilities afforded
by journaling provide the ability to ride out
network outages or temporary excessive
bandwidth requirements.
RPO=0. Data is always current.
Failover changes the direction of the Always On replication, making the DR data center the source of
the replication and the Primary data center the destination of the replication. The DR data center
effectively becomes the Primary and the Primary effectively becomes the DR data center. Replication
between sites is suspended if the original primary data center is not available.
The DR data center’s ability to support interfaces will vary with the specific interfaces deployed. In
general, if an interface API is available via a network connection from the DR site, and the required
licenses are in place, then the DR CAD may be manually connected to the interface. The DR scripts do
not include interface specific changes.
Failover from Primary to DR Site
Transition from the primary data center to the recovery data center is a manual process executed by a
System Administrator. The process involves three steps:
Step 1 - Troubleshooting: The CAD System Administrator determines that there is a problem with the
primary data center servers. The system’s Systems Management software monitors the health of the
primary data center. The system management console will raise appropriate alerts when an error
condition occurs. The system administrator assesses the alerts and determines if transitioning to the
recovery site is warranted. This determination may be based on SCOM alerts, CAD Client user reports,
or monitoring the SQL Always On dashboard. The System Administrator then investigates the issue
and determines if a failover to the DR site is warranted.
Step 2 - Site Failover: The failover from the primary data center to the DR site is a manual process
performed by the System Administrator. Using a step-by-step disaster recovery process, the system
administrator initiates the transition between the primary data center and the recovery data center using
the PremierOne System Management console. DR scripts automate the transition process. The DR
scripts may be initiated from either the primary or recovery data center.
Step 3 - Client Redirect: CAD clients access the PremierOne CAD application server by Host Name.
The DNS configuration specifies whether the clients are directed to the primary application servers or
the DR servers. During the manual failover process the System Administrator must redirect the
PremierOne CAD clients to the recovery data center by updating the DNS service pointer records to
reflect the IP address of the recovery data center.
Page 29
Failover from DR to Primary Site
The failover process from the DR site to the primary site follows the same process described above.
There are specific failover scripts for Primary to DR failover and DR to Primary failover.
Additional action may be required in the event the primary site has been down for an extended period
of time. After a period of non-replication there may be a significant difference between the DR database
and the primary site database. This can tax the network connection between the sites. The alternative
is taking the system offline, backing up the DR databases, and using the backups to reseed the primary
site databases. The System Administrator can then restart replication between the sites and proceed
with the failover to the primary site. The need for database reseeding is determined by the duration of
the primary site outage and available disk space to queue data for replication.
The specific time is unique to each implementation and is a function of CAD activity, disk space, and
network capacity. As a general rule, the database need not be reseeded during scheduled failovers and
should be reseeded after a primary site outage that lasts longer than a few hours.
CAD DR User Experience
The system’s CAD is not available during the DR failover process. Dispatch and Mobile clients will not
have access to the CAD servers during the transition process and the client will be unresponsive. If a
user attempts to log into the CAD system from a client, they will receive an error message indicating
that the application server is not available.
CAD DR Performance
The DR system is distinct from the High Availability design. It provides geographic site redundancy that
allows an agency to resume normal CAD operations after transitioning operation to a recovery data
center. After the initial diagnostic and troubleshooting process, the transition process is manually
initiated and requires approximately 30 (thirty) minutes to complete. After the failover is complete the
DNS must be updated to redirect CAD clients to the recovery data center.
Asynchronous replication is used to prevent performance impacts resulting from network latency
between the primary and recovery data centers. As a result, the data at the recovery data center may
lag behind the primary center’s data by several seconds. The actual time depends on network latency
and the activity on the CAD system. During a scheduled failover, the CAD system’s services in the
primary data center are stopped and the replication to the recovery data center is allowed complete. An
unscheduled or instantaneous failure of the primary data center may result in a small amount of data
loss. The actual data loss is a function of CAD activity and network connection speed.
4.3.2
PremierOne Records Disaster Recovery
Records DR Implementation
The Records DR system enables automated synchronization of the Records environment from a
primary data center to a geographically separate recovery data center. Records supports the use of
VMware’s Site Recovery Manager (SRM) that comprises a comprehensive disaster recovery model.
SRM is a disaster recovery and business continuity system from VMware, which automates the transfer
of virtual machines to a local or remote recovery site. SRM works with the existing vSphere software
and operates as an extension of vCenter server. SRM automates the recovery or migration of virtual
machines between the protected site and a recovery site. The Protected site is the primary site where
active production workloads are running. The recovery site is the datacenter location where production
workloads will transfer in the event the primary datacenter is unavailable. Virtual machines are moved
to recover from a disaster or as a planned failover. vCenter Site Recovery Manager facilitates the clean
Page 30
shutdown of virtual machines at the protected site for a planned migration. Non-planned recoveries are
best effort and possibly requiring T-log replay.
Figure 1-8: PremierOne Records DR Replication
VMware SRM is used with VMware vSphere Replication. vSphere Replication copies virtual machines
from one host to another, using the power of the hosts involved rather than the storage system.
During normal operation, the Records clients connect to the Records application servers in the primary
data center. Records data is stored in SQL databases collocated in the primary data center.
The Records data updated at the primary data center is replicated in the on-site backup high availability
Server using Microsoft SQL Always On Availability Groups.
The off-site Records DR server, DR backup server RDW, and Application servers are replicated using
SRM.
Failover from Primary to DR Site
Transition from the primary data center to the recovery data center is a manual process executed by a
System Administrator. The process involves three steps:
Step 1 - Troubleshooting: The Records System Administrator(s) determines that there is a problem
with the primary data center servers. This determination may be based on SCOM alerts, Records Client
user reports, monitoring the SQL Always On dashboard. The System Administrator then investigates
the issue and determines if a failover to the DR site is warranted.
Step 2 - Site Failover: The failover from the primary data center to the DR site is a manual process
performed by the System Administrator using the VMware vCenter client.
Step 3 - Client Redirect: Records clients access the Records application server by Host Name. The
DNS configuration specifies whether the clients are directed to the primary application servers or the
DR servers. During the manual failover process the System Administrator must redirect the Records
Page 31
clients to the recovery data center by updating the DNS service pointer records to reflect the IP address
of the recovery data center.
The system resumes normal operation after failover. After system administrator marked the DR site as
the “protected” site, SRM automatically resumes replication from the now active DR site to the original
primary data center when it becomes available.
If the primary data center, or network connectivity between the sites, is not available then SRM will
operate only on the DR site with no replication to the primary site. Once the primary site is available,
and the system administrator marks the DR as “protected” SRM will automatically start replicating data
from the DR site to the primary.
Failover from DR to Primary Site
The failover process from the DR site to the primary site follows the process described above.
Unless, the primary site has been down for an extended period of time, after a period of non-replication,
there may be a significant difference between the DR database and the primary site database. This can
tax the network connection between the sites. The system administrator can throttle replication traffic if
required.
Records DR User Experience
If the primary application servers or data center are unavailable, the Records Clients will not have
access to the application server and users will not be able to access Records documents. Client users
will not be able to navigate the application, access data, or log into the system.
After the System Administrator has initiated a failover to the DR site and completed the DNS
configuration, Client users may log back into PremierOne Records and resume operation. If a user was
in the process of updating a Document, they may resume at the point of the last Save or Auto Save.
Users (mobile and LAN based) need to logoff and exit the client and then restart and login after the
failover to the DR site is complete.
The Records Client logon screen will notify the user if the Records application server is not available.
In the event that the Records application server version and or Build Set is different on the DR
application server, the client will prompt the User to download a new client. This process is initiated with
a single button press and requires approximately two (2) minutes to complete.
Records DR Performance
The Records DR system provides geographic site redundancy that allows an agency to resume normal
Records operations after transitioning operation to a recovery data center. After an initial diagnostic and
evaluation process the failover is manually initiated and requires approximately 20 (twenty) minutes to
complete. The DNS “time to live” parameter affects the time Records clients may need to wait before
accessing the DR servers.
System Records DR performance is defined in terms of RPO and RTO:
x
RPO - A recovery point objective (RPO) is the maximum period for which data might be lost
from an IT service due to a major incident.
x
RTO - The recovery time objective (RTO) is the duration of time within which a business
process must be restored after a disaster to avoid unacceptable consequences associated with
a break in business continuity.
Page 32
The Records RPO is 15 (fifteen) minutes due to the use of SRM. Data entered into a Records
Document but not saved will be lost (unless it is still contained in a client cache). SRM will replicate
committed SQL transactions. Non-committed transactions will be lost.
The Records RTO is variable due to the manual process. The contributing tasks include problem
diagnostics, manual failover initiation, and DNS configuration updates.
4.4
Legacy Data Services
4.4.1
Legacy Data Access or Transactional Data Conversion
It is a very common desire for agencies when migrating to new systems to preserve and utilize the data
contained in the legacy systems. There are two types of data that will be accessed or migrated and
each type will be treated differently.
The first type of data is configuration data. This consists of code tables and other lists from the existing
CAD or RMS system. This would include data such as unit identifiers, incident types, personnel
information. These data types may either be imported into the PremierOne system or manually entered
during the provisioning process. For those tables to which data can be imported, the common process
is for the Motorola Solutions team to provide spreadsheets to MCSO personnel. MCSO personnel will
export the data from the existing system, transform it as needed to match the provided spreadsheets
and import it into the PremierOne system using the built-in import functionality. Data that will be
manually entered during the provisioning process is gathered by the MCSO and recorded on
provisioning worksheets.
The second type of data is historical data. This consists of the transactional data that is a record of
events / incidences that were recorded in the existing CAD or RMS system. This would include data
such as incident information, unit history information, messaging information.
Below are the strategies being offered to accommodate access to this historical data.
4.4.2
PremierOne CAD Transactional Data Conversion
Motorola Solutions will convert and extract specific data that exists in MCSO legacy CAD system and
then import to the CAD system. While Motorola Solutions is responsible for converting the specified
data, it is critical that the MCSO assigns a knowledgeable resource to this activity that will remain
engaged throughout the migration process.
The legacy databases must be in a MCSO supplied Microsoft SQL Server databases (hardware and
software) external to the system and Motorola Solutions must be able to link directly to the legacy
databases from Microsoft SQL Server. MCSO must also understand the database schema so the table
relations can be understood.
Motorola Solutions does not provide any data clean up or manipulation of the provided data. The
MCSO should conduct a comprehensive analysis of the data in the legacy systems to identify duplicate
data/records, lost data, or orphaned records.
Motorola Solutions will convert the most recent two years of data from the Hexagon system and place it
in the Production system. The remaining eight (8) years of Hexagon and NewWorld data will be
available in MCSO SQL databases for query.
The following are types of data being imported:
Page 33
x
Location
x
Call Type
x
Disposition
x
Comments
x
Units Involved
x
Agencies Involved
x
People Involved
x
Vehicles Involved
Imported incidents will have the following characteristics:
x
Imported incidents will be created and then “closed”.
x
Imported incidents cannot be re-opened or cloned.
x
Imported incidents older than the aging threshold set in PremierOne will be moved to
PremierOne CAD’s RDW and then purged from production.
4.4.3
Legacy Data Access - Data Warehouse
This data will be provided by MCSO in a SQL data warehouse that can be accessed via standard SQL
tools. MCSO can then develop queries and format the returns in PremierOne.
If MCSO chooses to have Motorola Solutions provide the query, they must also supply the database
schema so the table relations can be understood. The PremierOne system will query the data
warehouse for information regarding this data, during normal operations.
The legacy databases must be stored in MCSO supplied relational databases (hardware and software)
external to the PremierOne system and Motorola Solutions must be able to link directly to the legacy
databases from MS SQL Server. Motorola Solutions does not provide any data clean up or
manipulation of the provided data and conducts a single, one time, bulk load of legacy data. MCSO
should conduct a comprehensive analysis of the data in the legacy systems to identify duplicate
data/records, lost data, orphaned records, or records that have not been linked properly and resolve
those issues prior to extracting the data to be converted.
Please refer to the Legacy External Query Interface Functional Description in the Interfaces section.
4.4.4
Legacy RMS Data Convert on Demand to PremierOne Records
Motorola has included the Convert on Demand (CoD) tool that can connect to a Microsoft SQL Server
database and would be configured to read the legacy database records.
MCSO inspects the records to determine if they need to be imported into PremierOne Records. If
needed, that record or multiple records are imported into PremierOne Records on an as-needed basis.
The legacy databases must be stored in MCSO-supplied Microsoft SQL Server databases (hardware
and software) external to the PremierOne system and Motorola Solutions must be able to link directly to
the legacy databases from Microsoft SQL Server. Motorola Solutions does not provide any data clean
up or manipulation of the provided data and conducts a single, one time, bulk load of legacy data.
MCSO should conduct a comprehensive analysis of the data in the legacy systems to identify duplicate
data/records, lost data, orphaned records, or records that have not been linked properly and resolve
those issues prior to extracting the data to be converted.
Page 34
4.4.5
Legacy RMS Data to PremierOne Records Import
Motorola Solutions will extract and convert specific data specified below that exists in the MCSO TraCS
system and then import to the Records system. While Motorola Solutions is responsible for converting
the specified data, it is critical that MCSO assigns a knowledgeable resource to this activity that will
remain engaged throughout the migration process. MCSO must also understand the database schema
so the table relations can be understood.
The legacy databases must be stored in MCSO-supplied Microsoft SQL Server databases (hardware
and software) external to the system and Motorola Solutions must be able to link directly to the legacy
databases from Microsoft SQL Server.
Motorola Solutions does not provide any data clean up or manipulation of the provided data and
conducts a single, one time, bulk load of legacy data. MCSO should conduct a comprehensive analysis
of the data in the legacy systems to identify duplicate data/records, lost data, orphaned records, or
records that have not been linked properly and resolve those issues prior to extracting the data to be
converted.
The following data will be converted/imported:
x
Active case reports
x
Master index information
x
Case Management information
4.5
Third-Party Integrations
4.5.1
RapidSOS Integration for PremierOne
PremierOne Integrates RapidSOS features into PremierOne CAD allowing for faster and more reliable
caller location and to call-takers, improving response to emergency situations.
RapidSOS Location Data Integration
When a call-taker answers a call from within PremierOne, RapidSOS will retrieve the caller’s device-
based hybrid (DBH) location and provide it within three seconds on the call-taker’s CAD interface. The
call-taker can then use RapidSOS to track the location of the caller throughout the call, with location
data accurate to within three seconds each time the call-taker re-bids the location.
RapidSOS Supplemental Data Integration
In addition to location data, RapidSOS aggregates available medical or emergency information about
the caller from multiple data resources, then displays it to the call-taker through the PremierOne user
interface. This helps get crucial information to call-takers faster than questioning the caller —
information that the call-taker can then pass on to first responders to help them maintain their own and
the caller’s safety.
4.6
System Architecture
The PremierOne system is designed on the principles of Service Oriented Architecture (SOA) allowing
separation of servers and services to modular components. The system can be expanded through the
Page 35
allocation of additional physical or logical resources as needs grow. In addition, site-to-site replication
creating a multi-site architecture with disaster recovery is included.
The system is deployed with a single production environment incorporating the high availability
components and interfaces presented in this system. The production environment incorporates the high
availability components and reconfigured interfaces presented in this system.
The system is architected around a virtualized server configuration and supports VMware vSphere 6.5
(or later) for the hypervisor. Server virtualization provides application isolation providing the ability to
isolate specific services for ease of diagnostics and hardware resource management.
4.6.1
PremierOne High Availability Architecture
PremierOne is also architected to have no single point of failure. Its software design is redundant, as
database replication occurs across multiple servers. The system is built on industry standard
components from Microsoft .NET architecture using Microsoft Windows and Microsoft SQL Server and
other vendors.
The combined software, hardware and IT network architecture is designed to provide an integrated
high-availability system at each site. Redundant software and hardware components are the basis of
the high-availability system design. Redundant network paths are used throughout the system
configuration.
Multiple application servers support the application service layer and utilize load balancing to manage
the load across the servers. RAID storage configurations provide redundancy and recovery within the
storage components, and dual power supplies and circuits are used to ensure power redundancy.
Application, database and Application Delivery Controllers (ADC) failovers operate independent of one
another within PremierOne. This means the failure of one component does not require the other
components to failover.
PremierOne’s active monitoring identifies problems and failures before they occur. For example, low
disk space or high processor utilization will trigger an alert to be sent, to notify the recipient of any
possible problems or future failure before it affects the system. In the event of a service or component
failure, PremierOne will stop using the failed service or component instance and automatically shift over
to the secondary service or component instance without impacting operations.
The following depicts the fault tolerant components of the system.
Table 1-6: Fault Tolerant Software Components
Component
Multiple F5 ADCs to provide load balanced network traffic to the application services
PremierOne monitors active services and restarts them as necessary.
In the case of a server failure, the node is disabled transferring the load to the remaining nodes in the cluster.
Replicated databases on different servers. Servers are replicated in a cluster set.
ƒ SQL Server AlwaysOn provides redundancy and automatic failover.
ƒ In case of a database server failure, there is no user intervention required. Secondary database becomes the
active database without administrator intervention and continues processing transactions within the data
center.
Fault tolerant networking components throughout the entire stack, the use of Link Aggregation Groups between
network nodes and multipath configuration such that no single cable, port or device can interrupt system
operation.
Page 36
Component
PremierOne System Manager monitoring:
ƒ CAD application
ƒ Records application
ƒ Application Delivery Controller cluster
ƒ Database status
ƒ Disk space
ƒ Windows Performance Counters
The backup service (backup library and backup software), the Report Data Warehouse (ad hoc
reporting services), and the Test/Training environments are not designed to meet the same high
availability requirements as the production application and database servers. Reporting services and
test/training environment(s) are not considered critical and therefore are not redundant in the
configuration.
High availability is independent of a geographically redundant secondary disaster recovery system.
The system design also provides dual limited use environments that can be used as test and training
environments. One of the limited use environments will include simulated interfaces, as described in
Section 4.1.5.
Environment Summary:
x
1 Production Environment for both the Primary and Disaster Recovery Sites
x
1 Limited Use for Test or Training for both the Primary and Disaster Recovery Sites
x
Second Limited Use to segregate Test and Training
4.6.2
Microsoft Active Directory Service (On-Premise)
The system provides directory services to support the secure management and operations of the
system through an isolated Microsoft Active Directory (AD) environment. The servers provided with the
system contain computer accounts in this AD tree. Service and Administrator user accounts and groups
will be set up in the isolated Active Directory with the appropriate group memberships set.
In order to facilitate ease of user account management, the system can use MCSO’s AD environment
for authentication. Once the user account is built in the system provisioning, it can then use LDAP to
query MCSO’s environment for the account authentication. By using this configuration, MCSO can
enforce password policy, retention, and complexity requirements across the enterprise with a user
having a singular identity.
Motorola Solutions will provide a one-way forest trust from the system local domain to MCSO’s Active
Directory environment. The trust provides users with Domain Administrator privileges on MCSO’s AD
instance to access and administer the system environment while preserving authentication and logon
information. Motorola Solutions recommends that this trust be non-transitive in nature. Motorola
Solutions does not recommend a two-way trust, as none of the system service accounts need
authentication or resources on MCSO’s network.
The system’s Active Directory schema is for servers and services. Active Directory user authentication
(if desired) will be against MCSO's Active Directory schema.
Page 37
4.6.2.1
Name Resolution
The system provides host name resolution through an Active Directory Integrated Domain Name
Service (DNS). In order for computers residing outside of the system’s network to communicate with
the system, MCSO must configure their DNS servers to forward their computer’s name resolution
requests to the system’s DNS servers. This will allow devices on MCSO network to find systems within
the system’s environment.
For increased integration, MCSO, working with Motorola Solutions, must configure their DNS servers to
allow name resolution requests from within their networks to be processed.
4.6.3
Common Services
Common Services provides system administrators the flexibility to manage internal services throughout
the platform from a single point. The system’s Common Services include GIS, System Security,
Reporting, and the system tools for provisioning.
4.6.3.1
Geographic Information System (GIS)
Geo-spatial data is uploaded to the system through tools implemented within Esri ArcGIS. Address
validation data is maintained in redundant Microsoft SQL Server geodatabases that store locations and
boundaries both spatially and in optimized search tables. Esri ArcGIS Servers provide routing and ETA
calculations using the Network Analyst extension. Client maps are displayed using Esri ArcGIS Engine.
x
The system uses GIS for display, location validation, and unit recommendation. The system’s
tools made available for ArcTool box, provides the ability to load local data manually or through
an automated model.
x
The system’s Response Boundary Data Import Tool imports and aggregates boundaries in
multiple layers into a single spatial table within the geodatabase for support of multi-agency /
multi-jurisdictional scenarios. GIS data is a required key component of a system deployment.
GIS provides the mechanism for location validation and recommendation for response.
x
A system conformant and geographically accurate GIS data is required for the proper operation
of the system. It is MCSO’s responsibility to provide a complete and accurate GIS data that
conforms to the PremierOne GIS Data Requirements as noted in Section 4.1.12 for use in
PremierOne. Each agency being added to the system must have their geographic coverage
included in the geodatabase imported into the system.
x
The use of remote and/or Esri Online services is not supported. Motorola Solutions is not
responsible for map availability or any degradation of client performance caused by the use of
third-party hosted internet map services as these services are outside the domain of the system
infrastructure and are not managed by Motorola Solutions. The system is a mission critical
application that must control the import/access of the GIS data.
4.6.3.2
System Security
The system is deployed within its own Microsoft Active Directory (AD) domain in its own local area
network. Active Directory Domain Controllers authenticate and authorize users to perform actions within
the domain making sure authorized users have appropriate access to data and services. The system
user provisioning environment can be set up to query your AD environment (using LDAP) allowing for a
single point of user and password management across all applications.
The system network contains multiple virtual local area networks that are used to secure and segment
traffic for purposes of user access as well as data storage and replication. System architecture resides
Page 38
behind dual redundant firewalls to protect the system network from unauthorized intrusion and security
threats. These firewalls are provisioned in a high availability configuration so if either of the two fails,
traffic and security will remain intact across the other.
4.6.3.3
Query Services
PremierOne allows users to submit requests for information to external databases. These external
queries can involve local agencies, as well as state and federal agencies. External databases all have
their own data formats and respond to submitted queries with one or more responses. These queries
can be made available to all PremierOne applications.
PremierOne also allows MCSO to build queries against a local database during query provisioning. If a
query is configured for submission to both a state interface and a local database, state queries will
continue to be passed to the existing CommSys interface, while the local database query will run
through the custom XML (in a Motorola Solutions template) provided by MCSO.
4.6.3.4
Microsoft Reporting Services
PremierOne uses Microsoft SQL Server 2017 Reporting Services (SSRS) for reporting purposes. SQL
Server 2017 Reporting Services is a server-based reporting platform that is used to create and manage
tabular, matrix, graphical, dashboards, and free form reports that contain data from relational and
multidimensional data sources. The reports can be viewed and managed via a browser.
PremierOne also fully supports the use of Crystal Reports. The PremierOne Report Data Warehouse
(RDW) contains Criminal Justice Information System (CJIS) compliant data for the purposes of report
generation. The PremierOne CAD RDW is designed with views that are available for access by Crystal
Reports.
4.7
System Platform and Components
This section discusses the hardware, operating system, and system software of the system which will
be installed on premise at MCSO’s Data Center Facility. Quantities of hardware are provided in the
Equipment List in Section 4.11.1.
Note: It is the responsibility of MCSO to provide any specialized hardware and installation to ensure compliance
with any Local, State or Federal natural disaster safety regulations.
4.7.1
PremierOne System Hardware
The PremierOne hardware stack is comprised of various components selected for the need to provide
redundancy and high availability in a mission-critical environment. Specifications for the hardware are
also scoped around expected call volume metrics listed above. Additional hardware may be needed to
support functions unique to MCSO such as specific third-party integrations.
The system hardware is comprised of Hewlett Packard Enterprise (HPe) servers as physical hosts.
Host servers are HPe DL360c Gen11 servers configured with the following components:
x
Dual Intel® Xeon® Gold 6444Y processor, 32GB PC5-4800 Memory, BCM 57416 10GbE 2 Port,
The Monitor server is an HPe DL360 Gen11 configured with the following components:
x
Intel® XeonS® 4410Y processor, 32GB PC5-4800 Memory, with 1.2TB SAS 10K SFF
Page 39
x
Network Performance Monitor and Traffic Analyzer Module
4.7.2
PremierOne System On-Premise Storage
The system’s online storage is provided through Alletra. Our system design provides storage area
arrays that are utilized by the host servers for storage.
Alletra Storage
HPe Alletra systems support all-NVMe for accelerated applications and improved density. Alletra is
ideal for mission-critical workloads with extreme workload latency sensitivity and availability
requirements. A unique, multinode, all-active platform delivers massive parallelization for consistent
and predictable performance at scale. Alletra can be non-disruptively scaled- independently of capacity
to flexibly match workload and capacity requirements.
The Alletra 5000 Series SAN provides 46 TB of RAW storage.
4.7.3
PremierOne Network and Management Components
Motorola Solutions has included network hardware for the system server architecture. Networking
hardware for the connectivity outside the system LAN must be provided by MCSO.
Fortinet FortiGate Network Devices
Component isolation provides reliability, availability, and performance. The system is based on Fortinet
FortiGate devices to provide the perimeter network router, firewall and Virtual LAN (VLAN)
configurations for the PremierOne system. MCSO needs to supply four (4) 1GB LAN connections per
FortiGate; with a total of eight (8) 1GB connections.
Extreme Networks Data Center Switches
The ExtremeXOS modular operating system supports intelligent Layer 2 switching, Layer 3 IPv4/IPv6
routing, as well as role-based policy capabilities.
The ExtremeSwitching products are compact Ethernet switches. The switches and their design were
chosen to provide system availability and redundancy and connectivity for management activities.
F5 BigIP Application Delivery Controllers
The system consists of a virtual Application Delivery Controllers (ADC) for the system. These are
purpose-built appliances that reside outside of the application servers that present a “virtual server”
address to the outside world. Upon user connection, these appliances will forward the connection to the
most appropriate real server using bi-directional network address translation (NAT).
Network Management Tools
The system consists of a dedicated virtual server to host an instance of the network management tools.
The network management tool is set up to monitor traffic and critical data points through the firewalls
and load balancers to ensure appropriate system health. Additionally, it monitors and logs CPU and
memory utilization on all hardware components as well as various application-level metrics. Monitoring
occurs for both sites using a dedicated out of band management server. This data provides Motorola
Solutions’ support teams with the information necessary to support the system and provide historical
measurements of system performance, while also being able to provide a near real-time status
dashboard.
Page 40
4.7.4
Benefits of Motorola Solutions-Provided Hardware
Motorola Solutions designs the system to provide high levels of system availability, reliability, and
performance required for mission critical public safety applications. Motorola Solutions designs, tests,
and deploys the system’s software and hardware architecture for those requirements. The Motorola
Solutions defined hardware ensures physical redundancy throughout the critical components of the
system and is designed to support the system’s software architecture. Motorola Solutions is continually
evolving and enhancing the hardware, software, tools, scripting, and processes used to monitor,
manage, diagnose, troubleshoot, and tune a system. Use of the Motorola Solutions hardware platform
enables the full use of those optimizations and capabilities. With alternative platforms the full extent of
these capabilities are not possible.
Mitigating risk and ensuring predictable performance is a concern when a system is deployed on a
MCSO defined hardware platform. With the Motorola Solutions configuration, MCSO system will be on
the same platform that Motorola Solutions used to develop and test the system. Motorola Solutions
runs functional, performance, and deployment/upgrade tests against each system standard software
release. The Motorola Solutions platform also benefits from the collective knowledge and experience of
multiple Motorola Solutions deployments on the same platform. Optimizations, issue resolutions,
system configuration and management best practices, and historical data analysis are shared across
the systems on the Motorola Solutions platform. An alternative platform does not leverage these
benefits.
Motorola Solutions continues to enhance the capabilities to monitor the system, including incorporation
of Network Management software to monitor the network traffic and physical components of the
Motorola Solutions defined platform. Additionally, Motorola Solutions has developed scripts and tools to
monitor the system components. These scripts, tools, and software are designed specifically for the
Motorola Solutions platform and do not work with alternative platforms.
To ensure the most predictable, consistent, and optimized system builds, Motorola Solutions has
defined a rigorous system staging process. An established order-through-delivery process is used with
our suppliers, including specific factory build instructions, to ensure seamless end-to-end system
staging. As technology evolves and advances, this staging methodology ensures that changes to the
platform are incorporated into the system build. Within the staging process, Motorola Solutions
performs a variety of tests, including system load tests, to ensure a proper system build. This consistent
approach facilitates lower project costs and risks.
Motorola Solutions believes MCSO will find our pricing of the required PremierOne equipment to be
competitive, and the benefits of Motorola Solutions performing the system purchase and staging to be
valuable.
4.8
MCSO-Provided Workstation Specifications
Workstation specifications are representative of workstations used in the testing of the latest release of
system software and do not take into account any other applications.
Future releases of the system may dictate changes to the workstation specifications. Each agency
should consider their own technology replacement lifecycles and policies for specific purchase
decisions.
Page 41
4.8.1
PremierOne CAD Minimum Recommended Specifications
Table 1-7: PremierOne CAD Workstation Minimum Recommended Specifications
Component
Description
Processor
3 GHz Processor (not turbo) Intel® Core i9 Xeon® series preferred
RAM Memory
16 GB or more of memory, ECC preferred. (Although not needed for the
PremierOne client, inclusion of additional memory (example, 16GB) in new
workstation purchases is common for future capacity.)
Available Disk Space
20 GB available disk space; minimum 256 GB solid state drive (SSD) required for
optimal performance
Operating System
Windows 10 Professional higher (64-bit recommended)
Network Interface Card
100 Mb or faster (Gigabit recommended) Ethernet network adapter
- Note that network latency will impact system performance.
Display
Three (3) – 1920 x 1080+ pixel, 16+ bit color displays, 60Hz display refresh rate
Keyboard/Mouse
QWERTY Keyboard with 12 Function Keys and Touchpad / Point Stick (or
equivalent mouse device)
Graphics Adaptor
Discrete Graphics adapter with at least 512 MB RAM per monitor, 24-bit capable
graphics accelerator, OpenGL v2.0 runtime or higher. Latest available drivers.
Shader Model 3.0 or higher is recommended. AMD FirePro or Nvdia Quadro
series.
Network Bandwidth
2 Mbps network bandwidth (to server) with 20 ms or less round-trip latency
Additional Required
Software Applications for
PremierOne CAD
Adobe PDF reader (for help files)
SQL Server Express 2017 CU level supporting TLS 1.2 is required.
ArcGIS Engine 10.6.1 (included with PremierOne CAD client software)
Microsoft .NET Framework v4.8 and above
CAD Visual Map Files
Required
MXD and GDB formats
4.8.2
PremierOne Mobile and Records Mobile Workstation Minimum
Recommended Specifications
Table 1-8: PremierOne Mobile and Records Mobile Workstation Minimum Recommended Specifications
Component
Description
Device
Modern “business grade” or “ruggedized” Windows notebook
Processor
Multi-core processor (i5 or higher, 4-thread, 2.6 Ghz +), Intel® CoreTM or
newer Intel® Series
RAM Memory
16 GB or more RAM (4 GB must be available for PremierOne Mobile)
Available Disk Space
20 GB or more available disk space; SSD (Solid State Drive) recommended
Operating System
Windows 10 Professional or higher (64-bit recommended)
Network Interface Card
Wireless communications minimum 3G network, 4G/5G network
recommended
Network Middleware
1. Mobile Virtual Private Network (mVPN) with routing and IP persistence to
PremierOne system network
Page 42
Component
Description
Display
1024 x 768+ pixel resolution display minimum, 16+ bit color display, 11.6” or
larger display.
Usage on devices with alternative resolutions and smaller screens should be
tested and screen settings optimized. Example: On a 10.1” WUXGA screen,
use a resolution of 1280 x 800 and a font size of 125%.
Keyboard/Mouse
Standard QWERTY Keyboard with 12 Function Keys and Touchpad / Point
Stick (or equivalent mouse device)
Touchscreen
Optional
Graphics Adaptor
Discrete graphics card with at least 256 MB of RAMs
Additional Required Software
Applications for PremierOne
Mobile
Adobe PDF reader (for help files)
SQL Server Express 2017 CU level supporting TLS 1.2 is required.
Microsoft .NET Framework v4.8
Additional Required Software
Applications for PremierOne
Mobile Mapping
ArcGIS Engine 10.6.1 for Classic Map
Microsoft Visual C++ Redistributable for Visual Studio 2017
Mobile Symbology Map Format
Required
2. MMPK format with locater and routing features with a separate MMPK
with night mode symbology, if required
4.8.3
PremierOne Records Workstation Recommended Specifications
Table 1-9: PremierOne Records Workstation Recommended Specifications
Component
Description
Processor
2.0 GHz or better processor
RAM Memory
16 GB or more of memory
Available Disk Space
20 GB or more of available disk space for PremierOne
Solid State Disk Recommended
Operating System
Windows 10 Professional or higher (64-bit recommended)
Display
1024 X 768 or higher pixel, 16+ bit color display
Keyboard/Mouse
Standard QWERTY Keyboard and Touchpad / Point Stick (or equivalent mouse
device)
Touchscreen
Optional
Additional Required Software
Applications for PremierOne
Records
Adobe PDF reader (for help files)
SQL Server Express 2017 CU level supporting TLS 1.2 is required.
Microsoft .NET Framework v4.8+
Microsoft Visual Studio for the creation of In-Module Reports.
4.9
TCP/IP Network and Data Center Requirements
4.9.1
MCSO Network Requirements
Motorola Solutions’ system requires TCP/IP protocol for connectivity. All servers and workstations will
connect to MCSO’s existing network. MCSO will provide access to facilities and a dedicated resource
knowledgeable on MCSO’s WAN/LAN. MCSO will supply IP addresses and a mechanism for
Page 43
maintaining IP persistence. Desktop, Mobile, and Handheld clients require a persistent IP address from
the time the application is opened to the time the application is closed.
Motorola Solutions’ delivery model is reliant upon our ability to perform some tasks remotely, which
requires secure, remote broadband access for remote deployment, monitoring and support of the
system. MCSO-provided high-speed internet access with a minimum bandwidth of 10 Mbps is required
at the time of project kickoff and must remain available to Motorola Solutions throughout warranty and
support periods to accommodate remote support of the system. In the event that dedicated links are
required, a minimum of 7.5 Mbps upload and download access is required. It is MCSO's responsibility
to ensure that the aforementioned capacity is available. In the event remote broadband access is not
available to Motorola Solutions, preventing us from delivering the contracted service remotely, Motorola
Solutions will provide service on-site at additional cost. The additional cost will be presented to MCSO
via the change provision of the contract prior to the delivery of the on-site service.
PremierOne System CAD Client Network Requirements
The system is dependent on MCSO’s LAN for client workstation performance. The estimated network
requirement per CAD client with typical usage is 0.8 Mbps – 1.2 Mbps. The recommended built-to
bandwidth is 2 Mbps per workstation. Peak load events (e.g. login) require higher bandwidth and higher
bandwidth will generally be required for sites with higher quantities of users and greater data intensive
operations such as complex map annotation sets and map manipulation if the data resides on the
server. The bandwidth recommendations account for the operation of the LAN client to “not exceed the
values” with the map data being stored locally on the client workstation. Additional bandwidth will be
required for the transfer of large multimedia files, premise hazard data files and other large
attachments.
Network latency plays a key role in the responsiveness of CAD client operations. The system is
designed for optimal use on a local network environment where latency is very low. It is important that
efforts be made to provide the lowest latency possible between the system CAD servers and each CAD
client. PremierOne requires latency of no greater than 20ms round-trip from the client to the servers
and back.
PremierOne CAD Mobile and Records Mobile Client Network Requirements
Both CAD Mobile and Records Mobile's functionality is designed for 3G and 4G networks. 3G network
connectivity is required but 4G connectivity is highly recommended.
MCSO will need to provide 3G/4G wireless network infrastructure and connectivity with routing between
the Mobile clients and both the primary and, as applicable, at secondary disaster recovery site. Mobile
workstations require a persistent IP address from the time the application is opened to the time the
application is closed. A persistent IP address can be accommodated in many ways including static IP,
DHCP reservation, permanent DHCP lease, or with middleware such as RadioIP and NetMotion.
MCSO will need to supply IP addresses for Mobile clients.
PremierOne Records Client Network Requirements
Records is dependent on MCSO’s LAN for client workstation performance. The estimated bandwidth
requirements between server and a records client can vary based on the activity of the user. It is when
documents are being requested or submitted and searches are being performed, is when network
bandwidth is required. During data entry, network requirements are minimal. Peak load events (e.g.
login) require higher bandwidth and higher bandwidth will generally be required for sites with higher
quantities of users and higher frequency data intensive operations including image display.
Motorola Solutions encourages MCSO to test and evaluate the level of service being provided by their
carriers on a regular basis. This is to validate mobile applications will be not affected by provider
changes.
Page 44
4.9.2
MCSO Data Center Requirements
The environmental data center requirements stated in the following sections must be satisfied in order
to support the PremierOne installation. The requirements specify what MCSO must perform, provide, or
ensure in order to prepare for and aid with the system deployment.
Included in the requirements are various considerations for the servers and supplemental equipment,
power and network connectivity, access to various information and resources, and compliance with
laws and specifications.
Equipment Server Rack Specifications
The following tables provide Server Rack specifications needed to meet shipping and installation
requirements. This table will be updated if required, based on the final BOM.
Table 1-10: Server Rack Specifications
Component
Specifications
Server Rack Dimensions:
78.9 in. x 39.7 in. x 24 in.
Shipping Dimensions (with packaging materials):
86.2 in. x 48 in. x 35.6 in.
Shipping Weight:
766 lb. – Total
Installed Weight:
385 lb. – Rack
381 lb. – Equipment
766 lb. – Total
Maximum Load of Rack:
3000 lb.
Minimum Cabinet Clearance:
Front: 48 inches
Back: 30 inches
Power Distribution Units
HPe 4.9kVA 208V
Power Requirements and Heat Output
The following tables provide representative examples of the power utilization, heat output, and the
temperature ranges for the various components of the system and the electrical circuits needed by the
overall system. It is important to note that these numbers represent an estimate only. This table will be
updated, if required, based on the final equipment list.
Table 1-11: Power Requirements and Heat Output
Component
Max Total Power
(Watts)
Total Heat Generation
(BTU/hr.)
System Rack
7808
17610
Cooling airflow through each server rack enclosure is front-to-back. Because of high heat densities and
hot spots, MCSO must ensure that an accurate assessment of airflow into and out of the server
equipment has been performed. This is essential for reliable server operation. Airflow assessment is
not within the scope of Motorola Solutions’ responsibility.
Table 1-12: Temperature and Humidity Ranges
Specification
Operating
Temperature Range
50°F to 95°F
Relative Humidity Range
20% to 80% (non-condensing)
Page 45
Circuit Requirements
The system racks require a specific type of connector due to the type of equipment housed in each
rack. The power circuit requirements for each system server rack are contained in the table below.
Table 1-13: PremierOne Server Rack Circuit Requirements (per rack)
Voltage (VAC)
Dedicated Branch Circuit
Rating (A)
Quantity
Line Cord
208
30
3
NEMA L6-30P
4.10
CJIS and Compliance
At Motorola Solutions we believe compliance is a team effort. As our customers’ partner in compliance,
we are committed to employing privacy and security protocols that enable our customers to comply with
the most stringent legal and regulatory requirements. In addition, we build on a strong foundation with
an architecture (both Azure and on premise) designed and managed to meet a broad set of
international compliance standards, as well as region-specific and industry-specific standards.
System services are designed to use FIPS certified technologies to protect data at rest and in transit.
PremierOne services utilize FIPS compliant Transport Layer Security (TLS) 1.2 protocol with AES 256-
bit message encryption to establish secure communication with PremierOne CAD and Records and the
CAD and Records Mobile Clients.
Motorola Solutions employs rigorous third-party audits to verify its adherence to security controls and
standards. To demonstrate Motorola Solutions safeguarding of MCSO data, comprehensive third-party
audits of primary Software Enterprise development and support operations have been completed and
those operations have achieved ISO/IEC 27001:2013 (information security management systems)
certification and AICPA SOC2 Type 2 reports are available. ISO/IEC 27017:2015 (information security
controls for cloud services), ISO/IEC 27018:2019 (protection of personal information in public clouds)
and ISO/IEC 27701:2019 (privacy information management) have been completed. Supplemental
SOC2 Type 2 reports and ISO/IEC 27001:2013 certifications for the development and support
operations at satellite locations have been completed.
Motorola Solutions understands MCSO’ critical need to safeguard the lifecycle of Criminal Justice
Information. To support that need, Motorola Solutions designs its products and services to support
compliance with the FBI’s Criminal Justice Information Services (CJIS) Security Policy and we commit
to the terms of the CJIS Security Addendum. With a dedicated team of CJIS compliance professionals,
we assist MCSO through administering and coordinating CJIS compliant personnel credentialing,
providing documentation assistance in connection with CJIS audits and advising on how to configure
and implement our solutions in a manner consistent with the CJIS Security Policy.
4.11
PremierOne CAD, Mobile, and Records Equipment
List and Rack Layout
4.11.1
Equipment List
The following equipment list contains the type and number of software licenses, server hardware and
ancillary items provided by Motorola Solutions.
Page 46
Table 1-4: Equipment List
Name
Qty
PremierOne® HP Servers
PremierOne® HPE DL360 Gen11 Host Server (12 cores)
Includes Microsoft Windows Server OS
10
PremierOne® HPE DL360 Gen11 Monitor Server
Includes Microsoft Windows Server OS
1
PremierOne® Host Server Cables
PremierOne® Cable RJ-45(M) to RJ45(M) UTP 2.13m CAT6a Blue
12
PremierOne® Cable RJ-45(M) to RJ45(M) UTP 2.13m CAT6a Aqua
28
PremierOne® Cable RJ-45(M) to RJ45(M) UTP 2.13m CAT6a Black
28
PremierOne® Cable RJ-45(M) to RJ45(M) UTP 2.13m CAT6a Orange
32
PremierOne® Cable RJ-45(M) to RJ45(M) UTP 15.2cm CAT6 Red
2
PremierOne® OS/DB and Utility Software
Microsoft SQL Server Enterprise 2019 4 Core Base License
6
Microsoft SQL Server Enterprise 2019 2 Core Add License
10
Microsoft SQL Server Standard 2019 4 Core Base License
9
Microsoft SQL Server Standard 2019 2 Core Add License
20
Microsoft®SysCtrDatacenter SCOM 2019 2 Core Base and Add. License Packs
4
PremierOne® VM, Monitoring and ADC Software
VMWare vCenter 8 Std.
2
VMWare vSphere 8 Ent+ CPU
21
VMWare Site Recovery Manager 8 (SRM) 25 pack
1
PremierOne® Networking Hardware
PremierOne® Empty Rack
1
PremierOne® KVM
1
PremierOne® Power Distribution Unit
4
PremierOne® Rack Power Cables
1
FortiGate FG601E Firewall for PremierOne®
2
FortiGate FG601E Firewall PSU for PremierOne®
2
ExtremeSwitching – 32 Ports – Managed – Rack-Mountable
4
ExtremeSwitching – 48 Ports – Managed – Rack-Mountable
1
F5 BIG-IP LTM 1G Load Balancer
2
Other Hardware
Lantronix UDS1100 (One Required for Each 911 Interface)
2
Storage Hardware and Software
Alletra 5000 Series 46TB
2
TrueNAS R20 Network Attached Storage Appliance
1
TrueNAS R20 5 Yr. Support w/Drive Retention
1
Implementation/Installation
PSA Motorola Professional Services – Project Management
Included
Page 47
Name
Qty
PSA Motorola Professional Services – Engineering
Included
System Staging – CCSI Floor Space
Included
4.11.2
System Reference Equipment Rack Layout
Figure 1-2: Hardware Rack Layout for Primary and DR Sites
Note: This is a representative diagram only final configuration will be determined during system staging and is
subject to change.
MCSO must provide access to the loading dock at the installation location for the delivery of equipment
and that a MCSO resource is able to receive and secure the storage of equipment. Additionally, a
temporary staging area for the unpacking and assembly of equipment must be provided.
MCSO is responsible for any accommodation necessary to provide clearance and access through
hallways, doorways, and elevators meeting or exceeding the specifications of the shipping
container/rack at all sites housing system components.
Page 48
4.12
PremierOne GIS Requirements
4.12.1
Overview
This document contains information regarding Motorola PremierOne® GIS data requirements.
A Geographic Information System (GIS) is a system used to collect, manage, analyze, and display
geographic data. This document is intended for use by personnel who are responsible for administering
the GIS components of the PremierOne suite. System administration requires an understanding of both
current agency system administration rules and procedures and how PremierOne functions. For more
information about specific applications, see the PremierOne CAD User Guide, the PremierOne Mobile
User Guide, and the PremierOne Provisioning Guide which are provided post contract.
4.12.2
PremierOne Services Geodatabase
A “Geodatabase” is the common data storage and management framework for ArcGIS. Among other
things, it provides the ability to define table columns that use a spatial, or geometric, data type.
Database tables used to implement the Geodatabase are stored in an underlying RDBMS, such as
Microsoft SQL Server. Geodatabase tables that contain a spatial data type are called “Feature
Classes”. Feature Classes with the same spatial reference can be logically grouped within a “folder”-
like entity called a “Feature Dataset”. The PremierOne Data Import Tools import MCSO’ GIS data into
an SQL Server environment. The schema of the PremierOne Geodatabase has been designed to
provide optimal performance of the GIS services required by PremierOne.
4.12.3
GIS Data Requirements and Recommendations
The data recommendations provided by Motorola are to ensure appropriate functionality of MCSO’s
data within the Motorola System. The state and quality of GIS data used can directly affect ease of
implementation of the Motorola Systems, ability to perform address validation, response determination,
and on-going operations related to the Motorola System.
This document will describe the data values that must be available in any feature class that will be
imported into PremierOne. The names of the source feature classes and their fields do not need to
follow any standard. The data import tools will prompt the user to specify the source field name
associated with a logical value, such as “street name” or “city.”
There are two categories of GIS data utilized by PremierOne:
x
Services data – Data imported from MCSO’s GIS source for access by PremierOne’s
application services. This data is in a schema that is optimized for PremierOne’s address
verification, geocoding, routing, and jurisdiction determination services. Because this data is in a
specialized schema, it is not intended to be displayed on a map for visualization by dispatch or
mobile users.
x
Map data – Data that is displayed as geographic features on a map. As such, a map data
source must contain a spatial attribute. Map data sources are copied into the PremierOne
database using a MCSO-defined schema and are used as data sources for layers in a map
document (.mxd). In addition to the spatial attribute, map data sources typically contain
text/numeric attributes, such as feature names and other information of operational value.
It is expected that MCSO already maintains GIS data in ArcGIS. MCSO’s GIS data may represent data
that is used for a variety of municipal purposes such as growth planning, zoning, utilities, public safety,
et cetera.
Page 49
4.12.4
GIS Data Supported by PremierOne Services
The following GIS feature types that can be utilized by PremierOne are:
x
Street Centerlines
x
Address Points
x
Common Places
x
Response Boundaries
x
Reporting District Boundaries
x
Contractor Boundaries
x
Map Book Page Boundaries
x
Premise Hazard Areas
The following is a high-level description of the required data used for PremierOne and the optional data
that is not required but may be included by MCSO. An in-depth discussion of data structure and formats
is covered during the Kick-off meeting.
4.12.4.1
Street Centerline
The Street Centerline data source must contain, at a minimum, the data in Table 1-1: Street
Centerline Required Schema Definitions:
Table 1-1: Street Centerline Required Schema Definitions
Field
Required
Data Type
Descriptions
Left Low House
Yes
String (25)
Field contains the starting house number on the left side of
the street. A house number may be numeric or in a
supported alphanumeric or hyphenated format.
Left High House
Yes
String (25)
Field contains the ending house number on the left side of
the street. A house number may be numeric or in a
supported alphanumeric or hyphenated format.
Right Low House
Yes
String (25)
Field contains the starting house number on the right side of
the street. A house number may be numeric or in a
supported alphanumeric or hyphenated format.
Right High House
Yes
String (25)
Field contains the ending house number on the right side of
the street. A house number may be numeric or in a
supported alphanumeric or hyphenated format.
Street Name Part
Fields
Yes
String (100)
A list, in order, of the fields in the source Feature Class that
make up the street name. This may include parsed fields
containing the prefixes, suffixes, and name or the street
name may be stored entirely in a single concatenated field.
Left City
Yes
String (150)
City Name - Field can represent jurisdictional city or city
code.
Right City
Yes
String (150)
City Name - Field can represent jurisdictional city or city
code.
Left Postal City
No*
String (150)
Postal City Name - *Required for PremierOne Records.
Right Postal City
No*
String (150)
Postal City Name - *Required for PremierOne Records.
Left Zip Code
No*
String (20)
Postal Zip Code - *Required for PremierOne Records.
Page 50
Field
Required
Data Type
Descriptions
Right Zip Code
No*
String (20)
Postal Zip Code - *Required for PremierOne Records.
State
No*
String (50)
The State/Province in which the street exists.
*Required for PremierOne Records.
Table 1-2: Street Centerline Non-Required Schema Definitions exhibits the additional data fields that
are not required but may be used with PremierOne:
Table 1-2: Street Centerline Non-Required Schema Definitions
Field
Required
Data Type
Description
Left Subdivision
No
String (150)
The name is associated with a small area (neighborhood,
business park, etc.) within a city on the left side of the
street.
Right Subdivision
No
String (150)
The name is associated with a small area (neighborhood,
business park, etc.) within a city on the left side of the
street.
Description
No
String (100)
The field in the source Feature Class containing a free-text
description of the street segment. This can be used to
differentiate street segment features with similar names and
address ranges.
Low Cross Street
Override
No
String (100)
PremierOne automatically generates the cross streets
based on the street centerline file during the import process.
If a different low cross street is desired it must be entered in
this field to override the automatic assignment.
High Cross Street
Override
No
String (100)
PremierOne automatically generates the cross streets
based on the street centerline file during the import process.
If a different high cross street is desired it must be entered
in this field to override the automatic assignment.
Cross Street
Bypass Field
No
String (2)
Denotes which cross street fields need to be protected – L
represents the Low Cross Street Name, H represents the
High Cross Street name, and LH represents both the Low
and High Cross Street names.
For street centerline routing, the following fields are required and recommended. The routing street
centerline may be a different feature class than what is used for address validation above.
Table 1-3: Street Centerline (Routing) Schema Definitions
Routing
Cost (Time)
Yes
Double
There must be a field in the source street centerline feature
class that represents the average time required to traverse
the segment. There may be separate values for the left and
right side of the street segment if necessary.
A formula to determine the travel cost: Minutes: (length of
segment in feet x 0.0114) / speed (mph) or Seconds:
(length of segment in feet x .682) / speed* (mph).
(Length of segment in meters x 0.0373) / speed (mph)
(Length of segment in meters x 0.0600) / speed (kph)
*Speed Limit is a required field used to calculate Cost.
Page 51
Routing
From Elevation
No
Long Integer
Specifies the ‘elevation’ of a segment FROM node. This
field does not require actual elevation in terms of real-world
measurements. The value is only used to determine
whether a turn is allowed from one street to a street that
intersects it in a 2-dimensional space.
To Elevation
No
Long Integer
Specifies the ‘elevation’ of a segment FROM node. This
field does not require actual elevation in terms of real-world
measurements. The value is only used to determine
whether a turn is allowed from one street to a street that
intersects it in a 2-dimensional space.
OneWay
No
Double
Specifies the allowed traffic flow on a street segment with
respect to the FROM and TO nodes. Valid Values are: FT
that specifies the traffic may only flow in the direction from
the FROM node to the TO node. TF which specifies the
traffic may only travel from the TO node to the FROM node.
NT which specifies that traffic does not flow on the
segment. NULL or any other designation defines that traffic
may flow in either direction (FROM node to TO node, TO
node to FROM node).
4.12.4.2
Street Name Aliases
Street Name Aliases are maintained in a separate table. The GIS BA provides a blank Street Name
Alias table to MCSO. The schema definitions are exhibited below in Table 1-4: Street Name Aliases
Schema Definitions:
Table 1-4: Street Name Aliases Schema Definitions
Field
Data Type
Description
GRID
String (8)
Alpha “grid” part – required for alphanumeric
house numbers.
LOW_HOUSE
Long Integer
The low house numbers for which the alias should
be applied. If the alias should be applied to the
entire range of the street, simply use 1-
999,999,999.
HIGH_HOUSE
Long Integer
The low house numbers for which the alias should
be applied. If the alias should be applied to the
entire range of the street, simply use 1-
999,999,999.
REAL_PRE_DIR
String (4)
Prefix Direction of “real” street name.
REAL_PRE_TYPE
String (8)
Prefix Street Type of “real” street name.
REAL_STREET_NAME
String (76)
“Real” street name.
REAL_SUF_TYPE
String (8)
Street suffix type of “real” street name.
REAL_SUF_DIR
String (4)
Street suffix direction of “real” street name.
ALIAS_PRE_DIR
String (4)
Prefix direction of “alias” street name.
ALIAS_PRE_TYPE
String (8)
Prefix street type of “alias” street name.
ALIAS_STREET_NAME
String (76)
“Alias” street name.
ALIAS_SUF_TYPE
String (8)
Street type of “alias” street name.
Page 52
Field
Data Type
Description
ALIAS_SUF_DIR
String (4)
Suffix direction of “alias” street name.
CITY
String (150)
Name of the city in which the street belongs.
Aliases will only be applied to street segments
where the street name parts and the city name
match exactly between this table and other
addressing feature classes loaded to the system.
4.12.4.3
Street Name Standardization Exceptions Table
The Street Name Standardization Exception table is used to assure that street names that match a
predefined directional name are parsed correctly when loaded into the PremierOne data schema. For
instance, a street name of W ST would be interpreted as a prefix of W and street name of ST when
loaded into the PremierOne data schema.
x
Examples of predefined directionals are: S, N, W, E, NW, NE, SW, SE, etc.
Street Name Standardization Exceptions are maintained in a separate table. The GIS BA provides a
blank Street Name Standardization Exceptions table to MCSO. The schema definition for this table is:
Table 1-5: Street Name Standardization Exceptions Schema Definitions
Field
Data Type
Description
FULL_STREET
String (100)
The entire street name with prefixes and suffixes.
PRE_DIR
String (4)
Prefix Direction.
PRE_TYPE
String (8)
Prefix Street Type.
STREET_NAME
String (76)
Street Name.
SUF_TYPE
String (8)
Street Type.
SUF_DIR
String (4)
Suffix Direction.
4.12.4.4
Location Point Layer Requirements
Address Point Feature
Address Points are an additional address validation data type that allows for a premise match (exact
match) for addressed locations. Address points can be used to define precise building locations which
would provide better geocoding accuracy than interpolating a location using a street centerline feature
as well as to ensure accurate validation where house numbers do not follow standard addressing rules
(i.e. odd/even addresses on the same side of the street etc.).
Note – The street naming conventions for the address points must match the street naming
conventions on the street centerline file and both the city and zip code must match the street centerline
data.
The source feature class containing Address Points must contain the following information (Table 1-6:
Address Points Required Schema Definitions):
Table 1-6: Address Points Required Schema Definitions
Field
Required
Data Type
Description
Page 53
Field
Required
Data Type
Description
Address
Yes
String (100)
The main street address (including house number) of the
location, not including apartment or building numbers if
applicable. The values may exist in the source feature
class as a single field or parsed into two or more separate
fields.
City
Yes
String (150
City Name – Field can represent jurisdictional city or city
code.
Data in this field must match the CITY data in the Street
Centerline and the Common Place feature classes.
Postal City
No*
String (150)
Postal City Name – Required for PremierOne Records.
Zip Code
No*
String (20)
Zip (Postal Code) in any format – Required for
PremierOne Records.
State
No*
String (50)
Name of State, Province, etc. – Required for PremierOne
Records.
The following are additional data fields that are not required but may be used with PremierOne (Table
1-7: Address Points Additional Non-Required Schema Definitions):
Table 1-7: Address Points Additional Non-Required Schema Definitions
Field
Required
Data Type
Description
Subhouse
No
String (18)
Used to store supplemental address information, such as
a unit, space, or suite number (if applicable).
Building
No
String (20)
Used to store building name or number (if applicable).
Subdivision
No
String (150)
A well-known name associated with a small area
(neighborhood, business park, etc.) within a city.
Description
No
String (256)
A description can be helpful in situations where locations
need to be distinguished from each other, such as in a
case where a particular street intersects another street in
two distinct places.
Floor
No
String (20)
Alphanumeric or numeric (supported in v4.4 or higher).
Common Place Point Feature
It is Motorola’s recommendation to use Common Place points for locations commonly referenced by a
name instead of an address (i.e. Government Buildings, Churches, Grocery Stores, Malls, Retail
Stores, etc.). These types of common places have valid addresses but are not often referenced by the
caller using the address. In the chart below the Address field is noted as Required = No however, if
there is a known address it should be included with the record for address validation purposes.
There are common places that do not have a valid address. This would include locations that are
known by a specific name such as mile markers. Other types are locations that are well known in the
community similar to locations like 4 corners, the bronze statue, the Towers, etc, where the address
field would be blank.
Note – The naming conventions for the street names in the address field must match the naming
conventions on the street centerline file, and both the city and zip code must match the street centerline
data.
The source feature class containing Common Places must contain the following information (Table 1-8:
Common Places Required Schema Definitions):
Table 1-8: Common Places Required Schema Definitions
Page 54
Field
Required
Data Type
Description
Place Name
Yes
String (100)
The name used to refer to the location.
Address
No*
String (100)
The main street address (including house number) of the
location, not including apartment or building numbers if
applicable. The values may exist in the source feature
class as a single field or parsed into two or more separate
fields.
*It is recommended that if the location has a valid address
that it be included with the record.
City
Yes
String (150)
The name of the city for which the address point belongs.
Postal City
No*
String (150)
Postal City Name – Required for PremierOne Records.
ZipCode
No*
String (20)
Zip (Postal Code) in any format. – Required for
PremierOne Records.
State
No*
String (50)
Name of State, Province, etc. – Required for PremierOne
Records.
The following are additional data fields that are not required but may be used with PremierOne (Table
1-9: Common Places Non-Required Schema Definitions):
Table 1-9: Common Places Non-Required Schema Definitions
Field
Required
Data Type
Description
Place Type
No
String (25)
A user-defined category for which the location belongs
(i.e. SCHOOL, BUSINESS, POLICE STATION, etc.).
Subhouse
No
String (18)
Used to store supplemental address information, such as
a unit, space, or suite number (if applicable).
Building
No
String (20)
Used to store building name or number (if applicable). If
the location represents a store in a mall, the BUILDING
value could be used to store the name of the mall. This
allows for alternate search methods by Place Name or
Building Name.
Subdivision
No
String (150)
A well-known name associated with a small area
(neighborhood, business park, etc.) within a city.
Description
No
String (256)
A description can be helpful in situations where locations
need to be distinguished from each other, such as in a
case where a particular street intersects another street in
two distinct places.
Place Name
Alias(es)
No
String (100)
One or more fields containing place name aliases can be
defined.
Floor
No
String (20)
Alphanumeric or numeric (supported in v4.4 or higher).
Common Place Alias Table
Common place aliases may reside in the common place feature class or they may be maintained in a
separate table. Maintaining alias names in the common place feature class requires one column per
alias (i.e. a common place with 3 alias names would require 3 alias fields, a common place with 5 alias
names would require 5 alias fields, etc.). There is no limit to the number of aliases per record.
Common place alias names may be maintained in the Common Place Alias table (Table 1-10: Common
Places Alias Table Schema Definitions). The GIS BA provides a blank Common Place Alias table to
MCSO. The schema definition for this table is:
Table 1-10: Common Places Alias Table Schema Definitions
Page 55
Field
Required
Data Type
Description
ALIAS_PLACE_NAME
Yes
String (100)
Alias common place name.
REAL_PLACE_NAME
Yes
String (100)
“Real” common place name.
REAL_PLACE_ADDRESS
No
String (100)
“Real” common place address.
REAL_PLACE_CITY
Yes
String (150)
“Real” common place city identifier.
4.12.4.5
Response Boundaries
Response Boundaries are represented by closed shape polygons in the GIS data. The purpose of
creating boundaries, for use in CAD, is to recommend the streets, intersections, and common places to
the boundaries they fall within. The polygons will represent the smallest named geographic area used
to determine agency and beat-assigned resource responsible for responding to incidents. The
boundary layers are user-defined and may include law beats (for agencies requiring law dispatch), fire
zones (for agencies requiring fire dispatch), EMS zones (for agencies requiring emergency medical
dispatch, etc.).
Agency IDs should match what is defined in CAD Provisioning. It is recommended that Agency ID
should be 2-4 characters.
The source feature class(es) containing Response Boundaries must contain the following information
(Table 1-11: Response Boundaries Schema Definitions):
Table 1-11: Response Boundaries Schema Definitions
Field
Required
Data Type
Description
Name
Yes
String (100)
The name of the boundary(beat), such as “BEAT 100”,
F10, “STATION 5”, or “WEST SUBURBS.”
Agency
Yes
String (25)
The PremierOne Agency ID corresponding to the agency
responsible for responding to incidents created within this
boundary.
Floor
No
String (20)
Alphanumeric or numeric (supported in v4.5 or higher).
4.12.4.6
Reporting District Boundaries
Reporting District Boundaries are features that are represented geometrically by a polygon (area) which
represent the geographic areas used for reporting. Each reporting district boundary feature is specific to
a single agency. Motorola recommends that all reporting district boundaries for a particular agency type
(i.e. Law, Fire, Medical, et cetera) be maintained in a single GIS data source.
The source feature class(es) containing Reporting District Boundaries must contain the following
information (Table 1-12: Reporting District Boundaries Schema Definitions):
Table 1-12: Reporting District Boundaries Schema Definitions
Field
Required
Data Type
Description
Name
Yes
String (50)
The name of the boundary, such as “A100”, NW14, 362,
etc.
Agency
Yes
String (25)
The PremierOne Agency ID that corresponds to the
agency associated with the reporting district.
Floor
No
String (20)
Alphanumeric or numeric (supported in v4.5 or higher).
Page 56
4.12.4.7
Contractor Boundaries
Contractor Boundaries are features represented geometrically by a polygon (area). These features
represent the geographic areas used to define Contractor rotations. Each Contractor boundary feature
is specific to a single agency. Motorola recommends that all Contractor boundaries for a particular
contractor type (i.e. Tow, Taxi, Board Up, etc.) be maintained in a single GIS data source per agency
type. Using Contractor Boundaries is optional.
The source feature class(es) containing Contractor Boundaries must contain the following information
(Table 1-13: Contractor Boundaries Schema Definitions):
Table 1-13: Contractor Boundaries Schema Definitions
Field
Required
Data Type
Description
Name
Yes
String (50)
The name of the boundary, such as “A100”, NW14, 362,
etc.
Agency
Yes
String (25)
The PremierOne Agency ID that corresponds to the
agency associated with the reporting district.
Contractor
Name
Yes
String (10)
The name of the contractor type.
4.12.4.8
Map Book Features
Map Book Page Boundaries are features that are represented geometrically by a polygon (area) which
represent the geographic areas defined in a paper map book. Typically, these polygons are square or
rectangular depending on the pages of the physical map book. Map Book boundaries are not specific to
an agency or agency type.
The source feature class containing Map Book Boundaries may contain the following information (Table
1-14: Map Book Boundaries Schema Definitions):
Table 1-14: Map Book Boundaries Schema Definitions
Field
Required
Data Type
Description
Book Name
Yes
String (25)
The name of the map book.
Page Number
No
String (8)
The specific page number.
Grid Reference
Yes
String (8)
The grid name specific to the page (for example, “A1”).
4.12.4.9
Map Display
The PremierOne map display uses ArcMap documents (*.mxd files). The ArcMap document should
contain all layers used for the PremierOne data upload and may include additional layers not required
for dispatching (i.e. parks, fire hydrants, water, railroads, etc.). The data for the Map Display is not
required for the initial data upload and will be reviewed during the PremierOne Import Tool training
class.
Map Layer Hyperlink Field
A hyperlink field is supported in v4.5 within the Universal Map. Hyperlinks can be stored within any map
layer data source in a column that is named “hyperlink”. For ease of maintenance, it is most convenient
to create a new point geometry layer specific for maintaining hyperlinks.
The source feature class(es) containing Map Layer Hyperlinks must contain the following information
(Table 1-15: Map Layer Hyperlink Schema Definitions):
Page 57
Table 1-15: Map Layer Hyperlink Schema Definitions
Field
Required
Data Type
Description
Hyperlink
No
String
Internet URL, File path (files must exist in listed path on
each workstation).
This field supports one hyperlink per feature.
4.12.4.10 2D Indoor Map Requirements
Universal Map supports 2D indoor map layers to display interior features of buildings such as schools,
shopping centers, hospitals, or other buildings that have GIS indoor floor plans. If the required layers
are added and correctly attributed, it can also be used to search for features by name. For instance, a
building footprint layer can be searched by name and used as a reference point for assisting in locating
a wireless caller.
Each layer/table must be named exactly as listed below and within each layer there are required fields
which also must be named exactly as listed below (case-sensitivity is enforced). The required layers,
tables, and fields must be present and populated for the software to function at a base level (e.g.
utilizing the floor picker in Universal Map to display rooms on different floors, accessing pre plan
attachments, etc.).
Each of the layers referenced below should contain all floors of all buildings in one layer, specific to the
feature type (Polygon, Line, and Point). The software is designed to only display the features on each
floor via the floor picker.
After all layers/tables are built with the required fields and named as required, a Mobile Map Package
(mmpk) or ArcGIS Server Map Service containing these layers/tables is required. The mmpk/map
service must be built from a file geodatabase, personal geodatabase, or shapefile in the latest version
of ArcPro. If using a Mobile Map package, the indoor mapping layers/tables should be included in the
same package as the rest of your base/operational layers.
Indoor Mapping data is only available when zoomed into the map at a scale below 1:1000. Indoor
Mapping layers/tables are not displayed in the Maps panel and cannot be manually displayed/hidden
via the Legend (Table of Contents).
The source feature class(es) containing floor information for buildings is recommended to have the
following information stored with the name buildingPlan (Table 1-16: Building/Floor Plan Schema
Requirements):
Table 1-16: Building/Floor Plan Schema Requirements
Field
Required
Data Type
Description
buildingId
Yes
String (64)
Every individual building must have a unique buildingId
value. This attribute is used to associate items across all
of the Indoor Mapping layers/tables. The GIS
Administrator is responsible for defining and maintaining
building IDs. Any 64-character value can be used (such
as a Parcel number, GUID, etc.).
floorLabel
Yes
String (10)
The value to display in the Floor Picker. It is
recommended that these be short “elevator-style” labels.
Like buildingId, floorLabel is used to associate items
across all of the Indoor Mapping layers/tables.
floorDescription
Yes
String (64)
This value will be displayed when hovering over a floor in
the Floor Picker. This can be a longer description of the
Floor (such as “Underground Parking Level 1”).
Page 58
Field
Required
Data Type
Description
relativeLevel
Yes
Short Integer
This value is used to determine how floors should be
sorted in the Floor Picker. Floors are sorted by the
relativeLevel values from highest (on top) to lowest (on
bottom) in the Floor Picker. For example:
relativeLevel
floorLabel
floorDescription
2
2
2nd
1
G
Ground
-1
B
Basement
-2
P1
Underground
Level
The source polygon feature class(es) outlining building interior and exterior features is recommended to
have the following information stored within a layer named buildingPoly (Table 1-17: Building Polygon
Outline Schema Requirements):
Table 1-17: Building Polygon Outline Schema Requirements
Field
Required
Data Type
Description
buildingId
Yes
String (64)
See description in buildingPlan. There may be several
buildingPoly features for any floor of any building. The
buildingId and floorLabel values of each buildingPoly
feature must exactly match the buildingId and floorLabel
values of a specific row in the buildingPlan table.
floorLabel
Yes
String (10)
See description in buildingPlan. There may be several
buildingPoly features for any floor of any building. The
buildingId and floorLabel values of each buildingPoly
feature must exactly match the buildingId and floorLabel
values of a specific row in the buildingPlan table.
isFootprint
No
String (1)
By default, the map will not display any buildingPoly,
buildingLine, or buildingPoint features until a building is
selected and the Floor Picker is displayed. However, if
there is no other means of displaying the “footprints” of
buildings using another layer, putting a value of “Y” in the
isFootprint attribute will cause the buildingPoly feature to
be displayed prior to the building being selected. This
gives the user an opportunity to see that indoor mapping
data exists at this location so they can click on the
building and display the Floor Picker.
Type
Recommended
Any
This field can have any attribute name and any data type.
This field can be helpful for creating symbology for
buildingPoly features in the map if desired.
Label
Recommended
Any
This field can have any attribute name and any data type.
This field can be helpful for displaying labels for
buildingPoly features in the map if desired.
The source polyline feature class(es) outlining building interior and exterior features is recommended to
have the following information stored with a layer named buildingLine (Table 1-18: Building Polyline
Outline Schema Requirements
Page 59
Table 1-18: Building Polyline Outline Schema Requirements
Field
Required
Data Type
Description
buildingId
Yes
String (64)
See description in buildingPlan. There may be several
buildingPoly features for any floor of any building. The
buildingId and floorLabel values of each buildingPoly
feature must exactly match the buildingId and floorLabel
values of a specific row in the buildingPlan table.
floorLabel
Yes
String (10)
See description in buildingPlan. There may be several
buildingPoly features for any floor of any building. The
buildingId and floorLabel values of each buildingPoly
feature must exactly match the buildingId and floorLabel
values of a specific row in the buildingPlan table.
Type
Recommended
Any
This field can have any attribute name and any data type.
This field can be helpful for creating symbology for
buildingPoly features in the map if desired.
Label
Recommended
Any
This field can have any attribute name and any data type.
This field can be helpful for displaying labels for
buildingPoly features in the map if desired.
The source point feature class(es) representing the locations of features, such as stairs, restrooms,
elevators, etc., within the building is recommended to have the following information stored with the
layer named buildingPoint (Table 19):
Table 1-19: Building Point Features Schema Requirements
Field
Required
Data Type
Description
buildingId
Yes
String (64)
See description in buildingPlan. There may be several
buildingPoly features for any floor of any building. The
buildingId and floorLabel values of each buildingPoly
feature must exactly match the buildingId and floorLabel
values of a specific row in the buildingPlan table.
floorLabel
Yes
String (10)
See description in buildingPlan. There may be several
buildingPoly features for any floor of any building. The
buildingId and floorLabel values of each buildingPoly
feature must exactly match the buildingId and floorLabel
values of a specific row in the buildingPlan table.
extResrce
No
String (1024)
A field containing links to external resource documents
such as images, floorplans, etc. See Universal Map Local
External Resource Link Requirements section.
Type
Recommended
Any
This field can have any attribute name and any data type.
This field can be helpful for creating symbology for
buildingPoly features in the map if desired.
Label
Recommended
Any
This field can have any attribute name and any data type.
This field can be helpful for displaying labels for
buildingPoly features in the map if desired.
4.12.4.11 Universal Map Local External Resource Link Requirements
The following information provides details about the requirements needed for external resource links to
function properly in Universal Map. External resource links need to be included in GIS data layers in the
external resource link (extResrce) field and must match the file path exactly to where the files are
located.
Page 60
External resource links must include the path to the file or URL. Local file and network file paths must
be enclosed in double quotes. Avoid spaces in folder and file names (e.g. Use “MyFile” instead of “My
File”). Following are samples of links that are supported that must be included in the map data layers’
External Resource Links (extResrce) field:
x
URLs (e.g. http://www.vestapublicsafety.com)
x
Local file paths (e.g. “C:\Path\To\File”)
x
Local network file paths (e.g. “\\NetworkShare\Path\To\MyFile”)
The extResrce field may contain 0-Many links. Each link must include a short description (contained
within square brackets) followed by a resource location (contained within angled brackets).
The following are examples of links that are supported and where those could be located. Proper links
must be included in the map data layers’ External Resource Links field:
x
Sample Internet Links
-
[Yahoo!] <http://www.yahoo.com>
-
[Click here to go to Google!] <http://www.google.com>
x
Sample File Links
-
[A Text File] <C:\My Documents\Path\To\File.txt>
x
Sample Multiple Links
-
[Click here to go to Google!] <http://www.google.com> [A Text File] <C:\My
Documents\Path\To\File.txt>
Examples of files that can be linked include:
x
PDF files
x
Text or Microsoft Word files
x
Image / Photo files (e.g. JPEG, PNG)
x
Website URLs
Note that the Windows Operating system will determine which installed application a resource will be
loaded in based on the file’s extension (i.e. “pdf,” “jpg,” “txt”). If no application is registered in Windows
for a specific resource’s file extension, the resource will not load properly and Windows may prompt the
user to specify which installed application should open the resource.
Linked files should be stored on each workstation or a network location accessible by each workstation.
Network rules and infrastructure must be in place for the workstation to reach the locations of the files
or the URLs.
Locations where these can be stored include:
x
Local hard drive
x
Local attached drive
x
Internal network shared drive
x
Internal network web server
x
External internet web server
Page 61
4.13
PremierOne Standard and Custom Modules
4.13.1
Standard Records Modules
The following lists the standard modules available with PremierOne Records. MCSO is entitled to use
all the standard modules. The column indicating which modules MCSO intends to use is for planning
purposes and does not limit MCSO’s use of any module.
PremierOne Records Standard
Modules
MCSO Will Use
PremierOne Records
Standard Modules
MCSO Will Use
Community Feedback
Warrants
Daily Activity Report
X
Case Folders
X
Equipment
X
Case Reports
X
Gas Logs
Juvenile Referrals
X
Neighborhood Watch
X
Officer Narratives
X
Pump Logs
Officer Reports
X
Training
X
Witness Statement
X
Accident
X
Case Management
X
AFIS Fingerprint
X
Civil Papers
Animal Control
Civil Process Folders
Animal Licensing
Record Service Attempt
Booking
X
Master Index
X
Calls for Service
X
Entity
X
Citations
X
Location
X
Confidential Informant
X
People
X
Emergency Call Index
Property
X
Field Interviews
X
Vehicle
X
Firearm Dealers
IBR Documents
X
Firearm Permits
IBR XML Documents
X
Gangs
IBR Submission
X
Gang Members
UCR Documents
Impounds
UCR Submission
Intel
Agency Info
X
Narcotics
Auditing
X
Pawn
X
Archive
X
Pawn Dealers
Duplicate Masters
X
Permits and Licensing
List Management
X
Photo Lineup
X
Numbering
X
Property & Evidence
Orgbuilder
X
P&E Transactions
Security Configuration
Registrants
X
Purge
Subscriptions
User Management
Page 62
Suspicious Activity
Workflow
X
Task & Assignments
X
4.13.2
Custom Records Modules
Motorola will develop the following MCSO-specific modules:
Neighborhood Watch
Tow Module
ATF Form 4 (Class 3 Firearms Application)
Tip Module
Personal & Real Property Seizures & Sales
Memo Module
NamUS
eTrace (ATF)
TraQ Que Tel Modifications to P&E
Patrol Activity Log (PAL) Module
Patrol Activity Log (PAL) Module
DUI.22.12.LicenseePermit.English
-DUI.22.12.LicenseePermit.Spanish
DUI.22.12.LicenseeSuspension.English
-DUI.22.12.LicenseeSuspension.Spanish
DUI.22.12.MVDLEA.English
-DUI.22.12.MVDLEA.Spanish
DV Supplement
Juvenile Miranda Warnings
Juvenile Referrals
MCAO Submittal Checklist
MCAO Submittal Cover
MCSO Non-Traffic Contact
MCSO_FormIV
MCSO_ImpoundRecord_HearingPacket
MCSO_IncidentReport_v2
MCSO_TOUTrainingSummary
MCSO_UAS_Deployment
Naloxone Useage Report
NoticeOfIntentCom
NoticeOfIntentRes
NoticeOfTrespass
PhlebotomyBloodDraw
SAR
Search Log Deputy Copy
SeizureNoticeCom
Stolen Vehicle Affidavit
Vehicle Stop Contact Form
Victim's Rights
4.14
PremierOne Standard and Custom Reports
4.14.1
Standard CAD Reports
This table contains a list of some of the standard reports that are provided with PremierOne CAD.
Report
Input Parameters
Output
CAD Reports
Page 63
Report
Input Parameters
Output
Abandoned Call Summary
Date Range, Disposition, User ID,
Phone Number
Provides the time the abandoned
call record was created, the
trunk/line on which the call was
received, the phone number of the
caller, Disposition, elapsed time of
the call, the call taker’s User ID and
Workstation ID.
Average Response Times by
Incident Type
Date Range, Agency
Provides Average Response times
(At Scene - Incident Create Time) by
Incident Type.
BOLO Messages
Date Range, Sender Agency ID,
Device ID, Sender ID, Group By
(Agency-, Device-, Sender ID)
Provides a record of BOLO
Messages sent: Sender ID, Device
ID, Sent On, Recipient(s), Size,
Status, Attachments. Ability to view
content (Details).
Drill down for the following:
BOLO Message Attachments
N/A
Provides a list of BOLO Message
attachments: Sender ID, Sent On,
Recipients, Attachment Name, and
Size
BOLO Message Detail Report
N/A
Lists all fields of BOLO messages,
organized by Summary, Subject and
Vehicle information
Calls For Service
Date Range (Year)
Lists the E911 Call Count, by month
for year(s).
Drill down for the following:
Calls For Service Daily
N/A
Lists the E911 call count, daily for
month.
Calls For Service Hourly
N/A
Lists the E911 call count, hourly by
day of week.
Calls For Service Weekly
N/A
Lists the E911 call count, by week
for each month.
ChangeAccount Password
Report
N/A
Provides a list of account password
change incidents and whether they
were a success or a failure.
Page 64
Report
Input Parameters
Output
Incident Comments
Agency ID, Max Records, Date
Range, Call sign, Office ID, Address,
Location Name, Comment Text
Lists the comment text for the input
parameters. For comments, a
minimum of three characters are
required. Incident comments are
returned in the order of relevancy.
NOTE: The search for incident
comments is a full text search, and
not a string match; this is the same
search method used by most web
browsers. For example, ban does
not return banana. You can,
however, add specific words to the
SQL database dictionary. Full text
searches include plurals.
Incident Details
N/A
Provides incident details: General
Incident information, Location, and
Caller information, Time Stamps,
Assigned Units, Assigned
Personnel, Comments, and
Changes.
Incident Group By
Date Range, Agency
Provides an incident summary, with
incidents grouped by type: Incident
Type, Incident Number, Incident
Date, Priority, Incident Disposition,
Assigned Units, and Assigned
Officers.
Incident Summary
Date Range, Agency
Provides incident summary
information: Incident #, Create
Date/time, Duration (create to
close), I_type, Priority, Location,
Dispo(s), Assigned Unit(s),
Assigned Officer(s). Links to
Incident Detail Report.
Incidents by Area
Agency ID, area
Shows all incidents occurring in a
specified geographical area. For
example, incidents in area AR1.
Interface Query Summary
User ID, User Agency ID, Device ID,
Group by, Date range
Provides information on who ran
which query, from which device &
when: User Agency ID, Device
Type, Device ID, Query Name,
Executed On Search Parameters
Drill down for the following:
Interface Query Detail
User ID, Device ID, Date Range,
User Agency ID, Group by: Agency,
Device, User ID, Query Type
Provides Query specific details:
User ID, Agency ID, Device ID,
Device. Query Name, Submitted On
Search Parameters, Response(s):
Database, Code, Received On, Hit
Message
Page 65
Report
Input Parameters
Output
Logon and Logoff
Agency ID, User ID, Device ID, Date
Range, Group by: Date, Device,
User ID,
Provides information on who logged
in when and how many times: Date,
User ID, Device ID Unit ID, # of
Logon Attempts, # of Valid Logons,
# of Number Logoffs
Master Incident
Date range, agency ID, Incident
Type, Beat, Current Disposition,
Priority, Call Source, Call sign,
Officer ID, Address, Location Name
Provides incident summary
information for the input criteria. The
following information displays:
Incident Number, Address,
Building/Apt, Location Name, Date,
Report Number (RD), Source Code,
Priority, Incident Type, Primary Unit,
Officer, Area, Beat, And Disposition.
Master Response Statistics
Agency ID, Date Range, Incident
Type, Priority, Grouping
Provides the following information:
Incident Date, Priority, Start to
Create, Start to Dispatch, Dispatch
to Enroute, Enroute to On Scene,
Start to On Scene, Start to Close,
and Create to Close.
Message History
Date Range, Agency ID
Provides the messaging history for
an agency. The following
information is included: Sender ID,
Sender Name, Sent On,
Recipient(s), Device ID, Type, Size,
and Subject.
Messaging Report – Recipient
Sender, Agency ID, Device ID,
Sender ID (All), Date Range
Provides information on messages
received by specific user.
Drill down for the following:
Message details
Provides the specific message
Messaging Report – Sender
Sender Agency ID-, Device ID-,
Sender ID- (All), Date Range (-7 day)
prepopulated. Ability to specify
message size limits. Group by
Sender-, Device-, Agency ID.
Lists who sent messages and who
they sent them to. You can select
sender ID, Device ID (one, many,
all).
Drill down for the following:
Message details
Provides the specific message
Messaging Summary
User Agency ID, User ID (one, many,
all), date range
List message statistics: how many
messages received, sent, deleted, &
message size by users over a time
range
Provisioning Device
Agency ID, Device Type
Lists all devices & device properties
as provisioned in the system.
Grouped by Device Type (Device
Type, Device Name, Make, Serial
Number, Description)
Page 66
Report
Input Parameters
Output
Provisioning Personnel
Agency ID. Provides ability to search
by: User ID, FirstName, LastName.
Lists LastName, FirstName, User ID
of all personnel provisioned in
system. Drill through to Personnel
Details Report (Work, Roles,
Resource Assignments, Personal &
Contacts).)
Provisioning Vehicle
Agency ID, Vehicle Type. Provides
ability to select Vehicle Type (one,
many, all)
Lists all vehicles provisioned in
system by Vehicle Type: Vehicle
Code, Description, License Plate,
Odometer, Equipment, Type
Equipment ID, Capability
Purge Schedule
Agency ID, Database Type, Date
Range
Provides schedule of records to be
purged within date range
Purged Premise Hazard
Agency ID, Date Range
Lists deleted Premise Hazard
Records within date range.
Purged Records History
Agency ID, Database Type, Date
Range
Lists purged records within date
range
ReportingDW Schema
Table or View Name, Field Name,
Show Empty Tables, Only Show
Commonly Used Tables and Views.
Lists RDW tables and views based
on filters selected.
Roles and Privileges
Agency ID, Role
Lists roles and assigned
permissions
Terminal Logon
Agency ID, Device ID, Date Range
Lists failed login attempts by device
type and device ID.
Users and Corresponding Roles
Agency ID, Last, First Name
Lists users and their assigned roles
Mobile Reports
Mobile Query Report - VIN
Agency ID, VIN, Date Range, Search
Text
Lists all queries run on a particular
VIN during a date/ time range.
Mobile Query Report - Person
Agency ID, Person, Date Range,
Search Text
Lists all queries run on a particular
Person during a date/time range.
Mobile Query Report - Plate
Agency ID, Plate, Date Range,
Search Text
Lists all queries run against a
particular Plate during a date/time
range.
Officer Activity
Agency ID, User ID, Date Range
Shows all incident, query, and
messaging activity for a particular
officer during a date/time range.
Unit Officer
Agency ID, Date Range
Provides breakdown of time (and %
time) spent by Units & Officers on
each status (# of Incidents,
Assigned Officers, Unit Status (i.e.
en-route, onscene, Break,
Dispatched etc), Total Time Spent in
Each Status, % Time in Status)
Page 67
4.14.2
Standard Records Reports
This table contains a list of some of the standard reports that are provided with PremierOne Records.
PremierOne Records Standard Reports
Path
Name
/CALEA/CFS Bias Based Profiling
CFS Bias Based Profiling
/CALEA/CFS Bias Based Profiling Detail
CFS Bias Based Profiling Detail
/CALEA/Citations Bias Based Profiling
Citations Bias Based Profiling
/CALEA/Citations Bias Based Profiling Detail
Citations Bias Based Profiling Detail
/CALEA/CR Force Level
CR Force Level
/CALEA/CR Force Level Details
CR Force Level Details
/CALEA/Field Interview Bias Based Profiling
Field Interview Bias Based Profiling
/CALEA/Field Interview Bias Based Profiling Detail
/Case Management/Case Workload by Agency
Field Interview Bias Based Profiling Detail Case Workload
by Agency
/Case Management/Case Workload by Group
Case Workload by Group
/Case Management/Case Workload by Personnel
/Case Management/Case Workload by Personnel
Details
Case Workload by Personnel
Case Workload by Personnel Details
/CFS/CFS by Area
CFS by Area
/CFS/CFS by Area Details
CFS by Area Details
/CFS/CFS by Period
/CFS/CFS by Period Details
CFS by Period
CFS by Period Details
/CFS/CFS by Personnel
CFS by Personnel
/CFS/CFS by Personnel Details
/Citations/Citations by Area
CFS by Personnel Details Citations by Area
/Citations/Citations by Area Details
Citations by Area Details
/Citations/Citations by Period
/Citations/Citations by Period Details
Citations by Period Citations by Period Details
/Citations/Citations by Personnel
Citations by Personnel
/Citations/Citations by Personnel Details
/CR/CR by Area
Citations by Personnel Details CR by Area
/CR/CR by Area Details
CR by Area Details
/CR/CR by Period
CR by Period
/CR/CR by Period Details
CR by Period Details
/CR/CR by Personnel
CR by Personnel
/CR/CR by Personnel Details
CR by Personnel Details
/Field Interview/FI by Period
FI by Period
/Field Interview/FI by Period Details
FI by Period Details
/Field Interview/FI by Personnel
FI by Personnel
/Field Interview/FI by Personnel Details
FI by Personnel Details
/JMS/Arrestees Being Processed
/JMS/Inmate Process Req
Arrestees Being Processed Inmate Process Req
Page 68
PremierOne Records Standard Reports
/Template/LandscapeListTableTemplate
LandscapeListTableTemplate
/UCR/AdultArrest
/UCR/Arson
AdultArrest Arson
/UCR/HateCrime
HateCrime
4.14.3
Custom Reports
Motorola will develop the following MCSO-specific reports/dashboards:
002 - CAD AIMS Vehicle/Unit Search
Drive Exchange Form (Part of AZ Crash)
011 - Monthly DUI Report
DUI.22.12.LicenseePermit.English
-DUI.22.12.LicenseePermit.Spanish
DUI.22.12.LicenseeSuspension.English
-DUI.22.12.LicenseeSuspension.Spanish
DUI.22.12.MVDLEA.English
-DUI.22.12.MVDLEA.Spanish
017 - MCAO Dispatches
DV Supplement
018 - CAD Monthly Report
Incidental Contact Receipt
019 - Patrol Activity Log Unapproved - CAD
Juvenile Affidavit
021 - Patrol Personnel Stat Report
Juvenile Miranda Warnings
023 - Unit History
Juvenile Referrals
024 - Vehicle Usage
MCAO Submittal Checklist
025 - Radio Inventory
MCAO Submittal Cover
026 - Community Policity Total
MCSO Non-Traffic Contact
027 - Personnel Stat Crash Report
MCSO Tow Sheet - Deputy Copy
MCSO Tow Sheet - Tow Driver Copy
MCSO Tow Sheet
029 - Personnel Stat Call for Service Assisting Unit
048 - Personnel Stat Call for Service Primary Unit
MCSO_ConsentToSearch
030 - Personnel Stat Supplemental Detail
031 - Personnel Stat Incident Report Taken
032 - Personnel Stat Overview
033 - Personnel Stat Warrant
034 - Personnel Stat Traffic Stops
MCSO_FormIV
035 - Priority Counts
MCSO_ImpoundRecord_AgreementOfOperation
PAL Reports
036 - PAL Vehicle Mileage
037 - PAL Arrest Detail
038 - PAL Traffic Stop Detail
039 - PAL Supervisor On Scene Detail
040 - PAL IR Generated Detail
041 - PAL Calls for Service Detail
042 - PAL OnView Detail
043 - PAL Accident Detail
MCSO_ImpoundRecord_AuthorizationForRelease
044 - PAL Event History by Event
MCSO_ImpoundRecord_HearingPacket
047- Operation Command of Events by District
MCSO_ImpoundRecord_ImpoundNotice
Page 69
056 - CAD Type Code by Date and District
060 - Operation Command
MCSO_IncidentReport_v2
057 - Personnel Roster
MCSO_TOUTrainingSummary
Vehicle Stop Contact
MCSO_UAS_Deployment
Incidental Contact Form
Naloxone Useage Report
Daily Shift Roster by District and Date
NoticeOfIntentCom
AZ Citation (Officer Copy Form)
NoticeOfIntentRes
AZ Citation (Defendant Copy Form)
NoticeOfTrespass
Vessel Report
PhlebotomyBloodDraw
DUI State Form
PropertyReceipt
AdditionalUnitCameraLog
SAR
CaseClearanceReport
Search Log Deputy Copy
Search Log Deputy Owner
Community Policing Report Form
SeizureNoticeCom
SeizureNoticeRes
DeclarationOfService
Stolen Vehicle Affidavit
DelinquentTaxNotificationCom
DelinquentTaxNotificationRes
Vehicle Stop Contact Form
Victim's Rights
4.15
Purchase Option
The following system components are presented for the Customer’s consideration as additional purchase
options.
4.15.1
Option 1 – ActiveEye Managed Detection and Response for PremierOne
4.15.1.1
Overview
Identifying and mitigating cyber threats requires continuous monitoring and technical capabilities to
distinguish real threats from millions of alerts, as well as the expertise to quickly evaluate and
remediate them if needed. With ActiveEyeSM Managed Detection and Response (MDR) for
PremierOne, Motorola Solutions will provide your agency or command center personnel access to the
ActiveEye Security Platform, along with 24/7 support from specialized cybersecurity experts who will
monitor your mission-critical computer-aided dispatch (CAD) clients, servers and workstations for
indicators of threats and remediate them if needed.
The ActiveEye MDR solution can help secure your agency’s Motorola Solutions and third-party
connected networks, applications, and devices through a combination of ActiveEye technology,
endpoint detection, and the expertise of Motorola Solutions’ cybersecurity analysts in our Security
Operations Center (SOC). As we implement MDR, we will collaborate with your command center and
agency personnel to provision the solution to your needs.
Page 70
4.15.1.2
ActiveEye Security Management Platform
The ActiveEye Security Platform collects, manages, and analyzes security events. Built-in analytics
examine multiple real-time threat intelligence feeds, reference past events, and follow playbooks to
automate most actions. Analytics also prioritize events to quickly identify those that require remediation.
As a Security Orchestration, Automation and Response (SOAR) platform, ActiveEye speeds up
remediation, using predefined or custom playbooks to automatically investigate and respond to threats.
ActiveEye’s automatic investigation capabilities include looking up threat intelligence, querying past
data, adding recommended action notes to cases, and bringing event details to the main investigation
screen. Its automated response capabilities include changing alert priorities, closing alerts, blocklisting
files, removing files from systems, or isolating hosts from the network.
This automated approach to threat identification and remediation eliminates more than 95 percent of
false positives, allowing your team or our SOC analysts to shift their focus to more complex
investigation and response tasks.
4.15.1.3
ActiveEye Managed Security Portal
The ActiveEye Security Portal, a cloud-based web application, enables improved coordination of
cybersecurity efforts between your agency and Motorola Solutions. From this central platform, your
agency’s personnel will be able to view threat insights, event investigations, security reports, threat
advisories, and the status of cases.
Figure 1-6: ActiveEye Interface
Dashboard
The ActiveEye dashboard provides a summary of key information It includes a snapshot of open alerts,
alert categories, key performance indicators (KPI), open cases, and recent threat advisories. Users can
also see more in-depth information, such as the number of security cases, alert details, alert trends,
reports, and group communications.
Page 71
Security Cases
When a threat is identified, the SOC will create a security case. Through the ActiveEye Portal, your
agency’s personnel will be able to view details of current or past cases, create new cases, or respond
to ongoing cases.
Alert Details and Trends
Alerts can be evidence of a past, active, or developing threat. ActiveEye records relevant data for each
alert, enabling users to quickly view its trigger, the systems it impacts, and any actions taken to address
the alert.
ActiveEye also provides tools for reviewing groups of alerts based on key attributes or time periods.
Attribute filters enable users to toggle which alert groups are shown in ActiveEye, helping users spot
trends or threat activity. Users can also compare alert logs for specific time periods to determine if
specific trends are associated with a threat or are false positives.
Investigations and Reporting
ActiveEye includes robust ad hoc reporting capabilities that provide important information about active
and historical threats. Users can share information outside of ActiveEye by downloading reports in .csv
or .json format.
In addition to ad hoc reporting, ActiveEye can provide a daily email summary and monthly report. Daily
email summaries can include alert counts, security cases opened or closed, saved queries that have
new data, and detailed endpoint security statistics. If needed, ActiveEye can send one or more
summary emails with different content for different groups. Monthly reports are available as a PDF
download.
Security Advisories
ActiveEye also enables the SOC to share Security Advisories on active threats. These advisories guide
security teams on how to take actions against threats and where to get more information.
Information Sharing
ActiveEye includes several other functions for sharing information. Automatic security alerts notify pre-
defined contacts of incidents, based on incident priority. Other information-sharing functions include:
x
SOC Bulletins - Instructions from your agency’s personnel or the SOC that analysts reference
when creating security cases. These can communicate short-term situations where a security
case may not be required, such as during testing or maintenance windows.
x
Customer Notebook - The SOC will use the Customer Notebook to document your agency’s
environment and any specific network implementation details assisting the SOC investigation of
security cases.
x
Contact Procedures - Escalation procedures and instructions on who to contact if an incident
occurs. Contact procedures include instructions and procedures for specific security incident
levels. The SOC and your agency’s personnel will jointly manage contact procedures.
User Access
User access settings make it simple to add, update, and remove access to ActiveEye. Users may be
given administrative access, allowing them to perform administrative tasks such as setting up new
service connectors, resetting passwords, and setting up multi-factor authentication for other users.
Page 72
4.15.1.4
Service Modules
One or more service modules can be integrated through the ActiveEye platform. These modules
provide more information for ActiveEye to correlate, offering a clearer vision of events on your agency’s
network. In addition, modules enable security teams and analysts to more easily access and compare
data from disparate systems.
4.15.1.5
Endpoint Detection and Response
If an attacker attempts to breach your existing security controls, it is critical to respond quickly.
Integrating Endpoint Detection and Response (EDR) tools with the ActiveEye platform enables security
analysts to respond to attacks and view threat intelligence in a single interface. Through the ActiveEye
platform, analysts can isolate hosts, block files, allow files, and remove files.
ActiveEye MDR includes ongoing monitoring by Motorola Solutions SOC cybersecurity analysts to look
for potential cybersecurity threats to connected networks, applications, and devices on a 24/7 basis.
The SOC team operates from secure, redundant locations in the United States, and can securely
operate at remote locations if necessary. Team members complete regular training on customer data
management and privacy to protect sensitive customer data. Based on their broad security experience,
the SOC’s analysts will recommend security device configurations and implement playbooks to
increase focus on the most critical threats.
If a threat investigation requires input from your agency’s security team, the SOC will create a security
case and follow defined escalation procedures for each priority level. ActiveEye will enable your
agency’s personnel to view security cases and event investigation history.
In the event of a potential incident, the SOC will use data available in ActiveEye and access your
agency’s system to determine the extent of malicious activity. If needed, the SOC will add more
detection policies to your agency’s service modules.
4.15.2
Option 2 - NIST Cyber Security Framework (CSF) Security Program
Risk Assessment
The NIST Cyber Security Framework (CSF) Security Program Risk Assessment is a professional
service to evaluate an existing information security program against five core functions: identify, protect,
detect, respond, and recover. The NIST CSF Security Program Risk Assessment will support the
investigation of already established policies, standards, procedures, and technologies implemented by
the Customer and align these practices with the NIST CSF functions as well as the Department of
Homeland Security’s (DHS) Cross-Sector Cybersecurity Performance Goals (CPGs). The outcome of
the assessment will allow Motorola to provide the Customer with an understanding of its state of
compliance, provide insight into gaps that have been identified in the security program with respect to
the NIST CSF functions, DHS CPGs, and provide remediation recommendations for the organization to
improve upon.
Objectives
Customer is seeking assistance to evaluate if their security program meets prudent security guidelines.
This security review will provide Customer with visibility into how your existing IT Security standards
stand up against the NIST CSF Review to:
x
Identify potential gaps
x
Define the risk associated with the gaps
x
Offer specific advice on how to remediate the gaps
Page 73
4.15.2.1
System Security Plan Development
A System Security Plan (SSP) is a formal document that provides a comprehensive and detailed
overview of the security requirements for an information system, or for an information security program.
The SSP describes the security controls in place, or those planned for meeting the requirements
outlined in a security framework such as NIST 800-53r5 or NIST 800-171.
The Motorola cybersecurity team is comprised of accredited individuals with years of experience in the
public and private sectors implementing, auditing, and certifying systems in a variety of contexts and
risk levels.
4.15.2.2
Business Continuity and Disaster Recovery (BC/DR) Planning
Motorola will develop, in coordination with Customer’s security and privacy team, a Business Continuity
Plan (BCP). A BCP lays out the steps and procedures that should be taken before, during, and after a
disaster; this will ensure Customer reaches maximum functionality during an event and can return
operations back to normal in the shortest time possible following an event. Developing a BCP will allow
Customer to identify and address resiliency synchronization between business functions and
processes, departments, systems and IT infrastructure.
Page 74
Section 5
Exhibit B-1: Interface Functional
Design Documents
Due to the quantity and size of the Interface Functional Design Documents, they are posted on the
Maricopa County’s shared site and incorporated herein by reference.
Page 75
Section 6
Exhibit C: Statement of Work
6.1
Introduction
In accordance with the terms and conditions of the Agreement, this Statement of Work (SOW) defines
the principal activities and responsibilities of all parties for the delivery of the Motorola Solutions, Inc.
(Motorola) system as presented in this offer to the Maricopa County Sheriff’s Office (hereinafter referred
to as the “MCSO”). When assigning responsibilities, the phrase “Motorola” includes our subcontractors
and third-party partners.
Deviations and changes to this SOW are subject to mutual agreement between Motorola and MCSO
and will be addressed in accordance with the change provisions of the Agreement. MCSO
acknowledges that such deviations and changes to this SOW may incur additional costs. Said
additional costs will be disclosed and mutually agreed upon between Motorola and MCSO pursuant to
the change provisions of the Agreement.
Unless specifically stated, Motorola work will be performed remotely. MCSO will provide Motorola
resources with network access via a login to MCSO portal for SecureLink to enable Motorola to fulfil its
delivery obligations.
Motorola and MCSO will work to complete their respective responsibilities in accordance with the
mutually agreed upon Project Schedule. Any changes to the Project Schedule will be mutually agreed
upon via the change provision of the Agreement.
The number and type of software or subscription licenses, products, or services provided by Motorola
or its subcontractors are specifically listed in the Agreement and any reference within this document, as
well as subcontractors’ SOWs (if applicable), does not imply or convey a software or subscription
license or service that is not explicitly listed in the Agreement.
6.2
Award, Administration, and Project Initiation
Project Initiation and Planning will begin following execution of the Agreement between Motorola and
MCSO.
Following the conclusion of the Project Planning Session, Motorola’s Project Managers (PMs) will
conduct weekly status meetings. Three one-hour meetings per month will be conducted remotely and
the Motorola PM will meet with MCSO’s PM once a month on-site for the purpose of baselining
progress of current activities and the planning of future activities. Following the conclusion of the
Contract Design Review, the Motorola PM will prepare and submit weekly action reports and monthly
status reports to MCSO PM. Monthly Status Reports provide a summary of the activities completed in
the month, activities planned for the following month, project progress against the project schedule,
items of concern requiring attention, as well as potential project risks and agreed upon mitigation
actions.
Motorola utilizes Google Meet as its teleconference tool but recognizes MCSO uses Microsoft Teams
for teleconferencing. Motorola agrees to the use of Microsoft Teams and will work with MCSO team to
ensure logistical issues with scheduling Teams meetings are addressed.
Page 76
6.3
CJIS Information
For all employees having unescorted physical or logical access to unencrypted NCIC/III or CHRI data
or who manage, operate, develop, access, and maintain criminal justice information systems containing
unencrypted NCIC/III or CHRI data, Motorola, upon request, will provide state of residency verification
and will obtain Applicant Fingerprint Cards and submit them to MCSO for conducting a criminal
background investigation, unless the Agency requires a different procedure, prior to such employee
accessing the information system or arriving on customer premises if unescorted access is required. If
MCSO requires current Fingerprint Cards, Motorola employees will provide them.
6.4
Project Terms
The following project management terms are used in this document. Since these terms may be used
differently in other settings, these definitions are provided for clarity.
Project Schedule means the schedule providing dates and timeframes for completion of tasks and
deliverables during the course of the project. The Project Schedule is subject to change at the mutual
agreement of Motorola and MCSO.
Project Management Plan is composed of the Communications Management Plan, Risk Management
Plan, and Change Management Plan and provides the criteria for managing those tasks within the
project. Additional elements of the Project Management Plan include the project governance, i.e.
escalation procedures, etc.
6.5
Completion Criteria
Motorola Integration Services are considered complete upon Motorola performing the tasks listed as
Motorola Responsibilities for each activity. MCSO task completion will occur per the project schedule
enabling Motorola to complete its tasks without delay; Motorola is not responsible for any project delays
due to incomplete MCSO tasks nor is MCSO responsible for project delays due to incomplete Motorola
tasks
Where a deliverable includes multiple complex elements or is associated with a payment milestone, the
Motorola and County PMs will work together to develop a description of the elements (including but not
limited to acceptance criteria) of the deliverable prior to completing the tasks associated with the
deliverable to ensure expectations of the deliverable are clear and unambiguous.
MCSO will provide Motorola written notification (including email) that it does not accept the completion
of Motorola responsibilities or rejects a Motorola service deliverable within five business days of
completion or receipt of a deliverable. Such notification will identify the deficiency in the service or
deliverable. Motorola will review the rejection and, if mutually acknowledged, discuss and agree to the
corrective action within five (5) days and establish a due date and agree to the corrective action and
due date.
The Service Completion will be acknowledged in accordance with the terms and conditions of the
Agreement and the Service Completion Date will be memorialized by Motorola and MCSO. Software
System Completion will be in accordance with the terms and conditions of the Contract Agreement
unless otherwise stated in this Statement of Work.
Page 77
6.6
Project Roles and Responsibilities Overview
6.6.1
Motorola Project Roles and Responsibilities
A Motorola team, made up of specialized personnel, will be assigned to the project under the direction
of the Motorola PM. Team members will be multi-disciplinary and may fill more than one role. Team
members will be engaged in different phases of the project as necessary.
In order to maximize efficiencies, Motorola’s project team will provide services remotely via
teleconference, web-conference, or other remote methods in fulfilling its commitments, unless
otherwise stated as on-site as outlined in this Statement of Work.
The personnel role descriptions noted below provide an overview of typical project team members. One
or more resources of the same type may be engaged as needed throughout the project. There may be
other personnel engaged in the project under the direction of the PM.
Motorola’s project management approach has been developed and refined based on lessons learned in
the execution of hundreds of system implementations and is reliant upon collaboration and a working
partnership with our customers to enable success. Motorola will provide the expert knowledge around
our solutions and industry best practices enabling our resources to guide MCSO actions throughout the
delivery process. Our guidance coupled with your knowledge of your business, processes, resources,
and operating environment make a successful partnership.
Our experience has shown that customers who assume ownership of the system early on and take an
active role in delivery and education activities realize quicker user adoption and higher levels of
success with system operation.
Motorola’s Program Manager
A Program Manager will be assigned to monitor the project workstreams, provide assistance in issue
resolution, when/if required, and otherwise support the overall implementation.
Motorola’s Project Manager
Two Motorola PMs will be assigned who will be allocated at approximately 60% each for the project
duration. They are principal business representatives and points of contact for the organization, one for
CAD, one for Records. The PMs’ responsibilities include the following:
x
Manage the Motorola responsibilities related to the delivery of the project.
x
Implement the project in accordance with the methodology described in the Project
Management Plan.
x
Maintain the project schedule and manage the assigned Motorola personnel and applicable
subcontractors/supplier resources.
x
Manage the Change Order process per the Agreement.
x
Maintain project communications with MCSO.
x
Identify and manage project risks.
x
Collaborative coordination of MCSO resources to minimize and avoid project delays.
x
Measure, evaluate, and report the project status against the Project Schedule.
x
Conduct remote status meetings on mutually agreed dates to discuss project status.
Page 78
x
Prepare and submit weekly action reports and a monthly status report that identifies the
activities of the previous month, as well as activities planned for the current month, including an
updated Project Schedule and action item log.
x
Provide timely responses to issues related to project progress.
x
Ensure Motorola staff follow the background check process in a timely manner as outlined by
MCSO in order to gain both remote and on-site access to equipment.
Project Coordinator
A Project Coordinator will work with the Motorola Program and Project Managers and is responsible for
the following:
x
Facilitating and participating in status meetings
x
Record and distribute meeting minutes and action items
x
Document management (including SharePoint Administration)
x
Project schedule maintenance,
x
Managing the efforts of third party providers,
x
Maintenance of the elements of the Communications Plan and
x
Further assisting the Motorola program manager as required with customer communications,
resource scheduling, action item tracking.
Application Specialist
The Motorola Application Specialist (AS) will work with MCSO project team on system provisioning. The
Application Specialist’s responsibilities include the following:
x
Provide provisioning education and guidance to MCSO to set up, operate, and maintain the
system.
x
Provide product education as defined by this SOW and described in the Training Plan.
Solution Specialist
The Solution Specialist is responsible for influencing and driving optimal outcomes of the software
solution. Specific responsibilities include the following:
x
Consult with MCSO on objectives and guiding best practice adoption.
x
Drive early engagement of key project stakeholders to understand end-to-end workflows
affecting outcomes.
x
Provide expertise that addresses MCSO’s unique needs, objectives, and requirements.
Reporting Specialist
The Motorola Reporting Specialist specializes in data analysis, report generation, and reporting
outcomes. The Reporting Specialist’s responsibilities include the following:
x
Provide guidance on reporting requirements and decisions for MCSO specific reports and/or
dashboards.
x
Provide reporting education and guidance to MCSO to set up, operate, and maintain the
reporting system.
x
Provide product education as defined by this SOW and described in the Exhibit D - Training
Plan.
Page 79
GIS Specialist
The Motorola GIS Specialist specializes in geographical information technology. Responsibilities of the
Motorola GIS Specialist include the following:
x
Perform the GIS analysis on MCSO supplied GIS source data.
x
Provide the results of the GIS analysis based on the requirements of the Motorola GIS Data
Requirements document to include:
x
Geocoding Data.
x
Centerlines to support Routing.
x
Response Area Polygons.
x
Offer consultation services for the conversion of MCSO GIS source data for Motorola use.
x
Provide instruction on the use of GIS as it pertains to the Motorola system.
Solution Architect
The Solution Architect (SA) is responsible for the delivery of the technical and equipment elements of
the solution. Specific responsibilities include the following:
x
Confirmation that the delivered technical elements meet contracted requirements.
x
Delivery of interfaces and integrations between Motorola products.
x
Engagement throughout the duration of the delivery.
Scheduler
A Motorola Scheduler is responsible for developing and maintaining the overall project schedule,
ensuring that all activities are properly sequenced and resources are allocated efficiently. They
collaborate with various stakeholders to gather project data, analyze dependencies, and identify critical
paths to ensure timely project completion. The Scheduler plays a crucial role in monitoring project
progress, tracking deviations, and implementing necessary adjustments to keep the project on track.
Customer Success Onboarding Advocate
A Customer Success Advocate will be assigned to MCSO. As MCSO’s trusted advisor, the Customer
Success Advocate’s responsibilities include:
x
Collaborate with agency personnel and key stakeholders to document desired customer
outcomes for the system.
x
Collaborate with Motorola Project Team to schedule deployments and transitions in alignment
with MCSO’s desired outcomes.
x
Establish Customer Success Advocate as MCSO’s ongoing trusted advisor for Command
Center Software.
x
Familiarize the key MCSO stakeholders with Motorola processes (support, feature
enhancements, etc.).
x
Engage with MCSO on industry trends and Motorola evolutions.
Remote Application Administrators
Two Remote Application Administrators (AA) will support PremierOne CAD/Mobile and Records
applications (excluding infrastructure) following Go Live. They will also be on-site for Go Live as
described in Section 6.23.1.2. Following Go Live, the fully trained resources augment MCSO’s existing
team as it relates to troubleshooting and initiating support tickets on software issues, supporting user
Page 80
training, maintaining provisioning, introducing software upgrades, SSRS reporting, Records modules
and workflows.
Organizational Change Management (OCM) Leader
Motorola will engage a professional OCM leader to provide training, guidance and direction to MCSO’s
team on methodologies to introduce and encourage members of MCSO to adapt to the changes
introduced by new technology, such as the PremierOne CAD and Records solution. The OCM leader
assesses MCSO’s readiness for change and develops a systematic approach, body of knowledge,
training tools and materials to facilitate a successful transition to the new systems.
Customer Support Services Team
The Customer Support Services team will provide ongoing support following commencement of
beneficial use of MCSO’s System(s).
6.6.2
Customer Core Team, Project Roles and Responsibilities
The success of the project is dependent on early assignment of a Customer Core Team. Motorola has
defined the following key resources that are critical to this project and must participate in all the
activities further defined in this SOW. During the Project Planning phase, MCSO will be required to
deliver names and contact information for the below listed roles that will make up MCSO’s Core Team.
In many cases, MCSO will provide project roles that correspond with Motorola’s project roles. It is
critical that these resources are empowered to make decisions based on MCSO’s operational and
administration needs. MCSO's Core Team will be engaged from project initiation through beneficial use
of the system. Their continued involvement in the project and use of the system will convey the required
knowledge to maintain the system post-completion of the project and drive change and user adoption.
In some cases, one person may fill multiple project roles. MCSO’s Core Team must be committed to
participate in activities for a successful implementation. In the event that MCSO is unable to provide the
roles identified in this section, Motorola may be able to supplement MCSO resources at an additional
price.
The estimated level of effort expected for MCSO resources is reflected in the Implementation Staffing
Plan.
MCSO Project Manager
The PM will act as the primary MCSO point of contact for the duration of the project. The PM is
responsible for management of any third-party vendors that are MCSO’s subcontractors. In the event
the project involves multiple agencies, Motorola will work exclusively with a single MCSO assigned PM
(the primary PM). The PM’s responsibilities include the following:
x
Work with the Motorola PMs to manage the project in accordance with the Project Management
Plan.
x
Communicate and coordinate with other project participants.
x
Manage MCSO project team, including timely facilitation of efforts, tasks, and activities.
x
Maintain project communications with the Motorola PM.
x
Identify the efforts required of MCSO staff to meet the task requirements and milestones in this
SOW and Project Schedule.
x
Consolidate all project-related questions and queries from MCSO staff to present to the
Motorola PM.
x
Review the Project Schedule with the Motorola PM and finalize the detailed tasks, task dates,
and responsibilities.
Page 81
x
Measure and evaluate progress against the Project Schedule.
x
Monitor the project to ensure resources are available as scheduled.
x
Attend status meetings.
x
Provide timely responses to issues related to project progress.
x
Liaise and coordinate with other agencies, MCSO vendors, contractors, and common carriers.
x
Review and administer change control procedures, hardware and software certification, and all
related project tasks required to maintain the Project Schedule.
x
Ensure MCSO vendors’ adherence to overall Project Schedule and Project Plan.
x
Assign one or more personnel who will work with Motorola staff as needed for the duration of
the project, including at least one Application Administrator for PremierOne and one or more
representative(s) from the IT department.
x
Identify the resource with authority to formally acknowledge and approve Change Orders,
approval letter(s), and milestone recognition certificates, as well as approve and release
payments in a timely manner.
x
Provide building access to Motorola personnel to all MCSO facilities where system equipment is
to be installed during the project. Temporary identification cards are to be issued to Motorola
personnel, if required for access to facilities.
x
Ensure remote network connectivity and access for Motorola resources.
x
Assume responsibility for all fees for licenses and inspections related to the facilities in which
equipment will be installed and any delays associated with inspections due to required permits,
if necessary.
x
Ensure a safe work environment for Motorola personnel.
x
Provide signatures of Motorola-provided milestone certifications and Change Orders within five
business days of receipt.
System Administrator
The System Administrator manages the technical efforts and ongoing tasks and activities of their
system, as defined in the Customer Support Plan (CSP). Motorola recommends this role be familiar
with the following elements:
x
Windows Administration.
x
SQL Server.
x
SQL Server Reporting Services (SSRS).
x
System Center Operations Manager (SCOM).
Application Administrators
The Application Administrators manage MCSO owned provisioning maintenance and MCSO code
tables required to enable and maintain system operation. The Application Administrators’ involvement
will start prior to the Project Kick-off stage of the project. They will review and provide documentation
requested in the Team Project Sync (TPS) packet, attend education as outlined in the Training Plan
(e.g. provisioning, train-the-trainer), and remain engaged throughout the project. MCSO may elect to
have multiple Application Administrators for CAD and Records. The Application Administrator’s
responsibilities include the following:
x
Participate in overall delivery and training activities to understand the software, interfaces, and
functionality of the system.
Page 82
x
Work closely with the SMEs during the Business Process Review (BPR), provisioning process,
validation, and training.
x
Authorize global provisioning choices and decisions and be the point(s) of contact for reporting
and verifying problems and maintaining provisioning.
x
Obtain inputs from other user agency stakeholders related to business processes and
provisioning.
x
Facilitate escalation to and communication with Motorola Application Specialists during Go Live
activities.
GIS Administrator
The GIS Administrator is responsible for the development and maintenance of all the GIS data used in
the Motorola system. The GIS Administrator must have a working knowledge of Esri software including
ArcDesktop and ArcPro. Proficiency with model builder, toolbox tools, Network Analyst, and general
database structures is key to the GIS Administrator’s ability to manage the GIS needs of the Motorola
system. Duties for this resource include the following: provide data in the correct schema; develop,
maintain and update GIS data; support the GIS elements used in Motorola software; and keep in
regular communication with the other administrative resources. The GIS Administrator role and
associated responsibilities will be required for the duration of the Motorola system use.
Subject Matter Experts
The Subject Matter Experts (SME or Super Users) are the core group of users involved with the BPR
and analysis, training, and the provisioning process, including making global provisioning choices and
decisions. These members will be experienced users in the working area(s) they represent (dispatch,
patrol, etc.), possess a working knowledge of the day-to-day operation, understand agency protocols as
well as agency field use procedures, have the ability to gather the data needed from the legacy system,
and will be empowered to make decisions related to provisioning elements, workflows, and screen
layouts.
IT Personnel
IT personnel provide required information related to LAN, WAN, wireless networks, server, and client
infrastructure. They must also be familiar with connectivity to internal, external, and third-party systems
to which the Motorola system will interface.
Training Representative
Training representatives will be the point of contact for the Motorola Application Specialist when policy
and procedural questions arise. They will act as course facilitators and are MCSO’s educational
monitors. They will be responsible for the development of agency specific training material aside from
the Motorola provided documentation. This role will serve as the first line of support during Go Live for
MCSO’s end users.
Transformation Leads
Ideal candidates for the Transformation Leads include a varied selection of senior operational decision
makers, such as dispatch supervisors, senior call takers/dispatchers, and field training officers. As
participants on the change management team, their efforts will prove invaluable to project success.
Agency Trainers
Agency Trainers MCSO resources that will participate in Train the Trainer courses and work with
Motorola following Train the Trainer courses to develop/refine training curriculum that will be used for
end-user training. They may proctor end-user training courses for consistently, quality assurance, etc.
Page 83
User Agency Stakeholders
User Agency Stakeholders, if the system is deployed in a multi-agency environment, are those
resources representing agencies outside of MCSO’s agency. These resources will provide provisioning
inputs to MCSO Core Team if operations for these agencies differ from that of MCSO. MCSO will
manage User Agency Stakeholder involvement, as needed, to fulfill MCSO responsibilities.
6.6.3
General MCSO Responsibilities
In addition to MCSO Responsibilities stated elsewhere in this SOW, MCSO is responsible for:
x
All MCSO provided equipment, including hardware and third-party software, necessary for
delivery of the System not specifically listed as a Motorola deliverable. This will include end user
workstations, network equipment, telephone, or TDD equipment and the like.
x
Configuration, maintenance, testing, and supporting the third-party systems MCSO operates
that will be interfaced to as part of this project. For those third-party systems, MCSO is
responsible for establishing Application Programming Interface(s) (API) and providing
documentation that details the integration process for the level of interface integration defined
by Motorola.
x
Initiate, coordinate, and facilitate communication between Motorola and MCSO’s third-party
vendors as required to enable Motorola to perform its duties.
x
All necessary third-party upgrades of their existing system(s) as may be required to support the
solution. Motorola does not include any services, support, or pricing to support MCSO third-
party upgrades in this proposal.
x
Mitigate the impact to third-party systems, to include interfaces that result from MCSO
upgrading a third-party system. Motorola strongly recommends working with Motorola to
understand the impact of such upgrades prior to taking any upgrade action.
x
Motorola will have no responsibility for the performance and/or delays caused by other
contractors or vendors engaged by MCSO for this project, even if Motorola has recommended
such contractors.
x
Active participation of Customer Core Team in project delivery meetings and working sessions
during the course of the project. Customer Core Team will possess requisite knowledge of
MCSO operations and legacy system(s) and possess skills and abilities to operate and manage
the system.
x
The provisioning of MCSO code tables and GIS data. This information must be provided in a
timely manner in accordance with the Project Schedule.
x
Electronic versions of any documentation associated with the business processes identified.
x
Providing a facility with the required computer and audio-visual equipment for training and work
sessions, as defined in the Training Plan.
x
Ability to participate in remote project meeting sessions using a Microsoft platform, MCSO
provided alternate remote conferencing solution.
6.6.3.1
MCSO Implementation Staffing Plan
The below table represents the approximate MCSO resource allocation for the primary tasks in the
SOW.
Page 84
Position
Responsibilities
Implementation tasks in
which roles will be involved
(refer to the Statement of
Work for description of
MCSO responsibilities).
Estimated effort associated
with activity
Project Manager
(PM)
The PM is the primary
business representative
and point of contact for
the Motorola PM and is
responsible for
coordination of
Customer resources and
activities. The PM shall
schedule all Customer
resources required to
execute tasks, initiate
review meetings,
provide status
information to the
Motorola PM, and
oversee the execution of
this plan.
The PM is responsible
for formally
acknowledging and
approving Change
Orders, approval
letter(s), milestone
recognition certificates
and payments, or
identifying the resource
with authority to do so.
ƒ Project management is an
ongoing activity for the
duration of the project and is
considered a part of every
project task. Specifically, the
PM participates in and/or
acknowledges completion
of:
ƒ Project Planning
ƒ Business Process Re-
engineering
ƒ Hardware Installation
ƒ Product Validation (Testing)
ƒ Training Completion
ƒ Completion of System
Training
ƒ Go-Live
PM(s) should expect to be
engaged 75% of the overall
project duration with 100%
engagement at times.
Transformation
Lead
The Transformation
Lead must be able to
holistically represent
your organization and
be able to work cross
functionally between
Motorola, your
organization, and all
stakeholders involved in
the delivery of your new
system. They must be
empowered to
acknowledge the
resource and time
commitments required
of your organization and
authorize Motorola to
proceed with scheduling
the Project Kickoff
event.
ƒ Project Planning
ƒ Business Process Review
and
ƒ Provisioning
ƒ Application Training
ƒ Organizational Change
Management
100% when Motorola is on-
site for the referenced
activities. 50%-75% for the
duration of those activities.
Page 85
Position
Responsibilities
Implementation tasks in
which roles will be involved
(refer to the Statement of
Work for description of
MCSO responsibilities).
Estimated effort associated
with activity
Application
Administrator(s)
The Application
Administrator(s) manage
the provisioning
maintenance and code
tables required to
enable and maintain
system operation.
ƒ Project Planning Session
ƒ Project Kickoff Meeting
ƒ GIS Discovery Session
ƒ Contract Design Review
ƒ Business Process Review
and Provisioning
ƒ Product Validation
ƒ CAD/Mobile Train the
Trainer
ƒ Go-Live
100% allocation to referenced
activities
GIS Administrator
The GIS Administrator is
responsible for the
development and
maintenance of all the
GIS data used in the
Motorola system. This
includes providing data
in the correct schema;
developing, maintaining
and updating GIS data;
supporting the GIS
elements used in
Motorola Solutions
software; keeping in
regular communication
with the other
administrative
resources.
ƒ GIS Discovery
Teleconference
ƒ GIS Services
ƒ GIS Administrator Workshop
and Review
100% allocation to referenced
activities, then 50% or more
through project duration as
GIS updates are required for
CAD.
System
Administrator
Participate in installation
activities including
hardware/software and
interfaces. Post-live,
support Motorola on-site
System Administrator.
Perform analytics, report
generation, reporting
and verifying problems
ƒ Site Survey/Network
Analysis
ƒ Interface Installation
ƒ Post-live
ƒ 100%
ƒ 100%
ƒ 50%
ƒ Approx. 12hours per week
for standard system-level
monitoring/administration.
Subject Matter
Experts
The core group of users
supporting the
Application
Administrator; involved
with the Business
Process Review (BPR)
and the provisioning
process, including
department-specific
provisioning choices and
decisions; training.
ƒ Business Process Review
and Provisioning
ƒ Product Validation
ƒ Train the Trainer
ƒ End-User Training
ƒ Go-Live
ƒ Organizational Change
Management
ƒ Allocated as required to
perform assigned tasks
associated with the
referenced activities.
Page 86
Position
Responsibilities
Implementation tasks in
which roles will be involved
(refer to the Statement of
Work for description of
MCSO responsibilities).
Estimated effort associated
with activity
IT Personnel
These resources will
provide required
information related to
LAN, WAN, wireless
networks, server, and
client infrastructure as
well as information on
third party/external
systems to which
PremierOne will
interface.
Project Kickoff
Interface Planning
Interface Design Review
Contract Design Review
Site Survey and IP Network
Analysis
Hardware and Software On-
Site Installation
Interfaces and Installation
Interface Validation
CAD Go Live
ƒ 100%
ƒ 100%
ƒ 100%
ƒ 100%
ƒ 100%
ƒ 100%
ƒ 100%
ƒ 100%
ƒ 50%
Training
Representative(s)
Training representatives
will be the point of
contact for the Motorola
Application Specialist
when policy and
procedural questions
arise during training
delivery. They will act as
course facilitators and
are MCSO’s educational
monitors.
ƒ CAD Train the Trainer
ƒ Mobile Train the Trainer
ƒ End-User Training
ƒ Go-Live
ƒ 100%
ƒ 100%
ƒ 50%
ƒ TBD, based on Cutover
Plan
Trainers
Trainers will participate
in Motorola-led Train the
Trainer courses and
work with Motorola to
develop End-User
curriculum. They may
also help support Go-
Live.
ƒ CAD Train the Trainer
ƒ Mobile Train the Trainer
ƒ End-User Training
ƒ Go-Live
ƒ 100%
ƒ 100%
ƒ TBD
ƒ TBD, based on Cutover
Plan
6.7
Project Phases and Elements
The project will be implemented in accordance with the tasks and activities described below. The below
table represents the project phases and primary elements of each.
Page 87
6.8
Project Planning
A clear understanding of the needs and expectations of both Motorola and MCSO are critical to
fostering a collaborative environment of trust and mutual respect. Project Planning requires the
gathering of project-specific information in order to set clear project expectations and guidelines, create
the Project Management Plan and project schedule, and set the foundation for a successful
implementation. Examples of information gathered include the Business Process Review Agency Pre-
Kick-off Survey (a survey that is sent to MCSO to collect agency-specific information, such as dispatch
logistics, communication center information, operational process, and workflow). These documents are
collated into a single Team Project Sync (TPS) packet that will be delivered via the project
management portal/work management system by the Motorola PM prior to the start of the Project
Planning Session.
6.8.1
Project Management Plan
The Project Management Plan describes the project scope, objective, critical success factors, and roles
and responsibilities of project team members. This includes an organizational chart, mutual agreement
to the form, and format of all documentation between the parties, as well as the plans that describe the
criteria for managing risk, resources, quality, schedule, configuration and change.
A portal or repository will be established into which all project documentation and controls will be
posted. The project documents and artifacts described below will be maintained throughout the
implementation phase.
Documentation is organized into the following categories:
Project Status
x
Project Calendar
x
Monthly Status Report
Page 88
x
Project Status Meeting Minutes
x
Ad-hoc Project Meeting Minutes
x
Master Schedule
x
Action Item Register
x
Risk Management Register
Project Controls
x
Governance
-
Escalation procedures (issues and/or personnel)
x
Requests for Information
x
Change Control Requests
x
Project Submittals
x
Change Order Request Process
x
Change Order Log
x
Milestone Completion Certificates
x
Project Knowledge Database (Lessons Learned)
Project Communications
x
Communication Plan
x
Project Team Rosters/Organizational Chart
6.8.2
Project Planning Session - Teleconference/Web Meeting
A Project Planning Session teleconference will be scheduled after the Agreement has been executed.
The Project Planning Session is an opportunity for both the Motorola and MCSO PMs to meet prior to
the formal Project Kick-off meeting and review key elements of the project as well as expectations of
each other. The agenda includes:
x
A high-level review of the following project elements:
-
The Agreement documents.
-
A summary of the contracted applications, query(ies) and interface(s), and Equipment List.
-
Project delivery requirements as described in this SOW.
-
Which tasks will be conducted by on-site Motorola resources as well as the activities when
the Motorola PM will be on-site.
-
MCSO involvement in provisioning to confirm understanding of the scope and required time
commitments.
-
The high-level Project Schedule milestones and dates.
-
The Project Management Plan structure.
x
Confirm CJIS background investigations and fingerprint requirements for Motorola employees
and/or contractors.
x
Review CommandCentral Admin and Learning eXperience Portal (LXP) roles in the Project Plan
and provide MCSO Username and Access Information.
Page 89
x
Discuss Motorola remote access requirements (24-hour access to a secured two-way Internet
connection to the Motorola system firewalls for the purposes of deployment, maintenance, and
monitoring).
x
Discuss MCSO obligation to manage change among the stakeholder and user communities.
x
Provide Team Project Sync (TPS) packet five (5) days prior to the teleconference.
x
Review the Team Project Sync (TPS) packet. The information in this packet is used to prepare
for the Project Kickoff Meeting and BPR.
x
Review Software System completion criteria and the process for transitioning to support.
Note - Completing the TPS is a critical Project Task. Delayed, incomplete, or inaccurate information or
lack of participation will have a significant impact on the Project Schedule.
Motorola Responsibilities
x
Schedule the remote Project Planning Session.
x
Request the assignment and attendance of Customer Core Team and any additional MCSO
resources that are instrumental in the project's success, as needed.
x
Provide the initial Project Schedule and Project Management Plan.
x
Confirm MCSO receipt of the TPS packet and GIS Requirements Document.
x
Conduct a review of the Project Management Plan.
-
Project Portal/Repository
-
Project Status
Monthly Calendar
Project Status Meetings Minutes
Ad-hoc Status Meeting Minutes
Project Schedule
Action Item Register
Risk Management Register
-
Project Controls
Governance
à
Escalation procedures
Requests for Information
Task Orders
Change Order Requests
Project Submittals
Change Order Process
Change Order Log
Milestone Completion Certificates
Project Knowledge Database
-
Project Communications
Communications Plan
Project Team Rosters/Organization Chart
-
Project Delivery
Page 90
Technical Design and implementation
Business Process and Application Provisioning
Training
x
Review Motorola’s delivery approach and its reliance on MCSO provided remote access.
x
Document the mutually agreed upon Project Kickoff Meeting Agenda.
-
Introductions
-
Project Overview
-
System Architecture
-
Delivery Timeline
-
Schedule Management
-
BPR and Provisioning
-
Discovery Sessions
x
Request user information required to establish MCSO in the Motorola LXP.
x
Establish MCSO within the CommandCentral cloud platform, enabling CommandCentral as
outlined in the System Description.
x
Provide MCSO with a web link (URL) to the CommandCentral Admin portal.
x
Provide link or path to downloadable apps (as defined in System Description) on Google Play
Store or Apple App Store.
x
Review Training Plan
x
Identify the training collateral required by MCSO to comply with MCSO training department
requirements.
MCSO Responsibilities
x
Confirm with Motorola, MCSO GIS Administrator reviews the GIS Requirements Document.
x
Provide existing GIS source data to Motorola by the start of Project Kickoff and Discovery.
x
Identify MCSO Core Team and any additional MCSO resources that are instrumental in the
project's success, as needed.
x
Review the Project Management Plan.
x
Provide Core Team with TPS; return the completed TPS to Motorola no later than ten business
days before start of Project Kickoff Meeting.
x
Provide acknowledgement of the mutually agreed upon Project Kickoff Meeting agenda.
x
Provide approval to proceed with the Project Kickoff meeting.
x
Provide LXP and CommandCentral user information: first name, last name, unique email
address, and role.
x
Verify MCSO Administrator(s) have access to the LXP and CommandCentral Admin portal
x
Review and complete the Business Process Review Agency Pre-Kickoff Survey within ten
business days of the Project Planning Session to avoid impact on the Project Schedule.
Motorola Deliverables
x
Project Kickoff Meeting Agenda
x
Project Management Plan
x
High Level Project Schedule
Page 91
x
TPS packet
6.9
Marketing Campaign
Motorola recognizes the importance of generating interest in and enthusiasm for the roll-out of
Motorola’s new technology among users and other members of your agency. To facilitate
communications and share progress of the deployment within the department, Motorola will employ the
following components.
x
Intranet Portal:
-
A central "Source of Truth" intranet portal will be created, providing training materials,
current status updates, upcoming events, and detailed information on processes, policies,
and procedures.
-
The portal promotes interdepartmental channels via QR codes, ensuring easy and high
accessibility.
-
Daily administration of the portal will be managed by MCSO website administrator.
x
Advertising Campaign:
-
Pull-up banners will be placed in hallways and briefing rooms across various department
locations.
-
Posters and digital ads will be created and distributed within the agency through regular
email and instant message distributions.
-
Leadership, including watch commanders, sergeants, and records division management, will
receive monthly communication plans with messaging for verbal delivery during team stand-
up meetings, shift briefings, and other speaking opportunities.
x
Marketing Videos:
-
Professionally produced videos to showcase the new technology.
Department actors and actresses may participate in the videos, including interview sections
with command staff endorsing and promoting the change.
-
Videos can be utilized at department events, project status meetings, and posted on the
website. They will also be distributed via email marketing campaigns.
Motorola will engage the members of the MCSO’s Organizational Change Management team during the
Planning and Kickoff activities to provide examples of marketing collateral that can be delivered to MCSO. MCSO
and Motorola will mutually agree to the final deliverables that Motorola will provide.
Motorola Responsibilities
x
Provide structure/framework for intranet portal.
x
Provide content for intranet portal.
x
Develop and provide pull-up banners.
x
Create and deliver posters and digital ads.
x
Provide monthly communication plans through project closure.
x
Produce marketing videos.
Page 92
MCSO Responsibilities
x
Provide environment (i.e. SharePoint site) to host intranet portal.
x
Work with Motorola to develop intranet portal.
x
Administer the intranet portal.
x
Place banners and posters throughout agency locations.
x
Distribute digital ads via email and messaging.
x
Participate in production of marketing videos by making agency resources available, to the
degree MCSO determines.
Motorola Deliverables
x
Structure/framework and content for intranet portal
x
Banners, posters, and digital ads
x
Marketing videos
6.10
Kickoff and Discovery
6.10.1
Project Kickoff Meeting– On-Site Meeting
The purpose of the Project Kick-off Meeting is to introduce project participants and review the scope of
the project. The Project Kick-off event consists of various branched activities such as the BPR, the Site
Survey, and Interface Planning session (which commence following the general kickoff meeting, while
Motorola resources are still on-site), Reporting Overview teleconference, the GIS Discovery Session,
and CommandCentral Overview teleconferences. Availability of Customer Core Team and relevant
resources to participate in each activity is critical to the project success.
The Motorola PM, lead Application Specialists, and lead Solutions Architects travel to MCSO’s site.
Other Motorola project team resources attend remotely.
Motorola Responsibilities
x
Schedule and facilitate the Project Kickoff Meeting to clarify roles and responsibilities, establish
team-working relationships, and initiate project tasks.
x
Provide Project Kickoff presentation to MCSO PMs at least 4 business days prior to Project
Kickoff Meeting
x
Conduct the Project Kickoff in accordance with the agenda
x
Present a high-level overview of project scope.
x
Review the delivery schedule and associated requirements.
x
Confirm MCSO access to the LXP.
x
Confirm MCSO is established in CommandCentral Admin portal.
MCSO Responsibilities
x
Provide a meeting space equipped with remote conferencing capability, enabling remote
Motorola project team members to participate.
x
Identify and ensure participation of Customer Core Team and other key team members in
kickoff and project initiation activities.
Page 93
x
Provide input to the delivery schedule.
x
Confirm access to the LXP.
x
Confirm access to CommandCentral Admin portal.
Motorola Deliverables
x
Project Kickoff Meeting Minutes
x
Baselined Project Schedule as result of all planning and review/overview activities
Note - The Project Schedule will be maintained by Motorola and updated through mutual collaboration.
Schedule updates that impact milestones will be addressed via the change provision of the Agreement.
6.10.2
GIS Discovery Session Teleconference
A GIS Discovery Session will be scheduled to review the GIS Data Requirements document and
complete an overview of the GIS components of the project. The agenda will include:
x
Review the Motorola GIS Data Requirements document.
x
Discuss MCSO GIS skill-set and responsibilities.
x
Review the requirements of MCSO’s GIS sample data for the Motorola system.
x
Discuss any GIS related project questions.
Motorola Responsibilities
x
Schedule and conduct the remote GIS Discovery Session.
x
Request initial GIS dataset for data review.
MCSO Responsibilities
x
Review the GIS Data Requirements document prior to the meeting.
x
Discuss any areas of concern relative to GIS and schedule requirements.
x
Provide initial GIS dataset for review by Motorola.
Note - Providing MCSO GIS Data is a critical Project Task. Delayed, incomplete, or inaccurate
information may have a significant impact on the Project Schedule.
Motorola Deliverables
x
GIS Discovery Agenda
6.10.3
Reporting Services Overview Teleconference
The Reporting Services Overview will be scheduled to review the reporting functionality within the
Application(s), to review the reports available in the standard reports library and review the list of
reports Motorola will develop. The agenda will include:
x
A review of the Training Plan specific to reporting services.
x
Discuss MCSO Report Writer skill-set and responsibilities.
x
Review standard reports library.
x
Expectations and pre-work required for SSRS and IDD workshops.
x
Review list of custom reports.
Page 94
Motorola Responsibilities
x
Lead the discussion on the report writer skill-set and responsibilities.
x
Discuss expectations and pre-work that must be completed prior to the start of SSRS Report
Builder training.
x
Discuss and schedule SSRS and IDD Workshops.
x
Identify any areas of concern and limitations relative to standard reports and reporting services.
MCSO Responsibilities
x
Identify MCSO SMEs and stakeholders who will provide input of contracted printouts and IDD
dashboards.
x
Discuss any areas of concern relative to Reporting and schedule requirements.
Motorola Deliverables
x
Summary of overview identifying MCSO resources who will be involved in report writing
6.10.4
CommandCentral Overview Teleconference
The CommandCentral Overview will be scheduled to review the functionality within the
CommandCentral application. The agenda will include:
x
A review of the included CommandCentral applications, functionality, and integrations.
x
CommandCentral Administrator responsibilities and key deployment interactions.
Motorola Responsibilities
x
Lead the discussions on applications, functionality, and integrations.
x
Discuss CommandCentral Administrator responsibilities.
x
Enable designated MCSO Application Administrator with access to the LXP and
CommandCentral Admin Portal.
MCSO Responsibilities
x
Participate in discussion and reviews.
x
Provide Motorola with the names and contact information for the designated LXP and
application administrators.
x
Validate access to the LXP and CommandCentral Admin portal.
Motorola Deliverables
x
Administrator Credentials for LXP
x
Administrator Credentials for CommandCentral Admin Portal
6.10.5
Interface Planning Session
The objective of the interface planning sessions is to discuss the interface experience presented by
each contracted interface. Motorola will work with MCSO to schedule the sessions in logical groupings,
i.e. CAD interfaces, Records interfaces, and within those categories, related interfaces, i.e. data feeds.
The initial review sessions will occur on-site and, if required, followed up via remote meetings.
Topics of discussion will include the following:
Page 95
x
The functionality delivered with each interface as presented in the System Description and
associated Interface Functional Documents (IFDs) included in this Agreement.
x
Deployment requirements and dependencies of each interface (NDA, network information, API,
and access credentials required to connect to third-party systems).
x
Interface delivery and validation process.
Note - The interface deployment requirements are a prerequisite to roll out the interfaces. Delayed, incomplete, or
inaccurate information may have a significant impact on the Project Schedule.
Motorola is not responsible for third-party vendor management, scheduling, or additional cost for
software, modification, development, or testing unless the work is defined in this SOW or amended to
the Agreement via a change order.
Motorola Responsibilities
x
Discuss the need for additional information such as third-party API, SDKs, data schema, and
any internal and third-party documents necessary to establish interfaces.
x
Facilitate an overview of the interface to explain how each functions as well as any dependency
on third-party API, SDKs, data schema, and any internal and third-party documents necessary
to establish interfaces with local and remote systems.
x
Communicate the functional interface validation process.
x
Update IFDs as required to document additional third-party information.
MCSO Responsibilities
x
Establish all required third party API(s) and SDK(s) and provide all licensing and documentation
for MCSO’s existing systems.
x
Collect information on third-party API, SDKs, data schema, and any internal and third-party
documents necessary to establish interfaces with all local and remote systems and facilities
within ten days of the Project Kickoff Meeting or as mutually agreeable to avoid impact on the
Project Schedule.
x
Establish network connectivity between the Motorola server(s) and all third-party interface
demarcations.
Motorola Deliverables
x
Updated IFDs
6.10.6
Interface Design Review
Motorola and MCSO will have reviewed Motorola’s interface design, at the time of contract, as
documented in the IFDs in order to verify consensus of functionality of the interface prior to Motorola
commencing with development/deployment efforts. The review will include the structure of the interface,
involved data elements and data mapping, event trigger, update cadence, communication path,
connectivity requirements, and the expected user experience. Changes in design and or functionality
identified during the review that impact Motorola’s level of effort to develop the interface will be
evaluated for cost and price impact. In such cases, Motorola reserves the right to provide MCSO with a
change order to reflect the change in scope and any resulting change for the increased or decreased
price or to de-scope the interface from the contract. This activity will occur on-site.
Page 96
Motorola Responsibilities
x
Conduct a review of the interface to explain the design of the interfaces and how the interfaces
function in the Motorola system.
x
Work with MCSO’s third-party vendors, as required, to clarify any connectivity issues/data
transfer issues.
x
Finalize the IFDs to document information required to support required interface functionality,
identifying changes in scope from initial IFDs.
x
Consensus of the design will be memorialized by MCSO signature on the IFDs before Motorola
commences with any development/deployment activities.
MCSO’s Responsibilities
x
Make knowledgeable individuals available for the reviews.
x
Provide clarity on the use case of the interface and verify the functional specification in the IFD
meets the use case or identify desired changes to the specifications.
x
Facilitate communications and assist with resolution of issues that arise between Motorola and
MCSO’s third-party vendor(s).
x
Assume costs associated with efforts required of the third-party vendors, which may include
professional services, API/SDK fees, Non-Disclosure Agreements, licenses, and configuration
or development, if necessary, to support desired interface functionality.
x
Memorialize the interface specification by signature expeditiously, enabling Motorola to initiate
development activities.
x
Initiate a Change Order for any modifications.
x
Approve the Final IFDs
Note - Unknown circumstances, requirements, and anomalies at the time of initial design can present difficulties in
interfacing with some third-party applications. These difficulties could result in a poorly performing or even a non-
functional interface. When information and access to systems is provided, Motorola will attempt to mitigate these
difficulties. If Motorola mitigation requires additional third-party integration, application upgrades, API upgrades,
and/or additional software licenses, those costs will need to be addressed through the change order provision of
the Agreement.
Motorola Deliverables
x
Final IFDs
6.10.7
Contract Design Review
The objective of the Contract Design Review (CDR) is to review the contracted Products, Equipment
List, Training Plan, System Validation Plan, and contractual obligations of each party. The CDR will
occur following the conclusion of the Project Kick-off meeting while Motorola resources are still on-site.
In the event the CDR cannot commence following the Project Kick-off meeting while Motorola
resources are on-site, Motorola will schedule a web conference session at a mutually agreeable date
and time.
Motorola Responsibilities
x
Review third-party partner solutions and involvement in the project, as applicable.
x
Summarize and review the contracted Products, query(ies), and interface(s) described in the
System Description.
Page 97
x
A summary review of the contracted applications, query(ies) and interface(s), and Equipment
List.
x
Check the system Equipment List and note any necessary modifications.
x
Review handheld device hardware specifications, iOS or Android version requirements, and
reference to applicable CJIS security requirements.
x
Lead the discussion of the Training Plan, prerequisites, and associated requirements.
x
Plan installation activities with MCSO.
x
Discuss the Product Validation process for the contracted products.
x
Author CDR meeting minutes.
MCSO Responsibilities
x
Review all contract materials, inclusive of exhibits: e.g., Equipment List, Training Plan, SOW.
x
Prepare a list of questions pertaining to contracted materials and exhibits.
Motorola Deliverables
x
CDR meeting minutes
6.11
Environment Review and Site Preparations
6.11.1
Site Survey and IP Network Analysis
Following the Project Kick-off meeting, while Motorola resources are on-site, Motorola will review the
existing infrastructure(s) and installation location(s) to validate that the installation environment(s) and
local and wide area networks will provide optimal support of the Motorola solution. A single site
survey/IP Network Analysis will be conducted at the primary installation location, and a single site
survey will be conducted at the disaster recovery location.
The purpose of the site survey is to confirm MCSO’s installation environment conforms to the site
requirements presented in the System Description and hardware manufacturer specification. Motorola
will also verify that the physical installation environment is accessible, without special accommodation,
to support the movement of equipment in MCSO’s facility from the receiving dock to the equipment
room. Examples of areas of concern include door/hallway widths and heights, stairs, elevator weight
limitations, ventilation including cooling, power receptacle locations, and power types.
Motorola makes no provision and has no responsibility for cabling, special accommodations, power
consumption, or capital improvements to the installation environment that may be required to support
the Motorola system.
Motorola Responsibilities
x
Review the site requirements section of the System Description with MCSO.
x
Facilitate a meeting to review the physical installation environment and equipment travel path
from receiving dock through to equipment room.
x
Analyze IP network data.
x
Prepare a report with recommendations for any site and/or network preparation required to
provide an optimal environment for installation of the system equipment and identify any
deficiencies related to power, power supplies, cabling, IP network connectivity, and
communications equipment.
Page 98
MCSO Responsibilities
x
Provide escorted access to the installation location where Motorola system equipment will be
installed.
x
Provide documentation on the current infrastructure (i.e. existing hardware and operating
system software components and terminal networks), as well as projected utilization statistics
and other information as is reasonably required to validate final hardware requirements.
x
Provide information on current network architecture and configuration, as well as physical site
information, such as building plans and schematics, as available.
x
Provide IP addresses on MCSO’s network for the system servers and third-party application
servers. All server names and IP addresses behind Motorola’s Firewalls cannot be changed.
x
Make knowledgeable staff available to explain the current architecture, infrastructure, and
physical environment conditions (e.g. building engineers/electrician) as needed.
x
Provide a site for the installation, operation, and maintenance of all computer server(s),
workstation(s), and related peripherals in accordance with Motorola requirements and all
network infrastructures described in the System Description.
x
Ensure the computer processor(s), operating system software, third-party software, all
associated workstations, printers, communications, and related components conform to the
specifications in the System Description.
x
Provide a work area for Motorola on-site staff in the primary facility, located near, but outside of,
the computer machine room. The room must be equipped with a workstation, AC power to
support workspace for a minimum of two people, and Internet access. Wireless access is
recommended. This work area must be available during the course of the project.
x
Provide 24-hour access to a secured two-way Internet connection to the Motorola system
firewalls for the purposes of deployment, maintenance, and monitoring throughout the course of
the project and during maintenance and warranty phases.
x
Provide three (3) NTP timing sources available to the PremierOne Servers.
x
Review and approve the final hardware and operating system software configuration with the
Motorola project team.
x
Provide any cabling or capital improvements required for the installation environment and/or
power consumption considerations.
x
Provide reasonable care to prevent equipment exposure to contaminants that cause damage to
the equipment or interruption of service.
Motorola Deliverables
x
Site Survey and Network Analysis Results
6.11.2
ASTRO 25 Data Capacity Analysis
The objective of the Data Capacity Analysis is to verify that MCSO’s ASTRO® 25 communication
system is properly equipped, configured, and has the capacity to support ASTRO 25 data dependent
PremierOne CAD features, as described in the System Description. The results of the capacity analysis
provide guidance for provisioning ARL and AMS features. A System Engineer will conduct the analysis
of the existing ASTRO 25 system. If an ASTRO 25 system is in deployment, then the analysis will be
performed on the contracted ASTRO 25 system design. Some of these tasks are performed on-site.
Page 99
Motorola Responsibilities
x
Collect and review as-built information about the ASTRO 25 system from the ASTRO 25
deployment team, System Manager, or MCSO.
x
Document any deficiencies in the ASTRO 25 system such as licenses, product versions,
firmware versions, and system components required for PremierOne/CommandCentral ASTRO
25 integration.
x
Gather current ASTRO 25 system architecture, configuration, product, and firmware versions, if
Motorola-supported system.
x
Collect 30 days of ATIA data from the production ASTRO 25 system.
x
Analyze the ATIA data to determine the busy-hour voice load model.
x
Collect PremierOne CAD/CommandCentral provisioning parameters.
x
Collect current incident usage statistics.
x
Document the operation of ARL and AMS features including estimates of anticipated use.
x
Analyze collected data and define a data load model based on the desired features and target
configuration.
x
Perform a voice and data capacity analysis using the Hydra ASTRO 25 modeling tool. Multiple
scenarios will be considered in an effort to optimize the use of available RF channels to provide
PremierOne functionality, while maintaining the required voice Grade of Service (GoS).
x
Prepare ASTRO 25 Capacity Analysis Report that describes any required ASTRO 25 system
changes.
MCSO Responsibilities
x
Provide access to the ASTRO 25 Primary Site for collection of ATIA and configuration data.
x
Provide information on current ASTRO 25 system architecture, configuration, product, and
firmware versions, and any planned changes to the ASTRO 25 system, if ASTRO 25 system is
self-maintained.
x
Provide information about the current subscriber types, quantities, and expected use.
x
Provide information about any other current or planned users on the ASTRO 25 system.
x
Identify all current and planned ASTRO 25 data applications (e.g. third-party mapping
applications, Radio Management).
x
Review and discuss the Data Capacity Analysis report with Motorola.
x
Complete any ASTRO 25 improvements or version upgrades necessary to support the
PremierOne solution as documented in the ASTRO 25 Capacity Analysis Report .
x
Provide circuits and connectivity between the radio core, IMW, CEN, and CAD system.
Motorola Deliverables
x
ASTRO 25 Capacity Analysis Report
Page 100
6.12
GIS Services
6.12.1
GIS Scope Review
For this review, the Motorola GIS Specialist meets remotely with MCSO’s GIS Administrator to discuss
the approach to developing the GIS data for use with the Motorola system.
GIS Scope Review topics to be discussed include the following:
x
For CAD - Agency Response boundary needs, routing requirements, premise hazard areas and
specifics for address validation using street centerlines, common place points, address points,
and alias tables.
x
Mobile iOS/Android – Discuss agency-type specific web maps. Up to One (1) web map per
agency type (police and fire/EMS) will be delivered, based on the CAD data set.
x
For Records - Data types necessary for address validation support in the system, including
street centerlines, common place points, address points, street alias tables, and common place
alias tables.
The GIS Data Report describes MCSO’s source feature classes and data values that have been made
available to Motorola. The data is reviewed, and any items that may impact the applicable functionality
of the data within the Motorola System are noted in the GIS Data Report. The GIS Data Report is
delivered post-contract after review of MCSO GIS data. As GIS data is critical to the provisioning and
operation of the system, it is imperative that MCSO GIS Data be made available to Motorola prior to the
GIS Scope Review.
Motorola Responsibilities
x
Review GIS Draft Data Report.
x
Discuss current GIS business practices.
x
Review GIS data types to be used within the Motorola system.
x
Request that Agency Code and Beat Names be provided to Motorola prior to the GIS
Boundaries Workshop.
MCSO Responsibilities
x
Ensure availability of GIS Administrator for this meeting.
x
Confirm availability of the Esri ArcGIS Desktop and Network Analyst extension software
required for editing of GIS data.
x
Finalize the Agency Code and Beat Names for the geodatabase and provide to Motorola. All of
the data will be required, but the streets, address points, and common places can be works in
progress to be updated as the project progresses.
Note - Providing the Agency Code and Beat Names for the geodatabase is a critical Project Task. Delayed,
incomplete, or inaccurate information may have a significant impact on the Project Schedule.
Motorola Deliverables
x
GIS Data Report
Page 101
6.12.2
GIS Service Delivery
GIS Service delivery provides for the creation of a draft geodatabase that will be uploaded to the CAD
server to support provisioning efforts as well as draft maps that are created for use by the CAD
workstations. The GIS draft geodatabase is also required for address validation in PremierOne
Records.
Error reports are produced as a result of developing the draft geodatabase and will be delivered to
MCSO in updates to the GIS Data Report. MCSO will correct any data errors allowing Motorola to
incorporate the data into a revised draft geodatabase.
Geodatabase development provides for up to two iterations of draft databases developed by Motorola.
The final geodatabase is created as a product of the GIS Administrator Workshop. These tasks are
performed remotely.
Note – The following are supplementary (not included in the scope of this Agreement) to the tasks
required to maintain the data using the Esri Arc software:
x
Education that is specific to the use of the Esri Arc software, which can be obtained from Esri.
x
Creation or maintenance of GIS data.
x
Motorola is not responsible for data errors stemming from MCSO’s source data.
If MCSO is unable to perform these duties, Motorola may be able to provide the services at an
additional cost.
Motorola Responsibilities
x
Schedule and initiate a data delivery design teleconference to address critical data errors or to
confirm the data being incorporated into the draft geodatabase.
x
Create the draft visual maps and Routing Network.
x
Create the draft geodatabase.
x
Provide updates to the GIS Data Report reflecting any issues found during the geodatabase
build.
x
Provide up to two iterations of draft geodatabases.
x
Initiate GIS Administrator Readiness Check, which enables Motorola to schedule and conduct
the GIS Administrator Workshop.
MCSO Responsibilities
x
Attend data delivery design teleconference.
x
Correct any GIS errors identified in the GIS Data Report from geodatabase build.
x
Participate in the GIS Administrator Readiness Check and confirm the dates for the GIS
Administrator Workshop.
Motorola Deliverables
x
GIS Data Report Updates
6.12.3
GIS Administrator Workshop and Review
The GIS Administrator Workshop enables MCSO to work with the Motorola GIS Specialist to
understand the required GIS data structure and maintenance needs of the data in order to support
address validation, response determination, routing, and visual map displays. The workshop is
Page 102
conducted via remote teleconference over a period of two weeks, consisting of 24 hours of delivery,
during normal business hours. The product of the workshop is the final geofile build, and MCSO
assumes responsibility for further GIS updates and maintenance.
Motorola Responsibilities
x
Provide MCSO with the workshop agenda.
x
Conduct the workshop.
x
Provide an overview of the City Code, Agency Code, and Beat Names roles in the CAD system.
x
Discuss additional boundary capabilities and data development needs.
x
Document any MCSO and/or Motorola GIS action items that require follow up and resolution.
x
Resolve any Motorola follow-up action items.
x
Schedule the post-workshop follow-up review and GIS action item close out.
x
Within 30 days of the conclusion of the GIS Administrator Workshop, conduct a remote, two-
hour post-workshop follow-up review to address any remaining GIS process questions and
close out any follow-up actions noted during the GIS Administrator Workshop.
MCSO Responsibilities
x
Ensure availability of GIS Administrator for the workshop.
x
Resolve any MCSO follow-up action items.
x
Assume responsibility for the update and maintenance of the geofile.
x
Participate in the follow-up review.
Motorola Deliverables
x
Completion of GIS Workshop (in accordance with the Training Plan)
x
Final Motorola geofile build
6.13
Business Process Review (BPR)
6.13.1
Business Process Review
Motorola-led BPRs provide the opportunity for Motorola and MCSO to gather and measure information
variables and data of interest, and it provides Motorola and MCSO the opportunity to review current
operational processes and workflows and determine the provisioning parameters that will provide the
most optimal use of the Motorola system(s). The BPRs are conducted on-site.
The multifaceted review provides Motorola the opportunity to gather information on the day-to-day
operations of the different departments and users of the Motorola system(s); this could include
Communications Center, Field Personnel, Records Divisions, Real-Time Crime Centers. Information is
used in the process of creating the BPR Workbook and evaluating the agency’s current processes for
alignment with the new system deployment.
Note - Training engagements and provisioning reviews, as described in this SOW, are provided further on in the
project in accordance with the project schedule.
A BPR session is conducted separately for CAD/Mobile and Records/Records Mobile. One instance of
the activities described as “the BPR” will be conducted for a combined audience for CAD/Mobile and
one instance of the BPR activities will be conducted for a combined audience for Records/Records
Page 103
Mobile. The information collected in the BPRs will be used to determine the provisioning parameters
and enables Motorola to provide MCSO guidance on application provisioning and configuration options
that best meet MCSO’s needs and the requirements in Exhibits F and G - CAD and RMS Functional
Requirements Matrix respectively. The BPRs will be conducted following the Project Kick-off. The BPR
observation and information gathering process occurs on-site for no more than three consecutive days
each for CAD/Mobile and Records/Records Mobile in accordance with the project schedule.
Information gathered during the CAD/Mobile BPR and captured in the BPR Workbooks includes but
isn’t limited to general information about the communications center, roles of communications
personnel and the permissions the roles will require, dispatch processes and workflows, current
commands and functions, code tables, procedures regarding patrol/field personnel use of mobile
devices. Motorola will identify the information that must be gathered by MCSO personnel and provided
to Motorola for provisioning, including the required formats.
Information gathered during the Records BPR includes statute management, crime report
requirements, case report workflow and identification of Records modules that will be used. The
Records BPR will also address the information required to provision CommandCentral Responder
(citations and field interviews). Motorola will identify the information that must be gathered by MCSO
personnel and provided to Motorola for provisioning, including the required formats.
The Motorola GIS Specialist will meet remotely with MCSO’s GIS Administrator and CAD SMEs to
discuss and confirm Response Boundaries data that is loaded into CAD. Motorola will provide an
overview of the available boundary types and their function in CAD. Topics will include confirmation of
MCSO’s City Code, Agency Code, Beat Names, and their role in CAD to determine if any modifications
need to be made prior to import into the System.
The BPR will be attended by MCSO’s Core Team and additional agency SMEs as necessary. The
practical input based on experience in MCSO’s operational environment is indispensable in the
configuration of the system. Attendees will have the authority and responsibility of making declarative
statements and decisions about business practices and implementation of Motorola systems.
MCSO is responsible for engaging their core team and user agencies that will be provisioned in the
Motorola system(s) to obtain required inputs. It is preferable to have personnel that are required for one
section to attend all sections of the BPR information gathering process to ensure all parties are
represented. If an additional BPR or provisioning for additional agencies is required, it will be addressed
via the change order provision of the Agreement.
Motorola Responsibilities
x
Provide the BPR Agenda/Workbook(s) prior to the meeting.
x
Conduct separate BPR sessions for each of the contracted Product categories; one each for
CAD/Mobile, Records/Records Mobile.
x
Complete BPR Workbook(s) for contracted Product categories.
x
Request copies of completely populated sample forms, reports, dashboard views, and printouts
currently utilized.
x
Provide CAD Provisioning Data Gathering Guide.
MCSO Responsibilities
x
Review the BPR Agenda(s)/Workbook(s) prior to the meeting.
x
Complete prerequisites listed in the TPS prior to this meeting.
x
Ensure availability of the Core Team.
Page 104
x
Provide Motorola with copies of completely populated sample forms, reports, dashboard views,
and printouts currently utilized.
x
Review completed BPR Workbook(s) for contracted Product categories.
x
Confirm readiness of City Code, Agency Code, and Beat Names for loading into CAD.
x
Review CAD Provisioning Data Gathering Guide.
x
Approve CAD/Mobile BPR Workbook and Records BPR Workbook
Note - Import of the City Code, Agency Code, and Beat Names for the geodatabase is a critical Project Task.
Delayed, incomplete, or inaccurate information and BPR Workbooks may have a significant impact on the Project
Schedule and start of Provisioning Workshops.
Motorola Deliverables
x
BPR Agenda(s)
x
BPR Workbook(s)
x
CAD Provisioning Data Gathering Guide
6.13.2
MCSO Module-Level Requirements Gathering Workshop
PremierOne Records supports the ability to configure forms, modules, and screens. These
configurations consist of the following data elements. Motorola will perform up to 500 total
configurations identified during the Records BPR. In addition, Motorola will develop MCSO specific
modules identified in the System Description that contain up to thirteen hundred forty (1340) additional
configurations (field changes or additions or new modules). The workshop to gather requirements for
these modules is conducted during three (3) consecutive days on-site.
Data Element Configurations
Adding New
Modules
Adding New View
Adding New Pane
Adding Fields
Hiding Fields
Adding Grids
Adding Labels
Adding Text
Adding Image Box
Adding Hyperlink
Adding Groups
Hierarchical Code
Tables
Field to Code Table
Binding
Dependencies
Change Caption
Validations
Learn Mode
Information
Conversions
Swapping Code
Tables
Total Field
Configuration
Further discussion of the data element configurations will be done during the Records BPR and
documented within the BPR Workbook.
In the event MCSO’s requested changes exceed 1340 (as captured and tracked in the BPR workbook),
Motorola can provide, at MCSO request, a level of effort estimate for module level configurations and/or
form development that exceeds the scope of standard module tailoring and/or not expressly stated as
being developed and provided by Motorola ). This could incur additional costs and/or increase in
timeline. MCSO may make module level configurations or develop new forms themselves using the
Advanced Configuration Tool (ACT) or contract with Motorola to do this work via the change provision
of the Agreement.
Motorola Responsibilities
x
Document desired configurations as the draft MCSO specific modules in the BPR Workbook.
x
Review existing agency Citation processes including creation, submission, printing, sync with
RMS, supervisor or records personnel approval and submission to the Court system.
Page 105
x
Define citation fields including:
-
Field types (e.g., Name, Age).
-
Field validation (e.g., Optional, Mandatory).
-
Dynamic behavior (e.g., Alias Y/N field controls display of Alias field).
-
Field calculations (e.g., Age calculated from date of birth).
x
Review the state required citation format for printing (4-inch or 8.5x11-inch).
x
Review existing agency Field Interview processes.
x
Review existing form(s) used by agency(s) (e.g., existing paper form or software).
x
Receive feedback from MCSO and incorporate into final MCSO Specific Modules.
MCSO Responsibilities
x
Review and provide feedback on the desired configurations for the specific modules in the BPR
Workbook within 10 business days of receipt or as mutually agreed to between Motorola and
MCSO. If feedback is not received within the specified timeframe, Motorola considers this as the
final MCSO Specific Modules.
Motorola Deliverable
x
Updated BPR Workbook with MCSO specific module configurations
6.13.3
MCSO Specific Module Development
Motorola utilizes the information gathered in the BPR workbook during the ACT Module-Level
ReqXLUHPHQWV*DWKHULQJ:RUNVKRSWRGHYHORS0&62VSHFLILFPRGXOHVௗ7KHLQLWLDOGHYHORSPHQW
review, and final development is performed remotely.
Note that Module Development is typically a predecessor to Records Provisioning due to the potential
database changes new modules introduce. The Records Application Specialist will work with MCSO to
identify what Records provisioning, if any, may begin prior to the completion of module development.
Motorola Responsibilities
x
Develop MCSO specific modules.
x
Deliver a single draft of MCSO specific modules and review on MCSO system.
x
Receive feedback from MCSO and incorporate into final MCSO specific modules.
x
Deliver final MCSO specific modules to MCSO.
MCSO Responsibilities
x
Review and provide feedback on the draft of MCSO specific modules within 10 days of receipt
or Motorola considers this as the final MCSO specific modules.
x
Verify final MCSO Specific Modules.
Motorola Deliverable
x
MCSO Specific Modules
Page 106
6.14
Hardware and Software
6.14.1
Motorola Hardware Procurement
Motorola will procure the system equipment in accordance with the Equipment List.
6.14.1.1
System Staging
System staging provides for the installation of the premise-based software components on the
hardware at our staging facility. The system will be tested and verified to be operational in a staged
environment. Once validated, the system will be packaged and shipped to MCSO’s location for
installation.
Motorola Responsibilities
x
Receive the contracted hardware, software, and related components at the Motorola staging
facility.
x
Rack and install hardware components.
x
Conduct an equipment inventory and provide it to MCSO.
x
Install and configure system software.
x
Ship staged system to MCSO’s installation site.
MCSO Responsibilities
x
Receive the staged system and securely store it until Motorola installation.
x
Provide Motorola with written acknowledgement of receipt of delivered equipment.
Motorola Deliverables
x
Equipment Inventory that includes all Motorola-provided equipment, including models and serial
numbers, as applicable.
x
Staged System Delivery.
6.14.1.2
System On-Site Installation
The objective of this activity is to install the system at MCSO’s site. This activity addresses physical
installation activities and system connectivity verification.
Motorola Responsibilities
x
Install the staged system in MCSO’s environment to include connectivity between Motorola-
provided components and MCSO network components.
x
Maintain cable management within the rack/cabinets in a professional manner.
x
Label both ends of all network and power cables.
x
Conduct a Power On test to validate that the installed hardware and software are ready for
configuration.
x
Load preliminary provisioning data on primary system hardware.
x
Install and enable CloudConnect Virtual Machine and contracted cloud-based software.
x
Verify contracted software is available and accessible on the installed system.
x
Synchronize the primary and disaster recovery systems.
Page 107
x
Verify failover and restore connectivity.
x
Provide system administration credentials to MCSO to ensure full access to the system,
infrastructure components and databases.
MCSO Responsibilities
x
Confirm the server room complies with the requirements stated in the System Description.
x
Enable outgoing network connection (external firewall) to the CommandCentral cloud via a
MCSO provided internet connection.
x
Provide, install, maintain, and service any software as required for anti-viral, anti-malware
protection on the system. If the software requires connectivity to a central server for
maintenance and updates, the connectivity, including ports and access, needs to be provided.
x
Witness the power on test.
x
Confirm access to installed software.
Motorola Deliverable
x
Installed system.
x
Milestone acceptance certificate affirming successful “power on” test, availability of application,
demonstration of synchronization of primary and disaster recovery and failover/fail back.
x
System Administrator credentials
6.14.2
Windows Client Software Installation
Client software will be installed on workstations/mobile devices to facilitate provisioning activities and
provide instruction on-site to MCSO personnel who will complete software installation on the remaining
workstations/mobile devices.
Motorola understands MCSO intends to provision some number of workstations to use Virtual Desktop
Infrastructure (VDI). Motorola has not included the effort to support this. As discussed between
Motorola and MCSO, the following points were noted:
x
MCSO will have to script the running of our client configuration tool with a unique workstation id
(device id) when they do this process.
x
Each VM must meet the standard workstation specifications.
x
CAD clients cannot be “thin provisioned”. Each client must be statically built in the infrastructure
and assigned to the clients. This is important because things like E911 rely on knowing who sits
where.
-
Note that the next generation of the CAD client is expected to address this limitation.
-
MCSO may make one client then keep cloning it, changing the DNS name and updating the
configuration tool. Some customers have automated that part.
Motorola Responsibilities
x
Discuss client software distribution methodology.
x
Provide instruction on client software installation and install client software on up to five total
Client workstations and up to five total Mobile Windows clients. Provide MCSO with electronic
copy of Installation Guide.
x
Create Records client installation executable(s).
x
Verify Records Mobile client software functionality in offline mode.
Page 108
MCSO Responsibilities
x
Provide and install workstation/mobile device hardware in accordance with manufacturer’s
specifications.
x
Supply Windows Server Client Access Licenses (CALs) for all system client devices accessing
CAD, CAD Mobile, Records, and Records Mobile systems.
x
Assign personnel to observe the software installation process.
x
Provide advanced authentication for Mobile/Handheld device connectivity if required.
x
Provide power and network connectivity at designated workstation installation locations.
x
Provide wireless connectivity and middleware to deliver mobile Virtual Private Network (mVPN)
with routing and IP persistence to the system network.
x
Complete installation of client software on remaining workstations and mobile devices.
x
Procure, install, authorize, and configure ArcGIS Desktop/ArcGIS Pro and extensions.
Motorola Deliverables
x
CAD and Mobile Client Installation Guide.
x
Records and Records Mobile Client Installation Executables
6.14.3
Mobile Android and iOS Device Setup
Handheld device setup is primarily a MCSO series of tasks. Specifications for Handheld Devices can
be found in the System Description document. Motorola will provide remote guidance, make
recommendations, and provide access to Mobile Install Guide to facilitate MCSO’s Android and iOS
Device Setup.
MCSO Responsibilities
x
Provide handheld devices.
x
Provide, install, and configure mobile printers.
x
Provide and configure MDM software.
x
Verify all handheld devices are configured with applicable OS version, MDM software, and
printer configurations.
x
Verify devices meet CJIS requirements.
x
Permit Motorola Applications to be deployed from Apple App Store or Google Play Store.
x
Verify devices and applications can connect to CommandCentral cloud services.
x
Verify the device can access Google/Apple push notification.
x
Download and install application(s) on all handheld devices.
x
Provide sample handheld devices for all demonstrations.
6.14.4
Cumulative Updates
A Cumulative Update (CU) is a software update to one or more of the system applications. A CU may
be required to deliver specific features and functions and will need to be installed following the initial
system software installation. If CUs are installed by Motorola, the installation and demonstration of the
newly introduced or modified features/functions to MCSO will be performed remotely. CU delivery is
determined at Motorola’s discretion. If a CU that introduces new functionality is delivered following the
Page 109
conclusion of Motorola training, MCSO may purchase additional training as desired in accordance with
the Change Order provisions in the Agreement.
Motorola Responsibilities
x
Provide release notes.
x
Remotely install CU on the application servers.
x
Remotely demonstrate any new delivered features as needed and update the Functional
Validation Plan accordingly.
MCSO Responsibilities
x
Install CU on workstations.
x
Witness the demonstration of newly installed features, as required.
x
Provision the additional functionality as desired, based on the release notes.
x
Educate users on new features.
Motorola Deliverable
x
CU Release Notes
x
Functional demonstration of features that the CU was installed to resolve, if applicable.
6.15
System Provisioning
6.15.1
PremierOne Provisioning
The PremierOne applications can be provisioned to support various workflows, responses, and
recommendations, the effects of which are determined by the selections MCSO makes as part of
provisioning activities. PremierOne provisioning enables MCSO to select configurable parameters that
affect system outcomes (e.g. unit names, personnel, status codes, permissions). Using the information
captured in the BPR workbook and TPS, Motorola will provision the system to support MCSO’s
operational needs and expected operational outcomes.
6.15.1.1
Preliminary CAD Provisioning Profile
Motorola will develop a provisioning profile for CAD users based on the information and provisioning
approach documented in the BPR and MCSO-provided provisioning data. The provisioning profile will
reflect a subset of the provisioning data provided to Motorola by the County to include agency IDs, roles
and permissions, incident types, priorities, modifying circumstances and unit recommendations, officers
and special skills, unit types and capabilities, and other information the County deems necessary to
satisfy the requirements documented in the BPR Workbook. The provisioning profile is developed
remotely.
Motorola will schedule a remote meeting to review the provisioning to gain feedback and/or approval of
the provisioning approach. Motorola will proceed with the remaining provisioning and provisioning
workshops after approval of the provisioning profile is received from MCSO.
Motorola Responsibilities
x
Develop provisioning profiles.
x
Conduct meetings to review the provisioning profile.
Page 110
x
Modify provisioning profiles as required to meet functional requirements and the BPR.
x
Finalize the provisioning approach upon MCSO approval.
MCSO Responsibilities
x
Schedule applicable resources to participate in provisioning reviews.
x
Evaluate each of Motorola’s documented observations and suggestions for operational and
policy updates.
x
Provide feedback/requested changes to provisioning approach.
x
Review updated provisioning profiles.
x
Approve the final provisioning approach.
Motorola Deliverable
x
Final Provisioning Profile that reflects County’s approval of the provisioning approach
demonstrated by Motorola.
6.15.1.2
Provisioning Workshops
Motorola will perform all manual entry or import of all provisioning data. Motorola enters and/or imports
the provisioning data as provided by MCSO and then conducts workshops (“Set of PremierOne
CAD/Mobile Provisioning Workshops” and “Set of PremierOne Records Provisioning Workshops” as
described in the Training Plan) with MCSO participants of the BPR to demonstrate functionality and
workflows are consistent with the information and processes captured in the BPRs. The series of
workshops and checkpoints result with a Motorola-supported validation of the provisioned system. Four
CAD workshops are conducted on-site and two are conducted remotely. Three Records workshops are
conducted on-site and one is remote. Checkpoints are conducted remotely.
The focus of each workshop is defined in a Workshop Agenda that will be provided prior to the start of
each workshop. The objective of each workshop is the transfer of knowledge, from Motorola to MCSO,
of the provisioning parameters and options that affect system outcomes. PremierOne provisioning
activities will be completed for each contracted Product included in the system CAD, Mobile, and
Records.
Provisioning workshops are designed to be incremental and progressively advance provisioning
activities until provisioning is complete. Motorola will schedule and conduct checkpoints providing
MCSO a time to confer with Motorola.
Provisioning activities include instruction of the mechanics and methodologies required to maintain
system provisioning (Provisioning Training) and provides MCSO resources with the required knowledge
to maintain system provisioning required to support ongoing operational needs. On-site Provisioning
Training is presented as outlined in the Training Plan.
Note - Delayed, incomplete, or inaccurate information may have a significant impact on the Project Schedule.
Motorola Responsibilities
x
Provide MCSO with Provisioning Import Templates.
x
Conduct a review of the Provisioning Import Templates for MCSO completion.
x
Consult with MCSO on provisioning options that support MCSO’s business operations.
x
Provide guidance on making provisioning selections.
x
Import/enter information from the provisioning input templates.
Page 111
x
Complete additional provisioning data entry activities in accordance with existing and re-
engineered business processes.
x
Provide Agenda for each scheduled Workshop and Checkpoint.
x
Schedule Workshops and Checkpoints.
x
Conduct Provisioning Workshops and Checkpoints.
x
Educate MCSO on mechanics and methodologies required to complete and maintain system
provisioning.
x
Work with the County to update Exhibits F and G - CAD and RMS Functional Requirements
Matrix respectively to reflect changes as a result of provisioning and/or business process
changes, if applicable.
MCSO Responsibilities
x
Participate in the Provisioning Import Worksheet review.
x
Completed Provisioning Import Worksheets prior to the start of the second Provisioning
Workshop.
x
Attend all Provisioning Workshops and Checkpoints.
x
Complete tasks and assignments during and after each Workshop and Checkpoint.
x
Update provisioning selections, as needed.
x
Work with Motorola to update Exhibits F and G - CAD and RMS Functional Requirements Matrix
respectively in accordance with provisioning and business processes, if applicable.
Motorola Deliverables
x
Agenda for Provisioning Workshops and Checkpoints
x
Completion of Provisioning Workshops
x
Completed CAD and Records Provisioning
x
Updated Exhibits F and G - CAD and RMS Functional Requirements Matrix respectively to reflect
final Provisioning
6.15.2
CommandCentral Responder Provisioning
Provisioning is the process of configuring CommandCentral Responder and CommandCentral Cloud to
function based on the requirements in the System Description and the Records BPR Workbook. The
provisioning process is conducted by Motorola with input from Customer and will be performed during
provisioning of Records.
Motorola Responsibilities
x
Configure CommandCentral Responder based on BPR Workbook.
x
Configure CommandCentral Responder data capture forms.
x
Configure CommandCentral Responder citation mobile print format for defined number of
device combinations from the System Description.
x
Provide an on-site demonstration of the provisioned CommandCentral Responder capabilities
including standard Search forms, Citation forms and printed citation format.
MCSO Responsibilities
x
Assign SMEs to participate in the Motorola requests for information and provisioning process.
Page 112
x
Provide feedback on specific data field changes that differ from the originally agreed upon
configuration.
x
Provide all permutations of printer configurations that will be used to print the Citation.
x
Create and provide any agency-specific user training required to ensure users understand the
Citation processes and workflows.
x
Acknowledge CommandCentral Responder provisioning in accordance with the BPR
x
Acknowledge delivery of CommandCentral Responder capabilities (Search forms, Citation
forms, printed citation)
Motorola Deliverables
x
Demonstration of CommandCentral Responder in accordance with BPR and required forms
(Search, Citation, printed citation)
x
Certification of completed provisioning of CommandCentral Responder
6.15.3
AppArmor Provisioning/Configuration
Motorola will request access to MCSO’s Google and Apple app store accounts so that AppArmor may
submit the app under your organization’s account (this is important for downloads). AppArmor will also
require single sign-on (SSO) or a different integration (which can be executed concurrently to getting
access to Application store accounts and will likely be mostly executed by AppArmor). This also
involves SSO configuration.
Motorola will engage MCSO’s appropriate personnel/department to discuss the application aesthetics
with the AppArmor design team. They also incorporate decisions on the layout of the app as it pertains
to content and features. Once this stage is complete, the design team will begin work on the Marketing
Launch toolkit.
The Marketing Launch Tool includes:
x
Screenshots of the app
x
A suggested strategy in a PowerPoint document for the launch of your app, including best
practices, potential communication channels and more.
x
A suggested poster which features your app. The poster is left partially blank so MCSO can
populate it with your launch message.
x
A suggested "business card sized handout" which features MCSO’s app. It is also partially blank
so MCSO can populate it with your launch message.
x
High resolution screenshots of your app on all applicable platforms (e.g., iOS, Android)
x
A short 1-minute video meant to show off the basics of the app.
Motorola Responsibilities
x
Conduct review to discuss and document layout of AppArmor.
x
Develop the Marketing Launch toolkit.
MCSO Responsibilities
x
Identify resources to participate in the design of App Armor.
x
Review and approve the layout.
Page 113
Motorola Deliverable
x
AppArmor Design
x
AppArmor Marketing Launch Toolkit
6.15.4
10-21 Police Phone Agency and User Setup
MCSO’s email domain will become associated to an Agency ID when MCSO’s instance of the platform
is created. From there, Authorized Users with matching domains will be connected to the Agency ID
and included in the Agency’s users. Customer's users shall be provisioned under either Automatic or
Manual Assignment mode, as determined by MCSO at the point of configuration. Under Automatic
Assignment, Authorized Users with matching domains will be connected to the Agency ID and included
in the Agency’s users, up to the amount of purchased licenses. Under Manual Assignment, MCSO shall
select individual users to receive a license, up to the amount purchased.
Motorola Responsibilities
x
Create Customer instance of 10-21 Police Phone platform utilizing Customer provided details.
x
Validate agency domain and connect associated domains to Customer instance of platform.
x
Establish agency administrator, as designated by Customer, in Customer instance. If user exists
in 10-21, update status to admin. If new to 10-21, send new user temporary credentials to log in.
x
Provide instruction on user sign-up process.
x
Demonstrate ability for users to sign in to Customer instance of 10-21 Police Phone platform.
MCSO Responsibilities
x
Provide necessary customer details for onboarding
-
Agency name.
-
Email domain.
-
Associated domains.
-
Number of licenses purchased.
-
Auto/manual user provisioning.
-
Administrator contact details.
x
Designate an agency administrator.
x
New agency administrator signs into 10-21 CallManager to complete agency profile, including
dispatch telephone number, area code, timezone.
x
Agency administrator invites new users or administrators. Users sign up through 10-21 Police
Phone mobile app. Additional admins sign up through 10-21 CallManager site.
Note: New users with a domain matching the agency domain will automatically be associated to
MCSO’s instance.
Motorola Deliverable
x
Availability of MCSO Instance of 10-21 Police Phone platform
Page 114
6.16
System Validation Plans
6.16.1
Functional Validation
Functional Validation enables Motorola and MCSO to exercise the solutions, as provisioned, ensuring
readiness for Train-the-Trainer. Functional Validation activities are based on the Functional Validation
Plan (FVP) which includes a test case for each CAD/Mobile and Records function for which the system
has been provisioned. Functional Validation is performed following completion of provisioning. The
functional demonstration may not exercise all functions of the system, if identified as not being
applicable to MCSO’s operations as a result of provisioning or business process changes. The
functional validation will be conducted on-site over three consecutive days.
If there are exceptions or unsuccessful results as a result of performing the FVP, Motorola will
document the remedial action required in the Remediation Plan, i.e. Motorola providing clarification on
performing the validation steps, Motorola providing a bug fix, MCSO modifying provisioning information,
depending on the nature and priority of the exception or incomplete items. Once an exception is
resolved, Motorola will not perform a complete retest of the FVP but will identify test functions related to
test exceptions and perform those tests again to demonstrate compliance with functional requirements.
Following the FVP, Motorola will work with MCSO to develop the scripts for the Scenario Based
Validation.
Motorola Responsibilities
x
Update the Functional Validation Plan with the functional validation procedures for MCSO
approval.
x
Conduct functional validation according to the FVP.
x
Assign Priority Levels and develop a Remediation Plan for features and functions that do not
perform in accordance with the functional requirements.
x
Manage the Remediation Plan and coordinate Motorola and MCSO remediation actions.
x
Develop plan to retest functional exceptions to verify compliance with functional requirements.
x
Provide certification of successful completion of FVP.
x
Develop test cases for Scenario Based Validation.
MCSO Responsibilities
x
Ensure relevant resources are present for their specific area of responsibility.
x
Witness the functional demonstration and acknowledge its completion.
x
Participate in developing the Remediation Plan.
x
Coordinate, manage and complete MCSO remediation actions.
x
Acknowledge successful completion of the FVP.
Motorola Deliverable
x
Functional Validation Plan that includes all functional requirements.
x
Remediation Plan
x
Completed Functional Validation results.
Note – Motorola's provisioning responsibilities are considered complete at the conclusion of the FVP.
Page 115
6.16.2
Scenario Based Validation
Scenario based demonstration emulates typical operational workflows of installed and configured
solution components: CAD/Mobile, Records/Records Mobile, and CAD Mobile to Records Mobile;
confirming the transactional workflow from initiation through disposition. The system is exercised
throughout the delivery of the project by both Motorola and MCSO via provisioning, configuration, and
training activities. To solidify MCSO’s confidence in the system and prepare for Train the Trainer and
user training, Motorola will partner with MCSO in performing the scenarios ten (10) days after the FVP.
The Scenario Based Validation Plan is performed on-site over a three (3) day period. MCSO users will
continue to perform user testing for ten (10) business days after Motorola has completed it’.
The Scenario Based Validation Plan includes a list of the actions that are going to be taken, for
example, a traffic stop with location, license plate and comment or an incoming 9-1-1 call that is
entered, dispatched and units respond and clear, or a case report that includes collected property or
evidence, or that requires routing to an investigative unit for further action, or to a supervisor for
approval. The Plan will include the personas involved in the scenario (call-taker, dispatcher, field unit,
records technician, property and evidence technician, etc.) the command/function performed and the
expected and actual result.
If there are exceptions or unsuccessful results of the test scenarios, Motorola will document the
remedial action required, i.e. Motorola providing clarification on performing the validation steps,
Motorola providing a bug fix, MCSO modifying provisioning information, depending on the nature and
priority of the exception or incomplete items. Once an exception is resolved, Motorola will coordinate
with MCSO to perform the affected test scenario to demonstrate compliance with functional
requirements.
Motorola Responsibilities
x
Create the Scenario Based Validation Plan with guidance from MCSO, based on the functional
requirements matrix and in accordance with the BPR workbook/provisioning approach.
x
Perform scenario-based validation in accordance with the Scenario Based Validation Plan.
x
Document demonstration discrepancies in the Remediation as described in Section 6.16.1.
x
Manage the Remediation Plan and take Motorola remediation actions.
x
Perform test cases to demonstrate compliance with requirements following remediation.
x
Provide certification of successful completion of Scenario Based Validation Plan.
MCSO Responsibilities
x
Assist Motorola with creation of Scenario Based Validation plan and supply MCSO workflows
and objectives.
x
Provide resources to perform test scenarios with Motorola resources.
x
Review the demonstration scenarios and notify the Motorola PM of any items that require
discussion.
x
Coordinate and manage MCSO remediation actions.
x
Review and acknowledge successful completion of Scenario-Based Tests.
Motorola Deliverable
x
Scenario-based Demonstration Results Report that reflects the success or failure of each
element of the scenarios.
x
Remediation Plan (as applicable).
Page 116
Note - The Remediation Plan will identify the remediation action and the action owner (MCSO or Motorola).
Remediation steps may involve provisioning modifications, system configuration changes, and/or software version
update.
If MCSO test resources identify exceptions or unsuccessful results as a result of user acceptance
testing, they will document a description of how they performed the test and the expected and the
actual result, including any error messages received. Motorola will attempt to recreate the actions
performed to duplicate the error. If the error is verified, Motorola will document the remedial action
required, i.e. Motorola providing clarification on performing the validation steps, Motorola providing a
bug fix, MCSO modifying provisioning information, depending on the nature and priority of the
exception or incomplete items. Once an exception is resolved, Motorola will coordinate with MCSO to
demonstrate compliance with functional requirements. The County’s acknowledgement that Scenario
Based Validation and User Acceptance Testing has been completed will occur prior to the start of End
User Training.
6.17
Interfaces and Integration
The installation, configuration, and demonstration of interfaces will be an iterative series of activities
depending upon access to third-party systems. Interfaces will be installed and configured in accordance
with the System Description and interface-specific documentation. Integrated functionality between
Motorola-developed products will be completed through the software installation and provisioning
activities described herein. Integration activities that have specific requirements will be completed as
outlined in this SOW.
6.17.1
Interface Development
Development will be completed in accordance with the IFDs. MCSO is responsible for engaging third-
party vendors, as required, to facilitate connectivity and validation of the interfaces.
Motorola Responsibilities
x
Develop interfaces in accordance with the IFDs.
x
Establish connectivity to external and third-party systems.
x
Configure interfaces to support the functionality described in the IFDs .
x
Demonstrate the interface functions in accordance with the IFDs .
MCSO Responsibilities
x
Act as liaison between Motorola and third-party vendors or systems as required to establish
interface connectivity with the Motorola system.
x
Provide personnel proficient with and authorized to make changes to the network and third-party
systems to support Motorola’s interface installation efforts.
x
Provide network connectivity between PremierOne and third-party systems.
x
Acknowledge delivery of interface conforms to interface design.
NOTE - Unknown circumstances, requirements, and anomalies at the time of initial design can present difficulties
in interfacing to some third-party applications. These difficulties could result in a poorly performing or even a non-
functional interface. When information and access to systems is provided, Motorola will attempt to mitigate these
difficulties. If Motorola mitigation requires additional third-party integration, application upgrades, API upgrades,
and/or additional software licenses, those costs will need to be addressed through the change order provision of
the Agreement.
Page 117
Motorola Deliverables
x
Contracted Interfaces in accordance with Exhibit B-1
x
As-built IFDs
6.17.2
Interface Deployment
Connectivity will be established between the PremierOne production environment and the external
and/or third-party systems to which the contracted software will interface. Motorola will configure the
system to support each contracted interface as described in the interface-specific documentation.
MCSO is responsible for engaging third-party vendors, as required, to facilitate connectivity and testing
of the interfaces. Interface deployment tasks are performed on-site and remotely.
Once deployed in the production environment, interfaces will be configured and tested in the Disaster
Recovery and test environments (as described in the System Description).
Motorola Responsibilities
x
Establish connectivity to external and third-party systems.
x
Deploy interfaces to support the functionality described in the System Description and interface-
specific documentation discussed during the Interface Planning Session.
x
Validate that each interface can transmit and/or receive data in accordance with the System
Description and interface-specific documentation in Exhibit 6.
x
Configure and test interfaces in Disaster Recovery and test environments.
MCSO Responsibilities
x
Act as liaison between Motorola and third-party vendors or systems as required to establish
interface connectivity with the Motorola system.
x
Provide personnel proficient with and authorized to make changes to the network and third-party
systems to support Motorola’s interface installation efforts.
x
Provide network connectivity between PremierOne and the third-party systems.
x
Provide external interface connection demarcation points at locations agreed to by Motorola.
These locations shall normally be adjacent to the PremierOne equipment rack.
x
Provide external interface connection demarcation points in Disaster Recovery and test
environments.
Motorola Deliverables
x
Deployment of Contracted Interfaces in production, Disaster Recovery, and test environments.
6.17.3
Integration Activities
Proprietary processes enable the transfer and receipt of data between Motorola systems, as described
in the System Description. Integration activities are performed on-site and remotely.
Motorola Responsibilities
x
Establish and validate connectivity between the Motorola systems.
x
Validate that each system can transmit and/or receive data.
Page 118
MCSO Responsibilities
x
Provide personnel proficient with and authorized to make changes to the network and customer
owned third-party systems to support Motorola’s integration efforts.
x
Provide network connectivity between the Motorola systems.
6.17.4
Federal Uniform Crime Reporting (UCR)/Arizona Incident Based
Reporting System (NIBRS)
Motorola will deliver contracted software to support federal UCR and AZ NIBRS reporting requirements.
MCSO will continue to report UCR and NIBRS for the first three (3) months of PremierOne Records
production use.
Motorola Responsibilities
x
Deliver the UCR/NIBRS reporting capability or develop the state layer reporting capability.
x
Collaborate with MCSO to understand any provisioning parameters that may be, or are,
impacting UCR/NIBRS submission acceptance in the event of an initial failed submission.
x
Modify the state layer to account for any requirements necessary to be compliant with state
specific reporting requirements, as required by the State, and upon receipt of an official state
communication.
MCSO Responsibilities
x
Serve as the intermediary between Motorola and the State in clarifying reporting requirements
between state requirements and PremierOne Records state layer submission functionality.
x
Facilitate any required meetings between Motorola and the State.
x
Initiate UCR and NIBRS submissions to the State for the first three (3) months or until three (3)
months of submissions that meet accuracy criteria, if required.
x
Resolve any provisioning issues impacting State submission acceptance.
x
In the event of a failed submission:
-
Communicate the discrepancy in reporting requirements to the State.
-
Obtain an official state communication clearly articulating the State’s requirement.
-
Forward a copy of the official state communication to Motorola.
Motorola Deliverables
x
NIBRS Reporting that meets State/Federal submission requirements
6.17.5
Crash Report (Traffic Accident Reporting)
Motorola will deliver the Arizona Crash 01-2704A R02/20 and supplemental/ALISS AZCR17.xsd.
MCSO is responsible for providing an accident diagraming software/application, such as Easy Street.
Motorola Responsibilities
x
Provision Crash Reporting functionality.
x
Collaborate with MCSO to understand any provisioning parameters that may impact report
submission acceptance, in the event of an initial failed submission.
x
Modify the crash report to account for compliance with state specific reporting requirements, as
required by the State, and upon receipt of an official state communication.
Page 119
MCSO Responsibilities
x
Initiate a submission of the Crash Reports to the State.
x
Resolve any provisioning issues that affect State submission acceptance.
x
Serve as the intermediary between Motorola and the State in clarifying reporting requirements
between state requirements, MCSO requirements, and PremierOne Records Crash Report
submission functionality.
x
Obtain an official state communication clearly articulating the State’s requirement.
x
Forward a copy of the official state communication to Motorola.
x
Acknowledge successful submission of Crash Reports to the State.
Motorola Deliverables
x
State Crash Report that meets State submission requirements.
6.17.6
Interface Validation
The objective of Interface Validation is to verify that the installed interfaces perform in accordance with
the interface-specific documentation as reviewed during the Interface Planning Session. Interface
validation is performed on-site and remotely.
Motorola is not responsible for issues arising from lack of engagement of third-party and/or MCSO
resources to perform work required to enable, provision, or configure interface to a third-party system,
or troubleshooting any issues on MCSO’s third-party systems.
Interfaces that cannot be validated due to connectivity issues to external systems or the unavailability of
MCSO’s third-party system will be demonstrated to show that Motorola’s portion of an interface is
enabled to send and/or receive data that supports the user experience and functionality outlined in the
interface-specific documentation. In such cases, Motorola demonstrating the elements within Motorola’s
control will constitute a successful demonstration and completion of the demonstration task.
Motorola Responsibilities
x
Conduct Interface Validation demonstration.
x
Develop a Remediation Plan for anomalies that do not align with Motorola’s stated user
experience or functionality described in interface-specific documentation.
x
Manage the Remediation Plan and take Motorola remediation actions.
MCSO Responsibilities
x
Ensure required resources are present for their specific area of responsibility.
x
Provide a resource with access to the interfacing system to validate functionality.
x
Witness the execution of the demonstration and acknowledge successful completion.
x
Participate in the documentation of anomalies and work with Motorola to develop remediation
action(s).
x
Coordinate and manage MCSO remediation actions.
x
Approve Interface Validation Results and approve resolution of Remediation Plan (as
applicable)
Motorola Deliverable
x
Completed Interface Validation Results.
Page 120
x
Remediation Plan (as applicable).
6.18
Data Conversion
6.18.1
Transactional Data Conversion
Motorola will convert two years of legacy Hexagon CAD data and approximately three thousand (3000)
active cases from the legacy TraCS records management system that exist in a single legacy system,
respectively, to conform to the data structure of the PremierOne CAD and Records systems. A Data
Conversion Guide will be developed to document the field definitions and mapping. While Motorola is
responsible for converting the specified data, it is critical MCSO assigns a knowledgeable resource to
this activity who will remain engaged throughout the conversion process.
The legacy databases must be relational databases. Motorola must be able to link directly to the legacy
databases from MS SQL Server.
MCSO must conduct an analysis of their data in the legacy systems to identify duplicate data/records,
lost data, orphaned records, or records that haven’t been linked properly and resolve those issues prior
to extracting the data to be converted. Motorola does not provide any data clean up or manipulation of
the provided data and conducts a single, one-time, bulk load of legacy data.
MCSO will provide an environment within their network on which Motorola will configure data
conversion development tools. The environment requirements include the following:
x
Windows 2016 server 16 GB RAM, minimum 1 TB - 2 TB HDD (Depending on legacy database
backup size)
x
SQL 2017, 2016, or 2019 Server
x
SQL Management Studio. (depending on Customer's legacy database version, so the backup
can install successfully)
x
Visual Studio 2017 or Visual Studio 2013.
x
Notepad++ with the ability to use plugins.
x
Ability to connect to Premier One CAD and Records application servers
x
Permissions to install programs and add Services.
x
VPN access with ability to log in to the server at any time of the day
Data conversion routines will be executed in three phases:
x
Two Validation Test Loads - the first will contain up to one month of representative data and the
second will contain up to six months of representative data.
x
Bulk Load based on contracted delivery, less the delta agreed upon in phase three.
x
Delta Load - the delta of data between end of the bulk load and time of system Go Live. MCSO
must stop using their legacy system before this load. This Delta Load will consist of no more
than one month of data.
Upon notification of any anomalies of the two (2) Test Loads, resolve such anomalies within ten (10)
days, in accordance with the Project Schedule.
Motorola Responsibilities
x
Configure the data conversion development tools in MCSO-provided environment.
Page 121
x
Analyze data files with MCSO on-site to determine which tables contain the specified legacy
data and identify truncated, coded, or masked data.
x
Conduct a remote Data Conversion Preparation Workshop to identify where the information will
be positioned in PremierOne CAD and Records and develop documentation (Data Conversion
Guides).
x
Develop the conversion routine and execute the initial Validation Test Loads representative data
sets to identify and correct any issues.
x
Execute the second Validation Test Load on representative data sets and verify the conversion
results with MCSO.
x
If any anomalies still exist following the second Validation Test load, Motorola will resolve them
and run an additional Validation Test load to confirm all data is correctly mapped in PremierOne
CAD and PremierOne Records.
x
Perform the Bulk Loads in accordance with the Data Conversion Guides and results of
Validation Test Loads.
x
Perform the Delta Loads, which serves as the final data migration after the Live Cut, in
accordance with the Project Schedule.
x
Provide certification of completion of the Delta Load.
MCSO Responsibilities
x
Provide the data conversion environment.
x
Conduct an analysis of the data in the legacy system(s) to identify duplicate data/records, lost
data, orphaned records, or records that haven’t been linked properly and resolve those issues
prior to extracting the data to be converted.
x
Provide documentation of the legacy database and field mapping information of legacy systems
for Motorola’s understanding of MCSO’s data schema and relation.
x
Extract the data to be converted from the legacy databases.
x
Engage resources from legacy system vendors, if required, to provide information on legacy
database schema.
x
Participate in Data Conversion Preparation Workshop.
x
Review and approve the Data Conversion Guide within 10 calendar days of receipt.
x
Extract and make legacy data available in a SQL database for use in the data conversion
environment.
x
Review data after each Load to verify accuracy, in accordance with the Data Conversion Guide,
and notify Motorola within 2 days of any inaccuracies or discrepancies.
x
Provide acknowledgement and approval of completion of the Delta load.
Motorola Deliverables
x
Data Conversion Workshop.
x
Data Conversion Guide.
x
Converted Data per the Data Conversion Guide in accordance with the Project Schedule.
Page 122
6.18.2
Convert on Demand Tool
The Convert on Demand (CoD) tool provides MCSO the ability to configure and import documents from
legacy Records Management Systems (RMS) into PremierOne Records on an as-needed basis. The
CoD Tool only supports T-SQL relational databases for storing legacy information.
The database in which the legacy data resides will remain in an archived database instance, and when
the need arises, data is brought into PremierOne. The CoD tool can convert one record at a time or
perform a bulk import into PremierOne systems. The tool uses internal PremierOne Record
components to maintain data integrity of converted records in PremierOne Records.
The CoD tool also has a feature that enables users to compare legacy data in the PremierOne Records
format before deciding to convert specific records to PremierOne Records. This feature helps users to
validate data mapping between the legacy data and will present how it will appear in PremierOne
Records.
The CoD Tool Workshop is a 3-day, on-site workshop where Motorola will advise MCSO in the use of
the Tool and assist MCSO in the development of configuration documents/files or ETL scripts. This
workshop will be conducted after PremierOne Records has been provisioned, including the
development of new modules or modification of existing modules.
Motorola Responsibilities
x
Install the CoD tool on the PremierOne Records server.
x
Coordinating and conducting the CoD Tool Workshop, which will occur after ACT module
development and Records Provisioning has been completed.
MCSO Responsibilities
x
Participate in the CoD Tool Workshop.
x
Following the CoD Tool Workshop, create the required configuration documents/files.
Motorola Deliverables
x
Convert on Demand Tool.
6.19
Advanced Configuration Tool (ACT)
The Advanced Configuration Tool (ACT) is an application development tool designed to provide skilled
PremierOne Records resources the ability to modify and develop records functionality. Using ACT,
trained resources can design the navigation flow for modules and develop application components,
such as search fields, data grids, default views, and in-module reports. ACT is also used to modify and
develop modules in order to provide functionality to support future MCSO specific business processes.
Unlike configuration or provisioning, development done in ACT creates additional database structures
and application code.
6.19.1
ACT Workshop
Following the delivery of MCSO Specific Modules, Motorola remotely conducts the ACT Workshop to
enable MCSO to support future MCSO specific business processes. The skilled resource will be
familiar with relational database logic, data types, and understand data theory. The skilled resource
must understand the agency's end-to-end business operation, anticipate specific reporting needs, and
envision the required inputs to support the desired reporting outputs.
Page 123
Motorola Responsibilities
x
Provide access to the Motorola provided web-based learning environment 5 business days prior
to the Workshop start.
x
Facilitate ACT Workshop.
MCSO Responsibilities
x
Confirm access to the Motorola provided web-based learning environment no later than 2
business days prior to the Workshop start.
x
Attend the ACT Workshop.
Note - ACT changes made to the system outside of those captured in the BPR Workbook prior to Go Live will be
reviewed with the Motorola Application Specialist. Failure to do so prior to making changes using ACT could
negatively impact the system and potentially result in a project delay.
Motorola Deliverable
x
Advanced Configuration Tool.
x
Advanced Configuration Tool Workshop.
6.19.2
Rich Text Format (RTF) Building Workshop
RTF Building Workshop will be conducted after delivery of the ACT Workshop has concluded;
attendees must have also been part of the ACT Workshop. Motorola will guide MCSO in the creation or
modification of RTFs within the PremierOne Records system, giving MCSO the ability to configure
printable outputs to meet their needs. This workshop is conducted remotely.
Motorola Responsibilities
x
Provide access to the Motorola provided web-based learning environment 5 business days prior
to the Workshop start.
x
Facilitate the RTF Building Workshop.
MCSO Responsibilities
x
Confirm attendees have completed ACT Workshop prior to the RTF Building Workshop.
x
Confirm access to the Motorola provided web-based learning environment no later than 2
business days prior to the Workshop start.
x
Attend the RTF Building workshop.
6.19.3
RDLC Building Workshop
RDLC Building Workshop will only be conducted after delivery of the ACT Workshop and SSRS Workshop(s)
have concluded; attendees must have also been part of the ACT Workshop and SSRS Workshop(s). Motorola will
guide the County in the creation or modification of RDLCs within the PremierOne Records system, giving the
County the ability to create overview and summary reports on data contained within modules, along with the
ability to create printed forms from modules within PremierOne Records.
Motorola Responsibilities
x
Provide access to the Motorola provided web-based learning environment 5 business days prior to the
Workshop start.
x
Facilitate the RDLC Building Workshop.
Page 124
MCSO Responsibilities
x
Confirm attendees have completed ACT and SSRS Workshops prior to the RDLC Building Workshop.
x
Confirm access to the Motorola provided web based learning environment no later than 2 business days
prior to the Workshop start - use of 2 monitors is strongly recommended for each attendee of the
workshop.
x
Attend the RDLC Building Workshop.
6.20
Reports and Dashboards
6.20.1
Reports
Motorola will deliver the standard reports library and the custom reports listed in Exhibit B. A list of the
standard reports delivered with the installed version will be provided upon request. Upon receipt of the
standard reports library, any further changes will be addressed per the change order provision of the
Agreement.
Motorola will remotely review the standard reports library and introduce the functionality available within
SQL Server Reporting Service (SSRS) through the on-site SSRS Workshop (one each for CAD and
Records). The Workshop will be conducted in accordance with the Training Plan and for Records, will
take place after the conclusion of the ACT Workshop. Attendees must also have participated in the
ACT Workshop.
Motorola Responsibilities
x
Deliver standard reports library and review with MCSO.
x
Provide access to the Motorola provided web-based learning environment 5 business days prior
to the Workshop start.
x
Review all elements of custom reports listed in Exhibit B and provide draft/mock-up formats.
x
Develop custom reports listed in Exhibit B.
x
Deliver and demonstrate custom reports to MCSO to validate data elements in draft/mock-ups
are correctly populated.
x
Address any anomalies identified by MCSO.
x
Facilitate the on-site SSRS Workshop.
MCSO Responsibilities
x
Confirm attendees in the Records SSRS Workshop have participated in the ACT Workshop.
x
Confirm access to the Motorola provided web-based learning environment no later than 2
business days prior to the Workshop start.
x
Review draft/mock-up copies of custom reports.
x
Acknowledge/approve custom report drafts/mock-ups.
x
Review custom reports and advise of any anomalies.
x
Acknowledge acceptance of custom reports.
x
Attend the SSRS Workshop.
Motorola Deliverables
x
Standard reports library
Page 125
x
CAD and Records SSRS Workshops
x
Custom reports
6.20.2
Dashboards
The objective of this task is to introduce the functionality available via Intelligent Data Discovery (IDD). IDD
Workshops will be remotely conducted in accordance with the Training Plan. For CAD: Motorola will review the
three standard CAD dashboards and the View-Only CAD IDD Bundle for a single agency.
x
Three (3) Tailored Standard Dashboards
-
Roll Call Briefing Dashboard
-
Intelligent Resource Deployment Dashboard
-
COMPSTAT Dashboard
x
View Only CAD IDD bundle
-
Unit Status
-
Unit History
-
Map
-
Incident Search
-
Drill-through to Incident Details and Officer Activity Reports
x
Three (3) days of PremierOne CAD Intelligent Data Discovery (IDD) Workshop, after completion
of requirements.
x
Two (2) Customer Defined Dashboards (defined and scoped during the IDD Workshop and
limited to data existing in the system CAD dataset, built as a remote effort by Motorola).
For Records: Motorola will review the three standard dashboards for a single agency.
x
Three (3) Tailored Standard Dashboards
-
Master Index Search Dashboard
-
Records CompStat Dashboard
-
Records Major Crimes Dashboard
x
Three (3) days of PremierOne Records Intelligent Data Discovery (IDD) Workshop, after
completion of requirements.
x
Two (2) Customer Defined Dashboards (defined and scoped during the IDD Workshop and
limited to data existing in the system Records dataset, built as a remote effort by Motorola).
This effort will utilize MCSO’s existing Microsoft SQL Server licenses and Business Intelligence tools to
configure dashboards and data views using data available from the PremierOne environment.
Motorola Responsibilities
x
Provide the IDD Workbook 10 business days prior to the start of overview/consultation for
MCSO to complete.
x
Remotely conduct the Workshop over three days to review standard dashboards and define and
document requirements for two customer-defined dashboards.
x
Install standard dashboards.
x
Create the two customer-defined dashboards based on a list of 50 graphical elements (maps,
charts, gauges, etc.) per PremierOne Application (CAD/Mobile and Records).
x
Install customer-defined dashboards.
Page 126
MCSO Responsibilities
x
Complete the IDD Workbook 5 business days prior to the start of the overview/consultation.
x
Perform data entry (incident creation, dispatch, disposition) to confirm sufficient data exists for
reporting.
x
Define requirements for MCSO-defined dashboards utilizing the IDD Workbook.
x
Assign resource(s) that have received the CAD SSRS Reporting training to participate in the
review of the dashboards.
x
Assign resource(s) that have received the Records SSRS Reporting training to participate in the
initial dashboard consultation and review delivery of the dashboards.
Motorola Deliverable
x
Standard Dashboards and (2) MCSO defined dashboards for both CAD and Records in
conformance with the defined graphical elements defined during the workshop
6.21
System Training
The objective of this task is to prepare for and deliver the contracted training. Motorola training consists
of both computer-based (online) and instructor-led (on-site or remote). Training delivery methods, i.e.
on-site, virtually/remotely, on-line, vary depending on course content. Training is delivered in
accordance with the Training Plan.
Application training (CAD, Records, Mobile) occurs after Functional Validation, Scenario Based
Validation and Interface Validation are completed.
Following the completion of each Train the Trainer course (CAD, Records, Mobile), the Application
Engineer will work with the participants of the courses to assist in the development of end-user
curriculum.
6.21.1
Learning eXperience Portal (LXP Online Training)
Training is made available to MCSO, in part, via Motorola’s LXP. This subscription service provides
your users with continual access to Motorola’s library of online learning content and allows your users
the benefit of learning at times convenient to them. Access to LXP is available as long as an active
Maintenance and Support Agreement is in effect. Courses delivered or supplemented by LXP content
are described in the Training Plan.
Motorola Responsibilities
x
Configure a MCSO specific portal view.
x
Create learner access account to the portal for each username provided by MCSO.
x
Provide instruction to MCSO LXP Administrator on building groups.
MCSO Responsibilities
x
Provide Motorola with names (first and last) and email addresses for each learner.
x
Complete LXP Administrator training.
x
Advise users of the availability of the LXP.
x
Build groups as desired.
Page 127
Motorola Deliverable
x
LXP Administrator access and instruction
6.21.2
Instructor-Led Training (On-site and/or Remote)
Prior to the start of Train the Trainer courses, system provisioning and functional validation will be
completed. Scenario based validation and user acceptance testing will be completed prior to End User
training.
Motorola Responsibilities
x
Deliver User Guides and training materials in electronic format.
x
Perform training in accordance with the Training Plan.
x
Provide MCSO with training Attendance Rosters and summarize any pertinent observations that
may impact end user training.
x
Provide up to forty (40) hours of support following Train the Trainer courses to assist with end-
user curriculum.
MCSO Responsibilities
x
Supply classroom(s) based on the requirements listed in the Training Plan.
x
Designate training representatives who will work with the Motorola trainers in the development
and delivery of training.
x
Facilitate training of all MCSO end users in accordance with MCSO’s training delivery plan.
x
Update user guides and training materials as desired/required for end-user training.
Motorola Deliverables
x
Electronic versions of User Guides and Training Materials.
x
Attendance Rosters.
6.22
AppArmor Deployment and Testing
AppArmor will submit the app to the appropriate App stores. The app will be under review with Apple
and Google for 1-5 business days.
Training and testing on the system will occur during a soft launch period prior to deployment. In addition
to training provided to County trainers, AppArmor provides detailed documentation on dispatcher roles
and responsibilities, detailed documentation that identifies key features and functions and a video
library of resources.
Motorola Responsibilities
x
Submit AppArmor for review by the App stores (Apple and Google).
x
Conduct training to County trainers. Training can be recorded for future use.
x
Provide access to documentation and training resources.
x
Provide guidance on utilizing the Marketing Launch Kit to publicize the launch of AppArmor.
x
Provide assistance as needed for users to download the AppArmor app.
Page 128
MCSO Responsibilities
x
Facilitate download of AppArmor on County devices.
x
Identify City personnel to participate in AppArmor training.
Motorola Deliverables
x
AppArmor documentation
x
Video library of resources
x
AppArmor available for production use
6.23
System Go Live
6.23.1
Go Live Planning
Motorola will provide support of MCSO’s efforts with commencing live operation use of the system.
Motorola resources are supplemental to MCSO resources and provide support to MCSO trainers and
subject matter experts. MCSO Core Team, which consists of the County's application administrators
and trainers, is the first line of support to end users in the transition of live operations from MCSO’s
legacy system to the Motorola system. Motorola will work with MCSO to provide a Go Live Plan.
Examples of what is in this plan can include:
x
Motorola and MCSO resources and staffing.
x
Pre-Go Live tasks/activities to be performed leading up to Go Live.
x
Readiness review meetings.
x
Issue reporting and escalation processes.
x
Contingency/roll-back plans.
x
Go Live tasks and responsibilities during Go Live
Motorola Responsibilities
x
Facilitate meetings with MCSO staff to review the Go Live Plan.
x
Finalize the Go Live Plan.
MCSO Responsibilities
x
Coordinate the participation of MCSO’s technical and operational staff in Go Live planning and
review of the Go Live Plan.
x
Acknowledge and approve the Go Live Plan.
Motorola Deliverable
x
Go Live Plan.
6.23.1.1
Motorola Support Engagement
As part of Go Live planning, the Motorola PM will complete a System Configuration workbook
consisting of MCSO contact information and information required for remote access to the system.
Motorola will schedule a remote Support Engagement meeting between the PM, MCSO Support
Manager (CSM), Focal Support Technician and MCSO’s project team representatives no later than 30
Page 129
days before the identified Go Live date. The CSM will review MCSO Customer Support Plan in Exhibit I
with MCSO, including the process for obtaining support and contact information.
Motorola Responsibilities
x
Facilitate the Support Engagement Meeting between MCSO and the Motorola Support
organization.
MCSO Responsibilities
x
Identify authorized MCSO representatives to contact Motorola Support
x
System Configuration Workbook, in electronic format.
6.23.1.2
Go Live
In accordance with the Go Live Plan, Motorola and MCSO will begin transitioning MCSO from their
legacy system to live operation use of the Motorola system. Motorola will provide on-site support as
back up to MCSO at a single site per product in accordance with the Go Live Plan. If resources are
desired at multiple communications centers or locations, it will be addressed via the change order
provision of the Agreement. The Go Live transitions MCSO from the implementation phase of the
Agreement to the support phase under the governance of the Motorola Support organization. The CAD
and Records Application Administrators will support the go-live activities on-site with Motorola’s team.
Motorola Responsibilities
x
Work with MCSO to schedule the date and time for the Go Live.
x
Execute the Go Live Plan.
x
Provide on-site resources as specified in the Go Live Plan to support MCSO’s Core Team.
Unless otherwise documented in the Go Live Plan, support will be provided in accordance with
the following:
-
CAD and Mobile – 24-hour coverage for seventy-two (72) hours followed by 16-hours per
day for four (4) calendar days and 8 hours per day (8am – 5pm) for an additional seven (7)
days.
-
Records - 24-hours per day for three (3) days followed by 16-hour coverage for the next four
calendar days and 8 hours per day for the following seven (7) days.
x
Document and develop remediation plan for any residual issues for County approval.
x
Transition to Customer Support Organization in accordance with the Go-Live Plan and
Maintenance and Support Agreement.
Motorola CAD Resource Go Live Coverage
Resource Type
# of Resources
Coverage
Application Specialist
2-3
On-site, 24-hour coverage for first 72 hours
Application Specialist
2
On-site, 16-hour coverage for the next four (4) consecutive
days (to be scheduled to cover portions of all shifts, i.e. 10a-
6p, 6p-2a)
Application Specialist
1
On-site coverage for eight (8) hours per day for the next seven
(7) consecutive days (schedule to be mutually agreed upon)
Remote CAD Application
Administrator
1
On-site coverage 8-5, or as mutually agreed upon for the first
fourteen (14 days)
Page 130
Resource Type
# of Resources
Coverage
Solution Architects
2
24-hour coverage for first 72 hours and, if required to address
a Priority Level 1 issue, until such issue is resolved
Project Management
2
On-site, 16-hour coverage for the first seven (7) days, then
TBD
Motorola Records Resource Go Live Coverage
Resource Type
# of Resources
Coverage
Application Specialist
2-3
On-site, 24-hour coverage for first 72 hours
Application Specialist
2
On-site, 16-hour coverage for the next four (4) consecutive
days (to be scheduled to cover portions of all shifts, i.e. 10a-
6p, 6p-2a)
Application Specialist
1
On-site coverage for eight (8) hours per day for the next
consecutive seven (7) days (schedule to be mutually agreed
upon)
Remote Records
Application Administrator
1
On-site coverage 8-5, or as mutually agreed upon for the first
fourteen (14) days
Solution Architects
2
24-hour coverage for first 72 hours and, if required to address
a Priority Level 1 issue, until such issue is resolved
Project Management
2
On-site, 16-hour coverage for the first seven (7) days, then
TBD
Page 131
MCSO Responsibilities
x
MCSO Core Team scheduling for Go Live activities.
x
Manage Go Live activities.
x
MCSO to educate Core Team on methods and when to engage Motorola during Go Live.
x
Review and approve the remediation plan for residual Go Live issues.
Motorola Deliverables
x
On-Site Go Live Support.
x
Remediation Plan that identifies each residual error, the expected resolution and time frame for
resolution.
x
Transition to Customer Support Organization
6.23.2
45-Day Reliability Period
A 45-Day Reliability Period for each primary system component (defined as CAD/Mobile and
Records/Records Mobile) will be supported. The Reliability Period commences at Go Live upon the
initiation of the first incident in a production mode for CAD or the first record creation in Records,
whichever occurs first. Besides the on-site Go Live coverage, Motorola resources are not on-site during
this period but they will be available to respond to error conditions, if/as required.
During this period, the system will perform without any Priority Level 1 incidents as defined in the
Maintenance and Support Agreement. If a Priority Level 1 incident occurs, the Reliability Period will
stop until the issue is corrected, then restart on Day 1. For Priority Level 2 issues (not critical), the
reliability period will be stopped and if corrected within 24 hours, the period will resume from the day it
was stopped. If a Priority Level 2 (not critical) issue requires more than 24 hours to resolve, the
reliability period will start over from Day 1.
If one primary subsystem goes live before the other, the Reliability Period will start upon the later
cutover. During this period, the system will operate and perform as provisioned and configured, based
on the MCSO’s provisioning methodology.
During the Reliability Period, MCSO shall maintain a log of system problems or desired changes and
work with Motorola in correcting such problems according to the terms of the Maintenance and Support
Agreement. MCSO shall immediately notify Motorola by telephone if the system becomes unavailable.
Upon successful completion of the 45-day Reliability Period, Motorola and MCSO shall acknowledge
that the Reliability Period is complete.
6.24
Project Closure
Following the Go Live, successful completion of the Reliability Period and completion of Motorola’s
responsibilities and deliverables described in this SOW and County’s written acknowledgement of the
same, Motorola and the County will certify in writing that the service delivery is complete and the
implementation phase is formally closed.
The system is transitioned to the support phase of the Agreement per the terms and conditions of the
Maintenance and Support Agreement.
Page 132
6.24.1
Documentation
As part of project completion, Motorola will validate MCSO’s receipt of electronic copies of the following
documentation:
x
User Guides (for the primary products), in electronic format.
x
BPR Workbook(s) for each contracted Product Category.
x
System Administration Guide, in electronic format.
x
System Configuration Workbook, in electronic format.
x
As-Built System Design Documentation, in electronic format.
x
As-Built System documentation is also archived with the System Support Center along with
customer information and access procedures to facilitate efficient response and resolution of
any reported system issues.
6.25
Organizational Change Management (OCM)
Motorola will provide OCM services to assess MCSO’s readiness for change and develop a systematic
approach, body of knowledge, training tools and materials to facilitate a successful transition to the new
systems.
Even small changes to established practices bring challenges. Change introduces ambiguity, which
results in anxiety and stress. The more complex and expansive the change, the greater the level of
potential disruption, and the higher the level of anxiety and resistance to the change.
A CAD, Mobile and Records replacement project is one of the most complex and disruptive changes an
agency can undertake, upending worn habits and forcing personnel to adopt new ways of working.
Through the change process, prioritizing people must take precedence. Without clearly understanding
MCSO’s willingness and ability to change, and then defining a change management approach that
provides the necessary capabilities, the project is put at risk.
Motorola will employ the CHANGE Model framework which consists of six steps that occur over the
lifecycle of the project, each requiring accomplishment of distinct tasks. Tasks related to one step may
overlap and inform
others.
Motorola’s role in the OCM process is primarily one of guidance and facilitation, responsible for
transferring capabilities to MCSO stakeholders leading the change.
The Motorola OCM leader will engage during the planning phases of the project to review the overall
steps and methodology with the MCSO team. The software (“OCM software”) the OCM leader will use
to support end-to-end OCM planning, delivery, and dashboards and reporting will be introduced. The
OCM leader populates the OCM software throughout the process to produce dashboards and reports.
Agency users will have the ability to enter information relative to their role (functional change impacts
for example). The OCM software will be available through the six steps of the CHANGE model and
available with view-only access for up to six (6) months post-engagement, or as mutually agreed to.
Page 133
It is essential to project success that champions of the project are designated at each level of the
affected departments’ hierarchy. These Transformation Leads will serve as representatives on the
change management team, providing both input and gathering feedback for the duration of the project
lifecycle. As such, prospective Transformation Leads must be qualified for the role, and they must be
given the resources (in time and attention) to participate fully.
Ideal candidates for the Transformation Lead role include a varied selection of senior operational
decision makers, such as dispatch supervisors, senior call takers/dispatchers, and field training officers.
As participants on the change management team, their efforts will prove invaluable to project success.
6.25.1
Step 1: Challenge the Current State
The first step involves a thorough evaluation of the current state of MCSO’s departments.
Understanding the present operational processes, as well as the perspectives of various stakeholders,
is essential for successful change management. The goal is to identify key areas of potential resistance
and opportunities for improvement that can help shape an effective change management strategy.
The aim of "Challenge the Current State" is to lay the groundwork for an effective change management
plan. It will identify key issues and set the stage for the development of strategies that address these
issues, helping to ensure that the transition to the new CAD, Mobile and Records Management system
is as smooth and successful as possible.
Motorola Responsibilities
x
Participate on-site in the Project Planning and Kickoff meeting to introduce the OCM
methodology and approach.
x
Engage with executive sponsors and key stakeholder representatives in an on-site meeting to
further understand the specific needs, concerns, and expectations of all stakeholders. This
session will help in contextualizing the reason for the change, thereby improving buy-in from all
parties involved.
x
Facilitate an on-site in-depth impact analysis of the existing workflows, systems, and processes.
This analysis will provide an understanding of how the new CAD, Mobile and Records
Management systems will disrupt current operations and identify any critical factors that need to
be incorporated into the change management plan.
x
Conduct a comprehensive change readiness audit to assess the department's readiness for the
proposed change. This audit will include the evaluation of the staff's preparedness, the
organization's culture towards change, and current capabilities to manage change effectively.
x
Introduce the OCM software and demonstrate sample reports and dashboards that will be
developed,
x
Provision MCSO team members and stakeholders with access to the OCM software.
x
Develop the Change Management Dashboard and update it regularly to reflect progress along
project timeline, risks, and milestones.
MCSO Responsibilities
x
Ensure the availability and participation of executive sponsors and stakeholder representatives
for the on-site sessions.
x
Provide relevant departmental data and personnel for the Initial Impact Analysis.
x
Participate in the Change Readiness Audit, including completing questionnaires and interviews.
x
Review Deliverables and acknowledge/approve them or provide feedback for Motorola to
update and resubmit.
Page 134
Motorola Deliverables
x
Kickoff slide-deck that explains methodology and approach.
x
OCM software
x
A detailed report of the Initial Impact Analysis, highlighting critical factors to be considered for
the change management plan.
x
A Change Readiness Audit report that outlines the current readiness state of the department,
identifies areas of weaknesses, and includes a plan for addressing these areas.
x
A Change Readiness Checklist to provide guidance for the departments throughout the change
process.
x
Change Management Dashboard.
6.25.2
Step 2: Harmonize and Align Leadership
This phase focuses on establishing and aligning leadership with the change. The goal of this phase is
to assemble a strong leadership team that will guide and manage the change process, effectively
engaging stakeholders and overcoming barriers to change.
Motorola Responsibilities
x
Identify the empowered sponsors of the change who will provide leadership, resources, and
decision-making capacity throughout the process.
x
Work with MCSO to identify potential Transformation Leads to serve on the Change
Management Team. These individuals will drive the change at various levels of the organization.
They will be assessed based on their position power, leadership skills, credibility, and other
factors.
x
Define Project Success: Sponsors and Transformation Leads will define their view of project
success, setting clear objectives and measures for the change initiative during an on-site
meeting.
x
Review potential barriers to project success and develop counter-strategies.
x
Assemble a dedicated change management team and develop a charter document that outlines
the team's structure, mission, objectives, roles, and responsibilities.
x
Collaborate with the leadership team to create a unifying vision statement for the change
initiative, which provides clear benefits and aligns with the overall strategic vision of the
organization.
x
Conduct a stakeholder analysis to understand their interests, potential impact, and
communication needs.
MCSO Responsibilities
x
Participate in sessions to identify and assess Transformation Leads.
x
Assist in defining the project's success parameters.
x
Participate in brainstorming sessions for the creation of the vision statement with
Transformation Leads (and others at MCSO’s discretion)
x
Collaborate on the development of the change management team and charter document.
x
Provide necessary information for the stakeholder analysis.
Page 135
Motorola Deliverables
x
A "VIEW for Success" document outlining the characteristics of an effective Transformation
Lead.
x
A Vision Clarity Chart providing the definition of Project Success and a clear and consistent
vision for the change.
x
Change Leadership Guidelines to help direct the actions and decisions of the change leadership
team.
x
A Change Management Team structure with clear roles and responsibilities, along with a
charter document.
x
A Change Management Dashboard (CM Drivers) to track the change management process.
x
A detailed Stakeholder Analysis report.
6.25.3
Step 3: Activate Commitment
This phase centers on mobilizing the organization towards the desired change, overcoming resistance,
and fostering commitment.
Motorola Responsibilities
x
Categorize stakeholders into respective phases of the change journey, taking into consideration
their influence, interest, and expected level of commitment to change.
x
Develop a tailored plan for each stakeholder group to guide them through their respective phase
and level of commitment to change.
x
Conduct on-site sessions to uncover any resistance to change, understand the underlying
reasons, and strategize on how best to address them.
x
Leveraging the SHIFT model, we will apply strategic interventions to overcome resistance and
drive commitment to the proposed change.
x
Develop a Commitment Chart and update it to reflect progression of stakeholder commitment to
change as mutually agreed.
MCSO Responsibilities
x
Provide necessary information to categorize stakeholders into respective phases of change.
x
Participate in meetings to define the stakeholder management plan.
x
Engage in discussions to explore and understand resistance to change within the department.
x
Collaborate in implementing strategic interventions to overcome resistance.
Motorola Deliverables
x
A Commitment Chart to visualize the progression of stakeholder commitment to the change.
x
A Force Field Analysis report that outlines the forces that either drive or hinder change.
x
A detailed SHIFT model plan for overcoming resistance to change.
6.25.4
Step 4: Nurture and Formalize a Design
The "Nurture and Formalize a Design" phase involves solidifying the proposed change plans and
preparing for their implementation while proactively addressing potential risks and communication
needs. This phase is critical to help solidify our approach towards the change while addressing
Page 136
potential risks and setting up a comprehensive communication strategy to ensure MCSO is fully
prepared to execute the change management plan and effectively manage the implementation process.
Motorola Responsibilities
x
Identify the key human elements and process changes that are critical to the success of the
change initiative.
x
Conduct an on-site meeting to finalize the change management plan, addressing any potential
obstacles to its successful implementation using insights gathered from previous stages and
taking into account identified people and process considerations.
x
Perform a comprehensive risk assessment related to the change management plan to identify,
quantify, and plan for potential risks.
x
Assess the communication needs of different stakeholders and define a comprehensive
communication strategy to ensure clarity and consensus.
MCSO Responsibilities
x
Participate in identifying key people and process considerations.
x
Provide necessary feedback to finalize the change management plan.
x
Cooperate in risk assessment activities.
x
Help identify communication needs specific to various stakeholder groups.
Motorola Deliverables
x
A detailed report identifying key people and process considerations.
x
A finalized Change Management Plan.
x
A comprehensive risk assessment report.
x
A tailored Communication Strategy, which includes guidelines for effective communication
throughout the change process. Elements of the Marketing Campaign will be included in the
Communications Strategy.
6.25.5
Step 5: Guide Implementation
"Guide Implementation," addresses building support for the change solution, identifying and executing
quick wins, sustaining momentum, and encouraging the integration of change into the organization’s
culture.
Motorola Responsibilities
x
Provide guidance, support and task oversight to ensure activities outlined in change
management plan are carried out within expected timelines and the change process achieves
desired results. Motorola and MCSO will mutually agree to on-site presence, as required.
x
Provide guidance and support to MCSO to incorporate changes to the change management
plan if required during implementation.
x
Define short-term gains to be accomplished early in implementation phase that are measurable
and visible to the organization; are clear “wins” for the organization; and are part of the change
implementation.
x
Facilitate the use of communication channels developed in Step 4 to publicize and celebrate
progress; debunk rumors and neutralize or remove obstacles early.
x
Help identify factors that will prevent stakeholders from embracing and sustaining change, and
offer opportunities for those impacted by change to develop resilience factors.
Page 137
MCSO Responsibilities
x
Implement change management plan according to expected timeline and seek support from
Motorola if changes to the plan are identified during implementation.
x
Work with Motorola to define short-term gains and plan to achieve them.
x
Share regular communication across organization related to change project.
x
Manage consequences of change fatigue and potential project delays.
Motorola Deliverables
x
Ongoing guidance, support and task oversight according to change management plan.
6.25.6
Step 6: Evaluate and Institutionalize the Change
The "Evaluate and Institutionalize Change” phase involves making sure the change sticks. During this
phase we will continue to keep everyone involved in the process by evaluating the change effort,
reporting on successes, and implementing a monitoring plan. This phase also involves adjusting all
documented policies and procedures to support the new system, along with recognizing and disbanding
the change management team. This phase helps ensure the changes stick and how to monitor and
adjust to the change moving forward. Finally, teams evaluate how the change process went, and
recognize the work of the change management team and change sponsors.
Motorola Responsibilities
x
Work with MCSO to identify metrics used to evaluate ongoing state of project and develop
remedies for addressing potential roadblocks, then assign party for reporting on it regularly.
x
Help assess success of change, quantifying costs, ROI, interruptions caused by project,
commitment across hierarchy and responsiveness to problems that arose during project.
x
Recognize and Disband Change Management Team: Formally recognize the change
management team and change sponsors. Ask team to document best practices and results.
Encourage team members to stay involved, informally monitor and remain informed of the
impact of change.
MCSO Responsibilities
x
Identify metrics used to evaluate ongoing success of project.
x
Assign person responsible for reporting on project regularly.
x
Review and revise policy and procedures to accommodate any changes made to operations as
a result of project.
x
Document best practices and results
x
Assist in assessment of project success.
x
Formally recognize change management team with on-site team meetings, email
communication and other methods of public recognition.
Motorola Deliverables
x
Follow-up plan development focusing on key transition areas.
x
Evaluating the Change Process checklist, including rating success areas, lessons learned, and
reviewing best practices.
x
Process by which to close out Change Management Team and celebrate successes.
Page 138
6.26
Optionally Available Cybersecurity Services
(Managed Detection and Response)
If these options, which are available at an additional price, are added to the Agreement, the following
CyberSecurity Services will be provided/delivered.
Motorola ActiveEyeSM Managed Detection and Response provides endpoint monitoring by
experienced, specialized cybersecurity analysts with extensive experience working with PremierOneט
mission-critical networks.
The following elements are available as part of the Managed Security Service:
x
ActiveEye Security Management Platform.
-
Applicable service modules. These modules use Service Connectors to integrate specific
network components into the ActiveEye monitoring platform and SOC services.
-
Technical Support for troubleshooting.
x
Security Operations Center (SOC) monitoring and support.
x
Monitoring and response for applicable ActiveEye service modules.
In order to establish initial expectations for deployment, Motorola will work with MCSO to help you
understand the impact of introducing a new solution and your preparedness for the implementation and
support of ActiveEye Managed Detection and Response.
Motorola Responsibilities
x
Schedule a service kick-off meeting with MCSO and provide information-gathering documents
to MCSO. The kick-off meeting will be conducted remotely at the earliest mutually available
opportunity.
x
Provide detailed requirements regarding Customer infrastructure preparation actions within one
week of the kick-off meeting.
x
Provision tools in accordance with the requirements of this Service, and consistent with
information gathered in earlier phases. Motorola will also provide required Customer
deployment actions within one-week of the completion of all infrastructure readiness tasks.
x
Collaborate with MCSO’s Primary Point of Contact (POC) to define the timing, confirm scope,
and speak through any related details related to interview scheduling with key stakeholders,
relevant NIST Cyber Security Framework (CSF) documents, coordination of project status
meeting and milestone schedule, travel, and/or escalation protocol required for the kick-off of
the project.
MCSO Responsibilities
x
Attend the kick-off meeting and complete information gathering documents as quickly and
accurately as possible.
x
Accomplish all infrastructure preparation tasks as quickly as possible.
x
Deploy tools, as applicable, in their environment, in accordance with provided requirements.
Note - Failure to complete the actions above will delay the accomplishment of the implementation.
Page 139
6.26.1
ActiveEye Security Management Platform
The ActiveEye Security Platform will collect, analyze, and automate the investigation of IT and security
activity. The web-based ActiveEye portal enables MCSO to view threat insights, perform investigations,
create security reports, and view threat advisories. In addition, MCSO will be able to use the ActiveEye
portal to manage notification settings and communications with the Motorola SOC.
The ActiveEye platform collects data directly to its cloud service interface. Motorola will provide 24/7
access to the ActiveEye Security Management Platform. Motorola will notify MCSO if access will be
affected, such as by scheduled maintenance.
Motorola Responsibilities
x
Provide access to the ActiveEye portal for MCSO and any identified, approved users. After
initial deployment, MCSO will have self-service access to add/remove/update user access as
needed.
x
Provide the subscribed services.
x
Resolve platform issues and technical errors as documented by MCSO.
x
Retain security logs within ActiveEye for thirty days. Security logs will be archived for one year
by the long-term storage policy.
MCSO Responsibilities
x
Provide reasonable assistance to Motorola to perform the Service, as described in this SOW.
This assistance includes, but is not limited to, smart hands assistance with issues that may
require physical access to the devices affected by this Service, or virtual assistance with virtual
environment issues that require administrative access to devices affected by this Service.
x
Provide all technical, license, and service information requested in the implementation
documents prior to the commencement of the Service.
x
Perform all network and system integrations necessary for ActiveEye Service. This includes
providing external Internet connectivity for ActiveEye security components.
x
Install agents on in-scope systems and devices, as required.
x
Configure all necessary components of Customer’s infrastructure to integrate with ActiveEye.
x
Provide the name, email, landline telephone numbers, and mobile telephone number for all
shipping, installation, and security Points-of-Contact (POC).
x
Securely manage user access to the ActiveEye portal, creating new user accounts when
needed and removing a user’s access when it is no longer required.
Motorola Deliverable
x
Access to the ActiveEye portal
6.26.2
Endpoint Detection and Response
ActiveEye managed Endpoint Detection and Response integrates endpoint detection and response
(EDR) tools with the ActiveEye Security Management Platform to provide additional threat intelligence,
automated investigation, and orchestrated response actions to optimize protection of critical systems.
EDR integration with ActiveEye accelerates investigations by making necessary information available
for analysts in a single platform, where they can quickly access details of what caused an alert, its
context, and its history.
Page 140
The platform enables analysts to initiate response actions (i.e. isolate host, block list a file, allow list a
file, and remove file) on endpoints to respond to detection of verified malicious activity within MCSO’s
system. Available responses are determined by MCSO’s EDR tool and security policies.
A third-party license for the EDR solution may apply to MCSO’s use of this service unless the
applicable EDR solution is separately procured by MCSO. See also the Limitations and Exclusions
section.
Motorola Responsibilities
x
Provide ports and protocols to MCSO for the EDR solution.
x
Deploy and maintain EDR agents to PremierOne host environment.
x
Configure EDR solution to enable ActiveEye connection for event/alert collection and response
actions.
MCSO Responsibilities
x
Deploy and maintain EDR agents to Customer managed equipment.
x
Configure networking infrastructure to allow EDR agents to communicate over the internet with
the cloud.
x
Configure EDR solution to enable ActiveEye connection for event/alert collection and response
actions.
x
Comply/consent with the terms of applicable licenses, privacy statements, or other third-party
agreements to the extent third-party software or services are utilized or provided by/through
Motorola, including applicable EDR solution provider’s end user license agreements (EULAs), if
any.
x
Obtain any third-party consents required to enable Motorola to provide the monitoring service, if
applicable.
Motorola Deliverables
x
EDR agents deployed in PremierOne host environment.
x
EDR solution configured in ActiveEye.
6.26.3
Advanced Threat Insights
With Advanced Threat Insights, Motorola provides continuous surface, deep, and dark web monitoring,
alerts and notifications, Customer risk reviews, organization-specific threat intelligence and industry-
level threat intelligence. Trained cybersecurity analysts will search the surface, deep, and dark web
looking for indications that any of MCSO’s systems, Customer user accounts in the monitored domain,
or data sets have been compromised. In addition, cybersecurity analysts will search for evidence that
MCSO’s organization or primary applications may be the target of a threat actor campaign.
Motorola’s cybersecurity analysts will develop threat reports and review them with MCSO. Analysts
perform threat intelligence gathering using a combination of automated and human methods. They
review threat intelligence findings during normal US business hours 8x5 on standard US business days:
Monday through Friday 8 a.m. to 5 p.m. local time, excluding Motorola Holidays, which include (but are
subject to annual updates): New Year’s Day, Martin Luther King, Jr. Day, Memorial Day, Juneteenth,
July 4, Labor Day, Thanksgiving Day, Day after Thanksgiving, Christmas Eve, Christmas Day.
There are four main aspects of this service:
Page 141
x
Named Analyst - A dedicated analyst will work with MCSO to understand the organization’s
operating environment and architecture in more detail and depth. This approach enables the
analyst to provide detailed recommendations for improving MCSO’s overall risk posture from a
consistent single point of contact.
x
Proactive Threat Hunting - The analyst will dedicate time each month (number of hours
dependent on subscription) to evaluate available threat intelligence and sensor information (log
analysis, EDR, NIDs, etc.) to identify areas of concern. This manual investigation can uncover
previously undetected threats that exist outside of the scope of typical security alerting and
provide a starting point for remediation and security recommendations to improve MCSO’s
overall security posture. The focus of this work can be directed by MCSO toward the most
critical assets or those assets most at risk given the threat landscape at the time.
x
Surface, Deep, and Dark Web insights - Risks go beyond the visible boundaries of the
organization. Monitoring for key assets on the surface, deep, and dark web provides actionable
insights into how the organization is being targeted and what assets are at risk, such as lost or
exposed credentials and sensitive data.
x
Monthly Summary and Discussion of Findings - The assigned analyst will present key findings
for the past month, discuss new threats to consider, and suggest any additional security
measures relevant to MCSO’s organization.
Motorola Responsibilities
x
Coordinate with MCSO to collect relevant information necessary to execute threat intelligence
searches on the dark web.
x
Deliver a monthly risk report detailing threat intelligence specific to MCSO.
x
Provide MCSO with a monthly Public Safety Industry intelligence report detailing threat
intelligence related to the Public Safety community as a whole.
x
Hold monthly recurring (up to 1 hour) formal risk reviews with MCSO to evaluate threats facing
MCSO and intelligence discoveries. This review also serves as an opportunity to refine the list
of critical information the threat team needs to proactively search for.
x
Alert MCSO immediately when critical threats or information breaches are discovered.
MCSO Responsibilities
x
Coordinate with Motorola to maintain relevant information necessary to execute threat
intelligence searches on the dark web.
x
Obtain for Motorola all rights, if any, that may be necessary to permit requested threat
intelligence searches on the dark web.
Motorola Deliverables
x
Monthly formal risk review with MCSO.
x
Monthly risk report.
Disclaimer
Scope of services do not include employee related investigative services, such as those that may target
any specific employees (or other individuals) or implicate privacy rights, alleged or suspected internal
conduct, or rights that may be protected or regulated by law, e.g. information bearing on an individual’s
character, general reputation, personal characteristics, mode of living., etc. Motorola reserves the right
to withhold from Customer any information deemed outside the scope of the engagement or otherwise
subject to legal restrictions and take any other action it deems to be required by law.
Page 142
Customer understands that some information shared with Customer through the Advanced Threat
Insights service will, by its nature, be unverifiable, will be delivered on an as-is basis, and may or may
not be correct. Customer agrees any information shared is for Customer’s internal business purpose
use only and shall not be further distributed by Customer.
Motorola does not represent that it will identify, fully recognize, discover, or resolve all security events
or threats, system vulnerabilities, malicious codes or data, backdoors, or other system threats or
incompatibilities as part of the service, or that the agreed upon cadence/time of delivery will be
sufficient to identify, mitigate or prevent any cyber incident.
For subscribers of the Advanced Threat Insights service, Motorola disclaims any warranty and does not
guarantee to be able to locate all threat intelligence on the surface, deep or dark web. Motorola will
perform an expansive search but cannot cover every forum and information source.
6.27
Optionally Available Additional CyberSecurity
Services
The following cybersecurity services are included:
x
Risk Assessment
-
Risk Assessment Only
Framework Compliance Assessment (NIST CSF)
x
System Security Plan Development
x
Business Continuity and Disaster Recovery (BC/DR) Planning
The following site information is included in the scope of these services:
MCSO Site Information
Quantity
Site / Location
Network Environment
Service Type
1
Organization Level
PremierOne
NIST CSF Risk Assessment
System Security Plan Development 800-53
BC/DR Plan Creation
6.27.1
NIST CyberSecurity Framework (CSF) Security Program Risk
Assessment
The activity consists of the following tasks:
x
Assessment Initiation: Discovery, Key Risks, Control and Program Assessment
x
Draft NIST CSF Security Program Risk Assessment and DHS CPG scorecard creation
x
Draft Report Review and Final Report Delivery
Following the kick-off call and upon the arrival of the agreed upon assessment date(s), Motorola will
conduct the NIST CSF Security Program Risk Assessment and the DHS Cross-Sector Cybersecurity
Goals assessment based on the following methodology and tasks:
Discovery
Motorola will conduct up to fifteen (15) remote and/or onsite interviews to understand the NIST CSF
framework elements by which MCSO's cybersecurity efforts will be measured against, along with
Page 143
identifying MCSO's in-scope categories and subcategories. Through the interviews with key Customer
staff, Motorola will determine MCSO cybersecurity efforts as they relate to safeguarding or
disseminating data and the twenty-three (23) key NIST CSF framework Categories identified below:
Framework
Categories
Identify
ƒ Asset Management
ƒ Business Environment
ƒ Governance
ƒ Risk Assessment
ƒ Risk Management Strategy
ƒ Supply Chain Risk Management
Protect
ƒ Identity Management and Access Control
ƒ Awareness and Training
ƒ Data Security
ƒ Information Protection Processes and Procedures
ƒ Maintenance
ƒ Protective Technology
Detect
ƒ Anomalies and Events
ƒ Security Continuous Monitoring
ƒ Detection Processes
Response
ƒ Response Planning
ƒ Communications
ƒ Analysis
ƒ Mitigation
ƒ Improvements
Recover
ƒ Recovery Planning
ƒ Improvements
ƒ Communications
Additionally, the organization will be evaluated against the DHS Cross-Sector Cybersecurity
Performance Goals (CPG). The CPGs are a prioritized set of security practices that are intended to
measurably reduce cybersecurity risk in both information technology as well as operational technology
environments. The goals are applicable across all critical infrastructure sectors and represent
Page 144
protections against some of the most impactful techniques adversaries have used to compromise the
confidentiality, integrity, and availability of systems.
Key Risks
NIST’s Special Publication 800 Series provides guidance for supervision and administration of an
enterprise Information Security Management System (ISMS). Motorola methodology includes a
systematic orientation to the threat environment facing Customer’s industry as well as Customer’s
specific business and operating environment. Motorola will determine key risk areas based on
vulnerabilities, likely threats, potential impacts as identified through document reviews, interviews, and
the NIST CSF control set.
Control Assessment
Upon identifying the key risks for MCSO with respect to NIST CSF and DHS CPG compliance,
Motorola will perform a control analysis to determine the current profile of cybersecurity maturity with
NIST CSF and DHS CPG requirements and create a list of Information Security Management System
program and policy gaps. Motorola will then determine the target profile based on the desired level of
risk mitigation and risk appetite and outline the needed investments and rebalancing efforts to meet the
target profile required to satisfy compliance with NIST CSF and DHS CPG requirements.
Draft NIST CSF Security Program Risk Assessment Report Creation
Motorola will document the results of the NIST CSF Security Program Risk Assessment findings, gaps,
and recommendations in a written Portable Document Format (PDF) formatted report and make
reasonable efforts to prioritize issues via the most pressing risk areas and gaps.
Upon the completion of the Draft Report, Motorola will perform the following tasks with MCSO:
x
Provide MCSO with the Draft Report for their review and analysis. During this time, Motorola will
also coordinate a Draft Report Review session with the relevant stakeholders over the phone
and/or internet conferencing methods.
x
Review the report and findings with MCSO and discuss recommendations for mitigating the
relevant risks with MCSO.
x
Upon completion of the Draft Report Review, Motorola will make final modifications to the report
that are brought up by MCSO and deliver the Final Report back to MCSO POC to complete the
project. The Final Report contains an Executive Summary with a summary findings and
recommendations and a Technical Summary that provides more details.
Motorola Deliverables
x
Draft Report
x
Final Assessment Report
6.27.2
Business Continuity and Disaster Recovery (BC/DR) Planning
A Business Continuity Plan (BCP) will be prepared and readied for on-demand implementation for use
in sustaining operations and supporting Customer during a business interruption, disaster, or recovery
event. A BCP serves several essential purposes at the time of a disaster/incident: it is a quick reference
document that ensures key activities are accomplished, it provides ready access to resource
information such as vendor telephone numbers and equipment configurations, and it serves as a
management and communication tool by defining common progress checkpoints and milestones. A
BCP must be sufficiently detailed to guide alternate personnel through key recovery processes if
primary recovery personnel are unavailable. At other times, a BCP is a primary testing and training tool
for response and recovery procedures.
Page 145
Whether it’s a cyberattack holding Customer data for ransom, a global pandemic resulting in employees
needing to work from home, or a natural disaster such as a tornado, flood, or hurricane, a BCP will help
organizations respond faster to minimize negative impacts to business. The following areas are
categories a BCP should address to restore business after a disruption or disaster.
Introduction
x
BCP Objectives: Outline the key goals of the BCP and areas of focus to define scope (and
limitations).
x
Essential Business Functions: Identify Customer’s essential business functions using Recovery
Time Objectives (RTOs) and Recovery Point Objectives (RPOs) to guide recovery prioritization.
Most commonly, a Business Impact Analysis (BIA) and Risk Assessment (RA) are conducted
before a BCP to provide input for readiness and resiliency planning.
Contact Information
x
Internal Contacts: Include contact information for Customer employees and staff such as name,
job title, work telephone number, personal telephone number, email, address, emergency
contact, and manager.
x
Suppliers and Vendor Contacts: All supplier and vendor contacts should be included in the plan.
List company name, service description, telephone number, and email.
x
Emergency Contact: Include telephone numbers for local police, fire departments, ambulance
services, flood lines, insurance, utility companies, building maintenance, etc.
Development
In particular, a BCP is intended to:
x
Ensure the continuous performance of essential business functions and processes during an
emergency.
x
Establish emergency concepts, actions, and procedures.
x
Identify processes and functions that must be maintained, along with essential positions to
maintain those processes and functions.
x
Ensure protection of Customer resources, facilities, and personnel.
x
Protect essential facilities, equipment, records, and other assets.
x
Reduce or mitigate disruptions to operations and minimize damage and loss of resources.
x
Achieve a timely and orderly recovery from business disruptions or emergencies.
x
Identify alternate site(s) for Customer operations in the event that a primary operation facility is
not functional and/or available.
x
Establish a notification process for the Crisis Management Team to inform employees and other
key stakeholders of BCP activation. Activation categories are often identified as: Normal
Operations (No impact to Customer), Monitoring (Crisis Management Team is monitoring the
situation), Partial Activation (Crisis Management Team implements partial activation of the
plan), and Full Activation (Crisis Management Team implements full activation of the plan).
x
Conduct essential operations from an alternate site within twelve (12) hours of the event onset
for a period of up to thirty (30) days, as specified using RTOs and RPOs.
x
Establish order of succession and delegations of authority for the Crisis Management Team and
other continuity personnel.
x
Identify personnel needed to perform each department’s essential business functions.
Page 146
x
Identify means of communication with each department lead, employees, suppliers and
vendors, emergency personnel, and the public.
x
Prioritize the recovery of processes, functions, critical systems, applications, and vital records.
x
Identify backup processes, procedures, and manual workarounds.
Training, Testing, Distribution, and Review
x
Establish requirements for regularly scheduled training, testing, distribution, and exercising of
the BCP. BCP training, testing, and exercises should be conducted at least annually, or as
significant changes occur, for the Crisis Management Team and employees.
x
Establish interoperable communications and resource requirements to complete essential
functions.
Motorola Responsibilities
x
Work with MCSO to define the goals, scope and limitations of the BCP.
x
Assist MCSO with identification of essential business functions.
x
Collect information from internal contacts, suppliers and vendors and emergency contact
personnel.
x
Establish a notification process for the Crisis Management Team to inform employees and other
key stakeholders of BCP activation.
x
Provide guidance and best practices for training, testing, distribution and exercising of the BCP.
x
Prepare BCP for County review.
x
Update BCP as required, based on County feedback.
MCSO Responsibilities
x
Work with Motorola to define the goals, scope and limitations of the BCP/
x
Identify essential business functions.
x
Provide contact information for internal contacts, suppliers and vendors and emergency contact
personnel.
x
Establish requirements for training, testing, distribution and exercising of the BCP.
x
Review and approve BCP, or provide requested updates.
Motorola Deliverables
x
Business Continuity Plan
6.27.3
Cybersecurity Advisory Services: System Security Plan Development
The following describes the primary activities for development of the System Security Plan (SSP)
documentation.
6.27.3.1
SSP Active Assessment
Motorola Responsibilities
x
Provide a list of requested supporting documentation
x
Review the initial set of documents.
x
Prepare draft SSP for customer review.
Page 147
x
Conduct additional information if required to clarify control implementation.
x
Advise or provide language regarding formatting and content of supplemental documents.
MCSO Responsibilities
x
Provide key personnel for topical interviews (access control, boundary protection, system
integrity).
x
Provide evidence of implementation upon request.
x
Provide supplemental or supporting documentation such as additional policies, procedures, and
plans.
x
Provide additional information if required to clarify control implementation. Evidence can include
screen shots, documents, or records.
x
Provide a working location for onsite Motorola cybersecurity individuals performing on-site work.
6.27.3.2
SSP Writing and Draft Review
At periodic intervals, the SSP will be provided to be reviewed by MCSO-appointed agents. Motorola will
provide the SSP draft in an editable, common format.
Motorola Responsibilities
x
Provide iterative updates to the SSP for MCSO review.
x
Modify the SSP based on MCSO feedback.
x
Deliver final draft of the SSP to MCSO.
MCSO Responsibilities
x
Review the SSP and provide specific feedback to Motorola.
Motorola Deliverables
x
Draft SSP
6.27.3.3
SSP Finalization
A final draft of the SSP is submitted to MCSO for their comments and review includes a description of
each control in MCSO’s chosen framework (ex: NIST 800-53r5, NIST 800-171). The final SSP
describes how the organization meets, or plans to meet security requirements. It outlines the details of
implementation (or planned implementation), the scope of the system, the system security boundary,
and all required security controls. MCSO has 60 days to provide comments and/or feedback concerning
the draft SSP. At the end of the 60 days, the SSP is considered final.
Motorola Responsibilities
x
Make required adjustments to final draft of the SSP.
MCSO Responsibilities
x
Perform final review and acknowledge acceptance of the SSP.
Motorola Deliverables
x
Final SSP
Page 148
Section 7
Exhibit C-1: Project Schedule
Motorola has provided its Project Schedule on the following pages.
Page 149
Page 150
Page 151
Page 152
Page 153
Page 154
Page 155
Page 156
Page 157
Page 158
Page 159
Page 160
Page 161
Page 162
Page 163
Page 164
Page 165
Page 166
Page 167
Page 168
Page 169
Page 170
Page 171
Page 172
Page 173
Page 174
Use or disclosure of this proposal is subject to the restrictions on the cover page.Motorola Solutions
Page 175
Section 8
Exhibit D: PremierOne Training
Plan
8.1
Introduction
Motorola Solutions (Motorola) considers education to be a critical aspect of the system installation and
requires Motorola to work closely with the Customer to develop their knowledge and skills. This
Training Plan is tailored to your agency’s operational business process, job roles, and personnel needs
and will deliver the necessary information needed to effectively and efficiently use new systems and
technologies through a flexible, multimodal approach.
Motorola employs a multimodal methodology for training that offers a diverse range of materials,
application, and tools, including e-learning platforms, simulations and other technology-enabled
modalities as well as formats such as instructor-led training, on-the-job training, computer-based
training, coaching, workshops, and demonstrations. This approach to training allows Motorola to
customize a plan that supplements your personnel’s inherent knowledge with information about the
features, functions, and mechanics of the solution. Our goal is to work with you to optimize your training
so that your agency’s daily operations and workflows are productive and efficient.
Motorola’s instructors are certified through the Learning and Performance Institute’s Online Learning
Facilitators program, ensuring instruction is delivered in the most efficient and beneficial manner to
industry recognized standards.
Note - Customer specific needs that are not addressed as a Course or Workshop or outlined in this Training Plan
can be addressed via Motorola’s Consulting Services.
Motorola’s primary education delivery models are:
x
Instructor-Led: Instruction is provided by a Motorola instructor in a traditional Customer provided
classroom environment or via web conferencing hosted by Motorola.
x
Computer Based: Computer-based training provides self-paced instruction on the features and
functions of the Motorola software applications. This delivery method enables the attendee to
progress through training at a pace prescribed by the Customer that is comfortable to the
attendee. Motorola’s computer-based training delivery method includes the use of a Learning
eXperience Portal (LXP).
A sample of LXP course offerings include:
LXP Courses
PSA4001 CAD End User - Keyboard Shortcuts
PSA4044 PremierOne Mobile End User - Closing
Incidents
PSA4151 RMS Provisioning - Creating a New Code
Table
PSA0120 Mobile Android User - Logging in/Logging
Out
PSA4139 CAD/Mobile Provisioning - Incident
Management - Incident Response Factors
PSA0210 Mobile iOS User – Navigating the
Dashboard
Use or disclosure of this proposal is subject to the restrictions on the cover page.Motorola Solutions
Page 176
8.2
Workshops and Course Listing
The following tables present information on each workshop and course included in the Training Plan.
Due to the nature of each workshop and course, it is imperative that the maximum number of attendees
not be exceeded. Doing so erodes the integrity of each session and impairs attendee’s ability to retain
the subject matter information.
The following list provides definition of the methods of instruction used to deliver:
x
LXP-C – Software application training provides instruction on the features and functional use of
a software application or specific module. The delivery method is entirely computer based and
accessed via LXP on demand with no in-person training component.
x
LXP-P – LXP prerequisites, attendees must complete before attending in-person sessions.
x
LXP-R – LXP refresher, this software application training offers components that can be taken
on demand through the LXP after the in-person training has completed.
x
On-site (O) – in-person training from an on-site instructor conducted at the Customer’ facilities.
x
Virtual (V) – virtual instructor-led training (class will be recorded and made available for future
Customer use).
8.2.1
Workshops
Workshops offer guided instruction and hands-on exposure to each attendee providing practical
experience with the subject matter. In many cases the attendee must possess a common level of
industry knowledge and complete LXP prerequisites as defined for each workshop in order to grasp the
presented concepts and material.
Workshop Information
Workshop Information
Solution Name
Workshop Name
Max # of
Attendees
Per Session
# of
Workshop
Sessions
Included
Method of
Instruction
Workshop Duration
LXP
Learning
eXperience Portal
(LXP)
Administrator
Overview
2
1
Virtual
1 hr.
PremierOne CAD
Set of
PremierOne
CAD/Mobile
Provisioning
Workshops
Requires working
knowledge of
customer
business
workflows and
current
application
configuration.
9
1
LXP-P,
Virtual, On-
site & LXP-R
112 hrs. (over various
sessions)
Use or disclosure of this proposal is subject to the restrictions on the cover page.Motorola Solutions
Page 177
Query
Provisioning
and Formatting
Workshop
4
1
LXP-P &
Virtual
16 hrs. over 2 days
Premier One
Records
Set of
PremierOne
Records
Provisioning
Workshops
Requires working
knowledge of
customer
business
workflows and
current
application
configuration.
9
1
LXP-P,
Virtual, On-
site & LXP-R
60 hrs. (over various
sessions)
PremierOne
Records Rich
Text Format
(RTF) Workshop
Requires
knowledge of
current printouts
and PremierOne
Module
Configuration.
4
1
Virtual
8 hrs. over 1 day
PremierOne
Reporting
Services
SSRS Report
Builder
Workshop for
PremierOne
CAD
6
2
LXP-P,
On-site &
LXP-R
24 hrs. over 3
consecutive 8 hr. days
Intelligent Data
Discovery (IDD)
Workshop for
PremierOne
CAD
6
2
LXP-P,
On-site
24 hrs. over 3
consecutive 8 hr. days
SSRS Report
Builder
Workshop for
PremierOne
Records
6
2
LXP-P,
On-site &
LXP-R
24 hrs. over 3
consecutive 8 hr. days
Intelligent Data
Discovery (IDD)
Workshop for
PremierOne
Records
6
2
LXP-P,
On-site
24 hrs. over 3
consecutive 8 hr. days
Use or disclosure of this proposal is subject to the restrictions on the cover page.Motorola Solutions
Page 178
PremierOne
Reporting
Services Add On
Workshop
RDLC Printouts
in Premier One
Records
Requires
completion of
Advanced
Configuration
Tool (ACT) for
PremierOne
Records and
PremierOne
SSRS Report
Builder Workshop
6
1
Virtual
24 hrs. over 3
consecutive 8 hr. days
PremierOne
Infrastructure
System
Administration
PremierOne
CAD/Mobile
System
Administrator
Requires working
knowledge of
computer
hardware,
operating system
software and
database
maintenance
4
2
LXP-P &
On-site
24 hrs. over 3
consecutive 8 hr. days
PremierOne
Records System
Administrator
Requires working
knowledge of
computer
hardware,
operating system
software and
database
maintenance
4
2
LXP-P &
On-site
16 hrs. over 2
consecutive 8 hr. days
PremierOne GIS
GIS
Administrator
Workshop
Requires working
knowledge of
ESRI software
and GIS
Concepts
4
1
Virtual
24 hrs. over two weeks.
Premier One
Records Add-on
Convert on
Demand (CoD)
Workshop
Requires
knowledge of
legacy Records
data, data formats
and documents
1
On-site
24 hrs. Over 3
consecutive 8 hr. days
Use or disclosure of this proposal is subject to the restrictions on the cover page.Motorola Solutions
Page 179
8.2.2
Instructor-Led Training Courses
Similar to the Workshops structure, instructor-led training offers guided instruction but in a classroom
environment. Instructor-led training focuses on the mechanics of the application software features,
functions, and use. In many cases the attendee must possess a common level of industry knowledge
and complete LXP prerequisites in order to grasp the presented concepts and material.
The MCSO is entitled to an additional 728 hours of Records user training. The training may be
distributed over the Records course descriptions below or may be further deconstructed from the
Records End User training content based on user roles. These hours accommodate up to (4) End User
classes (4-day/32 hr. classes, onsite) for up to 50 users. The remaining 680 hours/85 8-hour days
accommodate ~1000 users with 8 hours of training. Training will be conducted for up to twelve (12)
attendees per session and will be scheduled over four (4) consecutive days per week. Based on
mutually agreed to schedules, Motorola will provide more than one (1) instructor to accommodate
concurrent training sessions at different locations and/or day shift and evening shift sessions.
Instructor-Led Training Course Information
Solution Name
Course Module
Maximum #
of Attendees
Per Course
# of
Instances
Included
Method of
Instruction
Class Duration
PremierOne
CAD
PremierOne
Computer Aided
Dispatch Train-the-
Trainer
12
1
LXP-P &
On-site
32 hrs. over 4
consecutive 8 hr.
days
PremierOne
CAD/Mobile Client
Installation
4
1
LXP-P &
On-site
24 hrs. over 3
consecutive 8 hr.
days
PremierOne
CAD Add-On
Courses
PremierOne
Computer Aided
Dispatch End User
Training
12
5
LXP-P &
On-site
30 hrs. over 3
consecutive 10 hr.
days
PremierOne
Records
PremierOne Records
Train-the-Trainer
12
1
LXP-P &
On-site
32 hrs. over 4
consecutive 8 hr.
days
PremierOne Records
Advanced
Configuration Tool
(ACT) Training
4
1
Virtual
32 hrs. over 4
consecutive days
PremierOne Records
Case Report
Completion and
Workflow End User
Training
12
##
LXP-P &
On-site
Six 4 hr. sessions
over 3 consecutive
8 hr. day
PremierOne Records
Case Management
End User Training
12
##
LXP-P &
On-site
Six 4 hr. sessions
over 3 consecutive
8 hr. day
PremierOne
Records Add
on Courses
PremierOne Records
End User Training
12
##
LXP-P &
On-site
32 hrs. over 4
consecutive 8 hr.
days
PremierOne
Mobile
PremierOne
CAD/Mobile Client
Installation
4
1
On-Site
24 hrs. over 3
consecutive 8 hr.
days
Use or disclosure of this proposal is subject to the restrictions on the cover page.Motorola Solutions
Page 180
8.2.3
Training Overview
The Customer Training Representative should be familiar with the Customer's daily operations and
must attend (or designate a replacement) each Motorola educational course. Motorola instructors will
rely on this representative to be the one point of contact for Motorola staff when policy and procedural
questions arise, act as course facilitator, and act as the Customer's educational monitor. The Customer
will also identify the personnel who will serve as trainers. These individuals must participate in all the
Train-the-Trainer courses. In addition to the skills described below, the Customer’s trainers must have
prior experience as a classroom instructor and a thorough understanding of the Customer's operations.
Other courses will require participants from different areas of the Customer's operations as shown in
the individual course descriptions, detailed in Section 3.3: Course Descriptions.
8.2.4
Training Facilities and Schedules
On-site training will be conducted in a Customer provided training facility setup in classroom
configuration with a workspace for attendee note taking, and computer and dual monitors for each
attendee. Each instructor-led on-site session requires a projector, connected to the applicable Motorola
system workstation, and a white-board for instructor’s use. The on-site workshop format requires multi-
monitor (minimum of three) workstations, one for each attendee. MCSO may record instructor-led
courses, if desired.
For classes provided virtually, Motorola will provide the conference link and host information required
for each attendee to join the session. The Customer is responsible for providing all equipment and
remote access mechanism required to enable each attendee to join the Motorola hosted event.
At least (5) days prior to on-site training courses, the customer must supply Motorola with a roster of
course attendees. Attendees should ensure access to the LXP and complete prerequisite training prior
to the on-site training course start date.
At least two days prior to each on-site session, the instructor will have access to the training facility and
all workstations for setup and workstation configuration. Motorola and the Customer shall mutually
agree to training schedules to accommodate the Customer’s shift operations and other site-specific
requirements. Evening courses will end by 11:00 p.m. End User training classes will be accommodated
on Saturdays. Sundays and Holidays will not be used as training days.
8.2.4.1
Training Methods and Procedures
Motorola offers on-site training and online training both coordinated with the LXP. Types of training
courses include:
x
Administrative workshops that provide specialized users with in-depth knowledge on the
features, operational, and administrative functions of the system.
PremierOne
Windows Mobile
Training (Includes
Records Mobile in
each 4 hr. session)
12
156
LXP-P &
On-site
Six 4 hr. sessions
over 3 consecutive
8 hr. days
PremierOne Mobile
for Android and iOS
End User Training
(Includes Responder
training)
All
Subscribers
All
Subscribers
LXP-C
4 hrs.
Use or disclosure of this proposal is subject to the restrictions on the cover page.Motorola Solutions
Page 181
x
Train the Trainer; instructor-led classroom training that provides key individuals with extensive
hands-on use of the system utilizing true-to-life incident scenarios so they can develop and
provide training to new users.
x
End User Training; Instructor-led classroom training that provides users with instruction on
subject matter relevant to their respective role in using and or supporting the PremierOne
System. In addition to facilitated discussion, End User training consists of workshop elements
where needed, to provide hands-on demonstration of the material being presented.
x
Instructor-Led virtual online training that uses the LXP.
x
Online “Anytime” training that uses the LXP.
x
Designated Motorola Instructors will provide application instruction using several techniques and
materials:
x
Instructor Lesson Plan: The instructor’s tool for planning the detailed course content on a
module-by-module basis.
x
Training Course Agenda: A handout for attendee that outlines the course sequence of events
including duration, and course modules.
x
Worksheets, Job-Aids, Quizzes: Activities provided by the instructor to help attendees retain
course information
x
Training Course Objectives: The instructor’s predefined course objectives. These are
provided for Train-the-Trainer classes only.
x
Evaluations: The Instructor Evaluation Form for attendees to complete on the final day of a
training class, the attendees will be asked to complete an Instructor Evaluation form. They are
optional forms and anonymity is acceptable.
x
Attendance Rosters: A roster, provided by the Customer, listing the names of training
participants five (5) days prior to the start of the course. Instructors will complete Attendance
Rosters of actual participants for each day of training
x
Prerequisite training: On demand LXP courses which provide base knowledge for all
attendees prior to the start of on the on-site class.
x
Motorola User Documentation: An electronic copy of the applicable Motorola Reference
Manuals and documentation will be provided prior to training. The Customer is responsible for
duplicating and delivering manuals to participating attendees prior to class commencement.
8.2.5
Session Attendance
Motorola is committed to providing a quality training experience and desires that the Customer receives
the maximum benefit from each on-site training session. Each training session has been sized to
provide the optimal training environment that meets the needs of the attendees in relation to the
complexity of the material being presented. Given the nature of the material being presented and the
intensity of the training, it is imperative that maximum course numbers not be exceeded. If the number
of attendees in attendance exceeds the published maximum number of attendees and the list of
participants identified on the training roster, Motorola will take corrective action, ensuring the integrity of
the session is maintained and the attendee’s ability to learn is protected. Motorola corrective action may
include:
x
Delaying the start of training until the number of attendees in attendance is in line with the
maximum number of attendees allowed for the session.
x
Splitting the class into multiple sessions. In such a case, the Customer will be charged for
multiple occurrences of the class plus additional expenses, including travel related expenses
incurred by Motorola Solutions.
Use or disclosure of this proposal is subject to the restrictions on the cover page.Motorola Solutions
Page 182
x
Delaying the classroom training until the Prerequisite training has been completed in the LXP by
each attendee.
8.2.6
LXP Requirements
x
The LXP is accessed via an internet browser. Motorola will set up an individual instance of the
Learning Management System, known as an organization. This provides autonomy to the
agency utilizing LXP.
x
Accounts to access the LXP are created for each learner using their Email address. All
attendees accessing LXP content must have their own account in the LXP. A learner will need
to have access to the internet via a workstation, laptop, tablet or smartphone to access learning.
x
Customer LXP Administrators will be given the ability to build Groups, a more granular
segmentation of the LXP that is generally utilized to separate learners of functions (i.e.
dispatchers, call takers, patrol, firefighter). One attendee can be assigned to multiple groups if
necessary. Attendees can be assigned a Learning Path, a collection of courses that include
likeminded courses.
x
In most cases audio accompanies visual display; speakers or headsets are recommended to
utilize full functionality of the LXP. Course assessment evaluations are also accessed via the
LXP. Access to these evaluations in the classroom is suggested.
8.2.6.1
LXP Learner Subscription Package
Learner-level subscriptions have been included for personnel who are expected to be users of one or
more products. Customer resources will have access to the LXP training materials during deployment
and as long as the post-live subscription is maintained during the warranty/maintenance period.
Learner-level subscriptions allow access to all materials available for the applications included in this
Training Plan.
8.3
Course Descriptions
8.3.1
Workshop Course Descriptions
The following tables provide detailed descriptions of workshop courses that will be provided as part of
the system at the location indicated.
Table 8-1: Learning eXperience Portal (LXP) Administrator Overview
Learning eXperience Portal Admin Overview
Goal
Provide training to add/modify users, run reports, and add/modify groups within the
Learning Management Solution.
Course Materials
LXP
Location
Virtual
Duration
Up to one hour
Participants
Those responsible for the management of assigning and overseeing LXP-C and LXP-P
training.
Class Size
Maximum of two attendees
Use or disclosure of this proposal is subject to the restrictions on the cover page.Motorola Solutions
Page 183
Learning eXperience Portal Admin Overview
Prerequisite
Knowledge of Customer Training Requirements.
Access to learningservices.motorolasolutions.com
Environment Setup
Workstation with internet connection
Table 8-2: Set of PremierOne CAD/Mobile Provisioning Workshops
Set of PremierOne CAD/Mobile Provisioning Workshops
Goal
Conduct structure workshops to provide instruction on configuration options of
PremierOne CAD and Mobile.
Course Materials
PremierOne CAD and Mobile Provisioning Guide
PremierOne CAD User Guide
PremierOne System Management Tool Portal User Guide
Course Outline.
LXP refresher training courses.
Location
Customer’s facility and virtual.
Duration
PremierOne CAD Workshop 1: On-Site (24 hours)
PremierOne CAD and Mobile Workshop 2: Virtual (24 hours)
PremierOne CAD and Mobile Workshop 3: Virtual (24 hours)
PremierOne CAD Workshop 4: On-Site (24 hours)
Participants
The goal of Motorola led Workshops and Checkpoints is to provide the Agency Core
Team with sufficient knowledge to provision the PremierOne CAD and Mobile product.
Participants should have knowledge of current CAD and Mobile applications and
customer operations with the authority to make decisions in relation to the new
PremierOne CAD and Mobile systems look and functionality is required.
Class Size
Maximum of nine (9) attendees
Prerequisite
Prerequisite training videos must be completed prior to the Workshop begining.
Prerequisite work not being completed will result in the Workshop and Checkpoint
being rescheduled.
LXP Required Prerequisite training courses:
ƒ PSA4154 Provisioning - Intro to Web Portal
ƒ PSA4126 Provisioning - Navigation & Terminology
ƒ PSA4149 Provisioning - Managing Admin Account
ƒ PSA4137 Provisioning – LSM
ƒ PSA4133 Provisioning - Clone & Delete
ƒ PSA4147 Provisioning - Importing & Exporting
ƒ PSA4125 Provisioning - Agency Types/Agency
Environment Setup
Attendee Workstations:
ƒ Each workstation or device used for LXP prerequisites must have an internet
connection
ƒ CAD workstation for each participant with network connection to the PremierOne
servers
ƒ Microsoft Excel and Word should be installed on at least one training workstation
Instructional Requirements:
ƒ Instructor’s workstation(s) with network connection.
ƒ Projector.
ƒ Dry erase board.
Use or disclosure of this proposal is subject to the restrictions on the cover page.Motorola Solutions
Page 184
Table 8-3: Query Provisioning and Formatting Workshop
Query Provisioning and Formatting Workshop
Goal
Conduct structure workshops to provide instruction on configuration options for queries
in PremierOne
Course Materials
PremierOne CAD and Mobile Provisioning Guide
Course Outline.
LXP refresher training courses.
Location
Virtual.
Duration
16 hours over 2 days
Participants
Participants should have knowledge of PremierOne CAD and Mobile Provisioning.
Class Size
Maximum of four (4) attendees
Prerequisite
Prerequisite training videos must be completed prior to the Workshop begining.
LXP Required Prerequisite training courses:
ƒ PSA4042 End User – Queries
ƒ PSA4038 End User – Query Smart Copy
Environment Setup
Attendee Workstations:
ƒ CAD workstation for each participant with network connection to the PremierOne
servers
Table 8-4: Set of PremierOne RMS Provisioning Workshops
Set of PremierOne RMS Provisioning Workshops
Goal
Conduct structure workshops to provide selected personnel with sufficient knowledge
to configure PremierOne Records to meet the agency’s needs, including security,
agency code tables, personnel, and other administrator items.
Course Materials
PremierOne Records Concepts and Getting Started Guide
PremierOne Records Provisioning Guide
PremierOne Records Mobile User Guide
PremierOne System Management Tool Portal User Guide
Course Outline.
LXP refresher training courses.
Location
Customer’s facility and virtual.
Duration
PremierOne RMS Workshop 1: On-Site (24 hours over 3 consecutive days)
PremierOne RMS Checkpoint 1: Virtual (8 hours in a single day)
PremierOne RMS Workshop 2: Virtual (20 hours over 5 consecutive days)
PremierOne RMS Checkpoint 2: Virtual (8 hours in a single day)
Participants
The goal of Motorola led Workshops and Checkpoints is to provide the Agency Core
Team with sufficient knowledge to provision the PremierOne RMS product.
Participants should have knowledge of current Records application and customer
operations with the authority to make decisions in relation to the new PremierOne RMS
systems look and functionality as required.
Class Size
Maximum of nine (9) attendees
Use or disclosure of this proposal is subject to the restrictions on the cover page.Motorola Solutions
Page 185
Set of PremierOne RMS Provisioning Workshops
Prerequisite
Prerequisite training videos must be completed prior to the Workshop beginning.
Prerequisite work not being completed will result in the Workshop and Checkpoint
being rescheduled.
LXP Required Prerequisite training courses:
ƒ PSA4151 Provisioning - Creating a New Code Table
ƒ PSA0098 Provisioning - Workflow 101
Environment Setup
Attendee Workstations:
ƒ One (1) workstation for each participant
ƒ Each workstation or device used for LXP prerequisites must have an internet
connection
ƒ Records workstation for each participant with network connection to the PremierOne
servers
ƒ Microsoft Excel and Word should be installed on at least one training workstation
Instructional Requirements:
ƒ Instructor’s workstation(s) with network connection.
ƒ Projector.
ƒ Dry erase board.
Table 8-5: PremierOne Records Rich Text Format (RTF) Workshop
PremierOne Records Rich Text Format (RTF) Workshop
Goal
Conduct structure workshop to create custom Rich Text Format (RTF) printouts as well
as edit existing system RTF printouts.
Course Materials
PremierOne Records Provisioning Guide
PremierOne Records Mobile User Guide
Course Outline.
Location
Virtual
Duration
8 hours over 1 day
Participants
Participants should have knowledge of current Records application and customer
operations with the authority to make decisions in relation to the new PremierOne RMS
systems look and functionality is required.
Class Size
Maximum of four (4) attendees
Prerequisite
Participants must have completed the Instructor-Led Advanced Configuration Tool
(ACT) prior to attending this workshop.
Environment Setup
Attendee Workstations:
ƒ One (1) workstation for each participant with an internet connection
Virtual Environment Browser Requirements:
ƒ The browser must support WebSockets in order to connect to CloudShare
environments and experiences.
ƒ The minimum bandwidth in order to connect to a Remote Desktop Protocol (RDP)
session is 150 Kbps.
Table 8-6: SSRS Report Builder Training in PremierOne for CAD and Records
SSRS Report Builder Training in PremierOne
Description
Provides guided instruction in a workshop format to create custom reports against the
PremierOne Reporting Data Warehouse (RDW) or DHStoreAnalysis Database using
Microsoft SQL Server Reporting Service (SSRS) and Report Builder software.
Use or disclosure of this proposal is subject to the restrictions on the cover page.Motorola Solutions
Page 186
SSRS Report Builder Training in PremierOne
Course Materials
SSRS Training Guide.
Course Outline.
Location
Customer’s facility.
Duration
Up to 24 hours over three consecutive business days.
Participants
Personnel who will create custom reports.
Class Size
Maximum of six (6) attendees.
Prerequisite
Class participants must have some knowledge/experience of creating “on demand”
reports.
Class participants should have experience working with relational database structures
as well as writing and understanding transact SQL code.
Environment Setup
Attendee Workstations:
ƒ One (1) workstation for each attendee with a connection to the PremierOne system
environment.
ƒ The following is the current list of Operating Systems and Browsers supported for
the web portal.
ƒ Windows 7, 8.1, 10; Windows Server 2008 R2, 2012, 2012 R2.
ƒ Microsoft Edge (+) Preferred.
ƒ Microsoft Internet Explorer 10 or 11.
ƒ Google Chrome (+).
ƒ Mozilla Firefox (+).
ƒ Microsoft SQL Server Reporting Services installed, configured, and working.
ƒ Microsoft Report Builder installed.
Optional:
ƒ SQL Server Management Studio on each Attendee Workstation.
ƒ One (1) CAD Client for the class is preferred in the case data entry needs to take
place in order to report against.
System Requirements:
ƒ Data pre-exists in the Reporting Data Warehouse or DHStoreAnalysis Database
(data is typically propagated during the training courses).
Instructional Requirements:
ƒ Instructor’s workstation(s) with network connection.
ƒ Projector.
ƒ Dry erase board.
Use or disclosure of this proposal is subject to the restrictions on the cover page.Motorola Solutions
Page 187
Table 8-7: Intelligent Data Discovery (IDD) in PremierOne CAD and Records
Intelligent Data Discovery (IDD) in PremierOne
Goal
Provide selected personnel with knowledge to create Business Intelligence dashboards
in PremierOne using Microsoft SQL Server Reporting Services tools (SSRS) and
Report Builder software.
Course Materials
Reporting and Analytics Intelligent Data Discovery Training Guide.
Course Outline.
Location
Virtual.
Duration
Up to 24 hours over three consecutive business days.
Participants
Personnel who will be responsible for building Business Intelligence Dashboards and
reports used for statistical analysis.
Class Size
Maximum of six (6) attendees.
Prerequisite
Successful completion of SSRS Reporting Training for PremierOne.
Experience in creating Reports using Microsoft SQL Server Reporting Services.
Familiarity with T-SQL statements for querying data within a SQL Server database
Environment Setup
Attendee Workstations:
ƒ One (1) workstation for each attendee with a connection to the PremierOne system
environment.
ƒ The following is the current list of Operating Systems and Browsers supported for
the web portal.
ƒ Windows 7, 8.1, 10; Windows Server 2008 R2, 2012, 2012 R2.
ƒ Microsoft Edge (+) Preferred.
ƒ Microsoft Internet Explorer 10 or 11.
ƒ Google Chrome (+).
ƒ Mozilla Firefox (+).
ƒ Microsoft SQL Server Reporting Services installed, configured, and working.
ƒ Microsoft Report Builder Installed.
ƒ All Training workstations installed with SQL Server Management Studio.
System Requirements:
ƒ Existing data in the DHStoreAnalysis (data is typically propagated during the TTT
course).
Table 8-8: RDLC Printouts in Premier One Records (Add-on)
RDLC Printouts in PremierOne Records
Goal
Provide selected personnel with knowledge to create in module and printed forms
based on data contained within the specified module in PremierOne Records.
Course Materials
Course Outline.
Location
Virtual.
Duration
Up to 24 hours over three consecutive business days.
Participants
Personnel who will be responsible for creating reports and managing data needs from
the PremierOne Records application.
Class Size
Maximum of six (6) attendees.
Use or disclosure of this proposal is subject to the restrictions on the cover page.Motorola Solutions
Page 188
RDLC Printouts in PremierOne Records
Prerequisite
Successful completion of SSRS Reporting Training for PremierOne.
Experience in creating Reports using Microsoft SQL Server Reporting Services.
Familiarity with T-SQL statements for querying data within a SQL Server database.
Environment Setup
Attendee Workstations:
ƒ One (1) workstation for each attendee with a connection to the PremierOne system
environment. (2) monitor setup is preferred.
ƒ Access to PremierOne Records Advanced Configuration Tool (ACT)
ƒ Windows 7, 8.1, 10; Windows Server 2008 R2, 2012, 2012 R2.
ƒ Microsoft Edge (+) Preferred.
ƒ Microsoft Internet Explorer 10 or 11.
ƒ Google Chrome (+).
ƒ Mozilla Firefox (+).
ƒ Microsoft Report Builder Installed.
ƒ All Training workstations installed with SQL Server Management Studio.
ƒ Visual Studio 2019.
ƒ Notepad ++.
System Requirements:
ƒ Full provisioned PremierOne Records Environment
Instructional Requirements:
ƒ Instructor’s workstation(s) with network connection.
Use or disclosure of this proposal is subject to the restrictions on the cover page.Motorola Solutions
Page 189
Table 8-9: PremierOne CAD/Mobile System Administrator Training
PremierOne CAD/Mobile System Administrator Training
Goal
Provides practical techniques for system administration and maintenance of the CAD
and Mobile components of the PremierOne system.
Course Materials
PremierOne SCOM Monitoring Guide
Course Outline.
LXP refresher training courses.
Location
Customer’s facility.
Duration
Up to 24 hours over three consecutive business days.
Participants
System Administrators - personnel responsible for the day-to-day management of the
system.
Class Size
Maximum of four (4) attendees.
Prerequisite
LXP Required Prerequisite training courses:
ƒ PSA4029 System Administration - Hardware Overview.
Knowledge of customer site network, IT policies and operations.
Microsoft proficiency as defined in the Prerequisites Section.
Environment Setup
Attendee Workstations:
ƒ Each workstation or device used for LXP prerequisites must have an internet
connection.
Instructional Requirements:
ƒ Instructor’s workstation(s) with network connection to the PremierOne servers.
ƒ Projector.
ƒ Dry erase board.
Use or disclosure of this proposal is subject to the restrictions on the cover page.Motorola Solutions
Page 190
Table 8-10: PremierOne Records System Administrator Training
PremierOne Records System Administrator Training
Goal
Provides practical techniques for system administration and maintenance of the
PremierOne Records system.
Course Materials
PremierOne Records System Administration Guide.
PremierOne SCOM Monitoring Guide.
Course Outline.
LXP refresher training courses.
Location
Customer’s facility.
Duration
Up to 16 hours over two consecutive business days.
Participants
System Administrators - personnel responsible for the day-to-day management of the
system.
Class Size
Maximum of four (4) attendees.
Prerequisite
LXP Required Prerequisite training courses:
ƒ PSA4029 System Administration - Hardware Overview
Knowledge of customer site network, IT policies and operations.
Microsoft proficiency as defined in the Prerequisites Section.
Environment Setup
Attendee Workstations:
ƒ Each workstation or device used for LXP prerequisites must have an internet
connection.
Instructional Requirements:
ƒ Instructor’s workstation(s) with network connection to the PremierOne servers.
ƒ Projector.
ƒ Dry erase board.
Use or disclosure of this proposal is subject to the restrictions on the cover page.Motorola Solutions
Page 191
Table 8-11: PremierOne GIS Administrator Workshop
PremierOne GIS Administrator Workshop
Goal
Provide the GIS Administrator the understanding to maintain the GIS data structure and
maintenance needs of the system to support GIS functionality areas: Address
Validation, Visual Map Displays, Routing, and Response Determination.
Course Materials
PremierOne Data Import Tools.
PremierOne GIS Configuration Guide.
Interactive GIS Admin Workshop Workbook.
Course Outline.
Location
Virtual
Duration
Up to twenty-four (24) hours over two weeks.
Participants
GIS Administrator and a secondary backup participant.
Class Size
Maximum of four (4) attendees.
Prerequisite
Working knowledge of current ESRI ArcDesktop and ArcGIS Pro.
Environment Setup
GIS Workstation Requirements:
ƒ Workstation must meet requirements listed in the GIS Admin Readiness Checklist.
Table 1-12: Convert on Demand (CoD) Workshop
Convert on Demand (CoD) Workshop
Goal
Provide the agency resource(s) with information necessary to use the CoD tool to
convert legacy Records Management data (i.e. case reports) to PremierOne Records
documents.
Course Materials
Convert on Demand Installation package and User Guide
Config Builder for Convert on Demand tool
Course Agenda
Location
On-Site
Duration
Up to twenty-four (24) hours over three (3) consecutive days.
Participants
Records Supervisor or Administrator
Class Size
Maximum of six (6) attendees.
Prerequisite
Thorough knowledge of legacy Records data and data elements
Microsoft SQL query writing skills
XML documents knowledge
Environment Setup
Legacy data must be in SQL database 2008 or greater
Need credentials that can be used to access SQL Server
Firewall must be open for SQL (port 1433) on both P1 Environment as well as
Legacy environments in order to make connection.
Workstation with NotePad++
Projector and whiteboard, if possible
8.3.2
Instructor-Led Course Descriptions
The following tables provide detailed descriptions of training courses that will be provided as part of the
system at the location indicated.
Use or disclosure of this proposal is subject to the restrictions on the cover page.Motorola Solutions
Page 192
Table 8-13: PremierOne CAD/Mobile Client Installation
PremierOne CAD/Mobile Client Installation
Goal
Provide selected personnel with knowledge to install PremierOne CAD and/or Mobile
client software on workstations. Includes prerequisite third-party software. If the
customer desires, an imaging solution can be presented.
Course Materials
PremierOne CAD Installation Guide.
PremierOne Mobile Windows Client Installation Guide.
PremierOne All-In-One (AIO) Installer Manual.
Motorola Mobile Map Installation Guide with PremierOne Mobile.
Course Outline.
LXP refresher training courses.
Location
Customer’s facility.
Duration
Up to 24 hours over three consecutive business days.
Participants
IT staff who are responsible for installing workstation software.
Class Size
Maximum of four (4) attendees
Prerequisite
Knowledge of Microsoft operating systems and basic software installation practices.
LXP Required Prerequisite training courses:
ƒ PSA0220 PremierOne CAD Client Installation
ƒ PSA0186 PremierOne Mobile Client Installation
Environment Setup
Attendee Workstations:
ƒ Each attendee should have a workstation that meets the minimum hardware
specifications for PremierOne CAD or Mobile software.
ƒ Workstations used for training should have connection to the PremierOne network
and user credentials to install software.
Instructional Requirements:
ƒ Instructor’s workstation(s) with network connection to the PremierOne servers.
ƒ Projector.
ƒ Dry erase board.
Table 8-14: PremierOne CAD Train-the-Trainer
PremierOne CAD Train-the-Trainer
Goal
Provide selected personnel with knowledge to support a comprehensive end user
training program.
Course Materials
PremierOne CAD User Guide.
CAD Online Help (accessible through the CAD Client).
Course Outline.
LXP refresher training courses.
Location
Customer’s facility.
Duration
Up to 32 hours over four consecutive business days on-site.
Approximately 6 hours of online prerequisite material.
Participants
Instructors who are responsible for the in house training of employees and for ongoing
user training.
Class Size
Maximum of twelve (12) attendees.
Use or disclosure of this proposal is subject to the restrictions on the cover page.Motorola Solutions
Page 193
PremierOne CAD Train-the-Trainer
Prerequisite
Knowledge of current CAD application and customer operations.
LXP Prerequisite training courses:
ƒ PSA4014 End User - CAD Client Overview.
ƒ PSA4007 End User - Logging In.
ƒ PSA4009 End User - Logging Off.
ƒ PSA4012 End User - Info Panel.
ƒ PSA4010 End User - Dynamic Help.
ƒ PSA4026 End User - Function Keys.
ƒ PSA4001 End User - Keyboard Shortcuts.
ƒ PSA4017 End User - Command Line & Punctuation.
ƒ PSA4013 End User - Clearing the Work Area.
ƒ PSA4016 End User - Location Verification.
Environment Setup
Attendee Workstations:
ƒ Each workstation or device used for LXP prerequisites must have an internet
connection.
ƒ One PremierOne CAD Workstation per attendee.
Instructional Requirements:
ƒ Instructor’s workstation(s) with network connection to the PremierOne servers.
ƒ Projector.
ƒ Dry erase board.
NOTE:
Allow two weeks from the end of train-the-trainer to the beginning of end user training
to allow customer to build site-specific documentation and outline for end user classes.
The Motorola Solutions Instructor will be available for remote consultation in producing
documentation and outline.
Table 8-15: PremierOne CAD End User Training
PremierOne CAD End User Training
Goal
Provide calltakers and dispatchers with the knowledge to effectively use PremierOne
CAD.
Course Materials
PremierOne CAD User Guide.
CAD Online Help (accessible through the CAD Client).
Course Outline.
LXP training courses.
Location
Customer’s facility.
Duration
Up to 32 hours over four consecutive business days on-site.
Approximately 6 hours of online prerequisite material.
Participants
Calltakers, dispatchers, supervisors and other users of the PremierOne CAD system.
Class Size
Maximum of twelve (12) attendees.
Use or disclosure of this proposal is subject to the restrictions on the cover page.Motorola Solutions
Page 194
PremierOne CAD End User Training
Prerequisite
Knowledge of current CAD application and customer operations.
LXP Prerequisite training courses:
ƒ PSA4014 End User - CAD Client Overview.
ƒ PSA4007 End User - Logging In.
ƒ PSA4009 End User - Logging Off.
ƒ PSA4012 End User - Info Panel.
ƒ PSA4010 End User - Dynamic Help.
ƒ PSA4026 End User - Function Keys.
ƒ PSA4001 End User - Keyboard Shortcuts.
ƒ PSA4017 End User - Command Line & Punctuation.
ƒ PSA4013 End User - Clearing the Work Area.
ƒ PSA4016 End User - Location Verification.
Environment Setup
Attendee Workstations:
ƒ Each workstation or device used for LXP prerequisites must have an internet
connection.
Instructional Requirements:
ƒ Instructor’s workstation(s) with network connection to the PremierOne servers.
ƒ Projector.
ƒ Dry erase board.
NOTE:
Allow two weeks from the end of train-the-trainer to the beginning of end user training
to allow time to build site-specific course outlines for end user classes.
Table 8-16: PremierOne Windows Mobile Training (Includes CAD and Records Mobile)
PremierOne Windows Mobile Training
Goal
Provide selected personnel with knowledge to support a comprehensive end user
training program.
Course Materials
PremierOne Mobile and PremierOne Records Mobile User Guides.
Course Outline.
Location
Customer’s facility
Duration
Six 4 hr. sessions over 3 consecutive 8 hr. days.
Participants
Instructors who are responsible for the in house training of employees and for ongoing
user training of PremierOne Windows Mobile
Class Size
Maximum of twelve (12) attendees
Use or disclosure of this proposal is subject to the restrictions on the cover page.Motorola Solutions
Page 195
PremierOne Windows Mobile Training
Prerequisite
Knowledge of current Mobile application and customer operations
LXP Prerequisite training courses:
ƒ PSA4043 End User - Logging On.
ƒ PSA4039 End User - Overview & Navigation.
ƒ PSA4041 End User - Mobile Sync.
ƒ PSA4047 End User - Incident & Unit History.
ƒ PSA4036 End User - Editing Capabilities and Skills.
ƒ PSA4045 End User - Monitored Agency/Areas.
ƒ PSA4223 End User - Unit Status.
ƒ PSA4224 End User - Self Dispatch.
ƒ PSA4225 End User - Stacked Incidents.
ƒ PSA4035 End User - Field Initiated Incidents.
ƒ PSA4042 End User – Queries.
ƒ PSA4046 End User - Generating Report Numbers.
ƒ PSA4040 End User - Logging Off.
Environment Setup
Attendee Workstations:
ƒ Windows Device for each attendee with applicable PremierOne Windows
applications installed
Instructional Requirements:
ƒ Instructor’s workstation(s) with network connection to the PremierOne Server.
ƒ Projector.
ƒ Dry erase board
Table 8-17: PremierOne Mobile for Android/iOS End User Training (Includes Responder)
PremierOne Mobile for Android and iOS End User Training
Goal
Through the LXP, provide a training program on the functionality of PremierOne Mobile
iOS and Android applications.
Course Materials
PremierOne Mobile iOS or Android User Guide.
Location
On Demand.
Duration
4 Hours.
Participants
PremierOne Mobile iOS or Android Users.
Use or disclosure of this proposal is subject to the restrictions on the cover page.Motorola Solutions
Page 196
PremierOne Mobile for Android and iOS End User Training
Prerequisite
Knowledge of customer’s current Mobile application and operations.
LXP Course Listings:
ƒ PSA0099 Provisioning - Unit Status Codes - Mobile/Handheld.
ƒ PSA0120 Mobile Android User - Logging in/Logging Out.
ƒ PSA0200 Mobile Android User - Navigating the Dashboard.
ƒ PSA0201 Mobile Android User - Using Queries (Law Only).
ƒ PSA0202 Mobile Android User - Using Mapping.
ƒ PSA0203 Mobile Android User - Managing Incidents.
ƒ PSA0204 Mobile Android User - Updating and Editing Incidents.
ƒ PSA0205 Mobile Android User - Managing Incidents (Law Only).
ƒ PSA0206 Mobile Android User - Using Status Monitors.
ƒ PSA0207 Mobile Android User - Viewing the Address Book.
ƒ PSA0208 Mobile Android User - Using Messaging.
ƒ PSA0209 Mobile Android User – Settings.
ƒ PSA0119 Mobile iOS User – Logging in/Logging Out.
ƒ PSA0210 Mobile iOS User – Navigating the Dashboard.
ƒ PSA0211 Mobile iOS User – Using Queries (Law Only).
ƒ PSA0212 Mobile iOS User – Using Mapping.
ƒ PSA0213 Mobile iOS User – Managing Incidents.
ƒ PSA0214 Mobile iOS User – Updating and Editing Incidents.
ƒ PSA0215 Mobile iOS User – Managing Incidents (Law Only).
ƒ PSA0216 Mobile iOS User – Using Status Monitors.
ƒ PSA0217 Mobile iOS User – Settings.
Environment Setup
Each workstation or device used for LXP training must have an internet connection.
Table 8-18: PremierOne Records Train-the-Trainer
PremierOne Records Train-the-Trainer
Goal
Provide selected personnel with knowledge to support a comprehensive end user
training program for the entire Records Application and all modules.
Course Materials
PremierOne Records Users Guide.
PremierOne Record Mobile User Guide.
LXP prerequisite training courses.
Course Outline.
Location
Customer’s facility.
Duration
Up to 32 hours over four consecutive business days
Participants
Instructors who are responsible for the in house training of employees and for ongoing
user training.
Class Size
Maximum of twelve (12) attendees.
Use or disclosure of this proposal is subject to the restrictions on the cover page.Motorola Solutions
Page 197
PremierOne Records Train-the-Trainer
Prerequisite
Knowledge of current FBR application and customer operations.
LXP Required Prerequisite training courses:
ƒ PSA4049 End User - Case Report.
ƒ PSA4050 End User - Pull Forward Feature.
ƒ PSA4051 End User - Case Reports/Report Writing.
ƒ PSA4053 End User - Document Workflow/Rollback.
ƒ PSA4054 End User - Messaging and Assignments.
ƒ PSA4038 End User - Query Smart Copy.
ƒ PSA4037 End User - Create Report Button.
Environment Setup
Attendee Workstations:
ƒ Each workstation or device used for LXP prerequisites must have an internet
connection.
ƒ One PremierOne Records Workstation per attendee.
Instructional Requirements:
ƒ Instructor’s workstation(s) with network connection to the PremierOne servers.
ƒ Projector.
ƒ Dry erase board.
NOTE
Allow two weeks from the end of train-the-trainer to the beginning of end user training
to allow customer to build site-specific documentation and outline for end user classes.
The Motorola Solutions Instructor will be available for remote consultation in producing
documentation and outline.
Table 8-19: PremierOne Records End User Training (Add-on)
PremierOne Records End User Training (Add-on)
Goal
Provide end users of PremierOne Records with knowledge of the system to create law
records and process the workflow and manage cases within the system.
Course Materials
PremierOne Users Guide.
LXP prerequisite training courses.
Course Outline.
Location
Customer’s facility.
Duration
Up to 32 hours over four consecutive business days
Participants
This course is designed for end users to learn and understand all aspects of the
PremierOne Records Application. If focused role based training is required, see
additional specific Instructor-Led training offerings.
Class Size
Maximum of twelve (12) attendees.
Prerequisite
Knowledge of current customer operations.
LXP Required Prerequisite training courses:
ƒ PSA4049 End User - Case Report.
ƒ PSA4050 End User - Pull Forward Feature.
ƒ PSA4051 End User - Case Reports/Report Writing.
ƒ PSA4053 End User - Document Workflow/Rollback.
ƒ PSA4054 End User - Messaging and Assignments.
ƒ PSA4038 End User - Query Smart Copy.
ƒ PSA4037 End User - Create Report Button.
Use or disclosure of this proposal is subject to the restrictions on the cover page.Motorola Solutions
Page 198
PremierOne Records End User Training (Add-on)
Environment Setup
Attendee Workstations:
ƒ Each workstation or device used for LXP prerequisites must have an internet
connection.
ƒ One PremierOne Records Workstation per attendee.
Instructional Requirements:
ƒ Instructor’s workstation(s) with network connection to the PremierOne servers.
ƒ Projector.
ƒ Dry erase board.
NOTE
Allow two weeks from the end of train-the-trainer to the beginning of end user training
to allow customers to build site-specific documentation and outline for end user
classes. The Motorola Solutions Instructor will be available for remote consultation in
producing documentation and outline.
Table 8-20: PremierOne Records Case Report Completion and Workflow End User Training
PremierOne Records Case Report Completion and Workflow End User Training
Goal
Provide end users of PremierOne Records with knowledge of the system to create law
records and process the workflow.
Course Materials
PremierOne Records Users Guide.
PremierOne Records Mobile User Guide.
LXP prerequisite training courses.
Course Outline.
Location
Customer’s facility.
Duration
Up to 32 hours over four consecutive business days
Participants
Law enforcement officers, supervisors
Class Size
Maximum of twelve (12) attendees.
Prerequisite
Knowledge of current customer operations.
LXP Required Prerequisite training courses:
ƒ PSA4049 End User - Case Report.
ƒ PSA4050 End User - Pull Forward Feature.
ƒ PSA4051 End User - Case Reports/Report Writing.
ƒ PSA4053 End User - Document Workflow/Rollback.
ƒ PSA4054 End User - Messaging and Assignments.
ƒ PSA4038 End User - Query Smart Copy.
ƒ PSA4037 End User - Create Report Button.
Environment Setup
Attendee Workstations:
ƒ Each workstation or device used for LXP prerequisites must have an internet
connection.
ƒ One PremierOne Records Workstation per attendee.
Instructional Requirements:
ƒ Instructor’s workstation(s) with network connection to the PremierOne servers.
ƒ Projector.
ƒ Dry erase board.
NOTE
Allow two weeks from the end of train-the-trainer to the beginning of end user training
to allow customers to build site-specific documentation and outline for end user
classes. The Motorola Solutions Instructor will be available for remote consultation in
producing documentation and outline.
Use or disclosure of this proposal is subject to the restrictions on the cover page.Motorola Solutions
Page 199
Table 8-21: PremierOne Records Case Management End User Training
PremierOne Records Case Management End User Training
Goal
Provide end users of PremierOne Records with knowledge of the system to manage
records that have been created through workflow and case management functions.
Course Materials
PremierOne Records Users Guide.
LXP prerequisite training courses.
Course Outline.
Location
Customer’s facility.
Duration
Up to 32 hours over four consecutive business days
Participants
Records clerks, supervisors, investigation staff.
Class Size
Maximum of twelve (12) attendees.
Prerequisite
Knowledge of customer operations.
LXP Required Prerequisite training courses:
ƒ PSA4049 End User - Case Report.
ƒ PSA4050 End User - Pull Forward Feature.
ƒ PSA4051 End User - Case Reports/Report Writing.
ƒ PSA4053 End User - Document Workflow/Rollback.
ƒ PSA4054 End User - Messaging and Assignments.
ƒ PSA4038 End User - Query Smart Copy.
ƒ PSA4037 End User - Create Report Button.
Environment Setup
Attendee Workstations:
ƒ Each workstation or device used for LXP prerequisites must have an internet
connection.
ƒ One PremierOne Records Workstation per attendee.
Instructional Requirements:
ƒ Instructor’s workstation(s) with network connection to the PremierOne servers.
ƒ Projector.
ƒ Dry erase board.
NOTE
Allow two weeks from the end of train-the-trainer to the beginning of end user training
to allow customers to build site-specific documentation and outline for end user
classes. The Motorola Solutions Instructor will be available for remote consultation in
producing documentation and outline.
Table 8-22: PremierOne Records Advanced Configuration Tool (ACT) Training
PremierOne Records ACT Training
Goal
To learn to make user interface (UI) modifications in PremierOne Records using the
Advanced Configuration Tool (ACT). ACT is a development tool provided for the
Customer’s use to make changes to forms, printouts, and navigation. The class will
provide guidelines for the allowable changes.
Course Materials
PremierOne Records Advanced Configuration Tool User Guide.
Course Outline.
Location
Virtual.
Duration
32 hours over four consecutive 8 hr. days.
Participants
Personnel responsible for system configuration.
Class Size
Maximum of four (4) attendees.
Use or disclosure of this proposal is subject to the restrictions on the cover page.Motorola Solutions
Page 200
PremierOne Records ACT Training
Prerequisite
Knowledge of current Records application and customer operations. Participants
should have a working knowledge of computer systems. Database knowledge is
preferable.
Environment Setup
Attendee Workstations:
ƒ One (1) workstation for each participant with an internet connection
Virtual Environment Browser Requirements:
ƒ The browser must support WebSockets in order to connect to CloudShare
environments and experiences.
ƒ The minimum bandwidth in order to connect to a Remote Desktop Protocol (RDP)
session is 150 Kbps.
NOTE
This class is not an extension of the PremierOne Records Provisioning class, and
requires an advanced level of expertise.
Use or disclosure of this proposal is subject to the restrictions on the cover page.
Page 201
Section 9
Exhibit E: Master Customer
Agreement & Addenda
EXHIBIT E
MASTER CUSTOMER AGREEMENT
This Master Customer Agreement (the “MCA”) is entered into between Motorola Solutions, Inc., with
offices at 500 W. Monroe Street, Suite 4400, Chicago, IL 60661 (“Motorola”) and Maricopa County
(“Customer”). Motorola and Customer will each be referred to herein as a “Party” and collectively as
the “Parties
1.
Agreement.
1.1.
Scope; Agreement Documents. This MCA governs Customer’s purchase of Products (as
defined below) and Services (as defined below) from Motorola. Additional terms and conditions
applicable to specific Products and Services are set forth in one or more addenda attached to this MCA
(each an “Addendum”, and collectively the “Addenda”). In addition, the Parties may agree upon
solution descriptions, equipment lists, statements of work, schedules, technical specifications, and
other ordering documents setting forth the Products and Services to be purchased by Customer and
provided by Motorola and additional rights and obligations of the Parties (the “Ordering Documents”).
To the extent required by applicable procurement law, a proposal submitted by Motorola in response to
a competitive procurement process will be included within the meaning of the term Ordering
Documents. This MCA, the Addenda, and any Ordering Documents collectively form the “Agreement”.
1.2.
Order of Precedence. Each Addendum will control with respect to conflicting terms in the MCA,
but only as applicable to the Products and Services described in such Addendum. Each Ordering
Document will control with respect to conflicting terms in the MCA or any Addenda, but only as
applicable to the Products and Services described on such Ordering Document. This Agreement is
subject to the terms of Maricopa County Contract 2300225-RFP (“2300225-RFP”) and this MCA is
attached to 2300225-RFP as Exhibit E. 2300225-RFP will control with respect to conflicting terms in
this Agreement.
2.
Products and Services.
2.1.
Products. Motorola will (a) sell hardware provided by Motorola (“Equipment”), (b) license
software which is either preinstalled on Equipment or installed on Customer-Provided Equipment (as
defined below) and licensed to Customer by Motorola for a perpetual or other defined license term
(“Licensed Software”), and (c) license cloud-based software as a service products and other software
which is either preinstalled on Equipment or installed on Customer-Provided Equipment, but licensed to
Customer by Motorola on a subscription basis (“Subscription Software”) to Customer, to the extent
each is set forth in an Ordering Document, for Customer’s own use in accordance with this Agreement.
The Equipment, Licensed Software, and Subscription Software shall collectively be referred to herein
as “Products”, or individually as a “Product”. At any time during the Term (as defined below), Motorola
may substitute any Products at no cost to Customer, if the substitute is substantially similar to the
Products set forth in the applicable Ordering Documents.
Use or disclosure of this proposal is subject to the restrictions on the cover page.
Page 202
2.1
Services.
2.2.1. Motorola will provide services related to purchased Products (“Services”), to the extent
set forth in an Ordering Document.
2.2.2. Integration Services; Maintenance and Support Services. If specified in an Ordering
Document, Motorola will provide, for the term of such Ordering Document, (a) design,
deployment, and integration Services in order to design, install, set up, configure, and/or
integrate the applicable Products at the applicable locations (“Sites”), agreed upon by
the Parties (“Integration Services”), or (b) break/fix maintenance, technical support, or
other Services (such as software integration Services) (“Maintenance and Support
Services”), each as further described in the applicable statement of work. Maintenance
and Support Services and Integration Services will each be considered “Services”, as
defined above.
2.2.3. Service Ordering Documents. The Fees for Services will be set forth in an Ordering
Document and any applicable project schedules. A Customer point of contact will be set
forth in the applicable statement of work for the Services. For purposes of clarity, each
statement of work will be incorporated into, and form an integral part of, the Agreement.
2.2.4. Service Completion. Unless otherwise specified in the applicable Ordering Document,
Services described in an Ordering Document will be deemed complete upon Motorola’s
performance of all Services listed in such Ordering Document (“Service Completion
Date”); any written approval by both Parties; provided, however, that Maintenance and
Support Services may be offered on an ongoing basis during a given Ordering
Document term, in which case such Maintenance and Support Services will conclude
upon the expiration or termination of such Ordering Document.
2.3.
Non-Preclusion. If, in connection with the Products and Services provided under this
Agreement, Motorola makes recommendations, including a recommendation to purchase other
products or services, nothing in this Agreement precludes Motorola from participating in a future
competitive bidding process or otherwise offering or selling the recommended products or other
services to Customer.
2.4.
Customer Obligations. Customer will ensure that information Customer provides to Motorola in
connection with receipt of Products and Services are accurate and complete in all material respects.
Customer will make timely decisions and obtain any required management approvals that are
reasonably necessary for Motorola to provide the Products and Services and perform its other duties
under this Agreement. Unless the applicable Ordering Document states otherwise, Motorola may rely
upon and is not required to evaluate, confirm, reject, modify, or provide advice concerning any
assumptions or Customer information, decisions, or approvals described in this Section. If any
assumptions in the Ordering Documents or information provided by Customer prove to be incorrect, or
if Customer fails to perform any of its obligations under this Agreement, Motorola’s ability to perform its
obligations may be impacted and changes to the Agreement, including the scope, Fees, and
performance schedule may be required.
2.5
Documentation. Products and Services may be delivered with documentation for the Equipment,
software Products, or data that specifies technical and performance features, capabilities, users, or
operation, including training manuals, and other deliverables, such as reports, specifications, designs,
plans, drawings, analytics, or other information (collectively, “Documentation”). Documentation is and
will be owned by Motorola, unless otherwise expressly agreed in an Addendum or Ordering Document
Use or disclosure of this proposal is subject to the restrictions on the cover page.
Page 203
that certain Documentation will be owned by Customer. Motorola hereby grants Customer a limited,
royalty-free, worldwide, non-exclusive license to use the Documentation solely for its internal business
purposes in connection with the Products and Services.
2.6
Motorola Tools and Equipment. As part of delivering the Products and Services, Motorola may
provide certain tools, equipment, models, and other materials of its own. Such tools and equipment will
remain the sole property of Motorola unless they are to be purchased by Customer as Products and are
explicitly listed on an Ordering Document. The tools and equipment may be held by Customer for
Motorola’s use without charge and may be removed from Customer’s premises by Motorola at any time
without restriction. Customer will safeguard all tools and equipment while in Customer’s custody or
control, and be liable for any loss or damage. Upon the expiration or earlier termination of this
Agreement, Customer, at its expense, will return to Motorola all tools and equipment in its possession
or control.
2.7
Authorized Users. Customer will ensure its employees and Authorized Users comply with the
terms of this Agreement and will be liable for all acts and omissions of its employees and Authorized
Users. Customer is responsible for the secure management of Authorized Users’ names, passwords
and login credentials for access to Products and Services. “Authorized Users” are Customer’s
employees, full-time contractors engaged for the purpose of supporting the Products and Services, and
the entities (if any) specified in an Ordering Document or otherwise approved by Motorola in writing
(email from an authorized Motorola signatory accepted), which may include affiliates or other Customer
agencies.
2.8
Export Control. Customer, its employees, and any other Authorized Users will not access or use
the Products and Services in any jurisdiction in which the provision of such Products and Services is
prohibited under applicable laws or regulations (a “Prohibited Jurisdiction”), and Customer will not
provide access to the Products and Services to any government, entity, or individual located in a
Prohibited Jurisdiction. Customer represents and warrants that (a) it and its Authorized Users are not
named on any U.S. government list of persons prohibited from receiving U.S. exports, or transacting
with any U.S. person; (b) it and its Authorized Users are not a national of, or a company registered in,
any Prohibited Jurisdiction; (c) Customer will not permit its Authorized Users to access or use the
Products or Services in violation of any U.S. or other applicable export embargoes, prohibitions or
restrictions; and (d) Customer and its Authorized Users will comply with all applicable laws regarding
the transmission of technical data exported from the U.S. and the country in which Customer, its
employees, and the Authorized Users are located.
2.9
Change Orders. Unless a different change control process is agreed upon in writing by the
Parties, a Party may request changes to an Addendum or an Ordering Document by submitting a
change order to the other Party (each, a “Change Order”). If a requested change in a Change Order
causes an increase or decrease in the Products or Services, the Parties by means of the Change Order
will make appropriate adjustments to the Fees, project schedule, or other matters. Change Orders are
effective and binding on the Parties only upon execution of the Change Order by an authorized
representative of both Parties.
3.
Term and Termination.
3.1
Term. The term of this MCA (“Term”) will commence on the Effective Date and will run
concurrent with the term of 2300225-RFP.
3.2.
Intentionally Omitted.
3.3.
Intentionally Omitted.
3.4.
Intentionally Omitted.
Use or disclosure of this proposal is subject to the restrictions on the cover page.
Page 204
3.5.
Intentionally Omitted.
4.
Intentionally Omitted.
5.
Sites; Customer-Provided Equipment; Non-Motorola Content.
5.1.
Customer-Provided Equipment. Certain components, including equipment and software, not
provided by Motorola may be required for use of the Products and Services (“Customer-Provided
Equipment”). Customer will be responsible, at its sole cost and expense, for providing and maintaining
the Customer-Provided Equipment in good working order. Customer represents and warrants that it has
all rights in Customer-Provided Equipment to permit Motorola to access and use the applicable
Customer-Provided Equipment to provide the Products and Services under this Agreement, and such
access and use will not violate any laws or infringe any third-party rights (including intellectual property
rights). Customer (and not Motorola) will be fully liable for Customer-Provided Equipment, and
Customer will immediately notify Motorola of any Customer-Provided Equipment damage, loss, change,
or theft that may impact Motorola’s ability to provide the Products and Services under this Agreement,
and Customer acknowledges that any such events may cause a change in the Fees or performance
schedule under the applicable Ordering Document.
5.2.
Non-Motorola Content. In certain instances, Customer may be permitted to access, use, or
integrate Customer or third-party software, services, hardware, content, and data that is not provided by
Motorola (collectively, “Non-Motorola Content”) with or through the Products and Services. If Customer
accesses, uses, or integrates any Non-Motorola Content with the Products or Services, Customer will
first obtain all necessary rights and licenses to permit Customer’s and its Authorized Users’ use of the
Non-Motorola Content in connection with the Products and Services. Customer represents and
warrants that it will obtain the foregoing rights and licenses prior to accessing, using, or integrating the
applicable Non-Motorola Content with the Products and Services, and that Customer and its Authorized
Users will comply with any terms and conditions applicable to such Non-Motorola Content. If any Non-
Motorola Content require access to Customer Data (as defined below), Customer with prior written
approval may authorize Motorola to allow the provider of such Non-Motorola Content to access
Customer Data, in connection with the interoperation of such Non-Motorola Content with the Products
and Services. Customer acknowledges and agrees that Motorola is not responsible for, and makes no
representations or warranties with respect to, the Non-Motorola Content (including any disclosure,
modification, or deletion of Customer Data resulting from use of Non-Motorola Content or failure to
properly interoperate with the Products and Services). If Customer receives notice from a third-party
providing Non-Motorola Content that any Non-Motorola Content must be removed, modified, or
disabled within the Products or Services, Customer will promptly do so. Motorola will have the right to
request that Customer disable or remove Non-Motorola Content if a violation of law occurs or if such
Non-Motorola Content poses a security or other risk or adverse impact to the Products or Services.
Motorola may provide certain Non-Motorola Content as an authorized sales representative of a third
party as set out in an Ordering Document. As an authorized sales representative, the third party’s terms
and conditions, as set forth in the Ordering Document, will apply to any such sales. Any orders for such
Non-Motorola Content will be filled by the third party. Nothing in this Section will limit the exclusions set
forth in Intellectual Property Infringement section of the Contract.
5.3.
End User Licenses. Notwithstanding any provision to the contrary in the Agreement, certain
Non-Motorola Content software are governed by a separate license, EULA, or other agreement,
including terms governing third-party equipment or software, such as open source software, included in
the Products and Services. Customer will comply, and ensure its Authorized Users comply, with any
such additional terms applicable to third-party equipment or software. If provided for in the separate
third party license, Customer may have a right to receive source code for such software; a copy of such
source code may be obtained free of charge by contacting Motorola.
Use or disclosure of this proposal is subject to the restrictions on the cover page.
Page 205
6.
Intentionally Omitted.
7.
Intentionally Omitted.
8.
Intentionally Omitted.
9.
Intentionally Omitted.
10. Proprietary Rights; Data; Feedback.
10.1.
Data Definitions. The following terms will have the stated meanings: “Customer Contact Data”
means data Motorola collects from Customer, its Authorized Users, and their end users for business
contact purposes, including marketing, advertising, licensing and sales purposes; “Service Use Data”
means data generated by Customer’s use of the Products and Services or by Motorola’s support of the
Products and Services, including personal information, product performance and error information,
activity logs and date and time of use; “Customer Data” means data, information, and content,
including images, text, videos, documents, audio, telemetry, location and structured data base records,
provided by, through, or on behalf of Customer, its Authorized Users, and their end users through the
use of the Products and Services. Customer Data does not include Customer Contact Data, Service
Use Data, or information from publicly available sources or other Third-Party Data or Motorola Data;
“Third-Party Data” means information obtained by Motorola from publicly available sources or its third
party content providers and made available to Customer through the Products or Services; “Motorola
Data” means data owned or licensed by Motorola; “Feedback” means comments or information, in oral
or written form, given to Motorola by Customer or Authorized Users, including their end users, in
connection with or relating to the Products or Services; and “Process” or “Processing” means any
operation or set of operations which is performed on personal information or on sets of personal
information, whether or not by automated means, such as collection, recording, copying, analyzing,
caching, organization, structuring, storage, adaptation, or alteration, retrieval, consultation, use,
disclosure by transmission, dissemination or otherwise making available, alignment or combination,
restriction, erasure or destruction.
10.2.
Motorola Materials. Customer acknowledges that Motorola may use or provide Customer with
access to software, tools, data, and other materials, including designs, utilities, models, methodologies,
systems, and specifications, which Motorola has developed or licensed from third parties (including any
corrections, bug fixes, enhancements, updates, modifications, adaptations, translations, de-
compilations, disassemblies, or derivative works of the foregoing, whether made by Motorola or another
party) (collectively, “Motorola Materials”). The Products and Services, Motorola Data, Third-Party
Data, and Documentation, are considered Motorola Materials. Except when Motorola has expressly
transferred title or other interest to Customer by way of an Addendum or Ordering Document, the
Motorola Materials are the property of Motorola or its licensors, and Motorola or its licensors retain all
right, title and interest in and to the Motorola Materials (including, all rights in patents, copyrights,
trademarks, trade names, trade secrets, know-how, other intellectual property and proprietary rights,
and all associated goodwill and moral rights). For clarity, this Agreement does not grant to Customer
any shared development rights in or to any Motorola Materials or other intellectual property, and
Customer agrees to execute any documents and take any other actions reasonably requested by
Motorola to effectuate the foregoing. Motorola and its licensors reserve all rights not expressly granted
to Customer, and no rights, other than those expressly granted herein, are granted to Customer by
implication, estoppel or otherwise. Customer will not modify, disassemble, reverse engineer, derive
source code or create derivative works from, merge with other software, distribute, sublicense, sell, or
export the Products and Services or other Motorola Materials, or permit any third party to do so.
10.3.
Ownership of Customer Data. Customer retains all right, title and interest, including intellectual
property rights, if any, in and to Customer Data. Motorola acquires no rights to Customer Data except
Use or disclosure of this proposal is subject to the restrictions on the cover page.
Page 206
those rights granted under this Agreement including the right to Process and use the Customer Data as
set forth in Section 10.4 – Processing Customer Data below and in other applicable Addenda. The
Parties agree that with regard to the Processing of personal information which may be part of Customer
Data, Customer is the controller and Motorola is the processor, and may engage sub-processors
pursuant to Section 10.4.3 – Sub-processors.
10.4.
Processing Customer Data.
10.4.1.
Motorola Use of Customer Data. To the extent permitted by law, Customer grants
Motorola and its subcontractors a right to use Customer Data and a royalty-free,
worldwide, non-exclusive license to use Customer Data (including to process, host,
cache, store, reproduce, copy, modify, combine, analyze, create derivative works
from such Customer Data and to communicate, transmit, and distribute such
Customer Data to third parties engaged by Motorola) to (a) perform Services and
provide Products under the Agreement, (b) analyze the Customer Data to operate,
maintain, manage, and improve Motorola Products and Services, and (c) create new
products and services.
10.4.2.
Collection, Creation, Use of Customer Data. Customer further represents and
warrants that the Customer Data, Customer’s collection, creation, and use of the
Customer Data (including in connection with Motorola’s Products and Services), and
Motorola’s use of such Customer Data in accordance with the Agreement, will
comply with all laws and will not violate any applicable privacy notices or infringe any
third-party rights (including intellectual property and privacy rights). It is Customer’s
responsibility to obtain all required consents, provide all necessary notices, and meet
any other applicable legal requirements with respect to collection and use (including
Motorola’s use) of the Customer Data as described in the Agreement.
10.4.3.
Sub-processors. Customer agrees that Motorola may engage sub-processors who in
turn may engage additional sub-processors to Process personal data in accordance
with this Agreement. When engaging sub-processors, Motorola will enter into
agreements with the sub-processors to bind them to data processing obligations to
the extent required by law.
10.5.
Data Retention and Deletion. Except as expressly provided otherwise under the Agreement,
Motorola will delete all Customer Data following termination or expiration of this MCA or the applicable
Addendum or Ordering Document, with such deletion to occur no later than ninety (90) days following
the applicable date of termination or expiration, unless otherwise required to comply with applicable
law. Any requests for the exportation or download of Customer Data must be made by Customer to
Motorola in writing before expiration or termination, subject to Section 13.8 – Notices. Motorola will
have no obligation to retain such Customer Data beyond expiration or termination unless the Customer
has purchased extended storage from Motorola through a mutually executed Ordering Document.
10.6.
Service Use Data. Customer understands and agrees that Motorola may collect and use
Service Use Data for its own purposes, including the uses described below. Motorola may use Service
Use Data to (a) operate, maintain, manage, and improve existing and create new products and
services, (b) test products and services, (c) to aggregate Service Use Data and combine it with that of
other users, and (d) to use anonymized or aggregated data for marketing, research or other business
purposes. Service Use Data may be disclosed to third parties. It is Customer’s responsibility to notify
Authorized Users of Motorola’s collection and use of Service Use Data and to obtain any required
consents, provide all necessary notices, and meet any other applicable legal requirements with respect
to such collection and use, and Customer represents and warrants to Motorola that it has complied and
will continue to comply with this Section.
Use or disclosure of this proposal is subject to the restrictions on the cover page.
Page 207
10.7
Third-Party Data and Motorola Data. Motorola Data and Third-Party Data may be available to
Customer through the Products and Services. Customer and its Authorized Users may use Motorola
Data and Third-Party Data as permitted by Motorola and the applicable Third-Party Data provider, as
described in the applicable Addendum. Unless expressly permitted in the applicable Addendum,
Customer will not, and will ensure its Authorized Users will not: (a) use the Motorola Data or Third-Party
Data for any purpose other than Customer’s internal business purposes; (b) disclose the data to third
parties; (c) “white label” such data or otherwise misrepresent its source or ownership, or resell,
distribute, sublicense, or commercially exploit the data in any manner; (d) use such data in violation of
applicable laws; (e) remove, obscure, alter, or falsify any marks or proprietary rights notices indicating
the source, origin, or ownership of the data; or (f) modify such data or combine it with Customer Data or
other data or use the data to build databases. Additional restrictions may be set forth in the applicable
Addendum. Any rights granted to Customer or Authorized Users with respect to Motorola Data or Third-
Party Data will immediately terminate upon termination or expiration of the applicable Addendum,
Ordering Document, this MCA, or 2300225-RFP. Further, Motorola or the applicable Third-Party Data
provider may suspend, change, or terminate Customer’s or any Authorized User’s access to Motorola
Data or Third-Party Data if Motorola or such Third-Party Data provider believes Customer’s or the
Authorized User’s use of the data violates the Agreement, applicable law or Motorola’s agreement with
the applicable Third-Party Data provider. Upon termination of Customer’s rights to use any Motorola
Data or Third-Party Data, Customer and all Authorized Users will immediately discontinue use of such
data, delete all copies of such data, and certify such deletion to Motorola. Notwithstanding any
provision of the Agreement to the contrary, Motorola will have no liability for Third-Party Data or
Motorola Data available through the Products and Services. Motorola and its Third-Party Data providers
reserve all rights in and to Motorola Data and Third-Party Data not expressly granted in an Addendum
or Ordering Document.
10.8
Feedback. Any Feedback provided by Customer is entirely voluntary, and will not create any
confidentiality obligation for Motorola, even if designated as confidential by Customer. Motorola may
use, reproduce, license, and otherwise distribute and exploit the Feedback without any obligation or
payment to Customer or Authorized Users and Customer represents and warrants that it has obtained
all necessary rights and consents to grant Motorola the foregoing rights.
10.9
Improvements; Products and Services. The Parties agree that, notwithstanding any provision of
this MCA or the Agreement to the contrary, all fixes, modifications and improvements to the Services or
Products conceived of or made by or on behalf of Motorola that are based either in whole or in part on
the Feedback, Customer Data, or Service Use Data (or otherwise) are the exclusive property of
Motorola and all right, title and interest in and to such fixes, modifications or improvements will vest
solely in Motorola. Customer agrees to execute any written documents necessary to assign any
intellectual property or other rights it may have in such fixes, modifications or improvements to
Motorola.
11.
Delays Caused by Customer.
Motorola’s performance of the Products and Services will be excused for delays caused by Customer
or its Authorized Users or subcontractors, or by failure of any assumptions set forth in this Agreement
(including in any Addendum or Ordering Document). In the event of a delay under this Section 11 –
Delays Caused by Customer, (a) Customer will continue to pay the Fees as required hereunder, (b)
the Parties will agree (in writing) upon a reasonable extension to any applicable performance schedule,
and (c) Customer will compensate Motorola for its out-of-pocket costs incurred due to the delay
(including those incurred by Motorola’s affiliates, vendors, and subcontractors).
12
Disputes. The Parties will use the following procedure to resolve any disputes relating to or
arising out of this Agreement (each, a “Dispute”):
Use or disclosure of this proposal is subject to the restrictions on the cover page.
Page 208
12.1.
Governing Law. All matters relating to or arising out of the Agreement are governed by the laws
of the State of Arizona, unless Customer is the United States Government (or an agency thereof), in
which case all matters relating to or arising out of the Agreement will be governed by the laws of the
State in which the Products and Services are provided. The terms of the U.N. Convention on Contracts
for the International Sale of Goods and the Uniform Computer Information Transactions Act will not
apply.
12.2.
Negotiation; Mediation. Either Party may initiate dispute resolution procedures by sending a
notice of Dispute (“Notice of Dispute”) to the other Party. The Parties will attempt to resolve the Dispute
promptly through good faith negotiations, including timely escalation of the Dispute to executives who
have authority to settle the Dispute (and who are at a higher level of management than the persons
with direct responsibility for the matter). All in person meetings under this Section 12.2 – Negotiation;
Mediation will take place in Maricopa County, Arizona, and all communication relating to the Dispute
resolution will be maintained in strict confidence by the Parties. Notwithstanding the foregoing, any
Dispute arising from or relating to Motorola’s intellectual property rights will not be subject to negotiation
or mediation in accordance with this Section, but instead will be decided by a court of competent
jurisdiction, in accordance with Section 12.3 – Litigation, Venue, Jurisdiction below.
12.3.
Litigation, Venue, Jurisdiction. If the Dispute has not been resolved by mediation within sixty
(60) days from the Notice of Mediation, either Party may submit the Dispute exclusively to a court in
Maricopa County, Arizona. Each Party expressly consents to the exclusive jurisdiction of such courts
for resolution of any Dispute and to enforce the outcome of any mediation.
13.
General.
13.1.
Compliance with Laws. Each Party will comply with applicable laws in connection with the
performance of its obligations under this Agreement, including that Customer will ensure its and its
Authorized Users’ use of the Products and Services complies with law (including privacy laws), and
Customer will obtain any FCC and other licenses or authorizations (including licenses or authorizations
required by foreign regulatory bodies) required for its and its Authorized Users’ use of the Products and
Services. Motorola may, at its discretion, cease providing or otherwise modify Products and Services
(or any terms related thereto in an Addendum or Ordering Document), in order to comply with any
changes in applicable law.
13.2.
Audit; Monitoring. Motorola will have the right to monitor and audit use of the Products, which
may also include access by Motorola to Customer Data and Service Use Data. Customer will provide
notice of such monitoring to its Authorized Users and obtain any required consents, including individual
end users, and will cooperate with Motorola in any monitoring or audit. Customer will maintain during
the Term, and for two (2) years thereafter, accurate records relating to any software licenses granted
under this Agreement to verify compliance with this Agreement.
13.3.
Intentionally Omitted.
13.4.
Waiver. A delay or omission by either Party to exercise any right under this Agreement will not
be construed to be a waiver of such right. A waiver by either Party of any of the obligations to be
performed by the other, or any breach thereof, will not be construed to be a waiver of any succeeding
breach or of any other obligation. All waivers must be in writing and signed by the Party waiving its
rights.
13.5.
Severability. If any provision of the Agreement is found by a court of competent jurisdiction to be
invalid, illegal, or otherwise unenforceable, such provision will be deemed to be modified to reflect as
nearly as possible the original intentions of the Parties in accordance with applicable law. The
Use or disclosure of this proposal is subject to the restrictions on the cover page.
Page 209
remaining provisions of this Agreement will not be affected, and each such provision will be valid and
enforceable to the full extent permitted by applicable law.
13.6.
Third-Party Beneficiaries. The Agreement is entered into solely between, and may be enforced
only by, the Parties. Each Party intends that the Agreement will not benefit, or create any right or cause
of action in or on behalf of, any entity other than the Parties. Notwithstanding the foregoing, a licensor
or supplier of third-party software included in the software Products will be a direct and intended third-
party beneficiary of this Agreement.
13.7.
Interpretation. The section headings in this Agreement are included only for convenience. The
words “including” and “include” will be deemed to be followed by the phrase “without limitation”. This
Agreement will be fairly interpreted in accordance with its terms and conditions and not for or against
either Party.
13.8.
Notices. Notices required under this Agreement to be given by one Party to the other must be in
writing and either personally delivered or sent to the address provided by the other Party by certified
mail, return receipt requested and postage prepaid (or by a recognized courier service, such as FedEx,
UPS, or DHL), and will be effective upon receipt.
13.9.
Cumulative Remedies. Except as specifically stated in this Agreement, all remedies provided for
in this Agreement will be cumulative and in addition to, and not in lieu of, any other remedies available
to either Party at law, in equity, by contract, or otherwise. Except as specifically stated in this
Agreement, the election by a Party of any remedy provided for in this Agreement or otherwise available
to such Party will not preclude such Party from pursuing any other remedies available to such Party at
law, in equity, by contract, or otherwise.
13.10. Survival. The following provisions will survive the expiration or termination of this Agreement for
any reason: Section 10 – Proprietary Rights; Data; Feedback; Section 11 –Delays Caused by
Customer; Section 12 – Disputes; and Section 13 – General.
Use or disclosure of this proposal is subject to the restrictions on the cover page.
Page 210
Equipment Purchase and Software License Addendum
This Equipment Purchase and Software License Addendum (this “EPSLA”) is entered into between
Motorola Solutions, Inc., with offices at 500 W. Monroe Street, Suite 4400, Chicago, IL 60661
(“Motorola”) and Maricopa County (“Customer”), and will be subject to, and governed by, the terms of
the Motorola Solutions Customer Agreement entered into between the Parties (the “MCA”). Capitalized
terms used in this EPSLA, but not defined herein, will have the meanings set forth in the MCA.
1.
Addendum. This EPSLA governs Customer’s purchase of Equipment and license of Licensed
Software (and, if set forth in an Ordering Document, related Services) from Motorola, and will form
part of the Parties’ Agreement.
2.
Delivery of Equipment and Licensed Software.
2.1.
Delivery and Risk of Loss. Motorola will provide to Customer the Products (and, if applicable,
related Services) set forth in an Ordering Document, in accordance with the terms of the Agreement.
Motorola will, using commercially reasonable practices, pack the ordered Equipment and ship such
Equipment to the Customer address set forth in the applicable Ordering Document or otherwise
provided by Customer in writing, using a carrier selected by Motorola. Notwithstanding the foregoing,
delivery of Equipment (and any incorporated Licensed Software) will occur, and title and risk of loss for
the Equipment will pass to Customer, upon shipment by Motorola in accordance with Ex Works,
Motorola’s premises (Incoterms 2020). Customer will pay all shipping costs, taxes, and other charges
applicable to the shipment and import or export of the Products and Services, as applicable, and
Customer will be responsible for reporting the Products for personal property tax purposes. Delivery of
Licensed Software for installation on Equipment or Customer-Provided Equipment will occur upon the
earlier of (a) electronic delivery of the Licensed Software by Motorola, and (b) the date Motorola
otherwise makes the Licensed Software available for download by Customer. If agreed upon in an
Ordering Document, Motorola will also provide Services related to such Products.
2.2
Delays. Any shipping dates set forth in an Ordering Document are approximate, and while
Motorola will make reasonable efforts to ship Products by any such estimated shipping date, Motorola
will not be liable for any delay or related damages to Customer. Time for delivery will not be of the
essence, and delays will not constitute grounds for cancellation, penalties, termination, or a refund.
3.
Licensed Software License and Restrictions.
3.1.
Licensed Software License. Subject to Customer’s and its Authorized Users’ compliance with
the Agreement (including payment terms), Motorola hereby grants Customer and its Authorized Users a
limited, non-transferable, non-sublicenseable, and non-exclusive license to use the Licensed Software
identified in an Ordering Document, in object code form only, and the associated Documentation, solely
in connection with the Equipment provided by Motorola or authorized Customer-Provided Equipment
(as applicable, the “Designated Products”) and solely for Customer’s internal business purposes.
Unless otherwise stated in an Addendum or the Ordering Document, the foregoing license grant will be
limited to the number of licenses set forth in the applicable Ordering Document and will continue for the
life of the applicable Designated Product. Except as otherwise permitted in an applicable Addendum or
Ordering Document, Customer may install, access, and use Licensed Software only in Customer’s
owned or controlled facilities, including any authorized mobile sites; provided, however, that Authorized
Users using authorized mobile or handheld devices may also log into and access the Licensed
Software remotely from any location.
3.2.
Subscription License Model. If the Parties mutually agree that any Licensed Software purchased
under this EPSLA will be replaced with or upgraded to Subscription Software, then upon such time
which the Parties execute the applicable Ordering Document, the licenses granted under this EPSLA
Use or disclosure of this proposal is subject to the restrictions on the cover page.
Page 211
will automatically terminate, and such Subscription Software will be governed by the terms of the
applicable Addendum under this Agreement.
3.3.
Customer Restrictions. Customers and Authorized Users will comply with the applicable
Documentation in connection with their use of the Products. Customer will not and will not allow others,
including the Authorized Users, to: (a) make the Licensed Software available for use by unauthorized
third parties, including via a commercial rental or sharing arrangement; (b) reverse engineer,
disassemble, or reprogram the Licensed Software or any portion thereof to a human-readable form; (c)
modify, create derivative works of, or merge the Licensed Software with other software or equipment;
(d) copy, reproduce, distribute, lend, lease, or transfer the Licensed Software or Documentation for or
to any third party without the prior express written permission of Motorola; (e) take any action that
would cause the Licensed Software or Documentation to be placed in the public domain; (f) use the
Licensed Software to compete with Motorola; or (g) remove, alter, or obscure, any copyright or other
notice.
3.4.
Copies. Customer may make one (1) copy of the Licensed Software solely for archival, back-up,
or disaster recovery purposes during the term of the applicable Licensed Software license. Customer
may make as many copies of the Documentation reasonably required for the internal use of the
Licensed Software during such Licensed Software’s license term. Unless otherwise authorized by
Motorola in writing, Customer will not, and will not enable or allow any third party to: (a) install a
licensed copy of the Licensed Software on more than one (1) unit of a Designated Product; or (b) copy
onto or transfer Licensed Software installed in a unit of a Designated Product onto another device.
Customer may temporarily transfer Licensed Software installed on a Designated Product to another
device if the Designated Product is inoperable or malfunctioning, if Customer provides written notice to
Motorola of the temporary transfer and identifies the device on which the Licensed is transferred.
Temporary transfer of the Licensed Software to another device must be discontinued when the original
Designated Product is returned to operation and the Licensed Software must be removed from the
other device. Customer must provide prompt written notice to Motorola at the time temporary transfer is
discontinued.
3.5.
Resale of Equipment. Equipment contains embedded Licensed Software. If Customer desires to
sell its used Equipment to a third party, Customer must first receive prior written authorization from
Motorola and obtain written acceptance of the applicable Licensed Software license terms, including
the obligation to pay relevant license fees, from such third party.
4.
Intentionally Omitted.
5.
Intentionally Omitted.
6.
Representations and Warranties.
6.1.
Motorola Warranties. Subject to the disclaimers and exclusions set forth in the MCA and this
EPSLA, (a) for a period of one (1) year commencing upon the delivery of Motorola-manufactured
Equipment under Section 2.1 – Delivery and Risk of Loss, Motorola represents and warrants that such
Motorola-manufactured Equipment, under normal use, will be free from material defects in materials
and workmanship; (b) to the extent permitted by the providers of third-party software or hardware
included in the Products and Services, Motorola will pass through to Customer any warranties provided
by such third parties, which warranties will apply for the period defined by the applicable third party; and
(c) for a period of ninety (90) days commencing upon the delivery of Motorola-owned Licensed
Software under Section 2.1 – Delivery and Risk of Loss, Motorola represents and warrants that such
Licensed Software, when used in accordance with the Documentation and the Agreement, will be free
from reproducible defects that prevent operation of features critical to the primary functionality or
successful operation of the Motorola-developed Licensed Software (as determined by Motorola). The
Use or disclosure of this proposal is subject to the restrictions on the cover page.
Page 212
warranty set forth in subsection (c) will be referred to as the “Motorola Licensed Software Warranty”. As
Customer’s sole and exclusive remedy for any breach of the Motorola Licensed Software Warranty,
Motorola will use commercially reasonable efforts to remedy the material defect in the applicable
Licensed Software; provided, however, that if Motorola does not remedy such material defect within a
reasonable time, then at Motorola’s sole option, Motorola will either replace the defective Licensed
Software with functionally-equivalent software, provide substitute software to Customer, or terminate
the applicable software license and refund any paid license fees to Customer on a pro-rata basis. For
clarity, the Motorola Licensed Software Warranty applies only to the most current version of the
Licensed Software issued by Motorola, and issuance of updated versions of any Licensed Software
does not result in a renewal or extension of the Motorola Licensed Software Warranty beyond the
ninety (90) day warranty period.
6.2.
ADDITIONAL EXCLUSIONS. IN ADDITION TO THE EXCLUSIONS FROM DAMAGES SET
FORTH IN 230022-RFP, AND NOTWITHSTANDING ANY PROVISION OF THE MCA TO THE
CONTRARY, MOTOROLA WILL HAVE NO LIABILITY FOR (A) DEFECTS IN OR DAMAGE TO
PRODUCTS RESULTING FROM USE OTHER THAN IN THE NORMAL AUTHORIZED MANNER, OR
FROM
ACCIDENT,
LIQUIDS,
OR
NEGLECT;
(B)
TESTING,
MAINTENANCE,
REPAIR,
INSTALLATION, OR MODIFICATION BY PARTIES OTHER THAN MOTOROLA; (C) CUSTOMER’S
OR ANY AUTHORIZED USER’S FAILURE TO COMPLY WITH INDUSTRY AND OSHA OR OTHER
LEGAL STANDARDS; (D) DAMAGE TO RADIO ANTENNAS, UNLESS CAUSED BY DEFECTS IN
MATERIAL OR WORKMANSHIP; (E) EQUIPMENT WITH NO SERIAL NUMBER; (F) BATTERIES OR
CONSUMABLES; (G) FREIGHT COSTS FOR SHIPMENT TO REPAIR DEPOTS; (H) COSMETIC
DAMAGE THAT DOES NOT AFFECT OPERATION; (I) NORMAL WEAR AND TEAR; (J) ISSUES OR
OBSOLESCENCE OF LICENSED SOFTWARE DUE TO CHANGES IN CUSTOMER OR
AUTHORIZED USER REQUIREMENTS, EQUIPMENT, OR SYSTEMS; OR (K) TRACKING AND
LOCATION-BASED SERVICES.
7.
Copyright Notices. The existence of a copyright notice on any Licensed Software will not be
construed as an admission or presumption of publication of the Licensed Software or public disclosure
of any trade secrets associated with the Licensed Software.
8.
Survival. The following provisions will survive the expiration or termination of this EPSLA for
any reason: Section 3 – Licensed Software License and Restrictions; Section 6.2 – Additional
Exclusions; Section 8 – Survival.
Use or disclosure of this proposal is subject to the restrictions on the cover page.
Page 213
Software Products Addendum
This Software Products Addendum (this “SPA”) is entered into between Motorola Solutions, Inc., with
offices at 500 W. Monroe Street, Suite 4400, Chicago, IL 60661 (“Motorola”) and Maricopa County
(“Customer”), and will be subject to, and governed by, the terms of the Motorola Solutions Customer
Agreement entered into between the Parties (the “MCA”), and the applicable Addenda. Capitalized
terms used in this SPA, but not defined herein, will have the meanings set forth in the MCA or the
applicable Addenda.
1.
Addendum. This SPA governs Customer’s purchase of certain Motorola software Products,
including Software Systems, and will form part of the Parties’ Agreement. A “Software System” is a
solution that includes at least one command center software Product and requires Integration Services
to deploy such software Product at a Customer Site or onto any Customer-Provided Equipment or
Equipment provided to Customer. In addition to the MCA, other Addenda may be applicable to the
Software System or other software Products, including the Subscription Software Addendum (“SSA”),
with respect to Subscription Software, and the Equipment Purchase and Software License Addendum
(“EPSLA”), with respect to Licensed Software and Equipment, as further described below. This SPA
will control with respect to conflicting or ambiguous terms in the MCA or any other applicable
Addendum, but only as applicable to the Software System or other software Products purchased under
this SPA and not with respect to other Products and Services.
2.
Software Systems; Applicable Terms and Conditions.
2.1.
On-Premise Software System. If Customer purchases an “on-premises Software System,”
where Equipment and Licensed Software are installed at Customer Sites or on Customer-Provided
Equipment, then, unless the Ordering Document(s) specify that any software is being purchased on a
subscription basis (i.e., as Subscription Software), such Equipment and Licensed Software installed at
Customer Sites or on Customer-Provided Equipment are subject to the EPSLA. On-premises Software
Systems described in this Section qualify for the System Warranty as described in Section 5 – On-
Premises Software System Warranty (the “System Warranty”). In connection with the on-premises
Software System, Customer may also purchase additional Subscription Software that integrates with its
on-premises Software System (e.g., CommandCentral Aware) (each, an “Add-On Subscription”). Any
Add-On Subscription will be subject to the terms and conditions of the SSA and excluded from the
System Warranty.
2.2.
Cloud Hosted Software System. If Customer purchases a “cloud hosted Software System,”
where the applicable software is hosted in a data center and provided to Customer as a service (i.e., as
hosted Subscription Software), including CommandCentral Products, then such Subscription Software
is subject to the SSA. Any Equipment purchased in connection with a cloud Software System is subject
to the EPSLA. Cloud hosted Software Systems described in this Section do not qualify for the System
Warranty. System completion, however, is determined in accordance with the provisions of Section 3 –
Software System Completion below.
2.3.
Services. Any Integration Services or Maintenance and Support Services purchased in
connection with, or included as a part of, a Software System are subject to the MCA, and as described
in the applicable Ordering Document.
3.
Software System Completion. Any Software System described in an Ordering Document
hereunder (including the Products, Integration Services, and all other components thereof) will be
deemed completed upon Customer’s (or the applicable Authorized User’s) Beneficial Use of each
Product that is included in the Software System (unless alternative acceptance procedures are set forth
in the applicable Ordering Document) (the “System Completion Date”). Customer will not
Use or disclosure of this proposal is subject to the restrictions on the cover page.
Page 214
unreasonably delay Beneficial Use of any Product within a Software System, and in any event, the
Parties agree that Beneficial Use of a Product will be deemed to have occurred thirty (30) days after
functional demonstration. For clarity, if a Software System is comprised of more than one Product,
Motorola may notify Customer that all Integration Services for a particular Product within the Software
System have been completed, and Customer may have Beneficial Use of such Product prior to having
Beneficial Use of other Products in the Software System, or of the Software System as a whole. In such
case, the Integration Services applicable to such Product will be deemed complete upon Customer’s
Beneficial Use of the Product (“Product Completion Date”), which may occur before the System
Completion Date. As used in this Section, “Beneficial Use” means use by Customer or at least one (1)
Authorized User of the material features and functionalities of a Product within a Software System, in
material conformance with Product descriptions in the applicable Ordering Document. This Section
applies to Products purchased as part of a Software System notwithstanding the delivery provisions of
the Addendum applicable to such Products, such as the SSA or EPSLA, and this Section will control
over such other delivery provisions to the extent of a conflict.
4.
Payment. Customer will pay invoices for the Products and Services covered by this SPA in
accordance with the invoice payment terms set forth in the MCA. Fees for Software Systems will be
invoiced as of the System Completion Date, unless another payment process or schedule or milestones
are set forth in an Ordering Document or applicable Addendum. In addition to Equipment, Licensed
Software, Subscription Software and Integration Services (as applicable) sold as part of a Software
System, the Ordering Documents for a Software System may also include post-deployment Integration
Services or other Services which are to be provided following the date of functional demonstration
(“Post-Deployment Services”). Post-Deployment Services will be invoiced upon their completion and
paid by Customer in accordance with the terms of the MCA.
5.
On-Premises Software System Warranty. Subject to the disclaimers in the MCA and any
other applicable Addenda, Motorola represents and warrants that, on the System Completion Date for
an on-premises Software System described in Section 2.1 – On-Premises Software System, or on the
applicable Product Completion Date for a specific Product within such on-premises Software System, if
earlier, (a) such Software System or Product will perform in accordance with the descriptions in the
applicable Ordering Documents in all material respects, and (b) if Customer has purchased any
Equipment or Motorola Licensed Software (but, for clarity, excluding Subscription Software) as part of
such on-premises Software System, the warranty period applicable to such Equipment and Motorola
Licensed Software will continue for a period of one (1) year commencing upon the System Completion
Date for the Software System that includes such Products, or on the applicable Product Completion
Date, if earlier, instead of commencing upon delivery of the Products in accordance with the terms and
conditions set forth in Section 6 – Representations and Warranties; Liabilities of the EPSLA. The
warranties set forth in the applicable Addenda are not otherwise modified by this SPA.
6.
Prohibited Use. Customer will not integrate or use, or permit a third party or an Authorized
User to integrate or use, any Non-Motorola Content with or in connection with a Software System or
other software Product provided by Motorola under this SPA, without the express written permission of
Motorola. This section will not prohibit the Customer from integrating with or using the data available in
the Reporting Data Warehouses with Non-Motorola Content.
7.
API Support. Motorola will use commercially reasonable efforts to maintain its Application
Programming Interface (“API”) offered sold in connection with any Software System. APIs will evolve
and mature over time, requiring changes and updates. Motorola will use reasonable efforts to continue
supporting any version of an API for 6 months after such version is introduced, but if Motorola
determines, in its sole discretion, to discontinue support of an API for any reason, Motorola will provide
reasonable advance notification to Customer. If an API presents a security risk, Motorola may
discontinue an API without prior notice.
Use or disclosure of this proposal is subject to the restrictions on the cover page.
Page 215
8.
Support of Downloaded Clients. If Customer purchases any software Product that requires a
client installed locally on any Customer-Provided Equipment or Equipment in possession of Customer,
Customer will be responsible for downloading and installing the current version of such client, as it may
be updated from time to time. Motorola will use reasonable efforts to continue supporting any version of
a client for forty-five (45) days following its release, but Motorola may update the current version of its
client at any time, including for bug fixes, product improvements, and feature updates, and Motorola
makes no representations or warranties that any software Product will support prior versions of a client.
9.
Applicable End User Terms. Additional license terms apply to third-party software included in
certain software Products which are available online at www.motorolasolutions.com/legal-flow-
downs. Customer will comply, and ensure its Authorized Users comply, with all such additional license
terms.
10.
Additional Terms for CAD and Records Products. The terms set forth in this Section apply in
the event Customer purchases any Computer Aided Dispatch (“CAD”) or Records Products under this
SPA.
10.1.
CJIS Security Policy. Motorola agrees to support Customer’s obligation to comply with the
Federal Bureau of Investigation Criminal Justice Information Services (“CJIS”) Security Policy and will
comply with the terms of the CJIS Security Addendum for the term of the Addendum or Ordering
Document for the applicable Product. Customer hereby consents to Motorola screened personnel
serving as the “escort” within the meaning of CJIS Security Policy for unscreened Motorola personnel
that require access to unencrypted Criminal Justice Information for purposes of Product support and
development.
11. Additional Cloud Terms. The terms set forth in this Section apply in the event Customer
purchases any cloud-hosted software Products.
11.1.
Data Storage. Motorola will determine, in its sole discretion, the location of the stored content for
cloud hosted software Products. All data, replications, and backups will be stored at a location in the
United States for Customers in the United States.
11.2
Data Retrieval. Cloud hosted software Products will leverage different types of storage to
optimize software, as determined in Motorola’s sole discretion. For multimedia data, such as videos,
pictures, audio files, Motorola will, in its sole discretion, determine the type of storage medium used to
store the content. The type of storage and medium selected by Motorola will determine the data
retrieval speed. Access to content in archival storage may take up to twenty-four (24) hours to be
viewable.
11.3
Availability. Motorola will make reasonable efforts to provide monthly availability of 99.9% for
cloud hosted software Products with the exception of maintenance windows. There are many factors
beyond Motorola’s control that may impact Motorola’s ability to achieve this goal.
11.4
Maintenance. Scheduled maintenance of cloud-hosted software Products will be performed
periodically. Motorola will make commercially reasonable efforts to notify customers one (1) week in
advance of any such maintenance. Unscheduled and emergency maintenance may be required from
time to time. Motorola will make commercially reasonable efforts to notify customers of any
unscheduled or emergency maintenance twenty-four (24) hours in advance.
12.
Survival. The following provisions will survive the expiration or termination of this SPA for any
reason: Section 1 – Addendum; Section 2 – Software Systems; Applicable Terms and
Conditions; Section 6 – Prohibited Use; Section 9 – Applicable End User Terms; Section 12 –
Survival.
Use or disclosure of this proposal is subject to the restrictions on the cover page.
Page 216
ATTACHMENT 1
ESRI On-Premise Terms
1. ESRI OEM SOFTWARE. Notwithstanding any provisions herein to the contrary, the following
provisions apply concerning the ESRI OEM Software.
1.1 The use of ESRI OEM Software is restricted to executable code.
1.2 The following are prohibited: (i) transfer of the OEM Software, except for a temporary transfer in the
event of a computer malfunction; (ii) assignment, time-sharing, lend or lease, or rental of the OEM
Software or use for commercial network services or interactive cable or remote processing services;
and (iii) title to the OEM Software from passing to Customer or any other party.
1.3 Also prohibited are the reverse engineering, disassembly, or decompilation of the OEM Software
and the duplication of the OEM Software, except for a single archival copy; reasonable Customer
backup copies are permitted.
1.4 To the extent permitted by law, ESRI’s liability is disclaimed for any damages, or loss of any kind,
whether special, direct, indirect, incidental, or consequential, arising from the use of the OEM Software,
including damages resulting from any ESRI provided Data (Data is not warranted) and damages
resulting from use in High Risk Activities such as the operation of nuclear facilities, aircraft navigation or
aircraft communications systems, air traffic control, life support, or weapon systems. ESRI specifically
disclaims any express or implied warranty of fitness for High Risk Activities.
1.5 Upon termination of the contract, Customer agrees to certify in writing to Motorola that it has
discontinued use and, unless otherwise required by applicable law or by a court order from a court with
competent jurisdiction, has destroyed or will return to Motorola all copies of the OEM Software and
documentation.
1.6 Customer will fully comply with all relevant export laws and regulations of the United States to
assure that the OEM Software, or any direct product thereof, is not exported, directly or indirectly, in
violation of United States law.
1.7 Customer shall not remove or obscure any copyright, trademark notice, or restrictive legend.
1.8 In any sublicense to the United States Government, the OEM Software shall be provided with
“Restricted Rights.”
2. ESRI WARRANTY.
2.1 As to ESRI OEM Software, during the term of this Agreement ESRI represents and warrants the
Software will substantially perform in conformance with the Specifications and its Documentation,
provided the Software is used as specified in the Documentation, and will provide Updates, Upgrades,
timely system releases, error corrections, and such improvements outlined in the ESRI life cycle
maintenance policy. The foregoing warranties do not apply to errors, defects, or nonconformities due to:
a) misuse of the Software solely by the Customer; b) unauthorized modification of the Software by
Customer; or c) failure of Customer to use compatible hardware and software as set forth in the
specifications.
2.2. If included under this Agreement, the Data has been obtained from sources believed to be reliable,
but its accuracy and completeness is not guaranteed. The Data may contain some nonconformities,
defects, errors or omissions. ESRI and Motorola make no warranty with respect to the Data. Without
limiting the generality of the preceding sentence, ESRI and Motorola do not warrant the Data will meet
the Customer’s needs or expectations, the use of Data will be uninterrupted, or that all nonconformities
can or will be corrected. ESRI and Motorola are not inviting reliance on the Data, and Customer should
always verify actual Data, including, but not limited to, map, spatial, raster and tabular information.
Use or disclosure of this proposal is subject to the restrictions on the cover page.
Page 217
2.3. EXCEPT FOR THE ABOVE EXPRESS LIMITED WARRANTIES, ESRI DISCLAIMS ALL OTHER
WARRANTIES OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE,
NONINTERFERENCE, SYSTEM INTEGRATION AND NON-INFRINGEMENT. ESRI DOES NOT
WARRANT THAT THE DATA WILL MEET CUSTOMER’S NEEDS OR EXPECTATIONS, THE USE OF
THE SAME WILL BE UNINTERRUPTED, OR THAT ALL NONCONFORMITIES CAN OR WILL BE
CORRECTED.
2.4. Customer’s exclusive remedy and ESRI’s entire liability for breach of the limited warranties set
forth herein shall be limited, at ESRI’s sole discretion, to (a) replacement of any defective media; (b)
repair, correction, or a work-around for the Software subject to the ESRI Support Services Policy, (c)
return of the license fees paid for the Software, Data, or Documentation that does not meet ESRI’s
limited warranty, provided that Customer uninstalls, removes, and, unless otherwise required by
applicable law or by a court order from a court with competent jurisdiction, destroys all copies of the
Software, Data, or Documentation and executes and delivers evidence of such de-installation and
destruction to ESRI.
3. THIRD PARTY PROVIDED DOCUMENTATION. Non-Motorola authored documentation will be
provided in the format available from the vendor and in accordance with the vendors distribution policy
Use or disclosure of this proposal is subject to the restrictions on the cover page.
Page 218
Microsoft On-Premise Terms
1. SOFTWARE LICENSE. As to any Microsoft Products being furnished, the Microsoft software for
those Microsoft Products is sublicensed to Licensee from Motorola pursuant to the software license
terms found in the Equipment Purchase Software License Addendum and is subject to the additional
Microsoft End-User License Agreement terms.
2. CUSTOMER USERS. Notwithstanding any provisions herein to the contrary, the following provisions
apply concerning the Microsoft Products. If Customer is acquiring from Motorola a Microsoft SQL
Server and/or a Microsoft System Center Operations Manager, then Customer warrants 1) that the
number of users that may access the System are correctly indicated in the Exhibits to this Agreement;
2) that Customer is not being licensed the SQL Server or Microsoft System Center Operations Manager
under a license from Microsoft, but rather under a sublicense from Motorola’ 3) that the copies of the
referenced Microsoft Products it receives from Motorola do not entitle it to maintain on its computer
systems any more copies of the Microsoft Products than it previously licensed from Motorola or
Microsoft; 4) that Customer possesses and will maintain sufficient quantities of fully valid Microsoft
licenses to support the maximum number of users and/or devices that may access or use the System
under the provisions of the End-User License Agreement, 5) that Microsoft will be an intended third
party beneficiary of the End-User License Agreement, with the right to enforce the warranties and any
other provisions of the End-User License Agreement provisions and to verify compliance of the End
User with the same, 6) that Customer shall not run on a mirrored database server for more than 30
days without obtaining a SQL license for that server, 7) that the Customer grants permission for the
disclosure of End-User information by Motorola as required in Motorola’s monthly royalty reports and
ordering information reports to Microsoft, 8) that Microsoft does not transfer any ownership rights in any
Product, and 9) that Motorola is solely responsible for providing technical support for the Microsoft
Products.
3. LIMITATIONS. The rights granted in this Agreement with respect to Microsoft Products are subject to
the following limitations: 1) Customer has no copyright interest in the Microsoft Products; 2) Customer
may not rent, lease, lend or provide hosting services with the Products; 3) Customer may not reverse
engineer, decompile or disassemble any Product; 4) Customer may not remove, modify or obscure any
copyrights, trademarks or other proprietary right notices contained in the Products; and 5) The
Microsoft Products are not designed or intended for use in any situation where failure or fault of the
product could lead to death or serious bodily injury of any person, or to severe physical or
environmental damage (“High Risk Use”). Motorola’s right to sublicense Microsoft Products excludes
the right to use, or distribute the Microsoft Products for Customer’s use in, or in conjunction with, High
Risk Use, therefore, High Risk Use is strictly prohibited. High Risk use, by way of example, includes
aircraft or other modes of human mass transportation, nuclear or chemical facilities, and Class III
medical devices under the Federal Food, Drug and Cosmetic Act. Notwithstanding the foregoing, as
long as PremierOne CAD is used in a manner for which it was designed and in accordance with the
documentation provided, Motorola declares such use is not considered to be High Risk Use as defined
by Microsoft.
4. MICROSOFT PRODUCTS WARRANTY. Notwithstanding any provisions herein to the contrary, the
following provisions apply to the Microsoft Products:
4.1. Microsoft Products are not fault tolerant or free from errors, conflicts, interruptions or other
imperfections. Performance may vary depending upon what hardware platform they are installed on,
the interactions with other software applications and each product’s configurations.
4.2. Microsoft Corporation is providing the Microsoft Products “as-is” with no warranty of any kind and
disclaims all warranties, express and implied, to the maximum extent allowed by applicable law.
Microsoft further disclaims any liability of Microsoft for any damages, whether direct, indirect incidental
or consequential, as a result of the use or installation of the Products. Additionally, to the extent
permitted under applicable law, Microsoft Corporation excludes for itself and its suppliers all warranties
of any kind, including:
a. any warranties of title, non-infringement, merchantability and fitness for a particular purpose;
Use or disclosure of this proposal is subject to the restrictions on the cover page.
Page 219
b. any implied warranty arising from course of dealing or usage of trade;
c. any common law duties relating to accuracy or lack of negligence with respect to the
Microsoft Products, any Master Copy, and any Software Documentation; and
d. that the products will operate properly in connection with the System, the Motorola products
or on any Customer system(s).
If applicable law gives Customer any implied warranties, guarantees or conditions despite the foregoing
exclusion, those warranties will be limited to one year and Customer remedies will be limited to the
maximum extent allowed by this Agreement.
5. THIRD PARTY PROVIDED DOCUMENTATION. Non-Motorola authored documentation will be
provided in the format available from the vendor and in accordance with the vendors distribution policy.
Explore (https://www.motorolasolutions.com/en_us.html)
Shop
(https://shop.motorolasolutions.com/)
(/en_us.html)
Home (/en_us.html) \ About Us (/en_us/about.html) \ Motorola Solutions Terms and Policies
(/en_us/about/legal.html)
\ Motorola Solutions Customer Terms (/en_us/about/legal/motorola-solutions-customer-
terms.html)
\ Flow-Down Terms (/en_us/about/legal/motorola-solutions-customer-terms/flow-down-
terms.html) \ Twilio/Sendgrid Services
Use of the Twilio Services provided hereunder shall be in accordance with
Twilio Acceptable Use Policy ( https://www.twilio.com/legal/aup), which is
hereby incorporated into this Agreement
Twilio may suspend the Twilio Services immediately upon notice to Customer for cause if: (i)
Customer or an End User materially violates (or Twilio believes, in good faith, that Customer or
an End User has materially violated) any provision of the Twilio Acceptable Use Policy
(https://www.twilio.com/legal/aup); (ii) there is an unusual and material spike or increase in
Customer’s use of the Twilio Services and Twilio believes, in good faith, that such traffic or use
is fraudulent or materially and negatively impacting the operating capability of the Twilio
Services; (iii) Twilio determines, in good faith, that its provision of the Twilio Services is
prohibited by applicable Law. Notwithstanding the foregoing, Twilio will use commercially
reasonable efforts to (x) provide Customer as much prior notice as possible of any situation its
aware of that could lead to a right to suspend described in this section, (y) work with Customer
to remedy any situation that could lead to a right to suspend described in this section if such
situation can be remedied, and (z) limit any suspension as much a possible given the
circumstances leading to the suspension (e.g., to certain phone numbers, sub-accounts or other
subset of traffic).
(https://www.motorolasolutions.com)
Follow Us: (https://blog.motorolasolutions.com/en_us/)
(https://www.linkedin.com/company/motorolasolutions)
(https://www.facebook.com/MotorolaSolutions)
(https://twitter.com/motosolutions)
(https://www.youtube.com/user/MotorolaSolutions)
ABOUT US
PARTNERS
INVESTORS
NEWSROOM
TRAINING
CAREERS
COMMUNITY
MOTOROLA, MOTO, MOTOROLA SOLUTIONS and the Stylized M Logo are trademarks or registered trademarks of Motorola Trademark Holdings, LLC
and are used under license. All other trademarks are the property of their respective owners.
©2024 Motorola Solutions, Inc. All rights reserved.
Use or disclosure of this proposal is subject to the restrictions on the cover page.
Page 220
Subscription Software Addendum
This Subscription Software Addendum (this “SSA”) is entered into between Motorola Solutions, Inc.,
with offices at 500 W. Monroe Street, Suite 4400, Chicago, IL 60661 (“Motorola”) and Maricopa County
(“Customer”), and will be subject to, and governed by, the terms of the Motorola Solutions Customer
Agreement entered into between the Parties (the “MCA”). Capitalized terms used in this SSA, but not
defined herein, will have the meanings set forth in the MCA.
1.
Addendum. This SSA governs Customer’s purchase of Subscription Software (and, if set forth
in an Ordering Document, related Services) from Motorola, and will form part of the Parties’
Agreement. Additional Subscription Software-specific Addenda or other terms and conditions may
apply to certain Subscription Software, where such terms are provided or presented to Customer.
2.
Delivery of Subscription Software.
2.1 Delivery. During the applicable Subscription Term (as defined below), Motorola will provide to
Customer the Subscription Software set forth in an Ordering Document, in accordance with the terms of
the Agreement. Motorola will provide Customer advance notice (which may be provided electronically)
of any planned downtime. Delivery will occur upon Customer’s receipt of credentials required for access
to the Subscription Software or upon Motorola otherwise providing access to the Subscription Software.
If agreed upon in an Ordering Document, Motorola will also provide Services related to such
Subscription Software.
2.2
Modifications. In addition to other rights to modify the Products and Services set forth in the
MCA, Motorola may modify the Subscription Software, any associated recurring Services and any
related systems so long as their functionality (as described in the applicable Ordering Document) is not
materially degraded. Documentation for the Subscription Software may be updated to reflect such
modifications. For clarity, new features or enhancements not already included in Exhibit I that are
added to any Subscription Software may be subject to additional Fees as agreed to by the Parties.
2.3
User Credentials. If applicable, Motorola will provide Customer with administrative user
credentials for the Subscription Software, and Customer will ensure such administrative user
credentials are accessed and used only by Customer’s employees with training on their proper use.
Customer will protect, and will cause its Authorized Users to protect, the confidentiality and security of
all user credentials, including any administrative user credentials, and maintain user credential validity,
including by updating passwords. Customer will be liable for any use of the Subscription Software
through such user credential (including through any administrative user credentials). To the extent
Motorola provides Services to Customer in order to help resolve issues resulting from unapproved or
unpermitted changes made to the Subscription Software through user credentials, such Services may
be billed to Customer on a time and materials basis. Customer will pay all invoices in accordance with
the payment terms of 2300225-RFP.
2.4
Beta Services. If Motorola makes any beta version of a software application (“Beta Service”)
available to Customer, Customer may choose to use such Beta Service at its own discretion, provided,
however, that Customer will use the Beta Service solely for purposes of Customer’s evaluation of such
Beta Service, and for no other purpose. Customer acknowledges and agrees that all Beta Services are
offered “as-is” and without any representations or warranties or other commitments or protections from
Motorola. Motorola will determine the duration of the evaluation period for any Beta Service, in its sole
discretion, and Motorola may discontinue any Beta Service at any time. Customer acknowledges that
Beta Services, by their nature, have not been fully tested and may contain defects or deficiencies.
3.
Subscription Software License and Restrictions.
Use or disclosure of this proposal is subject to the restrictions on the cover page.
Page 221
3.1.
Subscription Software License. Subject to Customer’s and its Authorized Users’ compliance
with the Agreement, including payment terms, Motorola hereby grants Customer and its Authorized
Users a limited, non-transferable, non-sublicenseable, and non-exclusive license to use the
Subscription Software identified in an Ordering Document, and the associated Documentation, solely
for Customer’s internal business purposes. The foregoing license grant will be limited to use in the
territory and to the number of licenses set forth in an Ordering Document (if applicable), and will
continue for the applicable Subscription Term. Customer may access, and use the Subscription
Software only in Customer’s owned or controlled facilities, including any authorized mobile sites;
provided, however, that Authorized Users using authorized mobile or handheld devices may also log
into and access the Subscription Software remotely from any location. No custom development work
will be performed under this Addendum.
3.2.
End User Licenses. Motorola may use, engage, resell, or otherwise interface with third-party
software, hardware or services providers (such as, for example, third-party end point detection and
response providers) and other sub-processors, who in turn may engage additional sub-processors to
process personal data and other Customer Data. Customer agrees that such third-party software or
services providers, sub-processors or their respective sub-processors may process and use personal
and other Customer Data in accordance with and subject to their own respective licenses or terms and
in accordance with applicable law. Customer authorizes and will provide and obtain all required notices
and consents, if any, and comply with other applicable legal requirements, if any, with respect to such
collection and use of personal data and other Customer Data by Motorola, and its subcontractors, sub-
processors and/or third-party software, hardware or services providers. Notwithstanding any provision
to the contrary, to the extent the use or performance of certain Services is governed by any separate
license, data requirement, EULA, privacy statement, or other applicable agreement, including terms
governing third-party software, hardware or services, including open source software, Customer will
comply, and ensure its Authorized Users comply, with any such agreements or terms, which shall
govern any such Services. As of the effective date of this contract the only applicable third-party
agreements are those attached to this addendum as Attachment 1. Any additional applicable third-party
agreements will require prior written approval by the County.
3.3.
Customer Restrictions. Customers and Authorized Users will comply with the applicable
Documentation and the copyright laws of the United States and all other relevant jurisdictions (including
the copyright laws where Customer uses the Subscription Software) in connection with their use of the
Subscription Software. Customer will not, and will not allow others including the Authorized Users, to
make the Subscription Software available for use by unauthorized third parties, including via a
commercial rental or sharing arrangement; reverse engineer, disassemble, or reprogram software used
to provide the Subscription Software or any portion thereof to a human-readable form; modify, create
derivative works of, or merge the Subscription Software or software used to provide the Subscription
Software with other software; copy, reproduce, distribute, lend, or lease the Subscription Software or
Documentation for or to any third party; take any action that would cause the Subscription Software,
software used to provide the Subscription Software, or Documentation to be placed in the public
domain; use the Subscription Software to compete with Motorola; remove, alter, or obscure, any
copyright or other notice; share user credentials (including among Authorized Users); use the
Subscription Software to store or transmit malicious code; or attempt to gain unauthorized access to the
Subscription Software or its related systems or networks.
4.
Term.
4.1
Add-On Subscription Terms. Unless otherwise specified in the applicable Ordering Document, if
Customer orders any additional Subscription Software or recurring Services under this SSA during the
term of 2300225-RFP, the subscription for each new Subscription Software or recurring Service will (a)
commence upon delivery of such Subscription Software or recurring Service, and continue until the
conclusion of the term of 2300225-RFP, and (b) renew as agreed by the parties. Thus, unless
Use or disclosure of this proposal is subject to the restrictions on the cover page.
Page 222
otherwise specified in the applicable Ordering Document, the subscription terms for all Subscription
Software and recurring Services hereunder will be synchronized.
4.2
Term. The term of this SSA (the “SSA Term”) will commence upon either (a) the Effective Date
of the MCA, if this SSA is attached to the MCA as of such Effective Date, or (b) the SSA Date set forth
on the signature page below, if this SSA is executed after the MCA Effective Date, and will continue
until the expiration or termination of all Subscription Terms under this SSA, unless this SSA or the MCA
is earlier terminated in accordance with the terms of the Agreement.
4.3
Termination. Notwithstanding the termination provisions of the MCA, Motorola may terminate
this SSA (or any Addendum or Ordering Documents hereunder), or suspend delivery of Subscription
Software or Services, immediately upon notice to Customer if (a) Customer breaches Section 3 –
Subscription Software License and Restrictions of this SSA, or any other provision related to
Subscription Software license scope or restrictions set forth in an Addendum or Ordering Document, or
(b) it determines that Customer’s use of the Subscription Software poses, or may pose, a security or
other risk or adverse impact to any Subscription Software, Motorola, Motorola’s systems, or any third
party (including other Motorola customers). Customer acknowledges that Motorola made a
considerable investment of resources in the development, marketing, and distribution of the
Subscription Software and Documentation, and that Customer’s breach of the Agreement will result in
irreparable harm to Motorola for which monetary damages would be inadequate. If Customer breaches
this Agreement, in addition to termination, Motorola will be entitled to all available remedies at law or in
equity (including immediate injunctive relief).
4.4
Wind Down of Subscription Software. In addition to the termination rights in the MCA, Motorola
may terminate any Ordering Document and Subscription Term, in whole or in part, in the event
Motorola plans to cease offering the applicable Subscription Software or Service to customers.
5.
Payment.
5.1
Payment. Unless otherwise provided in an Ordering Document (and notwithstanding the
provisions of the MCA), Customer will prepay an annual subscription Fee set forth in an Ordering
Document for each Subscription Software and associated recurring Service, before the commencement
of each annual subscription term. For any add-on subscriptions and/or services that may be subject to
a partial subscription year, the applicable annual subscription Fee will be prorated based on the number
of months in the partial subscription year. The annual subscription Fee for Subscription Software and
associated recurring Services may include certain one-time Fees, such as start-up fees, license fees, or
other fees set forth in an Ordering Document. Motorola will have the right to suspend the Subscription
Software and any recurring Services if Customer fails to make any payments when due. The parties
acknowledge that pricing for Cyber Services is dependent on the full term or subscription periods
specified in any such Ordering Document.
5.2
License True-Up. Motorola will have the right to conduct an audit of total user licenses
credentialed by Customer for any Subscription Software during a Subscription Term, and Customer will
cooperate with such audit. If Motorola determines that Customer’s usage of the Subscription Software
during the applicable Subscription Term exceeded the total number of licenses purchased by
Customer, Motorola may invoice Customer for the additional licenses used by Customer, pro-rated for
each additional license from the date such license was activated, and Customer will pay such invoice in
accordance with the payment terms in the MCA.
5.3
Customer Data. For avoidance of doubt, for Cyber Services so long as not specifically
identifying the Customer, “Customer Data,” as defined in the MCA, shall not include, and Motorola shall
be free to use, share and leverage security threat intelligence and mitigation data generally, including
without limitation, third party threat vectors and IP addresses, file hash information, domain names,
Use or disclosure of this proposal is subject to the restrictions on the cover page.
Page 223
malware signatures and information, information obtained from third party sources, indicators of
compromise, and tactics, techniques, and procedures used, learned or developed in the course of
providing Services
5.4
Future Regulatory Requirements. The Parties acknowledge and agree that Cyber Service is an
evolving technological area and therefore, laws and regulations regarding Services may change.
Changes to existing Services required to achieve regulatory compliance may be available for an
additional fee. Any required changes may also impact the price for Services.
6.
Liability.
6.1
ADDITIONAL EXCLUSIONS. IN ADDITION TO THE EXCLUSIONS FROM DAMAGES SET
FORTH IN THE MCA, AND NOTWITHSTANDING ANY PROVISION OF THE AGREEMENT TO THE
CONTRARY, MOTOROLA WILL HAVE NO LIABILITY FOR (A) INTERRUPTION OR FAILURE OF
CONNECTIVITY, VULNERABILITIES, OR SECURITY EVENTS; (B) DISRUPTION OF OR DAMAGE
TO CUSTOMER’S OR THIRD PARTIES’ SYSTEMS, EQUIPMENT, OR DATA, INCLUDING DENIAL OF
ACCESS TO USERS, OR SHUTDOWN OF SYSTEMS CAUSED BY INTRUSION DETECTION
SOFTWARE OR HARDWARE; (C) AVAILABILITY OR ACCURACY OF ANY DATA AVAILABLE
THROUGH THE SUBSCRIPTION SOFTWARE OR SERVICES, OR INTERPRETATION, USE, OR
MISUSE THEREOF; (D) TRACKING AND LOCATION-BASED SERVICES; OR (E) BETA SERVICES.
6.2
Direct Damages. For avoidance of doubt, notwithstanding the limitation set out in Section 10.3.2
of 2300225-RFP, the direct damages limitation for Cyber services provided under this SSA is limited to
the fees, or the portion of fees, relating only to the Cyber Security Services under this SSA, even if such
Services are offered or bundled with other Motorola services.
7.
Motorola as a Controller or Joint Controller. In all instances where Motorola acts as a
controller of data, it will comply with the applicable provisions of the Motorola Privacy Statement at
https://www.motorolasolutions.com/en_us/about/privacy-policy.html#privacystatement, as may be updated
from time to time. Motorola holds all Customer Contact Data as a controller and shall Process such
Customer Contact Data in accordance with the Motorola Privacy Statement. In instances where
Motorola is acting as a joint controller with Customer, the Parties will enter into a separate Addendum
to the Agreement to allocate the respective roles as joint controllers.
8.
Survival. The following provisions will survive the expiration or termination of this SSA for any
reason: Section 4 – Term; Section 5 – Payment; Section 8 – Survival.
Use or disclosure of this proposal is subject to the restrictions on the cover page.
Page 224
Motorola Solutions Data Processing Addendum - U.S.
This Data Processing Addendum, including Annexes I-III (“DPA”), forms part of the MCA which is
attached as Exhibit E to 2300225-RFP (“Agreement”) to reflect the parties’ agreement with regard to
the Processing of Customer Data, which may include Personal Data. In the event of a conflict
between this DPA and the MCA, this DPA will prevail. In the event of a conflict between this DPA and
the terms of 2300225-RFP other than the MCA, the terms of 2300225-RFP will prevail.
When Customer renews or purchases new Products or Services, the then-current DPA will apply and
will not change during the applicable Term except as necessary to conform to applicable law.
Notwithstanding the foregoing, when Motorola provides new features or supplements the Product or
Service, Motorola may provide additional terms or make updates to this DPA that will apply to
Customer’s use of those new features or supplements.
1.
Definitions.
To the extent the Agreement provides definitions for the terms defined in this Section 1, the
definitions of this Section 1 will apply to this DPA and the definitions of the Agreement will apply to
the Agreement.
“Controller” means the natural or legal person, public authority, agency or other body which, alone
or jointly with others, determines the purposes and means of the processing of personal data.
Regulatory frameworks may differ in their respective naming conventions and therefore may refer to
a Controller as a “Business” or otherwise.
“Customer Data” means data including images, text, videos, and audio, that are provided to
Motorola by, through, or on behalf of Customer and its Authorized Users or their end users, through
the use of the Products and Services. Customer Data does not include Customer Contact Data,
Service Use Data, other than that portion comprised of Personal Information, or Third Party Data.
“Customer Contact Data” means data Motorola collects from Customer for contact purposes,
including, without limitation, contract fulfillment, marketing, advertising, licensing, and sales activities.
“Data Protection Laws” means all data protection laws and regulations applicable to a Party with
respect to the Processing of Personal Data under the Agreement.
“Data Subjects” means the identified or identifiable person to whom Personal Data relates.
“Metadata” means data that describes other data.
“Motorola Data” means data owned by Motorola and made available to Customer in connection with
the Products and Services.
“Personal Data” or “Personal Information” means any information relating to an identified or
identifiable natural person transmitted to Motorola by, through, or on behalf of Customer and its
Authorized Users or their end users as part of Customer Data. An identifiable natural person is one
who can be identified, directly or indirectly, in particular by reference to an identifier such as a name,
an identification number, location data, an online identifier or to one or more factors specific to the
physical, physiological, genetic, mental, economic, cultural or social identity of that natural person.
Personal Data or Personal Information does not include CJIS-protected MCSO data.
“Process” or “Processing” means any operation or set of operations which is performed on
Customer Data, which may include Personal Data or on sets of Personal Data, whether or not by
automated means, such as collection, recording, copying, analyzing, caching, organization,
structuring, storage, adaptation, or alteration, retrieval, consultation, use, disclosure by transmission,
Use or disclosure of this proposal is subject to the restrictions on the cover page.
Page 225
dissemination or otherwise making available, alignment or combination, restriction, erasure or
destruction.
“Processor'' means a natural or legal person, public authority, agency or other body which
processes personal data on behalf of the Controller. Processors act on behalf of the relevant
Controller and under their authority. In doing so, they serve the Controller's interests rather than their
own. Regulatory frameworks may differ in their respective naming conventions and therefore may
refer to a Processor as a “Service Provider” or otherwise.
“Security Incident” means a confirmed or reasonably suspected accidental or unlawful destruction,
loss, alteration or disclosure of, or access to Customer Data, which may include Personal Data, while
processed by Motorola.
“Service Use Data” means data generated about the use of the Products and Services through
Customer’s use or Motorola’s support of the Products and Services, which may include Metadata,
Personal Data, product performance and error information, activity logs, and date and time of use.
“Sub-processor” means other Processors engaged by Motorola to Process Customer Data which
may include Personal Data.
“Third Party Data” means information obtained by Motorola from publicly available sources or its
third party content providers and made available to Customer through the Products or Services.
2.
Processing of Customer Data
2.1.
Roles of the Parties. The Parties agree that with regard to the Processing of Personal Data
hereunder, Customer is the Controller and Motorola is the Processor who may engage Sub-
processors pursuant to the requirements of Section 6 entitled “Sub-processors” below.
2.2.
Motorola’s Processing of Customer Data. Motorola and Customer agree that Motorola may
only use and Process Customer Data, including the Personal Information embedded in Service Use
Data, in accordance with applicable law and Customer’s documented instructions for the following
purposes: (i) to perform Services and provide Products under the Agreement;
(ii) analyze Customer Data to operate, maintain, manage, and improve Motorola products and
services; and (iii) create new products and services. Customer agrees that its Agreement (including
this DPA), along with the Product and Service Documentation and Customer’s use and configuration
of features in the Products and Services, are Customer’s complete and final documented instructions
to Motorola for the processing of Customer Data. Any additional or alternate instructions will be
agreed to according to the process for amending Customer’s Agreement. Customer represents and
warrants to Motorola that Customer’s instructions, including appointment of Motorola as a Processor
or Sub-processor, have been authorized by the relevant controller. Customer Data may be processed
by Motorola at any of its global locations and/or disclosed to Sub-processors. It is Customer’s
responsibility to notify Authorized Users of Motorola’s collection and use of Customer Data, and to
obtain any required consents, provide all necessary notices, and meet any other applicable legal
requirements with respect to such collection and use. Customer represents and warrants to Motorola
that it has complied with the terms of this provision.
2.3.
Details of Processing. The subject-matter of Processing of Personal Data by Motorola
hereunder, the duration of the Processing, the categories of Data Subjects and types of Personal Data
are set forth on Annex I to this DPA.
2.4.
Disclosure of Processed Data. Motorola will not disclose to or share any Customer Data with
any third party except to Motorola’s Sub-processors, suppliers and channel partners as necessary to
provide the products and services unless permitted under this Agreement, authorized by Customer or
required by law. In the event a government or supervisory authority demands access to Customer
Use or disclosure of this proposal is subject to the restrictions on the cover page.
Page 226
Data, to the extent allowable by law, Motorola will provide Customer with notice of receipt of the
demand to provide sufficient time for Customer to seek appropriate relief in the relevant jurisdiction. In
all circumstances, Motorola retains the right to comply with applicable law. Motorola will ensure that its
personnel are subject to a duty of confidentiality, and will contractually obligate its Sub-processors to a
duty of confidentiality, with respect to the handling of Customer Data and any Personal Data contained
in Service Use Data.
2.5.
Customer’s Obligations. Customer is solely responsible for its compliance with all Data
Protection Laws and establishing and maintaining its own policies and procedures to ensure such
compliance. Customer will not use the products and services in a manner that would violate applicable
Data Protection Laws. Customer will have sole responsibility for (i) the lawfulness of any transfer of
Personal Data to Motorola, (ii) the accuracy, quality, and legality of Personal Data provided to
Motorola; (iii) the means by which Customer acquired Personal Data, and (iv) the provision of any
required notices to, and obtaining any necessary acknowledgements, authorizations or consents from
Data Subjects. Customer takes full responsibility to keep the amount of Personal Data provided to
Motorola to the minimum necessary for Motorola to perform in accordance with the Agreement.
3.
Service Use Data. Except to the extent that it is Personal Information, Customer understands
and agrees that Motorola may collect and use Service Use Data for its own purposes, provided that
such purposes are compliant with applicable Data Protection Laws. Service Use Data may be
processed by Motorola at any of its global locations and/or disclosed to Sub-processors.
4.
Third-Party Data and Motorola Data. Motorola Data and Third Party Data may be available to
Customer through the products and services. Customer and its Authorized Users may use the
Motorola Data and Third Party Data as permitted by Motorola and the applicable third-party data
provider, as described in the Agreement Unless expressly permitted in the Agreement, Customer will
not, and will ensure its Authorized Users will not: (a) use the Motorola Data or Third-Party Data for
any purpose other than Customer’s internal business purposes or, unless otherwise required by
applicable law or a court order from a court with competent jurisdiction, disclose the data to third
parties; (b) “white label” such data or otherwise misrepresent its source or ownership, or resell,
distribute, sublicense, or commercially exploit the data in any manner; (c) use such data in violation
of applicable laws ; (d) use such data for activities or purposes where reliance upon the data could
lead to death, injury, or property damage; (e) remove, obscure, alter, or falsify any marks or
proprietary rights notices indicating the source, origin, or ownership of the data; or (f) modify such
data or combine it with Customer Data or other data or use the data to build databases. Additional
restrictions may be set forth in the Agreement. Any rights granted to Customer or Authorized Users
with respect to Motorola Data or Third-Party Data will immediately terminate upon termination or
expiration of the applicable addendum, order or the Agreement. Further, Motorola or the applicable
Third Party Data provider may suspend, change, or terminate Customer’s or any Authorized User’s
access to Motorola Data or Third-Party Data if Motorola or such Third Party Data provider believes
Customer’s or the Authorized User’s use of the data violates the Agreement, applicable law or by
Motorola’s agreement with the applicable Third Party Data provider. Upon termination of Customer’s
rights to use of any Motorola Data or Third-Party Data, Customer and all Authorized Users will
immediately discontinue use of such data, unless otherwise required by applicable law or a court
order from a court with competent jurisdiction, delete all copies of such data, and certify such deletion
to Motorola. Notwithstanding any provision of the Agreement to the contrary, Motorola has no liability
for Third-Party Data or Motorola Data available through the Products and Services. Motorola and its
Third Party Data providers reserve all rights in and to Motorola Data and Third-Party Data not
expressly granted in the Agreement.
5.
Motorola as a Controller or Joint Controller. In all instances where Motorola acts as a
Controller it will comply with the applicable provisions of the Motorola Privacy Statement at Privacy
Policy Statement - Motorola Solutions as each may be updated from time to time. Motorola holds all
Use or disclosure of this proposal is subject to the restrictions on the cover page.
Page 227
Customer Contact Data as a Controller and will Process such Customer Contact Data in accordance
with the Motorola Privacy Statement.
6.
Sub-processors.
6.1
Use of Sub-processors. Customer agrees that Motorola may engage Sub-processors who in
turn may engage Sub-processors to Process Personal Data in accordance with the DPA. A current list
of Sub-processors is set forth at Motorola Sub-Processors or Annex III, if Annex III has been
completed. When engaging Sub-processors, Motorola will enter into agreements with the Sub-
processors to bind them to obligations which are substantially similar or more stringent than those set
out in this DPA.
6.2 Changes to Sub-processing. The Customer hereby consents to Motorola engaging Sub-
processors to process Customer Data provided that: (i) Motorola will use its reasonable endeavors to
provide at least 10 days' prior notice of the addition or removal of any Sub-processor, which may be
given by posting details of such addition or removal at Motorola Sub-Processors; (ii) Motorola
imposes data protection terms on any Sub-processor it appoints that protect the Customer Data to the
same standard provided for by this DPA; and (iii) Motorola remains fully liable for any breach of this
clause that is caused by an act, error or omission of its Sub-processor(s). The Customer may object to
Motorola’s appointment or replacement of a Sub-processor prior to its appointment or replacement,
provided such objection is based on reasonable grounds relating to data protection. In such event,
Motorola will either appoint or replace the Sub-processor or, if this is not feasible, the Customer may
terminate this Agreement and receive a pro-rata refund of any prepaid service or support fees as full
satisfaction of any claim arising out of such termination.
6.3 Data Subject Requests. Motorola will, to the extent legally permitted, promptly notify Customer if
it receives a request from a Data Subject, including without limitation requests for access to,
correction, amendment, transport or deletion of such Data Subject’s Personal Data and, to the extent
applicable, Motorola will provide Customer with commercially reasonable cooperation and assistance
in relation to any complaint, notice, or communication from a Data Subject. Customer will respond to
and resolve promptly all requests from Data Subjects which Motorola provides to Customer.
Customer will be responsible for any reasonable costs arising from Motorola’s provision of such
assistance under this Section.
7.
Data Transfers
Motorola agrees that it will not make transfers of Personal Data under this Agreement from one
jurisdiction to another unless such transfers are performed in compliance with this DPA and
applicable Data Protection Laws. Motorola agrees to enter into appropriate agreements with its
affiliates and Sub-processors, which will permit Motorola to transfer Personal Data to its affiliates and
Sub-processors. Motorola also agrees to assist the Customer in entering into agreements with its
affiliates and Sub-processors if required by applicable Data Protection Laws for necessary transfers.
8.
Security. Motorola will implement appropriate technical and organizational measures to ensure
a level of security appropriate to the risks posed by the Processing of Customer Data which may
include Personal Data. The appropriate technical and organizational measures implemented by
Motorola are set forth in Annex II.
9.
Security Incident Notification. If Motorola becomes aware of a Security Incident, then
Motorola will (i) notify Customer of the Security Incident without undue delay, (ii) investigate the
Security Incident and apprise Customer of the details of the Security Incident and (iii) take
commercially reasonable steps to stop any ongoing loss of Customer Data including Personal Data
due to the Security Incident if in the control of Motorola. Notification of a Security Incident will not be
Use or disclosure of this proposal is subject to the restrictions on the cover page.
Page 228
construed as an acknowledgement or admission by Motorola of any fault or liability in connection with
the Security Incident. Motorola will make reasonable efforts to assist Customer in fulfilling Customer’s
obligations under Data Protection Laws to notify the relevant supervisory authority and Data Subjects
about such incident.
10.
Data Retention and Deletion.
Except for anonymized Customer Data, Motorola will delete all Customer Data no later than ninety
(90) days following termination or expiration of the Agreement unless otherwise required to comply
with applicable law.
11.
Audit Rights
11.1
Periodic Audit. Motorola will allow Customer to perform an audit of reasonable scope and
duration of Motorola operations relevant to the Products and Services purchased under the
Agreement, at Customer’s sole expense, for verification of compliance with the technical and
organizational measures set forth in Annex II if (i) Motorola notifies Customer of a Security Incident
that results in actual compromise to the Products and/or Services purchased; or (ii) if Customer
reasonably believes Motorola is not in compliance with its security commitments under this DPA, or
(iii) if such audit is legally required by the Data Protection Laws. Any audit will be conducted in
accordance with the procedures set forth in Section 11.3 of this DPA and may not be conducted more
than one time per year. Unless mandated by law or court order, no audits are allowed within a data
center for security and compliance reasons. Motorola will, in no circumstances, provide Customer with
the ability to audit any portion of its software, products, and services which would be reasonably
expected to compromise the confidentiality of any third party’s information or Personal Data.
11.2
Satisfaction of Audit Request. Upon receipt of a written request to audit, and subject to
Customer’s agreement, Motorola may satisfy such audit request by providing Customer with a
confidential copy of Motorola’s most recent applicable third party security review performed by a
nationally recognized independent third party auditor, such as a SOC2 Type II report or ISO 27001
and 27701 certification, in order that Customer may reasonably verify Motorola’s compliance with
industry standard information security and privacy frameworks.
11.3
Audit Process. Customer will provide at least sixty days (60) days prior written notice to
Motorola of a request to conduct the audit described in Section 11.1. All audits will be conducted
during normal business hours, at applicable locations or remotely, as designated by Motorola. Audit
locations, if not remote will generally be those location(s) where Customer Data is accessed, or
Processed, excluding data centers. The audit will not unreasonably interfere with Motorola’s day to
day operations. An audit will be conducted at Customer’s sole cost and expense and subject to the
terms of the confidentiality obligations set forth in the Agreement. Before the commencement of any
such audit, Motorola and Customer will mutually agree upon the time, and duration of the audit.
Motorola will provide reasonable cooperation with the audit, including providing the appointed auditor
a right to review, but not copy, Motorola security information or materials provided such auditor has
executed an appropriate non-disclosure agreement. Motorola’s policy is to share methodology and
executive summary information, not raw data or private information. Customer will, at no charge,
provide to Motorola a full copy of all findings of the audit.
12.
Regulation Specific Terms
12.1
Reserved.
12.2
FERPA. If Customer is an educational agency or institution to which regulations under the
Family Educational Rights and Privacy Act, 20 U.S.C. § 1232g (FERPA), apply, Motorola
acknowledges that for the purposes of the DPA, Motorola is a “school official” with “legitimate
educational interests” in the Customer Data, as those terms have been defined under FERPA and its
implementing regulations, and Motorola agrees to abide by the limitations and requirements imposed
Use or disclosure of this proposal is subject to the restrictions on the cover page.
Page 229
by 34 CFR 99.33(a) on school officials. Customer understands that Motorola may possess limited or
no contact information for Customer’s students and students’ parents.
12.3
CJIS. Motorola agrees to support the Customer’s obligation to comply with the Federal Bureau
of Investigation Criminal Justice Information Services (CJIS) Security Policy and will comply with the
terms of the CJIS Security Addendum for the Term of this Agreement. Customer hereby consents to
allow Motorola “screened” personnel as defined by the CJIS Security Policy to serve as an authorized
“escort” within the meaning of CJIS Security Policy for escorting unscreened Motorola personnel that
require access to unencrypted Criminal Justice Information for purposes of Tier 3 support (e.g.
troubleshooting or development resources). In the event Customer requires access to Service Use
Data for its compliance with the CJIS Security Policy, Motorola will make such access available
following Customer’s request. Notwithstanding the foregoing, in the event the Agreement terminates,
Motorola will carry out deletion of Customer Data in compliance with Section 10 herein and may
likewise delete Service Use Data within the time frame specified therein.
12.4
Reserved.
12.5
Data Protection Laws. Motorola will comply with its obligations under the applicable
legislation, and shall make available to Customer all information in its possession necessary to
demonstrate compliance with obligations in accordance with such legislation.
12.6
Motorola Contact. If Customer believes that Motorola is not adhering to its privacy or security
obligations hereunder, Customer will contact the Motorola Data Protection Officer at Motorola
Solutions,
Inc.,
500
W.
Monroe,
Chicago,
IL
USA
90661-3618
or
at
privacy1@motorolasolutions.com .
ANNEX I
DESCRIPTION OF TRANSFER
Categories of data subjects whose personal data is transferred
Data subjects include the data exporter’s representatives and end-users including employees,
contractors, collaborators, and customers of the data exporter. Data subjects may also include
individuals attempting to communicate or transfer personal information to users of the services
provided by data importer. Motorola acknowledges that, depending on Customer’s use of the online
Service, Customer may elect to include personal data from any of the following types of data subjects
in the Customer Data:
x
Employees, contractors, and temporary workers (current, former, prospective) of data exporter;
x
Dependents of the above;
x
Data exporter's collaborators/contact persons (natural persons) or employees, contractors or
temporary workers of legal entity collaborators/contact persons (current, prospective, former);
x
Users (e.g., customers, clients, patients, visitors, etc.) and other data subjects that are users of
data exporter's services;
x
Partners, stakeholders or individuals who actively collaborate, communicate or otherwise
interact with employees of the data exporter and/or use communication tools such as apps and
websites provided by the data exporter;
Use or disclosure of this proposal is subject to the restrictions on the cover page.
Page 230
x
Stakeholders or individuals who passively interact with data exporter (e.g., because they are
the subject of an investigation, research or mentioned in documents or correspondence from or
to the data exporter);
x
Minors; or
x
Professionals with professional privilege (e.g., doctors, lawyers, notaries, religious workers,
etc.).
Categories of personal data transferred
Customer’s use of the Products and Services. Customer may elect to include personal data from any
of the following categories in the Customer Data:
x
Basic personal data (for example place of birth, street name, and house number (address), city
of residence, country of residence, mobile phone number, first name, last name, initials, email
address, gender, date of birth), including basic personal data about family members and children;
x
Authentication data (for example user name, password or PIN code, security question, audit
trail);
x
Contact information (for example addresses, email, phone numbers, social media identifiers;
emergency contact details);
x
Unique identification numbers and signatures (for example Social Security number, bank
account number, passport and ID card number, driver's license number and vehicle registration
data, IP addresses, employee number, student number, patient number, signature, unique
identifier in tracking cookies or similar technology);
x
Pseudonymous identifiers;
x
Financial and insurance information (for example insurance number, bank account name and
number, credit card name and number, invoice number, income, type of assurance, payment
behavior, creditworthiness);
x
Commercial Information (for example history of purchases, special offers, subscription
information, payment history);
x
Biometric Information (for example DNA, fingerprints and iris scans);
x
Location data (for example, Cell ID, geo-location network data, location by start call/end of the
call. Location data derived from use of Wi-Fi access points);
x
Photos, video, and audio;
x
Internet activity (for example browsing history, search history, reading, television viewing, radio
listening activities);
x
Device identification (for example IMEI-number, SIM card number, MAC address);
x
Profiling (for example based on observed criminal or anti-social behavior or pseudonymous
profiles based on visited URLs, click streams, browsing logs, IP-addresses, domains, apps
installed, or profiles based on marketing preferences);
x
HR and recruitment data (for example declaration of employment status, recruitment
information (such as curriculum vitae, employment history, education history details), job and
Use or disclosure of this proposal is subject to the restrictions on the cover page.
Page 231
position data, including worked hours, assessments and salary, work permit details, availability,
terms of employment, tax details, payment details, insurance details and location, and
organizations);
x
Education data (for example education history, current education, grades and results, highest
degree achieved, learning disability);
x
Citizenship and residency information (for example citizenship, naturalization status, marital
status, nationality, immigration status, passport data, details of residency or work permit);
x
Information processed for the performance of a task carried out in the public interest or in the
exercise of an official authority;
x
Special categories of data (for example racial or ethnic origin, political opinions, religious or
philosophical beliefs, trade union membership, genetic data, biometric data for the purpose of
uniquely identifying a natural person, data concerning health, data concerning a natural person’s
sex life or sexual orientation, or data relating to criminal convictions or offenses); or
x
Any other personal data identified under applicable law or regulation.
Sensitive data transferred
To the extent that a solution sold under an Agreement requires the processing of sensitive personal
information, it will be restricted to the minimum processing necessary for the solution functionality and
be subject to technical security measures appropriate to the nature of the information.
The frequency of the transfer Data may be transferred on a continuous basis during the term of the
Agreement.
Nature of the processing
The nature, scope and purpose of processing personal data is to carry out performance of Motorola’s
obligations with respect to provision of the Products and Services purchased under the Agreement.
The data importer utilizes a global network of data centers and management/support facilities, and
processing may take place in any jurisdiction where data importer or its Sub-processors utilize such
facilities.
Purpose(s) of the data transfer and further processing
The nature, scope and purpose of processing personal data is to carry out performance of Motorola’s
obligations with respect to provision of the Products and Services purchased under the Agreement.
The data importer utilizes a global network of data centers and management/support facilities, and
processing may take place in any jurisdiction where data importer or its Sub-processors utilize such
facilities.
The period for which the personal data will be retained
Data retention is governed by Section 10 of this Data Processing Addendum
For transfers to (sub-) processors, also specify subject matter, nature and duration of the
processing
Transfers to Sub-processors will only be for carrying out the performance of Motorola’s obligations
with respect to provision of the Products and Services purchased under the Agreement. The data
importer utilizes a global network of data centers and management/support facilities, and processing
Use or disclosure of this proposal is subject to the restrictions on the cover page.
Page 232
may take place in any jurisdiction where data importer or its Sub-processors utilize such facilities. In
accordance with the DPA, the data exporter agrees the data importer may hire other companies to
provide limited services on data importer’s behalf, such as providing customer support. Any such
Sub-processors will be permitted to obtain Customer Data only to deliver the services the data
importer has retained them to provide, and they are prohibited from using Customer Data for any
other purpose.
Use or disclosure of this proposal is subject to the restrictions on the cover page.
Page 233
ANNEX II
TECHNICAL
AND
ORGANIZATIONAL
MEASURES
INCLUDING
TECHNICAL
AND
ORGANIZATIONAL MEASURES TO ENSURE THE SECURITY OF THE DATA
Measures of pseudonymization and encryption of personal data
Where technically feasible and when not impacting services provided: Motorola minimizes the data it
collects to information it believes is necessary to communicate, provide, and support products and
services and information necessary to comply with legal obligations. Motorola encrypts data in transit
and at rest. Motorola pseudonymizes and limits administrative accounts that have access to reverse
pseudonymization.
Measures for ensuring ongoing confidentiality, integrity, availability and resilience of
processing systems and services
In order to ensure ongoing confidentiality, integrity, availability and resilience of processing systems
and services, Motorola Solutions Information Protection policy mandates the institutionalization of
information protection throughout solution development and operational lifecycles. Motorola
maintains dedicated security teams for its internal information security and its products and services.
Its security practices and policies are integral to its business and mandatory for all Motorola
employees and contractors. The Motorola Chief Information Security Officer maintains responsibility
and executive oversight for such policies, including formal governance, revision management,
personnel education and compliance. Motorola generally aligns its information security practices to
the NIST Cybersecurity Framework as well as ISO 27001.
Measures for ensuring the ability to restore the availability and access to personal data in a
timely manner in the event of a physical or technical incident
Motorola’s availability and backup strategy is designed to ensure replication and fail-over protections
in the event of a physical or technical incident. Personal Data is backed up and maintained using at
least industry standard methods
Security Incident Procedures. Motorola maintains a global incident response plan to address any
physical or technical incident in an expeditious manner. Motorola maintains a record of security
breaches with a description of the breach, the time period, the consequences of the breach, the name
of the reporter, and to whom the breach was reported, and the procedure for recovering data. For
each security breach that is a Security Incident, notification will be made in accordance with the
Security Incident Notification section of this DPA.
Business Continuity and Disaster Preparedness. Motorola maintains business continuity and disaster
preparedness plans for critical functions and systems within Motorola’s control that support the
products and services purchased under the Agreement in order to avoid services disruptions and
minimize recovery risks.
Processes for regularly testing, assessing and evaluating the effectiveness of technical and
organizational measures in order to ensure the security of the processing
Motorola periodically evaluates its processes and systems to ensure continued compliance with
obligations imposed by law, regulation or contract with respect to the confidentiality, integrity,
availability, and security of Customer Data, including Personal Information. Motorola documents the
results of these evaluations and any remediation activities taken in response to such evaluations.
Motorola periodically has third party assessments performed against applicable industry standards,
such as ISO 27001, 27017, 27018 and 27701.
Use or disclosure of this proposal is subject to the restrictions on the cover page.
Page 234
Measures for user identification and authorization
Identification and Authentication. Motorola uses industry standard practices to identify and
authenticate users who attempt to access Motorola information systems. Where authentication
mechanisms are based on passwords, Motorola requires that the passwords are at least twelve
characters long and are changed regularly. Motorola uses industry standard password protection
practices, including practices designed to maintain the confidentiality and integrity of passwords
when they are assigned, distributed, and during storage.
Access Policy and Administration. Motorola maintains a record of security privileges of individuals
having access to Customer Data, including Personal Information. Motorola maintains appropriate
processes for requesting, approving and administering accounts and access privileges in connection
with the Processing of Customer Data. Only authorized personnel may grant, alter or cancel
authorized access to data and resources. Where an individual has access to systems containing
Customer Data, the individuals are assigned separate, unique identifiers. Motorola deactivates
authentication credentials on a periodic basis.
Measures for the protection of data during transmission
Data is generally encrypted during transmission within the Motorola managed environments.
Encryption in transit is also generally required of any Sub-processors. Further, protection of data in
transit is achieved through the access controls, physical and environmental security, and personnel
security described throughout this Annex II.
Measures for the protection of data during storage
Data is generally encrypted during storage within the Motorola managed environments. Encryption in
storage is also generally required of any Sub-processors. Further, protection of data in storage is also
achieved through the access controls, physical and environmental security, and personnel security
described throughout this Annex II.
Measures for ensuring physical security of locations at which personal data are processed
Motorola maintains appropriate physical and environment security controls to prevent unauthorized
access to Customer Data, including Personal Information. This includes appropriate physical entry
controls to Motorola facilities such as card-controlled entry points, and a staffed reception desk to
protect against unauthorized entry. Access to controlled areas within a facility will be limited by job
role and subject to authorized approval. Use of an access badge to enter a controlled area will be
logged and such logs will be retained in accordance with Motorola policy. Motorola revokes personnel
access to Motorola facilities and controlled areas upon separation of employment in accordance with
Motorola policies. Motorola policies impose industry standard workstation, device and media controls
designed to further protect Customer Data, including personal information.
Measures for ensuring personnel security
Access to Customer Data. Motorola maintains processes for authorizing and supervising its
employees, and contractors with respect to monitoring access to Customer Data. Motorola requires
its employees, contractors and agents who have, or may be expected to have, access to Customer
Data to treat that data as Motorola confidential restricted information.
Security and Privacy Awareness. Motorola ensures that its employees and contractors remain aware
of industry standard security and privacy practices, and their responsibilities for protecting Customer
Data, which may include Personal Data. This includes, but is not limited to, protection against
malicious software, password protection, and management, and use of workstations and computer
system accounts. Motorola requires periodic information security training, privacy training, and
business ethics training for all employees and contract resources.
Use or disclosure of this proposal is subject to the restrictions on the cover page.
Page 235
Sanction Policy. Motorola maintains a sanction policy to address violations of Motorola's internal
security requirements as well as those imposed by law, regulation, or contract.
Background Checks. Motorola follows its standard mandatory employment verification requirements
for all new hires. In accordance with Motorola internal policy, these requirements will be periodically
reviewed and include criminal background checks, proof of identity validation and any additional
checks as deemed necessary by Motorola.
Measures for ensuring events logging
Motorola logs, or enables Customers to log, access and use of products or services that Process
Customer Data. Logging of defined system activities, with appropriate event details, is required by
Motorola policy. Such policy also requires integrated audit record review via a security information
event management system and requirements for appropriate audit trail log management.
Measures for certification/assurance of processes and products
Motorola performs internal security evaluations such as secure application reviews and Secure
Design Review as well as production readiness reviews prior to product or service release. Where
appropriate, privacy assessments are performed for Motorola's products and services. A risk register
is created as a result of internal evaluations with assignments tasked to appropriate personnel.
Security audits are performed annually with additional audits as needed. Additional privacy
assessments, including updated data maps, may occur when material changes are made to the
products or services. Further, Motorola has achieved AICPA SOC2 Type 2 reporting and ISO/IEC
27001:2013 certification for the scope as set forth in its applicable certificate found at the Motorola
Solutions Trust Center.
Measures for ensuring data minimization
Motorola policies require processing of all personal information in accordance with applicable law,
including when that law requires data minimization. Further, Motorola conducts privacy assessments
of its products and services and evaluates if those products and services support the principles of
processing, such as data minimization.
Measures for ensuring data quality
Motorola policies require processing of all personal information in accordance with applicable law,
including when that law requires ensuring the quality and accuracy of data. Further, Motorola
conducts privacy assessments of its products and services and evaluates if those products and
services support the principles of processing, such as ensuring data quality.
Measures for ensuring limited data retention
Motorola maintains a data retention policy that provides a retention schedule outlining storage
periods for Personal Data. The schedule is based on business needs and provides sufficient
information to identify all records and to implement disposal decisions in line with the schedule. The
policy is periodically reviewed and updated.
Measures for ensuring accountability
To ensure compliance with the principle of accountability, Motorola maintains a Privacy Program
which generally aligns its activities to industry standard frameworks including the Nymity Privacy
Management and Accountability Framework, NIST Privacy Framework and ISO 27701. The Privacy
Program is audited annually by Motorola Solutions Audit Services.
Measures for allowing data portability and ensuring erasure
Use or disclosure of this proposal is subject to the restrictions on the cover page.
Page 236
When subject to a data subject request to move, copy or transfer their personal data, Motorola will
provide personal data to the Controller in a structured, commonly used and machine readable format.
Where possible and if the Controller requests it, Motorola can directly transmit the personal
information to another organization.
For transfers to Sub-processors
If, in the course of providing products and services under the Agreement, Motorola transfers
Customer Data containing Personal Data to Sub-processors, such Sub-processors will be subjected
to a security assessment and bound by obligations substantially similar, but at least as stringent, as
those included in this DPA.
Use or disclosure of this proposal is subject to the restrictions on the cover page.
Page 237
ANNEX III
SUB-PROCESSORS
Motorola Solutions Sub-processors are identified at the Motorola Solutions
Sub-processor Site unless otherwise identified below.
Use or disclosure of this proposal is subject to the restrictions on the cover page.
Page 10-1
Section 10
Exhibit F: CAD Functional
Response Matrix
Please reference the separate PDF version of this Matrix.
230055-Exhibit F -
CAD Functional Req
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
Motorola
CCF001
CAD Functional General
The general design of the system should
comply with the following requirements:
CAD
X
PremierOne complies with the functionality as described in the requirement.
1
Out of the Box
Motorola
CCF002
CAD Functional General
The system should be designed to operate as a
component of a comprehensive, seamlessly
integrated, incident-based Public Safety
Information Technology environment.
Examples would be integration with external
RMS systems, data warehouses, and external
reporting tools.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2
Out of the Box
Motorola
CCF003
CAD Functional General
Failover to the Disaster Recovery Site must not
be automatic and must be initiated by a System
User with the appropriate permission level.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
3
Out of the Box
Motorola
CCF004
CAD Functional General
The system should provide an Administration
and Security module that will allow the System
Administrator to control security, maintenance
of tables, backups, maintenance of reports,
screens, etc.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
4
Out of the Box
Motorola
CCF005
CAD Functional General
MCSO often must respond to new mandates
quickly that make it necessary to add new data
field to entry/retrieval masks and store their
entry content in the database. Vendors are
being asked to explain in detail how they can
satisfy this requirement.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement. The County will be
trained in the creation of masks.
5
Out of the Box
Motorola
CCF006
CAD Functional Reporting
The system should be capable of maintaining a
minimum of 10 years, plus current, of incident
data online without having to retrieve archived
data.
Mandatory
CAD
X
For optimal system performance, the following counts and recommendations for data retention
should not be exceeded. Five (5) years of PremierOne CAD data retention (2 years of live online
data and 3 years of archived data).
Sized for 5 years. Note to be added to Maintenance
and Support contract documentation to examine sizing
at year 5 as part of hardware refresh.
MCSO & Motorola teams agree requirement is
met out of the box per notes in Column O.
6
Cannot Meet
Motorola
CCF007
CAD Functional User Interface
The system should include as many labor saving
routines as possible. For example, when an
officer is preparing several reports related to a
single event the officer will not have to reenter
his/her badge number for each item, or the
location where the event occurred. Like
information should auto-populate.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
7
Out of the Box
Motorola
CCF008
CAD Functional Reporting
The system should have the ability to receive,
store, and manage data contained in selected
Maricopa County Sheriffs Office report forms.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
8
Out of the Box
Motorola
CCF009
CAD Functional General
The system should be designed to integrate
information logically, automatically, and
seamlessly with other systems, while
minimizing the use of point-to-point interfaces.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
9
Out of the Box
Motorola
CCF010
CAD Functional General
The system should include a geographically
based analytical tool (mapping) component
that provides analytical tools for viewing and
accessing spatial relationships among stored
data. Any data that is capable of having an
address or coordinates should be capable of
being represented visually on the map. This
includes incidents and other events, layering,
districts, hydrants, stations, jurisdictional
boundaries, and hospitals. The vendor's GIS
mapping system should interface with an ESRI
GIS and the vendor should be able to import
MCSO's GIS data into their GIS solution. The
vendor should provide means to facilitate new
uploads of GIS data into system for use with
their software. CAD spatial data should also
export into GIS.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement. Geo-spatial data is
uploaded to the system through tools implemented within Esri ArcGIS. Address validation data is
maintained in redundant Microsoft SQL Server geodatabases that store locations and boundaries
both spatially and in optimized search tables. Esri ArcGIS Servers provide routing and ETA
calculations using the Network Analyst extension. Client maps are displayed using Esri ArcGIS
Engine. Spatial data cannot be exported back to the GIS from CAD. The GIS data cannot be edited
directly from CAD.
10
Out of the Box
Motorola
CCF011
CAD Functional General
User import of data should not result in
slowdowns, downtime or the breaking of any
relational linkages.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
11
Out of the Box
Motorola
CCF012
CAD Functional Reporting
The system should provide the capability for an
audit trail of all transactions including records
views.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
12
Out of the Box
Motorola
CCF013
CAD Functional Reporting
All information contained within the CAD
should be available for inquires and report
production.
Preferred
CAD
X
PremierOne complies with the functionality as described in the requirement.
13
Out of the Box
Motorola
CCF014
CAD Functional Interface
The system should include simple methods for
exporting CAD data into External Applications.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
14
Out of the Box
Motorola
CCF015
CAD Functional General
The system database should have the ability to
input, store, export, text, sound, images, other
objects, such as: pictures, diagrams, audio files,
video to a case record.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
15
Out of the Box
Motorola
CCF016
CAD Functional General
The system's report formats should be
sufficiently configurable.
Preferred
CAD
X
PremierOne complies with the functionality as described in the requirement.
16
Out of the Box
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Page 1of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CCF017
CAD Functional General
The system should have the ability to search
code tables by code or by code description.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
17
Out of the Box
Motorola
CCF018
CAD Functional General
The system should capture relevant user-
defined data elements and perform required
edit validation for:
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
18
Out of the Box
Motorola
CCF018-1
CAD Functional General
Uniformed Crime Reporting (UCR) (NIBRS)
system (edit to ensure that required fields are
entered at time of entry)
Mandatory
CAD
X
PremierOne complies with the functionality in our included PremierOne Records application.
19
Out of the Box
Motorola
CCF018-2
CAD Functional General
Master Name Index (MNI)
Mandatory
CAD
X
PremierOne complies with the functionality in our included PremierOne Records application.
20
Out of the Box
Motorola
CCF018-3
CAD Functional General
Master Vehicle Index (MVI)
Mandatory
CAD
X
PremierOne complies with the functionality in our included PremierOne Records application.
21
Out of the Box
Motorola
CCF018-4
CAD Functional General
Master Property Index (MPI)
Mandatory
CAD
X
PremierOne complies with the functionality in our included PremierOne Records application.
22
Out of the Box
Motorola
CCF018-5
CAD Functional General
Master Telephone Index (MTI)
Mandatory
CAD
X
PremierOne complies with the functionality in our included PremierOne Records application.
23
Out of the Box
Motorola
CCF018-6
CAD Functional General
Automated Field Reporting
Mandatory
CAD
X
PremierOne complies with the functionality in our included PremierOne Records application.
24
Out of the Box
Motorola
CCF018-7
CAD Functional General
Investigations
Mandatory
CAD
X
PremierOne complies with the functionality in our included PremierOne Records application.
25
Out of the Box
Motorola
CCF018-8
CAD Functional General
Case Management
Mandatory
CAD
X
PremierOne complies with the functionality in our included PremierOne Records application.
26
Out of the Box
Motorola
CCF018-9
CAD Functional General
Crime Analysis
Mandatory
CAD
X
PremierOne complies with the functionality in our included PremierOne Records application.
27
Out of the Box
Motorola
CCF018-10
CAD Functional General
Arrest and Booking
Mandatory
CAD
X
PremierOne complies with the functionality in our included PremierOne Records application.
28
Out of the Box
Motorola
CCF018-11
CAD Functional General
Warrant Control
Mandatory
CAD
X
PremierOne complies with the functionality in our included PremierOne Records application.
29
Out of the Box
Motorola
CCF018-12
CAD Functional General
Registrant Tracking
Mandatory
CAD
X
PremierOne complies with the functionality in our included PremierOne Records application.
30
Out of the Box
Motorola
CCF018-13
CAD Functional General
Neighborhood Services
Mandatory
CAD
X
PremierOne complies with the functionality in our included PremierOne Records application.
31
Out of the Box
Motorola
CCF018-14
CAD Functional General
Code Enforcement
Mandatory
CAD
X
PremierOne complies with the functionality in our included PremierOne Records application.
32
Out of the Box
Motorola
CCF018-15
CAD Functional General
Animal Control
Mandatory
CAD
X
PremierOne complies with the functionality in our included PremierOne Records application.
33
Out of the Box
Motorola
CCF018-16
CAD Functional General
Accreditation
Mandatory
CAD
X
PremierOne complies with the functionality in our included PremierOne Records application.
34
Out of the Box
Motorola
CCF018-17
CAD Functional General
County Probation
Mandatory
CAD
X
PremierOne complies with the functionality in our included PremierOne Records application.
35
Out of the Box
Motorola
CCF019
CAD Functional General
The system must be designed with virtual
server failover functionality so that failure of
one virtual server does not cause any service
interruption to the users.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
36
Out of the Box
Motorola
CCF020
CAD Functional User Interface
The system should also provide the ability to
add icons to the application area with links to
County supplied documents by having an Icon
and short description of the document.
Mandatory
CAD
X
PremierOne partially complies with this functionality. It can be done in the Mobile environment,
but cannot be done on the Calltaker/Dispatcher workstations.
37
Out of the Box
Motorola
CCF021
CAD Functional User Interface
The CAD system should have an online help
feature and user guides with Windows
Hypertext, which includes instructions for
accessing user documentation. This function is
user programmable and may be searched
according to key words such as function names,
commands, or other easily recognized subjects.
It should support searching by context index, or
a find feature that provides a description of the
topic and a hypertext link to eliminate
directions to the information.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
38
Out of the Box
Motorola
CCF022
CAD Functional General
The vendor should also provide help files that
describe system commands and procedures.
Users should be able to search for a command,
or select from a command list. Double clicking
or selection with the cursor displays the help
information.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
39
Out of the Box
Motorola
CCF023
CAD Functional General
The vendor should provide documentation on
the system’s functional aspects.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
40
Out of the Box
Motorola
CCF024
CAD Functional User Interface
The system should permit users to data fill
those fields that are pre-defined (pick lists). If
the data remains invalid, a data pick list
displays, and the user can navigate through the
list to the desired entry, select that entry, and
the correct code is automatically entered into
the field.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
41
Out of the Box
Motorola
CCF025
CAD Functional General
The system should be capable of providing
administrative/supervisory control over who
can update and create pick lists.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
42
Out of the Box
Page 2of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CCF026
CAD Functional User Interface
If the user should enter an incorrect data into
any pre-defined field, the system should return
an error message. This feature should be user
configurable to prevent the lists from appearing
if so desired.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
43
Out of the Box
Motorola
CCF027
CAD Functional Reporting
MCSO would like the capability to track
common data entry errors so that they can
address some of them via training.
Mandatory
CAD
X
PremierOne does not have this functionality.
Address validation potentially the only data entry to
look at and there is bypass address functionality.
MCSO team states this is not a mandatory
requirement, explained functionality.
MCSO team stated this is not required to be met.
44
Cannot Meet
Motorola
CCF028
CAD Functional General
This process should provide for data integrity
and consistency by trapping data errors at input
time.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
45
Out of the Box
Motorola
CCF029
CAD Functional General
All pertinent documentation should be
available online and the system administrator
should be able to control its access.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
46
Out of the Box
Motorola
CCF030
CAD Functional General
The vendor shall indicate the availability of
placing the Disaster Recovery platform in a
Government Cloud.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
47
Out of the Box
Motorola
CCF031
CAD Functional General
The system must utilize Microsoft System
Center Operations Manager.
CAD
X
PremierOne complies with the functionality as described in the requirement.
48
Out of the Box
Motorola
CCF031
CAD Functional General
The system must provide and support multiple
operating environments, including a production
environment and a Test/Training environment.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
49
Out of the Box
Motorola
CCF032
CAD Functional General
The system must be sized to provide the
capability of handling at least two times the
normal peak workload.The system must be
sized to provide the capability of handling an
increased load of up to 100% as a result of
temporary surges during a major event.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
50
Out of the Box
Motorola
CCF033
CAD Functional General
The system must support system backups
without any down time or performance
degradation.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
51
Out of the Box
Motorola
CCF034
CAD Functional General
The system must support system upgrades
without any down time or performance
degradation.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
52
Out of the Box
Motorola
CCF035
CAD Functional General
The system must ensure that routine
maintenance or administration does not
require system down time or system reboots.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
53
Out of the Box
Motorola
CCF035
CAD Functional Security
The system must provide the capability of
adding additional hardware or software
components without negatively affecting
system performance.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
54
Out of the Box
Motorola
CCF036
CAD Functional Security
The system must integrate with MCSO's Active
Directory Domain system for authentication.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
55
Out of the Box
Motorola
CCF037
CAD Functional Security
The system must use FIPS certified technologies
to protect data at rest and in transit.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
56
Out of the Box
Motorola
CCF038
CAD Functional Security
Prior to using the system, users must be
required to logon with a maximum of the
following:
- A valid user ID
- A password
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
57
Out of the Box
Motorola
CCF039
CAD Functional Security
The proposed system must incorporate role-
based security.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
58
Out of the Box
Motorola
CCF040
CAD Functional Security
Security levels and user profiles must be
defined by system administrators.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
59
Out of the Box
Motorola
CCF041
CAD Functional Security
Security profiles must provide the capability of
being assigned to individual devices such as
workstations, handhelds, etc.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
60
Out of the Box
Motorola
CCF042
CAD Functional Security
The proposed system must include a security
profile for devices which has the option to limit
access to forms, queries, commands, features,
interfaces, etc. within the application based on
the device type and user role.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
61
Out of the Box
Motorola
CCF043
CAD Functional Security
The system must maintain a secure log of all
unauthorized access attempts into the
databases.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
62
Out of the Box
Motorola
CCF044
CAD Functional Security
The system must maintain a secure log of all
failed sign-on attempts by user, device ID, date,
and time.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
63
Out of the Box
Motorola
CCF045
CAD Functional Security
For multi-jurisdiction/multi-agency use, the
system must allow each jurisdiction/agency the
ability to control the security for their agency's
users.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
64
Out of the Box
Motorola
CCF045
CAD Functional General
The system must have a High Availability
architecture at the Primary PSAP location.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
65
Out of the Box
Motorola
CCF046
CAD Functional General
The system must allow alphanumeric employee
IDs in the system (IE: S0123456)
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
66
Out of the Box
Page 3of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CCF047
CAD Functional User Interface
The system must use a Graphical User Interface
(GUI), designed for ease of use, utilizing
industry standard graphical interfaces with pull-
down fields using defaults and automatic fill.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
67
Out of the Box
Motorola
CCF048
CAD Functional User Interface
The system must utilize all standard Windows
functionality regarding the sizing and
placement of windows and the ability to sort
columnar data by pointing and clicking.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
68
Out of the Box
Motorola
CCF049
CAD Functional User Interface
The system's User Interface must utilize menus,
keyboard shortcuts, point and click, and
function keys to operate and navigate.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
69
Out of the Box
Motorola
CCF050
CAD Functional User Interface
The system must allow the user to execute all
commands and functions with both a command
line and mouse.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
70
Out of the Box
Motorola
CCF051
CAD Functional User Interface
The system must support a multi-
jurisdiction/multi-agency environment.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
71
Out of the Box
Motorola
CCF052
CAD Functional User Interface
The system must allow multiple agencies to
operate on a shared system/platform while
maintaining separate data integrity on the
same database with access controlled by
security.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
72
Out of the Box
Motorola
CCF053
CAD Functional User Interface
The system must allow each agency to create
agency specific business rules as to the
operation of the system.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
73
Out of the Box
Motorola
CCF054
CAD Functional User Interface
The system must provide the ability to
continuously display updated information.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
74
Out of the Box
Motorola
CCF055
CAD Functional User Interface
The system must provide the ability for all
inactive windows to continuously be updated
as if they were active.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
75
Out of the Box
Motorola
CCF056
CAD Functional User Interface
The system must provide online help and quick-
start help functions within applications and
modules.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
76
Out of the Box
Motorola
CCF057
CAD Functional User Interface
The system must allow for system
administrators to add agency specific help text
to the system help functions. Any new releases
or fixes must not overlay or overwrite any user
specific help.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
77
Out of the Box
Motorola
CCF058
CAD Functional User Interface
The system must provide a thin-client
architecture or Browser User Interface (BUI) for
the configuration portal.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
78
Out of the Box
Motorola
CCF059
CAD Functional General
The system must allow the programming of
keyboard function keys.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
79
Out of the Box
Motorola
CCF060
CAD Functional General
The system must permit the configuration of
command line commands.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
80
Out of the Box
Motorola
CCF061
CAD Functional General
The system must include highly configurable
status monitors such that:
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
81
Out of the Box
Motorola
CCF062
CAD Functional General
CAD shall support user-defined windows or
monitor sets for dynamically updated views of
ongoing incident, unit, and interface activities
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
82
Out of the Box
Motorola
CCF063
CAD Functional General
Incident monitors shall be able to display
active/pending incidents by area and incident
status.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
83
Out of the Box
Motorola
CCF064
CAD Functional General
Incident status monitors shall have the ability
to display individual dispatches by alarm level
or time of dispatch
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
84
Out of the Box
Motorola
CCF065
CAD Functional General
The status monitor shall support the ability for
system administrators, groups, or each
individual to configure the layout of the
workstation screen(s), depending on the
number of monitors at the workstations, so
workstation windows for pending queues,
active units display, active incidents, etc., are
not "hard-coded".
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
85
Out of the Box
Motorola
CCF066
CAD Functional General
The status monitor shall make use of color,
sound (.wav files), and flashing in addition to
textual information to enhance status
recognition. These assignments shall be user-
definable.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
86
Out of the Box
Motorola
CCF067
CAD Functional General
Filtering and sort order of data shall be
configurable per monitor set.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
87
Out of the Box
Motorola
CCF068
CAD Functional General
CAD commands and functions shall be
programmable as mouse functions uniquely for
each individual status monitor.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
88
Out of the Box
Motorola
CCF069
CAD Functional General
Incident commands shall be available in Unit
status monitors and Unit Command shall be
available in Incident status monitors as mouse
functions
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
89
Out of the Box
Motorola
CCF070
CAD Functional General
The mouse functions shall support setting
default values (for example in building
common status changes) or prompt the user to
enter a value.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
90
Out of the Box
Page 4of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CCF071
CAD Functional General
When using the mouse functions within the
status monitor the functions shall use the unit
ID or incident the user has selected and not
require them to re-enter this data.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
91
Out of the Box
Motorola
CCF072
CAD Functional General
When configuring a status monitor the user
shall be able to select the fields, the length of
the fields, and the order of the fields to be
displayed.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
92
Out of the Box
Motorola
CCF073
CAD Functional General
The user shall have the ability to save the status
monitor placement on the desktop as a follow-
me setting
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
93
Out of the Box
Motorola
CCF074
CAD Functional Auditing
The system must be capable of maintaining a
history of system access by user(s) including
dates, times, and workstations which must be
able to be queried by user-defined attributes.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
94
Out of the Box
Motorola
CCF075
CAD Functional Auditing
The system must provide the capability to audit
all functions at the user level.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
95
Out of the Box
Motorola
CCF076
CAD Functional Auditing
The system must allow audit logging to be
definable by a system administrator.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
96
Out of the Box
Motorola
CCF077
CAD Functional Auditing
The system must maintain a secure log of all
user activity.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
97
Out of the Box
Motorola
CCF078
CAD Functional Auditing
The system must allow for system
administration to be supported by detailed
auditing and reporting capabilities.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
98
Out of the Box
Motorola
CCF079
CAD Functional Support
The vendor must guarantee support for
software while the systems are covered under
warranty and/or by maintenance contracts.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
99
Out of the Box
Motorola
CCF080
CAD Functional Support
24/7/365 Support must be provided (phone,
internet, email, etc.)
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
100
Out of the Box
Motorola
CCF081
CAD Functional Support
The vendor must provide a secure remote
management tool, within MCSO's guidelines, to
permit access to the servers for
troubleshooting in cases where assistance is
needed.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
101
Out of the Box
Motorola
CCF082
CAD Functional Support
Vendor must monitor the infrastructure and
reliability from a 24/7/365 NOC.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
102
Out of the Box
Motorola
CCF083
CAD Functional General
The system should have the ability to display
multiple command lines at once.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement. Multiple Command
Lines can be seen at once, however, each Command Line is designated for a specific event.
103
Out of the Box
Motorola
CCF084
CAD Functional General
The CAD Command Line should have the ability
to control every function of CAD directly from
the command line. Every function from the
software should be integrated into the CAD
Command Line without limiting dispatcher
workflows by using the mouse.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
104
Out of the Box
Motorola
CCF085
CAD Functional General
The CAD Command Line should keep a history
of previous used commands. Allowing the user
to nagivate using the mouse or keyboard if
desired.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
105
Out of the Box
Motorola
CCF086
CAD Functional General
Ability to create automated commands that
allow the user to run multiple workflows using
one command line.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
106
Out of the Box
Motorola
CCHEC001
CAD Call
Handling /
Event Create
Call Handling
The system shall import and attach/append,
automatically upon user command, automatic
number information (ANI) and automatic
location information (ALI) to a CFS.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
107
Out of the Box
Motorola
CCHEC002
CAD Call
Handling /
Event Create
Call Handling
The system shall import (automatically)
external alarm data that conforms to the
APCO/CSAA (Central Station Alarm Association)
published ANS; and, The system shall generate
a CFS upon receipt of a new alarm notification.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement. A Palo Verde
Nuclear Plant Alarms interface has been included in the solution.
108
Out of the Box
Page 5of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CCHEC003
CAD Call
Handling /
Event Create
Call Handling
The system shall import (automatically) a CFS
received from another CAD system.
Mandatory
CAD
X
The PremierOne CAD-to-CAD interface allows for the bi-directional transfer of incident and unit
data. This transfer occurs between one or more External systems that are communicating with
PremierOne via the CAD-to-CAD interface and is accomplished with messaging to and from
PremierOne. This two-way transfer supports Primary or Secondary PSAPs that need to send an
incident to another system for processing and management. It also supports agencies that need
to identify and dispatch resources across jurisdictional boundaries in cases of mutual aid or
disasters. The CAD-to-CAD interface replaces the need for requests for resources from an External
System to be handled verbally via telephone between agencies.
The Motorola Solutions PremierOne CAD-to-CAD interface is configured through the product by:
ͻWƌŽǀŝƐŝŽŶŝŶŐƚŚĞĞdžƚĞƌŶĂůĂŐĞŶĐLJ
ͻĞĨŝŶŝŶŐƚŚĞďƵƐŝŶĞƐƐƌƵůĞƐĨŽƌƚŚĞŝŶƚĞƌĨĂĐĞ͘
When CAD-to-CAD is desired with a disparate CAD system, a CAD-to-CAD HUB Interface would be
required.
A CAD-to-CAD HUB or Exchange is a CAD vendor neutral, functional interoperability platform. At
the regional level, it provides real-time access to unit and incident details, the ability to remotely
dispatch units from neighboring jurisdictions, as well as providing a real-time view of dispatch
activity across the region. Additionally, a hub or exchange provides a level of isolation between
the participants. This is important as new agencies join or existing agencies depart the exchange.
Existing operational interactions between agencies that remain is unchanged.
Motorola Solutions + EDC Hub | Vendors participating in CAD-to-CAD via Hub:
ͻDŽƚŽƌŽůĂ^ŽůƵƚŝŽŶƐWƌĞŵŝĞƌKŶĞ
ͻ,ĞdžĂŐŽŶͬ /ŶƚĞƌŐƌĂƉŚ
ͻĞŶƚƌĂů^ƋƵĂƌĞdŝďƵƌŽŶ
ͻĞŶƚƌĂů^ƋƵĂƌĞͬ dƌŝdĞĐŚ/ŶĨŽƌŵ
ͻdLJůĞƌdĞĐŚŶŽůŽŐŝĞƐͬ EĞǁtŽƌůĚ
ͻĞŶƚƌĂů^ƋƵĂƌĞͬ K^^/KŶĞ^ŽůƵƚŝŽŶ
Motorola Solutions welcomes the opportunity to discuss the available options and to gather the
109
Out of the Box
Motorola
CCHEC004
CAD Call
Handling /
Event Create
Call Handling
The system should have the ability to display
multiple command lines at once.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
110
Out of the Box
Motorola
CCHEC005
CAD Call
Handling /
Event Create
Call Handling
The CAD Command Line should keep a history
of previous used commands. Allowing the user
to nagivate using the mouse or keyboard if
desired.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
111
Out of the Box
Motorola
CCHEC006
CAD Call
Handling /
Event Create
CAD Incident /Event
Type
The system shall allow for system administrator-
defined CAD incident types or nature codes.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
112
Out of the Box
Motorola
CCHEC007
CAD Call
Handling /
Event Create
CAD Incident /Event
Type
The system shall allow system users to modify
the incident type and provide new/updated
response plan information/suggestions based
on the new incident type.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
113
Out of the Box
Motorola
CCHEC008
CAD Call
Handling /
Event Create
CAD Incident /Event
Type
The system shall provide the capability to
create an event, assign a unit, and close the
event with a disposition without going through
the dispatch process steps.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
114
Out of the Box
Motorola
CCHEC009
CAD Call
Handling /
Event Create
CAD Incident /Event
Type
The system shall provide the capability to flag a
CFS (Call for Service) as an “Advised Event”
separate from the incident type/nature code.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
115
Out of the Box
Motorola
CCHEC010
CAD Call
Handling /
Event Create
Update Call for
Service
The system shall enable the user to enter
supplemental (new) information into the CFS
(Call for Service) event record of one or more
user-specified CAD events.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
116
Out of the Box
Motorola
CCHEC011
CAD Call
Handling /
Event Create
Update Call for
Service
The system shall display a notification of the
event update at each appropriate CAD position
whenever an active event record is updated, as
determined by the system’s configuration.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
117
Out of the Box
Motorola
CCHEC012
CAD Call
Handling /
Event Create
Update Call for
Service
The system shall create an automatic time/date
stamp for every transaction related to an event,
and The system shall store the responsible
operator’s identification (ID), the console ID,
and the nature of the change.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
118
Out of the Box
Motorola
CCHEC013
CAD Call
Handling /
Event Create
Update Call for
Service
The system shall add audit records to the event
history or store audit records in the CAD
system’s audit log file in chronological order;
and, The system shall provide a complete
historical audit of all event activity (e.g.,
comments, unit status changes, license plate
information, field updates).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
119
Out of the Box
Motorola
CCHEC014
CAD Call
Handling /
Event Create
Update Call for
Service
The system shall store old entry information,
with the appropriate date, time, operator ID,
and console stamps if the new entry replaces
existing information in the event record.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
120
Out of the Box
Motorola
CCHEC015
CAD Call
Handling /
Event Create
Update Call for
Service
The system shall enable the audit information
to be retrieved and printed in both summary
and detailed formats when incident
information is displayed.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
121
Out of the Box
Motorola
CCHEC016
CAD Call
Handling /
Event Create
Update Call for
Service
The system shall create a permanent audit trail
for all information recorded related to an
event, whether or not that information is later
modified or deleted.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
122
Out of the Box
Page 6of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CCHEC017
CAD Call
Handling /
Event Create
Update Call for
Service
The system shall support ease of entry for
supplemental event information and changes
to existing event information.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
123
Out of the Box
Motorola
CCHEC018
CAD Call
Handling /
Event Create
Update Call for
Service
The system shall allow the user to display a
supplemental data entry screen by specifying
either the event number or a unit assigned to
the event.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
124
Out of the Box
Motorola
CCHEC019
CAD Call
Handling /
Event Create
Update Call for
Service
The system shall allow the user to display a
data entry screen to change information
previously entered into a CAD event by
specifying either the event number or a unit
assigned to the event.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
125
Out of the Box
Motorola
CCHEC020
CAD Call
Handling /
Event Create
Update Call for
Service
The system shall provide agency-definable
visual and audible alerts to notify field units and
other appropriate CAD system users, including
users of systems interfaced to CAD such as
MDC's (Mobile Data Computers), of event
changes and supplemental information.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
126
Out of the Box
Motorola
CCHEC021
CAD Call
Handling /
Event Create
Update Call for
Service
The system shall allow the user to add
supplemental information and/or change active
events.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
127
Out of the Box
Motorola
CCHEC022
CAD Call
Handling /
Event Create
Update Call for
Service
The system shall allow the user to update any
field in the CFS event record (except user-
designated fields, such as application-generated
times and date stamps, operator identification
information, ANI/ALI information, and CAD
position that completed a CAD transaction).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
128
Out of the Box
Motorola
CCHEC023
CAD Call
Handling /
Event Create
Update Call for
Service
The system shall document all changes and
supplemental information in the event history.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
129
Out of the Box
Motorola
CCHEC024
CAD Call
Handling /
Event Create
Update Call for
Service
The system shall provide an event
update/change data entry screen.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
130
Out of the Box
Motorola
CCHEC025
CAD Call
Handling /
Event Create
Update Call for
Service
The system shall allow the user to update or
change a unit’s most recent event by entering
the unit’s identification or any unit that is
currently assigned.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
131
Out of the Box
Motorola
CCHEC026
CAD Call
Handling /
Event Create
Update Call for
Service
The system shall require confirmation from the
user when attempting to update any field in a
closed event.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
132
Out of the Box
Motorola
CCHEC027
CAD Call
Handling /
Event Create
Update Call for
Service
The system shall provide the user with
acknowledgment that an update to a CAD
event record was successfully completed.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
133
Out of the Box
Motorola
CCHEC028
CAD Call
Handling /
Event Create
Update Call for
Service
The system shall allow the user to supplement
and/or change active events.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
134
Out of the Box
Motorola
CCHEC029
CAD Call
Handling /
Event Create
Update Call for
Service
The system shall allow the user to supplement
and/or change any field of a closed event
without having to change the state of the
event.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
135
Out of the Box
Motorola
CCHEC030
CAD Call
Handling /
Event Create
General
The system shall provide the capability to close
out the CFS record without assigning a
resource, if it is determined that a CFS does not
require the assignment of a resource(s).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
136
Out of the Box
Motorola
CCHEC031
CAD Call
Handling /
Event Create
General
The system shall allow the user to append a
disposition code and comments to events that
are not assigned any resources.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
137
Out of the Box
Motorola
CCHEC032
CAD Call
Handling /
Event Create
Disposition
The system shall allow the user to enter one or
more dispositions, as dictated by MCSO's
policy, when a CAD event is closed.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
138
Out of the Box
Motorola
CCHEC033
CAD Call
Handling /
Event Create
Disposition
The system shall close a CAD event record
automatically if no resources remain assigned
to the event.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
139
Out of the Box
Motorola
CCHEC034
CAD Call
Handling /
Event Create
Disposition
The system shall provide the capability for a
mobile unit to enter one or more dispositions
when clearing from a CAD event.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
140
Out of the Box
Motorola
CCHEC035
CAD Call
Handling /
Event Create
Event Classification
and Priority
The system shall enable CAD users to select the
appropriate incident/event type from a pre-
defined list of codes based upon information
received from reporting party.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
141
Out of the Box
Motorola
CCHEC036
CAD Call
Handling /
Event Create
Event Classification
and Priority
The system shall provide, in a multiple dispatch
agency or jurisdiction environment, the ability
to create multiple CFS (Calls for Service) events
with a single CFS (Calls for Service) event entry
(e.g. a shooting incident type would create
multiple events needing resources from
multiple linked agencies)
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
142
Out of the Box
Page 7of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CCHEC037
CAD Call
Handling /
Event Create
Event Classification
and Priority
The system shall provide the ability to generate
a CFS (Call for Service) event with only the
location and incident type code entered.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
143
Out of the Box
Motorola
CCHEC038
CAD Call
Handling /
Event Create
Event Classification
and Priority
The system shall allow the user to upgrade or
downgrade the CFS event to fit the reported
event by changing the priority for the event.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
144
Out of the Box
Motorola
CCHEC039
CAD Call
Handling /
Event Create
Event Classification
and Priority
The system shall allow the user to utilize
incident screening menus, such as a drop-down
menu, to assist in determining the appropriate
incident/event type code.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
145
Out of the Box
Motorola
CCHEC040
CAD Call
Handling /
Event Create
Event Classification
and Priority
The system shall allow the user to interrupt the
CFS event creation process and save entered
information, sometimes known as call stacking,
to process a higher priority incoming incident.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
146
Out of the Box
Motorola
CCHEC041
CAD Call
Handling /
Event Create
Event Classification
and Priority
The system shall provide a warning notification
of the held CFS event generated at an
administrator-configured time. Any position can
review current CFS events, retrieve a partial CFS
record, and complete the CFS event entry.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
147
Out of the Box
Motorola
CCHEC042
CAD Call
Handling /
Event Create
Event Classification
and Priority
The number of partial CFS events that can be
stacked by a single position The system shall be
an administrator-configurable system
parameter.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
148
Out of the Box
Motorola
CCHEC043
CAD Call
Handling /
Event Create
Event Classification
and Priority
The system shall provide the ability to override
the event priority.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
149
Out of the Box
Motorola
CCHEC044
CAD Call
Handling /
Event Create
Event Classification
and Priority
The system shall provide the ability to create
and maintain incident screening menus or
prompts that can be used to aid the call taker in
determining the appropriate incident/event
type code.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
150
Out of the Box
Motorola
CCHEC045
CAD Call
Handling /
Event Create
Event Classification
and Priority
The system shall provide the ability to save one
or more partially completed CFS events in order
to enter a higher priority incident, keeping all
entered data intact.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
151
Out of the Box
Motorola
CCHEC046
CAD Call
Handling /
Event Create
Event Classification
and Priority
The system shall provide a warning (visual
and/or audible) that a partially completed CFS
(Calls for Service) event has been held for an
administrator-defined period of time.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
152
Out of the Box
Motorola
CCHEC047
CAD Call
Handling /
Event Create
Event Classification
and Priority
The system shall provide the ability to view a
summary of all system-wide, partially-
completed CFS events being held and awaiting
completion.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
153
Out of the Box
Motorola
CCHEC048
CAD Call
Handling /
Event Create
Event Classification
and Priority
The summary The system shall include, at a
minimum, the position and user ID that placed
the CFS event on hold and the elapsed time
that the CFS event has been on hold.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
154
Out of the Box
Motorola
CCHEC049
CAD Call
Handling /
Event Create
Event Classification
and Priority
The system shall provide the ability to redirect
assigned resources to a higher priority CFS
(Calls for Service) event based on MCSO's
defined criteria.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
155
Out of the Box
Motorola
CCHEC050
CAD Call
Handling /
Event Create
Event Classification
and Priority
The system shall store all active and partially
completed CAD events in system administrator-
configurable queues.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
156
Out of the Box
Motorola
CCHEC051
CAD Call
Handling /
Event Create
Event Classification
and Priority
The system shall allow CAD users to be able to
select a partially completed CFS (Calls for
Service) event from a CAD event queue and
complete the CFS (Calls for Service) entry
process.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
157
Out of the Box
Motorola
CCHEC052
CAD Call
Handling /
Event Create
Check for Duplicate
Incidents
The system shall store all transactions resulting
from the duplicate event detection process in
the system’s audit log.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
158
Out of the Box
Motorola
CCHEC053
CAD Call
Handling /
Event Create
Check for Duplicate
Incidents
The system shall identify during the creation of
a CFS event whether the event is a potential
duplicate of an active CAD event or an event
recently closed; and, The system shall notify the
call taker of the results.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
159
Out of the Box
Motorola
CCHEC054
CAD Call
Handling /
Event Create
Check for Duplicate
Incidents
The system shall check, as configured by the
system administrator, by exact street address,
street address block range, or geo-coordinates,
the location of each new CFS event to
determine whether another event exists.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
160
Out of the Box
Motorola
CCHEC055
CAD Call
Handling /
Event Create
Check for Duplicate
Incidents
Based on system parameters set by the
administrator, either all matching events The
system shall be presented to the user, or only
those events with the same or similar nature
code.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
161
Out of the Box
Page 8of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CCHEC056
CAD Call
Handling /
Event Create
Check for Duplicate
Incidents
The system shall check, as configured by the
system administrator, within a pre-defined
search radius of the location of each new CFS
event, to determine whether another event
exists within the search radius.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
162
Out of the Box
Motorola
CCHEC057
CAD Call
Handling /
Event Create
Check for Duplicate
Incidents
Based on system parameters set by the
administrator, either all matching events The
system shall be presented to the user, or only
those events with the same or similar nature
code.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
163
Out of the Box
Motorola
CCHEC058
CAD Call
Handling /
Event Create
Check for Duplicate
Incidents
The system shall allow an authorized user to
change the duplicate event search parameters
(e.g. distance, exact street address match only,
street address block range).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
164
Out of the Box
Motorola
CCHEC059
CAD Call
Handling /
Event Create
Check for Duplicate
Incidents
The system shall present the user with the
following information for each potential
duplicate event if potential duplicates are
located:
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
165
Out of the Box
Motorola
CCHEC060
CAD Call
Handling /
Event Create
Check for Duplicate
Incidents
Incident ID
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
166
Out of the Box
Motorola
CCHEC061
CAD Call
Handling /
Event Create
Check for Duplicate
Incidents
Type of incident
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
167
Out of the Box
Motorola
CCHEC062
CAD Call
Handling /
Event Create
Check for Duplicate
Incidents
Location of the incident
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
168
Out of the Box
Motorola
CCHEC063
CAD Call
Handling /
Event Create
Check for Duplicate
Incidents
Status of the incident
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
169
Out of the Box
Motorola
CCHEC064
CAD Call
Handling /
Event Create
Check for Duplicate
Incidents
The system shall allow the user the ability to
create a new CFS (Calls for Service) event and
link the event to the primary event record; or,
to merge any new information contained in a
duplicate event into the main event record
associated with the identified duplicate CAD
event.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
170
Out of the Box
Motorola
CCHEC065
CAD Call
Handling /
Event Create
Check for Duplicate
Incidents
The system shall allow the call taker to re-open
closed CAD events that are duplicates of a new
event, add additional information to the re-
opened CAD event records, and, if necessary, re-
route them back through the dispatch process.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
171
Out of the Box
Motorola
CCHEC066
CAD Call
Handling /
Event Create
Check for Duplicate
Incidents
The system shall, based on agency policy,
restrict users from changing or deleting any
previously entered data contained in re-opened
closed CAD events.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
172
Out of the Box
Motorola
CCHEC067
CAD Call
Handling /
Event Create
Check for Duplicate
Incidents
The system shall cross-reference duplicate
events to the primary event records, leave both
events open, or abandon processing of the
duplicate event.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
173
Out of the Box
Motorola
CCHEC068
CAD Call
Handling /
Event Create
Incident Information The system shall provide the ability to create a
CFS (Calls for Service) with minimum required
fields (e.g. location and event type).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
174
Out of the Box
Motorola
CCHEC069
CAD Call
Handling /
Event Create
Incident Information The system shall provide the ability to dispatch
once location and nature are obtained.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
175
Out of the Box
Motorola
CCHEC070
CAD Call
Handling /
Event Create
Incident Information The system shall provide the ability to
alter/augment event as further information is
obtained by the call taker.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
176
Out of the Box
Motorola
CCHEC071
CAD Call
Handling /
Event Create
Incident Information The system shall include an automated
connection/interface to the 9-1-1 telephone
system to use ANI/ALI and RapidSOS data to
populate the incident entry screen form.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
177
Out of the Box
Motorola
CCHEC072
CAD Call
Handling /
Event Create
Incident Information The system shall provide the ability to use
ANI/ALI data to assist with CFS (Calls for
Service) entry.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
178
Out of the Box
Motorola
CCHEC073
CAD Call
Handling /
Event Create
Incident Information The system shall provide the ability to enter
unlimited narrative with text wrap-around
feature.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
179
Out of the Box
Motorola
CCHEC074
CAD Call
Handling /
Event Create
Capture Location
Determination
The system shall obtain all different versions
(Standard, Standard Plus, Extended Plus) of
ANI/ALI information automatically from
interfaced phone systems without requiring the
user to manually re-enter the information into
a CAD event entry screen.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
180
Out of the Box
Motorola
CCHEC075
CAD Call
Handling /
Event Create
Capture Location
Determination
The system shall append 9-1-1 reported data to
the record if the user has entered data into any
field before accepting the 9-1-1 information,
but not overwrite the data entered by the user.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
181
Out of the Box
Page 9of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CCHEC076
CAD Call
Handling /
Event Create
Location Verification Validate the street name is an actual street in
the service area
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
182
Out of the Box
Motorola
CCHEC077
CAD Call
Handling /
Event Create
Location Verification Resolve ambiguities, while accounting for
spelling variations and duplications
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
183
Out of the Box
Motorola
CCHEC078
CAD Call
Handling /
Event Create
Location Verification Validate intersections
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
184
Out of the Box
Motorola
CCHEC079
CAD Call
Handling /
Event Create
Location Verification Validate address ranges
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
185
Out of the Box
Motorola
CCHEC080
CAD Call
Handling /
Event Create
Location Verification Relate common place names to actual
addresses
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
186
Out of the Box
Motorola
CCHEC081
CAD Call
Handling /
Event Create
Location Verification Transform latitude and longitude to map
coordinates for display
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
187
Out of the Box
Motorola
CCHEC082
CAD Call
Handling /
Event Create
Location Verification Translate incident locations to agency reporting
areas
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
188
Out of the Box
Motorola
CCHEC083
CAD Call
Handling /
Event Create
Location Verification Translate alias names into actual street names
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
189
Out of the Box
Motorola
CCHEC084
CAD Call
Handling /
Event Create
Location Verification Display high and low cross streets
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
190
Out of the Box
Motorola
CCHEC085
CAD Call
Handling /
Event Create
Location Verification Display city and county,
neighborhoods/localities
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
191
Out of the Box
Motorola
CCHEC086
CAD Call
Handling /
Event Create
Location Verification Assign and display the response areas
containing an incident
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
192
Out of the Box
Motorola
CCHEC087
CAD Call
Handling /
Event Create
Location Verification Assign and display the map pages where an
incident is located
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
193
Out of the Box
Motorola
CCHEC088
CAD Call
Handling /
Event Create
Location Verification Display CAD system premises warnings or
hazards based on the location of incident(s)
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
194
Out of the Box
Motorola
CCHEC089
CAD Call
Handling /
Event Create
Location Verification Display CAD system premises warnings or
hazards based on the incident type that are
within a configurable radius of incident
locations
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
195
Out of the Box
Motorola
CCHEC090
CAD Call
Handling /
Event Create
Location Verification Display prior incidents that occurred at an
incident’s location within a configurable period
of time
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
196
Out of the Box
Motorola
CCHEC091
CAD Call
Handling /
Event Create
Location Verification Display nearby incidents (user-defined criteria)
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
197
Out of the Box
Motorola
CCHEC092
CAD Call
Handling /
Event Create
Location Verification The system shall provide the ability to enter a
unique building and unit number to clearly
identify the location (e.g. 100 West Ave., Bldg.
2, Unit 1).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
198
Out of the Box
Motorola
CCHEC093
CAD Call
Handling /
Event Create
Location Verification The system shall, depending on the permissions
granted to the user, provide the ability to edit
ALI 9-1-1 information in the event record if the
information provided by the phone company is
incorrect.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
199
Out of the Box
Motorola
CCHEC094
CAD Call
Handling /
Event Create
Location Verification The system shall include the following fields for
all records containing an address: street
number; apartment/suite number; street; road
type (Drive, Avenue, Street, Alley); direction;
city, state, and/or zip code (modify list as
appropriate).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
200
Out of the Box
Motorola
CCHEC095
CAD Call
Handling /
Event Create
Location Verification The system shall validate entered incident
addresses against the CAD geofile.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
201
Out of the Box
Motorola
CCHEC096
CAD Call
Handling /
Event Create
Location Verification The system shall provide various suggestions to
assist users in selecting accurate incident
locations.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
202
Out of the Box
Motorola
CCHEC097
CAD Call
Handling /
Event Create
Location Verification The system shall provide the ability to search
commonplace names by entering the name
only on the location line without added
characters in front, such as @.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
203
Out of the Box
Motorola
CCHEC098
CAD Call
Handling /
Event Create
Location Verification The system shall allow each address or
commonplace name to have an unlimited
number of alias names.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
204
Out of the Box
Motorola
CCHEC099
CAD Call
Handling /
Event Create
Location Verification The system shall allow authorized users to store
multiple names for businesses and tenants for a
given street address.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
205
Out of the Box
Motorola
CCHEC100
CAD Call
Handling /
Event Create
Location Verification The system shall organize the display of
possible address matches in an ergonomic,
easily understood manner that aids users in
identifying valid incident locations.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
206
Out of the Box
Page 10of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CCHEC101
CAD Call
Handling /
Event Create
Location Verification The system shall allow authorized users to
configure their tactical map display to show
jurisdictional boundaries (e.g. city boundaries)
and to display potential valid incident locations
by jurisdiction.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
207
Out of the Box
Motorola
CCHEC102
CAD Call
Handling /
Event Create
Location Verification The system shall allow the user, in case the
location entered by the user is unverifiable (e.g.
the location does not exist in the geofile), the
capability to exit or bypass the verification
process and manually route the CFS (Calls for
Service) event(s) to the appropriate dispatch
position(s).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
208
Out of the Box
Motorola
CCHEC103
CAD Call
Handling /
Event Create
Location Verification The system shall provide the ability to enter a
partial street name, with a minimum number of
characters, and be presented with a list of
possible matches to pick from for an exact
match.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
209
Out of the Box
Motorola
CCHEC104
CAD Call
Handling /
Event Create
Location Verification The system shall provide the ability to enter an
incorrect street address for a correct street
name and be presented with a list of valid
ranges.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
210
Out of the Box
Motorola
CCHEC105
CAD Call
Handling /
Event Create
Location Verification The system shall provide the ability to enter
common street alias and abbreviations instead
of the actual street name (e.g. MLK for Martin
Luther King Blvd).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
211
Out of the Box
Motorola
CCHEC106
CAD Call
Handling /
Event Create
Location Verification The system shall provide the ability to override
the CAD system’s geofile by manually entering
valid response area data.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
212
Out of the Box
Motorola
CCHEC107
CAD Call
Handling /
Event Create
Location Verification The system shall provide the ability to enter a
reason for an overridden location.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
213
Out of the Box
Motorola
CCHEC108
CAD Call
Handling /
Event Create
Location Verification The system shall provide the ability to generate
a report of geofile overrides.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
214
Out of the Box
Motorola
CCHEC109
CAD Call
Handling /
Event Create
Location Verification The system shall provide the ability to display
the incident location in relation to other active
incidents on the system’s tactical map display
during the CAD event entry process.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
215
Out of the Box
Motorola
CCHEC110
CAD Call
Handling /
Event Create
Location Verification Data entry fields containing an address The
system shall follow the NENA Standard for NG9-
1-1 GIS Data Model (71-003), Section 3.5 (GIS
Database Model Layers) and should, at a
minimum, include the data elements contained
in the Site/Structure Address table.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
216
Out of the Box
Motorola
CCHEC111
CAD Call
Handling /
Event Create
Retrieve Incomming
Calls
The system shall include an interface to the 9-1-
1 telephone system that, upon user command,
causes the automatic transfer of an emergency
call’s ALI information from the telephone
system to an appropriate field of the CAD event
data entry screen.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
217
Out of the Box
Motorola
CCHEC112
CAD Call
Handling /
Event Create
Retrieve Incomming
Calls
The system shall allow call takers to initiate a
CAD command/or function that will cause the
CAD system to populate the CAD event data
entry screen with call-back telephone number
information if it is available.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
218
Out of the Box
Motorola
CCHEC113
CAD Call
Handling /
Event Create
Retrieve Incomming
Calls
The system shall transfer, depending on PSAP
policy, the telephone subscriber’s name to a
field in the CAD event data entry screen’s
reporting party’s name data field.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
219
Out of the Box
Motorola
CCHEC114
CAD Call
Handling /
Event Create
Retrieve Incomming
Calls
The system shall include data fields within the
CAD event data entry screen for reporting
party’s name, address and callback number
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
220
Out of the Box
Motorola
CCHEC115
CAD Call
Handling /
Event Create
Involved Person Info The system shall be capable of collecting the
following information about each individual
associated with an event:
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
221
Out of the Box
Motorola
CCHEC116
CAD Call
Handling /
Event Create
Involved Person Info Age
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
222
Out of the Box
Motorola
CCHEC117
CAD Call
Handling /
Event Create
Involved Person Info Date of Birth
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
223
Out of the Box
Motorola
CCHEC118
CAD Call
Handling /
Event Create
Involved Person Info Eye Color
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
224
Out of the Box
Motorola
CCHEC119
CAD Call
Handling /
Event Create
Involved Person Info Hair color
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
225
Out of the Box
Page 11of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CCHEC120
CAD Call
Handling /
Event Create
Involved Person Info Height
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
226
Out of the Box
Motorola
CCHEC121
CAD Call
Handling /
Event Create
Involved Person Info Name
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
227
Out of the Box
Motorola
CCHEC122
CAD Call
Handling /
Event Create
Involved Person Info Operators License Number
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
228
Out of the Box
Motorola
CCHEC123
CAD Call
Handling /
Event Create
Involved Person Info Operators License State
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
229
Out of the Box
Motorola
CCHEC124
CAD Call
Handling /
Event Create
Involved Person Info Race
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
230
Out of the Box
Motorola
CCHEC125
CAD Call
Handling /
Event Create
Involved Person Info Sex
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
231
Out of the Box
Motorola
CCHEC126
CAD Call
Handling /
Event Create
Involved Person Info Weight
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
232
Out of the Box
Motorola
CCHEC127
CAD Call
Handling /
Event Create
Involved Person Info Additional remarks (e.g. clothing description,
scars/marks/tattoos)
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
233
Out of the Box
Motorola
CCHEC128
CAD Call
Handling /
Event Create
Involved Person Info The system shall initiate an automatic query,
upon entry of information about an individual
associated with an event, using the following
guidelines at a minimum:
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
234
Out of the Box
Motorola
CCHEC129
CAD Call
Handling /
Event Create
Involved Person Info If the name only is known, then a name query
The system shall be initiated to local files
capable of performing a lookup based only on a
name.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
235
Out of the Box
Motorola
CCHEC130
CAD Call
Handling /
Event Create
Involved Person Info If the minimum required fields contain enough
data for state and federal queries, then the
system The system shall initiate queries to
local, state and federal databases.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
236
Out of the Box
Motorola
CCHEC131
CAD Call
Handling /
Event Create
Involved Person Info The system shall return all responses from
local, state, and federal databases to the data
entry originator.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
237
Out of the Box
Motorola
CCHEC132
CAD Call
Handling /
Event Create
Involved Person Info The system shall bring positive responses (e.g.
possible “hits”) that require a review by the
originator to the attention of the originator
through the use of audible and visual
indicators.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
238
Out of the Box
Motorola
CCHEC133
CAD Call
Handling /
Event Create
Involved Vehicle Info The system shall return all responses from
local, state and federal databases to the data
entry originator.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
239
Out of the Box
Motorola
CCHEC134
CAD Call
Handling /
Event Create
Involved Vehicle Info The system shall bring positive responses (e.g.
“hits”) that require a review by the originator
to the attention of the originator through the
use of audible and visual indicators.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
240
Out of the Box
Motorola
CCHEC135
CAD Call
Handling /
Event Create
Involved Vehicle Info The system shall be capable of collecting the
following information about each vehicle
associated with an event:
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
241
Out of the Box
Motorola
CCHEC136
CAD Call
Handling /
Event Create
Involved Vehicle Info License plate
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
242
Out of the Box
Motorola
CCHEC137
CAD Call
Handling /
Event Create
Involved Vehicle Info License plate state
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
243
Out of the Box
Motorola
CCHEC138
CAD Call
Handling /
Event Create
Involved Vehicle Info License plate type
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
244
Out of the Box
Motorola
CCHEC139
CAD Call
Handling /
Event Create
Involved Vehicle Info License plate year of expiration
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
245
Out of the Box
Motorola
CCHEC140
CAD Call
Handling /
Event Create
Involved Vehicle Info Primary vehicle color
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
246
Out of the Box
Motorola
CCHEC141
CAD Call
Handling /
Event Create
Involved Vehicle Info Vehicle Identification Number (VIN)
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
247
Out of the Box
Motorola
CCHEC142
CAD Call
Handling /
Event Create
Involved Vehicle Info Vehicle make
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
248
Out of the Box
Motorola
CCHEC143
CAD Call
Handling /
Event Create
Involved Vehicle Info Vehicle model
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
249
Out of the Box
Motorola
CCHEC144
CAD Call
Handling /
Event Create
Involved Vehicle Info Vehicle year
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
250
Out of the Box
Motorola
CCHEC145
CAD Call
Handling /
Event Create
Involved Vehicle Info Secondary vehicle color
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
251
Out of the Box
Page 12of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CCHEC146
CAD Call
Handling /
Event Create
Involved Vehicle Info Remarks
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
252
Out of the Box
Motorola
CCHEC147
CAD Call
Handling /
Event Create
Involved Vehicle Info The system shall initiate an automatic query to
local, state and federal databases, upon entry
of information about a vehicle associated with
an event, using the following guidelines at a
minimum:
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
253
Out of the Box
Motorola
CCHEC148
CAD Call
Handling /
Event Create
Involved Vehicle Info License plate number and license plate state
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
254
Out of the Box
Motorola
CCHEC149
CAD Call
Handling /
Event Create
Involved Vehicle Info VIN and vehicle make
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
255
Out of the Box
Motorola
CCHEC150
CAD Call
Handling /
Event Create
Involved Vehicle Info The system shall initiate a cascaded query,
upon receipt of a response from the DMV
containing the name of the registered owner of
the vehicle, to local, state and federal
databases, to check the wanted status, driver’s
license status, and other statuses of interest
about the registered owner.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
256
Out of the Box
Motorola
CCHEC151
CAD Call
Handling /
Event Create
Location Hazards
and Previous History
The system shall have the capability to retrieve
information about a premises and the
surrounding/adjacent area as an automatic
function during the creation of a CFS.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
257
Out of the Box
Motorola
CCHEC152
CAD Call
Handling /
Event Create
Location Hazards
and Previous History
The system shall have the capability to retrieve
information about a premises and the
surrounding/adjacent area as an ad-hoc query.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
258
Out of the Box
Motorola
CCHEC153
CAD Call
Handling /
Event Create
Location Hazards
and Previous History
The system shall display historical incident
information based on a configurable date range
pre-set by the systems administrator, and
according to local SOP.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
259
Out of the Box
Motorola
CCHEC154
CAD Call
Handling /
Event Create
Location Hazards
and Previous History
The system shall display historical incident
information based on a configurable geo-area
range pre-set by the systems administrator, and
according to local SOP.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
260
Out of the Box
Motorola
CCHEC155
CAD Call
Handling /
Event Create
Location Hazards
and Previous History
The system shall display historical incident
information based on a configurable date range
pre-set AND geo-area range pre-set by the
systems administrator, and according to local
SOP.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
261
Out of the Box
Motorola
CCHEC156
CAD Call
Handling /
Event Create
Location Hazards
and Previous History
The system shall be capable of storing
information of interest to responders including,
but not limited to:
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
262
Out of the Box
Motorola
CCHEC157
CAD Call
Handling /
Event Create
Location Hazards
and Previous History
Hazardous materials stored at the location
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
263
Out of the Box
Motorola
CCHEC158
CAD Call
Handling /
Event Create
Location Hazards
and Previous History
Firearms kept at the location
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
264
Out of the Box
Motorola
CCHEC159
CAD Call
Handling /
Event Create
Location Hazards
and Previous History
Information specific to individuals at the
location, including, but not limited to:
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
265
Out of the Box
Motorola
CCHEC160
CAD Call
Handling /
Event Create
Location Hazards
and Previous History
Warrants on file
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
266
Out of the Box
Motorola
CCHEC161
CAD Call
Handling /
Event Create
Location Hazards
and Previous History
Serious medical information
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
267
Out of the Box
Motorola
CCHEC162
CAD Call
Handling /
Event Create
Location Hazards
and Previous History
Impairments
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
268
Out of the Box
Motorola
CCHEC163
CAD Call
Handling /
Event Create
Location Hazards
and Previous History
Potential dangers to first responders
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
269
Out of the Box
Motorola
CCHEC164
CAD Call
Handling /
Event Create
Location Hazards
and Previous History
Information specific to the address, including,
but not limited to:
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
270
Out of the Box
Motorola
CCHEC165
CAD Call
Handling /
Event Create
Location Hazards
and Previous History
Entry codes
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
271
Out of the Box
Motorola
CCHEC166
CAD Call
Handling /
Event Create
Location Hazards
and Previous History
Knox or Lock-Box information (Sun City
Residents)
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
272
Out of the Box
Motorola
CCHEC167
CAD Call
Handling /
Event Create
Location Hazards
and Previous History
The system shall enable all required data for
direct input, to be uploaded, or to be loaded via
a live interface from RMS(s).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
273
Out of the Box
Page 13of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CCHEC168
CAD Call
Handling /
Event Create
CAD Event Creation
The system shall support the creation of a CFS
(Calls for Service) event with a bare minimum
amount of information to trigger the dispatch
of resources when the matter is urgent. This
includes the location of the event and the event
type.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
274
Out of the Box
Motorola
CCHEC169
CAD Call
Handling /
Event Create
CAD Event Creation
It must be possible to update CFS (Calls for
Service) event as additional information is
gathered from the reporting party.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
275
Out of the Box
Motorola
CCHEC170
CAD Call
Handling /
Event Create
CAD Event Creation
The system shall support the creation of new
CFS (Calls for Service) events—in
communications centers where separate call
takers and radio dispatchers are employed—by
either call takers or dispatchers depending on
the source of the event information.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
276
Out of the Box
Motorola
CCHEC171
CAD Call
Handling /
Event Create
CAD Event Creation
The system shall auto-create a CAD event for
the Automated Secure Alarm Protocol (ASAP)
standard if applicable.
Optional
CAD
X
PremierOne complies with the functionality as described in the requirement.
277
Out of the Box
Motorola
CCHEC172
CAD Call
Handling /
Event Create
CAD Event Creation
The system shall be able to create in CAD, an
"Advised" event that allows the dispatcher to
create a CFS for informational purposes only,
that does not require unit assignment or
require entry of a disposition.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
278
Out of the Box
Motorola
CCHEC173
CAD Call
Handling /
Event Create
CAD Event Creation
The system shall spawn a copy of the CFS (Calls
for Service) event—in agencies where multiple
agencies and/or services are dispatched, or
when an interface to another CAD system
exists—for the additional agencies with a
unique incident/event number for each;
however, all copies of the CFS event The system
shall be linked teach other so CAD users can
ascertain that they are a single CAD event.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
279
Out of the Box
Motorola
CCHEC174
CAD Call
Handling /
Event Create
Determining
Response Agency
and Service Area
The system shall store all service agency and
response area assignments in CFS events and
the system’s audit log file.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
280
Out of the Box
Motorola
CCHEC175
CAD Call
Handling /
Event Create
Determining
Response Agency
and Service Area
The system shall validate the location of new a
CAD event against the system’s geofile to verify
the location is within the service area handled
by the PSAP.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
281
Out of the Box
Motorola
CCHEC176
CAD Call
Handling /
Event Create
Determining
Response Agency
and Service Area
The system shall identify the new CAD event’s
location and nature code, and use the system’s
geofile to identify the appropriate service
agencies that need to handle the event.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
282
Out of the Box
Motorola
CCHEC177
CAD Call
Handling /
Event Create
Determining
Response Agency
and Service Area
The system shall identify the appropriate
service agencies to handle a CAD event, and use
the system’s geofile to determine the
appropriate response area(s) within each
agency’s service area.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
283
Out of the Box
Motorola
CCHEC178
CAD Call
Handling /
Event Create
Determining
Response Agency
and Service Area
The system shall provide a method for CAD
users to manually enter/assign the appropriate
service agencies and response areas to CAD
events if the CAD event’s location cannot be
validated against the system’s geofile or if the
validation process results in the assignment of
an improper service agency or response area.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
284
Out of the Box
Motorola
CCHEC179
CAD Call
Handling /
Event Create
Determining
Response Agency
and Service Area
The system shall use the service agency and
response to notify the appropriate dispatchers
that they must process a CAD event.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
285
Out of the Box
Motorola
CCHEC180
CAD Call
Handling /
Event Create
Alarm Processing
The system shall provide a feature where the
location of an alarm can be retrieved by the
number displayed on the enunciator panel, if
the PSAP monitors alarm enunciator panels.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
286
Out of the Box
Motorola
CCHEC181
CAD Call
Handling /
Event Create
Alarm Processing
The system shall adhere to the APCO/CSAA
2.101.1-2008 External Alarm Interface
Exchange American National Standard (see
below).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
287
Out of the Box
Motorola
CCHEC182
CAD Call
Handling /
Event Create
Alarm Processing
The system shall receive alarm notifications and
updates related to the alarm notification from
alarm monitoring companies.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
288
Out of the Box
Motorola
CCHEC183
CAD Call
Handling /
Event Create
Alarm Processing
The system shall utilize the alarm notification
data to create a CFS event without call taker
involvement if the address is valid and
minimum required fields have been provided.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
289
Out of the Box
Motorola
CCHEC184
CAD Call
Handling /
Event Create
Alarm Processing
The system shall spawn a copy of the CFS event
to other agencies, if applicable.
Optional
CAD
X
PremierOne complies with the functionality as described in the requirement.
290
Out of the Box
Page 14of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CCHEC185
CAD Call
Handling /
Event Create
Alarm Processing
The system shall process updates from the
alarm company as an update to the CFS and
shown to the telecommunicator responsible for
dispatch operations with an audible and visual
indication that a new update has been
received.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
291
Out of the Box
Motorola
CCHEC186
CAD Call
Handling /
Event Create
Alarm Processing
The system shall send the appropriate response
messages teach message received from the
alarm company and enable system users to
send update messages to the alarm company
operator when additional information is
required.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
292
Out of the Box
Motorola
CCHEC187
CAD Call
Handling /
Event Create
Alarm Processing
The system shall send an automatic update
message to the alarm company during the
progression of the event—when the primary
agency has been dispatched, when the primary
agency has arrived on scene, and when the CFS
has been closed, including any disposition
information reported by the primary agency
that responded.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
293
Out of the Box
Motorola
CCHEC188
CAD Call
Handling /
Event Create
CAD Event Routing
The system shall examine the location, event
type and response plans (when dedicated
dispatch positions are in operation) to route
the CFS event tone or more dispatch positions
as the CFS event entry is being performed by a
call taker.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
294
Out of the Box
Motorola
CCHEC189
CAD Call
Handling /
Event Create
Ability to Route to a
"Decision
Dispatcher"
The system shall be capable of routing a CFS to
a decision dispatch position that will dispatch
resources.
Optional
CAD
X
PremierOne complies with the functionality as described in the requirement.
295
Out of the Box
Motorola
CCHEC190
CAD Call
Handling /
Event Create
Ability to Route to a
"Decision
Dispatcher"
The system shall route the event (once the
decision dispatcher has dispatched the event to
the appropriate resources) to another
dispatcher that takes responsibility for the
event from that point forward.
Optional
CAD
X
PremierOne complies with the functionality as described in the requirement.
296
Out of the Box
Motorola
CCHEC191
CAD Call
Handling /
Event Create
Ability to Route to a
"Decision
Dispatcher"
The system shall be able to route CAD events to
the appropriate decision dispatcher (when
multiple “decision dispatchers” exist) based on
parameters configured by the system
administrator.
Optional
CAD
X
PremierOne complies with the functionality as described in the requirement.
297
Out of the Box
Motorola
CCHEC192
CAD Call
Handling /
Event Create
Ability to Route to a
"Decision
Dispatcher"
The system shall be able to route to the
appropriate radio dispatcher (when multiple
radio dispatchers exist to handle the remainder
of the event) based on the actions by the
decision dispatcher and/or predicated by event
type and location.
Optional
CAD
X
PremierOne complies with the functionality as described in the requirement.
298
Out of the Box
Motorola
DSO001
Dispatch
Support Ops
Response Plans
The system shall allow for dynamic and
fixed/static response plans.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
299
Out of the Box
Motorola
DSO002
Dispatch
Support Ops
Response Plans
The system shall allow for unlimited alarm
levels.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
300
Out of the Box
Motorola
DSO003
Dispatch
Support Ops
Response Plans
The system shall allow for the use of primary
and secondary capabilities.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
301
Out of the Box
Motorola
DSO004
Dispatch
Support Ops
Response Plans
The system shall allow for assignment to be by
resource type, capability and equipment (e.g.
thermal imager).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
302
Out of the Box
Motorola
DSO005
Dispatch
Support Ops
Response Plans
The system shall allow for the use of personnel
capabilities (e.g. personnel with Spanish
speaking ability).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
303
Out of the Box
Motorola
DSO006
Dispatch
Support Ops
Response Plans
The system shall allow for the use of resource
groups made up of individual units [e.g. a
Hazmat (hazardous material) group made up of
several units and dispatched as a single
“Hazmat team” (i.e. single unit)].
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
304
Out of the Box
Motorola
DSO007
Dispatch
Support Ops
Response Plans
The system shall allow for the use of premises-
based or address-based response plans.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
305
Out of the Box
Motorola
DSO008
Dispatch
Support Ops
Response Plans
The system shall allow for the use of AVL
systems for selecting units.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
306
Out of the Box
Motorola
DSO009
Dispatch
Support Ops
Response Plans
The system shall support multiple agency
response plans. (MCSO & PROBATION)
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
307
Out of the Box
Motorola
DSO010
Dispatch
Support Ops
Response Plans
The system shall allow for unit assignment
based on time or distance to the incident.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
308
Out of the Box
Motorola
DSO011
Dispatch
Support Ops
Response Plans
The system shall allow for adjustable plans that
are based on time of day or day of week.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
309
Out of the Box
Motorola
DSO012
Dispatch
Support Ops
Adjustable Dispatch
Levels
The system shall allow for adjustable dispatch
levels.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
310
Out of the Box
Motorola
DSO013
Dispatch
Support Ops
Adjustable Dispatch
Levels
The system shall allow for an unlimited number
of dispatch levels.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
311
Out of the Box
Motorola
DSO014
Dispatch
Support Ops
Adjustable Dispatch
Levels
The system shall allow for a user-defined
naming convention for the dispatch levels.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
312
Out of the Box
Page 15of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
DSO015
Dispatch
Support Ops
Adjustable Dispatch
Levels
The system shall enable adjustable dispatch
levels to be individually activated (e.g. a
998,999 response plan would change to Level 1
or all plans could change to a defined level).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
313
Out of the Box
Motorola
DSO016
Dispatch
Support Ops
Adjustable Dispatch
Levels
The system shall have an easily viewable
method to review current dispatch levels.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
314
Out of the Box
Motorola
DSO017
Dispatch
Support Ops
Adjustable Dispatch
Levels
The system shall alert the dispatcher when the
required number or type of units are not
dispatched (e.g. one police unit to a domestic
call instead of two, or two fire engines to a
commercial fire instead of four).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
315
Out of the Box
Motorola
DSO018
Dispatch
Support Ops
Additional Attributes The system shall provide a means to assign
multiple attributes to units.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
316
Out of the Box
Motorola
DSO019
Dispatch
Support Ops
Additional Attributes The system shall provide a means to assign
multiple attributes to personnel.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
317
Out of the Box
Motorola
DSO020
Dispatch
Support Ops
Additional Attributes The system shall provide a means to search for
units or personnel attributes on the fly.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
318
Out of the Box
Motorola
DSO021
Dispatch
Support Ops
Additional Attributes The system shall provide a means to assign
resources to multiple units (i.e. SWAT, Drones,
K9 etc).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
319
Out of the Box
Motorola
DSO022
Dispatch
Support Ops
Special Dispatch
Areas
The system shall define special dispatch area
types and assign each a unique identifier.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
320
Out of the Box
Motorola
DSO023
Dispatch
Support Ops
Special Dispatch
Areas
The system shall assign a special dispatch area
type to CAD geofile addresses, intersections,
and blocks for each service agency (e.g. Court
Jursdiction, Towing companies etc).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
321
Out of the Box
Motorola
DSO024
Dispatch
Support Ops
Special Dispatch
Areas
The system shall specify a non-standard
response for a location identified with a special
dispatch area type.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
322
Out of the Box
Motorola
DSO025
Dispatch
Support Ops
Special Dispatch
Areas
The system shall define non-standard responses
as being applicable only during certain days of
the week and/or times of the day (i.e. window
for utilization).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
323
Out of the Box
Motorola
DSO026
Dispatch
Support Ops
Special Dispatch
Areas
The system shall provide the capability that if
one or more windows are defined but none of
them are applicable, then the standard
response is employed.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
324
Out of the Box
Motorola
DSO027
Dispatch
Support Ops
Radio Channel
Designations
The system shall have a table of radio
channels/talk groups.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
325
Out of the Box
Motorola
DSO028
Dispatch
Support Ops
Radio Channel
Designations
The system shall allow each radio channel or
talk group to be used for tactical purposes to be
flagged as such in the CAD system.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
326
Out of the Box
Motorola
DSO029
Dispatch
Support Ops
Radio Channel
Designations
The system shall allow each radio channel or
talk group defined in the CAD system to have
an associated list of the agencies whose units
have those radio channels or talk groups on
their radios.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
327
Out of the Box
Motorola
DSO030
Dispatch
Support Ops
Radio Channel
Designations
The system shall allow the radio channels or
talk groups used for tactical purposes to be
ranked according to the order in which they are
assigned.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
328
Out of the Box
Motorola
DSO031
Dispatch
Support Ops
Radio Channel
Designations
The system shall track the maximum number of
concurrent incidents that may be specified for
each radio channel or talk group.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
329
Out of the Box
Motorola
DSO032
Dispatch
Support Ops
Radio Channel
Designations
The system shall include a flag indicating a
requirement for the automatic assignment of a
tac channel that can be set for each incident
type in the CAD system.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
330
Out of the Box
Motorola
DSO033
Dispatch
Support Ops
Radio Channel
Designations
The system shall assign a tactical radio channel
available to units upon the dispatch to an
incident requiring the automatic assignment of
a tac channel.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
331
Out of the Box
Motorola
DSO034
Dispatch
Support Ops
Radio Channel
Designations
The system shall allow the dispatcher to
manually flag or assign one or more tactical
radio channels or talk groups to an incident.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
332
Out of the Box
Motorola
DSO035
Dispatch
Support Ops
Radio Channel
Designations
The system shall track the release and
reassignment of radio channels/talk groups.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
333
Out of the Box
Motorola
DSO036
Dispatch
Support Ops
Radio Channel
Designations
The system shall release the tac channels/talk
groups assigned to an incident when that
incident has been cleared and make the tac
channels/talk groups available for other
incidents.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
334
Out of the Box
Page 16of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
DSO037
Dispatch
Support Ops
Radio Channel
Designations
The system shall be able to, upon assignment of
a tactical radio channel or talk group to an
incident, direct the radio system to have the
radios associated with units assigned to the
incident to be automatically switched to that
tac channel/talk group (if the radio system
provides this capability).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
335
Out of the Box
Motorola
DSO038
Dispatch
Support Ops
Radio Channel
Designations
The system shall be able to, upon clearing an
incident of which a tac channel/talk group has
been assigned and the release of the channel or
talk group has occurred, direct the radio system
to have the radios associated with units
assigned to the incident to automatically revert
to their previous channel or talk group
selection.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
336
Out of the Box
Motorola
DSO039
Dispatch
Support Ops
Radio Channel
Designations
The system shall be able to record which radio
channels were patched together for an incident
including start and end times.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
337
Out of the Box
Motorola
DSO040
Dispatch
Support Ops
BOLO/Attempt to
Locate
The system shall support creation and
distribution of any BOLO entered into the
system.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
338
Out of the Box
Motorola
DSO041
Dispatch
Support Ops
BOLO/Attempt to
Locate
The system shall provide a BOLO structure to
include all necessary information such as the
nature of the BOLO, priority, date, range of
effectiveness, subject and/or vehicle
information, hazard information, and contact
information.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
339
Out of the Box
Motorola
DSO042
Dispatch
Support Ops
BOLO/Attempt to
Locate
The system shall allow narrative fields for
additional information.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
340
Out of the Box
Motorola
DSO043
Dispatch
Support Ops
BOLO/Attempt to
Locate
The system shall provide the means for BOLO
information to be easily searchable, printable,
and have the ability to automatically populate
on an incident sheet referencing any particular
name, address, or vehicle information.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
341
Out of the Box
Motorola
DSO044
Dispatch
Support Ops
BOLO/Attempt to
Locate
The system shall flag the field (automatically)
with configurable visual and audible alerts.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
342
Out of the Box
Motorola
DSO045
Dispatch
Support Ops
BOLO/Attempt to
Locate
The system shall support a workflow record for
initial BOLO creation and any additional edits.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
343
Out of the Box
Motorola
DSO046
Dispatch
Support Ops
Dispatch Units
The system shall have the optional ability to
assign one incident number to each unit
responding to the incident.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
344
Out of the Box
Motorola
DSO047
Dispatch
Support Ops
Dispatch Units
The system shall assign an incident number to
each agency responding to the incident.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
345
Out of the Box
Motorola
DSO048
Dispatch
Support Ops
Dispatch Units
The system shall capture every time stamp
associated with each unit’s response and status
change related to the incident.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
346
Out of the Box
Motorola
DSO049
Dispatch
Support Ops
Dispatch Units
The system shall capture all status changes and
their times for statistical and research purposes
(e.g. out of service versus in service to calculate
“lost unit hours”).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
347
Out of the Box
Motorola
DSO050
Dispatch
Support Ops
Resource Alerting
The system shall generate (automatically)
information appropriate for use with email
and/or SMS sent to a mobile device when units
are dispatched or on demand by a dispatcher.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
348
Out of the Box
Motorola
DSO051
Dispatch
Support Ops
Resource Alerting
The system shall interface with tone encoder
systems. (Palo Verde Nuclear Plant Alarms)
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
349
Out of the Box
Motorola
DSO052
Dispatch
Support Ops
Resource Alerting
The system shall support sending SMS
messages either directly via cellular modem or
using a common carrier’s SMTP interface.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
350
Out of the Box
Motorola
RUM001
Resources /
Unit
Management
Staffed vs. Unstaffed
Units
The system shall provide the ability to
dynamically document that a unit is staffed or
unstaffed before or after it is assigned to an
incident. (Lake Patrol)
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
351
Out of the Box
Motorola
RUM002
Resources /
Unit
Management
Cross-Staffing
The system shall account for the qualifications
of personnel—such as K9, AR-15 certification,
Another Language and rescue certification—to
establish the best possible resource allocation
based on prioritized needs for the response.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
352
Out of the Box
Motorola
RUM003
Resources /
Unit
Management
Additional Unit
Status
The system shall allow for multiple transports
by the same unit on the same incident (e.g. a
mass casualty incident).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
353
Out of the Box
Motorola
RUM004
Resources /
Unit
Management
Additional Unit
Status
The system shall include the various statuses
needed for unit readiness.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
354
Out of the Box
Motorola
RUM005
Resources /
Unit
Management
Task Force
Assignment
The system shall allow the dispatcher to group
units into a task force or strike team (i.e. virtual
unit).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
355
Out of the Box
Page 17of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RUM006
Resources /
Unit
Management
Task Force
Assignment
The system shall track (individually) all
resources in the system’s database, and The
system shall also make a record that the
resources were part of a virtual unit so the
virtual unit response data can be easily
retrieved.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
356
Out of the Box
Motorola
RUM007
Resources /
Unit
Management
Rosters
The system shall provide the capability to
create rosters (i.e. assign personnel to a vehicle
or position to facilitate on/off duty
transactions).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
357
Out of the Box
Motorola
RUM008
Resources /
Unit
Management
Rosters
The system shall allow the dispatcher to adjust
the rosters and/or assignments (i.e. on-the-fly,
during shifts, and above normal complements).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
358
Out of the Box
Motorola
RUM009
Resources /
Unit
Management
Rosters
The system shall warn the dispatcher if a
resource complement is below minimum.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
359
Out of the Box
Motorola
RUM010
Resources /
Unit
Management
Rosters
The system shall contain a 2-way, real-time
interface to auto populate roster information in
CAD.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
360
Out of the Box
Motorola
RUM011
Resources /
Unit
Management
Scheduling
The system shall provide scheduling capabilities
to include pre-assignment of personnel to
shifts, beats.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
361
Out of the Box
Motorola
RUM012
Resources /
Unit
Management
Scheduling
The system shall allow the dispatcher, with
proper permissions, to make adjustments to
scheduling on-the-fly and/or during shifts.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
362
Out of the Box
Motorola
RUM013
Resources /
Unit
Management
Mileage Tracking
The system shall capture beginning and ending
mileage for individual transports.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
363
Out of the Box
Motorola
RUM014
Resources /
Unit
Management
Mileage Tracking
The system shall provide a method of
integration with an AVL system for increased
accuracy and efficiency.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
364
Out of the Box
Motorola
RUM015
Resources /
Unit
Management
Mileage Tracking
The system shall include the use of intuitive
interfaces that facilitate mandatory entry based
on given incident types or processes.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
365
Out of the Box
Motorola
RUM016
Resources /
Unit
Management
Mileage Tracking
The system shall provide the ability for an
authorized user to manually override an entry
by a dispatcher or supervisor.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
366
Out of the Box
Motorola
RUM017
Resources /
Unit
Management
Mileage Tracking
The system shall record the overridden
information in an audit log.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
367
Out of the Box
Motorola
RUM018
Resources /
Unit
Management
Unit Disposition
The system shall enable the CAD administrator
to define a list of available unit dispositions.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
368
Out of the Box
Motorola
RUM019
Resources /
Unit
Management
Unit Disposition
The system shall make the primary unit of the
call the first unit on-scene or when a proper
closing dispo code is given.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
369
Out of the Box
Motorola
RUM020
Resources /
Unit
Management
Unit Disposition
The system shall not allow calls with one unit
assigned or the last unit assigned to enter a
improper closing disposition, unless closing
disposition was already given by another unit
assigned on the call.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
370
Out of the Box
Motorola
RUM021
Resources /
Unit
Management
Unit Disposition
The system shall require a disposition based on
call type and jurisdiction.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
371
Out of the Box
Motorola
RUM022
Resources /
Unit
Management
Unit Disposition
The system shall enable assisting units to report
one or more dispositions when agency policy
requires a disposition from each unit assigned
to a CFS.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
372
Out of the Box
Motorola
RUM023
Resources /
Unit
Management
Unit Disposition
The system shall facilitate the recording of
dispositions by the dispatcher or the field unit if
MDC-equipped.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
373
Out of the Box
Motorola
RUM024
Resources /
Unit
Management
Unit Disposition
The system shall include a multiplication factor
for each disposition when multiple instances of
the same disposition apply (e.g. 10 traffic
summons written could be recorded using a
single disposition of “traffic summons issued,”
times 10).
Mandatory
CAD
X
PremierOne does not have this functionality.
MCSO team stated this is not required to be met.
374
Cannot Meet
Motorola
RUM025
Resources /
Unit
Management
Unit Disposition
The CAD system The system shall NOT require a
disposition if agency policy does not require the
use of dispositions.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
375
Out of the Box
Motorola
RUM026
Resources /
Unit
Management
Geo-Fencing
The system shall provide geo-fence creation
tools that allow the use of polygons, circles,
ellipses, and rectangles.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
376
Out of the Box
Motorola
RUM027
Resources /
Unit
Management
Geo-Fencing
The system shall display details about a
resource to aid in identification, location and
purpose.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
377
Out of the Box
Motorola
RUM028
Resources /
Unit
Management
Geo-Fencing
The system shall facilitate the creation of
multiple, coexisting, overlapping geo-fences.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
378
Out of the Box
Motorola
RUM029
Resources /
Unit
Management
Geo-Fencing
The system shall support unique geo-fence
names and each geo-fence The system shall be
visually distinct.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
379
Out of the Box
Motorola
RUM030
Resources /
Unit
Management
Geo-Fencing
The system shall generate an alert whenever a
vehicle or resource enters and/or exits a geo-
fence.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
380
Out of the Box
Page 18of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RUM031
Resources /
Unit
Management
Geo-Fencing
The system shall include alerts that consist of:
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
381
Out of the Box
Motorola
RUM032
Resources /
Unit
Management
Geo-Fencing
Unique visual and audible identification
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
382
Out of the Box
Motorola
RUM033
Resources /
Unit
Management
Geo-Fencing
Resource identification
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
383
Out of the Box
Motorola
RUM034
Resources /
Unit
Management
Geo-Fencing
Geo-fence Identification
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
384
Out of the Box
Motorola
RUM035
Resources /
Unit
Management
Geo-Fencing
Current resource position
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
385
Out of the Box
Motorola
RUM036
Resources /
Unit
Management
Geo-Fencing
Timestamps of entry and exit of geo-fence
areas
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
386
Out of the Box
Motorola
RUM037
Resources /
Unit
Management
Geo-Fencing
Ability to clear alerts and history from view
while maintaining historic records as needed
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
387
Out of the Box
Motorola
RUM038
Resources /
Unit
Management
Geo-Fencing
The system shall be able to alert personnel
though technologies such as text messaging or
email.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
388
Out of the Box
Motorola
RUM039
Resources /
Unit
Management
Geo-Fencing
The system shall provide the ability to create,
manage and record geo-fence areas to track
the entry and/or exit of GIS based resources.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
389
Out of the Box
Motorola
RUM040
Resources /
Unit
Management
Geo-Fencing
The system shall provide informative and
manageable alerts to appropriate personnel
through visual and audible representation.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
390
Out of the Box
Motorola
RUM041
Resources /
Unit
Management
Vehicle/Unit Change The system shall account for the number of
personnel currently staffed on the unit. (FTO
Vehicle, SWAT etc.)
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
391
Out of the Box
Motorola
RUM042
Resources /
Unit
Management
Vehicle/Unit Change The system shall allow system supervisors and
other authorized users the ability to modify
vehicle and resource capabilities, as required,
without adversely impacting the system (i.e.
without having to shut the system down).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
392
Out of the Box
Motorola
RUM043
Resources /
Unit
Management
Vehicle/Unit Change The system shall allow easy modifications to
unit capabilities to accommodate frequent
changes throughout the day.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
393
Out of the Box
Motorola
RUM044
Resources /
Unit
Management
Vehicle/Unit Change The system shall track units having multiple
units with multiple capabilities, and attributes
The system shall be reflected as multiple types
(e.g. a K9, AR-15, etc.).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
394
Out of the Box
Motorola
RUM045
Resources /
Unit
Management
Vehicle/Unit Change The system shall recommend resources based
on the appropriate type.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
395
Out of the Box
Motorola
RUM046
Resources /
Unit
Management
Vehicle/Unit Change The system shall allow the dynamic entry of
personnel staffing specific units.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
396
Out of the Box
Motorola
RUM047
Resources /
Unit
Management
Vehicle/Unit Change The system shall allow the staffing module to
be accessed from the field by authorized users
to dynamically reflect changing assignments.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
397
Out of the Box
Motorola
RUM048
Resources /
Unit
Management
Vehicle/Unit Change The system shall allow for tracking vehicle ID in
addition to unit radio call sign (e.g. a given
vehicle may be referred to as “Unit 1” one day
and a different vehicle the next day.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
398
Out of the Box
Motorola
RUM049
Resources /
Unit
Management
Driving
Directions/Routing
The system shall present the destination
address visually for validation and acceptance.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
399
Out of the Box
Motorola
RUM050
Resources /
Unit
Management
Driving
Directions/Routing
The system shall provide a route that considers
speed limits, traffic lights, stop signs, and other
traffic control variables.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
400
Out of the Box
Motorola
RUM051
Resources /
Unit
Management
Driving
Directions/Routing
The system shall provide a visual map that
presents the entire route.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
401
Out of the Box
Motorola
RUM052
Resources /
Unit
Management
Driving
Directions/Routing
The system shall provide a visual map that
centers the unit and presents a configurable
radius around the unit (i.e. feet, miles, meters),
and provides turn-by-turn navigation.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
402
Out of the Box
Motorola
RUM053
Resources /
Unit
Management
Driving
Directions/Routing
The system shall provide a directions list from
unit current location to destination.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
403
Out of the Box
Motorola
RUM054
Resources /
Unit
Management
Driving
Directions/Routing
The system shall allow authorized field units to
create and clear impedances, which may be
used for directing other units.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
404
Out of the Box
Motorola
RUM055
Resources /
Unit
Management
Driving
Directions/Routing
The system shall account for one-way roads,
highway overpasses, and other considerations
that impact safety.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
405
Out of the Box
Page 19of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RUM056
Resources /
Unit
Management
Driving
Directions/Routing
The system shall include traffic weights that are
considerate of time-of-day, day-of-week, and
day-of-year to account for rush hour and
holiday congestion.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
406
Out of the Box
Motorola
RUM057
Resources /
Unit
Management
Driving
Directions/Routing
The system shall provide configurable forms
that allow resizing, on-off, and night/day
modes.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
407
Out of the Box
Motorola
RUM058
Resources /
Unit
Management
Driving
Directions/Routing
The system shall provide a manual entry
interface for non-CAD driven use.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
408
Out of the Box
Motorola
RUM059
Resources /
Unit
Management
Driving
Directions/Routing
The system shall prevent audible alerts from
interfering from other system notifications that
may impact unit safety.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
409
Out of the Box
Motorola
CIEM001
Call/Incident/E
vent
Management
Display of Incident/
Event Data
The system shall display CFS event data on the
CAD monitor after being selected by the
dispatcher. All CFS event data The system shall
be accessible to the dispatcher.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
410
Out of the Box
Motorola
CIEM002
Call/Incident/E
vent
Management
Display of Incident/
Event Data
The system shall enable Windows tabs to be
used to allow the dispatcher to select
supplemental history about the incident (e.g.
premises history, Location of interest, past
event history, hazards, persons of interest)
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
411
Out of the Box
Motorola
CIEM003
Call/Incident/E
vent
Management
Display of Incident/
Event Data
The system shall display (automatically)
updates to the CFS event for the dispatcher.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
412
Out of the Box
Motorola
CIEM004
Call/Incident/E
vent
Management
Display of Incident/
Event Data
The system shall provide updated information
that is easily discernible from the previously
read data (e.g. newest information on the top,
different font/color text).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
413
Out of the Box
Motorola
CIEM005
Call/Incident/E
vent
Management
Display of Incident/
Event Data
The system shall present an audible and/or
visual indication to the dispatcher when a CFS
event is updated by another source such as a
call taker, another dispatcher, or a field unit.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
414
Out of the Box
Motorola
CIEM006
Call/Incident/E
vent
Management
Display of Incident/
Event Data
The system shall provide, upon receipt of an
update, a method of ease, such as an ‘Update’
button, for the dispatcher to retrieve the CFS
event that has been updated.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
415
Out of the Box
Motorola
CIEM007
Call/Incident/E
vent
Management
Display of Incident/
Event Data
The system shall remove CFS events as they are
closed by the dispatcher from the CFS event
display, without additional interaction from the
dispatcher.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
416
Out of the Box
Motorola
CIEM008
Call/Incident/E
vent
Management
Update Incident
Status
The system shall provide the capability to
record supplemental information updates in
the CFS event as it is received from callers, field
resources and other sources.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
417
Out of the Box
Motorola
CIEM009
Call/Incident/E
vent
Management
Update Incident
Status
The system shall retain a copy of any
information updated prior to the update for
audit purposes.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
418
Out of the Box
Motorola
CIEM010
Call/Incident/E
vent
Management
Update Incident
Status
The system shall provide a method to update
the actual incident type versus the reported
incident type.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
419
Out of the Box
Motorola
CIEM011
Call/Incident/E
vent
Management
Dispatch Decision/
Automation
The system shall recommend resources, when
the resource requirement is changed, based
upon agency defined procedures, workload
balancing, unit capability, and proximity of the
resources.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
420
Out of the Box
Motorola
CIEM012
Call/Incident/E
vent
Management
Update Assigned
Resources
The system shall detect when a reduction in
dispatched resources is required.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
421
Out of the Box
Motorola
CIEM013
Call/Incident/E
vent
Management
Update Assigned
Resources
The system shall recommend readjusted
resources that meet the requirements of the
incident.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
422
Out of the Box
Motorola
CIEM014
Call/Incident/E
vent
Management
Update Assigned
Resources
The system shall record the modifications to
the CFS event when changed by the dispatcher.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
423
Out of the Box
Motorola
CIEM015
Call/Incident/E
vent
Management
Update Assigned
Resources
The system shall record any changes to
assigned resources as an update to the CFS
event.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
424
Out of the Box
Motorola
CIEM016
Call/Incident/E
vent
Management
Update Assigned
Resources
The system shall provide the capability to
recommend additional resources based on
response plans and/or local policies.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
425
Out of the Box
Motorola
CIEM017
Call/Incident/E
vent
Management
Update
Supplemental
Resources Tracking
The system shall allow the ability to divide the
response area into multiple zones, based on
user-defined criteria, to ensure a quick
response to the request.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
426
Out of the Box
Motorola
CIEM018
Call/Incident/E
vent
Management
Update
Supplemental
Resources Tracking
The system shall make recommendations for
resources to prevent any one entity from being
favored.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
427
Out of the Box
Page 20of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CIEM019
Call/Incident/E
vent
Management
Update
Supplemental
Resources Tracking
The system shall allow cancellation of or by-
passing the recommendation, returning the
skipped company to be placed back in the
rotation either at the bottom or top of the
rotation, depending on the circumstances.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
428
Out of the Box
Motorola
CIEM020
Call/Incident/E
vent
Management
Update
Supplemental
Resources Tracking
The system shall provide the ability to skip a
suggested resource, capturing the reason for
the exception and placing the resource either
back at the top of the queue or at the bottom,
based on the reasoning.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
429
Out of the Box
Motorola
CIEM021
Call/Incident/E
vent
Management
Update
Supplemental
Resources Tracking
The system shall provide the ability to create
and maintain rotating and non-rotating service
provider information (i.e. towing companies).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
430
Out of the Box
Motorola
CIEM022
Call/Incident/E
vent
Management
Assign Units
The system shall allow the assignment of units
by using drag-and-drop and point-and-click pull-
down menus.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
431
Out of the Box
Motorola
CIEM023
Call/Incident/E
vent
Management
Assign Units
The system shall re-queue the CFS that has had
all units removed, but has not been handled.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
432
Out of the Box
Motorola
CIEM024
Call/Incident/E
vent
Management
Assign Units
The system shall recommend a unit that is
unavailable only if SOP permits units to be pre-
empted for a higher priority event.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
433
Out of the Box
Motorola
CIEM025
Call/Incident/E
vent
Management
Assign Units
The system shall provide the ability to assign
one or more units to an incident with a single
command.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
434
Out of the Box
Motorola
CIEM026
Call/Incident/E
vent
Management
Assign Units
The system shall provide the ability to
dynamically, and without user intervention,
change the unit recommendation if relevant
incident information changes (i.e. type,
location, priority).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
435
Out of the Box
Motorola
CIEM027
Call/Incident/E
vent
Management
Assign Units
The system shall provide the ability to notify
users that the unit recommendation has
changed.
Preferred
CAD
X
PremierOne complies with the functionality as described in the requirement.
436
Out of the Box
Motorola
CIEM028
Call/Incident/E
vent
Management
Assign Units
The system shall provide the ability to cancel a
unit from an assignment: If the cancelled unit is
the only unit assigned, then the CFS will be
returned to the pending event queue.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
437
Out of the Box
Motorola
CIEM029
Call/Incident/E
vent
Management
Assign Units
The system shall provide the ability to assign or
add multiple units to a CFS event with a single
command.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
438
Out of the Box
Motorola
CIEM030
Call/Incident/E
vent
Management
Assign Units
The system shall provide the ability to assign a
single unit to multiple CFS events.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
439
Out of the Box
Motorola
CIEM031
Call/Incident/E
vent
Management
Assign Units
The system shall provide the ability to hold a
CFS event for a specific unit.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
440
Out of the Box
Motorola
CIEM032
Call/Incident/E
vent
Management
Assign Units
The system shall allow the dispatcher to
override the system recommended units and
assign other units.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
441
Out of the Box
Motorola
CIEM033
Call/Incident/E
vent
Management
Assign Units
The system shall allow the dispatcher to assign
any valid field unit to an incident even if that
unit is not currently logged on to the system.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
442
Out of the Box
Motorola
CIEM034
Call/Incident/E
vent
Management
Assign Units
The system shall notify the dispatcher and
confirm that the correct unit has been assigned
if a unit assigned to an incident is not logged on
the system.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
443
Out of the Box
Motorola
CIEM035
Call/Incident/E
vent
Management
Update Incident
Data
The system shall log the following information
for all entries into the CFS event: date, time,
user ID (or note if action was system
generated), position (terminal) ID, action
performed, and any notes associated with
action.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
444
Out of the Box
Motorola
CIEM036
Call/Incident/E
vent
Management
Update Incident
Data
The system shall display additional CFS event
information to the dispatcher for action.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
445
Out of the Box
Motorola
CIEM037
Call/Incident/E
vent
Management
Update Incident
Data
The system shall allow, at any time, additional
incident information to be added to the CFS
event, both prior to and after closing the
incident.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
446
Out of the Box
Motorola
CIEM038
Call/Incident/E
vent
Management
Update Incident
Data
The system shall allow the user to display the
added comments in reverse chronological
order.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
447
Out of the Box
Motorola
CIEM039
Call/Incident/E
vent
Management
Update Incident
Data
The system shall provide the user the option of
specifying the CFS event to update by entering
the call sign of any assigned unit or by entering
the incident number.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
448
Out of the Box
Motorola
CIEM040
Call/Incident/E
vent
Management
Update Incident
Data
The system shall permit multiple users,
including MDC-equipped field resources, the
ability to simultaneously update information to
the CFS event.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
449
Out of the Box
Page 21of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CIEM041
Call/Incident/E
vent
Management
Update Incident
Data
The system shall provide controls when two or
more CAD users attempt to update the same
field in the CFS event
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
450
Out of the Box
Motorola
CIEM042
Call/Incident/E
vent
Management
Update Incident
Data
For example, in the event that User A is saving
modifications to a field, and that field has been
modified by another user since User A retrieved
the CFS event, the application The system shall
notify User A that the field that is being
modified has been changed since User A
retrieved the record and confirm that User A
wants tcontinue with the update.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
451
Out of the Box
Motorola
CIEM043
Call/Incident/E
vent
Management
Update Incident
Data
The system shall provide the ability for one or
more CAD users to simultaneously add incident
information to an active or closed CFS event.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
452
Out of the Box
Motorola
CIEM044
Call/Incident/E
vent
Management
Update Incident
Data
The system shall provide the ability to add
supplemental information to closed incidents
based on assigned user rights.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
453
Out of the Box
Motorola
CIEM045
Call/Incident/E
vent
Management
Update Incident
Data
The system shall notify the entering party that
the incident being updated has been closed.
This will allow the entering party to reopen the
incident for re-queuing to dispatch if necessary.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
454
Out of the Box
Motorola
CIEM046
Call/Incident/E
vent
Management
Update Incident
Data
The system shall provide the ability to update
the CFS event by specifying the incident/event
number or the call sign of assigned units.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
455
Out of the Box
Motorola
CIEM047
Call/Incident/E
vent
Management
Assign Case Number
to RMS
The system shall facilitate an interface to an
RMS to allow the transfer and tracking of
incident data.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
456
Out of the Box
Motorola
CIEM048
Call/Incident/E
vent
Management
Assign Case Number
to RMS
The system shall provide the ability to transfer
the incident data to the RMS at a set time
(incident closure) or at dispatcher discretion
based upon the field unit’s needs.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
457
Out of the Box
Motorola
CIEM049
Call/Incident/E
vent
Management
Assign Case Number
to RMS
The system shall coordinate the assignment of
RMS incident/case numbers through a jointly
used, shared list by the RMS and CAD system or
through a list maintained in the CAD system.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
458
Out of the Box
Motorola
CIEM050
Call/Incident/E
vent
Management
Assign Case Number
to RMS
The system shall provide the ability for the
dispatcher to retrieve the RMS incident number
at any point during the event or after the
incident has been closed.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
459
Out of the Box
Motorola
CIEM051
Call/Incident/E
vent
Management
Assign Case Number
to RMS
MCSO is familiar with a process that assigns an
event number to all activities entered into CAD.
Some of the activities result in departmental
reports being prepared. These reports use their
event numbers for identification. This process
can require additional event numbers when
more than one crime is being reported on
additional departmental reports. MCSO is
interested in hearing recommendations on how
best to identify its events and reports.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement. The process
described using an event number for the incident report and report number(s) for the associate
case reports is the recommended way to handle report number assignments.
460
Out of the Box
Motorola
CIEM052
Call/Incident/E
vent
Management
Assign Case Number
to RMS
The system should be able to provide the
capability of providing a "one to one" case
number and event number.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
461
Out of the Box
Motorola
CIEM053
Call/Incident/E
vent
Management
Assign Case Number
to RMS
These options should be configurable by the
system administrator.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
462
Out of the Box
Motorola
CIEM054
Call/Incident/E
vent
Management
Assign Case Number
to RMS
Field users should have the ability to retrieve
case and event information using their MDCs
without involving Communications.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
463
Out of the Box
Motorola
CIEM055
Call/Incident/E
vent
Management
Transfer Incident
Data to the Records
Management
System
The system shall provide the ability to
automatically transfer CAD system CFS event
data relating to an incident to an RMS for use
by the agency.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
464
Out of the Box
Motorola
CIEM056
Call/Incident/E
vent
Management
Transfer Incident
Data to the Records
Management
System
The system shall provide the ability to transfer
data prior to the normal chronological transfer
point to provide the public safety responders
with an RMS incident number when needed,
and if this method is required to retrieve an
RMS incident number.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
465
Out of the Box
Motorola
CIEM057
Call/Incident/E
vent
Management
Display Additional
Incident Data
The system shall notify the appropriate CAD
users via visual and/or audible indication when
information is added or changed to a CFS event.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
466
Out of the Box
Motorola
CIEM058
Call/Incident/E
vent
Management
Display Additional
Incident Data
The system shall provide a separate notification
for each entry made.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
467
Out of the Box
Page 22of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CIEM059
Call/Incident/E
vent
Management
Display Additional
Incident Data
The system shall provide the ability to visually
differentiate text notes in the CFS event added
by different operators for the same incident
(i.e. color and/or CAD user identification).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
468
Out of the Box
Motorola
CIEM060
Call/Incident/E
vent
Management
Display Additional
Incident Data
The system shall display additional CFS event
data with the newest information displayed
first.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
469
Out of the Box
Motorola
CIEM061
Call/Incident/E
vent
Management
Display Additional
Incident Data
The system shall display additional CFS event
data with the newest information displayed in
differently formatted text (e.g. color, font,
formatting, such as bold, italics).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
470
Out of the Box
Motorola
CIEM062
Call/Incident/E
vent
Management
Display Additional
Incident Data
The system shall provide the ability to view all
additional CFS event data at one time.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
471
Out of the Box
Motorola
CIEM063
Call/Incident/E
vent
Management
Display Additional
Incident Data
The system shall provide the ability to
automatically notify users monitoring or
displaying the CFS event that information has
changed.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
472
Out of the Box
Motorola
CIEM064
Call/Incident/E
vent
Management
Display Additional
Incident Data
The system shall provide the ability to
dynamically, and without user intervention,
display changes to a CFS event as they occur
based on assigned user rights.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
473
Out of the Box
Motorola
CIEM065
Call/Incident/E
vent
Management
Reopen Incident
The system shall ensure all changes to the CFS
event are time/date stamped.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
474
Out of the Box
Motorola
CIEM066
Call/Incident/E
vent
Management
Reopen Incident
The system shall notify the CAD user
attempting to add information to a closed CFS
event that the event is closed.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
475
Out of the Box
Motorola
CIEM067
Call/Incident/E
vent
Management
Reopen Incident
The system shall provide the ability to add
comments to a CFS event without reopening
the original CFS event.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
476
Out of the Box
Motorola
CIEM068
Call/Incident/E
vent
Management
Reopen Incident
The system shall provide the ability to reopen a
CFS event by incident number, location, or unit
ID.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
477
Out of the Box
Motorola
CIEM069
Call/Incident/E
vent
Management
Reopen Incident
The system shall provide the ability to reopen
closed CFS events and assign units.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
478
Out of the Box
Motorola
CIEM070
Call/Incident/E
vent
Management
Reopen Incident
The system shall provide the ability to open a
closed CFS event as a new CFS using
information from the old CFS event, and have
the option preserve old timestamps per Court
monitor requests.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement. PremierOne has the
ability to clone incidents.
479
Out of the Box
Motorola
CIEM071
Call/Incident/E
vent
Management
Add Destination
Locations
The system shall have the ability to accurately
track the destination of all units assigned to a
particular incident within the CFS event, and to
allow these locations and activities to change
throughout the incident.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
480
Out of the Box
Motorola
CIEM072
Call/Incident/E
vent
Management
Multiple
Simultaneous
Incidents to Single
Unit
The system shall allow a dispatcher to hold or
stack events to a busy unit, as well as units that
are in-service.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
481
Out of the Box
Motorola
CIEM073
Call/Incident/E
vent
Management
Multiple
Simultaneous
Incidents to Single
Unit
o If a unit is on an assignment, when the unit
clears its assignment, then the system The
system shall notify the dispatcher the unit is
available.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
482
Out of the Box
Motorola
CIEM074
Call/Incident/E
vent
Management
Multiple
Simultaneous
Incidents to Single
Unit
The system shall provide the agency a method
to define what events can be held.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
483
Out of the Box
Motorola
CIEM075
Call/Incident/E
vent
Management
Multiple
Simultaneous
Incidents to Single
Unit
The system shall notify the unit that it is being
held when an event is placed on hold.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
484
Out of the Box
Motorola
CIEM076
Call/Incident/E
vent
Management
Multiple
Simultaneous
Incidents to Single
Unit
The system shall allow several events to be
placed on hold for a single unit.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
485
Out of the Box
Motorola
CIEM077
Call/Incident/E
vent
Management
Multiple
Simultaneous
Incidents to Single
Unit
The system shall allow a CFS event to be held
for a unit that is not yet logged on.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
486
Out of the Box
Motorola
CIEM078
Call/Incident/E
vent
Management
Multiple
Simultaneous
Incidents to Single
Unit
The system shall record in the history of the CFS
event when an event is placed on hold.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
487
Out of the Box
Motorola
CIEM079
Call/Incident/E
vent
Management
Multiple
Simultaneous
Incidents to Single
Unit
The system shall apply timers to all held CFS
events and alert the dispatcher when a held
event has exceeded the allowable time in a
held status.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
488
Out of the Box
Motorola
CIEM080
Call/Incident/E
vent
Management
Multiple
Simultaneous
Incidents to Single
Unit
The system shall provide dispatchers with the
ability to pre-empt a unit and dispatch the unit
to another event.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
489
Out of the Box
Page 23of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CIEM081
Call/Incident/E
vent
Management
Multiple
Simultaneous
Incidents to Single
Unit
If all units are removed from the original event
the system shall be placed in the pending CFS
events monitor.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
490
Out of the Box
Motorola
CIEM082
Call/Incident/E
vent
Management
Multiple
Simultaneous
Incidents to Single
Unit
The system shall NOT limit the ability of the
dispatcher to assign another unit to the
incident or for field units to self-dispatch
(assign) themselves to an event that has been
placed on hold, if permitted by agency policy.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
491
Out of the Box
Motorola
CIEM083
Call/Incident/E
vent
Management
Scheduled Events
The system shall provide the ability to
automatically schedule the CFS event for future
dispatch.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
492
Out of the Box
Motorola
CIEM084
Call/Incident/E
vent
Management
Scheduled Events
The system shall allow scheduled events to be
created by entering a CFS or by sending a
message.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
493
Out of the Box
Motorola
CIEM085
Call/Incident/E
vent
Management
Scheduled Events
The system shall be capable of displaying a list
of all scheduled events.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
494
Out of the Box
Motorola
CIEM086
Call/Incident/E
vent
Management
Scheduled Events
The system shall provide the ability for
authorized users to activate a scheduled event
at any time.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
495
Out of the Box
Motorola
CIEM087
Call/Incident/E
vent
Management
Scheduled Events
The system shall send a message to the
appropriate users when the scheduled activity
occurs.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
496
Out of the Box
Motorola
CIEM088
Call/Incident/E
vent
Management
Scheduled Events
The system shall support location override for
scheduled incidents.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
497
Out of the Box
Motorola
CIEM089
Call/Incident/E
vent
Management
Single Discipline
Incident to Combine
Discipline Incident
The system shall provide the ability to add
another agency’s resources to a CFS event.
Preferred
CAD
X
PremierOne complies with the functionality as described in the requirement.
498
Out of the Box
Motorola
CIEM090
Call/Incident/E
vent
Management
Single Discipline
Incident to Combine
Discipline Incident
The system shall provide the ability to assign an
agency specific incident/event number to the
CFS event.
Preferred
CAD
X
PremierOne complies with the functionality as described in the requirement.
499
Out of the Box
Motorola
CIEM091
Call/Incident/E
vent
Management
Single Discipline
Incident to Combine
Discipline Incident
The system shall provide the ability to link
added agency records with the initial CFS event.
Preferred
CAD
X
PremierOne complies with the functionality as described in the requirement.
500
Out of the Box
Motorola
CIEM092
Call/Incident/E
vent
Management
Single Discipline
Incident to Combine
Discipline Incident
The system shall provide the ability to share
incident information across multiple linked
records.
Preferred
CAD
X
PremierOne complies with the functionality as described in the requirement.
501
Out of the Box
Motorola
CIEM093
Call/Incident/E
vent
Management
Single Discipline
Incident to Combine
Discipline Incident
The system shall provide the ability to track the
added resources for the duration of the
incident.
Preferred
CAD
X
PremierOne complies with the functionality as described in the requirement.
502
Out of the Box
Motorola
CIEM094
Call/Incident/E
vent
Management
Timers
The system shall have, and allow configuration
of, multiple timers based on unit status and
CAD incident type, such as time on a particular
call, time since last check-in, and time at the
hospital or jail.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
503
Out of the Box
Motorola
CIEM095
Call/Incident/E
vent
Management
Timers
The system shall have, and allow configuration
of, timers for CAD system events, such as a
priority 1 call overdue to be dispatched.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
504
Out of the Box
Motorola
CIEM096
Call/Incident/E
vent
Management
Timers
The system shall allow for operators to
manually place a timer alert on a CFS or a unit.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
505
Out of the Box
Motorola
CIEM097
Call/Incident/E
vent
Management
Timers
The system shall minimally include “down to
the second” timestamps (e.g. hhhh/mm/ss).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
506
Out of the Box
Motorola
CIEM098
Call/Incident/E
vent
Management
Timers
The system shall allow configurable timers (i.e.
‘hh:mm:ss’, ‘mm:ss’, or ‘ss’).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
507
Out of the Box
Motorola
CIEM099
Call/Incident/E
vent
Management
User Defined Status
Timers
The system shall be equipped with predefined
timers that can be configured by the system
administrator.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
508
Out of the Box
Motorola
CIEM100
Call/Incident/E
vent
Management
User Defined Status
Timers
The system shall provide the ability for the
system administrator to create customized
definable timers.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
509
Out of the Box
Motorola
CIEM101
Call/Incident/E
vent
Management
User Defined Status
Timers
The system shall record timer activity to the
CFS event log.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
510
Out of the Box
Motorola
CIEM102
Call/Incident/E
vent
Management
User Defined Status
Timers
The system shall produce both visual and
audible alerts to the dispatcher when a timer is
triggered.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
511
Out of the Box
Motorola
CIEM103
Call/Incident/E
vent
Management
Attempt to Locate
The system should support the creation and
maintenance of agency-definable ATL related to
people, places, and objects (e.g., cars) for
dissemination to users via a mask.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
512
Out of the Box
Motorola
CIEM104
Call/Incident/E
vent
Management
Attempt to Locate
The system should provide the ability to archive
and query ATL by date, time range, and all
other data fields.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
513
Out of the Box
Page 24of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CIEM105
Call/Incident/E
vent
Management
Attempt to Locate
The ATL should be capable of being associated
to a specific event(s) and the information
should be added to the event.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
514
Out of the Box
Motorola
CIEM106
Call/Incident/E
vent
Management
Attempt to Locate
Users should have the ability to send the ATL
and information to workstations, MDCs, and
groups.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
515
Out of the Box
Motorola
CIEM107
Call/Incident/E
vent
Management
Attempt to Locate
When generating a ATL with an event number,
the system should auto fill agency-defined
information.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement by manually placing
note in the ATL.
516
Out of the Box
Motorola
CDISP001
Dispatching
General
The system should allow any dispatcher to take
control of any event from another dispatcher.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
517
Out of the Box
Motorola
CDISP002
Dispatching
General
The system should allow dispatchers to control
units and events based on geographical
location, e.g. talk group.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
518
Out of the Box
Motorola
CDISP003
Dispatching
General
The system should provide the capability to
dispatch non-County units such as other
municipalities being dispatched by the MCSO,
Citizen Volunteers, Animal Control Officers,
Park Rangers, and Code Compliance Officers,
some of which may not be equipped with
MDCs. The displays of non-County activities
should utilize labels and colors that are system
administrator definable.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
519
Out of the Box
Motorola
CDISP004
Dispatching
General
The system should provide the capability to
segregate Telephone Response Unit (TRU),
Animal Control Officers and any other groups
that may be dispatched now and in the future
into separate screen displays. An example
would be to configure separate calls pending
displays for each group.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
520
Out of the Box
Motorola
CET003
Dispatching
General
DISPATCH SCREEN
521
0
Motorola
CDISP005
Dispatching
General
The systems should be able to dynamically
display unit and event data without the need to
manually refresh the display.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
522
Out of the Box
Motorola
CDISP006
Dispatching
General
The patrol area should display on the header of
all event displays.
Mandatory
CAD
X
PremierOne partially complies with the functionality as described in the requirement. The patrol
area does not display in the header, but it is visible in the event display.
523
Out of the Box
Motorola
CDISP007
Dispatching
General
The system should be able to dynamically
display event and/or unit status data in a
summary window.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
524
Out of the Box
Motorola
CDISP008
Dispatching
General
The system should require only the minimum
amount of user interaction (key strokes) to
navigate pages.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
525
Out of the Box
Motorola
CDISP009
Dispatching
General
The system should allow MCSO to create pre-
defined event and/or unit status monitors to
accommodate logical groupings (e.g., by status,
area, agency, jurisdiction).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
526
Out of the Box
Motorola
CDISP010
Dispatching
General
The user should be able to modify the sorting of
the status monitor every column within a status
monitor (e.g., by time, by status, by location,
etc.).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
527
Out of the Box
Motorola
CDISP011
Dispatching
General
The system should permit the user to configure
the column of the status monitor in
ascending/descending order.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
528
Out of the Box
Motorola
CDISP012
Dispatching
General
The system should have the user-defined ability
to vertically and/or horizontally sort and/or
group units and/or events.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement. PremierOne
provides the ability for users to sort and filter the display of events.
529
Out of the Box
Motorola
CDISP013
Dispatching
General
The system should be able to maintain an
unlimited number of events or units within a
single monitor.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
530
Out of the Box
Motorola
CDISP014
Dispatching
General
The system should be able to display elapsed
time in status monitors.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
531
Out of the Box
Motorola
CDISP015
Dispatching
General
The unit and dispatch screen format should be
fully configurable by agency.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
532
Out of the Box
Motorola
CDISP016
Dispatching
General
The system should provide the ability to
monitor events and unit status using user
defined parameters.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
533
Out of the Box
Motorola
CDISP017
Dispatching
General
The event type with the highest agency defined
priority should be in the forefront and the
update visually differentiated from the other
call details, e.g. highlighted.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
534
Out of the Box
Motorola
CDISP018
Dispatching
General
Radio Identifiers. Agency configurable incident
and command radio channels (multiple fields)
should appear on the event display, including
the mobile terminal displays. Communications
needs the capability to change these fields
when an event is moving to another channel
(talk group).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
535
Out of the Box
Motorola
CET003
Dispatching
General
DISPATCH DISPLAY
536
0
Page 25of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CDISP019
Dispatching
User Interface
CAD monitors should be sortable by the user;
unwanted fields should be able to be turned off
at user preference. There should also be a save
feature for the individual user preference.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
537
Out of the Box
Motorola
CDISP020
Dispatching
User Interface
Monitors should have a clearly defined format
to identify held events.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
538
Out of the Box
Motorola
CDISP021
Dispatching
User Interface
All monitors should have a clearly defined
format to display expired timers. The capability
to have visual warnings move to the top of the
calls status screen has been suggested.
Mandatory
CAD
X
PremierOne complies with the functionality as described in first part of this requirement. The
visual warnings do not move to the top of the call status screen.
539
Out of the Box
Motorola
CDISP022
Dispatching
User Interface
All monitors should have a clearly defined
format to display expired timers.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
540
Out of the Box
Motorola
CDISP023
Dispatching
User Interface
The Communications Supervisor CAD
Administrator should have the capability to set
timers by call type. For example, the timer for
a domestic disturbance may be different from a
check welfare call.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
541
Out of the Box
Motorola
CDISP024
Dispatching
User Interface
MCSO dispatchers should be able to sort by
dispatch group or station assignment.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
542
Out of the Box
Motorola
CDISP025
Dispatching
User Interface
The user should be able to monitor any
dispatch group without taking or having control
over the units or events.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
543
Out of the Box
Motorola
CDISP026
Dispatching
User Interface
All of the attributes of all masks of any display
should be configurable by the System
Administrator.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
544
Out of the Box
Motorola
CDISP027
Dispatching
User Interface
Resizing windows should not stop the system
from processing information.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
545
Out of the Box
Motorola
CDISP028
Dispatching
User Interface
The system should provide, at a minimum, real
time monitors for monitoring:
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
546
Out of the Box
Motorola
CDISP028-1
Dispatching
User Interface
Active Events
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
547
Out of the Box
Motorola
CDISP028-2
Dispatching
User Interface
Pending Events
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
548
Out of the Box
Motorola
CDISP028-3
Dispatching
User Interface
Available Units
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
549
Out of the Box
Motorola
CDISP028-4
Dispatching
User Interface
Push to talk (radio interface)
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
550
Out of the Box
Motorola
CDISP028-5
Dispatching
User Interface
Active Units
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
551
Out of the Box
Motorola
CDISP028-6
Dispatching
User Interface
Unit Status
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
552
Out of the Box
Motorola
CDISP029
Dispatching
User Interface
The system should display in a separate
window on the status monitor a chronological
display of push to talk radio IDs as they are
received at that position. The system should log
incoming push to talk messages to include date
and time stamp and radio ID and unit
designator.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
553
Out of the Box
Motorola
CDISP030
Dispatching
User Interface
Users should have the ability to turn on or turn
off monitors (the system administrator will
determine if any monitor can not be turned
off).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
554
Out of the Box
Motorola
CDISP031
Dispatching
User Interface
Held events should have a visible identifier on
related monitors
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
555
Out of the Box
Motorola
CDISP032
Dispatching
General
The information displayed in monitors should
be configurable by the system, performing
logical processing of any associated unit or
event data values. Examples include: monitor
designed/ configured to display all units that
are not currently available in their home
quarters, i.e., any unit staffed with less than
three personnel.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
556
Out of the Box
Motorola
CDISP033
Dispatching
General
The system should provide for a method of
monitoring units that have been "relocated".
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
557
Out of the Box
Motorola
CET003
Dispatching
General
EQUIPMENT STATUS MONITOR
558
0
Motorola
CDISP034
Dispatching
General
The system should display the location of
incidents and units in real-time without
manually having to refresh the system.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
559
Out of the Box
Motorola
CDISP035
Dispatching
User Interface
The system should provide a fully user-
configurable unit status table and allow real-
time updates to status, e.g., “on-scene”.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
560
Out of the Box
Motorola
CDISP036
Dispatching
General
The proposed application should include the
ability to return an assigned unit to service
(user definable) and dispatch a second unit to
the event from which the first is being freed
with a single command. The system should be
able to exchange two units assigned to
separate events with a single command.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
561
Out of the Box
Motorola
CDISP037
Dispatching
General
The proposed application should automatically
preempt a Unit(s) when they are assigned to a
different event. This should be definable by
agency, discipline, or jurisdiction.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
562
Out of the Box
Motorola
CDISP038
Dispatching
User Interface
The system should provide a quick and easy
way to change a unit's status.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
563
Out of the Box
Motorola
CET003
Dispatching
General
DISPATCH FUNCTIONS
564
0
Page 26of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CDISP039
Dispatching
General
The system should provide the ability for the
system administrator to permit users to
update/modify event types, dispositions,
addresses and other user-definable data for
events that have been closed without having to
re-open event.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
565
Out of the Box
Motorola
CDISP040
Dispatching
General
The proposed application should provide the
ability to cross reference or duplicate events
and memo those events with user defined
information.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
566
Out of the Box
Motorola
CDISP041
Dispatching
General
The system should provide a command for
changing the location and/or status of a unit(s)
assigned or recommended to an event.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
567
Out of the Box
Motorola
CDISP042
Dispatching
General
The system should provide the capability to
reroute or reassign units to higher priority calls
without necessarily removing them from their
current events/assignments. When
rerouted/reassigned, appropriate tracking
should take place to avoid inaccurate response
time reporting.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
568
Out of the Box
Motorola
CDISP043
Dispatching
General
The system should allow deputies to be
removed from a call and assigned to a higher
priority call without closing the original event if
any other officers remain on the call. One or
more of the reassigned units may retain
ownership of the original call and return to it
when time is available.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
569
Out of the Box
Motorola
CET003
Dispatching
General
ATTACH EVENT INFORMTATION
570
0
Motorola
CDISP044
Dispatching
User Interface
Users should have the ability to attach
information into an event, this includes
messages sent from workstations and/or
MDC's.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
571
Out of the Box
Motorola
CDISP045
Dispatching
General
All attached information should be tracked in
the event history and should identify the
employee ID, workstation ID and time and date
stamp.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
572
Out of the Box
Motorola
CDISP046
Dispatching
User Interface
The system should provide users the ability to
attach information into active and inactive
events. This functionality should allow field
units and Communications Staff to add
comments to active and inactive events.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
573
Out of the Box
Motorola
CET003
Dispatching
General
HOLDING EVENTS
574
0
Motorola
CDISP047
Dispatching
General
Holding means that events are in the pending
queue and not yet assigned because they are
being held for a specific unit.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
575
Out of the Box
Motorola
CDISP048
Dispatching
General
The system should allow a dispatcher to hold
events to a busy unit as well as units that are in-
service. If a unit is on an assignment, when the
unit(s) clears its assignment the application
should notify the dispatcher and the unit(s) that
held events are waiting for the unit(s) and the
unit(s) is now available. The Agency should be
able to define which events can be held.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
576
Out of the Box
Motorola
CDISP049
Dispatching
General
When an event is placed on hold it should
notify the unit that it is being held for the unit.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
577
Out of the Box
Motorola
CDISP050
Dispatching
General
The system should allow several events to be
placed on hold for a single unit.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
578
Out of the Box
Motorola
CDISP051
Dispatching
General
An event being placed on hold should not limit
the ability of the dispatcher to send another
unit on the event or for field units self
dispatching on the event.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
579
Out of the Box
Motorola
CDISP052
Dispatching
General
The system should allow an event to be held for
a unit that is not yet logged on
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
580
Out of the Box
Motorola
CDISP053
Dispatching
General
When an event is placed on hold it should be
reflected in the history of the event.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
581
Out of the Box
Motorola
CDISP054
Dispatching
General
Timers should be applied to all held events.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
582
Out of the Box
Motorola
CET003
Dispatching
General
CROSS REFERENCING EVENTS
583
0
Motorola
CDISP055
Dispatching
General
In the event that the dispatcher determines
that one or more CAD events reference the
same call for service it should be possible to
cross-reference the events.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
584
Out of the Box
Motorola
CDISP056
Dispatching
General
When cross-referencing two events the system
should enter the event number of each cross-
referenced event into the audit trail of the
other event(s).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
585
Out of the Box
Motorola
CDISP057
Dispatching
General
The system should include the ability to
perform a cross-reference of events in one
step.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
586
Out of the Box
Page 27of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CDISP058
Dispatching
General
The system should have the ability, if desired,
to transfer name, call back number, remarks
and any other user defined event information
along with the event ID into the event that is
being retained.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
587
Out of the Box
Motorola
CET003
Dispatching
General
EXCHANGING UNITS
588
0
Motorola
CDISP059
Dispatching
General
The system should be able to exchange one
unit assigned to an event with another unit
with a single agency defined command.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
589
Out of the Box
Motorola
CDISP060
Dispatching
General
The system should automatically preempt a
unit(s) assigned to an event when they are
assigned to a different event. This should be
definable by agency.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
590
Out of the Box
Motorola
CDISP061
Dispatching
General
The system should include the ability to return
an assigned unit to service (agency-definable),
and dispatch a second unit to the event from
which the first is being freed with a single
command.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
591
Out of the Box
Motorola
CET003
Dispatching
General
ASSIGNING DISPOSITION
592
0
Motorola
CDISP062
Dispatching
User Interface
The system should allow the user to assign a
disposition to an event. The disposition types
should be determined by the System
Administrator
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
593
Out of the Box
Motorola
CDISP063
Dispatching
General
The system should have the capability to assign
multiple dispositions to a to a single event.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
594
Out of the Box
Motorola
CDISP064
Dispatching
General
If multiple dispositions are assigned to an event
the disposition received from the primary
assigned unit should be the final disposition.
Mandatory
CAD
X
PremierOne partially complies with the functionality of this requirement. If an agency decides that
a disposition is required, the agency has the following configuration options:
1. Require at least one disposition to close the incident. In this case, a disposition must be
provided when closing an incident. A disposition may or may not be associated with a resource
unit assigned to the incident.
2. Require each standard resource unit (the primary unit) that was assigned to the incident to
specify a disposition before that unit can be cleared from the incident. In this case, a disposition
must be provided for the standard resource unit to clear an active unit from an incident.
3. Require a disposition only from the standard resource unit designated as
the primary unit. In this case, the primary unit must provide a disposition to be cleared from the
incident. All non-primary units can be cleared from the incident without requiring a disposition.
In all three cases, the appropriate dispositions can also be provided when closing the incident. The
appropriate dispositions can be provided ahead of time (while units remain assigned to the
incident), therefore allowing you to close the incident by simply clearing the last unit from the
incident.
595
Out of the Box
Motorola
CDISP065
Dispatching
General
The system should provide the ability to change
or add a disposition on a closed event based
upon system administrator configurable
security settings and role based privileges.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
596
Out of the Box
Motorola
CDISP066
Dispatching
General
Dispositions should be displayed in a manner
that is easy for Users to see.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
597
Out of the Box
Motorola
CDISP067
Dispatching
General
The system should not allow a call to be closed
if any units are still on the call.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
598
Out of the Box
Motorola
CDISP068
Dispatching
General
Once the last unit has cleared an event, that
event should automatically close without a
disposition code if the event type does not
require a disposition.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
599
Out of the Box
Motorola
CET003
Dispatching
General
PRE-EMPT
600
0
Motorola
CDISP069
Dispatching
General
The user should have the ability to pre-empt a
unit(s) from an active call, the unit(s) should be
placed available and the event should go to the
pending event monitor (if no unit remains
active on the call).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
601
Out of the Box
Motorola
CDISP070
Dispatching
General
Users should have the ability to pre-empt a
unit(s) and dispatch the unit(s) on another
event. If all units are removed from the original
event it should be placed in the pending events
monitor.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
602
Out of the Box
Motorola
CET003
Dispatching
General
EVENT AND UNIT TIMERS
603
0
Motorola
CDISP071
Dispatching
General
The system should be able to display elapsed
timers in agency defined status monitors.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
604
Out of the Box
Motorola
CDISP072
Dispatching
General
The system should have the ability to create
pre-defined agency configurable elapsed timers
for events and/or unit status changes.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
605
Out of the Box
Motorola
CDISP073
Dispatching
General
The system should allow users to create a
custom, one-time event or unit specific elapsed
timer (e.g., unit contact timer).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
606
Out of the Box
Motorola
CDISP074
Dispatching
General
The system should be able to display an agency
defined warning if elapsed timer expires (visual
and/or audible alert).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
607
Out of the Box
Page 28of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CDISP075
Dispatching
General
The system should provide an event timer that
will: activate after 'n' minutes and will initiate
countdown upon unit arrival. "n' =
Administrator selected based upon Event type.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
608
Out of the Box
Motorola
CDISP076
Dispatching
General
The user should have the ability to turn off or
reset all timers for a single, multiple or all units
related to a single event in a single command.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
609
Out of the Box
Motorola
CDISP077
Dispatching
General
The system should provide an active window to
display units whose timers have expired, once
the timers are reset the units should disappear
from this active window.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
610
Out of the Box
Motorola
CDISP078
Dispatching
General
The dispatcher should have the ability to cancel
or set all the units timers associated with an
event if necessary with a single action.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
611
Out of the Box
Motorola
CDISP079
Dispatching
General
The system should record all event and unit
times, including tracking times separately for
primary and all secondary units assigned to a
call.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
612
Out of the Box
Motorola
CET003
Dispatching
General
DISPATCHER/FIELD UPDATE NOTIFICATIONS
613
0
Motorola
CDISP080
Dispatching
General
The dispatcher should be notified by an agency-
configurable visual and/or and audible alert
when a new event has been created and is
pending which is also based on event priority.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
614
Out of the Box
Motorola
CDISP081
Dispatching
General
The system should provide agency-definable
visual and audible alerts to notify field
units/dispatchers of event priority changes and
supplemental information.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
615
Out of the Box
Motorola
CDISP082
Dispatching
General
The dispatcher should have a visual indication
that a call has been updated without having to
rely on the Status Monitor.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
616
Out of the Box
Motorola
CDISP083
Dispatching
General
If a generic update button indicator is used to
alert the user that a call has been updated the
dispatcher should be able to click on the button
and be presented with the updated
information.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
617
Out of the Box
Motorola
CDISP084
Dispatching
General
Once viewed the details should display as
normal and the update indicator returned to
neutral. If there are more updates to view, the
update button would continue to be lit.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
618
Out of the Box
Motorola
CDISP085
Dispatching
General
The necessity to scroll or search through the
record should be minimized.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
619
Out of the Box
Motorola
CDISP086
Dispatching
User Interface
When a dispatcher makes an update,
supplement or change to an event they control
they should not receive notification of that
change, however the dispatcher should be
notified if change is made by call taker.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
620
Out of the Box
Motorola
CDISP087
Dispatching
User Interface
The dispatcher should be advised immediately
whenever a field unit self dispatches or self
initiates on an event. The importance level of
the notification should be configurable by the
System Administrator. The system should be
capable of being set to send urgent
notifications to the dispatcher for certain event
types such as robberies, traffic stops etc. and to
send routine notifications for minor event types
such as marking out at the station or court
.When a self initiating unit has currently
assigned calls, the system needs to prompt the
dispatcher to either reassign the "orphaned"
calls, place them back in calls holding, or allow
them to remain with the unit for later follow-
up. Some definitive action should be taken to
ensure that the "orphaned" calls are processed.
Mandatory
CAD
X
PremierOne partially complies with this requirement. Notifications are sent to the dispatcher for
all self-initiated dispatches and the initial call is stacked if the system is provisioned for call
stacking. All notifications are sent with the same notification status, but the call type would have
an elevated priority
621
Out of the Box
Motorola
CDISP088
Dispatching
General
The system should not allow a unit to self
initiate on a call without entering an event type
and location.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
622
Out of the Box
Motorola
CDISP089
Dispatching
General
Emergency activations from either radio or
MDC's should create an emergency notification
to the dispatcher
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
623
Out of the Box
Motorola
CDISP090
Dispatching
User Interface
Any Emergency activation should require a
dispatch function to acknowledge the
activation
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
624
Out of the Box
Motorola
CET003
Dispatching
General
UNIT/RESOURCE SET-UP
625
0
Motorola
CDISP091
Dispatching
General
The system should allow the system
administrator to configure unit attributes.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
626
Out of the Box
Page 29of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CDISP092
Dispatching
General
The status screen(s) at the workstation should
have a agency configurable display of response
areas.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
627
Out of the Box
Motorola
CDISP093
Dispatching
General
The system should allow for multiple unit types
by agency, discipline and jurisdiction
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
628
Out of the Box
Motorola
CDISP094
Dispatching
General
Different discipline, agency and jurisdictions
should have the ability to create common alpha
numeric unit IDs.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
629
Out of the Box
Motorola
CDISP095
Dispatching
General
The unit ID should be able to contain a
minimum of eight (8) alpha numeric characters.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
630
Out of the Box
Motorola
CDISP096
Dispatching
General
The system should maintain multiple agency-
definable identifiers for each unit such as unit
designator, vehicle number, portable radio
number, mobile radio number, EIN, CAD ID,
home quarters, etc.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
631
Out of the Box
Motorola
CDISP097
Dispatching
General
The system should be able to query a unit
based on associated data such as: unit
designator, vehicle number, portable radio
number, mobile radio number, EIN, CAD ID,
home quarters, etc.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
632
Out of the Box
Motorola
CDISP098
Dispatching
General
The user should have the ability to search the
system for unit related resources. For example:
special skills such as languages, EMT and
abilities, RBT tech, crash reconstruction.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
633
Out of the Box
Motorola
CET003
Dispatching
General
EVENT RECOMMENDATIONS
634
0
Motorola
CDISP099
Dispatching
General
MCSO currently uses patrol areas and may be
planning to incorporate closest unit dispatch as
part of this system migration. Event displays
and recommendations need to be able to
provide this type of dispatcher specific data.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
635
Out of the Box
Motorola
CDISP100
Dispatching
General
All events should be assigned to a dispatcher
via; a map driven "special/temporary"
geographical area, the response area, or the
event type as defined by the Agency, discipline
and jurisdiction. Hierarchy of assignment is in
the above listed order. E.g. a temporary
dispatch area overrides all other pre-designed
routing parameters.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
636
Out of the Box
Motorola
CDISP101
Dispatching
General
All system recommended units should be
displayed on one screen.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
637
Out of the Box
Motorola
CDISP102
Dispatching
General
The response order recommendations are
based on AVL, or /Patrol Area assignments. The
dispatcher should be able to choose between
either of the above recommendations with a
user selectable function.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
638
Out of the Box
Motorola
CDISP103
Dispatching
General
The system should be capable of being
configured to recommend on unit type, unit
capabilities, AVL position and/or area
responsibilities
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
639
Out of the Box
Motorola
CDISP104
Dispatching
General
The system should have a recommended unit
override function. Individual unit(s) can be
removed from the recommended list via a
mouse click. Multiple units should be able to be
added to the dispatch via a free form line.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
640
Out of the Box
Motorola
CDISP105
Dispatching
General
The system should also show all closest
alternate units and be able to add individual
unit(s) to the dispatch compliment via a mouse
click, command line, etc.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
641
Out of the Box
Motorola
CDISP106
Dispatching
General
Any dispatcher can view a pending event and
unit recommendation without any impact on
the controlling dispatcher viewing the same
information and the dispatching of the event.
e.g.. when someone views an event with
recommended units the units are not
encumbered in any way.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
642
Out of the Box
Motorola
CDISP107
Dispatching
General
The system should provide the dispatcher a
method to view the closest available unit (s)
(least travel time) for any location or event.
The default number of unit(s) and or unit types
to be automatically displayed is agency
configurable.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
643
Out of the Box
Motorola
CDISP108
Dispatching
General
The system should support the ability to
recommend the closest (least travel time)
appropriate unit(s) for an event, based on
unique capabilities; e.g. Shot-gun certified,
canine, etc.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
644
Out of the Box
Page 30of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CDISP109
Dispatching
General
The system should provide for a mechanism to
automatically recommend a "Special" response
compliment for a predefined location/event
type combination.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
645
Out of the Box
Motorola
CDISP110
Dispatching
General
The system should automatically generate
priority, unit type requirements, back up, or
non-standard routing based on the parameters
for that event as defined by the system
administrator.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
646
Out of the Box
Motorola
CET003
Dispatching
General
DISPATCHING EVENTS
647
0
Motorola
CDISP111
Dispatching
User Interface
The dispatcher should be able to process
pending events in any sequence.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
648
Out of the Box
Motorola
CDISP112
Dispatching
User Interface
Users should have the ability to dispatch a
single unit or multiple units with no limit to the
number of units that can be dispatched to a
single event.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
649
Out of the Box
Motorola
CDISP113
Dispatching
User Interface
When selected, the event should automatically
display along with unit recommendations
according to the Agency Parameters set for
each event type. Dispatchers should be able to,
at any time, quickly request the display and unit
recommendations for any pending event
without having to perform multiple steps.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
650
Out of the Box
Motorola
CDISP114
Dispatching
User Interface
When the system recommends units for
dispatch or a request is made for additional
units, the dispatcher should have the following
options for completing the dispatch:
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
651
Out of the Box
Motorola
CDISP114-1
Dispatching
User Interface
Press a single key to accept the recommended
units and dispatch
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
652
Out of the Box
Motorola
CDISP114-2
Dispatching
User Interface
Select individual units from the recommended
units for dispatch, then dispatch
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
653
Out of the Box
Motorola
CDISP114-3
Dispatching
User Interface
Select units not recommended by the system
for dispatch , then dispatch
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
654
Out of the Box
Motorola
CDISP114-4
Dispatching
User Interface
Accept recommended units and add to, then
dispatch,
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
655
Out of the Box
Motorola
CDISP114-5
Dispatching
User Interface
Based on geographical area, display a static
response order for all units.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
656
Out of the Box
Motorola
CDISP115
Dispatching
User Interface
The proposed CAD should allow a dispatcher to
dispatch:
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
657
Out of the Box
Motorola
CDISP115-1
Dispatching
User Interface
From the command line, through the event
Dispatch form, or
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
658
Out of the Box
Motorola
CDISP115-2
Dispatching
User Interface
From a mouse click on the status monitor
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
659
Out of the Box
Motorola
CDISP115-3
Dispatching
User Interface
From a mouse click on a unit icon on the map
display
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
660
Out of the Box
Motorola
CDISP115-4
Dispatching
User Interface
“Hot Keys”
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
661
Out of the Box
Motorola
CDISP116
Dispatching
User Interface
The dispatcher should be able to transfer any
pending event to another dispatcher. Any
dispatcher should be able to dispatch units to
any event based on agency control.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
662
Out of the Box
Motorola
CDISP117
Dispatching
User Interface
The user should have the ability to dispatch a
unit or units to a defined location other than
that of the event location when necessary
based on agency control.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
663
Out of the Box
Motorola
CDISP118
Dispatching
User Interface
Once a pending event has been displayed, the
system should be configurable so that
subsequent displays will automatically generate
unit recommendations based on agency
control.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
664
Out of the Box
Motorola
CDISP119
Dispatching
User Interface
Once the event has been displayed, the
dispatcher should be able to dispatch the event
from the pending event list without re-display
based on agency control. An event should not
have to be displayed in order to dispatch the
event.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
665
Out of the Box
Motorola
CDISP120
Dispatching
User Interface
With the AVL feature the user should be able to
click on an event then on a unit or units to
assign the units to the call regardless of control
(group assignment) of that unit.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
666
Out of the Box
Motorola
CDISP121
Dispatching
User Interface
Users should be able to assign units to an event
via the command line.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
667
Out of the Box
Motorola
CET003
Dispatching
General
SELF-INITIATED EVENTS
668
0
Motorola
CDISP122
Dispatching
User Interface
The system should include a command, agency
defined, for CAD (including MDC) users to
create an event, assign and arrive a unit in a
single step. (Self-Initiated Event) For example,
an officer comes upon an accident while on
routine patrol.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
669
Out of the Box
Motorola
CDISP123
Dispatching
User Interface
The system should automatically attempt to
verify the event location for the self-initiated
event.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
670
Out of the Box
Page 31of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CDISP124
Dispatching
User Interface
If the self-initiated event is a high priority event
the system should automatically generate
necessary notifications.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
671
Out of the Box
Motorola
CDISP125
Dispatching
User Interface
The order of the notifications sent to the
dispatcher should be based on the event
priority. For example a unit marks on a parking
complaint at the same time another unit marks
on a traffic stop, the traffic stop should move
ahead of the parking complaint.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
672
Out of the Box
Motorola
CET003
Dispatching
General
EVENT/UNIT STATUS
673
0
Motorola
CDISP126
Dispatching
General
The system should be capable of establishing
and processing the following agency-definable
unit and event statuses:
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
674
Out of the Box
Motorola
CDISP126-1
Dispatching
General
In-service
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
675
Out of the Box
Motorola
CDISP126-2
Dispatching
General
Waiting/Pending(new and not yet assigned)
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
676
Out of the Box
Motorola
CDISP126-3
Dispatching
General
Acknowledge
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
677
Out of the Box
Motorola
CDISP126-4
Dispatching
General
Enroute
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
678
Out of the Box
Motorola
CDISP126-5
Dispatching
General
Dispatched, (assigned to a unit(s)
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
679
Out of the Box
Motorola
CDISP126-6
Dispatching
General
Arrived, (need an indication and timestamp for
each unit arriving on scene)
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
680
Out of the Box
Motorola
CDISP126-7
Dispatching
General
On the Scene (Arrived)
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
681
Out of the Box
Motorola
CDISP126-8
Dispatching
General
Transport hospital, jail, etc.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
682
Out of the Box
Motorola
CDISP126-9
Dispatching
General
Arrived hospital, jail, etc.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
683
Out of the Box
Motorola
CDISP126-10
Dispatching
General
Scheduled, (entered into the system but not
due for service until a scheduled time and
date), and
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
684
Out of the Box
Motorola
CDISP126-11
Dispatching
General
Closed
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
685
Out of the Box
Motorola
CDISP126-12
Dispatching
General
APD Available at station
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
686
Out of the Box
Motorola
CDISP126-13
Dispatching
General
AOV Available Out of Vehicle
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
687
Out of the Box
Motorola
CDISP126-14
Dispatching
General
AOP Available on pager or phone
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
688
Out of the Box
Motorola
CDISP126-15
Dispatching
General
OUT of service not available for call
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
689
Out of the Box
Motorola
CDISP126-16
Dispatching
General
Available
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
690
Out of the Box
Motorola
CDISP126-17
Dispatching
General
Unavailable
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
691
Out of the Box
Motorola
CDISP126-18
Dispatching
General
Available but on scene
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
692
Out of the Box
Motorola
CDISP126-19
Dispatching
General
Report Writing
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
693
Out of the Box
Motorola
CDISP127
Dispatching
User Interface
To assist the agency in monitoring the arrival of
units to events, vendors are requested to
propose possible solutions (e.g., management
reports identifying units that have neglected to
"mark" themselves on the scene of an event).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement. With PremierOne
Mobile the County can utilize GPS data to automatically update unit status to arrived on scene
when the unit is within a set distance from the location.
694
Out of the Box
Motorola
CDISP128
Dispatching
General
The system should have the ability to require at
least one unit to be on the scene, or have the
call closed, before any unit responding can go
available. The call should not be able to be
closed if no unit has arrived on scene or the call
was cancelled. Communications is trying to
ensure that a unit actually arrives, thus
preventing all units from being made available
from a call when it is the intent.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
695
Out of the Box
Motorola
CET003
Dispatching
General
RESOURCE CONTROL/RESPONSIBILITY
696
0
Motorola
CDISP129
Dispatching
User Interface
The system should support the ability to easily
search for and identify special capabilities to
employees, units, and equipment.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
697
Out of the Box
Motorola
CDISP130
Dispatching
User Interface
The system should allow the system
administrator to establish a home location for
each unit and a user defined ability to view any
home quarters/group and all units assigned to
it.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
698
Out of the Box
Motorola
CDISP131
Dispatching
User Interface
Upon dispatch, the system should remove the
event from the pending queue, update the
status display, start the status timers, and log
the times. All event information should be
placed into the dispatched unit(s) history.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
699
Out of the Box
Motorola
CDISP132
Dispatching
User Interface
The dispatcher should be able to quickly
request and display unit recommendations in
dispatch order for any pending and
dispatched/working event.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
700
Out of the Box
Motorola
CDISP133
Dispatching
User Interface
The dispatcher should be able to transfer the
control of any unit to another dispatcher based
on agency control.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
701
Out of the Box
Motorola
CDISP134
Dispatching
User Interface
The dispatcher should have the ability to take
control of any unit based on agency control.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
702
Out of the Box
Motorola
CDISP135
Dispatching
User Interface
The system should be capable of determining
the last known location for a unit.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
703
Out of the Box
Motorola
CDISP136
Dispatching
User Interface
The system should include the ability to make
available one or more assigned unit(s) from an
event.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
704
Out of the Box
Page 32of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CDISP137
Dispatching
User Interface
The proposed application should include the
ability to change unit status of one or more
assigned Unit(s) on an event.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
705
Out of the Box
Motorola
CET003
Dispatching
General
ASSISTING UNITS
706
0
Motorola
CDISP138
Dispatching
General
The system should recommend assisting units
based on unit type and/or capability.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
707
Out of the Box
Motorola
CDISP139
Dispatching
General
The system should recommend assisted units
based either on AVL position or by area
assignment.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
708
Out of the Box
Motorola
CET003
Dispatching
General
ASSIST
709
0
Motorola
CDISP140
Dispatching
User Interface
The system should provide a command to
assign and record a unit providing backup
assistance to an event.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
710
Out of the Box
Motorola
CDISP141
Dispatching
General
The command should allow a dispatcher, to
type a command for “Assist” followed by a unit
number. The CAD system should record the
unit as dispatched to the other unit’s event.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
711
Out of the Box
Motorola
CDISP142
Dispatching
General
The command should allow an MDC equipped
unit to utilize a "hot" button for “Assist”. The
CAD system should record the unit as
dispatched to the other unit’s event.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
712
Out of the Box
Motorola
CDISP143
Dispatching
General
The CAD system should record the unit as
dispatched to the other unit’s event.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
713
Out of the Box
Motorola
CDISP144
Dispatching
General
The assisting unit should receive a “Dispatch
Message” from the CAD system detailing the
event information.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
714
Out of the Box
Motorola
CDISP145
Dispatching
General
All assist commands should be reflected in the
related monitors.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
715
Out of the Box
Motorola
CDISP146
Dispatching
General
All assist commands should be reflected in the
related unit histories.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
716
Out of the Box
Motorola
CDISP147
Dispatching
General
ASSIST ENROUTE
717
0
Motorola
CDISP147
Dispatching
General
A Command to assign and record a unit
providing backup assistance as enroute to an
event is desired.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
718
Out of the Box
Motorola
CDISP148
Dispatching
General
Command allows a unit, or dispatcher, to type a
command for “Assist Enroute” and another unit
ID. The CAD system should record the unit as
“assigned” and enroute to the other unit’s
event. The assisting unit should receive a
“Dispatch Message” from the CAD system
detailing the event information.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
719
Out of the Box
Motorola
CDISP147
Dispatching
General
ASSIST ONSCENE
720
0
Motorola
CDISP150
Dispatching
General
A Command to assign and record a unit
providing backup assistance as on scene of an
event.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
721
Out of the Box
Motorola
CDISP151
Dispatching
General
Command allows a unit, or dispatcher, to type a
command for “Assist On scene” and another
unit ID. The CAD system should record the unit
as “assigned” and on scene of the other unit’s
event. The assisting unit should receive a
“Dispatch Message” from the CAD system
detailing the event information.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
722
Out of the Box
Motorola
CDISP147
Dispatching
General
RESOURCE RECOMMENDATION
723
0
Motorola
CDISP152
Dispatching
General
Unit Recommendation, Response Order
Determination:
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
724
Out of the Box
Motorola
CDISP152-1
Dispatching
General
Closest Unit Recommendation
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
725
Out of the Box
Motorola
CDISP152-2
Dispatching
General
Patrol Area (PA)
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
726
Out of the Box
Motorola
CDISP152-3
Dispatching
General
Agency-wide preferred, default, display
method.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
727
Out of the Box
Motorola
CDISP153
Dispatching
General
The dispatcher should be able to toggle
between closest unit recommendation and
Patrol Area suggestion with one function.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
728
Out of the Box
Motorola
CDISP154
Dispatching
General
By agency, preferred default determination
method should be capable of being made for
type/urgency combinations. (For example, PD
may default to static response order for most
events. However, a high priority in-progress
events will require the closest units, regardless
of static patrol area assignment.)
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
729
Out of the Box
Motorola
CDISP155
Dispatching
General
If the AVL system is not functioning, the system
should automatically rollover to Patrol Area
method.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
730
Out of the Box
Motorola
Dispatching
General
OPERATING CONDITIONS
731
0
Motorola
CDISP156
Dispatching
General
Agencies should have the ability to establish
multiple operating possibilities, and set any one
condition as the active operating condition for
dispatching purposes.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
732
Out of the Box
Page 33of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CDISP157
Dispatching
General
The response plan for events may change
depending on the operating condition. For
example, accidents occurring during a severe
storm have a different response plan than
normal operations.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
733
Out of the Box
Motorola
CDISP158
Dispatching
General
Events can be routed to different dispatch
positions depending on the operating
condition.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
734
Out of the Box
Motorola
CDISP159
Dispatching
General
Operating Condition should be capable of being
changed, by agency, with a command line
entry.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
735
Out of the Box
Motorola
CDISP160
Dispatching
General
Current Operating Condition should be capable
of being queried by users and/or should be
displayed on monitors.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
736
Out of the Box
Motorola
CDISP161
Dispatching
General
The system should be configurable to prompt
the users to consider changing operating
conditions. For example, the department may
want to base condition changes on percentage
of units that are on calls.
Mandatory
CAD
X
PremierOne does not have this functionality.
Functionality tied to response modes, and response
modes have to be configured in order to validate.
MCSO & Motorola teams agree requirement is
met out of the box per notes in Column O.
737
Cannot Meet
Motorola
Dispatching
General
CROSS DISTRICT RESPONSES
738
0
Motorola
CDISP162
Dispatching
General
The system should have the ability to set user-
definable recommendations for cross district
responses and automated messaging based on
user-definable parameters for reported
offense/incident type and geographical
proximity.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
739
Out of the Box
Motorola
CDISP163
Dispatching
General
For example, the system administrator should
be able to configure offense/incident type and
unit geographical proximity algorithms so that if
South District County units are responding to a
man with a gun near the North County District
border, and a North District Unit is within one-
half mile of the event, the system should;
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
740
Out of the Box
Motorola
CDISP164
Dispatching
General
Send an alert with event details to the Fifth
District unit's MDC (including the radio channel
they should switch to) and the Fifth District
dispatcher and,
Mandatory
CAD
X
PremierOne partially complies with the functionality as described in the requirement. Officers are
not sent an alert, but the details would be sent to the officer being dispatched to the call.
741
Out of the Box
Motorola
CDISP164-1
Dispatching
General
Inform the controlling dispatcher of the North
District unit's proximity for possible dispatch.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
742
Out of the Box
Motorola
CET001
Event Type
General
The system should provide for an agency-
configurable event type table.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
743
Out of the Box
Motorola
CET002
Event Type
General
The dispatcher or authorized user should be
able to change the event type/priority/urgency
code as required by the event. As with all
actions conducted on the proposed CAD, the
activity should also be noted in the audit log.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
744
Out of the Box
Motorola
CET003
Event Type
General
SPECIAL INSTRUCTIONS AND/OR RESPONSE
PLANS
745
0
Motorola
CET003
Event Type
General
The system should allow specific instructions to
be associated with event types.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
746
Out of the Box
Motorola
CET004
Event Type
General
Once the event type are entered the special
instructions should be available
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
747
Out of the Box
Motorola
CET005
Event Type
General
The special instructions file can be text or for a
drill down tree. In a tree format the responses
should reflect in the event history
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement. Any response to
special instructions would be added directly into the incident comments.
748
Out of the Box
Motorola
CET006
Event Type
General
The system should allow specific instructions
for event addresses.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
749
Out of the Box
Motorola
CET007
Event Type
General
The special instructions that require a response
should allow the automated inclusion of
entered answers into the event details.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
750
Out of the Box
Motorola
CET003
Event Type
General
EVENT URGENCY and EVENT PRIORITY
751
0
Motorola
CET008
Event Type
General
The urgency code should be configurable by the
system administrator.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
752
Out of the Box
Motorola
CET009
Event Type
General
The event priority is determined by the event
type and associated urgency code and
displayed as the default.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
753
Out of the Box
Motorola
CET010
Event Type
General
The user should be able to change the event
type/priority/urgency code as required by the
event. As with all actions conducted on the
proposed CAD, the activity is also noted in the
audit log.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
754
Out of the Box
Motorola
CET011
Event Type
General
The system should ensure that any change
made to the priority of an active event will
result in the appropriate changes to pending
queues and status monitors and notification to
the assigned dispatcher(s).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
755
Out of the Box
Motorola
CET003
Event Type
General
EVENT INFORMATION
756
0
Motorola
CET012
Event Type
General
The system should provide the capability to
toggle between multiple active events with a
minimum of keystrokes.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
757
Out of the Box
Page 34of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CET013
Event Type
General
The event entry form should contain the
following minimum agency-definable fields:
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
758
Out of the Box
Motorola
CET013-1
Event Type
General
Caller's Name
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
759
Out of the Box
Motorola
CET013-2
Event Type
General
Caller's street address
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
760
Out of the Box
Motorola
CET013-3
Event Type
General
Event location
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
761
Out of the Box
Motorola
CET013-4
Event Type
General
Caller's County
Mandatory
CAD
X
PremierOne does not have this functionality.
MCSO & Motorola teams agree requirement is
met out of the box.
762
Cannot Meet
Motorola
CET013-5
Event Type
General
Caller's current location (address/
intersection/commonplace/XY coordinates)
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
763
Out of the Box
Motorola
CET013-6
Event Type
General
Caller's phone number
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
764
Out of the Box
Motorola
CET013-7
Event Type
General
The phone field should display 4 separate
sections and searchable on the database by
each section or all sections combined (3 digit
area code, 3 digit exchange, 4 digit number, and
up to four digit extension, preceded by an EXT)
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
765
Out of the Box
Motorola
CET013-8
Event Type
General
Alternate Callback number
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
766
Out of the Box
Motorola
CET14
Event Type
General
The phone field should display 4 separate
sections and searchable on the database by
each section or all sections combined (3 digit
area code, 3 digit exchange, 4 digit number, and
up to four digit extension, preceded by an EXT)
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
767
Out of the Box
Motorola
CET14-1
Event Type
General
Complainant contact
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
768
Out of the Box
Motorola
CET14-2
Event Type
General
Complainant contact (yes, no or if needed)-
configurable by the System Administrator
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
769
Out of the Box
Motorola
CET14-3
Event Type
General
Call Source
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
770
Out of the Box
Motorola
CET14-4
Event Type
General
The call source (911, 7 digit, administrative line,
wireless, etc.) should be configurable by the
System Administrator
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
771
Out of the Box
Motorola
CET15
Event Type
General
Narrative/Remarks: The narrative field should
not have any limit on the number of
alphanumeric characters.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
772
Out of the Box
Motorola
CET16
Event Type
General
Narrative/Remarks: The narrative field should
allow the use of special characters
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
773
Out of the Box
Motorola
CET17
Event Type
General
Narrative/Remarks: Action Code field
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
774
Out of the Box
Motorola
CET18
Event Type
General
The Sub-form of the Event mask should contain
the following minimum agency-definable fields:
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
775
Out of the Box
Motorola
CET18-1
Event Type
General
Vehicle Description
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
776
Out of the Box
Motorola
CET18-2
Event Type
General
Suspect Description
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
777
Out of the Box
Motorola
CET18-3
Event Type
General
Article Description
Mandatory
CAD
X
PremierOne does not have this functionality.
MCSO clarified this is related to an article query, or
also tooltip to help user understand what
abbreviations to use for queries.
Motorola demonstrated article query type and also
help text to assist with article abbreviations, via tooltip
configuration by query.
MCSO & Motorola teams agree requirement is
met out of the box per notes in Column O.
778
Cannot Meet
Motorola
CET19
Event Type
General
The system should allow the user to perform an
automatic check of local, state, and national
databases upon call taker entry of key data
fields such as tag number, date of birth, name,
etc.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
779
Out of the Box
Motorola
CET20
Event Type
General
If the event location is within a gated
community the system needs to access and
display the gate codes for the dispatcher and
for the officer(s) responding. Vendors are to
explain in detail how they will meet this
requirement.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
780
Out of the Box
Motorola
Event Type
General
DETAILS TO FOLLOW
781
0
Motorola
CET21
Event Type
General
The system should allow the user to route the
event to a dispatcher with the minimum
required fields and invoke a system-definable
indicator to the dispatcher that there is more
information to follow. After this action is
invoked, a supplemental form should
automatically appear on the screen.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
782
Out of the Box
Motorola
CET22
Event Type
General
The details to follow function should serve as
supplemental form and allow users to continue
to add narrative information to the event. This
process should only add and not change data.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
783
Out of the Box
Motorola
Event Type
General
ADVISED EVENTS
784
0
Motorola
CET23
Event Type
General
The system should provide the ability to record
information from citizens about particular
situations or events that do not require the
dispatching of any public safety resources.
These incidents create event records that
should be recorded and retrievable from the
system/event history files for later access and
information analysis.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
785
Out of the Box
Page 35of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CET24
Event Type
General
Advised events should have the capability to be
routed to pre-defined workstations or groups.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
786
Out of the Box
Motorola
CET25
Event Type
General
An event type should be capable of being pre-
determined as an advised event, with specific
notification/routing characteristics.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
787
Out of the Box
Motorola
CET26
Event Type
General
During event entry, the user should have the
ability of designating any event as an advised
event.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
788
Out of the Box
Motorola
CET27
Event Type
General
Advised events should be capable of creating
agency definable notifications.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
789
Out of the Box
Motorola
Event Type
General
DIRECTED FIELD EVENT
790
0
Motorola
CET28
Event Type
General
Users should be able to enter an event that will
not go to dispatch but will assign a unit and
disposition and close the event upon entry with
the user designated disposition.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
791
Out of the Box
Motorola
CET29
Event Type
General
The directed field event should be included in
the location history of an address
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
792
Out of the Box
Motorola
CET30
Event Type
General
Directed patrol events should be associated
with an employee ID. If the EIN is not found to
be logged on upon creation of the event the
system should log the ID on and assign the
paper then log the unit off. If the unit is found
logged on the event should be added to their
unit history and the unit will remain logged on.
Mandatory
CAD
X
PremierOne complies with most of the functionality described. The dispatcher would have to
manually log the unit off.
793
Out of the Box
Motorola
CET31
Event Type
General
The directed patrol event identifier should be
clear in the unit history to differentiate it from
normal events
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
794
Out of the Box
Motorola
Event Type
General
CATCH UP
795
0
Motorola
CET32
Event Type
General
The system should provide the ability to
continue event entry, processing, and dispatch
operations as long as power is available to the
workstations. The vendor should describe their
system's method for accomplishing this
functionality.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement. Calltaker/Dispatcher
workstations can work offline similar to the way our Mobile units operate in the field when
connection is lost to the server.
796
Out of the Box
Motorola
CET33
Event Type
General
In the alternative, the proposed application
should allow any authorized user to add events
after they have already occurred. (Catch-up
Mode)
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
797
Out of the Box
Motorola
CET34
Event Type
General
The method for entering after-the-fact events
should not vary from the normal event entry
format although additional narrative and event
information should be required.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
798
Out of the Box
Motorola
CET35
Event Type
General
The system should enable the user to enter
event and unit details on the same form.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
799
Out of the Box
Motorola
CET36
Event Type
General
The system should support "catch-up" entry of
event data from full access CAD workstations
for at least the following situations:
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
800
Out of the Box
Motorola
CET36-1
Event Type
General
An event that was active at the time the system
failed
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
801
Out of the Box
Motorola
CET36-2
Event Type
General
An event that was created and then closed
while the system was inoperable due to a
system failure
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
802
Out of the Box
Motorola
CET36-3
Event Type
General
An event that was created during a system
failure and is still active when the system is
restored.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
803
Out of the Box
Motorola
CET37
Event Type
General
The event entry mask for catch-up events
should minimally contain the following user-
defined fields in which to enter the following
information:
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
804
Out of the Box
Motorola
CET37-1
Event Type
General
The EIN and workstation position of the person
receiving the call, and the EIN and workstation
position of the person who enters the event.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
805
Out of the Box
Motorola
CET37-2
Event Type
General
Units assigned
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
806
Out of the Box
Motorola
CET37-3
Event Type
General
Status changes
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
807
Out of the Box
Motorola
CET37-4
Event Type
General
Dispositions
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
808
Out of the Box
Motorola
CET37-5
Event Type
General
All times associated with the event, and
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
809
Out of the Box
Motorola
CET37-6
Event Type
General
All times associated with the units
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
810
Out of the Box
Motorola
CET37-7
Event Type
General
Any other necessary user-defined fields.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
811
Out of the Box
Motorola
CET38
Event Type
General
The system should not generate unit
recommendations for catch-up events.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
812
Out of the Box
Motorola
CET39
Event Type
General
The system should clearly indicate in the event
record that the information was entered after
the fact.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
813
Out of the Box
Motorola
CET40
Event Type
General
The system should allow the user to generate
case numbers for events that may have
occurred on a previous date.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
814
Out of the Box
Page 36of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CET41
Event Type
General
The system should have the ability to process
both real-time and catch up events at the same
workstation at the same time.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
815
Out of the Box
Motorola
CET42
Event Type
General
The system should have the ability to enter,
search for, and link multi-agency events that
were entered by different users after the
system was restored.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
816
Out of the Box
Motorola
Event Type
General
SCHEDULED EVENT
817
0
Motorola
CET43
Event Type
General
The system should allow a user to schedule an
event at a later time, date, by designator, EIN,
etc. (Scheduled Event).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
818
Out of the Box
Motorola
CET44
Event Type
General
The system should allow scheduled events to
be scheduled to occur on a recurring basis.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
819
Out of the Box
Motorola
CET45
Event Type
General
MCSO plans to use this capability to schedule
individual officers to tasks like attending Court.
Please explain how this feature, if available, can
be used for individual officer scheduling. If it
cannot be used for this purpose, please offer an
alternative. An officer may notify
Communications that they are unavailable to
take calls for a period of time during their shift.
Communications needs a way making a note of
this situation to avoid trying to dispatch the
officer when unavailable. This capability needs
to be in addition to the unit status being set.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement. The system enables
officials to maintain situational awareness of all scheduled events. Users can set events like court
appearances, work releases, and other activities to recur daily, weekly, monthly, or annually. They
can also partition events by agency as appropriate. The module’s event viewer provides the time,
event, inmate name, and other details that may be important for security purposes. Additionally,
users can create reminders that show approaching or past-due events. The software allows users
to snooze, dismiss, or open event details at any time.
820
Out of the Box
Motorola
Event Type
General
DUPLICATE CALL PROCESS
821
0
Motorola
CET46
Event Type
General
The duplicate event detection process should
be configurable by the System Administrator to
detect events irrespective of agency source.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
822
Out of the Box
Motorola
CET47
Event Type
General
Duplicate event detection should be performed
on all events entered into the system.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
823
Out of the Box
Motorola
CET48
Event Type
General
The system should notify the user of all possible
duplicate events based on geographical
proximity, event type and/or other application
configurable parameters as defined during the
design of the system and system administrator
configuration.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
824
Out of the Box
Motorola
CET49
Event Type
General
A summary line of user definable data for each
possible duplicate event should be displayed on
the user's workstation.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
825
Out of the Box
Motorola
CET50
Event Type
General
If a duplicate event is detected, the prior event
information should be displayed for review
upon request, before entering the current
event.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
826
Out of the Box
Motorola
CET51
Event Type
General
During event entry, the user should be notified
of any active or recently closed events near the
one being entered based on user-defined
parameters.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
827
Out of the Box
Motorola
CET52
Event Type
General
At a minimum, the system should provide the
user with the following details about events
which have been flagged as potential duplicate
events:
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
828
Out of the Box
Motorola
CET52-1
Event Type
General
The exact location of the event
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
829
Out of the Box
Motorola
CET52-2
Event Type
General
The type of event
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
830
Out of the Box
Motorola
CET52-3
Event Type
General
The status of the event
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
831
Out of the Box
Motorola
CET52-4
Event Type
General
The time the event was initiated
Mandatory
CAD
X
PremierOne does not have this functionality.
Way to check duplicate calls where multiple call takers
are simultaneous entering the same call?
Motorola explained "Both verification & submission"
service settings provides this functionality, to prevent
duplicate call entry.
MCSO & Motorola teams agree requirement is
met out of the box per notes in Column O.
832
Cannot Meet
Motorola
CET52-5
Event Type
General
The unit(s) assigned, if any.
Mandatory
CAD
X
PremierOne does not have this functionality.
MCSO & Motorola teams agree requirement is
met out of the box.
833
Cannot Meet
Motorola
CET52-6
Event Type
General
Event number
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
834
Out of the Box
Motorola
CET53
Event Type
General
The system should allow the user to create a
new event if it is determined that the events
are not duplicates, or exit back to the event
entry form.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
835
Out of the Box
Motorola
CET54
Event Type
General
The system should allow the user to select one
of the possible duplicate events from the
duplicate event check screen.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
836
Out of the Box
Motorola
CET55
Event Type
General
If the user selects one of the events, the system
should add all the information that was entered
on the event form (caller's name, address,
phone, and comments, etc.) as supplemental
comments to the selected event's audit trail.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
837
Out of the Box
Page 37of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CET56
Event Type
General
The system should provide the user the option
of continuing to enter the event as a new
event, appending the event to the earlier event
as a supplement, linking the event as separate
but related, designating the event as a
duplicate, or terminating the entry process.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
838
Out of the Box
Motorola
CET57
Event Type
General
When appending an existing event the system
should provide the ability to automatically
upgrade the event type, priority, and/or
urgency. This capability should be agency
configurable.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
839
Out of the Box
Motorola
CET58
Event Type
General
The system should allow the user to identify
two or more events as being duplicates.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
840
Out of the Box
Motorola
CET59
Event Type
General
The system should automatically cross
reference all related events and close all but
the user defined active call.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
841
Out of the Box
Motorola
CET60
Event Type
General
Once a call has been duped and closed the
event should carry a disposition of "duplicate"
and should have the "active" event number in
its history.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
842
Out of the Box
Motorola
CET61
Event Type
General
In addition to the capabilities to identify
duplicate calls described above, MCSO wants to
be able to view a snap shot of the most recent
incoming 911 calls, per workstation, at any
point in time upon request.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement. Motorola has a
snapshot report that shows the current state of incidents and units at a given date and time for
the entire system. It is not broken out by workstation. A report could be written to break the
information out by workstation.
843
Out of the Box
Motorola
Event Type
General
EVENT REDIRECT
844
0
Motorola
CET62
Event Type
General
The system should allow agency-definable
routing of events.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
845
Out of the Box
Motorola
CET63
Event Type
General
Once an event has been initiated the system
should be able to, upon configuration,
automatically route the event to the correct
dispatcher(s) based on the agency, location,
and dispatch group.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
846
Out of the Box
Motorola
CET64
Event Type
General
The system should allow the user to “override”
the address validation process by manually
routing the call to the correct dispatcher.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
847
Out of the Box
Motorola
CET65
Event Type
General
The system should log each occurrence of an
address “override” and provide a means of
reporting such occurrences to System
Administrator.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
848
Out of the Box
Motorola
CET66
Event Type
General
An agency-definable audible tone and/or visual
message should notify the dispatcher that a
new event has been sent to their queue.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
849
Out of the Box
Motorola
CET67
Event Type
General
The system should place the event on the
dispatcher's queue of events awaiting dispatch
in priority order and, within a priority, by time
received.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
850
Out of the Box
Motorola
CET68
Event Type
General
When an event is initiated, the event
information should be visually displayed to the
appropriate dispatcher(s) in the pending events
queue.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
851
Out of the Box
Motorola
CET69
Event Type
General
Events should be capable of being assigned to a
dispatcher as defined by the agency via any one
of the following:
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
852
Out of the Box
Motorola
CET69-1
Event Type
General
Map Driven "special/temporary" geographical
area/polygon
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
853
Out of the Box
Motorola
CET69-2
Event Type
General
Event Type
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
854
Out of the Box
Motorola
CET69-3
Event Type
General
Primary Geographical area (response
area/Patrol area)
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
855
Out of the Box
Motorola
CET69-4
Event Type
General
Pre-defined talk group (e.g., geographic
location).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
856
Out of the Box
Motorola
CET70
Event Type
General
The hierarchy of assignment should be
definable by Agency.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
857
Out of the Box
Motorola
Event Type
General
SUPPLEMENTING EVENT INFORMATION/EVENT
CHANGES
858
0
Motorola
CET71
Event Type
General
The system should enable the user, when
supplementing information into linked events,
to designate one or more events in which the
supplemental information should appear.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
859
Out of the Box
Motorola
CET72
Event Type
General
The system should support ease of entry for
additional event information and changes to
event information.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
860
Out of the Box
Motorola
CET73
Event Type
General
The user should be able to bring up an event
form either in relation to the event number or a
unit assigned to the event.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
861
Out of the Box
Motorola
CET74
Event Type
General
The system should provide agency-definable
visual and audible alerts to notify field
units/dispatchers of event changes and
additional information.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
862
Out of the Box
Page 38of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CET75
Event Type
General
The system should allow users to supplement
and/or change active events, and all changes
should be tracked in the call history.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
863
Out of the Box
Motorola
CET76
Event Type
General
The system should allow a user to update any
field except application-generated times and
dates, operator ID, ANI/ALI information, and
CAD position.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
864
Out of the Box
Motorola
CET77
Event Type
General
All changes and supplemental information
should be documented in the event history and
the original information should be retained.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
865
Out of the Box
Motorola
CET78
Event Type
General
The system should provide an event
update/change mask.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
866
Out of the Box
Motorola
CET79
Event Type
General
The system should have the ability for a user to
update or change a unit's most recent event by
using the unit ID of the unit or any unit that is
currently assigned.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
867
Out of the Box
Motorola
CET80
Event Type
General
The system should require confirmation from
the user when attempting to update any field in
a closed event.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
868
Out of the Box
Motorola
CET81
Event Type
General
Whenever an active event record is updated
the system, the system should by default,
display a notification of the event update at
each position logged on to monitor (training
mode), or control the area in which the
updated event is occurring.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
869
Out of the Box
Motorola
CET82
Event Type
General
The user making the update to the record
should receive an agency-definable
acknowledgment that the update was
processed.
Mandatory
CAD
X
PremierOne complies with the notification, but that notification is not agency definable.
870
Out of the Box
Motorola
CET83
Event Type
General
Every transaction related to an event, including
inquiries and responses, should be
automatically stamped with the date and time
of the transaction, the responsible operator’s
ID and the console ID, and becomes a
permanent part of the event history. These
audit records should be added to the event
history in chronological order and provide a
complete historical audit of all event activity
such as comments, unit status changes, license
plate information, field updates, etc. If the
entry replaces existing information in the event
record, the old information, with the
appropriate date, time, operator, and console
stamps, is stored as a comment in the event
history. The audit information is retrievable in
both summary and detailed formats when
incident information is displayed and may be
printed.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
871
Out of the Box
Motorola
CET84
Event Type
General
A permanent audit trail should be maintained
for all information recorded with an event.
Once recorded, incident history should not be
modified or deleted. If corrections are
necessary the records should be supplemented.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
872
Out of the Box
Motorola
CET85
Event Type
General
The system should allow users to supplement
and or change active events and closed events;
that user should be able to update any field of a
closed event without having re-open the event.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
873
Out of the Box
Motorola
Event Type
General
REOPENING A CLOSED EVENT
874
0
Motorola
CET86
Event Type
General
Users should be able to re-open an event that
has been closed.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
875
Out of the Box
Motorola
CET87
Event Type
General
The event should require a comment as to why
the event is being opened.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
876
Out of the Box
Motorola
CET88
Event Type
General
The call should go to the appropriate dispatcher
as a pending or waiting event.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
877
Out of the Box
Motorola
CET89
Event Type
General
The re-opened event should contain the
date/time, employee ID and position ID of the
workstation opening the event.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
878
Out of the Box
Motorola
CET90
Event Type
General
Once an event is re-opened it should act as any
other active event.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
879
Out of the Box
Page 39of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CET91
Event Type
General
Once a reopened event is dispatched to an
MDC it should display a "reopened status"
indicator to the user.
Mandatory
CAD
X
PremierOne does not have this functionality.
Motorola demonstrated that re-opening a call will
change to a "Pending" status. Closed calls can be
updated, remarks added will still be closed. Adding
comments while closed does not change the time
stamp of when closed.
There is a configuration to allow updating of closed
calls.
When re-opened a new incident number is not
created.
MCSO question - can you use command line and get a
clue that incident was re-opened? Motorola response -
On form itself does not indicate but will note in history
trail.
MCSO & Motorola teams agree requirement is
met out of the box per notes in Column O.
880
Cannot Meet
Motorola
CET92
Event Type
General
The system should provide a command that will
close an event without canceling it, when no
units are required to be assigned.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
881
Out of the Box
Motorola
CET93
Event Type
General
The system should provide a command for re-
opening or re-activating an event that has
previously been closed.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
882
Out of the Box
Motorola
CET94
Event Type
General
When a closed event is reopened the system
should record the following minimum
information:
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
883
Out of the Box
Motorola
CET94-1
Event Type
General
User ID, Workstation Number, Time and Date
that the event was re-opened, and provide a
narrative field for the users to explain why the
event was re-opened.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
884
Out of the Box
Motorola
CET94-2
Event Type
General
The original event retains the original date and
time of entry, while adding the re-opened date
and time to the original event.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
885
Out of the Box
Motorola
CET95
Event Type
General
Any changes made to the event while reopened
should appear in the event record.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
886
Out of the Box
Motorola
CET96
Event Type
General
Prior to closing a reopened event, the
application should require an authorized user
to validate or provide a disposition if necessary.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
887
Out of the Box
Motorola
CET97
Event Type
General
Cancelled events should be capable of being
reopened (as defined by the user) or changed.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
888
Out of the Box
Motorola
CET98
Event Type
General
If an event was closed by cancellation without a
unit being assigned to the event and it is
reopened with a unit being assigned, the event
should become part of the unit and event
history.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
889
Out of the Box
Motorola
Event Type
General
CANCELLATION REQUESTS
890
0
Motorola
CET99
Event Type
General
The user should have the ability to request the
cancellation of an event.
Mandatory
CAD
X
PremierOne doesn't have this functionality. Messaging can be used to notify users of a request to
cancel a call or notify users a call has been cancelled.
Motorola - displayed example of alarm call, can right
click and choose cancellation, can enter from
command line. MCSO feedback that two incidents to
cancel will not work. Motorola demonstrated
configured automated disposition for command line
entry.
MCSO & Motorola teams agree requirement is
met out of the box per notes in Column O.
891
Cannot Meet
Motorola
CET100
Event Type
General
The system should provide the capability for
the dispatcher to enter comments into the
canceled event history.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
892
Out of the Box
Motorola
CET101
Event Type
General
The request notification should go to the
controlling dispatcher, be displayed in the
event history, and go to any units that have
been dispatched.
Mandatory
CAD
X
PremierOne doesn't have this functionality. Messaging can be used to notify users of a request to
cancel a call or notify users a call has been cancelled.
This requirement was demonstrated as part of CET99. MCSO & Motorola teams agree requirement is
met out of the box per notes in Column O.
893
Cannot Meet
Motorola
CET102
Event Type
General
Only a calltaker or dispatcher should have the
ability to cancel an event.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
894
Out of the Box
Motorola
CET103
Event Type
General
If a calltaker is cancelling a call that has just
been sent to a dispatcher, the dispatcher must
receive a message informing of the
cancellation.
Mandatory
CAD
X
PremierOne doesn't have this functionality. Messaging can be used to notify users of a request to
cancel a call or notify users a call has been cancelled.
This requirement was demonstrated as part of CET99. MCSO & Motorola teams agree requirement is
met out of the box per notes in Column O.
895
Cannot Meet
Motorola
Event Type
General
MEMO
896
0
Motorola
CET104
Event Type
General
The system should provide the capability of
recording miscellaneous information to a unit
and/or event history on active and inactive
events.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
897
Out of the Box
Motorola
CET105
Event Type
General
Memos to specified unit IDs should be recorded
in the unit history. If the identified unit is
assigned to an event, the information should
also be recorded to the event history.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
898
Out of the Box
Motorola
CET106
Event Type
General
Memos to a specific event should be
accomplished by specifying an event number or
by default to the user's active event
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
899
Out of the Box
Motorola
Event Type
General
HIGH PRIORITY NOTIFICATION
900
0
Motorola
CET107
Event Type
General
The proposed system should notify the
dispatcher visually that a high priority event has
been initiated.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
901
Out of the Box
Page 40of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CET108
Event Type
General
All high priority events entered into the system
should have the ability to generate an agency-
defined notification to designated
workstation/persons/groups as assigned by the
System Administrator or supervisor (For
example, on a homicide, MCSO Command Staff,
and PIO are notified).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
902
Out of the Box
Motorola
CET109
Event Type
General
An unlimited number of notifications should be
allowed for any event type as determined by
the System Administrator.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
903
Out of the Box
Motorola
CET110
Event Type
General
Notifications should be capable of being
triggered by Event type, LOI, Specific addresses,
etc.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
904
Out of the Box
Motorola
CET111
Event Type
General
The individuals/groups to be notified should
also receive an alert at their MDC/Workstation
if they are logged on to CAD.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
905
Out of the Box
Motorola
CET112
Event Type
General
The system should be capable of sending
notifications to any wireless communication
device.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
906
Out of the Box
Motorola
CET113
Event Type
General
Personnel receiving notifications via CAD
messaging for command staff who
acknowledge the message should have the
acknowledgment memoed into the event
history.
Mandatory
CAD
X
PremierOne does not have this functionality. Users have the ability to manually reference a
message to an event.
Just outbound data, no acknowledgement capability.
In handheld application can write comments into the
events.
MCSO & Motorola teams agree requirement is
met out of the box per notes in Column O.
907
Cannot Meet
Motorola
CET114
Event Type
General
The system should have the ability to provide
MDC equipped units with internally and
externally initiated Amber Alert information
(including photos).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
908
Out of the Box
Motorola
CET115
Event Type
General
The system administrator should be able to
control who has the capability to send and
receive high priority notifications.
Mandatory
CAD
X
PremierOne does not have this functionality. Users have the ability to manually reference a
message to an event.
MCSO team stated this is not required to be met.
909
Cannot Meet
Motorola
SRRT001
Supplemental
Resource
Request and
Tracking
Request
Supplemental
Resource
The system shall be able to store, and easily
retrieve, a file for standardized and ad hoc
supplemental resources that may be recalled
and requested as needed for services not
available from the public safety agencies.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
910
Out of the Box
Motorola
SRRT002
Supplemental
Resource
Request and
Tracking
Request
Supplemental
Resource
The system shall make request and “dispatch”
of said resources on the basis of the unique
type of service needed, the geographic
proximity to the site of the needed service, or a
rotation of the unique service providers of a
given type—or, a combination of methods.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
911
Out of the Box
Motorola
SRRT003
Supplemental
Resource
Request and
Tracking
Request
Supplemental
Resource
The system shall allow for agency-configurable
non-agency units to be recommended, such as
the closest towing company recommendation
when a unit is dispatched to an accident event
type. The recommendation will take into
account the rotation of towing companies.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
912
Out of the Box
Motorola
SRRT004
Supplemental
Resource
Request and
Tracking
Request
Supplemental
Resource Rotation
List
The system shall store, and provide for easy
retrieval, a list of authorized providers of
unique or supplemental supplies or services.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
913
Out of the Box
Motorola
SRRT005
Supplemental
Resource
Request and
Tracking
Request
Supplemental
Resource Rotation
List
The system shall provide multiple sources of
contact for each authorized vendor.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
914
Out of the Box
Motorola
SRRT006
Supplemental
Resource
Request and
Tracking
Request
Supplemental
Resource Rotation
List
The system shall be able to display the list of
authorized service providers based upon
geographical proximity to the site of need, by
rotation, or by agency preference based upon
contractual agreement.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
915
Out of the Box
Motorola
SRRT007
Supplemental
Resource
Request and
Tracking
Notify Supplemental
Resource Service
The system shall provide the ability to contact
the supplemental resource; and,
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
916
Out of the Box
Motorola
SRRT008
Supplemental
Resource
Request and
Tracking
Notify Supplemental
Resource Service
The system shall provide dispatch information
by the dispatcher about the incident to which
the resource is requested to respond.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
917
Out of the Box
Motorola
SRRT009
Supplemental
Resource
Request and
Tracking
Notify Supplemental
Resource Service
The system shall provide the ability to record
the availability of the entity to provide its
services.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
918
Out of the Box
Motorola
SRRT010
Supplemental
Resource
Request and
Tracking
Notify Supplemental
Resource Service
A supplemental service that cannot be
contacted or informs the agency of its inability
to respond within a prescribed time The system
shall be considered unavailable to provide the
service.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
919
Out of the Box
Page 41of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
SRRT011
Supplemental
Resource
Request and
Tracking
Notify Supplemental
Resource Service
System shall provide the ability to select a
supplemental resource.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
920
Out of the Box
Motorola
SRRT012
Supplemental
Resource
Request and
Tracking
Notify Supplemental
Resource Service
If a resource is unavailable, or unable to
respond in a reasonable time frame, then the
user of the system shall contact the next listed
resource until one is found that is available
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
921
Out of the Box
Motorola
SRRT013
Supplemental
Resource
Request and
Tracking
Notify Supplemental
Resource Service
The system shall provide the ability to create a
record of the supplemental service request.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
922
Out of the Box
Motorola
SRRT014
Supplemental
Resource
Request and
Tracking
Notify Supplemental
Resource Service
The system shall accommodate selection from
the provided list either at random, by
geographic proximity to the site of need, or by
rotation.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
923
Out of the Box
Motorola
SRRT015
Supplemental
Resource
Request and
Tracking
Notify Supplemental
Resource Service
The system shall trigger the next provider in the
rotation, when selected by rotation and upon
creation of the record
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
924
Out of the Box
Motorola
SRRT016
Supplemental
Resource
Request and
Tracking
Notify Supplemental
Resource Service
The system shall process the rotation
regardless of the requested resource’s ability to
respond.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
925
Out of the Box
Motorola
SRRT017
Supplemental
Resource
Request and
Tracking
Notify Supplemental
Resource Service
The system shall allow for a provider in a
rotation (i.e. tow trucks, callouts, etc.) to be
placed back into any spot in the rotation.
Example: If a tow truck is canceled prior to
arrival, the dispatcher should be able to place
that two truck back into the #1 spot for
rotation.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
926
Out of the Box
Motorola
IDP001
Incident
Disposition
Determine Incident/
Event Status
The system shall provide the ability to change
the event status as the situation evolves or a
resolution is achieved.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
927
Out of the Box
Motorola
IDP002
Incident
Disposition
Determine Incident/
Event Status
The system shall allow the field user to enter
one or more event dispositions.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
928
Out of the Box
Motorola
IDP003
Incident
Disposition
Determine Incident/
Event Status
The system shall allow the field user to update
the CFS event in CAD and make that data
available to the RMS.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
929
Out of the Box
Motorola
IDP004
Incident
Disposition
Utilize Incident
Management
The system shall have the ability to dynamically
update the CFS event with notations, updates,
status changes, and notifications.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
930
Out of the Box
Motorola
IDP005
Incident
Disposition
Utilize Incident
Management
The system shall make the updated CFS data
available for transfer to an RMS.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
931
Out of the Box
Motorola
IDP006
Incident
Disposition
Determine Record
Functionality
The system shall provide the ability to
automatically transfer incident/event data
relevant to external RMS or reporting systems.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
932
Out of the Box
Motorola
IDP007
Incident
Disposition
Determine Record
Functionality
The system shall be able to determine, based
upon incident type and/or disposition, whether
an agency report is required.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
933
Out of the Box
Motorola
IDP008
Incident
Disposition
Determine Record
Functionality
The system shall accommodate either a push or
pull of incident/event data from/to the RMS.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
934
Out of the Box
Motorola
IDP009
Incident
Disposition
Record Dispo
The system shall provide for the CFS event to
contain the disposition of the incident.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
935
Out of the Box
Motorola
IDP010
Incident
Disposition
Record Dispo
The system shall provide for narrative to be
added giving detail to the disposition.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
936
Out of the Box
Motorola
IDP011
Incident
Disposition
Send Data to
Records
Management
System
The system shall provide for the CFS event to
contain the disposition of the incident.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
937
Out of the Box
Motorola
IDP012
Incident
Disposition
Send Data to
Records
Management
System
The system shall provide for narrative to be
added giving detail to the disposition.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
938
Out of the Box
Motorola
IDP013
Incident
Disposition
Assign Agency-
Specific Report
Numbers
The system shall assign an agency-specific
report (i.e. case) number—if a report is
required, and if required by agency policy—in
addition to the CAD incident/event number,
before the CFS event data is transferred to the
RMS.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
939
Out of the Box
Motorola
IDP014
Incident
Disposition
Assign Agency-
Specific Report
Numbers
The system shall allow for both the CAD CFS
Event Number and the Agency Report Numbers
to be fully configurable (e.g. “1 to n,”
“mmddyyxxxx,” “mmddyyhhmmssxxx,”
“FY12xxxxxx,” “2012-mmdd-
xxxxx","MC23xxxxxx","IR123456”).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
940
Out of the Box
Motorola
CSADM001
CAD System
Administration
Geofile Maintenance The system shall validate all locations entered
into or processed by the CAD system against
the CAD system’s geofile.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
941
Out of the Box
Page 42of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CSADM002
CAD System
Administration
Geofile Maintenance The system shall provide an interactive, GUI-
based address matching tool for assisting users
to determine the location of incidents that do
not have an exact geofile match for their
initially-entered location.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
942
Out of the Box
Motorola
CSADM003
CAD System
Administration
Geofile Maintenance The system shall be capable of determining X,Y
coordinate values that represent the location of
incidents whose locations have been validated.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
943
Out of the Box
Motorola
CSADM004
CAD System
Administration
Geofile Maintenance The system shall be capable of displaying
coordinates anywhere on the map with mouse
over.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
944
Out of the Box
Motorola
CSADM005
CAD System
Administration
Geofile Maintenance The system shall support coordinate-based
operations including X,Y, Lat/Lon, and USNG.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
945
Out of the Box
Motorola
CSADM006
CAD System
Administration
Geofile Maintenance The system shall make possible integration of
the CAD system’s geofile with Global
Positioning Satellite (GPS), AVL, and Automatic
Person Location (APL) systems.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
946
Out of the Box
Motorola
CSADM007
CAD System
Administration
Geofile Maintenance The system shall support X,Y coordinate-based
geographic searches for such things as nearby
hazardous materials, duplicate incidents, and
premises information at or near an incident’s
location.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
947
Out of the Box
Motorola
CSADM008
CAD System
Administration
Geofile Maintenance The system shall be capable of importing
geographic boundary information (e.g. station
boundaries, jurisdictional boundaries, reporting
districts, response zones, neighborhoods,
precincts) from GIS and other geographic data
sources.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
948
Out of the Box
Motorola
CSADM009
CAD System
Administration
Geofile Maintenance The system shall be capable of importing
topologically-structured street networks and
other linear features (e.g. rivers, streams, utility
right of ways, bus routes) from GIS and other
geographic data sources.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
949
Out of the Box
Motorola
CSADM010
CAD System
Administration
Geofile Maintenance The system shall be capable of importing point
data (e.g. landmarks, parcel address points,
business locations, retail store address points,
fire hydrants) from GIS and other geographic
data sources.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
950
Out of the Box
Motorola
CSADM011
CAD System
Administration
Geofile Maintenance The system shall be capable of importing other
types of geographic data (e.g. park boundaries,
rectified aerial photography, trailer parks,
apartment complexes) from GIS and other
geographic data sources.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
951
Out of the Box
Motorola
CSADM012
CAD System
Administration
Geofile Maintenance The system shall include location databases
such as hazards, general premises information,
street closures, and other user-definable GIS
type data.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
952
Out of the Box
Motorola
CSADM013
CAD System
Administration
Geofile Maintenance The system shall support parcel-level GIS
information and use this information for
address/location validation.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
953
Out of the Box
Motorola
CSADM014
CAD System
Administration
Geofile Maintenance The system shall support multiple layers of
information; for example, the storage of
building footprints, aerial photographs and
other images (i.e. pictures of specific buildings)
that are associated with specific areas and
addresses.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
954
Out of the Box
Motorola
CSADM015
CAD System
Administration
Geofile Maintenance The system shall maintain the CAD system’s
geofile while the system is live and operational.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
955
Out of the Box
Motorola
CSADM016
CAD System
Administration
Geofile Maintenance The system shall support boundary assignments
(i.e. determining the response zone and
jurisdiction for each incident) in real time by
processing the incident’s X,Y coordinates
against the RCL and/or address point file, and
the appropriate boundary files.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
956
Out of the Box
Motorola
CSADM017
CAD System
Administration
Geofile Maintenance The system shall support duplicate incident
checks based upon the location of the incident.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
957
Out of the Box
Motorola
CSADM018
CAD System
Administration
Geofile Maintenance All incidents located within the CAD system’s
duplicate incident search radius The system
shall be checked as potential duplicates.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
958
Out of the Box
Motorola
CSADM019
CAD System
Administration
Geofile Maintenance The system shall should meet i3 standards and
functions in order to comply with NG9-1-1
requirements.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
959
Out of the Box
Motorola
CSADM020
CAD System
Administration
Geofile Maintenance The system shall include interactive tools for
validating the accuracy and completeness of
the geofile.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
960
Out of the Box
Page 43of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CSADM021
CAD System
Administration
Geofile Maintenance The system shall be able to support different
search distance criteria for different types of
incident situations and hazards (e.g. a search
radius of 300 feet will be used for hazardous
conditions, and a search radius of 1,320 feet
will be used to identify potentially duplicate
incidents).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
961
Out of the Box
Motorola
CSADM022
CAD System
Administration
Geofile Maintenance CAD system administrators The system shall be
able to modify these search distance
parameters.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
962
Out of the Box
Motorola
CSADM023
CAD System
Administration
Geofile Maintenance CAD users The system shall have the ability to
select the unit of measurement necessary (feet
versus meters).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
963
Out of the Box
Motorola
CSADM024
CAD System
Administration
Geofile Maintenance The system shall generate an audible and/or
visual alert when any potential duplicate
incidents are identified.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
964
Out of the Box
Motorola
CSADM025
CAD System
Administration
Geofile Maintenance The system shall include the capability for
manually editing and entering any geographic
data required by, or imported into, the
system’s GIS (given the appropriate user
permissions).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
965
Out of the Box
Motorola
CSADM026
CAD System
Administration
Security
The system shall employ data security
measures that are compliant with applicable
state and federal security standards.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
966
Out of the Box
Motorola
CSADM027
CAD System
Administration
Security
The system shall employ data encryption that
meets CJIS security policy standards for any
exchange or transmittal of CAD data between
remote devices and CAD system servers.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
967
Out of the Box
Motorola
CSADM028
CAD System
Administration
Security
The system shall provide appropriate
safeguards to ensure that only authorized
devices and users are allowed access to the
CAD system and stored information.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
968
Out of the Box
Motorola
CSADM029
CAD System
Administration
Security
The system shall provide a security profile to
control individual user access to the various
modules, applications, functions, features, and
data available within the CAD system.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
969
Out of the Box
Motorola
CSADM030
CAD System
Administration
Security
The system shall provide security to ensure that
fire and EMS personnel do not have access to
law incidents when CJIS data is restricted to
only law enforcement user access.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
970
Out of the Box
Motorola
CSADM031
CAD System
Administration
Security
The system shall meet CJIS Security Policy
requirements.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
971
Out of the Box
Motorola
CSADM032
CAD System
Administration
Security
The system shall validate each user’s
credentials through a mandatory logon process
before being granted access to any functions or
data available within the CAD system.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
972
Out of the Box
Motorola
CSADM033
CAD System
Administration
Security
The system shall enable a user replacing an
existing user to quickly log off the existing user
and logon without the need to exit from CAD or
re-start the CAD application (i.e. when two-
factor authentication does not apply.)
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
973
Out of the Box
Motorola
CSADM034
CAD System
Administration
Security
The system shall enable system administrators
to create and maintain a centralized and
indexed database containing information about
each system user, including their unique user
ID, password, contact information, and security
profile.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
974
Out of the Box
Motorola
CSADM035
CAD System
Administration
Security
The system shall enable system administrators
to define individual user access privileges and
assign them to security groups.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
975
Out of the Box
Motorola
CSADM036
CAD System
Administration
Security
The system shall provide a method for
authorized users to reset a user’s password.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
976
Out of the Box
Motorola
CSADM037
CAD System
Administration
Security
The system shall associate the user ID and
workstation ID with all CAD system
transactions, including data entry and report
generation.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
977
Out of the Box
Motorola
CSADM038
CAD System
Administration
Security
The system shall limit access to the centralized
user security database to only specifically
authorized users.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
978
Out of the Box
Motorola
CSADM039
CAD System
Administration
Security
The system shall establish security profiles that
are assigned to individual users or user groups
based on personnel classifications (e.g. call
taker, dispatcher, system administrator,
supervisor).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
979
Out of the Box
Motorola
CSADM040
CAD System
Administration
Security
The system shall prohibit deletion of any data
entered into a CFS event.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
980
Out of the Box
Page 44of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CSADM041
CAD System
Administration
Security
The system shall provide application and
module level security that enables certain users
to access specific CAD system functions and
application modules, while keeping other users
from accessing these same functions and
modules.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
981
Out of the Box
Motorola
CSADM042
CAD System
Administration
Security
The system shall provide data entry form
security that enables certain users to access
specific data entry forms, while keeping other
users from accessing these same data entry
forms.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
982
Out of the Box
Motorola
CSADM043
CAD System
Administration
Security
The system shall provide record type security
that enables certain users to access specific
CAD system record types, while keeping other
users from accessing these same record types.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
983
Out of the Box
Motorola
CSADM044
CAD System
Administration
Security
The system shall provide transaction level
security that enables certain users to access
specific transaction types (e.g. criminal history
queries to NCIC), while keeping other users
from accessing these same transaction types.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
984
Out of the Box
Motorola
CSADM045
CAD System
Administration
Security
The system shall provide data field level
security that enables certain users to access
specific CAD data fields, while keeping other
users from accessing these same data fields.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
985
Out of the Box
Motorola
CSADM046
CAD System
Administration
Security
The system shall facilitate the use of unique
user IDs and passwords to control CAD system
access and privileges.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
986
Out of the Box
Motorola
CSADM047
CAD System
Administration
Security
The system shall be capable of using biometric
identification (e.g. thumb print identification,
retinal ID) to control system access and
privileges.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
987
Out of the Box
Motorola
CSADM048
CAD System
Administration
Security
The system shall provide a “single entry” to
enable logons to multiple authorized systems
that are available through the system (e.g.
NCIC, Nlets).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
988
Out of the Box
Motorola
CSADM049
CAD System
Administration
Security
The system shall limit access to system
functions and data by physical device (e.g. PCs,
terminals), as well as by user ID.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
989
Out of the Box
Motorola
CSADM050
CAD System
Administration
Security
The system shall have the capability to
automatically log-off CAD workstations based
on inactivity periods set by the system
administrator for specific user groups, users
and workstations.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
990
Out of the Box
Motorola
CSADM051
CAD System
Administration
Security
The system shall provide the ability to “lock
out” a user after a system administrator
defined number of failed attempted logons.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
991
Out of the Box
Motorola
CSADM052
CAD System
Administration
Security
The system shall require users to change their
individual password after a system
administrator configurable time limit for use of
the same password expires or a set time period
(e.g. 90 days).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
992
Out of the Box
Motorola
CSADM053
CAD System
Administration
Security
The system shall provide the ability for
individual system users to change their
passwords.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
993
Out of the Box
Motorola
CSADM054
CAD System
Administration
Security
The system shall provide the capability for
individual user name change (e.g. getting
married) and The system shall keep a link to
historical data.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
994
Out of the Box
Motorola
CSADM055
CAD System
Administration
Logging
The system shall include a transaction audit
database that contains all system transactions
and that includes the logon identification (i.e.
user ID and workstation ID), date and time
stamp, transaction type, contents before ID,
and contents after the transaction completes.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
995
Out of the Box
Motorola
CSADM056
CAD System
Administration
Logging
The system shall enable system administrators
to turn the transaction audit log function on
and off by application module, transaction type,
specific data entry form(s), specific tables and
data fields within tables, individual users, user
groups, and various combinations of these
factors.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
996
Out of the Box
Motorola
CSADM057
CAD System
Administration
Logging
The system shall enable authorized system
users to search the transaction audit database
by date and time ranges, by application
module, transaction type, specific tables and
data fields within tables, specific data entry
forms, individual users, user groups,
workstation ID, and by various combinations of
these factors.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
997
Out of the Box
Page 45of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CSADM058
CAD System
Administration
Logging
The system shall enable authorized system
users to create formatted reports and/or
export the results of transaction audit database
queries and searches.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
998
Out of the Box
Motorola
CSADM059
CAD System
Administration
Logging
The system shall enable authorized system
users to generate statistical reports on
transactions contained in the transaction audit
database for all users, a subset of users and/or
user groups, for a specified date and time
range, and for various combinations of these
factors.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
999
Out of the Box
Motorola
CSADM060
CAD System
Administration
Logging
The system shall prohibit any changes to the
contents of the CAD transaction audit database.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1000
Out of the Box
Motorola
CSADM061
CAD System
Administration
Logging
The CAD system’s CAD transaction audit
database:
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1001
Out of the Box
Motorola
CSADM062
CAD System
Administration
Logging
The system shall store all transactions
completed on open/active incidents, including
the transaction’s date and time stamp, the user
and workstation ID performing the transaction,
and the before and after results of the
transaction.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1002
Out of the Box
Motorola
CSADM063
CAD System
Administration
Logging
The system shall store all system messages,
including the message’s date and time stamp,
the user and workstation ID sending and
receiving the message, and the message
contents.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1003
Out of the Box
Motorola
CSADM064
CAD System
Administration
Logging
The system shall store transaction information
associated with all CAD configuration
parameters and files, including any time a user
views, prints, edits, ads, or deletes the
configuration parameters and/or CAD system
configuration file records.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1004
Out of the Box
Motorola
CSADM065
CAD System
Administration
Logging
The system shall should capture the messages
and associated information (e.g. date and time
stamp, user ID, workstations ID) of user and
system generated queries to interfaced system
and databases (e.g. NCIC, Nlets).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1005
Out of the Box
Motorola
CSADM066
CAD System
Administration
Logging
The system shall should capture the date, time
and user ID associated with previous incident
history access.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1006
Out of the Box
Motorola
CSADM067
CAD System
Administration
Logging
The system shall should capture transaction
information associated with all CAD security
transactions, including any time a CAD user
views, prints, edits, ads, or deletes the security
information within the CAD system.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1007
Out of the Box
Motorola
CSADM068
CAD System
Administration
Logging
The system shall store transaction information
associated with all CAD system modifications
completed by system administrators, including
administrator user ID, date/time of
modification, modification made, and table
value prior to the completed modification.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1008
Out of the Box
Motorola
CSADM069
CAD System
Administration
Logging
The system shall store the date, time,
workstation ID, and user ID associated with
unsuccessful sign-on attempts.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1009
Out of the Box
Motorola
CSADM070
CAD System
Administration
Configurations
The system shall enable authorized system
administrators to configure the CAD system to
meet the requirements of the agencies using
the system by creating and modifying CAD
configuration parameters.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1010
Out of the Box
Motorola
CSADM071
CAD System
Administration
Configurations
The system shall enable authorized system
administrators to modify CAD configuration
parameters without the requirement for
programmer or other support from the
manufacturer of the CAD system.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1011
Out of the Box
Motorola
CSADM072
CAD System
Administration
Configurations
The system shall enable authorized system
administrators to modify/Import/Export CAD
print templets without the requirement of
support from the manufacturer of the CAD
system.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1012
Out of the Box
Motorola
CSADM073
CAD System
Administration
Configurations
CAD configuration parameters:
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1013
Out of the Box
Motorola
CSADM074
CAD System
Administration
Configurations
The system shall include functionality for table
driven and directly modifiable functionality by
authorized system administrators.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1014
Out of the Box
Page 46of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CSADM075
CAD System
Administration
Configurations
The system shall include functionality for
interactive, menu-driven, GUI-based tool that
allows authorized administrators to easily
update and modify parameters.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1015
Out of the Box
Motorola
CSADM076
CAD System
Administration
Configurations
The system shall include functionality for on-
line help that lists all of the available options for
a configuration parameter, and a description of
the impacts resulting from changing the
parameter to each of its available options.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1016
Out of the Box
Motorola
CSADM077
CAD System
Administration
Configurations
The system shall include functionality for
modifications to CAD configuration parameters
when the CAD system is active without having
to shut the entire CAD system down or restart
it.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1017
Out of the Box
Motorola
CSADM078
CAD System
Administration
Configurations
The system shall include functionality for
modifying agency and user specific workflows,
such as when and under what circumstances a
CFS event is automatically routed from a call
taker to a dispatcher and which users (e.g. call
takers, dispatchers, supervisors) receive system
routed CFS events.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1018
Out of the Box
Motorola
CSADM079
CAD System
Administration
Configurations
The system shall include functionality for
specifying the agencies that will be included in
the CAD system, along with their attributes (i.e.
fire department, volunteers, law enforcement
agency).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1019
Out of the Box
Motorola
CSADM080
CAD System
Administration
Configurations
The system shall include functionality for
specifying and modifying the type of resources
available in the system.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1020
Out of the Box
Motorola
CSADM081
CAD System
Administration
Configurations
The system shall include functionality for
specifying the incident types that will be
processed by the system.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1021
Out of the Box
Motorola
CSADM082
CAD System
Administration
Configurations
The system shall include functionality for
entering and modifying dispatch policies that
specify the type of resources that are
dispatched to specific incident types.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1022
Out of the Box
Motorola
CSADM083
CAD System
Administration
Configurations
The system shall include functionality for
configuring different system dispatch policies
for each incident type, priority and agency
using the system.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1023
Out of the Box
Motorola
CSADM084
CAD System
Administration
Configurations
The system shall include functionality for
specifying the type of alerts and timers
available in the system and their specific
attributes (e.g. on/off, time interval, triggers,
display features).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1024
Out of the Box
Motorola
CSADM085
CAD System
Administration
Configurations
The system shall include functionality for
entering and modifying the type of dispositions,
priorities, and other CFS event related
parameters of the CAD system.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1025
Out of the Box
Motorola
CSADM086
CAD System
Administration
Configurations
The system shall include functionality for
specifying the starting point and formats of
case numbers created by the CAD system for
each agency using the system.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1026
Out of the Box
Motorola
CSADM087
CAD System
Administration
Configurations
The system shall include functionality for
specifying the sort order, layout, color, font,
and other appearance and operational
attributes of the CAD system’s windows and
menus.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1027
Out of the Box
Motorola
CSADM088
CAD System
Administration
Configurations
The system shall include functionality for
modifying the look and feel of CAD
workstations.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1028
Out of the Box
Motorola
CSADM089
CAD System
Administration
Configurations
The system shall include functionality for
modifying the look and feel of the tactical map
display available in the system (e.g. setting up
the graphic information appearing at different
zoom levels, predefined zoom levels for
different incident types, icons).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1029
Out of the Box
Motorola
CSADM090
CAD System
Administration
Configurations
The system shall include functionality for
modifying the display and functional
characteristics of CAD system queues (e.g.
pending incident queue, incident queue, active
incident queue, stacked incidents queue).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1030
Out of the Box
Motorola
CSADM091
CAD System
Administration
Configurations
The system shall include functionality for
modifying the display and functional
characteristics of the CAD system’s resource
recommendations.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1031
Out of the Box
Motorola
CSADM092
CAD System
Administration
Configurations
The system shall include functionality for
modifying the display and functional
characteristics of interfaced systems and
gateways (e.g. 9-1-1 call interfaces, paging and
other responder alerting interfaces, NCIC and
other criminal database interfaces, mobile
computer system).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1032
Out of the Box
Page 47of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CSADM093
CAD System
Administration
Table Maintenance
The system shall include CAD tables that are
maintained using entry windows.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1033
Out of the Box
Motorola
CSADM094
CAD System
Administration
Table Maintenance
The system shall include CAD table
maintenance entry windows that have context-
sensitive, field-level help.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1034
Out of the Box
Motorola
CSADM095
CAD System
Administration
Table Maintenance
The system shall enable changes made to CAD
tables to become immediately effective and
The system shall not affect overall CAD system
availability nor require any CAD system down
time.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1035
Out of the Box
Motorola
CSADM096
CAD System
Administration
Table Maintenance
The system shall allow agencies to define
additional data elements based on their
operational requirements.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1036
Out of the Box
Motorola
CSADM097
CAD System
Administration
Table Maintenance
The system shall provide the ability for tables to
be defined to support the maintenance of the
following CAD objects, including, but not
limited to:
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1037
Out of the Box
Motorola
CSADM098
CAD System
Administration
Table Maintenance
Agencies
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1038
Out of the Box
Motorola
CSADM099
CAD System
Administration
Table Maintenance
BOLOs, including location, person, and vehicle
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1039
Out of the Box
Motorola
CSADM100
CAD System
Administration
Table Maintenance
Clearance/disposition codes
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1040
Out of the Box
Motorola
CSADM101
CAD System
Administration
Table Maintenance
Hazards
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1041
Out of the Box
Motorola
CSADM102
CAD System
Administration
Table Maintenance
Court Jurisdictions
Mandatory
CAD
X
PremierOne does not have this functionality.
MCSO team stated this is not required to be met.
1042
Cannot Meet
Motorola
CSADM103
CAD System
Administration
Table Maintenance
Incident/event types
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1043
Out of the Box
Motorola
CSADM104
CAD System
Administration
Table Maintenance
Substations
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1044
Out of the Box
Motorola
CSADM105
CAD System
Administration
Table Maintenance
Memos
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1045
Out of the Box
Motorola
CSADM106
CAD System
Administration
Table Maintenance
Messages (e.g. canned, scheduled)
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1046
Out of the Box
Motorola
CSADM107
CAD System
Administration
Table Maintenance
Notifications
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1047
Out of the Box
Motorola
CSADM108
CAD System
Administration
Table Maintenance
Personnel
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1048
Out of the Box
Motorola
CSADM109
CAD System
Administration
Table Maintenance
Rosters
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1049
Out of the Box
Motorola
CSADM110
CAD System
Administration
Table Maintenance
Response plans
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1050
Out of the Box
Motorola
CSADM111
CAD System
Administration
Table Maintenance
Service types (i.e. law enforcement, fire, EMS)
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1051
Out of the Box
Motorola
CSADM112
CAD System
Administration
Table Maintenance
Skills (personnel)
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1052
Out of the Box
Motorola
CSADM113
CAD System
Administration
Table Maintenance
SOPs
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1053
Out of the Box
Motorola
CSADM114
CAD System
Administration
Table Maintenance
Units
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1054
Out of the Box
Motorola
CSADM115
CAD System
Administration
Table Maintenance
Unit attributes (e.g. ALS, BLS, Hurst tool)
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1055
Out of the Box
Motorola
CSADM116
CAD System
Administration
Table Maintenance
Unit statuses (i.e. dispatched, en route, arrived,
cleared)
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1056
Out of the Box
Motorola
CSADM117
CAD System
Administration
Table Maintenance
Unit Types (e.g. i.e. patrol car, motorcycle,
engine, ladder, pumper)
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1057
Out of the Box
Motorola
CSADM118
CAD System
Administration
Table Maintenance
Vehicles
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1058
Out of the Box
Motorola
CSADM119
CAD System
Administration
Comm Center / PSAP
Relocation
The system shall meet PSAP industry best
practices and CJIS requirements.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1059
Out of the Box
Page 48of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CSADM120
CAD System
Administration
Comm Center / PSAP
Relocation
The system shall account for replacement or
the movement of any necessary existing
equipment including base computers,
terminals, network, and personnel.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1060
Out of the Box
Motorola
CSADM121
CAD System
Administration
Comm Center / PSAP
Relocation
The system shall account for a data-backup
plan.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1061
Out of the Box
Motorola
CSADM122
CAD System
Administration
Comm Center / PSAP
Relocation
The system shall account for coordination of
external inputs to the CAD system from third-
party vendors (e.g. telephone, data, 9-1-1) for a
minimal loss of functionality.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1062
Out of the Box
Motorola
CSADM123
CAD System
Administration
Comm Center / PSAP
Relocation
The system shall provide for access to a copy of
the production system through the backup or
disaster recovery environments.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1063
Out of the Box
Motorola
CSADM124
CAD System
Administration
CAD Catch-up
The system shall have the ability to manually
open and create a CFS event sheet.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1064
Out of the Box
Motorola
CSADM125
CAD System
Administration
CAD Catch-up
The system shall provide the ability to log the
entering individual’s information and time of
entry.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1065
Out of the Box
Motorola
CSADM126
CAD System
Administration
CAD Catch-up
The system shall provide the ability for all
information to be entered without any
restrictions, and times/dates changed to reflect
the actual time that notice of the CFS event was
received.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1066
Out of the Box
Motorola
CSADM127
CAD System
Administration
CAD Catch-up
The system shall denote the manually-entered
CFS event so there is a record that the CFS
event was not entered when it was actually
received.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1067
Out of the Box
Motorola
CSADM128
CAD System
Administration
CAD Catch-up
The system shall include all the information in
back entered records that a live incident/event
sheet should require.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1068
Out of the Box
Motorola
CSF001
System
Functions
Messaging
Vendor shall explain what can be done to
prevent incoming messages from over
cluttering screens when messaging volumes are
high. The active units display needs to be in full
view at all time.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement. PremierOne CAD can
send and receive email messages to and from other PremierOne CAD and Mobile users as well as
radio users, and can send and receive email messages to and from external email systems. The
total number of read and unread messages in a folder can be displayed by selecting the check box
at the top of the column of the list of messages. The number displays above the Work Assist Area.
This feature can determine how many messages are in the folder and if any need to be deleted.
For messages to be downloaded, no folder can have more than 300 unread and read messages. If
the message count of unread and read messages in any folder is greater than or equal to 300, the
next synchronization cycle will NOT download the next set of messages. To receive all the latest
unread messages, users should delete old messages from their folders to make room for newer
ones.
1069
Out of the Box
Motorola
CSF002
System
Functions
Messaging
The vendor shall explain in detail the process
for accessing past messages.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement. You can access
messaging by performing one of the following actions:
- On the command line, type SM and press ENTER or F10.
- On the command line, press F6 and press ENTER or F10.
The Messaging form opens with the Messages tab active. The Messaging Work Assist Area has the
following tabs:
ͻ/ŶďŽdžʹDĞƐƐĂŐĞƐƐĞŶƚƚŽLJŽƵĂƵƚŽŵĂƚŝĐĂůůLJŐŽƚŽƚŚĞ/ŶďŽdž͘
The Inbox tab displays the total number of unread messages in the Inbox folder on the client/the
total number of unread messages on the server. For example, 1/20 means there is one unread
message on the client and 20 unread messages on the server. The total number of read and
unread messages in a folder can be displayed by selecting the check box at the top of the column
of the list of messages. The number displays above the Work Assist Area. This feature can be used
to determine how many messages are in the folder and if any need to be deleted.
1070
Out of the Box
Motorola
CSF003
System
Functions
Messaging
The system should have the ability to support
messaging from MDCs and Workstations to:
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1071
Out of the Box
Motorola
CSF004
System
Functions
Messaging
Workstation(s), Group(s), MDC(s), Cellular
devices, Event Number, individuals, E-mail, text
messages, other connected PSAPS
(notifications only) and any combination
thereof
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1072
Out of the Box
Motorola
CSF005
System
Functions
Messaging
All messages need to identify the workstation
or MDC that sent the message and all the
workstations or MDCs that received the
message.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1073
Out of the Box
Motorola
CSF006
System
Functions
Messaging
All messages need to be time stamped.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1074
Out of the Box
Motorola
CSF007
System
Functions
Messaging
The message should appear at the receiving
terminal as it was typed in to include
punctuation, returns, spacing etc.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1075
Out of the Box
Motorola
CSF008
System
Functions
Messaging
When a message is printed the system needs to
display the position requesting the print and
the associated employee name and ID on the
printed header. Can this functionality be
turned off if so desired?
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1076
Out of the Box
Motorola
CSF009
System
Functions
Messaging
The system provides the capability for users to
define static and dynamic (ad-hoc) message
groups for messaging.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1077
Out of the Box
Page 49of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CSF010
System
Functions
Messaging
The system should provide a simple/easy
means for printing complete message
information.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1078
Out of the Box
Motorola
CSF011
System
Functions
Messaging
The system has the capability of providing
Agency-defined visual and/or audible indicators
that a message has been received for both CAD
workstations and MDCs.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1079
Out of the Box
Motorola
CSF012
System
Functions
Messaging
Priority messages should produce an agency-
defined audible or visual flashing indicator that
is different from normal messages.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1080
Out of the Box
Motorola
CSF013
System
Functions
Messaging
Priority message notifications should take
priority over routine messages.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1081
Out of the Box
Motorola
CSF014
System
Functions
Messaging
Messaging can support a single user action to
reply/forward to sender (similar to e-mail )
without having to type a reply from a MDC,
workstation, email, wireless device. The reply
action should be configurable by Agency.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1082
Out of the Box
Motorola
CSF015
System
Functions
Messaging
The system shall enable the system
administrator to define the rules for automatic
Call for Service event notifications.
Preferred
CAD
X
PremierOne complies with the functionality as described in the requirement.
1083
Out of the Box
Motorola
CSF016
System
Functions
Messaging
For MDC's, the proposed message application
should provide an option for a pop up window
without the need for the operator to take an
affirmative action to make the message visible.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1084
Out of the Box
Motorola
CSF017
System
Functions
Messaging
Forwarded messages should indicate the initial
sender's ID in addition to the ID of the user who
forwarded the message and the time the
original message was sent and forwarded.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1085
Out of the Box
Motorola
CSF018
System
Functions
Messaging
Replies and forwarded messages should retain
all previous messages in the thread in
chronological order. (As text messaging or
email does.)
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1086
Out of the Box
Motorola
CSF019
System
Functions
Messaging
The system should allow users, upon request,
to receive acknowledgement that their sent
message was read and indicate the time the
message was opened and read (agency-
definable parameter).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1087
Out of the Box
Motorola
CSF020
System
Functions
Messaging
Alerts and notifications should be delivered as a
automatic pop-up window requiring action, a
static display indicating that notifications
should be checked or a highlighted button that
triggers a pop-up list. Each should be
configurable by the system administrator for
maximum suitability to the CAD function
supported.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1088
Out of the Box
Motorola
CSF021
System
Functions
Messaging
The message system should allow Agency
configurable notification and message masks.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1089
Out of the Box
Motorola
CSF022
System
Functions
Messaging
The system should provide a minimum of three
agency definable alert tones for messaging on
workstations and MDCs.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1090
Out of the Box
Motorola
CSF023
System
Functions
Messaging
Users should be able to save received messages
for future review.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1091
Out of the Box
Motorola
CSF024
System
Functions
Messaging
The system administrator is provided
unrestricted access to all messaging
functionality.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1092
Out of the Box
Motorola
CSF025
System
Functions
Messaging
The system should allow the system
administrator to define individual and role
based messaging capability.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1093
Out of the Box
Motorola
CSF026
System
Functions
Messaging
The system should allow the user to send the
underlying text of any message received on the
MDC to a printer.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1094
Out of the Box
Motorola
CSF027
System
Functions
Messaging
The user should have the capability to select
any printer available on the network and not be
confined to only the default printer for his or
her terminal device,
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1095
Out of the Box
Motorola
CSF028
System
Functions
Messaging
The system should minimally support the
following classifications of user-definable
messages:
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1096
Out of the Box
Motorola
CSF029
System
Functions
Messaging
Routine, messages that are sent, which should
be archived.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1097
Out of the Box
Motorola
CSF030
System
Functions
Messaging
Remote messages (from outside sources such
as ACJIS, NCIC, etc., should include the message
number provided by ACJIS, NCIC, NLETS).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1098
Out of the Box
Motorola
CSF031
System
Functions
Messaging
The system should have the ability to generate
and save user-defined groups.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1099
Out of the Box
Page 50of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CSF032
System
Functions
Messaging
The system should have the ability to send
messages to users not logged on to the system.
Users who receive a message and are not
logged on to the system will receive the
message upon log on. If an intended recipient
is not logged on the sender should be notified.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1100
Out of the Box
Motorola
CSF033
System
Functions
Messaging
The system administrator should have the
ability to configure the time period and type of
messages stored and forwarded to a deputy
upon logon.
Mandatory
CAD
X
PremierOne partially complies with the functionality as described in the requirement. System
Administrators have the ability to configure the time period, but not the type of message.
1101
Out of the Box
Motorola
CSF034
System
Functions
Messaging
The system should allow all messages to be
indexed and sequentially numbered to facilitate
ease of search and recall.
Mandatory
CAD
X
PremierOne does not have this functionality
MCSO team stated this is not required to be met.
1102
Cannot Meet
Motorola
CSF035
System
Functions
Messaging
The system should allow users to query and
view a number of messages at once by
specified date and time range(s).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement. Users see a
summary list of all messages on the message screen.
1103
Out of the Box
Motorola
CSF036
System
Functions
Messaging
The system should have the ability to "mine"
the text of messages for key words as well as by
EIN, position, dates and times, groups, and any
other user-defined parameters.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1104
Out of the Box
Motorola
CSF037
System
Functions
Messaging
The system should provide users the ability to
quickly and easily recall their most recently
viewed messages.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1105
Out of the Box
Motorola
CSF038
System
Functions
Messaging
MDC and workstation users should be able to
view more than one message at a time without
deleting the previous message.
Mandatory
CAD
X
PremierOne does not have this functionality. In PremierOne, users can only view one message at
a time. Users do not have to delete messages in order to view another message.
Motorola demonstrated creation of message and
viewing of messages in MDC and CAD desktop client.
MCSO - can we customize message to go to a certain
group? Motorola demonstrated address groups.
MCSO & Motorola teams agree requirement is
met out of the box per notes in Column O.
1106
Cannot Meet
Motorola
CSF039
System
Functions
Messaging
Communications Supervisors should have the
capability to view messages (real time and
historical) operator to operator and operator to
MDC.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1107
Out of the Box
Motorola
CSF040
System
Functions
Messaging
The system should provide the capability to
print messages taking place between specific
terminals//individuals in chronological order.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1108
Out of the Box
Motorola
CSF041
System
Functions
Messaging
The system should provide a simple way to
associate messages to events and store them as
part of the event logs.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1109
Out of the Box
Motorola
CSF042
System
Functions
Notifications
The system shall enable the system
administrator to define the rules for automatic
CFS (Calls for Service) event notifications.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1110
Out of the Box
Motorola
CSF043
System
Functions
Notifications
The system shall provide the ability to create
messages that are retained in the system and
sent at pre-specified times.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1111
Out of the Box
Motorola
CSF044
System
Functions
Notifications
The system shall provide the ability to maintain
a log of all messages processed by the system.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1112
Out of the Box
Motorola
CSF045
System
Functions
Notifications
The system shall allow the user to send and
store messages to other users, groups,
positions, or mobile devices.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1113
Out of the Box
Motorola
CSF046
System
Functions
Notifications
The system shall allow a message to be sent to
multiple recipients and/or groups.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1114
Out of the Box
Motorola
CSF047
System
Functions
Notifications
The system shall log all sent messages.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1115
Out of the Box
Motorola
CSF048
System
Functions
Notifications
The system shall provide the ability to create
and maintain automatic reminders of scheduled
activities (e.g. radio tests):
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1116
Out of the Box
Motorola
CSF049
System
Functions
Notifications
Daily
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1117
Out of the Box
Motorola
CSF050
System
Functions
Notifications
Weekly
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1118
Out of the Box
Motorola
CSF051
System
Functions
Notifications
Monthly
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1119
Out of the Box
Motorola
CSF052
System
Functions
Notifications
Annually
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1120
Out of the Box
Motorola
CSF053
System
Functions
Notifications
User-defined (e.g. 30 minutes, 15 minutes, first
day of the month)
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1121
Out of the Box
Motorola
CSF054
System
Functions
Notifications
Multiple activities or reminders per time slot
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1122
Out of the Box
Motorola
CSF055
System
Functions
Contact List
The system shall allow a message to be sent to
multiple recipients and/or groups.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1123
Out of the Box
Motorola
CSF056
System
Functions
Contact List
The system shall be able to log all sent
messages.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1124
Out of the Box
Motorola
CSF057
System
Functions
Contact List
The system shall provide an emergency
contacts list, to include:
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1125
Out of the Box
Motorola
CSF058
System
Functions
Contact List
Contact name
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1126
Out of the Box
Motorola
CSF059
System
Functions
Contact List
Street address
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1127
Out of the Box
Motorola
CSF060
System
Functions
Contact List
City
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1128
Out of the Box
Page 51of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CSF061
System
Functions
Contact List
State
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1129
Out of the Box
Motorola
CSF062
System
Functions
Contact List
Zip
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1130
Out of the Box
Motorola
CSF063
System
Functions
Contact List
Telephone numbers
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1131
Out of the Box
Motorola
CSF064
System
Functions
Contact List
Relationship
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1132
Out of the Box
Motorola
CSF065
System
Functions
Contact List
User-defined/configurable fields
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1133
Out of the Box
Motorola
CSF066
System
Functions
Premise Information
/ Hazards/ Special
Situations
The system shall provide the ability to enter a
premises location by address, cross street or
latitude/longitude.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1134
Out of the Box
Motorola
CSF067
System
Functions
Premise Information
/ Hazards/ Special
Situations
The system shall provide the ability to capture,
maintain or interface to specific premises
information types for operators:
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1135
Out of the Box
Motorola
CSF068
System
Functions
Premise Information
/ Hazards/ Special
Situations
Hazardous materials
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1136
Out of the Box
Motorola
CSF069
System
Functions
Premise Information
/ Hazards/ Special
Situations
Hazardous conditions
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1137
Out of the Box
Motorola
CSF070
System
Functions
Premise Information
/ Hazards/ Special
Situations
Lock codes
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1138
Out of the Box
Motorola
CSF071
System
Functions
Premise Information
/ Hazards/ Special
Situations
Dangerous animals
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1139
Out of the Box
Motorola
CSF072
System
Functions
Premise Information
/ Hazards/ Special
Situations
Handicap
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1140
Out of the Box
Motorola
CSF073
System
Functions
Premise Information
/ Hazards/ Special
Situations
Emergency contact information
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1141
Out of the Box
Motorola
CSF074
System
Functions
Premise Information
/ Hazards/ Special
Situations
Unit safety
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1142
Out of the Box
Motorola
CSF075
System
Functions
Premise Information
/ Hazards/ Special
Situations
Warrants
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1143
Out of the Box
Motorola
CSF076
System
Functions
Premise Information
/ Hazards/ Special
Situations
Alarms
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1144
Out of the Box
Motorola
CSF077
System
Functions
Premise Information
/ Hazards/ Special
Situations
Protective Orders, Sexual Offenders
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1145
Out of the Box
Motorola
CSF078
System
Functions
Premise Information
/ Hazards/ Special
Situations
Building plans
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1146
Out of the Box
Motorola
CSF079
System
Functions
Premise Information
/ Hazards/ Special
Situations
Other user-defined premises fields/information Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1147
Out of the Box
Motorola
CSF080
System
Functions
Premise Information
/ Hazards/ Special
Situations
Electronic attachments (e.g. images, files)
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1148
Out of the Box
Motorola
CSF081
System
Functions
Premise Information
/ Hazards/ Special
Situations
The system shall provide the ability to
automatically create (i.e. upon closing of an
incident) premises history based on pre-
determined criteria.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1149
Out of the Box
Motorola
CSF082
System
Functions
Premise Information
/ Hazards/ Special
Situations
The system shall provide the ability to define
valid date ranges for time-limited premises
information at a given location (i.e. information
valid between start date and end date), and to
notify supervisor of pending expiration dates.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1150
Out of the Box
Motorola
CSF083
System
Functions
Premise Information
/ Hazards/ Special
Situations
The system shall provide the ability for
supervisors to delete premises information for
a given address or location based on expiration
date and/or time of record, with prompted
review prior to deletion (i.e. minimum of five
years, on-line storage).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1151
Out of the Box
Page 52of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CSF084
System
Functions
Premise Information
/ Hazards/ Special
Situations
The system shall provide the ability to define
criteria for automatic premises information
purges and activate or deactivate this feature.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1152
Out of the Box
Motorola
CSF085
System
Functions
Premise Information
/ Hazards/ Special
Situations
The system shall provide the ability to verify
that premises warning or hazard information
has not been affected by changes to the
geofile.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1153
Out of the Box
Motorola
CSF086
System
Functions
Premise Information
/ Hazards/ Special
Situations
The system shall provide the ability to view
premises information for a specific
suite/apartment/unit, or to view all premises
information for an entire building.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1154
Out of the Box
Motorola
CSF087
System
Functions
Premise Information
/ Hazards/ Special
Situations
The system shall provide the ability to
automatically embed premises information into
the event history at the time the event is
created.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1155
Out of the Box
Motorola
CSF088
System
Functions
Premise Information
/ Hazards/ Special
Situations
The system shall create a permanent record of
the premises information in the event history.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1156
Out of the Box
Motorola
CSF089
System
Functions
Premise Information
/ Hazards/ Special
Situations
The system shall provide (or interface to) a
“cautions” file to contain information
pertaining to dangerous individuals possibly
residing at that location or near proximity, and
exceptional persons at the location, such as an
emotionally disturbed person.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1157
Out of the Box
Motorola
CSF090
System
Functions
Premise Information
/ Hazards/ Special
Situations
This The system shall include a caution type
category and free form narrative.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1158
Out of the Box
Motorola
CSF091
System
Functions
Premise Information
/ Hazards/ Special
Situations
The caution type The system shall be
searchable.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1159
Out of the Box
Motorola
CSF092
System
Functions
Comm Center / PSAP
Standar Operating
Procedure
The system shall provide the ability to store and
easily retrieve SOPs for the PSAP.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1160
Out of the Box
Motorola
CSF093
System
Functions
Comm Center / PSAP
Standar Operating
Procedure
The system shall provide a SOP tool to prompt
the user to ask for additional information,
perform certain tasks, or relay critical
information to responding units or other
responders.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1161
Out of the Box
Motorola
CSF094
System
Functions
Comm Center / PSAP
Standar Operating
Procedure
The system shall provide a method where the
retrieval of relevant SOPs are accessible from
the CFS event information window and
associated with the location, incident type,
unit, or special skilled personnel responding.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1162
Out of the Box
Motorola
CSF095
System
Functions
Command Line/GUI
The system shall include the ability to be
operated via a command line entry, mouse and
keyboard, or both.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1163
Out of the Box
Motorola
CSF096
System
Functions
Date/Timestamp
The system shall stamp date/time and log CAD
activities, such as status changes, task
accomplishments (i.e. Fire Attack Initiated,
Time Fire Declared Under Control, Time at
Patient), and notifications, as well as many
other system transactions and the time they
occur.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1164
Out of the Box
Motorola
CSF097
System
Functions
Date/Timestamp
The system shall save original time stamps even
if they are overridden.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1165
Out of the Box
Motorola
CSF098
System
Functions
Date/Timestamp
The system shall protect time stamp overrides;
and, any changes The system shall be
documented on the incident, including the ID of
the person performing the modification and the
reason for the modification.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1166
Out of the Box
Motorola
CSF099
System
Functions
Date/Timestamp
The system shall maintain all time stamps to be
minimally accurate to the second (e.g.
hh:mm:ss).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1167
Out of the Box
Motorola
CSF100
System
Functions
CFS Routing
The system shall have the ability to create a CFS
event for user-defined multi-agency events and
route the CFS event to the appropriate agency
dispatch position(s).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1168
Out of the Box
Motorola
CSF101
System
Functions
CFS Routing
The system shall have the ability to create a
linked CFS event for each required agency and
route the CFS event(s) to the appropriate
dispatch positions when an event involves
more than one agency.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1169
Out of the Box
Page 53of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CSF102
System
Functions
CFS Routing
The system shall have the capacity to create a
multi-jurisdictional response; for example,
should Jurisdiction X determine that Jurisdiction
Y resources are needed on the scene, the fire
dispatcher The system shall have the ability to
forward/copy the CFS event without re-
entering the event information to the
appropriate Jurisdiction Y dispatcher based on
CAD recommended or dispatched units.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1170
Out of the Box
Motorola
CSF103
System
Functions
CFS Routing
The system shall provide the ability to create
and route a CFS event for dispatch even though
the event is in another jurisdiction.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1171
Out of the Box
Motorola
CSF104
System
Functions
CFS Routing
The system shall provide the ability to transfer
an active CFS event to another agency without
closing the CAD CFS event within the originating
agency.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1172
Out of the Box
Motorola
CSF105
System
Functions
CFS Routing
The system shall provide the ability to link cross-
jurisdictional events using agency-definable
parameters.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1173
Out of the Box
Motorola
CSF106
System
Functions
CFS Routing
The system shall update the originating
jurisdiction’s CFS event information if the
dispatcher in the receiving jurisdiction updates
or supplements the event.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1174
Out of the Box
Motorola
CSF107
System
Functions
CFS Routing
The system shall have the ability to create
agency-definable recommendations for cross
jurisdictional responses and automated
messaging based on user-definable parameters.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1175
Out of the Box
Motorola
CSF108
System
Functions
CFS Routing
The system shall provide the ability to identify
other jurisdiction addresses and alert the CAD
user with the jurisdiction’s name and contact
information.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1176
Out of the Box
Motorola
CRM001
CAD Reporting
and Monitoring
Dispatch Supervisor
Support
The system shall provide the ability for a CAD
supervisor, or another dispatcher with
appropriate system permissions, to observe the
activity of a given dispatcher including the
pending events queue, active events, available
units list, and map.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1177
Out of the Box
Motorola
CRM002
CAD Reporting
and Monitoring
Dispatch Supervisor
Support
The system shall enable a supervisor, or
another dispatcher with appropriate system
permissions, to co-dispatch the units under the
control of another dispatcher.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1178
Out of the Box
Motorola
CRM003
CAD Reporting
and Monitoring
Dispatch Supervisor
Support
The system shall have the ability to add
additional dispatchers “on-the-fly” for one or
more services, either globally or for
predetermined geographical areas.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1179
Out of the Box
Motorola
CRM004
CAD Reporting
and Monitoring
Dispatch Supervisor
Support
The system shall provide the ability for a CAD
supervisor, or another dispatcher with
appropriate system permissions, to observe the
activity of a given dispatcher including the
pending events queue, active events, available
units list, and map.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1180
Out of the Box
Motorola
CRM005
CAD Reporting
and Monitoring
Dispatch Supervisor
Support
The system shall enable a supervisor, or
another dispatcher with appropriate system
permissions, to co-dispatch the units under the
control of another dispatcher.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1181
Out of the Box
Motorola
CRM006
CAD Reporting
and Monitoring
Dispatch Supervisor
Support
The system shall have the ability to add
additional dispatchers “on-the-fly” for one or
more services, either globally or for
predetermined geographical areas.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1182
Out of the Box
Motorola
CRM007
CAD Reporting
and Monitoring
CAD Management
Reporting
The system must include a separate Reporting
Data Warehouse for reporting purposes.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1183
Out of the Box
Motorola
CRM008
CAD Reporting
and Monitoring
CAD Management
Reporting
The system must utilize Microsoft SQL Server
Reporting Services (SSRS) as its ad hoc reporting
tool.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1184
Out of the Box
Motorola
CRM009
CAD Reporting
and Monitoring
CAD Management
Reporting
All standard reports provided with the system
must be developed and provided usnig SSRS.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1185
Out of the Box
Motorola
CRM010
CAD Reporting
and Monitoring
CAD Management
Reporting
The system shall include standard reports that
simultaneously use date, time, location, and/or
incident type search parameters for report
definitions.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1186
Out of the Box
Motorola
CRM011
CAD Reporting
and Monitoring
CAD Management
Reporting
The system shall include the capability of
customizing standard reports and for creating
user-defined reports.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1187
Out of the Box
Page 54of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CRM012
CAD Reporting
and Monitoring
CAD Management
Reporting
The system shall provide access to all reports to
the user, subject to permissions, from within
the CAD system.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1188
Out of the Box
Motorola
CRM013
CAD Reporting
and Monitoring
CAD Management
Reporting
The system shall include reports in the CAD
security/permissions function (i.e. individual
reports can be made available/unavailable
based on a user’s security profile).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1189
Out of the Box
Motorola
CRM014
CAD Reporting
and Monitoring
CAD Management
Reporting
The system shall provide all reports to users,
subject to permissions, regardless of the
application used to create user-defined or
custom reports (i.e. internal to the CAD system
or via a third-party reporting or analysis tool).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1190
Out of the Box
Motorola
CRM015
CAD Reporting
and Monitoring
CAD Management
Reporting
The system shall provide an ad hoc reporting
capability.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1191
Out of the Box
Motorola
CRM016
CAD Reporting
and Monitoring
CAD Management
Reporting
The system shall provide a data exporting
capability.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1192
Out of the Box
Motorola
CRM017
CAD Reporting
and Monitoring
Training/Testing
The system shall include a training environment
that accurately mirrors the live environment,
including all tables and administrative
configurations, and allows for call takers and
dispatchers to train on specific services and on
pre-configured geographic areas identical to
that of the live environment.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1193
Out of the Box
Motorola
CRM018
CAD Reporting
and Monitoring
Training/Testing
The TEST system shall be able to be used to test
modifications and updates to the live CAD
application prior to implementing the
modifications and updates in the live
environment.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1194
Out of the Box
Motorola
CLS001
Location
Services
Tactical Map Display The Tactical Map display must be a
representaion of GIS data.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1195
Out of the Box
Motorola
CLS002
Location
Services
Tactical Map Display The system shall be a seamlessly integrated
computerized map, which is a digitized
representaiton of the GIS data.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1196
Out of the Box
Motorola
CLS003
Location
Services
Tactical Map Display The system shall be fully integrated with the
CAD system.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1197
Out of the Box
Motorola
CLS004
Location
Services
Tactical Map Display The system shall integrate with aerial imaging
technologies to provide digital aerial imaging.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1198
Out of the Box
Motorola
CLS005
Location
Services
Tactical Map Display The system shall link high-resolution aerial
photos to mapping systems; overlay shape files
directly on top of orthogonal images; and,
display vector data.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1199
Out of the Box
Motorola
CLS006
Location
Services
Tactical Map Display The system shall include geographic data to
support, at a minimum, the following:
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1200
Out of the Box
Motorola
CLS007
Location
Services
Tactical Map Display Boundaries
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1201
Out of the Box
Motorola
CLS008
Location
Services
Tactical Map Display Boundary assignments (i.e. determining the
response zone for each incident) completed in
real time by processing the incident’s X,Y
coordinates the boundary layers to determine
the incident’s location and response zone
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1202
Out of the Box
Motorola
CLS009
Location
Services
Tactical Map Display Address validation and to determine an
incident’s location
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1203
Out of the Box
Motorola
CLS010
Location
Services
Tactical Map Display Bulk data uploading
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1204
Out of the Box
Motorola
CLS011
Location
Services
Tactical Map Display As needed data updates
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1205
Out of the Box
Motorola
CLS012
Location
Services
Tactical Map Display In order to support the geofile system, the CAD
system:
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1206
Out of the Box
Motorola
CLS013
Location
Services
Tactical Map Display The system shall provide geo-fencing,
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1207
Out of the Box
Motorola
CLS014
Location
Services
Tactical Map Display The system shall support valid MSAG names
and multiple “aliases” for street names,
intersections, commonplace names, landmarks,
and street or highway route numbers.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1208
Out of the Box
Motorola
CLS015
Location
Services
Tactical Map Display The system shall stem geographically sensitive
hazards, dispatch policies, and other system
functions from validated locations.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1209
Out of the Box
Motorola
CLS016
Location
Services
Duplicate Check
The system shall make a duplicate event check
based upon the location and/or coordinates of
the event, during the CFS event creation
process.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1210
Out of the Box
Motorola
CLS017
Location
Services
Duplicate Check
The system shall notify the event entry
position via a prompt and show a list of the
potential duplicate(s) if, during event creation,
a potential duplicate event in the area is found.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1211
Out of the Box
Page 55of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CLS018
Location
Services
Duplicate Check
The system shall have a parameter (modifiable
by the system administrator) specifying the
distance in number of feet or other unit of
measurement, from the location of the incident
for duplicate checking.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1212
Out of the Box
Motorola
CLS019
Location
Services
Special Situations/
Hazards
The system shall define location databases
such as hazards, general premises information,
street closures, and other user definable tables.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1213
Out of the Box
Motorola
CLS020
Location
Services
Special Situations/
Hazards
The system shall perform a distance search to
identify the existence of location information
(e.g. hazards) during the event creation
process.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1214
Out of the Box
Motorola
CLS021
Location
Services
Special Situations/
Hazards
The system shall support different search
distance criteria for different types of locations.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1215
Out of the Box
Motorola
CLS022
Location
Services
Special Situations/
Hazards
The system shall support coordinate-based
operations;
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1216
Out of the Box
Motorola
CLS023
Location
Services
Special Situations/
Hazards
The system shall be capable of full integration
with a GPS-based AVL system; and,
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1217
Out of the Box
Motorola
CLS024
Location
Services
Special Situations/
Hazards
The system shall be capable of accepting
named standards driven GPS reporting devices,
such as GPS-enabled smartphones and portable
radios.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1218
Out of the Box
Motorola
CLS025
Location
Services
Special Situations/
Hazards
The system shall allow the system
administrator to be able to modify parameters.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1219
Out of the Box
Motorola
CLS026
Location
Services
AVL
In order to support the AVL system, the CAD
system:
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1220
Out of the Box
Motorola
CLS027
Location
Services
AVL
The system shall seamlessly integrate with the
CAD system and provide detailed, accurate, real-
time vehicle tracking.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1221
Out of the Box
Motorola
CLS028
Location
Services
AVL
The system shall include the AVL ID
(represented as an alias) for each unit user’s
status.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1222
Out of the Box
Motorola
CLS029
Location
Services
AVL
The system shall include the indication that
AVL is enabled for each unit on the user’s status
window. AVL can also be used for reporting,
messaging, response and alerting
functionalities.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1223
Out of the Box
Motorola
CLS030
Location
Services
AVL
The system shall include a visual indication if
units displaying on the map and in the queues
are AVL equipped.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1224
Out of the Box
Motorola
CLS031
Location
Services
AVL
The visual indication if units displaying on the
map and in the queues are AVL equipped The
system shall be customizable by the system
administrator.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1225
Out of the Box
Motorola
CLS032
Location
Services
AVL
The system shall be customizable by the
system administrator.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1226
Out of the Box
Motorola
CLS033
Location
Services
AVL
The system shall be able to play back a unit’s
AVL travel history and see the unit icon move
from location to location on a map window.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1227
Out of the Box
Motorola
CLS034
Location
Services
AVL
The system shall be capable of integrating with
the existing GIS database.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1228
Out of the Box
Motorola
CLS035
Location
Services
AVL
The system shall have other interactive
functionalities also available, such as the ability
to create and view unlimited groups of vehicles.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1229
Out of the Box
Motorola
CLS036
Location
Services
AVL
The system shall provide for an automated
alert function.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1230
Out of the Box
Motorola
CLS037
Location
Services
AVL
The system shall provide for an automated
alert for when vehicle is out of service.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1231
Out of the Box
Motorola
CLS038
Location
Services
AVL
The system shall provide the ability to
determine and modify all such alerts.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1232
Out of the Box
Motorola
CLS039
Location
Services
AVL
The system shall provide the following
information on any unit suffering loss of GPS
signal (e.g. vehicle stopped, vehicle shut off,
loss of network signal, loss of GPS data):
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1233
Out of the Box
Motorola
CLS040
Location
Services
AVL
Last known position
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1234
Out of the Box
Motorola
CLS041
Location
Services
AVL
Time of signal loss
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1235
Out of the Box
Motorola
CLS042
Location
Services
AVL
Time lapse since signal loss
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1236
Out of the Box
Motorola
CLS043
Location
Services
AVL
The system shall provide minimal AVL reports
that include:
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1237
Out of the Box
Motorola
CLS044
Location
Services
AVL
Complete activity detail for specific date range
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1238
Out of the Box
Motorola
CLS045
Location
Services
AVL
Vehicle last stop/end time for date range
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1239
Out of the Box
Motorola
CLS046
Location
Services
AVL
Exception reports including all events that
triggered an alert
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1240
Out of the Box
Page 56of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CLS047
Location
Services
AVL
Vehicle first start/begin time for date range
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1241
Out of the Box
Motorola
CLS048
Location
Services
AVL
Miles per day, stops per day, average and
summaries per vehicle
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1242
Out of the Box
Motorola
CLS049
Location
Services
AVL
The system shall pass unit status information
to the AVL system whenever unit status is
changed.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1243
Out of the Box
Motorola
CLS050
Location
Services
AVL
The system shall pass any changes in unit
location information to the AVL system if unit
location changes are generated within the
proposed system (as opposed to the AVL
navigation system).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1244
Out of the Box
Motorola
CLS051
Location
Services
AVL
The system shall display AVL updates on the
map within two seconds of their receipt from
the AVL controller.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1245
Out of the Box
Motorola
CLS052
Location
Services
AVL
The system shall should be able to dispatch the
nearest appropriate unit based on its AVL
location using an appropriate routing engine to
make that determination.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1246
Out of the Box
Motorola
CLS053
Location
Services
Integration
In order to support map integration and
functionality, the CAD system:
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1247
Out of the Box
Motorola
CLS054
Location
Services
Integration
The system shall validate all incident locations,
whether obtained from an E9-1-1 controller or
entered directly by the call taker for
administrative line (ten-digit) calls, against the
CAD system’s geofile to provide, at a minimum,
cross streets, response areas, map page and
coordinate, legal street names, and zip code.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1248
Out of the Box
Motorola
CLS055
Location
Services
Integration
The system shall allow for the manual
processing of the incident location, in the event
a location cannot be properly validated against
the geofile, so that a CFS event can be created
if the location has been confirmed or known to
exist within the local jurisdiction.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1249
Out of the Box
Motorola
CLS056
Location
Services
Integration
The system shall produce (automatically) a
report of all incident entries that did not
validate on a scheduled basis.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1250
Out of the Box
Motorola
CLS057
Location
Services
Integration
The system shall save original E9-1-1 ANI/ALI
information as part of the CFS event if the user
changes the original information (e.g. the
incident is not at the caller’s location).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1251
Out of the Box
Motorola
CLS058
Location
Services
Integration
The system shall allow for processing of non-
validated locations and notify the dispatcher of
the special address.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1252
Out of the Box
Motorola
CLS059
Location
Services
Integration
The system shall identify the appropriate
agency district, sector, reporting area, agency
of jurisdiction, and any other geographic
boundaries containing an address, once it has
been validated.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1253
Out of the Box
Motorola
CLS060
Location
Services
Integration
The system shall display the two nearest cross-
streets.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1254
Out of the Box
Motorola
CLS061
Location
Services
Integration
The system shall perform location
validations/geofile lookups independent of the
CFS event creation process.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1255
Out of the Box
Motorola
CMOB001
CAD Mobile
Data
Administrative
The system must provide the ability to grant
managerial users access to reset passwords for
others by Agency while preventing access to
update permissions for these users
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1256
Out of the Box
Motorola
CMOB002
CAD Mobile
Data
Administrative
The system must provide the ability to grant
managerial users access to unlock lock user
accounts and reset passwords while restricting
the visiility to personnel detiails such as
address, social security number, etc
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1257
Out of the Box
Motorola
CMOB003
CAD Mobile
Data
Administrative
The system shall provide the system
administrator with the ability to configure
Mobile to their specifications for each Agency
and Agency type.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1258
Out of the Box
Motorola
CMOB004
CAD Mobile
Data
Administrative
The system's function keys must be
customizable by Agency and Agency Type,
giving easy access to frequently used functions.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1259
Out of the Box
Motorola
CMOB005
CAD Mobile
Data
Administrative
The system must allow administrator's to
configure specific incident monitors by Agency
and Agency Type for the Mobile client
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1260
Out of the Box
Motorola
CMOB006
CAD Mobile
Data
Administrative
The system must allow the administrator to
configure specific unit status monitors by
Agency and Agency Type for the Mobile client
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1261
Out of the Box
Motorola
CMOB007
CAD Mobile
Data
Administrative
The system must be able to turn on/off the
Mobile Command line by agency through
configuration
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1262
Out of the Box
Page 57of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CMOB008
CAD Mobile
Data
Administrative
The system must offer a web browser within
the Mobile Client with administrator ability to
restrict web-site access.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1263
Out of the Box
Motorola
CMOB009
CAD Mobile
Data
Administrative
The ability for Mobile queries to be
customizable by the agency
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1264
Out of the Box
Motorola
CMOB010
CAD Mobile
Data
Administrative
The Mobile system must record all database
changes as well as other events in the system
that may not result in a database change. Every
change to the data within the database must be
recorded in the Auditing System. Describe how.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1265
Out of the Box
Motorola
CMOB011
CAD Mobile
Data
Administrative
The Mobile System must support multiple
agencies and multiple jurisdictions (Sheriff,
Probation and interconnected agencies if any)
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1266
Out of the Box
Motorola
CMOB012
CAD Mobile
Data
Technical
The Mobile system must utilize a Microsoft
Windows server operating software.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1267
Out of the Box
Motorola
CMOB013
CAD Mobile
Data
Technical
The Mobile system must utilize Microsoft SQL
database software.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1268
Out of the Box
Motorola
CMOB014
CAD Mobile
Data
Technical
The Mobile system must utilize Microsoft
Windows client software.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1269
Out of the Box
Motorola
CMOB015
CAD Mobile
Data
Technical
The Mobile system must utilize a Web-Services,
service-oriented architecture (SOA). Describe
how.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement. Service Oriented
Architecture (SOA) designed on Microsoft® .NET technology increases operational, reporting and
administrative efficiencies across multiple applications and platforms which provides the basis for
a scalable architecture.
1270
Out of the Box
Motorola
CMOB016
CAD Mobile
Data
Technical
Database backups must be performed online
without DBMS downtime
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1271
Out of the Box
Motorola
CMOB017
CAD Mobile
Data
Technical
The Mobile system must support database
concurrency. Describe how.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement. Due to its redundant
hardware components (network load balanced servers, teamed Network Interface Cards, and
redundant connectivity), PremierOne has no single point of failure. Moreover, the software design
is also redundant, and database replication occurs across databases. The system is transaction-
based and features a stateless design wherever possible.
1272
Out of the Box
Motorola
CMOB018
CAD Mobile
Data
Technical
The Mobile system must support database
replication. Describe how.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement. Motorola utilizes
Microsoft SQL Server Database Mirroring for database high availability. Two database servers are
provided for redundancy and act as mirrored hosts. A third server, the Report Data Warehouse
(RDW) acts as the witness server to manage the mirror. Additionally, the PremierOne architecture
includes data replicated from the primary site SAN to the optional disaster recovery site SAN using
SAN-to-SAN data replication. This process is ongoing and sends transaction data from the primary
site to the disaster recovery site.
1273
Out of the Box
Motorola
CMOB019
CAD Mobile
Data
Technical
The Mobile shall support N-Tier Physical
Architecture
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1274
Out of the Box
Motorola
CMOB020
CAD Mobile
Data
Technical
The server configurations should provide
geographic redundancy. Describe how.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement. Motorola has
included a PremierOne Disaster Recovery solution for geographic redundancy. Please see the
System Description,for a description of the disaster recovery solution.
1275
Out of the Box
Motorola
CMOB021
CAD Mobile
Data
Technical
The mobile data client shall be capability of
roaming across a variety of 4G/5G or faster
data networks, to give the user the most
constant and reliable connectivity.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1276
Out of the Box
Motorola
CMOB022
CAD Mobile
Data
Technical
Ability to provide an acknowledgement to all
received transmissions.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1277
Out of the Box
Motorola
CMOB023
CAD Mobile
Data
Technical
Mobile client must support both laptops and
tablets running Windows 10/11.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1278
Out of the Box
Motorola
CMOB024
CAD Mobile
Data
Technical
The system must support touch-screen
functionality.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1279
Out of the Box
Motorola
CMOB025
CAD Mobile
Data
Technical
The system shall provide a logging feature that
logs adds, changes and/or deletes to any
configuration item.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1280
Out of the Box
Motorola
CMOB026
CAD Mobile
Data
Technical
The system must include a browser based
administration tool for all configuration and
provisioning activity.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1281
Out of the Box
Motorola
CMOB027
CAD Mobile
Data
Technical
The system must integrate to Microsoft
Systems Center Operations Manager for system
operation activities. Describe how.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement. Motorola Solutions
resources will configure Microsoft System Communication Operations Manager (SCOM) and
Prometheus/Grafana to monitor the applications, the hardware and the network edge devices.
These alerts will be sent via SMTP to Motorola Solutions monitoring management tools, which will
process the alert through logical analytics and create a support event, which is routed to a
technician, trained to triage and take corrective action.
1282
Out of the Box
Motorola
CMOB028
CAD Mobile
Data
Technical
The system shall include commonly used pre-
defined reports and an ah-hoc report writing
tool
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1283
Out of the Box
Motorola
CMOB029
CAD Mobile
Data
Technical
Ability to install third-party programs on the
MDC
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1284
Out of the Box
Motorola
CMOB030
CAD Mobile
Data
Technical
System should autodetect and autoconnect to
GPS devices when MDT or tablet is docked,
undocked or re-docked within a logged on
session
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1285
Out of the Box
Motorola
CMOB031
CAD Mobile
Data
Technical
Must provide offer a client side API/SDK for
sharing Query Response and Incident Details
with thrid party client applications
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1286
Out of the Box
Page 58of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CMOB032
CAD Mobile
Data
Operations
The system should process data in real time.
This means any parameter change or database
change should be done while the system is
online. The change should take effect
immediately.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1287
Out of the Box
Motorola
CMOB033
CAD Mobile
Data
Operations
The Mobile database shall process data in real
time. This means any parameter change or
database change is done while the system is on-
line. For instance, if a user agency wanted to
add a column to a status monitor, they can do
this while the Mobile is in-use. The change
takes effect upon the next auto synchronization
or on a manual synchronization request.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1288
Out of the Box
Motorola
CMOB034
CAD Mobile
Data
Operations
Configuration changes shall not require a
shutdown or logoff of the system for
synchronizing updates from the Server to the
Mobile clients.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1289
Out of the Box
Motorola
CMOB035
CAD Mobile
Data
Operations
The system must provide the ability for system
administrators to establish Mobile UI
customizations by Agency for the following:
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1290
Out of the Box
Motorola
CMOB036
CAD Mobile
Data
Operations
Function Keys
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1291
Out of the Box
Motorola
CMOB037
CAD Mobile
Data
Operations
Size of Function Keys
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1292
Out of the Box
Motorola
CMOB038
CAD Mobile
Data
Operations
Status Monitor Columns
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1293
Out of the Box
Motorola
CMOB039
CAD Mobile
Data
Operations
Unit Status Colors
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1294
Out of the Box
Motorola
CMOB040
CAD Mobile
Data
Operations
Mobile Services
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1295
Out of the Box
Motorola
CMOB041
CAD Mobile
Data
Operations
Mobile Command Line display or not display
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1296
Out of the Box
Motorola
CMOB042
CAD Mobile
Data
Operations
Action Buttons for each Service
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1297
Out of the Box
Motorola
CMOB043
CAD Mobile
Data
Operations
Visual Notifications for Incident Updates
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1298
Out of the Box
Motorola
CMOB044
CAD Mobile
Data
Operations
Audible Notifications for Incident Updates
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1299
Out of the Box
Motorola
CMOB045
CAD Mobile
Data
Operations
Query Request Forms and fields within each
form
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1300
Out of the Box
Motorola
CMOB046
CAD Mobile
Data
Operations
The system must provide the ability for system
administrators to establish Mobile UI
customizations by Agency Type for the
following:
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1301
Out of the Box
Motorola
CMOB047
CAD Mobile
Data
Operations
Function Keys
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1302
Out of the Box
Motorola
CMOB048
CAD Mobile
Data
Operations
Size of Function Keys
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1303
Out of the Box
Motorola
CMOB049
CAD Mobile
Data
Operations
Status Monitor Columns
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1304
Out of the Box
Motorola
CMOB050
CAD Mobile
Data
Operations
Unit Status Colors
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1305
Out of the Box
Motorola
CMOB051
CAD Mobile
Data
Operations
Mobile Services
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1306
Out of the Box
Motorola
CMOB052
CAD Mobile
Data
Operations
Mobile Command Line display or not display
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1307
Out of the Box
Motorola
CMOB053
CAD Mobile
Data
Operations
Action Buttons for each Service
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1308
Out of the Box
Motorola
CMOB054
CAD Mobile
Data
Operations
Visual Notifications for Incident Updates
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1309
Out of the Box
Motorola
CMOB055
CAD Mobile
Data
Operations
Audible Notifications for Incident Updates
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1310
Out of the Box
Motorola
CMOB056
CAD Mobile
Data
Operations
Query Request Forms and fields within each
form
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1311
Out of the Box
Motorola
CMOB057
CAD Mobile
Data
Operations
The system must provide the ability to support
local and remote printing
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1312
Out of the Box
Motorola
CMOB058
CAD Mobile
Data
Operations
The system must provide the ability to indicate
when CAD is unable to receive a transmission.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1313
Out of the Box
Motorola
CMOB059
CAD Mobile
Data
Operations
The system must provide the ability to log and
display all times in military (24 hour) clock
format
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1314
Out of the Box
Motorola
CMOB060
CAD Mobile
Data
Operations
The system must provide the ability to log
times in 12-hour format (i.e., HH:MM:SS).
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1315
Out of the Box
Motorola
CMOB061
CAD Mobile
Data
Operations
The system must provide the ability to have a
command line in Mobile for commonly used
functions
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1316
Out of the Box
Motorola
CMOB062
CAD Mobile
Data
Operations
The system must provide the ability to limit
actions to only one or two key strokes for
functions including, but not limited to:
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1317
Out of the Box
Motorola
CMOB063
CAD Mobile
Data
Operations
Logon/logoff
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1318
Out of the Box
Motorola
CMOB064
CAD Mobile
Data
Operations
Run license plate numbers
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1319
Out of the Box
Page 59of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CMOB065
CAD Mobile
Data
Operations
Access to web links
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1320
Out of the Box
Motorola
CMOB066
CAD Mobile
Data
Operations
The system must provide the ability for Unit
status updates from the Mobile Client
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1321
Out of the Box
Motorola
CMOB067
CAD Mobile
Data
Operations
The system must provide the ability to send
street address with Status updates derived
from GPS
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1322
Out of the Box
Motorola
CMOB068
CAD Mobile
Data
Operations
The system must provide the ability to create a
Traffic Stop from a single touch action or single
funciton key
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1323
Out of the Box
Motorola
CMOB069
CAD Mobile
Data
Operations
The system must provide the ability to Self
Dispatch/Self Assign to existing incident
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1324
Out of the Box
Motorola
CMOB070
CAD Mobile
Data
Operations
The system must provide the ability to obtain
drive directions to incidents
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1325
Out of the Box
Motorola
CMOB071
CAD Mobile
Data
Operations
The system must provide the ability to clear a
vehicle stop
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1326
Out of the Box
Motorola
CMOB072
CAD Mobile
Data
Operations
The system must provide the ability to clear
incident call
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1327
Out of the Box
Motorola
CMOB073
CAD Mobile
Data
Operations
The system must provide the ability to look up
premise history
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1328
Out of the Box
Motorola
CMOB074
CAD Mobile
Data
Operations
The system must provide the ability to view
previous incidents
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1329
Out of the Box
Motorola
CMOB075
CAD Mobile
Data
Operations
The system must provide the ability to
accelerate routine data entry tasks (i.e.
workflow functionality) with the following:
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1330
Out of the Box
Motorola
CMOB076
CAD Mobile
Data
Operations
Drop-down lists
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1331
Out of the Box
Motorola
CMOB077
CAD Mobile
Data
Operations
Auto-fill/auto-search
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1332
Out of the Box
Motorola
CMOB078
CAD Mobile
Data
Operations
The system must provide the ability to perform
commands using any of the following methods:
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1333
Out of the Box
Motorola
CMOB079
CAD Mobile
Data
Operations
Easy access toolbar
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1334
Out of the Box
Motorola
CMOB080
CAD Mobile
Data
Operations
Right mouse click
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1335
Out of the Box
Motorola
CMOB081
CAD Mobile
Data
Operations
Agency defined function keys (hot keys)
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1336
Out of the Box
Motorola
CMOB082
CAD Mobile
Data
Operations
Command lines
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1337
Out of the Box
Motorola
CMOB083
CAD Mobile
Data
Operations
Touch screen
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1338
Out of the Box
Motorola
CMOB084
CAD Mobile
Data
Operations
The system must provide the ability to use the
following to invoke a function (e.g., status
change, send message, etc.):
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1339
Out of the Box
Motorola
CMOB085
CAD Mobile
Data
Operations
Command entries on a command line
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1340
Out of the Box
Motorola
CMOB086
CAD Mobile
Data
Operations
Function keys (one touch keys)
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1341
Out of the Box
Motorola
CMOB087
CAD Mobile
Data
Operations
Point-and-click devices (i.e., mouse, trackball,
touch pad)
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1342
Out of the Box
Motorola
CMOB088
CAD Mobile
Data
Operations
Touch screen
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1343
Out of the Box
Motorola
CMOB089
CAD Mobile
Data
Operations
The system must provide a command line
continuously on the MDC screen.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1344
Out of the Box
Motorola
CMOB090
CAD Mobile
Data
Operations
The system must provide the ability to move
forward and backward to complete data fields
without having to retype the entire field (e.g.,
insert and delete, cut and paste).
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1345
Out of the Box
Motorola
CMOB091
CAD Mobile
Data
Operations
The system must provide the ability to page up
and down
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1346
Out of the Box
Motorola
CMOB092
CAD Mobile
Data
Operations
The system must provide the ability to scroll up
and down
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1347
Out of the Box
Motorola
CMOB093
CAD Mobile
Data
Operations
The system must provide the ability to support
agency and agency type configurations for
single touch action buttons and/or function
keys for these functions and statuses:
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1348
Out of the Box
Motorola
CMOB094
CAD Mobile
Data
Operations
Arrived/unit on-scene
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1349
Out of the Box
Motorola
CMOB095
CAD Mobile
Data
Operations
Retrieve call information
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1350
Out of the Box
Motorola
CMOB096
CAD Mobile
Data
Operations
Clear/available
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1351
Out of the Box
Motorola
CMOB097
CAD Mobile
Data
Operations
Code 3 (lights and sirens on)
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1352
Out of the Box
Motorola
CMOB098
CAD Mobile
Data
Operations
Display message
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1353
Out of the Box
Motorola
CMOB099
CAD Mobile
Data
Operations
Disposition call/Close
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1354
Out of the Box
Motorola
CMOB100
CAD Mobile
Data
Operations
Emergency Activation
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1355
Out of the Box
Motorola
CMOB101
CAD Mobile
Data
Operations
En route to station
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1356
Out of the Box
Page 60of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CMOB102
CAD Mobile
Data
Operations
En route/unit responding
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1357
Out of the Box
Motorola
CMOB103
CAD Mobile
Data
Operations
In-service
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1358
Out of the Box
Motorola
CMOB104
CAD Mobile
Data
Operations
In-service/report writing
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1359
Out of the Box
Motorola
CMOB105
CAD Mobile
Data
Operations
Available on Radio
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1360
Out of the Box
Motorola
CMOB106
CAD Mobile
Data
Operations
Available in Quarters
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1361
Out of the Box
Motorola
CMOB107
CAD Mobile
Data
Operations
Map access
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1362
Out of the Box
Motorola
CMOB108
CAD Mobile
Data
Operations
Out-of-service
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1363
Out of the Box
Motorola
CMOB109
CAD Mobile
Data
Operations
Premise information
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1364
Out of the Box
Motorola
CMOB110
CAD Mobile
Data
Operations
Unit status Monitor
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1365
Out of the Box
Motorola
CMOB111
CAD Mobile
Data
Operations
Active Incident (My Incident)
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1366
Out of the Box
Motorola
CMOB112
CAD Mobile
Data
Operations
Action to make yourself the Primary Unit
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1367
Out of the Box
Motorola
CMOB113
CAD Mobile
Data
Operations
Vehicle registration check
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1368
Out of the Box
Motorola
CMOB114
CAD Mobile
Data
Operations
Vehcile by Plate Query
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1369
Out of the Box
Motorola
CMOB115
CAD Mobile
Data
Operations
Traffic Stop
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1370
Out of the Box
Motorola
CMOB116
CAD Mobile
Data
Operations
Ability to temporarily lock the mobile client
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1371
Out of the Box
Motorola
CMOB117
CAD Mobile
Data
Operations
Ability to unlock the Mobile Client by entering a
password
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1372
Out of the Box
Motorola
CMOB118
CAD Mobile
Data
Operations
Ability to display the following information on
the screen during normal operations:
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1373
Out of the Box
Motorola
CMOB119
CAD Mobile
Data
Operations
Availability of wireless connectivity
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1374
Out of the Box
Motorola
CMOB120
CAD Mobile
Data
Operations
GPS Device connectivity status
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1375
Out of the Box
Motorola
CMOB121
CAD Mobile
Data
Operations
Online/Offline indication
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1376
Out of the Box
Motorola
CMOB122
CAD Mobile
Data
Operations
Current status of Mobile Unit
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1377
Out of the Box
Motorola
CMOB123
CAD Mobile
Data
Operations
Message alert
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1378
Out of the Box
Motorola
CMOB124
CAD Mobile
Data
Operations
Unit ID
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1379
Out of the Box
Motorola
CMOB125
CAD Mobile
Data
Access
The system must require both user
identification and password or user code.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1380
Out of the Box
Motorola
CMOB126
CAD Mobile
Data
Access
The system must provide the ability to log-on
multiple individuals per unit.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1381
Out of the Box
Motorola
CMOB127
CAD Mobile
Data
Access
The system must provide the ability to assign
crew members and designate crew member
radios when logging on as a Mobile Unit
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1382
Out of the Box
Motorola
CMOB128
CAD Mobile
Data
Access
The system must provide the ability to assign
up to 10 crew members and designate crew
member radios when logging on as a Mobile
Unit
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1383
Out of the Box
Motorola
CMOB129
CAD Mobile
Data
Access
The system must provide the ability to
automatically log-off prior Units upon entry of a
log-on command by a new user with the same
Unit ID.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1384
Out of the Box
Motorola
CMOB130
CAD Mobile
Data
Access
The system must provide the ability, when
there are multiple users logged onto one MDC,
to allow one user to log-off the system while
allowing another to remain logged on.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1385
Out of the Box
Motorola
CMOB131
CAD Mobile
Data
Access
The system must provide the ability to support
an automatic download of software/files at log-
on without interfering with operational
performance (background application).
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1386
Out of the Box
Motorola
CMOB132
CAD Mobile
Data
Access
The system must provide the ability to Ability to
automatically update unit roster information
based on MDC log-on information.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1387
Out of the Box
Motorola
CMOB133
CAD Mobile
Data
Access
The system must provide the ability to Ability to
separate MDC log off from designating status as
off-shift.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1388
Out of the Box
Motorola
CMOB134
CAD Mobile
Data
Access
The system must provide the ability to Ability to
separate MDC log on from designating status as
on-shift.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1389
Out of the Box
Motorola
CMOB135
CAD Mobile
Data
Access
The system must Allow users to logon to
Mobile as Units from a different agency
enabling multi-agency and multi-jurisdictional
support with a single User Account
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1390
Out of the Box
Page 61of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CMOB136
CAD Mobile
Data
Access
The system must Allow a user to logon to
Mobile and designate a Vehicle from another
agency allowing users from one agency to
provide services and drive vehicles on behalf of
another agency
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1391
Out of the Box
Motorola
CMOB137
CAD Mobile
Data
Access
The system must Allow a user to logon to
Mobile and designate a Radio from another
agency allowing a single agency to own and
manage radios used by personnel in other
agencies
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1392
Out of the Box
Motorola
CMOB138
CAD Mobile
Data
Incident Dispatch
Management
The system must provide the ability to receive
dispatches on the MDC.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1393
Out of the Box
Motorola
CMOB139
CAD Mobile
Data
Incident Dispatch
Management
The system must provide the ability to
accurately timestamp all field and dispatch
transmissions to and from MDC
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1394
Out of the Box
Motorola
CMOB140
CAD Mobile
Data
Incident Dispatch
Management
The system must provide the ability to provide
visual or audible alert to indicate that a
dispatch has arrived.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1395
Out of the Box
Motorola
CMOB141
CAD Mobile
Data
Incident Dispatch
Management
The system must provide the ability to both
open Incident details and update unit status to
"enroute" with a single touch of the screen
upon receipt of a dispatch notification
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1396
Out of the Box
Motorola
CMOB142
CAD Mobile
Data
Incident Dispatch
Management
The system must provide the ability to provide
visual or audible alert to indicate that an
incident has been updated
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1397
Out of the Box
Motorola
CMOB143
CAD Mobile
Data
Incident Dispatch
Management
The system must provide the ability to provide
a distinguishable visual and audible alert for
high priority calls (as defined by the agency).
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1398
Out of the Box
Motorola
CMOB144
CAD Mobile
Data
Incident Dispatch
Management
The system must provide the ability to access
and read all call comments associated with a
call
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1399
Out of the Box
Motorola
CMOB145
CAD Mobile
Data
Incident Dispatch
Management
The system must provide the ability to display
visual alerts for high priority premise/hazard
information
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1400
Out of the Box
Motorola
CMOB146
CAD Mobile
Data
Incident Dispatch
Management
The system must provide the ability to present
audible alerts for high priority premise/hazard
information
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1401
Out of the Box
Motorola
CMOB147
CAD Mobile
Data
Incident Dispatch
Management
Share incident and query information for field
reports (no duplicate data entry)
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1402
Out of the Box
Motorola
CMOB148
CAD Mobile
Data
Incident Dispatch
Management
The system must provide the ability to display
the following dispatch information upon
dispatch of unit to an incident:
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1403
Out of the Box
Motorola
CMOB149
CAD Mobile
Data
Incident Dispatch
Management
Assisting unit(s)
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1404
Out of the Box
Motorola
CMOB150
CAD Mobile
Data
Incident Dispatch
Management
Building plans
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1405
Out of the Box
Motorola
CMOB151
CAD Mobile
Data
Incident Dispatch
Management
Comments/narrative (unlimited)
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1406
Out of the Box
Motorola
CMOB152
CAD Mobile
Data
Incident Dispatch
Management
Complainant Name/Contact Info/Address
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1407
Out of the Box
Motorola
CMOB153
CAD Mobile
Data
Incident Dispatch
Management
Date and time incident entered
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1408
Out of the Box
Motorola
CMOB154
CAD Mobile
Data
Incident Dispatch
Management
Document associated with a particular location Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1409
Out of the Box
Motorola
CMOB155
CAD Mobile
Data
Incident Dispatch
Management
Incident location with cross streets
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1410
Out of the Box
Motorola
CMOB156
CAD Mobile
Data
Incident Dispatch
Management
Incident priority (e.g., user-defined or defined
by incident code )
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1411
Out of the Box
Motorola
CMOB157
CAD Mobile
Data
Incident Dispatch
Management
Incident type
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1412
Out of the Box
Motorola
CMOB158
CAD Mobile
Data
Incident Dispatch
Management
Radio Channel/Talk Group
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1413
Out of the Box
Motorola
CMOB159
CAD Mobile
Data
Incident Dispatch
Management
Display all assigned units on an incident
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1414
Out of the Box
Motorola
CMOB160
CAD Mobile
Data
Incident Dispatch
Management
Dynamically display a visual unit status
indicator for each unit assigned to an incident
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1415
Out of the Box
Motorola
CMOB161
CAD Mobile
Data
Incident Dispatch
Management
New or developing information in free form
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1416
Out of the Box
Motorola
CMOB162
CAD Mobile
Data
Incident Dispatch
Management
Suspect Information (name, description,
location)
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1417
Out of the Box
Motorola
CMOB163
CAD Mobile
Data
Incident Dispatch
Management
Phone number at incident location (if different) Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1418
Out of the Box
Motorola
CMOB164
CAD Mobile
Data
Incident Dispatch
Management
Prior incident information
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1419
Out of the Box
Motorola
CMOB165
CAD Mobile
Data
Incident Dispatch
Management
Premise history information
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1420
Out of the Box
Motorola
CMOB166
CAD Mobile
Data
Incident Dispatch
Management
Recommended route via voice and graphic
drive directions
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1421
Out of the Box
Motorola
CMOB167
CAD Mobile
Data
Incident Dispatch
Management
Reporting party name, phone number, address
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1422
Out of the Box
Motorola
CMOB168
CAD Mobile
Data
Incident Dispatch
Management
Attachments such as photos, audio recording,
or streaming video
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1423
Out of the Box
Page 62of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CMOB169
CAD Mobile
Data
Incident Dispatch
Management
The system must provide the ability to receive
supplemental incident information (e.g.,
location, suspect, vehicle or other information,
etc.) without interrupting/overlaying current
screen:
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1424
Out of the Box
Motorola
CMOB170
CAD Mobile
Data
Incident Dispatch
Management
Visual alert
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1425
Out of the Box
Motorola
CMOB171
CAD Mobile
Data
Incident Dispatch
Management
Audible alert
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1426
Out of the Box
Motorola
CMOB172
CAD Mobile
Data
Incident Dispatch
Management
The system must provide the ability to receive
notification of dispatcher-initiated changes to
an incident (e.g., supplemental information,
unit reassignments, incident cancellation,
preempting off call, etc.) without
interrupting/overlaying current screen:
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1427
Out of the Box
Motorola
CMOB173
CAD Mobile
Data
Incident Dispatch
Management
Visual alert
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1428
Out of the Box
Motorola
CMOB174
CAD Mobile
Data
Incident Dispatch
Management
Audible alert
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1429
Out of the Box
Motorola
CMOB175
CAD Mobile
Data
Incident Dispatch
Management
The system must provide the ability for mobile
screen to update automatically as new
information is added to a call (without user
reqired interaction)
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1430
Out of the Box
Motorola
CMOB176
CAD Mobile
Data
Incident Dispatch
Management
The system must provide the ability to add
report numbers to an incident from the Mobile
Client
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1431
Out of the Box
Motorola
CMOB177
CAD Mobile
Data
Incident Dispatch
Management
The system must provide the ability to delete
report numbers associated with an incident
from the Mobile Client
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1432
Out of the Box
Motorola
CMOB178
CAD Mobile
Data
Incident Dispatch
Management
The system must provide the ability to update
incident type and location from the Mobile
client
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1433
Out of the Box
Motorola
CMOB179
CAD Mobile
Data
Incident Dispatch
Management
The system must provide the ability to add
incident comments from the Mobile client
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1434
Out of the Box
Motorola
CMOB180
CAD Mobile
Data
Incident Dispatch
Management
The system must provide the ability to change
your assigment from backup to the primary unit
on an incident from a single key stroke
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1435
Out of the Box
Motorola
CMOB181
CAD Mobile
Data
Incident Dispatch
Management
The system must provide the ability to add or
update persons associated with the incident
from the Mobile Client
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1436
Out of the Box
Motorola
CMOB182
CAD Mobile
Data
Incident Dispatch
Management
The system must provide the ability to add or
update vehicles associated with the incident
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1437
Out of the Box
Motorola
CMOB183
CAD Mobile
Data
Incident Dispatch
Management
The system must provide the ability to import
person or vehicles into an incident from a query
response
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1438
Out of the Box
Motorola
CMOB184
CAD Mobile
Data
Incident Dispatch
Management
The system must provide the ability to request
a contractor such as a Tow Company or Taxi
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1439
Out of the Box
Motorola
CMOB185
CAD Mobile
Data
Incident Dispatch
Management
The system must provide the ability to provide
/ recommend taxi and tow compandies based
on contractor rotation schedules
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1440
Out of the Box
Motorola
CMOB186
CAD Mobile
Data
Incident Dispatch
Management
The system must provide the ability to update
assigned contract information from the MDT
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1441
Out of the Box
Motorola
CMOB187
CAD Mobile
Data
Incident Dispatch
Management
The system must provide the ability to view
assigned contractors and contractor contact
information for each vehicle and person
associated to an incident
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1442
Out of the Box
Motorola
CMOB188
CAD Mobile
Data
Incident Dispatch
Management
The system must provide the ability to add and
update/maintain Premise information on the
MDT
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1443
Out of the Box
Motorola
CMOB189
CAD Mobile
Data
Incident Dispatch
Management
The system must provide access to all
associated query results for an incident/call
that were submitted from the Mobile Client
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1444
Out of the Box
Motorola
CMOB190
CAD Mobile
Data
Incident Dispatch
Management
The system must provide access to all
associated query results for an incident/call
that were submitted from a CAD Client
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1445
Out of the Box
Motorola
CMOB191
CAD Mobile
Data
Incident Dispatch
Management
The system must provide the ability for changes
and updates to be made interactively and
instantly transmitted to or from the CAD
system
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1446
Out of the Box
Motorola
CMOB192
CAD Mobile
Data
Incident Dispatch
Management
The system must provide the ability to auto-
populate a street address from a Mobile Unit
GPS location when creating a field initiated
event from the Mobile client
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1447
Out of the Box
Motorola
CMOB193
CAD Mobile
Data
Incident Dispatch
Management
The system must provide the ability to auto-
populate a street address from a Mobile Unit
GPS location when updating a field initiated
event from the Mobile client
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1448
Out of the Box
Page 63of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CMOB194
CAD Mobile
Data
Incident Dispatch
Management
The system must provide the ability to perform
agency-defined CAD Incident update functions
subject to access privileges (e.g., adding
miscellaneous text comments to a call; adding
disposition code to a call, etc.)
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1449
Out of the Box
Motorola
CMOB195
CAD Mobile
Data
Incident Dispatch
Management
The system must provide the ability to display
Console ID with comments when an Incident
Comment is entered from a CAD Workstation
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1450
Out of the Box
Motorola
CMOB196
CAD Mobile
Data
Incident Dispatch
Management
The system must provide the ability to display
Unit ID with comments when an Incident
Comment is entered from a Mobile or
Handheld Workstation
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1451
Out of the Box
Motorola
CMOB197
CAD Mobile
Data
Incident Dispatch
Management
The system must provide the ability to display
User ID the User with comments to identify
who entered an Incident Comment
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1452
Out of the Box
Motorola
CMOB198
CAD Mobile
Data
Incident Dispatch
Management
The system must provide the ability to display
Timestamp indicating the time an Incident
Comment was entered
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1453
Out of the Box
Motorola
CMOB199
CAD Mobile
Data
Incident Dispatch
Management
The system must provide the ability to
dynamically update Incident Comments on any
incident that you view, regardless of wheter
you are assigned to the incident or not without
requiring an action from the Mobile User to
receive the updates
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1454
Out of the Box
Motorola
CMOB200
CAD Mobile
Data
Incident Dispatch
Management
The system must provide the ability to
dynamically refresh incidents that you are
assigned when any update is made to the
Incident without requiring an action from the
Mobile User to receive the incident refresh
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1455
Out of the Box
Motorola
CMOB201
CAD Mobile
Data
Incident History
The system must provide the ability to search
historical incidents from a Mobile Form
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1456
Out of the Box
Motorola
CMOB202
CAD Mobile
Data
Incident History
The system must provide the ability to search
prior incidents by associated persons first
and/or last name
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1457
Out of the Box
Motorola
CMOB203
CAD Mobile
Data
Incident History
The system must provide the ability to search
prior incidents by associated vehicle plate
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1458
Out of the Box
Motorola
CMOB204
CAD Mobile
Data
Incident History
The system must provide the ability to search
prior incidents by Disposition Code or
Disposition Description
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1459
Out of the Box
Motorola
CMOB205
CAD Mobile
Data
Incident History
The system must provide the ability to search
prior incidents by responding unit id
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1460
Out of the Box
Motorola
CMOB206
CAD Mobile
Data
Incident History
The system must provide the ability to search
prior incidents by Incident/event Address
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1461
Out of the Box
Motorola
CMOB207
CAD Mobile
Data
Incident History
The system must provide the ability to search
prior incidents by date range
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1462
Out of the Box
Motorola
CMOB208
CAD Mobile
Data
Incident History
The system must provide the ability to search
comments from CAD or Mobile
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1463
Out of the Box
Motorola
CMOB209
CAD Mobile
Data
Incident History
The system must provide the ability to view
Incident History on Active and Closed Calls
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1464
Out of the Box
Motorola
CMOB210
CAD Mobile
Data
Incident History
The system must provide the ability to filter
Incident History to show only Comments
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1465
Out of the Box
Motorola
CMOB211
CAD Mobile
Data
Incident History
The system must provide the ability to filter
Incident History to show only Unit Status
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1466
Out of the Box
Motorola
CMOB212
CAD Mobile
Data
Unit History
The system must provide the ability to search
unit history for your self or others by User ID
and date range
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1467
Out of the Box
Motorola
CMOB213
CAD Mobile
Data
Unit History
The system must provide the ability to search
unit history for your self or others by Unit ID
and date range
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1468
Out of the Box
Motorola
CMOB214
CAD Mobile
Data
Unit History
The system must provide the ability to filter
Unit History to show only Unit Status Updates
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1469
Out of the Box
Motorola
CMOB215
CAD Mobile
Data
Unit History
The system must provide the ability to filter
Unit History to show only Incident Updates
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1470
Out of the Box
Motorola
CMOB216
CAD Mobile
Data
Unit History
The system must provide the ability to filter
Unit History to show only State/NCIC Query
Requests
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1471
Out of the Box
Motorola
CMOB217
CAD Mobile
Data
Unit Management
The system must provide the ability to update
Unit Activity Codes from Mobile such as DUI
Task Force, Click-it or Ticket Task Force, or
MADD sponsored Activities
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1472
Out of the Box
Motorola
CMOB218
CAD Mobile
Data
Unit Management
The system must provide the ability to update
Unit Capabilities and Equipment from the
Mobile Client (examples: Drone, AR-15,K9,
Shotgun)
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1473
Out of the Box
Page 64of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CMOB219
CAD Mobile
Data
Unit Management
The system must provide the ability to update
Unit/User skills from the Mobile Client
(examples: Spanish speaking, Advanced Life
Support, Basic Life Support, Dive Team, Lake
Patrol)
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1474
Out of the Box
Motorola
CMOB220
CAD Mobile
Data
Unit Management
The system must provide the ability to search
personnel skills on or off duty
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1475
Out of the Box
Motorola
CMOB221
CAD Mobile
Data
Unit Management
The system must provide the ability to
designate and display colors to diplay in Unit
Status Monitors as a visual unit status
indication
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1476
Out of the Box
Motorola
CMOB222
CAD Mobile
Data
Unit Management
The system must provide the ability to
designate and display colors to indicate Unit
Status for each unit assigned to an incident
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1477
Out of the Box
Motorola
CMOB223
CAD Mobile
Data
Unit Management
The system must provide the ability to
dynamically update the unit status color on
incidents as each unit update occurs without
requiring an action by the Mobile user to
receive the update
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1478
Out of the Box
Motorola
CMOB224
CAD Mobile
Data
Unit Management
The system must provide the ability to auto-
populate a street address from a Mobile Unit
GPS location when updating unit status from
the Mobile Client
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1479
Out of the Box
Motorola
CMOB225
CAD Mobile
Data
Unit Management
The system must provide the ability to require a
Comments with Status Updates for selected
Unit Status Codes
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1480
Out of the Box
Motorola
CMOB226
CAD Mobile
Data
Unit Management
The system must provide the ability to require a
Location with Status Updates for selected Unit
Status Codes
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1481
Out of the Box
Motorola
CMOB227
CAD Mobile
Data
Unit Management
The system must provide the ability to require a
odometer/mileage with Status Updates for
selected Unit Status Codes
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1482
Out of the Box
Motorola
CMOB228
CAD Mobile
Data
Unit Management
The system must provide the ability to transmit
unit status information to the CAD system in
real time.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1483
Out of the Box
Motorola
CMOB229
CAD Mobile
Data
Unit Management
The system must provide the ability to update
Unit status from the Mobile client via
dropdown selection
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1484
Out of the Box
Motorola
CMOB230
CAD Mobile
Data
Unit Management
The system must provide the ability to update
Unit status from the Mobile client via function
key
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1485
Out of the Box
Motorola
CMOB231
CAD Mobile
Data
Unit Management
The system must provide the ability to update
unit skills and capabilities from the Mobile
Client
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1486
Out of the Box
Motorola
CMOB232
CAD Mobile
Data
Unit Management
The system must provide the ability to update
activitiy codes from the Mobile Client for
tracking special assignments such as MADD,
DUI Task Force, Click it or Ticket initiatives
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1487
Out of the Box
Motorola
CMOB233
CAD Mobile
Data
Unit Management
Allow users to change jurisdictional geography
(Area, Station) from the Mobile Client without
logging off
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1488
Out of the Box
Motorola
CMOB234
CAD Mobile
Data
Unit Management
Allow users to change roles (Patrol, Swat,
Command) from the Mobile Client without
logging off
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1489
Out of the Box
Motorola
CMOB235
CAD Mobile
Data
Emergecy
Notifications
The system must provide the ability to Activate
a Deputy in Emergency Notification from a
single touch action
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1490
Out of the Box
Motorola
CMOB236
CAD Mobile
Data
Emergecy
Notifications
The system must provide the ability to confirm
or cancel an Emergency Notification before
broadcasting in the event of accidental
activation
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1491
Out of the Box
Motorola
CMOB237
CAD Mobile
Data
Emergecy
Notifications
The system must automatically transmit the
following information in an emergency
situation:
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1492
Out of the Box
Motorola
CMOB238
CAD Mobile
Data
Emergecy
Notifications
User name
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1493
Out of the Box
Motorola
CMOB239
CAD Mobile
Data
Emergecy
Notifications
User ID
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1494
Out of the Box
Motorola
CMOB240
CAD Mobile
Data
Emergecy
Notifications
Location
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1495
Out of the Box
Motorola
CMOB241
CAD Mobile
Data
Emergecy
Notifications
Reference to incident
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1496
Out of the Box
Motorola
CMOB242
CAD Mobile
Data
Emergecy
Notifications
The system must offer single touch on an
Emergency Alert Notification to display the
location of a Unit in Emergency on a map
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1497
Out of the Box
Motorola
CMOB243
CAD Mobile
Data
Emergecy
Notifications
The system must offer single touch on an
Emergency Alert Notification to display the
incident that the Unit in Emergency is assigned
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1498
Out of the Box
Motorola
CMOB244
CAD Mobile
Data
Emergecy
Notifications
The system must provide the ability to
configure emergency key activation by agency-
defined key combination.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1499
Out of the Box
Page 65of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CMOB245
CAD Mobile
Data
Emergecy
Notifications
The system must provide the ability to send to
all mobile and CAD users (except the sender) an
emergency notification with unit ID and
location (if known) when the emergency key is
activated.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1500
Out of the Box
Motorola
CMOB246
CAD Mobile
Data
Emergecy
Notifications
The system must provide the ability to prevent
emergency notification from appearing on the
sender's screen.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1501
Out of the Box
Motorola
CMOB247
CAD Mobile
Data
Emergecy
Notifications
The system must provide the ability for the
MDC screen to revert to its prior view after the
user dismisses an emergency message.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1502
Out of the Box
Motorola
CMOB248
CAD Mobile
Data
Status Monitors
The system must provide the ability to provide
a Incident and Unit Status Monitors with the
following:
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1503
Out of the Box
Motorola
CMOB249
CAD Mobile
Data
Status Monitors
Current/active calls for multiple agencies
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1504
Out of the Box
Motorola
CMOB250
CAD Mobile
Data
Status Monitors
Pending calls
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1505
Out of the Box
Motorola
CMOB251
CAD Mobile
Data
Status Monitors
Unit Status Monitor for multiple agencies
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1506
Out of the Box
Motorola
CMOB252
CAD Mobile
Data
Status Monitors
Logged on Users
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1507
Out of the Box
Motorola
CMOB253
CAD Mobile
Data
Status Monitors
User's Closed Incidents for past 24 hours
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1508
Out of the Box
Motorola
CMOB254
CAD Mobile
Data
Status Monitors
The system must provide the ability to view
pending calls
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1509
Out of the Box
Motorola
CMOB255
CAD Mobile
Data
Status Monitors
The system must provide the ability to view
active calls
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1510
Out of the Box
Motorola
CMOB256
CAD Mobile
Data
Status Monitors
The system must provide the ability to self
dispatch / self assign to an active or pending
call from a monitor
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1511
Out of the Box
Motorola
CMOB257
CAD Mobile
Data
Status Monitors
The system must provide the ability to locate
and display a incident on the Mobile map from
a single touch of a Incident Monitor
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1512
Out of the Box
Motorola
CMOB258
CAD Mobile
Data
Status Monitors
The system must provide the ability to locate
and display a unit on the Mobile map from a
single touch of the Unit Status Monitor
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1513
Out of the Box
Motorola
CMOB259
CAD Mobile
Data
Status Monitors
The system must provide the ability to address
a message to one or multiple units selected
from a Unit Status Monitor
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1514
Out of the Box
Motorola
CMOB260
CAD Mobile
Data
Status Monitors
The system must provide the ability to select a
unit from a Monitor to see the Unit Details
including Persons assigned, Skills and
Capabilities, Assigned Incident, activity Activity
Code
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1515
Out of the Box
Motorola
CMOB261
CAD Mobile
Data
Status Monitors
The system must provide the ability to select an
Incident from a Monitor to see full Incident
Details
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1516
Out of the Box
Motorola
CMOB262
CAD Mobile
Data
CJIS Security
Compliance
The Mobile system must provide a customer
configurable password management system.
Passwords must be configured for expiration,
minimum length, character types and numbers.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1517
Out of the Box
Motorola
CMOB263
CAD Mobile
Data
CJIS Security
Compliance
The mobile system must provide CJIS 5.4 FIPS
140-2 encryption including:
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1518
Out of the Box
Motorola
CMOB264
CAD Mobile
Data
CJIS Security
Compliance
128 bit or 256 bit AES encryption
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1519
Out of the Box
Motorola
CMOB265
CAD Mobile
Data
CJIS Security
Compliance
Encrypted data at rest
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1520
Out of the Box
Motorola
CMOB266
CAD Mobile
Data
CJIS Security
Compliance
Encrypted data in-motion
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1521
Out of the Box
Motorola
CMOB267
CAD Mobile
Data
CJIS Security
Compliance
Encrypted data over-the-air
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1522
Out of the Box
Motorola
CMOB268
CAD Mobile
Data
CJIS Security
Compliance
The Mobile System must utlizie eCertificates
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1523
Out of the Box
Motorola
CMOB269
CAD Mobile
Data
Query and Audits
The system must provide the ability to log all
mobile activities (e.g., NLETS queries, messages,
failed logon attempts) by the following:
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1524
Out of the Box
Motorola
CMOB270
CAD Mobile
Data
Query and Audits
MDC
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1525
Out of the Box
Motorola
CMOB271
CAD Mobile
Data
Query and Audits
Case number (if applicable)
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1526
Out of the Box
Motorola
CMOB272
CAD Mobile
Data
Query and Audits
Date and time of transmission
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1527
Out of the Box
Motorola
CMOB273
CAD Mobile
Data
Query and Audits
Incident number (if applicable)
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1528
Out of the Box
Motorola
CMOB274
CAD Mobile
Data
Query and Audits
IP Address
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1529
Out of the Box
Motorola
CMOB275
CAD Mobile
Data
Query and Audits
ORI
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1530
Out of the Box
Motorola
CMOB276
CAD Mobile
Data
Query and Audits
Radio device ID
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1531
Out of the Box
Motorola
CMOB277
CAD Mobile
Data
Query and Audits
Terminal ID
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1532
Out of the Box
Page 66of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CMOB278
CAD Mobile
Data
Query and Audits
Unit call sign
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1533
Out of the Box
Motorola
CMOB279
CAD Mobile
Data
Query and Audits
User ID
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1534
Out of the Box
Motorola
CMOB280
CAD Mobile
Data
Query and Audits
User name
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1535
Out of the Box
Motorola
CMOB281
CAD Mobile
Data
Query and Audits
RMS inquiries
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1536
Out of the Box
Motorola
CMOB282
CAD Mobile
Data
Query and Audits
Inquiries to NLETS/NCIC
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1537
Out of the Box
Motorola
CMOB283
CAD Mobile
Data
Query and Audits
Inquiries to designated local, state and national
databases
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1538
Out of the Box
Motorola
CMOB284
CAD Mobile
Data
Query and Audits
Access and display of electronic photos within a
query response
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1539
Out of the Box
Motorola
CMOB285
CAD Mobile
Data
Query and Audits
Query specific unit status
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1540
Out of the Box
Motorola
CMOB286
CAD Mobile
Data
Query and Audits
Query specific unit location
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1541
Out of the Box
Motorola
CMOB287
CAD Mobile
Data
Query and Audits
Display thumbnail photos on MDC
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1542
Out of the Box
Motorola
CMOB288
CAD Mobile
Data
Query and Audits
The system must support barcode scan of
drivers license to submit a person query
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1543
Out of the Box
Motorola
CMOB289
CAD Mobile
Data
Query and Audits
The system must provide the ability to auto-
populate a street address from a Mobile Unit
GPS location when submitting a vehicle or
person query
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1544
Out of the Box
Motorola
CMOB290
CAD Mobile
Data
Query and Audits
The system must provide the ability to access
any query form with a single key stroke
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1545
Out of the Box
Motorola
CMOB291
CAD Mobile
Data
Query and Audits
The system must provide the ability to use
predefined data entry forms/screens (masks) to
minimize data transmitted during queries
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1546
Out of the Box
Motorola
CMOB292
CAD Mobile
Data
Query and Audits
The system must provide the ability for agency
to create standard screen formats for all agency
inquiries
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1547
Out of the Box
Motorola
CMOB293
CAD Mobile
Data
Query and Audits
The system must provide pre-defined data
entry/query forms should include, but not be
limited to:
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1548
Out of the Box
Motorola
CMOB294
CAD Mobile
Data
Query and Audits
Articles
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1549
Out of the Box
Motorola
CMOB295
CAD Mobile
Data
Query and Audits
Accident Investigation
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1550
Out of the Box
Motorola
CMOB296
CAD Mobile
Data
Query and Audits
Boats
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1551
Out of the Box
Motorola
CMOB297
CAD Mobile
Data
Query and Audits
Driver license query
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1552
Out of the Box
Motorola
CMOB298
CAD Mobile
Data
Query and Audits
License plate query
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1553
Out of the Box
Motorola
CMOB299
CAD Mobile
Data
Query and Audits
License tabs
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1554
Out of the Box
Motorola
CMOB300
CAD Mobile
Data
Query and Audits
Log-on/log-off
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1555
Out of the Box
Motorola
CMOB301
CAD Mobile
Data
Query and Audits
Missing person information
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1556
Out of the Box
Motorola
CMOB302
CAD Mobile
Data
Query and Audits
Name
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1557
Out of the Box
Motorola
CMOB303
CAD Mobile
Data
Query and Audits
Premise information query
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1558
Out of the Box
Motorola
CMOB304
CAD Mobile
Data
Query and Audits
Location Information query for premise
records, hazards, and prior incidents
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1559
Out of the Box
Motorola
CMOB305
CAD Mobile
Data
Query and Audits
Previous events
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1560
Out of the Box
Motorola
CMOB306
CAD Mobile
Data
Query and Audits
The system must allow single key stroke to
attach a query response to an the users active
incident
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1561
Out of the Box
Motorola
CMOB307
CAD Mobile
Data
Query and Audits
The system must allow single key stroke to
import data from a query response to update
persons and/or vehicles associated with the
users active incident
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1562
Out of the Box
Motorola
CMOB308
CAD Mobile
Data
Query and Audits
The system must allow single touch action to
create a traffic stop populated vehicle details
from a selected query response
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1563
Out of the Box
Motorola
CMOB309
CAD Mobile
Data
Query and Audits
The system must allow query response to be
sent to other units through a message
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1564
Out of the Box
Motorola
CMOB310
CAD Mobile
Data
Query and Audits
The system must provide the ability to
distribute query results to all units assigned to
the same call as the Mobile User, from the
Mobile client
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1565
Out of the Box
Motorola
CMOB311
CAD Mobile
Data
Query and Audits
The system must provide the ability to
distribute query results to all units assigned to
the same call as the Mobile User from CAD
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1566
Out of the Box
Motorola
CMOB312
CAD Mobile
Data
Query and Audits
The system must provide the ability to save all
previous license plate searches until user clears
data or logs off of the Mobile Client
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1567
Out of the Box
Page 67of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CMOB313
CAD Mobile
Data
Query and Audits
The system must provide the ability to produce
a visible (e.g. record is in red) and audible (e.g.
special beep tone) alarm when a return
contains a record marked as potentially
hazardous "hot hit"
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1568
Out of the Box
Motorola
CMOB314
CAD Mobile
Data
Query and Audits
The system must provide the ability to produce
a visible and audible alert when a record
returns a record containing a stolen vehicle
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1569
Out of the Box
Motorola
CMOB315
CAD Mobile
Data
Query and Audits
The system must provide the ability to drill
down into query returns regarding a potentially
hazardous subject, vehicle, and/or location to
find the details of that hazard
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1570
Out of the Box
Motorola
CMOB316
CAD Mobile
Data
Query and Audits
The system must provide the ability to select
results from Records/RMS queries and drill
down for detailed information
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1571
Out of the Box
Motorola
CMOB317
CAD Mobile
Data
Query and Audits
The system must provide the ability to generate
a traffic stop with a single touch, that imports
vehicle information from a selected query
result into the incident
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1572
Out of the Box
Motorola
CMOB318
CAD Mobile
Data
Query and Audits
The system must provide the ability to scan a 2-
D drivers license barcode to submit a query
from Mobile
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1573
Out of the Box
Motorola
CMOB319
CAD Mobile
Data
Query and Audits
The system must provide the ability to scan a 2-
D vehicle registration barcode to submit a
query from Mobile
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1574
Out of the Box
Motorola
CMOB320
CAD Mobile
Data
Messaging
The system must provide the ability to store
messages for later viewing
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1575
Out of the Box
Motorola
CMOB321
CAD Mobile
Data
Messaging
The system must provide the ability for host
computer to store unread messages when user
logs off
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1576
Out of the Box
Motorola
CMOB322
CAD Mobile
Data
Messaging
The system must provide the ability for users to
save BOLOs for later retrieval, even after
session log-off
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1577
Out of the Box
Motorola
CMOB323
CAD Mobile
Data
Messaging
The system must provide the ability to sort
stored messages based on priority and then by
date/time
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1578
Out of the Box
Motorola
CMOB324
CAD Mobile
Data
Messaging
The system must provide the ability for
messages to be able to be sorted by most
recent or first call received
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1579
Out of the Box
Motorola
CMOB325
CAD Mobile
Data
Messaging
The system must provide the ability to select a
row in an Incident Monitor to address a
message to all units assigned to the
corresponding incident
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1580
Out of the Box
Motorola
CMOB326
CAD Mobile
Data
Messaging
The system must provide the ability to select a
row or multiple rows on a Unit Monitor to
address a message to one or multiple units
based on the selected row
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1581
Out of the Box
Motorola
CMOB327
CAD Mobile
Data
Messaging
The system must provide the ability to address
a message to all units assigned to an incident by
selecting a link within the Incident Display
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1582
Out of the Box
Motorola
CMOB328
CAD Mobile
Data
Messaging
The system must provide Electronic messaging
between two or more MDCs
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1583
Out of the Box
Motorola
CMOB329
CAD Mobile
Data
Messaging
The system must provide Electronic messaging
between all MDCs
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1584
Out of the Box
Motorola
CMOB330
CAD Mobile
Data
Messaging
The system must provide Electronic messaging
between MDCs and CAD
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1585
Out of the Box
Motorola
CMOB331
CAD Mobile
Data
Mapping
The system must provide the ability to receive
drive directions to any incident location from a
single touch of the incident screen including:
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1586
Out of the Box
Motorola
CMOB332
CAD Mobile
Data
Mapping
Voice drive directions
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1587
Out of the Box
Motorola
CMOB333
CAD Mobile
Data
Mapping
Graphical drive directions
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1588
Out of the Box
Motorola
CMOB334
CAD Mobile
Data
Mapping
Turn-by-Turn textual drive directions
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1589
Out of the Box
Motorola
CMOB335
CAD Mobile
Data
Mapping
The system must provide the ability to display
and center the map on the incident location
from a single touch of the incident screen
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1590
Out of the Box
Motorola
CMOB336
CAD Mobile
Data
Mapping
The system must provide the ability to support
AVL functionality
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1591
Out of the Box
Motorola
CMOB337
CAD Mobile
Data
Mapping
When incorporated with AVL system the
system shall support multiple unit display on
the Mobile Map
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1592
Out of the Box
Motorola
CMOB338
CAD Mobile
Data
Mapping
When incorporated with AVL system the
system administrator shall be able to define
permissions for of which units each user can
view on their Mobile Map.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1593
Out of the Box
Motorola
CMOB339
CAD Mobile
Data
Mapping
The system must provide the ability to support
GPS functionality.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1594
Out of the Box
Motorola
CMOB340
CAD Mobile
Data
Mapping
The system must provide the ability to display
other units on the Mobile map
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1595
Out of the Box
Page 68of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CMOB341
CAD Mobile
Data
Mapping
The system must provide the ability for the
System Administrator to configure what units
to display on a Mobile User's map base on the
User's role
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1596
Out of the Box
Motorola
CMOB342
CAD Mobile
Data
Mapping
The system must provide the ability to
configure the Mobile map to display other units
within a configurable geographic distance,
regardless of agency (Example: Display all units
in a 2 mile radius)
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1597
Out of the Box
Motorola
CMOB343
CAD Mobile
Data
Mapping
The system must provide the ability to set the
Mobile map to display units assigned to the
same incident as the Mobile User
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1598
Out of the Box
Motorola
CMOB344
CAD Mobile
Data
Mapping
The system must provide the ability for the
Mobile User to configure which incidents to
display on the Mobile map, including only
incidents in the User's same Area, Agency or
Multiple Agencies by area
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1599
Out of the Box
Motorola
CMOB345
CAD Mobile
Data
Mapping
The system must provide the ability to cache
map layers to minimize the amount of data
transmitted wirelessly
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1600
Out of the Box
Motorola
CMOB346
CAD Mobile
Data
Mapping
The system must provide the ability to support
full touch screen capThe system must provide
the ability
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1601
Out of the Box
Motorola
CMOB347
CAD Mobile
Data
Mapping
The system must provide the ability to support
administrative tools that are produced by
outside agencies to manage map layers
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1602
Out of the Box
Motorola
CMOB348
CAD Mobile
Data
Mapping
The system must provide the ability to support
data developed on an ESRI GIS-based platform,
including, but not limited to: street centerlines,
address points, buildings
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1603
Out of the Box
Motorola
CMOB349
CAD Mobile
Data
Mapping
The system must provide the ability to display
County maps with agency-defined features (i.e.,
street names, block ranges, terrain features,
common places, etc.)
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1604
Out of the Box
Motorola
CMOB350
CAD Mobile
Data
Mapping
Ths system must display your own Vehicle
location on the Mobile map with 1 second or
less refresh rate
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1605
Out of the Box
Motorola
CMOB351
CAD Mobile
Data
Mapping
The system must display location of other units
on the Mobile map
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1606
Out of the Box
Motorola
CMOB352
CAD Mobile
Data
Mapping
The system must provide the ability to hide
supervisory units or specialty units on the map
while displaying all other units on the map
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1607
Out of the Box
Motorola
CMOB353
CAD Mobile
Data
Mapping
The system must provide the ability to allow
supervisory units to see other supervisors while
preventing visibility of supervisory units to
subordinates
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1608
Out of the Box
Motorola
CMOB354
CAD Mobile
Data
Mapping
The system must provide the ability to provide
the same navigation functionality as for CAD
mapping
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1609
Out of the Box
Motorola
CMOB355
CAD Mobile
Data
Mapping
The system must provide the ability to zoom in
and zoom out on map
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1610
Out of the Box
Motorola
CMOB356
CAD Mobile
Data
Mapping
The system must provide the ability to zoom by
click with re-center
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1611
Out of the Box
Motorola
CMOB357
CAD Mobile
Data
Mapping
The system must provide the ability to zoom
in/out to fixed extents
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1612
Out of the Box
Motorola
CMOB358
CAD Mobile
Data
Mapping
The system must provide the ability to pan by
sliding gesture
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1613
Out of the Box
Motorola
CMOB359
CAD Mobile
Data
Mapping
The system must provide the ability to identify
layer attributes
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1614
Out of the Box
Motorola
CMOB360
CAD Mobile
Data
Mapping
The system must provide the ability to support
dynamic labeling of layers.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1615
Out of the Box
Motorola
CMOB361
CAD Mobile
Data
Mapping
The system must provide the ability to support
scaled dependencies for layers
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1616
Out of the Box
Motorola
CMOB362
CAD Mobile
Data
Mapping
The system must provide the ability to support
hyperlinks to files, URL's and other documents
(emergency plans, hazmat)
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1617
Out of the Box
Motorola
CMOB363
CAD Mobile
Data
Mapping
The system must provide the ability to locate
address information by address point or street
centerline
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1618
Out of the Box
Motorola
CMOB364
CAD Mobile
Data
Mapping
The system must provide the ability to display
map legend
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1619
Out of the Box
Motorola
CMOB365
CAD Mobile
Data
Mapping
The system must provide the ability to display
compass direction between two user selected
points
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1620
Out of the Box
Motorola
CMOB366
CAD Mobile
Data
Mapping
The system must provide the ability to display
distance in standard measurements between
two user selected points
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1621
Out of the Box
Motorola
CMOB367
CAD Mobile
Data
Mapping
The system must provide the ability to
graphically display street network for a desired
coverage area
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1622
Out of the Box
Page 69of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CMOB368
CAD Mobile
Data
Mapping
The system must provide the ability to access
and display specific map layers (e.g., apartment
complexes, special structures, etc.)
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1623
Out of the Box
Motorola
CMOB369
CAD Mobile
Data
Mapping
The system must provide the ability to display
maps with the following features, including, but
not limited to:
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1624
Out of the Box
Motorola
CMOB370
CAD Mobile
Data
Mapping
Streets, intersections and freeways
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1625
Out of the Box
Motorola
CMOB371
CAD Mobile
Data
Mapping
Street names
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1626
Out of the Box
Motorola
CMOB372
CAD Mobile
Data
Mapping
Block ranges
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1627
Out of the Box
Motorola
CMOB373
CAD Mobile
Data
Mapping
Business name
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1628
Out of the Box
Motorola
CMOB374
CAD Mobile
Data
Mapping
Major buildings or facilities
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1629
Out of the Box
Motorola
CMOB375
CAD Mobile
Data
Mapping
Parcel
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1630
Out of the Box
Motorola
CMOB376
CAD Mobile
Data
Mapping
Map page or reference numbers
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1631
Out of the Box
Motorola
CMOB377
CAD Mobile
Data
Mapping
Reporting districts
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1632
Out of the Box
Motorola
CMOB378
CAD Mobile
Data
Mapping
Parks
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1633
Out of the Box
Motorola
CMOB379
CAD Mobile
Data
Mapping
Schools
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1634
Out of the Box
Motorola
CMOB380
CAD Mobile
Data
Mapping
Police / Sheriff stations
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1635
Out of the Box
Motorola
CMOB381
CAD Mobile
Data
Mapping
Response areas
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1636
Out of the Box
Motorola
CMOB382
CAD Mobile
Data
Mapping
Map or terrain features (e.g., rivers)
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1637
Out of the Box
Motorola
CMOB383
CAD Mobile
Data
Mapping
Photo overlay
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1638
Out of the Box
Motorola
CMOB384
CAD Mobile
Data
Mapping
Common places (i.e., point coverage)
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1639
Out of the Box
Motorola
CMOB385
CAD Mobile
Data
Mapping
Agency-defined layers
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1640
Out of the Box
Motorola
CMOB386
CAD Mobile
Data
Mapping
Ability to center map display on:
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1641
Out of the Box
Motorola
CMOB387
CAD Mobile
Data
Mapping
Current vehicle location (with AVL)
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1642
Out of the Box
Motorola
CMOB388
CAD Mobile
Data
Mapping
Dispatch location
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1643
Out of the Box
Motorola
CMOB389
CAD Mobile
Data
Mapping
Location of cursor when mouse button is
clicked
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1644
Out of the Box
Motorola
CMOB390
CAD Mobile
Data
Mapping
Specified geographic area
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1645
Out of the Box
Motorola
CMOB391
CAD Mobile
Data
Mapping
Station location
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1646
Out of the Box
Motorola
CMOB392
CAD Mobile
Data
Mapping
The system must provide the ability to display
location at cursor when mouse button is clicked
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1647
Out of the Box
Motorola
CMOB393
CAD Mobile
Data
Mapping
The system must provide the ability to reset
map to original screen/format with one screen
touch
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1648
Out of the Box
Motorola
CMOB394
CAD Mobile
Data
Mapping
The system must provide the ability for an
apartment complex map to "pop up" when user
clicks on the location for the apartment
complex (assuming user-created map layer
containing site maps)
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1649
Out of the Box
Motorola
CMOB395
CAD Mobile
Data
Mapping
The system must provide the ability to center
the map on a verified location and mark the
location with a unique icon
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1650
Out of the Box
Motorola
CMOB396
CAD Mobile
Data
Mapping
The system must provide the ability to
suppport a single touch action from an incident
view to display the incident location on the
Mobile map location
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1651
Out of the Box
Motorola
CMOB397
CAD Mobile
Data
Mapping
The system must provide the ability to display
active incidents and pending incidents on the
Mobile map
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1652
Out of the Box
Motorola
CMOB398
CAD Mobile
Data
Mapping
The system must provide the ability to display
unit with visual status indication on the Mobile
map
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1653
Out of the Box
Motorola
CMOB399
CAD Mobile
Data
Mapping
The system must provide the ability to filter the
display of active incident and unit status based
on map scale
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1654
Out of the Box
Motorola
CMOB400
CAD Mobile
Data
Mapping
The system must provide the ability to support
quickest-time routing for all dispatches
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1655
Out of the Box
Motorola
CMOB401
CAD Mobile
Data
Mapping
The system must provide the ability to calculate
drive directions to incident/specified location
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1656
Out of the Box
Motorola
CMOB402
CAD Mobile
Data
Mapping
The system must provide the ability to
recalculate drive directions to
incident/specified location when the user
drives off course
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1657
Out of the Box
Page 70of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CMOB403
CAD Mobile
Data
Mapping
The system must provide the ability to display
shortest route from point-A to point-B (i.e.,
street network routing), and highlight quickest
route, including directions based upon
roadway/access availability (e.g., construction,
detours)
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1658
Out of the Box
Motorola
CMOB404
CAD Mobile
Data
Mapping
The system must provide the ability to view
other unit locations and last known locations
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1659
Out of the Box
Motorola
CMOB405
CAD Mobile
Data
Mapping
The system must provide the ability to display
vehicle location on a map and view the vehicle
progress toward incident location
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1660
Out of the Box
Motorola
CMOB406
CAD Mobile
Data
Mapping
The system must provide the ability to display
direction of travel of units
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1661
Out of the Box
Motorola
CMOB407
CAD Mobile
Data
Mapping
The system must provide the ability to
automatically rotate map orientation with the
direction the vehicle is traveling
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1662
Out of the Box
Motorola
CMOB408
CAD Mobile
Data
Mapping
The system must provide the ability to highlight
on the map the recommended route from
current location to a dispatched incident site
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1663
Out of the Box
Motorola
CMOB409
CAD Mobile
Data
Mapping
The system must provide the ability for Mobile
User to enter road or road segment closures
that are automatically available to other Mobile
Users and Dispatch
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1664
Out of the Box
Motorola
CMOB410
CAD Mobile
Data
Mapping
The system must provide the ability for Mobile
User to create a geo-fence on the Mobile Map
that is automatically available to other Mobile
Users and Dispatch
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1665
Out of the Box
Motorola
CMOB411
CAD Mobile
Data
Mapping
Mobile users must receive notifications when
entering and exiting geofenced areas
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1666
Out of the Box
Motorola
Mobile Specific
Functionality
General
GLOBAL EXPECTATIONS
1667
0
Motorola
CMSF001
Mobile Specific
Functionality
General
The CAD and Mobile applications should be
seamlessly integrated.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1668
Out of the Box
Motorola
CMSF002
Mobile Specific
Functionality
General
The system should transmit dispatch
information from CAD to MDCs and status
information from MDCs to the CAD application
in real time.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1669
Out of the Box
Motorola
CMSF003
Mobile Specific
Functionality
General
The system should facilitate the transfer of unit
response, event information, and resource
information and messages between the CAD
and MDCs.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1670
Out of the Box
Motorola
CMSF004
Mobile Specific
Functionality
General
The MDC client should be able to easily filter
CAD information. The system should permit
different filters to be created so that users can
elect to view different information about
events.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1671
Out of the Box
Motorola
CMSF005
Mobile Specific
Functionality
General
The mobile application should support
NetMotion gateway functionality including
session persistency and security.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1672
Out of the Box
Motorola
CMSF006
Mobile Specific
Functionality
General
The system should have a push-button urgent
function that alerts the ECC and field units of an
impending situation (where an employee might
need immediate assistance).
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1673
Out of the Box
Motorola
CMSF007
Mobile Specific
Functionality
General
The system should support an agency-definable
visual indicator that transmitted messages were
successfully received by the system.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1674
Out of the Box
Motorola
CMSF008
Mobile Specific
Functionality
General
The vendor should provide a list of existing
COTS interfaces to peripherals such as mobile
printers, bar code readers, biometric devices,
digital cameras, etc. that can interface with the
MDC.
Mandatory
Mobile
X
Motorola does not have a list of supported peripherals. The ability for peripheral devicdes to
interface with the Windows Mobile device is based on the peripheral being a Microsoft Windows
supported device.
MCSO & Motorola teams agree requirement is
met out of the box per notes in Column N.
1675
Cannot Meet
Motorola
Mobile Specific
Functionality
General
MDC CLIENT
1676
0
Motorola
CMSF009
Mobile Specific
Functionality
General
The system should include an Field Based
Reporting system which facilitates the capture
of State/Federal reporting requirements while
in the field. It will also allow the electronic
transfer of information to FBR/RMS for
supervisory review and approval. Further
details are found in RMS, Case Report Entry and
Processing.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1677
Out of the Box
Motorola
CMSF010
Mobile Specific
Functionality
General
Each MDC should have the ability to
send/receive messages from CAD as well as all
MCSO MDCs.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1678
Out of the Box
Motorola
Mobile Specific
Functionality
General
DESKTOP/MDC WEB PORTAL
1679
0
Page 71of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CMSF011
Mobile Specific
Functionality
General
When a user signs on to the MDC or desktop,
the system should be capable of displaying a
status indicator informing the user [via a
personal home page], and linking to
information such as:
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1680
Out of the Box
Motorola
CMSF011-1
Mobile Specific
Functionality
General
returns from delayed inquiries to RMS, NCIC,
ACJIS, and other resources,
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1681
Out of the Box
Motorola
CMSF011-2
Mobile Specific
Functionality
General
persons or items of interest “hits”
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1682
Out of the Box
Motorola
CMSF011-3
Mobile Specific
Functionality
General
outlook e-mail
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement if Outlook is accessed
through a web-browser, i.e., Outlook Web Access (OWA).
1683
Out of the Box
Motorola
CMSF011-4
Mobile Specific
Functionality
General
outlook calendar
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement if Outlook is accessed
through a web-browser, i.e., Outlook Web Access (OWA).
1684
Out of the Box
Motorola
CMSF011-5
Mobile Specific
Functionality
General
and any other agency defined data sources.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement if the external system
is accessed through a web-browser.
1685
Out of the Box
Motorola
CMSF012
Mobile Specific
Functionality
General
Officers and other authorized users should have
the capability to easily retrieve event/call
history information that is commonly needed
to create follow-up reports.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1686
Out of the Box
Motorola
Mobile Specific
Functionality
General
LOCAL/NON-LOCAL STORAGE OF DATA
1687
0
Motorola
CMSF013
Mobile Specific
Functionality
General
The system should be capable of accessing
agency definable local and non-local files as
defined by the system administrator.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1688
Out of the Box
Motorola
CMSF014
Mobile Specific
Functionality
General
The MDCs should provide storage and
hypertext access to:
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1689
Out of the Box
Motorola
CMSF014-1
Mobile Specific
Functionality
General
Departmental policy manuals and procedures.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1690
Out of the Box
Motorola
CMSF014-2
Mobile Specific
Functionality
General
State and municipal statutes.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1691
Out of the Box
Motorola
CMSF014-3
Mobile Specific
Functionality
General
Site reference files, including intranet.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1692
Out of the Box
Motorola
CMSF014-4
Mobile Specific
Functionality
General
Any other County provided electronic
documents and images
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1693
Out of the Box
Motorola
CMSF015
Mobile Specific
Functionality
General
To the extent possible, these documents and
functions should be located and accessible on
the local hard drives of MDC-equipped units.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1694
Out of the Box
Motorola
Mobile Specific
Functionality
General
SELF-INITIATED EVENTS
1695
0
Motorola
CMSF016
Mobile Specific
Functionality
General
The system should include a command for MDC
users to create an event, assign and arrive in a
single step (Self-Initiated Event). For example,
a unit comes upon an accident while returning
from a cleared event.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1696
Out of the Box
Motorola
CMSF017
Mobile Specific
Functionality
General
At a minimum, the Self-Initiated event
command should include separate fields for
recording the following information:
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1697
Out of the Box
Motorola
CMSF017-1
Mobile Specific
Functionality
General
AVL or employee reported event location
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1698
Out of the Box
Motorola
CMSF017-2
Mobile Specific
Functionality
General
Event type
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1699
Out of the Box
Motorola
CMSF017-3
Mobile Specific
Functionality
General
District
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1700
Out of the Box
Motorola
CMSF017-4
Mobile Specific
Functionality
General
Patrol Area (PA)
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1701
Out of the Box
Motorola
CMSF017-5
Mobile Specific
Functionality
General
Assisting unit(s),
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1702
Out of the Box
Motorola
CMSF017-6
Mobile Specific
Functionality
General
Comments
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1703
Out of the Box
Motorola
CMSF018
Mobile Specific
Functionality
General
The application should provide the ability to
allow an employee to create an event for the
purpose of creating a case number for
reporting purposes only.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1704
Out of the Box
Motorola
Mobile Specific
Functionality
General
DISPLAY
1705
0
Page 72of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CMSF019
Mobile Specific
Functionality
General
All screens (dispatch, unit status, event history,
etc.) should be System Administrator
configurable.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1706
Out of the Box
Motorola
CMSF020
Mobile Specific
Functionality
General
The system should use a Graphical User
Interface which utilizes menus, keyboard
commands, keyboard shortcut(s) (e.g. Alt P),
and touch-screen function keys to operate and
navigate the proposed application.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1707
Out of the Box
Motorola
CMSF021
Mobile Specific
Functionality
General
It should be noted that the agency's preferred
method of navigating the MDC functionality is
via the touchscreen.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1708
Out of the Box
Motorola
CMSF022
Mobile Specific
Functionality
General
The system should utilize “speed” or “hot” key
shortcuts to specify frequently-recurring
information.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1709
Out of the Box
Motorola
CMSF023
Mobile Specific
Functionality
General
The proposed application should have the
following functionality:
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1710
Out of the Box
Motorola
CMSF023-1
Mobile Specific
Functionality
General
Option to lock windows in place.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1711
Out of the Box
Motorola
CMSF023-2
Mobile Specific
Functionality
General
Option to resize windows and dialogue boxes.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1712
Out of the Box
Motorola
CMSF023-3
Mobile Specific
Functionality
General
Capability to restore windows arrangement to
the default, if changed.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1713
Out of the Box
Motorola
CMSF024
Mobile Specific
Functionality
General
Message and dialog boxes which are displayed
automatically by the proposed application,
rather than being a response to a user request,
should not cover other windows so as to
impede the efficient processing of calls for
service or other work.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1714
Out of the Box
Motorola
CMSF025
Mobile Specific
Functionality
General
The proposed application should provide the
user with a consistent user interface design
between the CAD terminal and MDC (e.g. use of
controls, function keys, navigational
procedures, etc.) in order to reduce user
training and application administration.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1715
Out of the Box
Motorola
CMSF026
Mobile Specific
Functionality
General
The proposed application should be able to set
the following as either: Agency, System
Administration, or user definable:
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1716
Out of the Box
Motorola
CMSF026-1
Mobile Specific
Functionality
General
Configurable resolution,
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1717
Out of the Box
Motorola
CMSF026-2
Mobile Specific
Functionality
General
Configurable display colors,
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1718
Out of the Box
Motorola
CMSF026-3
Mobile Specific
Functionality
General
Configurable font sizes for different windows
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1719
Out of the Box
Motorola
CMSF026-4
Mobile Specific
Functionality
General
Configurable display of units on events using
different colors for different unit status.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1720
Out of the Box
Motorola
CMSF027
Mobile Specific
Functionality
General
When a user changes their display preferences
it should be saved to their sign-on profile for
future use.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement. PremierOne Mobile
remembers user settings from one session to the next so that the individual preferences are
restored each time the user logs in. These settings are called follow-me settings. Follow-me
settings are the specific settings that are set through the Mobile client, such as customizing the
status monitors (column width, font size, sorting of comments), messaging, and queries. The list
also contains Monitored Area settings, and Logged On Areas.
1721
Out of the Box
Motorola
CMSF028
Mobile Specific
Functionality
General
The system should utilize agency-configurable,
predefined data entry forms (masks) to
minimize transmitted data.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1722
Out of the Box
Motorola
CMSF029
Mobile Specific
Functionality
General
The system should provide an auto query
button which presents results based on current
event or unit information.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1723
Out of the Box
Motorola
CMSF030
Mobile Specific
Functionality
General
The system should provide an Agency-definable
visual indicator to inform users if their last
transmission was successful or not.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1724
Out of the Box
Motorola
CMSF031
Mobile Specific
Functionality
General
The system should have the ability to maintain
a continuous/active map display.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1725
Out of the Box
Motorola
CMSF032
Mobile Specific
Functionality
General
The system should have agency-configurable
alerts (visual and/or audible) on all terminals
warning of pending messages.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1726
Out of the Box
Motorola
CMSF033
Mobile Specific
Functionality
General
The system should provide the ability to
configure the application to display a command
line.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1727
Out of the Box
Motorola
CMSF034
Mobile Specific
Functionality
General
The system should provide an agency-definable
fixed key or command to bring up a help file
(may be part of menu bar) that will display
mask and command names and uses.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1728
Out of the Box
Page 73of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CMSF035
Mobile Specific
Functionality
General
Command Line entries should not require the
use of qualifiers (hyphens, parenthesis, slashes,
etc.)
Mandatory
Mobile
X
PremierOne requires agency definable characters to separate different types of information in
Command Line entry. These characters are determined by the Systems Administrator. See the
following explanation of each separator and the default character used:
WƌŝŵĂƌLJƐĞƉĂƌĂƚŽƌƐʹdŚĞĐŚĂƌĂĐƚĞƌƵƐĞĚĂƐƚŚĞƐĞƉĂƌĂƚŽƌŽŶƚŚĞĐŽŵŵĂŶĚƚŚĂƚŝŶĚŝĐĂƚĞƐƚŚĞĞŶĚ
of the entry of a command or identifier/value pair. The default is a period. Example: II.123 w
main.theft
sĂůƵĞƐĞƚƐĞƉĂƌĂƚŽƌƐʹdŚĞĐŚĂƌĂĐƚĞƌƵƐĞĚƚŽƐĞƉĂƌĂƚĞŵƵůƚŝƉůĞǀĂůƵĞƐŝŶĂůŝƐƚŝŶŐŽŶƚŚĞĐŽŵŵĂŶĚ
line. The default is a comma. Example: ON.unit1, unit2, unit 3
EĂŵĞǀĂůƵĞƐĞƉĂƌĂƚŽƌƐʹdŚĞĐŚĂƌĂĐƚĞƌƵƐĞĚƚŽƐĞƉĂƌĂƚĞĂŶŝĚĞŶƚŝĨŝĞƌĨƌŽŵƚŚĞǀĂůƵĞĞŶƚĞƌĞĚĨŽƌ
use by the identifier. The default is a semi-colon. Example: II.L;123 w main st.T;accident
ŽŵŵĂŶĚƐĞƚƐĞƉĂƌĂƚŽƌʹdŚĞĐŚĂƌĂĐƚĞƌƵƐĞĚƚŽĂůůŽǁŵƵůƚŝƉůĞŝƐƐƵĂŶĐĞƐŽĨĚŝĨĨĞƌĞŶƚǀĂůƵĞƐŝŶƚŚĞ
same command (like issuing the command twice/more from one command line entry. The default
is ^.
ŐĞŶĐLJ/ǀĂůƵĞƐƐĞƉĂƌĂƚŽƌʹdŚĞĐŚĂƌĂĐƚĞƌƵƐĞĚƚŽƐĞƉĂƌĂƚĞĂŐĞŶĐLJ/ĨƌŽŵŽƚŚĞƌŝŶĨŽƌŵĂƚŝŽŶŝŶ
values entered on the command line. The default is /. Example: IS.DC/AR1.
LJŶĂŵŝĐŚĞůƉƐǁŝƚĐŚʹdŚĞĐŚĂƌĂĐƚĞƌƵƐĞĚƚŽƚƵƌŶŽŶͬ ŽĨĨĚLJŶĂŵŝĐŚĞůƉŽŶƚŚĞĐŽŵŵĂŶĚůŝŶĞ͘ dŚĞ
default is [.
MCSO team agrees with explanation in column
N.
1729
Cannot Meet
Motorola
CMSF036
Mobile Specific
Functionality
General
Summary information that is presented in
columns should be sortable via touch-pad and
touch screen.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1730
Out of the Box
Motorola
CMSF037
Mobile Specific
Functionality
General
The system should have a user defined audible
and visual notification to indicate the receipt of
an event, dispatch message, urgent messages,
etc.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1731
Out of the Box
Motorola
CMSF038
Mobile Specific
Functionality
General
The system should use standard screen formats
for all inquiries
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1732
Out of the Box
Motorola
CMSF039
Mobile Specific
Functionality
General
The application should have the ability to
display an agency-definable toolbar on the
screen that cannot be covered up by other
applications.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1733
Out of the Box
Motorola
CMSF040
Mobile Specific
Functionality
General
Certain agency specific information should
always be displayed on the active screen,
including:
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1734
Out of the Box
Motorola
CMSF040-1
Mobile Specific
Functionality
General
Time
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1735
Out of the Box
Motorola
CMSF040-2
Mobile Specific
Functionality
General
Unit Status Display: Active area for constant
display of current status and response area
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1736
Out of the Box
Motorola
CMSF040-3
Mobile Specific
Functionality
General
Unit Location, or destination location (Address) Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1737
Out of the Box
Motorola
CMSF040-4
Mobile Specific
Functionality
General
Assigned radio channel
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1738
Out of the Box
Motorola
CMSF041
Mobile Specific
Functionality
General
Unit status and location information for Animal
Control Officers, Code Enforcement, and Park
Rangers should be available to the MDCs, but
should not be intermingled with MCSO unit
data.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1739
Out of the Box
Motorola
Mobile Specific
Functionality
General
DAY/NIGHT MODE
1740
0
Motorola
CMSF042
Mobile Specific
Functionality
General
The mobile client should support a day and
night mode for screen display, to include day
and night mode for the map display and all
other applications accessed via the MDC.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1741
Out of the Box
Motorola
CMSF043
Mobile Specific
Functionality
General
The day and night modes should provide a
consistent appearance when switching
between applications. For example, when
switching between the CAD and the Field Based
Reporting Systems the day/night modes shall
present a consistent illumination between
applications so that the user does not have to
adjust the brightness when switching between
applications.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1742
Out of the Box
Motorola
Mobile Specific
Functionality
General
EVENT NOTIFICATIONS
n
1743
0
Motorola
CMSF045
Mobile Specific
Functionality
General
The system should provide the ability to:
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1744
Out of the Box
Motorola
CMSF045-1
Mobile Specific
Functionality
General
Receive electronic dispatch messages from the
CAD application
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1745
Out of the Box
Motorola
CMSF045-2
Mobile Specific
Functionality
General
Provide user-definable audible and visual
notification of receipt of dispatch message
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1746
Out of the Box
Page 74of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CMSF045-3
Mobile Specific
Functionality
General
Save dispatched CAD events locally, to the
MDC(s) which received the assignment.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement. Users can work in
offline mode using PremierOne CAD Mobile. Offline mode is useful when the mobile unit cannot
connect to the central server. In offline mode, users will have access to information that has been
downloaded to the unit.
1747
Out of the Box
Motorola
CMSF045-4
Mobile Specific
Functionality
General
Allow the user to, with a single touch of a
button, recall the dispatch information for the
currently assigned event.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1748
Out of the Box
Motorola
CMSF045-5
Mobile Specific
Functionality
General
Provide a (user-definable) visual indicator to
inform users if their last transmission was
successful or not.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1749
Out of the Box
Motorola
CMSF045-6
Mobile Specific
Functionality
General
Provide the ability to display user-definable
information upon the dispatch of units to an
event.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1750
Out of the Box
Motorola
CMSF046
Mobile Specific
Functionality
General
Upon dispatch of unit(s) to an event, the
system should display the following minimum
user-definable dispatch information:
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1751
Out of the Box
Motorola
CMSF046-1
Mobile Specific
Functionality
General
Event location with apartment number and
high and low cross streets
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1752
Out of the Box
Motorola
CMSF046-2
Mobile Specific
Functionality
General
vent type
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1753
Out of the Box
Motorola
CMSF046-3
Mobile Specific
Functionality
General
Event priority and urgency code(e.g., user
defined or defined by event code)
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1754
Out of the Box
Motorola
CMSF046-4
Mobile Specific
Functionality
General
Response list in dispatched order
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1755
Out of the Box
Motorola
CMSF046-5
Mobile Specific
Functionality
General
Recommended route to the event location (tab
or button)
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1756
Out of the Box
Motorola
CMSF046-6
Mobile Specific
Functionality
General
Date and time of event entry
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1757
Out of the Box
Motorola
CMSF046-7
Mobile Specific
Functionality
General
Reporting party name, phone number, address
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1758
Out of the Box
Motorola
CMSF046-8
Mobile Specific
Functionality
General
Application generated event number
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1759
Out of the Box
Motorola
CMSF046-9
Mobile Specific
Functionality
General
Phone number at event location
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1760
Out of the Box
Motorola
CMSF046-10
Mobile Specific
Functionality
General
Location of interest information flag
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1761
Out of the Box
Motorola
CMSF046-11
Mobile Specific
Functionality
General
Dispatch Group Assignment
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1762
Out of the Box
Motorola
CMSF046-12
Mobile Specific
Functionality
General
Premise history information (flag)
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1763
Out of the Box
Motorola
CMSF046-13
Mobile Specific
Functionality
General
Comments (in chronological order)
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1764
Out of the Box
Motorola
CMSF046-14
Mobile Specific
Functionality
General
District
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1765
Out of the Box
Motorola
CMSF046-15
Mobile Specific
Functionality
General
Patrol Area
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1766
Out of the Box
Motorola
CMSF046-16
Mobile Specific
Functionality
General
See complainant (Yes/No/If needed)
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1767
Out of the Box
Motorola
CMSF046-17
Mobile Specific
Functionality
General
An icon indicating the location of the event on
the map
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1768
Out of the Box
Motorola
CMSF046-18
Mobile Specific
Functionality
General
Event number (MC Number)
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1769
Out of the Box
Motorola
CMSF047
Mobile Specific
Functionality
General
The system should be able to update unit status
using single function keys and/or touch screen
button with an agency-definable color and label
indicating status for:
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1770
Out of the Box
Motorola
CMSF047-1
Mobile Specific
Functionality
General
Enroute, (indicates at least one unit has been
marked enroute).
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1771
Out of the Box
Motorola
CMSF047-2
Mobile Specific
Functionality
General
Onscene, but available (indicates unit is
onscene of event but able to clear to handle
another call)
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1772
Out of the Box
Motorola
CMSF047-3
Mobile Specific
Functionality
General
Onscene
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1773
Out of the Box
Motorola
CMSF047-4
Mobile Specific
Functionality
General
Available
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1774
Out of the Box
Page 75of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CMSF047-5
Mobile Specific
Functionality
General
Out of Vehicle (could be used with any status)
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1775
Out of the Box
Motorola
CMSF047-6
Mobile Specific
Functionality
General
Closed with disposition from a pick-list.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1776
Out of the Box
Motorola
CMSF047-7
Mobile Specific
Functionality
General
Transport
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1777
Out of the Box
Motorola
CMSF048
Mobile Specific
Functionality
General
Unit status attributes should include
available/not available for recommendation,
time penalty for response recommendation
based on event priority, AVL polling rate.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1778
Out of the Box
Motorola
CMSF049
Mobile Specific
Functionality
General
The system should transmit status information
in real time from MDC to the CAD application
and from the CAD to the MDC.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1779
Out of the Box
Motorola
CMSF050
Mobile Specific
Functionality
General
The system should transmit dispatch
information in real time, from CAD to the target
MDC and status information from MDC to the
CAD application, and
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1780
Out of the Box
Motorola
CMSF051
Mobile Specific
Functionality
General
The system should be able to display an event
using different colors for different priorities,
and
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1781
Out of the Box
Motorola
CMSF052
Mobile Specific
Functionality
General
Receive supplemental dispatch information
such as:
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1782
Out of the Box
Motorola
CMSF052-1
Mobile Specific
Functionality
General
Updates to a dispatched event.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1783
Out of the Box
Motorola
CMSF053
Mobile Specific
Functionality
General
The system should support System
Administrator configurable visual and audible
notification of event/unit status changes, such
as:
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1784
Out of the Box
Motorola
CMSF053-1
Mobile Specific
Functionality
General
Preempting of the dispatch
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1785
Out of the Box
Motorola
CMSF053-2
Mobile Specific
Functionality
General
Event cancellation
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1786
Out of the Box
Motorola
CMSF053-3
Mobile Specific
Functionality
General
Specific units which have arrived on the scene
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1787
Out of the Box
Motorola
CMSF053-4
Mobile Specific
Functionality
General
Unit reassignments
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1788
Out of the Box
Motorola
CMSF053-5
Mobile Specific
Functionality
General
Unit exchange
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1789
Out of the Box
Motorola
CMSF053-6
Mobile Specific
Functionality
General
Change of phone number
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1790
Out of the Box
Motorola
CMSF053-7
Mobile Specific
Functionality
General
Channel assignment change
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1791
Out of the Box
Motorola
CMSF054
Mobile Specific
Functionality
General
The system should be able to perform pertinent
CAD update functions that are limited only by
security access privileges (adding comments or
disposition code to a call, etc.) such as:
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1792
Out of the Box
Motorola
CMSF054-1
Mobile Specific
Functionality
General
Update CAD with unit history information
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1793
Out of the Box
Motorola
CMSF055
Mobile Specific
Functionality
General
Confirm the entry of a self-initiated event by
displaying a agency-defined verification
message
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1794
Out of the Box
Motorola
CMSF056
Mobile Specific
Functionality
General
The system should be able to retrieve previous
events including a user-definable summary of
event and unit statuses
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1795
Out of the Box
Motorola
CMSF057
Mobile Specific
Functionality
General
The system should capture agency-definable
event and unit data from CAD, import the data
to the MDC and populate appropriate case
report fields.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1796
Out of the Box
Motorola
CMSF058
Mobile Specific
Functionality
General
The system should be able to retrieve detailed
premise/location, prior history, etc. and,
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1797
Out of the Box
Motorola
CMSF058-1
Mobile Specific
Functionality
General
Automatically create premise and CAD call
history upon closing of an event, and
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1798
Out of the Box
Motorola
CMSF058-2
Mobile Specific
Functionality
General
Auto-archive premise and call history based on
agency-definable criteria
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1799
Out of the Box
Page 76of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CMSF059
Mobile Specific
Functionality
General
The system should transmit (to CAD)
information in an emergency situation, any
agency-defined unit information with the touch
of a single emergency button, such as:
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1800
Out of the Box
Motorola
CMSF059-1
Mobile Specific
Functionality
General
Portable and Mobile Radio ID's
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1801
Out of the Box
Motorola
CMSF059-2
Mobile Specific
Functionality
General
Unit ID
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1802
Out of the Box
Motorola
CMSF059-3
Mobile Specific
Functionality
General
AVL reported location and/or location of last
assignment
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1803
Out of the Box
Motorola
CMSF059-4
Mobile Specific
Functionality
General
Officer in charge name EIN
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1804
Out of the Box
Motorola
CMSF059-5
Mobile Specific
Functionality
General
Officer in charge radio ID
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1805
Out of the Box
Motorola
CMSF060
Mobile Specific
Functionality
General
The system should be capable of sending this
information to all agency-defined CAD users.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1806
Out of the Box
Motorola
CMSF061
Mobile Specific
Functionality
General
When the user presses the on-screen
emergency function, the button should visually
count-down an agency-defined number of
seconds, before it sends an emergency
command to the CAD.
Mandatory
Mobile
X
PremierOne partially complies with the functionality as described in the requirement. In
PremierOne, the Emergency button can be configured to automatically send when pressed, or
require a 2nd step. There is no countdown mechanism.
1807
Out of the Box
Motorola
CMSF062
Mobile Specific
Functionality
General
If the user presses the on-screen emergency
button a second time prior to the counter
reaching zero, the emergency command should
be cancelled.
Mandatory
Mobile
X
PremierOne does not have this functionality.
MCSO team stated this is not required to be met.
1808
Cannot Meet
Motorola
CMSF063
Mobile Specific
Functionality
General
This button should change colors (agency-
definable) to indicate that the count-down has
started.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1809
Out of the Box
Motorola
CMSF064
Mobile Specific
Functionality
General
The MDC's Emergency button should be placed
in a location to prevent accidental activation as
defined by the Agency/System Administrator.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1810
Out of the Box
Motorola
Mobile Specific
Functionality
General
TRANSACTION LOGGING
1811
0
Motorola
CMSF065
Mobile Specific
Functionality
General
The system should provide the ability to
automatically log MDC transactions, including:
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1812
Out of the Box
Motorola
CMSF065-1
Mobile Specific
Functionality
General
User name
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1813
Out of the Box
Motorola
CMSF065-2
Mobile Specific
Functionality
General
User ID
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1814
Out of the Box
Motorola
CMSF065-3
Mobile Specific
Functionality
General
Terminal ID
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1815
Out of the Box
Motorola
CMSF065-4
Mobile Specific
Functionality
General
Date and time of transmission
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1816
Out of the Box
Motorola
CMSF065-5
Mobile Specific
Functionality
General
Create an audit log of all file maintenance (add,
delete, change) activity
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1817
Out of the Box
Motorola
CMSF066
Mobile Specific
Functionality
General
Selectively audit logged messages by:
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1818
Out of the Box
Motorola
CMSF066-1
Mobile Specific
Functionality
General
MDC ID/Name
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1819
Out of the Box
Motorola
CMSF066-2
Mobile Specific
Functionality
General
User name
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1820
Out of the Box
Motorola
CMSF066-3
Mobile Specific
Functionality
General
User ID
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1821
Out of the Box
Motorola
CMSF066-4
Mobile Specific
Functionality
General
Send date and time
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1822
Out of the Box
Motorola
CMSF066-5
Mobile Specific
Functionality
General
Receive/open date and time
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1823
Out of the Box
Motorola
CMSF066-6
Mobile Specific
Functionality
General
Entire message
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1824
Out of the Box
Motorola
CMSF067
Mobile Specific
Functionality
General
Any user-defined key words or combination of
key words
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1825
Out of the Box
Motorola
CMSF068
Mobile Specific
Functionality
General
Automatically log unsuccessful log-on attempts
by:
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1826
Out of the Box
Page 77of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CMSF068-1
Mobile Specific
Functionality
General
Terminal/workstation ID
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1827
Out of the Box
Motorola
CMSF068-2
Mobile Specific
Functionality
General
Date and time
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1828
Out of the Box
Motorola
CMSF068-3
Mobile Specific
Functionality
General
User ID
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1829
Out of the Box
Motorola
CMSF069
Mobile Specific
Functionality
General
The system should provide an audit trail of
information accessed with MDC unit ID(s) and
time stamp of each transaction.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1830
Out of the Box
Motorola
CMSF070
Mobile Specific
Functionality
General
The system should provide the system
administrator configurable option for
supervisors to view all messages sent and
received from an MDC.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1831
Out of the Box
Motorola
Mobile Specific
Functionality
General
OTHER APPLICATIONS
1832
0
Motorola
CMSF071
Mobile Specific
Functionality
General
MDC's should be capable of running multiple
applications (e.g. CAD, Field Based Reporting,
NCIC, MS WORD, County VPN, etc.).
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1833
Out of the Box
Motorola
Mobile Specific
Functionality
General
SWITCHING BETWEEN APPLICATIONS
1834
0
Motorola
CMSF072
Mobile Specific
Functionality
General
Users should be able to switch between
entering data into reports and forms, to
viewing and responding to a dispatch message,
to retrieving query responses, to initiating
messages, to updating their status, to reviewing
messages, etc., without losing any information
that has been entered into the system.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1835
Out of the Box
Motorola
Mobile Specific
Functionality
General
VOICE TRANSACTION VOICE RETURN
1836
0
Motorola
CMSF073
Mobile Specific
Functionality
General
The system should provide text to voice
locution, a text string from CAD is sent to the
MDC and the locution software plays the
announcement of the agency-definable
information through speakers attached to the
MDC. In the event that the system is already
playing an announcement it shall store the
incoming announcement and play it as soon as
the first announcement is completed. Examples
of announcements include dispatched events,
vehicle and person checks, etc. If this is an
option, please price separately.
Mandatory
Mobile
X
PremierOne does not comply with this functionality. Agencies experimenting with text-to-voice
have ended up disabling this function as it can get very annoying and endanger the first
responder.
MCSO team stated this is not required to be met.
1837
Cannot Meet
Motorola
Mobile Specific
Functionality
General
NETWORK TIMER SYNCHRONIZATION
1838
0
Motorola
CMSF074
Mobile Specific
Functionality
General
Date and time on the MDCs units is critical to a
number of processes. For example, vehicle
status updates, report status changes, message
sent and message received time stamps, etc.,
should all be synchronized between the various
MDC units in the system for the date and time
stamping to be useful. It is necessary for the
MDCs to synchronize the date and time on all
system MDC units. The MDC server and/or
message switch should obtain the current date
and time from the master clock at the ECC. The
current date and time should be broadcast to
all of the MDC units logged onto the system.
(Refer to the master clock specifications in the
Technical Requirements.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1839
Out of the Box
Motorola
CMSF075
Mobile Specific
Functionality
General
Each MDC unit’s system clock should be
updated based on the master clock date and
time. The synchronization should occur upon
successful login and, thereafter, per County-
specified time interval (e.g., every hour)
Mandatory
Mobile
X
PremierOne does not have this functionality. Time synchronization functionality is based on
Microsoft Windows sync capabilities.
Use case described by MCSO is that user puts laptop to
sleep at end of shift and when laptop is brought back
online the laptop time is not in sync with the server.
Motorola tested and stated for this use case the laptop
will be synced to server when brought back online
from hibernation.
MCSO & Motorola teams agree requirement is
met out of the box per notes in Column O.
1840
Cannot Meet
Motorola
Mobile Specific
Functionality
General
TRAFFIC STOPS AND FIELD INTERVIEWS
1841
0
Page 78of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CMSF076
Mobile Specific
Functionality
General
The system should include a command and
mask with agency definable fields for MDC
users to initiate, record and clear a traffic stop.
The system should automatically initiate agency
definable queries of systems as a result of
completing this mask. Example: the vehicle tag
entered would initiate a check on the
registered owner through MVD, NCIC, and RMS
(local warrant files). These returns would be
automatically routed to the MDC.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1842
Out of the Box
Motorola
CMSF077
Mobile Specific
Functionality
General
The system should include a command and
mask with agency definable fields for MDC
users to initiate, record and clear a field
interview.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1843
Out of the Box
Motorola
CMSF078
Mobile Specific
Functionality
General
The system should allow a unit to conduct a
traffic stop or field interview while
simultaneously assigned to an event or activity.
It will not be necessary to clear the unit from
their current status before the traffic stop or
field interview can be initiated. (The prior
activity will be placed in a pending status for
the unit.)
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1844
Out of the Box
Motorola
CMSF079
Mobile Specific
Functionality
General
The user should have the option to store
locally, or import directly, some or all of the
information received as the result of
person/vehicle records checks through
MVD/NLETS/NCIC/RMS, ACJIS, or other agency
definable systems, into an FBR application. This
would include, but is not limited to: field
reports, accident reports, warning tickets, field
contacts, electronic tickets, and supplements.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1845
Out of the Box
Motorola
Mobile Specific
Functionality
General
ON SCENE STATUSES
1846
0
Motorola
CMSF081
Mobile Specific
Functionality
General
Mobile users who mark themselves Onscene
(on the scene) of an assigned event, should be
able to place themselves in an Available or
Unavailable status, while remaining assigned to
an event, via an agency definable button on the
mobile screen. This status will be transmitted
to the CAD system and available to all users.
Preferred
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1847
Out of the Box
Motorola
CMSF082
Mobile Specific
Functionality
General
The Available and Unavailable command should
be available to the workstation as well. There
may be times when units are away from their
MDCs and direct a dispatcher by radio or a call
taker by phone to mark them available or
unavailable.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1848
Out of the Box
Motorola
CMSF083
Mobile Specific
Functionality
General
When users who mark themselves Onscene of
an assigned event notify CAD that they are
Available while still assigned to the event, the
system may recommend the user for dispatch
to agency-definable events. When the system
does this, the system should indicate to the ECC
dispatcher that the recommended unit is
Onscene of another event, requiring the
dispatcher to check with that unit to see if they
are able to leave for the new event.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1849
Out of the Box
Motorola
CMSF084
Mobile Specific
Functionality
General
The agency should be able to define the event
types that result in recommendations for unit
assignments for units that are Onscene But
Available.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1850
Out of the Box
Motorola
CMSF085
Mobile Specific
Functionality
General
The agency should be able to set default
Onscene statuses for each event type. For
example, a unit marking Onscene of a Shooting
would always be statused as Onscene as the
default; whereas a unit marking Onscene of a
Community Oriented Patrol event would always
be statused as Onscene But Available as the
default.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1851
Out of the Box
Motorola
Mobile Specific
Functionality
General
MDC PAGE
1852
0
Motorola
CMSF086
Mobile Specific
Functionality
General
The mobile client should provide access to all of
the below listed functionality via agency
definable touch screen buttons such as but not
limited to:
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1853
Out of the Box
Motorola
CMSF086-1
Mobile Specific
Functionality
General
Sends the ENROUTE command back to
dispatch.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1854
Out of the Box
Page 79of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CMSF086-2
Mobile Specific
Functionality
General
Sends the ONSCENE command back to
dispatch.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1855
Out of the Box
Motorola
CMSF086-3
Mobile Specific
Functionality
General
Sends an AVAILABLE IN message to dispatch
indicating the unit is available for dispatch.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1856
Out of the Box
Motorola
CMSF086-4
Mobile Specific
Functionality
General
Performs a unit summary query.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1857
Out of the Box
Motorola
CMSF086-5
Mobile Specific
Functionality
General
Displays pending events for the unit.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1858
Out of the Box
Motorola
CMSF086-6
Mobile Specific
Functionality
General
Displays a form where you can enter a CAD
Command.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1859
Out of the Box
Motorola
CMSF086-7
Mobile Specific
Functionality
General
Performs a Vehicle Query.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1860
Out of the Box
Motorola
CMSF086-8
Mobile Specific
Functionality
General
Performs a Person Query
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1861
Out of the Box
Motorola
CMSF086-9
Mobile Specific
Functionality
General
Performs a Traffic Stop.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1862
Out of the Box
Motorola
CMSF086-10
Mobile Specific
Functionality
General
Self initiated event.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1863
Out of the Box
Motorola
CMSF086-11
Mobile Specific
Functionality
General
Sends a Wrecker Request to dispatch.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1864
Out of the Box
Motorola
CMSF086-12
Mobile Specific
Functionality
General
Sends an Assist request to dispatch.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1865
Out of the Box
Motorola
CMSF086-13
Mobile Specific
Functionality
General
Allows you to change the unit’s location.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1866
Out of the Box
Motorola
CMSF086-14
Mobile Specific
Functionality
General
Sends a Transport Subject status to dispatch.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1867
Out of the Box
Motorola
CMSF086-15
Mobile Specific
Functionality
General
Provides a screen to enter accident
information.
Mandatory
Records Mobile
X
PremierOne complies with the functionality with the use of our included PremierOne Records
application.
1868
Out of the Box
Motorola
CMSF086-16
Mobile Specific
Functionality
General
Provides a screen to add supplement person
information to an event.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1869
Out of the Box
Motorola
CMSF086-17
Mobile Specific
Functionality
General
Provides a screen to add supplement vehicle
information to an event.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1870
Out of the Box
Motorola
CMSF086-18
Mobile Specific
Functionality
General
Displays Event Status Unit.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1871
Out of the Box
Motorola
CMSF086-19
Mobile Specific
Functionality
General
Retrieves information on CAD users.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1872
Out of the Box
Motorola
CMSF086-20
Mobile Specific
Functionality
General
Displays the email screen.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1873
Out of the Box
Motorola
CMSF086-21
Mobile Specific
Functionality
General
Displays a free-form text area in which to write
and save notes.
Mandatory
Mobile
X
PremierOne does not have this functionality.
MCSO team stated this is not required to be met.
1874
Cannot Meet
Motorola
CMSF086-22
Mobile Specific
Functionality
General
Displays the event history of a specified event.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1875
Out of the Box
Motorola
CMSF086-23
Mobile Specific
Functionality
General
Displays the current unit history.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1876
Out of the Box
Motorola
CMSF086-24
Mobile Specific
Functionality
General
Displays the event that the unit is currently
assigned to.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1877
Out of the Box
Motorola
CMSF086-25
Mobile Specific
Functionality
General
Displays the Location of Interest and Location
History screen.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1878
Out of the Box
Motorola
CMSF086-26
Mobile Specific
Functionality
General
Sets the unit status to Out of Vehicle.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1879
Out of the Box
Motorola
CMSF086-27
Mobile Specific
Functionality
General
Sets the unit status to In Vehicle.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1880
Out of the Box
Motorola
CMSF086-28
Mobile Specific
Functionality
General
Displays the history of the location that the unit
is currently assigned to.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1881
Out of the Box
Motorola
CMSF086-29
Mobile Specific
Functionality
General
Communicates to dispatch that you cannot
respond to an event.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1882
Out of the Box
Motorola
CMSF086-30
Mobile Specific
Functionality
General
Communicates to dispatch that the unit is
unavailable.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1883
Out of the Box
Page 80of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CMSF086-31
Mobile Specific
Functionality
General
Displays a screen for terminal to terminal
messages.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1884
Out of the Box
Motorola
CMSF086-32
Mobile Specific
Functionality
General
Retrieves the next message.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1885
Out of the Box
Motorola
CMSF086-33
Mobile Specific
Functionality
General
Clears the unit from the event.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1886
Out of the Box
Motorola
CMSF086-34
Mobile Specific
Functionality
General
Displays information on the location of the
event the unit’s currently assigned to.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1887
Out of the Box
Motorola
CMSF086-35
Mobile Specific
Functionality
General
Displays a screen where you can change your
password.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1888
Out of the Box
Motorola
CMSF086-36
Mobile Specific
Functionality
General
Is used to sign in or out of the system.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1889
Out of the Box
Motorola
CMSF087
Mobile Specific
Functionality
General
Data pertaining to any non-County units that
are being dispatched and currently active on
calls should be available to County MDCs, but
not interspersed with any County activities on
mobile terminal displays.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
1890
Out of the Box
Motorola
CRINT001
Radio
Integration
Radio Console
Integration
The solution must provide MCC7500 radio
console integration that allows CAD users to
select and dynamically group channels utilizing
a single keyboard and mouse from within CAD.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1891
Out of the Box
Motorola
CRINT002
Radio
Integration
Radio Console
Integration
The solution must provide MCC7500 radio
console integration that allows CAD users to
initiate a priority transmit utilizing a single
keyboard and mouse from within CAD.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1892
Out of the Box
Motorola
CRINT003
Radio
Integration
Radio Console
Integration
The solution must provide MCC7500 radio
console integration that allows CAD users to
initiate a multi-select of radios upon incident
dispatch allowing communication to all units
regardless of talk group affiliation utilizing a
single keyboard and mouse from within CAD.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1893
Out of the Box
Motorola
CRINT004
Radio
Integration
Radio Console
Integration
The solution must provide MCC7500 radio
console integration that allows CAD users to
manually regroup a set of specified CAD Units’
radios to a specified pre-existing talk group
from the CAD system command line.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1894
Out of the Box
Motorola
CRINT005
Radio
Integration
Radio Console
Integration
The solution must provide MCC7500 radio
console integration that allows CAD system to
automatically regroup the radios of all CAD
recommended units to a call for service to a
specified pre-existing talk group.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1895
Out of the Box
Motorola
CRINT006
Radio
Integration
Radio PTT
Integration
The system must integrate with the radio
system such that when a unit transmits a radio
message the system will display the unit
identifier associated with the radio that is
transmitting in a separate CAD status monitor.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1896
Out of the Box
Motorola
CRINT007
Radio
Integration
Radio PTT
Integration
The system shall provide a shortcut to quickly
and easily move the last unit identifier from the
PTT monitor to any location on the CAD client.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1897
Out of the Box
Motorola
CRINT008
Radio
Integration
Radio PTT
Integration
If a unit keys the radio emergency button, the
unit on the Push to Talk monitor shall change to
a highlighted color and be highlighted.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1898
Out of the Box
Motorola
CRINT009
Radio
Integration
Radio Subscriber
Location Integration
The proposed system should provide the
capability to support Automated Vehicle
Location (AVL) and Radio subscriber location
with intelligence to associate Mobile
workstation and Portable Radio locations on
the CAD and Mobile map based upon
established out-of-vehicle statuses. (The
system dynamically changes the display to
radio location of personnel when they are in a
status that reflects that the operators are out
of vehicle.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1899
Out of the Box
Motorola
CRINT010
Radio
Integration
Radio Subscriber
Location Integration
The system must dynamically change the
device being displayed (Mobile computer
versus Portable Radio) based on incident type
or unit status as defined by agency practices.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1900
Out of the Box
Page 81of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CRINT011
Radio
Integration
Radio Subscriber
Location Integration
The proposed CAD/Mobile system must be able
to receive multiple GPS feeds for a single
deputy's location (Mobile workstation/Portable
Radio) and dynamically change which is
displayed on CAD & Mobile map at any given
time.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1901
Out of the Box
Motorola
CRINT012
Radio
Integration
Radio Messaging
Services Integration
The CAD system shall be integrated with the
radio system such that the CAD system is able
to exchange digital messages with
appropriately equipped radios. These
messages must include dispatch notifications,
BOLO’s and custom messages. Messages must
be able to be addressed to:
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1902
Out of the Box
Motorola
CRINT013
Radio
Integration
Radio Messaging
Services Integration
User ID(Serial)
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1903
Out of the Box
Motorola
CRINT014
Radio
Integration
Radio Messaging
Services Integration
Unit ID
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1904
Out of the Box
Motorola
CRINT015
Radio
Integration
Radio Messaging
Services Integration
Device identifier
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1905
Out of the Box
Motorola
CRINT016
Radio
Integration
Radio Messaging
Services Integration
And by a group
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1906
Out of the Box
Motorola
CRINT017
Radio
Integration
Responder Alerts
Integration
The CAD system shall support / include the
ability to integrate with the radio system to
receive alerts related to various sensors located
on deputies’ persons and in vehicles utilized by
First responders (emergency buttons, PTT key-
ins, etc.).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1907
Out of the Box
Motorola
CRINT018
Radio
Integration
Responder Alerts
Integration
The system must include a disarm mode that
will inactivate the alerts temporarily.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1908
Out of the Box
Motorola
CINF001
Interfaces
E9-1-1
The system must provide the capability to
enable incoming E9-1-1 ANI/ALI data to be
automatically mapped to corresponding
address and phone data fields based on the
Master Street Address Guide (MSAG) standard
in the CFS event entry form.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1909
Out of the Box
Motorola
CINF002
Interfaces
E9-1-1
The system must provide the capability to
support all E9-1-1 ANI/ALI formats including
wireline, WPH1, WPH2, and VoIP.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1910
Out of the Box
Motorola
CINF003
Interfaces
E9-1-1
The system must provide the capability to
enable the capture of additional fields captured
in the CFS event, including ESN, call type
(landline, wireless), and ANI/ALI tracking ID (if
available).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1911
Out of the Box
Motorola
CINF004
Interfaces
E9-1-1
The system must provide the capability to use
GIS data to extrapolate the closest geographical
attribute (address, intersection, common
place).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1912
Out of the Box
Motorola
CINF005
Interfaces
E9-1-1
The radius used to extrapolate the closest
geographical attribute must [Shall/Should] be a
configurable item within the system.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1913
Out of the Box
Motorola
CINF006
Interfaces
E9-1-1
If GIS data is used to create the caller location,
then the offset used to determine the
approximate location should be displayed.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1914
Out of the Box
Motorola
CINF007
Interfaces
External DB
The system must provide the capability to
provide configurable query forms and response
displays and be able to be custom-built to
accommodate different federal, state and local
database protocols.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1915
Out of the Box
Motorola
CINF008
Interfaces
External DB
The system must provide the capability to
provide authorization to perform various
queries, and the ability to read responses
definable by the individual agency and by role
to the field level.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1916
Out of the Box
Motorola
CINF009
Interfaces
External DB
The system must provide the capability to allow
users to submit queries either with the query
form or the command line (if applicable).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1917
Out of the Box
Motorola
CINF010
Interfaces
External DB
The system must provide the capability to allow
users to automatically submit queries for
persons and vehicles as part of other data entry
processes, such as CFS event creation.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1918
Out of the Box
Motorola
CINF011
Interfaces
External DB
The system must provide the capability to
enable the query request type and the
database(s) to be queried to be specified from
a predefined list, with automatic narrowing of
pertinent databases based on user data input.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1919
Out of the Box
Page 82of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CINF012
Interfaces
External DB
The system must provide the capability to
provide intelligent updating of the query forms
based on other CAD forms that contain person
or vehicle data.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1920
Out of the Box
Motorola
CINF013
Interfaces
External DB
The system must provide the capability to
provide a method for multiple queries to be
submitted through a single form or command.
This is sometimes referred to as query
spawning or cascading.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1921
Out of the Box
Motorola
CINF014
Interfaces
External DB
The system must provide the capability to make
query responses accessible either through the
query response form or from the command line
and [shall/should] be associated with a query
response type.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1922
Out of the Box
Motorola
CINF015
Interfaces
External DB
The system must provide the capability to allow
users to submit new queries based on data in
the query response to logical links;
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1923
Out of the Box
Motorola
CINF016
Interfaces
External DB
Th system must also reference attachments
that are associated with the response, which
can be downloaded and viewed. Ideally, CAD
will provide the capability to view common
industry-standard multimedia file-types.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1924
Out of the Box
Motorola
CINF017
Interfaces
External DB
The system must provide the capability to
provide the capability to alert dispatchers, PSAP
supervisors, and street-level supervisors of
“Hot Hit” responses to queries made by officers
in the field, or data run that exists elsewhere in
the CAD system (i.e. in a CFS event).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1925
Out of the Box
Motorola
CINF018
Interfaces
External DB
The system must provide the capability to
provide optional audible and visual alerts that
can be configured by the system administrator.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1926
Out of the Box
Motorola
CINF019
Interfaces
External DB
The system must provide the capability to log
all queries and their responses (when
permitted) for audit purposes.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1927
Out of the Box
Motorola
CINF020
Interfaces
External DB
The system must provide the capability to
provide the ability to configure alerts for
queries run by unauthorized personnel or
devices, as well as the ability to monitor
multiple queries of the same data or specified
data.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1928
Out of the Box
Motorola
CINF021
Interfaces
Messaging
The system must provide the capability to be
capable of using industry-standard messaging
protocols such as SMS and SMTP.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1929
Out of the Box
Motorola
CINF022
Interfaces
Messaging
The system must provide the capability to
create (automatically) an SMTP message(s) for
selected CAD incidents.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1930
Out of the Box
Motorola
CINF023
Interfaces
Messaging
The system must provide the capability to
create (automatically) an alphanumeric page
for selected CAD incidents.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1931
Out of the Box
Motorola
CINF024
Interfaces
Messaging
The system must provide the capability to allow
a dispatcher to initiate an alphanumeric page
for any paging group.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1932
Out of the Box
Motorola
CINF025
Interfaces
Messaging
The information sent in the page [Shall/Should]
be configurable by the agency and
[shall/should] generally contain the incident
number, type of incident, and location of the
incident.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1933
Out of the Box
Motorola
CINF026
Interfaces
Messaging
The system must provide the capability to
provide an administrative mechanism to define
paging groups.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1934
Out of the Box
Motorola
CINF027
Interfaces
Messaging
The system must provide the capability to
include multiple message types, including
email, BOLOs, notifications, tactical command
chat rooms, and others.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1935
Out of the Box
Motorola
CINF028
Interfaces
Messaging
The system must provide the capability to
provide a capability to format and send
messages using just-in-time information, such
as incident dispatch information, BOLOs or
emergency weather alerts, and configurable
triggers for these messages (e.g. incident type,
assigned resources or location) for configurable
recipients (i.e. send the chief a page when a
specific incident type occurs at a specified
location).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1936
Out of the Box
Motorola
CINF029
Interfaces
Messaging
The system must provide the capability to
ensure that messaging interfaces make use of
the CAD address book.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1937
Out of the Box
Page 83of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CINF030
Interfaces
Messaging
The CAD address book [Shall/Should] allow for
defining the types of devices recipients are able
to receive messages on; and, [Shall/Should]
have the ability to define a default device, as
well as what devices (one, some or all) to
receive messages on by day/time/response
mode.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1938
Out of the Box
Motorola
CINF031
Interfaces
Messaging
The system must provide the capability to
provide the ability to include attachments
associated with the message that can be
downloaded and viewed by operators and
recipients. Ideally, CAD should provide a
capability to view common industry-standard
multimedia file-types.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1939
Out of the Box
Motorola
CINF032
Interfaces
Communications
Interfaces
The system must provide the capability to page
or text (automatically) a message to pre-
defined recipients or groups of recipients based
on the event type.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1940
Out of the Box
Motorola
CINF033
Interfaces
Communications
Interfaces
The system must provide the capability to
provide the capability for a CAD operator (PSAP
personnel or CAD users) to page, email, or text
a message to pre-defined recipients or groups
of recipients.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1941
Out of the Box
Motorola
CINF034
Interfaces
Communications
Interfaces
Integration / Interfaces with Other Systems:
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1942
Out of the Box
Motorola
CINF035
Interfaces
Communications
Interfaces
The system must provide the capability to allow
the agency direct access to the underlying
system information stored in the database
(ODBC, FTP, web services) for future interface
configuration, as well as appropriate database
and system documentation to support this
access.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1943
Out of the Box
Motorola
CINF036
Interfaces
Communications
Interfaces
The system must provide the capability to
interface with alarm monitoring companies
using ASAP. This interface must conform to
standards contained in the APCO/CSAA ANS
2.101.1-2008: Alarm Monitoring Company to
Public Safety Answering Point (PSAP) Computer-
Aided Dispatch (CAD) External Alarm Interface
Exchange.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1944
Out of the Box
Motorola
CINF037
Interfaces
National SAR
Initiative
Functionality
The system must provide the capability to allow
users to flag a CFS as “suspicious” with regard
to the National SAR Initiative.
Optional
CAD
X
PremierOne complies with the functionality as described in the requirement.
1945
Out of the Box
Motorola
CINF038
Interfaces
National SAR
Initiative
Functionality
The system must provide the capability to send
a “suspicious-flagged” CFS to an external
application, database, or RMS that handles SAR
reporting.
Optional
CAD
X
PremierOne complies with the functionality as described in the requirement.
1946
Out of the Box
Motorola
CINF039
Interfaces
National SAR
Initiative
Functionality
The system must provide the capability to
provide the capability to notify an intelligence
unit/counterterrorism unit when a SAR is
submitted.
Optional
CAD
X
PremierOne complies with the functionality as described in the requirement.
1947
Out of the Box
Motorola
CI001
Intercommunic
ation
Interface
All external communication with ACJIS will
occur via WebSphere MQ. Separate queues will
be provided for input and output. Input and
output will conform to AZ CJIS interface
specifications.
Mandatory
CAD
X
PremierOne does not utilize WebSphere MQ as a message queue.
P1 will correctly interface with the state for query and
IBR transactions, but not via WebSphere MQ.
MCSO & Motorola teams agree requirement is
met out of the box per notes in Column O.
1948
Cannot Meet
Motorola
CI001-1
Intercommunic
ation
Interface
Alternatively a driect connection to AZDPS for
ACJIS inquiries
Mandatory
CAD
X
Motorola Solutions has included the "State Query Interface" to provide the ability to run
ACJIS/NCIC Queries. The Interface allows PremierOne users to submit transactions to State and
Federal systems, via the State Message Switch. Query requests made on PremierOne CAD or
Mobile clients are routed to one of the PremierOne application servers. The PremierOne Query
Service processes the request and determines which data source(s) can fulfill the request. This
information is then passed to the PremierOne Common Services Interface (CSI) component, which
translates the request to XML messages and passes it on to the CommSys ConnectCIC. ConnectCIC
handles the State connection and translates the messages to the query strings required by the
State. The State Message Switch forwards the request to the appropriate system. When a
response is received, ConnectCIC parses and returns the response to CSI as an XML message. CSI
parses the response and forwards it to PremierOne Messaging Service, which handles the routing
of the query response to the requestor.
1949
With Third Party
Vendor
Motorola
CI002
Intercommunic
ation
Interface
On the MDC:
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1950
Out of the Box
Motorola
CI002-1
Intercommunic
ation
User Interface
The tag number field will be the only field
requiring entry when running a Arizona tag.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1951
Out of the Box
Motorola
CI002-2
Intercommunic
ation
User Interface
The drop-down states field will include all
states, (including Mexico and Canadian
territories), and U.S. territories.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1952
Out of the Box
Motorola
CI003
Intercommunic
ation
Interface
The system should restrict queries that result in
large volumes of data by:
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1953
Out of the Box
Motorola
CI003-1
Intercommunic
ation
User Interface
Warning of the numbers of records and amount
of data found
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1954
Out of the Box
Motorola
CI003-2
Intercommunic
ation
User Interface
Prompting the user to continue or discontinue
the query
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1955
Out of the Box
Page 84of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CI003-3
Intercommunic
ation
User Interface
Permit the viewing of a specified number of
records and data as set by the System
Administrator.
Mandatory
CAD
X
PremierOne does not have this functionality.
MCSO team stated this is not required to be met.
1956
Cannot Meet
Motorola
CI004
Intercommunic
ation
User Interface
The system should have the ability to sort
query results chronologically or by priority with
an option for descending or ascending order.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1957
Out of the Box
Motorola
CI005
Intercommunic
ation
Interface
The system should provide pre-defined agency-
configurable query forms to include:
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1958
Out of the Box
Motorola
CI005-1
Intercommunic
ation
User Interface
Log-on/log-off status
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1959
Out of the Box
Motorola
CI005-2
Intercommunic
ation
User Interface
Vehicle queries, including boats
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1960
Out of the Box
Motorola
CI005-3
Intercommunic
ation
User Interface
Gun queries
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1961
Out of the Box
Motorola
CI005-4
Intercommunic
ation
User Interface
Query by license plate number
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1962
Out of the Box
Motorola
CI005-5
Intercommunic
ation
User Interface
Query by VIN number
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1963
Out of the Box
Motorola
CI005-6
Intercommunic
ation
User Interface
Person query (to include searching with wild
cards, where allowed, e.g.. Age range),
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1964
Out of the Box
Motorola
CI005-7
Intercommunic
ation
User Interface
Wanted check by name
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1965
Out of the Box
Motorola
CI005-8
Intercommunic
ation
User Interface
Driver transcript query by name
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1966
Out of the Box
Motorola
CI005-9
Intercommunic
ation
User Interface
Driver transcript query by operator's license
number
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1967
Out of the Box
Motorola
CI005-10
Intercommunic
ation
User Interface
Local Warrant files
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1968
Out of the Box
Motorola
CI005-11
Intercommunic
ation
User Interface
Driver operator's license by name
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1969
Out of the Box
Motorola
CI005-12
Intercommunic
ation
User Interface
Driver operator's license by operator's license
number, or Social Security Number
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1970
Out of the Box
Motorola
CI005-13
Intercommunic
ation
User Interface
Criminal History
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1971
Out of the Box
Motorola
CI005-14
Intercommunic
ation
User Interface
All vehicles listed to an individual
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1972
Out of the Box
Motorola
CI005-15
Intercommunic
ation
User Interface
Premise information query, and
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1973
Out of the Box
Motorola
CI005-16
Intercommunic
ation
User Interface
All other agency-definable forms as defined by
MCSO
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1974
Out of the Box
Motorola
CI005-17
Intercommunic
ation
User Interface
MCSO is requesting the capability to create
additional query forms without vendor
assistance.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1975
Out of the Box
Motorola
CI006
Intercommunic
ation
User Interface
The system should allow queries to be grouped
and run automatically based upon event type.
For example, when a traffic stop is entered the
system should run the license plate as soon as
it is entered, run a name check on the
registered owner, and then return either a mug
photo or MVD photo of the registered owner.
If the driver is not the registered owner, the
system should run a name check on the driver
and the two photo inquiries (mug and MVD
photo).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1976
Out of the Box
Motorola
CI006-1
Intercommunic
ation
Interface
The system will support displaying AZ MVD
information and a front-facing image driver’s
license photo. Driver’s license photos will be
sent as a base 64-encoded string and will be
rendered in the CAD interface.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1977
Out of the Box
Motorola
Intercommunic
ation
Interface
MARICOPA COUNTY MUG SHOTS
1978
0
Motorola
CI007
Intercommunic
ation
Interface
The RMS system will provide an asynchronous
query and display mechanism to query
Maricopa County mug shots by the following
combinations:
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement. Motorola has
included an interface to query the County jail for mugshots.
1979
Out of the Box
Motorola
CI007-1
Intercommunic
ation
User Interface
Name and date of birth
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1980
Out of the Box
Motorola
CI007-2
Intercommunic
ation
User Interface
Maricopa County booking number
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1981
Out of the Box
Motorola
CI008
Intercommunic
ation
Interface
This request and the subsequent response shall
be sent via WebSphere MQ and will conform to
the AZ CJIS messaging protocol.
Mandatory
CAD
X
PremierOne does not utilize WebSphere MQ as a message queue.
P1 will correctly interface with the state for query and
IBR transactions, but not via WebSphere MQ.
MCSO & Motorola teams agree requirement is
met out of the box per notes in Column O.
1982
Cannot Meet
Motorola
CI009
Intercommunic
ation
User Interface
When an inquiry is automatically initiated due
to a field being entered on a call entry mask,
the resulting replies should have the capability
of being forwarded to the call taker and to the
units on, or responding to, the event, as
configured by MCSO.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1983
Out of the Box
Page 85of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CI010
Intercommunic
ation
User Interface
The system should provide the ability to display
and print an event record upon command,
based on a search of the file. When an event is
recalled, it appears with all event record
information displayed. MCSO will develop
report format criteria with the vendor during
application development.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1984
Out of the Box
Motorola
CI011
Intercommunic
ation
User Interface
It should be possible to search and retrieve
Event Records with full, partial or data in
multiple fields utilizing any combination, but
not limited to, the following user-defined
criteria:
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1985
Out of the Box
Motorola
CI011-1
Intercommunic
ation
User Interface
Event Number
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1986
Out of the Box
Motorola
CI011-2
Intercommunic
ation
User Interface
Address
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1987
Out of the Box
Motorola
CI011-3
Intercommunic
ation
User Interface
Commonplace Name
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1988
Out of the Box
Motorola
CI011-4
Intercommunic
ation
User Interface
Any or all Units assigned
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1989
Out of the Box
Motorola
CI011-5
Intercommunic
ation
User Interface
EIN of responding officer
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1990
Out of the Box
Motorola
CI011-6
Intercommunic
ation
User Interface
Name of responding officer
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1991
Out of the Box
Motorola
CI011-7
Intercommunic
ation
User Interface
Date Range
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1992
Out of the Box
Motorola
CI011-8
Intercommunic
ation
User Interface
Time Range
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1993
Out of the Box
Motorola
CI011-9
Intercommunic
ation
User Interface
Address range
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1994
Out of the Box
Motorola
CI011-10
Intercommunic
ation
User Interface
Time of event Creation
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1995
Out of the Box
Motorola
CI011-11
Intercommunic
ation
User Interface
Event Type
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1996
Out of the Box
Motorola
CI011-12
Intercommunic
ation
User Interface
Event Priority
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1997
Out of the Box
Motorola
CI011-13
Intercommunic
ation
User Interface
Event Urgency Code
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1998
Out of the Box
Motorola
CI011-14
Intercommunic
ation
User Interface
Disposition
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
1999
Out of the Box
Motorola
CI011-15
Intercommunic
ation
User Interface
Case Number
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2000
Out of the Box
Motorola
CI011-16
Intercommunic
ation
User Interface
Any telephone number recorded in the event
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2001
Out of the Box
Motorola
CI011-17
Intercommunic
ation
User Interface
Any license plate number recorded in the event Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2002
Out of the Box
Motorola
CI011-18
Intercommunic
ation
User Interface
Any name recorded in the event
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2003
Out of the Box
Motorola
CI011-19
Intercommunic
ation
User Interface
District
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2004
Out of the Box
Motorola
CI011-20
Intercommunic
ation
User Interface
Field Area (FA)
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2005
Out of the Box
Motorola
CI011-21
Intercommunic
ation
User Interface
EIN of entering user
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2006
Out of the Box
Motorola
CI011-22
Intercommunic
ation
User Interface
EIN of dispatching user
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2007
Out of the Box
Motorola
CI011-23
Intercommunic
ation
User Interface
Terminal ID for entering workstation
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2008
Out of the Box
Motorola
CI011-24
Intercommunic
ation
User Interface
By attached ANI/ALI data
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2009
Out of the Box
Motorola
CI011-25
Intercommunic
ation
User Interface
By key words search in remarks area
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2010
Out of the Box
Motorola
CI012
Intercommunic
ation
User Interface
All of the above fields should be capable of
being searched upon from within the CAD client
by personnel as authorized by the System
Administrator.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2011
Out of the Box
Motorola
CI013
Intercommunic
ation
User Interface
It should be possible to query Unit History
detail by all available data fields, including but
not limited to:
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2012
Out of the Box
Motorola
CI013-1
Intercommunic
ation
User Interface
Unit Number
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2013
Out of the Box
Motorola
CI013-2
Intercommunic
ation
User Interface
Event Number
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2014
Out of the Box
Motorola
CI013-3
Intercommunic
ation
User Interface
Date and time range
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2015
Out of the Box
Motorola
CI013-4
Intercommunic
ation
User Interface
Location
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2016
Out of the Box
Motorola
CI013-5
Intercommunic
ation
User Interface
Vehicle number
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2017
Out of the Box
Motorola
CI013-6
Intercommunic
ation
User Interface
By Map Grid/Zone
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2018
Out of the Box
Motorola
CI013-7
Intercommunic
ation
User Interface
District
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2019
Out of the Box
Motorola
CI013-8
Intercommunic
ation
User Interface
Patrol Area
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2020
Out of the Box
Page 86of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CI014
Intercommunic
ation
User Interface
Through the standard report menu personnel
should be able to receive a Unit History Log.
This user-definable report:
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2021
Out of the Box
Motorola
CI014-1
Intercommunic
ation
User Interface
Contains a log of activities by shift(s), officer(s),
unit assignment(s), Patrol Area(s), District(s),
vehicle, emergency switch, and/or agency for a
given date span.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2022
Out of the Box
Motorola
CI014-2
Intercommunic
ation
User Interface
Shows all activities to which given units or
personnel have responded.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2023
Out of the Box
Motorola
CI014-3
Intercommunic
ation
User Interface
Is particularly useful in reviewing an employee
or unit's work for a given period of time. The
user defines the parameters of the report.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2024
Out of the Box
Motorola
CI015
Intercommunic
ation
User Interface
The system should allow:
Mandatory
CAD
X
PremierOne will meet the County's requirement for robust data analysis, reporting, and
dashboard capabilities. In addition, PremierOne is deployed with a Reporting Data Warehouse
(RDW) which is a near real time copy (mirror) of the production database.
PremierOne CAD utilizes Microsoft SQL Server Reporting Services (SSRS) for its standard reports.
SSRS is a server-based reporting platform that is used to create and manage tabular, matrix,
graphical, dashboards, and free form reports that contain data from relational and
multidimensional data sources. A sample of the standard reports include Average Response
Times by Incident Type, BOLO Messages, Various Calls For Service reports, various Incident
reports (grouped by type, by area, etc), Login and Logoff, various Provisioning reports, Purge
schedule, various Query reports, and Officer Activity. As part of deployment, Motorola will apply
canned reports to the system and lead a reporting writing workshop with County personnel. The
Motorola system is capable of creating and printing reports with information available in the
database via SSRS reports authored by the County.
2025
Out of the Box
Motorola
CI015-1
Intercommunic
ation
User Interface
Retrieval of the history of a selected employee,
including all times which can be sorted by the
user.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2026
Out of the Box
Motorola
CI015-2
Intercommunic
ation
User Interface
Retrieval of the history of a selected unit,
including all times which can be sorted by the
user.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2027
Out of the Box
Motorola
CI015-3
Intercommunic
ation
User Interface
User defined queries of any data associated
with an event, unit, or employee for any given
date and/or time.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2028
Out of the Box
Motorola
CI015-4
Intercommunic
ation
User Interface
The preparation of an ad-hoc report that
illustrates the unit and event history of any
patrol shift or District by user-defined dates and
times.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2029
Out of the Box
Motorola
CI016
Intercommunic
ation
User Interface
The system should also provide the ability to
prepare Unit History Reports for ECC personnel,
i.e., calltakers and dispatchers.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2030
Out of the Box
Motorola
CI017
Intercommunic
ation
User Interface
When MCSO patrol personnel are not handling
a dispatched assignment they utilize "In-
service" discretionary time for directed
activities. The system should provide the
capability for authorized users to prepare user-
definable reports that illustrate in statistical
and graphical terms each period of "In-service"
time that was available for any officer/unit
during any user-definable date and time period.
The system should be capable of reporting this
data as a sum (the total amount of "In-service"
time available for any officer/unit for a given
tour of duty) and as a summary representation
of the "blocks" or, "In-service" time that was
available between assignments (e.g., during any
given tour of duty how many blocks of "In-
service" time were available and what was their
duration [for each block and as an average of
the blocks for the tour of duty].
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2031
Out of the Box
Motorola
CI018
Intercommunic
ation
User Interface
The system should provide the capability to
prepare the aforementioned report by a single
unit/officer and any number of units/officers
for a user-definable time and date range.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2032
Out of the Box
Motorola
CI019
Intercommunic
ation
User Interface
The system should be capable of preparing user-
definable agency specific standard reports for
emergency calls, non-emergency calls, and both
combined, including but not limited to:
Mandatory
CAD
X
PremierOne will meet the County's requirement for robust data analysis, reporting, and
dashboard capabilities. In addition, PremierOne is deployed with a Reporting Data Warehouse
(RDW) which is a near real time copy (mirror) of the production database.
PremierOne CAD utilizes Microsoft SQL Server Reporting Services (SSRS) for its standard reports.
SSRS is a server-based reporting platform that is used to create and manage tabular, matrix,
graphical, dashboards, and free form reports that contain data from relational and
multidimensional data sources. A sample of the standard reports include Average Response
Times by Incident Type, BOLO Messages, Various Calls For Service reports, various Incident
reports (grouped by type, by area, etc), Login and Logoff, various Provisioning reports, Purge
schedule, various Query reports, and Officer Activity. As part of deployment, Motorola will apply
canned reports to the system and lead a reporting writing workshop with County personnel. The
Motorola system is capable of creating and printing reports with information available in the
database via SSRS reports authored by the County.
2033
Out of the Box
Motorola
CI019-1
Intercommunic
ation
User Interface
Number of events by event type, or by calendar
day/time/week/shift
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2034
Out of the Box
Page 87of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CI019-2
Intercommunic
ation
User Interface
Number of events by day of week and/or time
of day
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2035
Out of the Box
Motorola
CI020
Intercommunic
ation
User Interface
Reports should be capable of being generated
based on data such as but not limited to
(reports may be based on multiple fields):
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2036
Out of the Box
Motorola
CI020-1
Intercommunic
ation
User Interface
Date
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2037
Out of the Box
Motorola
CI020-2
Intercommunic
ation
User Interface
Time of day
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2038
Out of the Box
Motorola
CI020-3
Intercommunic
ation
User Interface
Day of week
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2039
Out of the Box
Motorola
CI020-4
Intercommunic
ation
User Interface
Event Type
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2040
Out of the Box
Motorola
CI020-5
Intercommunic
ation
User Interface
Priority
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2041
Out of the Box
Motorola
CI020-6
Intercommunic
ation
User Interface
Group
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2042
Out of the Box
Motorola
CI020-7
Intercommunic
ation
User Interface
District
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2043
Out of the Box
Motorola
CI020-8
Intercommunic
ation
User Interface
Patrol Area
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2044
Out of the Box
Motorola
CI020-9
Intercommunic
ation
User Interface
Terminal ID for entering workstation
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2045
Out of the Box
Motorola
CI020-10
Intercommunic
ation
User Interface
EIN of entering user
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2046
Out of the Box
Motorola
CI020-11
Intercommunic
ation
User Interface
EIN of dispatching user
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2047
Out of the Box
Motorola
CI020-12
Intercommunic
ation
User Interface
EIN of Assigned Unit
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2048
Out of the Box
Motorola
CI020-13
Intercommunic
ation
User Interface
Response time
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2049
Out of the Box
Motorola
CI020-14
Intercommunic
ation
User Interface
Average response time
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2050
Out of the Box
Motorola
CI020-15
Intercommunic
ation
User Interface
Disposition code applied
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2051
Out of the Box
Motorola
CI020-16
Intercommunic
ation
User Interface
Call time (from entry to completion (closed))
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2052
Out of the Box
Motorola
CI020-17
Intercommunic
ation
User Interface
Average call time (from entry to completion
(closed))
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2053
Out of the Box
Motorola
CI020-18
Intercommunic
ation
User Interface
Average response time to events by reporting
area by event type and time of day
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2054
Out of the Box
Motorola
CI020-19
Intercommunic
ation
User Interface
Average response time to events by reporting
area by event type and day of week
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2055
Out of the Box
Motorola
CI020-20
Intercommunic
ation
User Interface
Average response time to events by reporting
area by event type and shift (from time a call is
received to dispatch, and time of dispatch to
first unit on the scene, and time of call received
to arrival of first unit on the scene).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2056
Out of the Box
Motorola
CI020-21
Intercommunic
ation
User Interface
Average time to dispatch for all call types based
on priority.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2057
Out of the Box
Motorola
CI020-22
Intercommunic
ation
User Interface
Average time to dispatch from the first CAD
time stamp (when the call is accepted at the
call taker position) by Agency
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2058
Out of the Box
Motorola
CI020-23
Intercommunic
ation
User Interface
Total person hours expended on events by call
type (burglar alarms, disorderly conduct, etc.)
by time of day, day of week, etc., and
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2059
Out of the Box
Motorola
CI020-24
Intercommunic
ation
User Interface
The sum of total staffing hours that were
available by agency, by rank/position and all
other available CAD criteria.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2060
Out of the Box
Motorola
CI020-25
Intercommunic
ation
User Interface
Elapsed time expended processing calls, from
time the ANI/ALI appears on the call taker
screen to the time
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2061
Out of the Box
Motorola
CI020-26
Intercommunic
ation
User Interface
The call taker sends the initial event
information to the dispatcher
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2062
Out of the Box
Motorola
CI020-27
Intercommunic
ation
User Interface
The call is concluded and the time the event
information is sent to the dispatcher (wrap-up
time)
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2063
Out of the Box
Motorola
CI020-28
Intercommunic
ation
User Interface
The event is dispatched
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2064
Out of the Box
Motorola
CI021
Intercommunic
ation
User Interface
The system should track and report on average
times to dispatch for all event types.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2065
Out of the Box
Motorola
CI022
Intercommunic
ation
User Interface
The system should be able to report total staff
hours expended on specific events/incident
types and prepare summary and ad-hoc reports
based on user-definable parameters such as
event type(s), date and time ranges, etc.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2066
Out of the Box
Motorola
CI023
Intercommunic
ation
User Interface
This report should be configurable and sortable. Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2067
Out of the Box
Motorola
CI024
Intercommunic
ation
User Interface
This report is in addition to the capture and
reporting of individual unit dispatch and arrival
times.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2068
Out of the Box
Page 88of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CI025
Intercommunic
ation
User Interface
The system administrator should be able to
easily create new event codes. For example, it
will be possible to create an event code which
users can apply to all events in which MCSO are
engaged in flood relief activities. In this
example, authorized users will be able to search
by the event code to determine the total
number of staff-hours expended on flood relief
activities by a user-definable date and time
range.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2069
Out of the Box
Motorola
CI026
Intercommunic
ation
User Interface
The appearance and layout of all reports and
queries should be user-definable
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2070
Out of the Box
Motorola
CI026-1
Intercommunic
ation
User Interface
The user should be able to save the report
format for future use.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2071
Out of the Box
Motorola
CI027
Intercommunic
ation
User Interface
The reports should be able to be sent to a
printer selected by the user performing the
search/report or to a user-definable default
printer.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2072
Out of the Box
Motorola
CI028
Intercommunic
ation
User Interface
The reports should be able to be saved to a
format that permits the archiving and e-mailing
of the report as an attachment that can be
viewed in any external application.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2073
Out of the Box
Motorola
CI029
Intercommunic
ation
User Interface
The system should be capable of extracting
data to be sent to a third party vendor. This
should include all reports (statistical, graphical,
etc.) resulting from CAD and RMS queries.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2074
Out of the Box
Motorola
CI030
Intercommunic
ation
User Interface
The system should provide an external facing
API for data reporting to third party providers.
Mandatory
CAD
X
PremierOne does not currently support an API that allows custom development. However,
functionality may be be implemented with existing PremierOne features:
PremierOne allows third-party systems to retrieve near real time information from PremierOne
CAD RDW. PremierOne is set up to post transactional updates from CAD to the RDW database
within 30 seconds. Standard SQL Views are available in PremierOne CAD RDW. A SQL account with
read-only access to these views will be created for the third-party system. The third-party system
can retrieve PremierOne data using a SQL connection.
MCSO is in agreement with explanation provided in
column N.
MCSO requires data access, which is available in the
reporting data warehouse for both CAD and Records.
MCSO & Motorola teams agree requirement is
met out of the box per notes in Column N.
2075
Cannot Meet
Motorola
CI031
Intercommunic
ation
User Interface
The system should be capable of preparing a
user-definable report which illustrates
(textually and graphically/spatially) for each
event, the location of each responding unit at
the time they received the dispatched event.
This information should be logged as part of
each event history.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2076
Out of the Box
Motorola
CI032
Intercommunic
ation
User Interface
The system should be capable of preparing a
user-definable report which illustrates and
compares 1) the travel time expended for each
responding unit from time of dispatch to time
of arrival versus 2) the CUFRR estimated time of
travel for each responding unit from time of
dispatch to time of arrival on the scene.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2077
Out of the Box
Motorola
CI033
Intercommunic
ation
User Interface
The system should permit the preparation of
user-definable year-end/12-month CAD
management reports based on any of the
aforementioned report criteria. Such report
production will require a minimum of one year
of CAD data.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2078
Out of the Box
Motorola
CI034
Intercommunic
ation
User Interface
The system should also provide a subsystem
where a user can query the system for a certain
type of skill set (i.e. a person who speaks
Spanish and has CPR training).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2079
Out of the Box
Motorola
CI035
Intercommunic
ation
User Interface
The system should provide the full complement
of NCIC, NLETS and ACJIS update and query
transactions. Entry masks should be included
for the most commonly used transactions (i.e.
Criminal history, Drivers License, Vehicle Want
and Registration, Firearm, Boats and messaging
to and from other ORI identified agencies.
Vendors shall specify what entry masks come
with their system and the cost to acquire
additional masks if so desired. The capability to
enter queries in a string format (expert mode)
must be made available for all transactions.
Mandatory
CAD
X
Motorola Solutions has included the "State Query Interface" to provide the ability to run
ACJIS/NCIC Queries. The Interface allows PremierOne users to submit transactions to State and
Federal systems, via the State Message Switch. Query requests made on PremierOne CAD or
Mobile clients are routed to one of the PremierOne application servers. The PremierOne Query
Service processes the request and determines which data source(s) can fulfill the request. This
information is then passed to the PremierOne Common Services Interface (CSI) component, which
translates the request to XML messages and passes it on to the CommSys ConnectCIC. ConnectCIC
handles the State connection and translates the messages to the query strings required by the
State. The State Message Switch forwards the request to the appropriate system. When a
response is received, ConnectCIC parses and returns the response to CSI as an XML message. CSI
parses the response and forwards it to PremierOne Messaging Service, which handles the routing
of the query response to the requestor.
2080
With Third Party
Vendor
Motorola
CI036
Intercommunic
ation
Interface
The system should be able to communicate to
third party API in a bi-directional way. This
should allow interfaces such as ASAP to PSAP to
exchange data.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2081
Out of the Box
Page 89of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CNT001
NLETS
Transactions
User Interface
System should all available NLETS/ACJIS/MVD
and RMS transactions including, but not limited
to the following:
Mandatory
CAD/Mobile/Record
s
X
PremierOne complies with the functionality as described in the requirement. Motorola Solutions
has included the "State Query Interface" to provide the ability to run FCIC/NCIC Queries. The
Interface allows PremierOne users to submit transactions to State and Federal systems, via the
State Message Switch. Query requests made on PremierOne CAD or Mobile clients are routed to
one of the PremierOne application servers. The PremierOne Query Service processes the request
and determines which data source(s) can fulfill the request. This information is then passed to the
PremierOne Common Services Interface (CSI) component, which translates the request to XML
messages and passes it on to the CommSys ConnectCIC. ConnectCIC handles the State connection
and translates the messages to the query strings required by the State. The State Message Switch
forwards the request to the appropriate system. When a response is received, ConnectCIC parses
and returns the response to CSI as an XML message. CSI parses the response and forwards it to
PremierOne Messaging Service, which handles the routing of the query response to the requestor.
2082
With Third Party
Vendor
Motorola
CNT001-1
NLETS
Transactions
User Interface
MKE Description
Mandatory
CAD/Mobile/Record
s
X
PremierOne complies with the functionality as described in the requirement.
2083
Out of the Box
Motorola
CNT001-2
NLETS
Transactions
User Interface
ACQ/AVQ NLETS Commercial Carrier
Query
Mandatory
CAD/Mobile/Record
s
X
PremierOne complies with the functionality as described in the requirement.
2084
Out of the Box
Motorola
CNT001-3
NLETS
Transactions
User Interface
AVQ NLETS Commercial Vehicle
Query
Mandatory
CAD/Mobile/Record
s
X
PremierOne complies with the functionality as described in the requirement.
2085
Out of the Box
Motorola
CNT001-4
NLETS
Transactions
User Interface
CWQ Interstate Concealed
Weapons Permit Query
Mandatory
CAD/Mobile/Record
s
X
PremierOne complies with the functionality as described in the requirement.
2086
Out of the Box
Motorola
CNT001-5
NLETS
Transactions
User Interface
DQ Interstate Driver’s License
Query
Mandatory
CAD/Mobile/Record
s
X
PremierOne complies with the functionality as described in the requirement.
2087
Out of the Box
Motorola
CNT001-6
NLETS
Transactions
User Interface
IPQ/FPQ Interpol Wanted Persons
Mandatory
CAD/Mobile/Record
s
X
PremierOne complies with the functionality as described in the requirement.
2088
Out of the Box
Motorola
CNT001-7
NLETS
Transactions
User Interface
ITQ/FTQ Interpol Stolen Travel
Documents
Mandatory
CAD/Mobile/Record
s
X
PremierOne complies with the functionality as described in the requirement.
2089
Out of the Box
Motorola
CNT001-8
NLETS
Transactions
User Interface
IVQ/FVQ Interpol Stolen Vehicles
Mandatory
CAD/Mobile/Record
s
X
PremierOne complies with the functionality as described in the requirement.
2090
Out of the Box
Motorola
CNT001-9
NLETS
Transactions
User Interface
KQ Interstate Driver’s License
History
Mandatory
CAD/Mobile/Record
s
X
PremierOne complies with the functionality as described in the requirement.
2091
Out of the Box
Motorola
CNT001-10
NLETS
Transactions
User Interface
RQ Interstate Vehicle
Registration Query
Mandatory
CAD/Mobile/Record
s
X
PremierOne complies with the functionality as described in the requirement.
2092
Out of the Box
Motorola
CNT001-11
NLETS
Transactions
User Interface
VQ Canadian Stolen Vehicle
Query
Mandatory
CAD/Mobile/Record
s
X
PremierOne complies with the functionality as described in the requirement.
2093
Out of the Box
Motorola
CNT001-12
NLETS
Transactions
User Interface
WQ Canadian Wanted Person
Query
Mandatory
CAD/Mobile/Record
s
X
PremierOne complies with the functionality as described in the requirement.
2094
Out of the Box
Motorola
CNT001-13
NLETS
Transactions
User Interface
XQ Canadian Vehicle
Registration Query
Mandatory
CAD/Mobile/Record
s
X
PremierOne complies with the functionality as described in the requirement.
2095
Out of the Box
Motorola
CNT001-14
NLETS
Transactions
User Interface
DQP - Ability to request picture from MVD
Mandatory
CAD/Mobile/Record
s
X
PremierOne complies with the functionality as described in the requirement.
2096
Out of the Box
Motorola
CSIA001
Situational
Awareness
Architecture
The solution shall be Cloud-hosted
Mandatory
CommandCentral
Aware
X
PremierOne complies with the functionality as described in the requirement.
2097
Out of the Box
Motorola
CSIA002
Situational
Awareness
Architecture
The solution shall be a browser based mapping
application
Mandatory
CommandCentral
Aware
X
PremierOne complies with the functionality as described in the requirement.
2098
Out of the Box
Motorola
CSIA003
Situational
Awareness
Architecture
The solution shall be available on tablets
Mandatory
CommandCentral
Aware
X
PremierOne complies with the functionality as described in the requirement.
2099
Out of the Box
Motorola
CSIA004
Situational
Awareness
Architecture
The solution shall support Esri ArcGIS data
Mandatory
CommandCentral
Aware
X
PremierOne complies with the functionality as described in the requirement.
2100
Out of the Box
Motorola
CSIA005
Situational
Awareness
Video Streaming
The solution shall support in-car-vehicle camera
real-time streaming
Mandatory
CommandCentral
Aware
X
PremierOne complies with the functionality as described in the requirement.
2101
Out of the Box
Motorola
CSIA006
Situational
Awareness
Video Streaming
The solution shall support body-worn camera
real-time streaming
Mandatory
CommandCentral
Aware
X
PremierOne complies with the functionality as described in the requirement.
2102
Out of the Box
Motorola
CSIA007
Situational
Awareness
Video Streaming
The solution shall support fixed video real-time
streaming
Mandatory
CommandCentral
Aware
X
PremierOne complies with the functionality as described in the requirement.
2103
Out of the Box
Motorola
CSIA008
Situational
Awareness
Video Streaming
The solution shall support manned/unmanned
video feeds, such as drones
Mandatory
CommandCentral
Aware
X
PremierOne complies with the functionality as described in the requirement.
2104
Out of the Box
Motorola
CSIA009
Situational
Awareness
Video Streaming
The solution shall support multiple camera
layouts
Mandatory
CommandCentral
Aware
X
PremierOne complies with the functionality as described in the requirement.
2105
Out of the Box
Motorola
CSIA010
Situational
Awareness
Video Streaming
The solution shall allow users to view up to 16
real time video feeds on 1 tab
Mandatory
CommandCentral
Aware
X
PremierOne complies with the functionality as described in the requirement.
2106
Out of the Box
Motorola
CSIA011
Situational
Awareness
Location
The solution shall support responder vehicle
location via mobile video reporting
Mandatory
CommandCentral
Aware
X
PremierOne complies with the functionality as described in the requirement.
2107
Out of the Box
Motorola
CSIA012
Situational
Awareness
Location
The solution shall support responder vehicle
location via Automatic Vehicle Location (AVL)
Mandatory
CommandCentral
Aware
X
PremierOne complies with the functionality as described in the requirement.
2108
Out of the Box
Motorola
CSIA013
Situational
Awareness
Location
The solution shall support real-time responder
location via radio devices, PTToC application
reporting and body worn cameras
Preferred
CommandCentral
Aware
X
PremierOne complies with the functionality as described in the requirement.
2109
Out of the Box
Motorola
CSIA014
Situational
Awareness
Incident Re-creation The solution shall support breadcrumbing trail
of mobile video device
Mandatory
CommandCentral
Aware
X
PremierOne complies with the functionality as described in the requirement.
2110
Out of the Box
Motorola
CSIA015
Situational
Awareness
Incident Re-creation The solution shall support breadcrumbing trail
of radio devices and/ or PTToC application
location
Preferred
CommandCentral
Aware
X
PremierOne complies with the functionality as described in the requirement.
2111
Out of the Box
Motorola
CSIA016
Situational
Awareness
Incident Re-creation The solution shall support historical Mapping of
mobile video device
Mandatory
CommandCentral
Aware
X
PremierOne complies with the functionality as described in the requirement.
2112
Out of the Box
Motorola
CSIA017
Situational
Awareness
Incident Re-creation The solution shall support historical Mapping of
radio devices and/ or PTToC application
Preferred
CommandCentral
Aware
X
PremierOne complies with the functionality as described in the requirement.
2113
Out of the Box
Motorola
CSIA018
Situational
Awareness
GIS Map Intelligence The solution shall support customized workflow
with rules and conditions (i.e. rules engine)
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2114
Out of the Box
Page 90of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CSIA019
Situational
Awareness
GIS Map Intelligence The solution shall support the ability to
geofence boundaries via mobile video device
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2115
Out of the Box
Motorola
CSIA020
Situational
Awareness
GIS Map Intelligence The solution shall support the ability to
geofence boundaries via radio devices and/ or
PTToC application
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2116
Out of the Box
Motorola
CSIA021
Situational
Awareness
GIS Map Intelligence The solution shall support directed patrol via
mobile video device
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2117
Out of the Box
Motorola
CSIA022
Situational
Awareness
GIS Map Intelligence The solution shall support directed patrol via
radio devices and/or PTToC application
reporting
Preferred
CAD
X
PremierOne complies with the functionality as described in the requirement.
2118
Out of the Box
Motorola
CSIA023
Situational
Awareness
GIS Map Intelligence The solution shall support multiple zones of
interest, such as crime zones of mobile video
device
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2119
Out of the Box
Motorola
CSIA024
Situational
Awareness
GIS Map Intelligence The solution shall support multiple zones of
interest, such as crime zones of radio devices
and/ or PTToC application
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2120
Out of the Box
Motorola
CSIA025
Situational
Awareness
GIS Map Intelligence The solution shall support identification and
alerts of cameras near occuring incidents
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2121
Out of the Box
Motorola
CSIA026
Situational
Awareness
GIS Map Intelligence The solution shall allow for Pan-Tilt-Zoom (PTZ)
to defined preset locations
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2122
Out of the Box
Motorola
CSIA027
Situational
Awareness
GIS Map Intelligence The solution shall support tactical whiteboard
response plans
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2123
Out of the Box
Motorola
CSIA028
Situational
Awareness
GIS Map Intelligence The solution shall support real-time weather
feeds
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2124
Out of the Box
Motorola
CSIA029
Situational
Awareness
GIS Map Intelligence The solution shall support real-time traffic
feeds
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2125
Out of the Box
Motorola
CSIA030
Situational
Awareness
GIS Map Intelligence The solution shall support the importing of
floor plans
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2126
Out of the Box
Motorola
CSIA031
Situational
Awareness
GIS Map Intelligence The solution shall support Wi-Fi positioning via
radion device or body-worn camera (BWC)
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2127
Out of the Box
Motorola
CSIA032
Situational
Awareness
GIS Map Intelligence The solution shall support gunshot detection
alerts on the map
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2128
Out of the Box
Motorola
CSIA033
Situational
Awareness
GIS Map Intelligence The solution shall support unit management of
multiple mobile video devices of officer in/ out
vehicle
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2129
Out of the Box
Motorola
CSIA034
Situational
Awareness
GIS Map Intelligence The solution shall support unit management of
multiple radio devices and/ or PTToC app of an
officer in/ out vehicle
Preferred
CAD
X
PremierOne complies with the functionality as described in the requirement.
2130
Out of the Box
Motorola
CSIA035
Situational
Awareness
GIS Map Intelligence The solution shall include a staleness status
indicator for mobile video device/ unit
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2131
Out of the Box
Motorola
CSIA036
Situational
Awareness
GIS Map Intelligence The solution shall include a staleness status
indicator for radio and/or PTToC device/unit
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2132
Out of the Box
Motorola
CSIA037
Situational
Awareness
Search
The solution shall support federated query
integration with external databases
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2133
Out of the Box
Motorola
CSIA038
Situational
Awareness
Search
The solution shall support searching for a radio
device subscriber using Radio ID or Alias
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2134
Out of the Box
Motorola
CSIA039
Situational
Awareness
Video/access Control
Integration
The solution shall include a Video Module Audit
Log
Mandatory
CommandCentral
Aware
X
PremierOne complies with the functionality as described in the requirement.
2135
Out of the Box
Motorola
CSIA040
Situational
Awareness
Video/access Control
Integration
The solution shall incorporate Fixed Video
Management System (VMS) solutions into one
single screen
Mandatory
CommandCentral
Aware
X
PremierOne complies with the functionality as described in the requirement.
2136
Out of the Box
Motorola
CSIA041
Situational
Awareness
Video/access Control
Integration
The solution shall support automated trigger
opening of nearby fixed cameras
Mandatory
CommandCentral
Aware
X
PremierOne complies with the functionality as described in the requirement.
2137
Out of the Box
Motorola
CSIA042
Situational
Awareness
Video/access Control
Integration
The solution shall support automated fixed
video alerting (via rules engine)
Mandatory
CommandCentral
Aware
X
PremierOne complies with the functionality as described in the requirement.
2138
Out of the Box
Motorola
CSIA043
Situational
Awareness
Video/access Control
Integration
The solution shall include the ability to view
Access Control alerts from map
Mandatory
CommandCentral
Aware
X
PremierOne complies with the functionality as described in the requirement.
2139
Out of the Box
Motorola
CSIA044
Situational
Awareness
Video/access Control
Integration
The solution shall support CCTV real-time video
streaming
Mandatory
CommandCentral
Aware
X
PremierOne complies with the functionality as described in the requirement.
2140
Out of the Box
Motorola
CSIA045
Situational
Awareness
Video/access Control
Integration
The solution shall include fixed video analytics
Mandatory
CommandCentral
Aware
X
PremierOne complies with the functionality as described in the requirement.
2141
Out of the Box
Motorola
CSIA046
Situational
Awareness
LPR Integration
The solution shall support LPR Integration
Preferred
CommandCentral
Aware
X
PremierOne complies with the functionality as described in the requirement.
2142
Out of the Box
Motorola
CSIA047
Situational
Awareness
LPR Integration
Vendor to explain integration with LPR solution Preferred
CommandCentral
Aware
X
PremierOne complies with the functionality as described in the requirement. CommandCentral
Aware integrates with the Vigilant LEARN solution, which enables search and analysis of Vigilant
LPR detections within the Aware Map Module. When a license plate detection displays in real-
time on the Aware map, the license plate can be searched directly from the CommandCentral
Aware interface enabling you to see previous historical detections (time, date, location) and
additional details associated with the license plate. With an existing Vigilant LEARN subscription,
users can analyze and research the LPR hit for more information and research the plate from the
LEARN database.
2143
Out of the Box
Page 91of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CSIA048
Situational
Awareness
Digital Evidence
Management
System (DEMS)
Integration
The solution shall support Digital Evidence
Management System (DEMS) integration for
mobile video
Preferred
CommandCentral
Aware
X
PremierOne complies with the functionality as described in the requirement.
2144
Out of the Box
Motorola
CSIA049
Situational
Awareness
Digital Evidence
Management
System (DEMS)
Integration
The solution shall support Digital Evidence
Management System (DEMS) integration for
fixed camera
Preferred
CommandCentral
Aware
X
PremierOne complies with the functionality as described in the requirement.
2145
Out of the Box
Motorola
CSIA050
Situational
Awareness
Digital Evidence
Management
System (DEMS)
Integration
The solution shall support CAD integration
Preferred
CommandCentral
Aware
X
PremierOne complies with the functionality as described in the requirement.
2146
Out of the Box
Motorola
CSIA051
Situational
Awareness
Digital Evidence
Management
System (DEMS)
Integration
The solution shall support CAD Event Monitor
Preferred
CommandCentral
Aware
X
PremierOne complies with the functionality as described in the requirement.
2147
Out of the Box
Motorola
CSIA052
Situational
Awareness
Community
Engagement
Integration
The solution shall support private citizen
cameras registration/ camera location shown
on the map
Preferred
CommandCentral
Community
X
PremierOne complies with the functionality as described in the requirement.
2148
Out of the Box
Motorola
CSIA053
Situational
Awareness
Community
Engagement
Integration
The solution shall support anonymous Tipping
displayed on a map or via SMS
Preferred
CommandCentral
Community
X
PremierOne complies with the functionality as described in the requirement.
2149
Out of the Box
Motorola
CSIA054
Situational
Awareness
9-1-1 Integration
The solution shall include real-time precise
caller location via RapidSOS and ANI/ALI
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement. RapidSOS
Integration with PremierOne CAD is included with our solution.
2150
With Third Party
Vendor
Motorola
CSIA055
Situational
Awareness
9-1-1 Integration
The solution shall include real-time 9-1-1 Call
Plotting (i.e. location updates)
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2151
Out of the Box
Motorola
CSIA056
Situational
Awareness
9-1-1 Integration
The solution shall include breadcrumb trail of
caller's location
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2152
Out of the Box
Motorola
CSIA057
Situational
Awareness
9-1-1 Integration
The solution shall indicate 9-1-1 call status
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2153
Out of the Box
Motorola
CSIA058
Situational
Awareness
CJIS Compliance
The solution shall be CJIS Compliant
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2154
Out of the Box
Motorola
CSIA059
Situational
Awareness
CJIS Compliance
The solution shall be FISMA Compliant
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2155
Out of the Box
Motorola
CSIA060
Situational
Awareness
CJIS Compliance
The solution shall be Federal Risk and
Authorization Management Program
(FedRAMP) Compliant
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2156
Out of the Box
Motorola
CSIA061
Situational
Awareness
CJIS Compliance
The solution shall be SOC 2 compliant
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2157
Out of the Box
Motorola
CTDD001
TDD
User Interface
The CAD system should import TDD
information (ANI/ALI and narrative data) from
the MR 911 system into the event entry form
as defined by the agency.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2158
Out of the Box
Motorola
CTDD002
TDD
User Interface
The CAD system should assign unique numbers
to each TDD communication.
Mandatory
CAD
X
PremierOne does not have this functionality.
MCSO team stated this is not required to be met.
2159
Cannot Meet
Motorola
CTDD003
TDD
User Interface
If the TDD communication is related to event
entry the event should reflect the unique TDD
number
Mandatory
CAD
X
PremierOne does not have this functionality.
MCSO team stated this is not required to be met.
2160
Cannot Meet
Motorola
CTDD004
TDD
User Interface
The user should have the ability to choose to
include the text of the TDD conversation in a
related event, regardless of the TDD call being
processed on the CAD system or MR 911
system.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement. The text would be
manually copied from one event to another.
2161
Out of the Box
Motorola
CTDD005
TDD
User Interface
The system should comply with Americans with
Disabilities Act (ADA) Title II, Part IV, and
Paragraph 35.162.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2162
Out of the Box
Motorola
CSF001
Supervisor
Functionality
General
For performance reviews authorized
supervisors need the ability to observe in real
time all the activities of a specific work station.
The system should provide the ability for any
authorized ECC supervisor to remotely view any
ECC CAD terminal.
Mandatory
CAD
X
A Supervisor could bring up the same information in the same status monitors using a console
control command. The user can not bring up the specific dispatcher, but can bring up the same
coverage group.
Supervisor can see what is going on with any incident
and units but does not have a remote desktop view.
Clarification that MCSO is not requiring remote
desktop view.
MCSO & Motorola teams agree requirement is
met out of the box per notes in Column O.
2163
Cannot Meet
Motorola
CSF002
Supervisor
Functionality
General
The system should provide the capability for
authorized ECC supervisors to remotely take
control of any ECC CAD terminal.
Mandatory
CAD
X
An authorized Supervisor can take over the call from any position, but cannot take over the
terminal from a remote position.
A supervisor can takeover an event, but not the
terminal.
MCSO & Motorola teams agree requirement is
met out of the box per notes in Column O.
2164
Cannot Meet
Motorola
Supervisor
Functionality
General
DUTY OFFICER SUMMARY
2165
0
Motorola
CSF003
Supervisor
Functionality
General
Upon command the system should generate a
snapshot of current activity. The snapshot
should include:
Mandatory
CAD
X
Motorola has a snapshot report that shows the current state of incidents and units at a given date
and time for the entire system. It is not broken out by workstation. A report could be written to
break the information out by workstation.
2166
Out of the Box
Motorola
CSF003-1
Supervisor
Functionality
General
The amount of units logged on by agency
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2167
Out of the Box
Motorola
CSF003-2
Supervisor
Functionality
General
The amount of supervisors logged on by agency Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2168
Out of the Box
Motorola
CSF003-3
Supervisor
Functionality
General
The amount of available units
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2169
Out of the Box
Motorola
CSF003-4
Supervisor
Functionality
General
The amount of unavailable units
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2170
Out of the Box
Motorola
CSF004
Supervisor
Functionality
General
All fields should be sortable based on various
criteria to include group.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2171
Out of the Box
Motorola
CSF005
Supervisor
Functionality
General
Multiple search criteria should be able to be
entered at once. Two different groups for
example.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2172
Out of the Box
Motorola
CSF006
Supervisor
Functionality
General
Forced in locations:
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2173
Out of the Box
Page 92of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CSF006-1
Supervisor
Functionality
User Interface
The user should have the ability to search for
locations that were forced into the system.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2174
Out of the Box
Motorola
CSF006-2
Supervisor
Functionality
User Interface
The user should be able to search by street
name
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2175
Out of the Box
Motorola
CSF006-3
Supervisor
Functionality
User Interface
The user should be able to search by employee
ID
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2176
Out of the Box
Motorola
CSF006-4
Supervisor
Functionality
User Interface
The user should be able to search by position
ID
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2177
Out of the Box
Motorola
CSF006-5
Supervisor
Functionality
User Interface
The user should be able to search by agency
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2178
Out of the Box
Motorola
CSF006-6
Supervisor
Functionality
User Interface
The user should be able to search by group
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2179
Out of the Box
Motorola
CSF006-7
Supervisor
Functionality
User Interface
The user should be able to search by date/time Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2180
Out of the Box
Motorola
CSF006-8
Supervisor
Functionality
User Interface
The user should be able to search by remarks
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2181
Out of the Box
Motorola
CSF006-9
Supervisor
Functionality
General
The user should be able to search any of the
above using a wild card
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2182
Out of the Box
Motorola
Supervisor
Functionality
General
MESSAGE REVIEW
2183
0
Motorola
CSF010
Supervisor
Functionality
General
The user should have the ability to search for
messages sent to or from workstations or from
MDCs
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2184
Out of the Box
Motorola
CSF011
Supervisor
Functionality
General
The user should be able to search by employee
ID
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2185
Out of the Box
Motorola
CSF012
Supervisor
Functionality
General
The user should be able to search by position ID Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2186
Out of the Box
Motorola
CSF013
Supervisor
Functionality
General
The user should be able to search on text
contained in the message (to include partial
text searches)
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2187
Out of the Box
Motorola
CSF014
Supervisor
Functionality
General
The user should be able to search by date/time Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2188
Out of the Box
Motorola
CSF015
Supervisor
Functionality
General
The user may search by type of message (ACJIS,
remote, urgent, routine)
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2189
Out of the Box
Motorola
CSF016
Supervisor
Functionality
General
The searches should be able to be done with
partial data.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2190
Out of the Box
Motorola
CSF017
Supervisor
Functionality
General
Multiple fields should be searchable at one
time.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2191
Out of the Box
Motorola
CSF018
Supervisor
Functionality
General
Once retrieved the message should appear
exactly as it was originally sent
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2192
Out of the Box
Motorola
Supervisor
Functionality
General
MESSAGE INFORMATION
2193
0
Motorola
CSF019
Supervisor
Functionality
General
The user should be able query on the amount
of unread messages in a specific workstation or
MDC
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2194
Out of the Box
Motorola
CSF020
Supervisor
Functionality
General
The return should show the total number of
messages in the Queue
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2195
Out of the Box
Motorola
Supervisor
Functionality
General
MESSAGE REMOVAL
2196
0
Motorola
CSF021
Supervisor
Functionality
General
The user should be able to delete all unread
messages in the workstation or MDC queue
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2197
Out of the Box
Motorola
CSF022
Supervisor
Functionality
General
The user should be able to delete unread
messages in remote workstations
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2198
Out of the Box
Motorola
CSF023
Supervisor
Functionality
General
The system should return a message count of
how many messages were in the queue
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2199
Out of the Box
Motorola
Supervisor
Functionality
General
UNIT CREATION
2200
0
Motorola
CSF024
Supervisor
Functionality
General
The System Administrator should have the
ability to create units on the fly as needed.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2201
Out of the Box
Motorola
Supervisor
Functionality
General
SYSTEM HISTORY
2202
0
Motorola
CSF025
Supervisor
Functionality
General
The user should be able to query the system to
receive a log of activity from a specific terminal
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2203
Out of the Box
Motorola
CSF026
Supervisor
Functionality
User Interface
The user should be able to search by time/date Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2204
Out of the Box
Motorola
CSF027
Supervisor
Functionality
User Interface
The user should be able to search by
workstation ID
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2205
Out of the Box
Motorola
CSF028
Supervisor
Functionality
User Interface
The user should be able to search by employee
ID
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2206
Out of the Box
Motorola
CSF029
Supervisor
Functionality
User Interface
The user should be able to search by function
or activity
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2207
Out of the Box
Motorola
CSF030
Supervisor
Functionality
User Interface
The user should be able to search by partial
data
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2208
Out of the Box
Motorola
CSF031
Supervisor
Functionality
User Interface
The system should return a display of the
actions taken, the times they were attempted,
what workstation ID attempted the action,
what employee ID attempted the action and a
line if text showing what was attempted
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2209
Out of the Box
Motorola
Supervisor
Functionality
General
DAILY ACTIVITY REPORT
2210
0
Motorola
CSF032
Supervisor
Functionality
User Interface
The user should be able to create summary
reports on notable public safety activities in
MCSO
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2211
Out of the Box
Page 93of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CSF033
Supervisor
Functionality
User Interface
The system should generate a unique name for
each report
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2212
Out of the Box
Motorola
CSF034
Supervisor
Functionality
User Interface
There should be no limit on the amount of
alphanumeric and special characters used in the
narrative section.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2213
Out of the Box
Motorola
CSF035
Supervisor
Functionality
User Interface
The system should retain the form in which the
narrative was written, to include punctuation,
spacing etc.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2214
Out of the Box
Motorola
CSF036
Supervisor
Functionality
User Interface
The system should store these reports for a
period of time defined by the System
Administrator
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2215
Out of the Box
Motorola
CSF037
Supervisor
Functionality
General
The user should be able to send the reports to
designated workstations or MDCs (to include
printers) either individually or as a group.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2216
Out of the Box
Motorola
CSF038
Supervisor
Functionality
Reporting
The reports should have a formatted header
which should include items such as date/time,
event type, event number, response area,
officer handling the report, author of the
report, designator of the unit handling the
report, event location.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2217
Out of the Box
Motorola
CSF039
Supervisor
Functionality
General
The user should be able to search for the report
by date/time.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2218
Out of the Box
Motorola
CSF040
Supervisor
Functionality
General
The user should be able to search for the report
by its report number.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2219
Out of the Box
Motorola
CSF041
Supervisor
Functionality
General
The user should be able to search by location.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2220
Out of the Box
Motorola
CSF042
Supervisor
Functionality
General
The user should be able to search by the
handling officer or designator.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2221
Out of the Box
Motorola
CSF043
Supervisor
Functionality
General
All searches should be able to use a wild card.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2222
Out of the Box
Motorola
CSF044
Supervisor
Functionality
General
The system should be capable of displaying the
numbers of logged on units verses the number
of available units, by unit type and capability
with exact numbers and percentage formatting.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2223
Out of the Box
Motorola
CHHD001
Hand-Held
Devices
General
The vendor should identify the hand-held
devices they currently offer, support, and/or
interface with.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement. PremierOne
supports the use of both Android and iOS handheld devices for PremierOne Mobile. Current
operating system versions supported: Android versions 10 - 12, iOS versions 14 - 16.
2224
Out of the Box
Motorola
CHHD002
Hand-Held
Devices
General
Vendors should identify MDC functionality that
is supported on their hand-held system.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement. PremierOne Mobile
for Android and iOS supports most of the functionality of our Windows product. Current
functionality includes cloud enabled, silent dispatch, incident & unit management, real-time status
monitors, field initiation for traffic stops and other incidents, database querying, unit location
tracking, premise and hazard details with images, geofencing with entry and exit alerts 4G and LTE
network capability, CJIS security support with FIPS 140-2 encryption and auditing, barcode scan,
voice entry for comments, actionable url in comments. Messaging and BOLOs are currently in
process for release to the Android and iOS platforms.
2225
Out of the Box
Motorola
Hand-Held
Devices
General
LINE-UP
2226
0
Motorola
CHHD003
Hand-Held
Devices
User Interface
The system should provide the ability to
establish a roster of all employees with the
following minimum agency-definable
information:
Mandatory
Mobile
X
PremierOne complies with this requirement of creating rosters through the Dispatcher
workstation. These features are NOT available on our hand-held devices.
2227
Out of the Box
Motorola
CHHD003-1
Hand-Held
Devices
User Interface
ID number
Mandatory
Mobile
X
PremierOne complies with this requirement of creating rosters through the Dispatcher
workstation. These features are NOT available on our hand-held devices.
2228
Out of the Box
Motorola
CHHD003-2
Hand-Held
Devices
User Interface
Rank
Mandatory
Mobile
X
PremierOne complies with this requirement of creating rosters through the Dispatcher
workstation. These features are NOT available on our hand-held devices.
2229
Out of the Box
Motorola
CHHD003-3
Hand-Held
Devices
User Interface
Station assignment
Mandatory
Mobile
X
PremierOne complies with this requirement of creating rosters through the Dispatcher
workstation. These features are NOT available on our hand-held devices.
2230
Out of the Box
Motorola
CHHD003-4
Hand-Held
Devices
User Interface
Patrol Area
Mandatory
Mobile
X
PremierOne complies with this requirement of creating rosters through the Dispatcher
workstation. These features are NOT available on our hand-held devices.
2231
Out of the Box
Motorola
CHHD003-5
Hand-Held
Devices
User Interface
Shift
Mandatory
Mobile
X
PremierOne complies with this requirement of creating rosters through the Dispatcher
workstation. These features are NOT available on our hand-held devices.
2232
Out of the Box
Motorola
CHHD003-6
Hand-Held
Devices
User Interface
District
Mandatory
Mobile
X
PremierOne complies with this requirement of creating rosters through the Dispatcher
workstation. These features are NOT available on our hand-held devices.
2233
Out of the Box
Motorola
CHHD003-7
Hand-Held
Devices
User Interface
Default unit assignment
Mandatory
Mobile
X
PremierOne complies with this requirement of creating rosters through the Dispatcher
workstation. These features are NOT available on our hand-held devices.
2234
Out of the Box
Motorola
CHHD003-8
Hand-Held
Devices
User Interface
Skills (e.g. foreign language, rifle)
Mandatory
Mobile
X
PremierOne complies with this requirement of creating rosters through the Dispatcher
workstation. These features are NOT available on our hand-held devices.
2235
Out of the Box
Motorola
CHHD003-9
Hand-Held
Devices
User Interface
Assigned portable radio number
Mandatory
Mobile
X
PremierOne complies with this requirement of creating rosters through the Dispatcher
workstation. These features are NOT available on our hand-held devices.
2236
Out of the Box
Motorola
CHHD003-10
Hand-Held
Devices
User Interface
Duty Status (limited duty)
Preferred
Mobile
X
PremierOne complies with this requirement of creating rosters through the Dispatcher
workstation. These features are NOT available on our hand-held devices.
2237
Out of the Box
Motorola
CHHD004
Hand-Held
Devices
User Interface
Special skills, and other personnel information
maintained in the RMS Personnel Module
should be capable of being transferred to the
Line-Up.
Mandatory
Mobile
X
PremierOne complies with this requirement of creating rosters through the Dispatcher
workstation. These features are NOT available on our hand-held devices.
2238
Out of the Box
Page 94of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CHHD005
Hand-Held
Devices
General
The system should have the ability to prepare a
daily line up (personnel roster) that is
populated automatically by the RMS-Personnel
Module. For example, all personnel identified
as being assigned to Patrol North station, day
work A-squad, would be populated onto the
line up record for a scheduled work day. In this
case, default patrol area assignments would be
based upon assigned Patrol Beat of record, and
adjustable by the preparing supervisor altering
the line up. Special duty status (Annual Leave,
Light Duty, Desk, etc.), or daily assignments
(e.g., Court, etc.) would be indicated on the
Line Up.
Mandatory
Mobile
X
Due to an addendum dated 8-28, this information would not come from an RMS Personnel
Module. For PremierOne this information would be stored in CAD.
2239
Out of the Box
Motorola
CHHD006
Hand-Held
Devices
General
The system should provide the ability:
Mobile
X
PremierOne complies with the functionality as described in the requirement.
2240
Out of the Box
Motorola
CHHD006-1
Hand-Held
Devices
General
To auto-populate data from the CAD or RMS
personnel module or elsewhere into the line-up
file.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
2241
Out of the Box
Motorola
CHHD006-2
Hand-Held
Devices
General
Permit the System Administrator to define the
duty hours for each shift and to manually set
the duty hours for a specific line-up if
necessary. This might be necessary when
additional units are staffed for a special event.
Preferred
Mobile
X
PremierOne complies with the functionality as described in the requirement.
2242
Out of the Box
Motorola
CHHD006-3
Hand-Held
Devices
General
Allow supervisors to assign a user-defined
number of officers to a single unit.
Optional
Mobile
X
PremierOne complies with the functionality as described in the requirement.
2243
Out of the Box
Motorola
CHHD006-4
Hand-Held
Devices
General
For supervisors to create shift line-ups from
the roster.
Preferred
Mobile
X
PremierOne complies with the functionality as described in the requirement.
2244
Out of the Box
Motorola
CHHD006-5
Hand-Held
Devices
General
For supervisors to define the Division, District,
Patrol Beat, shift and date for which they are
creating the lineup.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
2245
Out of the Box
Motorola
CHHD006-6
Hand-Held
Devices
General
For supervisors to search for and retrieve a
previously completed line-up, modify any
information and save it as a new line-up.
Preferred
Mobile
X
PremierOne complies with the functionality as described in the requirement.
2246
Out of the Box
Motorola
CHHD006-7
Hand-Held
Devices
General
To retrieve the line-up for a given date, time
and shift.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
2247
Out of the Box
Motorola
CHHD006-8
Hand-Held
Devices
General
For Squad line-ups to be prepared in advance,
based on date, and printed in advance as
necessary.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
2248
Out of the Box
Motorola
CHHD007
Hand-Held
Devices
General
The system should provide the capability for
the Patrol Official in-charge (roll call or other
official) to enter the roll call information, the
status (on-duty, vacation, sick, court-duty, etc.)
for each employee assigned to that shift, and
the unit assignment for each.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
2249
Out of the Box
Motorola
CHHD008
Hand-Held
Devices
General
The system should provide the ability to enter
the following information for each on-duty
officer:
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
2250
Out of the Box
Motorola
CHHD008-1
Hand-Held
Devices
General
Assigned unit (call sign)
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
2251
Out of the Box
Motorola
CHHD008-2
Hand-Held
Devices
General
Vehicle number
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
2252
Out of the Box
Motorola
CHHD008-3
Hand-Held
Devices
General
Vehicle radio number
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
2253
Out of the Box
Motorola
CHHD008-4
Hand-Held
Devices
General
Portable radio number
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
2254
Out of the Box
Motorola
CHHD008-5
Hand-Held
Devices
General
Vehicle equipment
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
2255
Out of the Box
Motorola
CHHD008-6
Hand-Held
Devices
General
Duty times
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
2256
Out of the Box
Motorola
CHHD008-7
Hand-Held
Devices
General
Special Skills
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement.
2257
Out of the Box
Motorola
CHHD008-8
Hand-Held
Devices
General
Special Daily Assignments (Court, Training, etc.) Preferred
Mobile
X
PremierOne complies with the functionality as described in the requirement.
2258
Out of the Box
Motorola
CHHD009
Hand-Held
Devices
General
The daily assignments information above needs
to be easily accessible to Communications to
avoid officer schedule/dispatch conflicts.
Communications should also be able to enter
special assignment data for the current shifts.
Mandatory
Mobile
X
PremierOne complies with the functionality utilizing Unit Status monitors.
2259
Out of the Box
Motorola
CHHD010
Hand-Held
Devices
General
The system should have the ability to enter a
command or action which will place a specified
line-up on duty.
Mandatory
Mobile
X
PremierOne complies with this requirement through the Dispatcher workstation. These features
are NOT available on our hand-held devices.
2260
Out of the Box
Motorola
CHHD011
Hand-Held
Devices
General
The daily line-up function should operate in
such a way that Communication (Dispatch)
does not have to individually enter any unit
data as new shifts go on duty. An officer going
"in service" should validate to the current line-
up, and automatically populate the active units
list for communications.
Mandatory
Mobile
X
PremierOne does not have this functionality.
MCSO team stated this is not required to be met.
2261
Cannot Meet
Page 95of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CHHD012
Hand-Held
Devices
General
Units initially signing on should first validate to
the duty roster (line up) to avoid them
messaging Communications before they are
aware of their presence.
Mandatory
Mobile
X
PremierOne does not have this functionality.
MCSO team stated this is not required to be met.
2262
Cannot Meet
Motorola
CHHD013
Hand-Held
Devices
General
Ability to enter a command or action which will
place a specified unit or units in the line-up on
duty.
Mandatory
Mobile
X
PremierOne complies with this requirement through the Dispatcher workstation. This feature is
NOT available on our hand-held devices. From the hand-held device, a deputy can only place
themselves on-duty.
2263
Out of the Box
Motorola
CHHD014
Hand-Held
Devices
General
The system should allow the user to create a
statistical management report, including
staffing levels, illustrating for the entire
department, or, any subset (Division, District,
Patrol Beat, etc.) and all deputies and officials
by:
Mandatory
Mobile
X
PremierOne CAD utilizes Microsoft SQL Server Reporting Services (SSRS) for its standard reports.
SSRS is a server-based reporting platform that is used to create and manage tabular, matrix,
graphical, dashboards, and free form reports that contain data from relational and
multidimensional data sources. A sample of the standard reports include Average Response
Times by Incident Type, BOLO Messages, Various Calls For Service reports, various Incident
reports (grouped by type, by area, etc), Login and Logoff, various Provisioning reports, Purge
schedule, various Query reports, and Officer Activity. Additional reports an be created by
authorized users. This functionality is NOT available on hand-held devices.
2264
Out of the Box
Motorola
CHHD014-1
Hand-Held
Devices
User Interface
Patrol District
Mandatory
Mobile
X
PremierOne complies with this requirement if the users while using SSRS. As part of deployment,
Motorola will apply canned reports to the system and lead a reporting writing workshop with
County personnel. The Motorola system is capable of creating and printing reports with
information available in the database via SSRS reports authored by the County. These features are
NOT available on our hand-held devices.
2265
With Configuration
Motorola
CHHD014-2
Hand-Held
Devices
User Interface
Patrol Area
Mandatory
Mobile
X
PremierOne complies with this requirement if the users while using SSRS. As part of deployment,
Motorola will apply canned reports to the system and lead a reporting writing workshop with
County personnel. The Motorola system is capable of creating and printing reports with
information available in the database via SSRS reports authored by the County. These features are
NOT available on our hand-held devices.
2266
With Configuration
Motorola
CHHD014-3
Hand-Held
Devices
User Interface
Specialized Unit
Mandatory
Mobile
X
PremierOne complies with this requirement if the users while using SSRS. As part of deployment,
Motorola will apply canned reports to the system and lead a reporting writing workshop with
County personnel. The Motorola system is capable of creating and printing reports with
information available in the database via SSRS reports authored by the County. These features are
NOT available on our hand-held devices.
2267
With Configuration
Motorola
CHHD015
Hand-Held
Devices
User Interface
Which includes a summary of any user defined
parameters such as;
Mandatory
Mobile
X
PremierOne complies with this requirement if the users while using SSRS. As part of deployment,
Motorola will apply canned reports to the system and lead a reporting writing workshop with
County personnel. The Motorola system is capable of creating and printing reports with
information available in the database via SSRS reports authored by the County. These features are
NOT available on our hand-held devices.
2268
With Configuration
Motorola
CHHD015-1
Hand-Held
Devices
User Interface
Sex
Preferred
Mobile
X
PremierOne complies with this requirement if the users while using SSRS. As part of deployment,
Motorola will apply canned reports to the system and lead a reporting writing workshop with
County personnel. The Motorola system is capable of creating and printing reports with
information available in the database via SSRS reports authored by the County. These features are
NOT available on our hand-held devices.
2269
With Configuration
Motorola
CHHD015-2
Hand-Held
Devices
User Interface
Foreign languages spoken
Preferred
Mobile
X
PremierOne complies with this requirement if the users while using SSRS. As part of deployment,
Motorola will apply canned reports to the system and lead a reporting writing workshop with
County personnel. The Motorola system is capable of creating and printing reports with
information available in the database via SSRS reports authored by the County. These features are
NOT available on our hand-held devices.
2270
With Configuration
Motorola
CHHD015-3
Hand-Held
Devices
User Interface
Special training or skill set (Rifle trained, etc.)
Preferred
Mobile
X
PremierOne complies with this requirement if the users while using SSRS. As part of deployment,
Motorola will apply canned reports to the system and lead a reporting writing workshop with
County personnel. The Motorola system is capable of creating and printing reports with
information available in the database via SSRS reports authored by the County. These features are
NOT available on our hand-held devices.
2271
With Configuration
Motorola
CHHD016
Hand-Held
Devices
User Interface
Which can be sorted by:
Mobile
X
PremierOne complies with this requirement if the users while using SSRS. As part of deployment,
Motorola will apply canned reports to the system and lead a reporting writing workshop with
County personnel. The Motorola system is capable of creating and printing reports with
information available in the database via SSRS reports authored by the County. These features are
NOT available on our hand-held devices.
2272
With Configuration
Motorola
CHHD016-1
Hand-Held
Devices
User Interface
On-duty officers
Mandatory
Mobile
X
PremierOne complies with this requirement if the users while using SSRS. As part of deployment,
Motorola will apply canned reports to the system and lead a reporting writing workshop with
County personnel. The Motorola system is capable of creating and printing reports with
information available in the database via SSRS reports authored by the County. These features are
NOT available on our hand-held devices.
2273
With Configuration
Motorola
CHHD016-2
Hand-Held
Devices
User Interface
Off-duty officers
Mandatory
Mobile
X
PremierOne complies with this requirement if the users while using SSRS. As part of deployment,
Motorola will apply canned reports to the system and lead a reporting writing workshop with
County personnel. The Motorola system is capable of creating and printing reports with
information available in the database via SSRS reports authored by the County. These features are
NOT available on our hand-held devices.
2274
With Configuration
Motorola
CHHD016-3
Hand-Held
Devices
User Interface
Limited-Duty officers
Mandatory
Mobile
X
PremierOne complies with this requirement if the users while using SSRS. As part of deployment,
Motorola will apply canned reports to the system and lead a reporting writing workshop with
County personnel. The Motorola system is capable of creating and printing reports with
information available in the database via SSRS reports authored by the County. These features are
NOT available on our hand-held devices.
2275
With Configuration
Motorola
CHHD016-4
Hand-Held
Devices
User Interface
Officers on Sick Leave
Mandatory
Mobile
X
PremierOne complies with this requirement if the users while using SSRS. As part of deployment,
Motorola will apply canned reports to the system and lead a reporting writing workshop with
County personnel. The Motorola system is capable of creating and printing reports with
information available in the database via SSRS reports authored by the County. These features are
NOT available on our hand-held devices.
2276
With Configuration
Motorola
CHHD016-5
Hand-Held
Devices
User Interface
By rank
Mandatory
Mobile
X
PremierOne complies with this requirement if the users while using SSRS. As part of deployment,
Motorola will apply canned reports to the system and lead a reporting writing workshop with
County personnel. The Motorola system is capable of creating and printing reports with
information available in the database via SSRS reports authored by the County. These features are
NOT available on our hand-held devices.
2277
With Configuration
Motorola
CHHD016-6
Hand-Held
Devices
User Interface
And all of the aforementioned parameters.
Mandatory
Mobile
X
PremierOne complies with this requirement if the users while using SSRS. As part of deployment,
Motorola will apply canned reports to the system and lead a reporting writing workshop with
County personnel. The Motorola system is capable of creating and printing reports with
information available in the database via SSRS reports authored by the County. These features are
NOT available on our hand-held devices.
2278
With Configuration
Page 96of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CHHD017
Hand-Held
Devices
User Interface
The system should permit the line-up to be
printed.
Mandatory
Mobile
X
PremierOne complies with this requirement if the users while using SSRS. As part of deployment,
Motorola will apply canned reports to the system and lead a reporting writing workshop with
County personnel. The Motorola system is capable of creating and printing reports with
information available in the database via SSRS reports authored by the County. These features are
NOT available on our hand-held devices.
2279
With Configuration
Motorola
Hand-Held
Devices
General
OFF-DUTY WORK ROSTER
2280
0
Motorola
CHHD018
Hand-Held
Devices
General
The system should provide the capability to
maintain a roster of Officers working off duty
assignments.
Mandatory
Mobile
X
PremierOne complies with the functionality utilizing Unit Status monitors.
2281
Out of the Box
Motorola
CHHD019
Hand-Held
Devices
General
Rosters should be updated by Officers and/or
by Communications and should contain:
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2282
Out of the Box
Motorola
CHHD020
Hand-Held
Devices
General
Unit #, Officer #, Business/Location Name ,
Location (validated, can be an intersection),
Starting Date (MMDDYYYY), Starting Time
HH:MM (Military), Ending Date (MMDDYYYY),
Ending Time (MMDDYYYY).
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2283
Out of the Box
Motorola
CHHD021
Hand-Held
Devices
General
When an event occurs at a location where an
off duty officer is currently working the Call
taker/Dispatcher needs to be informed.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2284
Out of the Box
Motorola
CHHD022
Hand-Held
Devices
General
When an event occurs within an established
distance of the current off duty work location
the Call taker/Dispatcher needs to be informed.
Mandatory
Mobile
X
PremierOne complies with the functionality utilizing geofencing.
2285
Out of the Box
Motorola
CHHD023
Hand-Held
Devices
General
Note: If the same functionality can be obtained
by using an alternative approach, please
describe your solution.
Mandatory
Mobile
X
Motorla complies with the requirements as stated in CHHD018 through CFFD022 and does not
require an alternative approach.
2286
Out of the Box
Motorola
Hand-Held
Devices
General
ACJIS/NCIC FUNCTIONS
2287
0
Motorola
CHHD024
Hand-Held
Devices
General
Where transactions below are in a combined
statement, MCSO requires the flexibility to
complete any element of the transaction
separately, i.e. allow officers to enter stolen
vehicles, boats, bicycles, etc.
Preferred
Mobile
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2288
Out of the Box
Motorola
CHHD025
Hand-Held
Devices
General
MCSO needs the capability of sending and
receiving the full complement of ACJIS/NCIC
transactions. Some teletype transactions are
free form narrative requests while most are
mask formatted messages requesting
information or some action on their part.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2289
Out of the Box
Motorola
CHHD026
Hand-Held
Devices
General
With respect to the free form teletype
transactions:
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2290
Out of the Box
Motorola
CHHD027
Hand-Held
Devices
General
The system should have the ability to pull pre
formatted forms created by MCSO and stored
for retrieval and usage. The forms should
contain the following sections:
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2291
Out of the Box
Motorola
CHHD028
Hand-Held
Devices
General
An authorization section stating that the
request being made is authorized by the
Maricopa County Sheriff.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2292
Out of the Box
Motorola
CHHD029
Hand-Held
Devices
General
MCSO's assigned ORI # and a section identifying
the initiating operator's Operator ID, Employee
Number and Terminal Operator Certification.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2293
Out of the Box
Motorola
CHHD030
Hand-Held
Devices
General
The system should provide the ability to issue
sequential teletype numbers for tracking
purposes. The teletype form should be able to
handle not only single entries but multiple
entries on single form.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2294
Out of the Box
Motorola
CHHD031
Hand-Held
Devices
General
The system should provide a database to store
summaries of entries into the ACJIS and NCIC
system. The teletype mask is used for this
entry, retrieval, modification and deletion. The
teletype form should be completely searchable
(every field).
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2295
Out of the Box
Motorola
CHHD032
Hand-Held
Devices
General
In cases where multiple messages are related
to an original message, these follow-up
messages should be associated with the original
Teletype number.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2296
Out of the Box
Motorola
CHHD033
Hand-Held
Devices
General
The system should minimally provide the below
listed agency-definable forms/masks and
functionality:
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2297
Out of the Box
Motorola
CHHD034
Hand-Held
Devices
General
A consolidated form to run ACJIS/NCIC and local
checks on items such as: Securities, Boats,
Articles, ORI and guns.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2298
Out of the Box
Motorola
CHHD035
Hand-Held
Devices
General
A consolidated form to run ACJIS/NCIC and local
checks on items such as: Wanted persons,
Missing persons, Driver listings, All vehicles
listed to an owner, lookouts. The user should
have the ability to run a driver listing on a
person in Arizona or anywhere outside Arizona.
The user should be able to run a driver
transcript.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2299
Out of the Box
Page 97of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CHHD036
Hand-Held
Devices
General
The system should provide the ability to create
and manage agency-definable teletype forms,
including but not limited to:
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2300
Out of the Box
Motorola
CHHD036-1
Hand-Held
Devices
General
A form used to enter a stored vehicle into the
ACJIS system. Includes the ability to modify and
cancel a stored vehicle entry.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2301
Out of the Box
Motorola
CHHD036-2
Hand-Held
Devices
General
A form to send an administrative message
through ACJIS [ALETS-NLETS] /NCIC. This is a
preformatted form to identify destinations.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2302
Out of the Box
Motorola
CHHD036-3
Hand-Held
Devices
User Interface
A form used to enter, modify, locate, cancel or
clear an article(s) entered into the ACJIS and/or
NCIC system.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2303
Out of the Box
Motorola
CHHD036-4
Hand-Held
Devices
User Interface
A form used to enter, modify, locate, cancel or
clear a boat entered into the MCSO, ACJIS
and/or NCIC system.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2304
Out of the Box
Motorola
CHHD036-5
Hand-Held
Devices
User Interface
A form used to enter, modify, locate, cancel or
clear a stolen, lost, and/or recovered gun from
the ACJIS and/or NCIC system.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2305
Out of the Box
Motorola
CHHD036-6
Hand-Held
Devices
User Interface
A form used to enter, modify, locate, cancel or
clear a stolen license plate entry from ACJIS
and/or NCIC.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2306
Out of the Box
Motorola
CHHD036-7
Hand-Held
Devices
User Interface
A form used to enter, modify, locate, cancel or
clear a missing person entry from ACJIS and/or
NCIC.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2307
Out of the Box
Motorola
CHHD036-8
Hand-Held
Devices
User Interface
A form used to enter, modify, locate, cancel,
clear, enter supplemental dental, modify
dental, cancel dental, supplemental entry, and
supplemental cancel for an unidentified person
entry from ACJIS and/or NCIC.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2308
Out of the Box
Motorola
CHHD036-9
Hand-Held
Devices
User Interface
A form used to enter, modify, locate, cancel or
clear a stolen security entry in NCIC.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2309
Out of the Box
Motorola
CHHD036-10
Hand-Held
Devices
User Interface
A form used to enter, modify, locate, cancel or
clear a stolen vehicle entry in ACJIS and/or
NCIC.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2310
Out of the Box
Motorola
CHHD036-11
Hand-Held
Devices
User Interface
A form used to enter, locate, quash, cancel,
clear and/or enter supplemental information
for a wanted person entry from and/or ACJIS
and/or NCIC.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2311
Out of the Box
Motorola
CHHD036-12
Hand-Held
Devices
User Interface
A form used to enter or modify stolen article in
the NCIC system. The system should allow for
groups of articles to be entered on one form.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2312
Out of the Box
Motorola
CHHD036-13
Hand-Held
Devices
User Interface
A consolidated form to run ACJIS/NCIC and local
checks on items such as: VIN numbers, License
plates, Stored vehicles, lookouts.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2313
Out of the Box
Motorola
CHHD036-14
Hand-Held
Devices
User Interface
A form used to enter or modify a stolen vehicle
into the ACJIS and/or NCIC system. The form
should also allow for the entry and the
modification of vehicle parts in NCIC.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2314
Out of the Box
Motorola
CHHD036-15
Hand-Held
Devices
General
A form used to send a confirmation request to
a location inside or outside the state of Arizona
through ACJIS system. The form should contain
all the appropriate fields to confirm: wanted
people, missing persons, stolen vehicles, stolen
license plates, stolen articles, stolen guns,
stolen boats, and stolen securities.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2315
Out of the Box
Motorola
CHHD036-16
Hand-Held
Devices
General
A form to run criminal histories through ACJIS
and NCIC. Access to both NCIC/ACJIS files
should available through this form.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2316
Out of the Box
Motorola
CHHD037
Hand-Held
Devices
General
The system should have the ability to access
LOJACK and other vehicle locating services
through NLETS through a query and check
transactions.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2317
Out of the Box
Motorola
CHHD038
Hand-Held
Devices
General
All forms to be NCIC 2000 compliant and meet
all ACJIS standards as set in the current manual.
ALL required codes to be compliant with the
NCIC 2000 code manual and the current ACJIS
code manual.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2318
Out of the Box
Motorola
CHHD039
Hand-Held
Devices
General
All messages received and displayed from
ACJIS/NCIC should contain all the original data
in the same format in which it was sent by
ACJIS/NCIC
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2319
Out of the Box
Motorola
CHHD040
Hand-Held
Devices
General
The proposed CAD application should be
interfaced with the RMS to access and update
warrant files.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2320
Out of the Box
Page 98of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CHHD041
Hand-Held
Devices
General
All ACJIS/NCIC forms should be System
Administrator configurable. These forms
periodically change due to ACJIS and or NCIC
rule changes we should be able to change the
forms easily when necessary.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2321
Out of the Box
Motorola
CHHD042
Hand-Held
Devices
General
The system should have the ability to dump
information from forms prepared on a field
based report application directly to ACJIS/NCIC
forms. For example when a stolen vehicle
report is entered on an MDC the related data
necessary for ACJIS/NCIC entry should go
directly to Teletype so the data can be entered
into the ACJIS system without having to re-type
the data.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2322
Out of the Box
Motorola
CHHD043
Hand-Held
Devices
General
When a ACJIS/NCIC entry is made a supplement
to the original case report in the RMS system
should be made when the case report is
entered into RMS.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2323
Out of the Box
Motorola
CHHD044
Hand-Held
Devices
General
The teletype section should have access to the
RMS to validate ACJIS/NCIC records both for
legitimacy and accuracy.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2324
Out of the Box
Motorola
CHHD045
Hand-Held
Devices
General
When an ACJIS/NCIC entry fails to match up
with a case report in RMS (after a designated
period of time) an administrator should be
notified
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2325
Out of the Box
Motorola
CHHD046
Hand-Held
Devices
General
The teletype section should have access to the
RMS system to verify the ACJIS/NCIC record is
still valid. The user should also have access to
certain data in the RMS record such as
complainants name and phone numbers
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2326
Out of the Box
Motorola
CHHD047
Hand-Held
Devices
General
Clears or locates entered into ACJIS or NCIC
should trigger notifications to the handling
officer or detective of the related case (when
applicable).
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2327
Out of the Box
Motorola
CHHD048
Hand-Held
Devices
General
The system should have the ability to dump
data from an ACJIS/NCIC response directly into
a different teletype form without having to
retype the data. For example, from CAD
dispatchers should be able to query a tag
number and utilize the return information to
auto-populate a CJIS stolen vehicle entry form.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2328
Out of the Box
Motorola
Hand-Held
Devices
General
SUPPLEMENTAL PERSON/VEHICLE
2329
0
Motorola
CHHD049
Hand-Held
Devices
General
Users should have the ability to utilize agency-
defined CAD masks to append person, vehicle,
location, caller, article, gun, information and
comments into a CAD event history.
Mandatory
Mobile
x
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2330
Out of the Box
Motorola
CHHD050
Hand-Held
Devices
General
Users should have the ability to import
information received as the result of inquiries
into this mask.
Mandatory
Mobile
x
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2331
Out of the Box
Motorola
Hand-Held
Devices
General
TOW FILE
2332
0
Motorola
CHHD051
Hand-Held
Devices
User Interface
The system should support the ability to enter
and track all information on every privately
towed vehicle where the owner is not aware
the car had been towed via a TOW form. The
entries go in to both the CAD stored vehicle file
and stored vehicle file.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2333
Out of the Box
Motorola
CHHD052
Hand-Held
Devices
User Interface
The TOW form should enter data into a CAD
level database.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2334
Out of the Box
Motorola
CHHD053
Hand-Held
Devices
User Interface
All the fields in the Tow Form should conform
to data requirements supporting Arizona
Statues 28-3511, 28-3512, and 28-3514.
Mandatory
Records
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Records.
2335
Out of the Box
Motorola
CHHD054
Hand-Held
Devices
User Interface
The data entered into the TOW file should be
sent to the ACJIS system and stored in the ACIC
stored vehicle file.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2336
Out of the Box
Motorola
CHHD055
Hand-Held
Devices
User Interface
All the fields in the Tow Form should conform
to ACIC/NCIC standards.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2337
Out of the Box
Motorola
CHHD056
Hand-Held
Devices
User Interface
TOW File: One years worth of live TOW data
should be storable on the CAD system for users
to access. The data should be stored or
archived for user access and made easily
available for reporting purposes.
Mandatory
Records
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Records.
2338
Out of the Box
Motorola
CHHD057
Hand-Held
Devices
User Interface
The TOW file should be completely searchable
(including using a single or multiple wildcards in
multiple fields).
Mandatory
Records
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Records.
2339
Out of the Box
Motorola
CHHD058
Hand-Held
Devices
User Interface
The TOW file should minimally include the
following agency-definable fields:
Records
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Records.
2340
Out of the Box
Motorola
CHHD058-1
Hand-Held
Devices
User Interface
A system generated sequential TOW number
Mandatory
Records
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Records.
2341
Out of the Box
Page 99of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CHHD058-2
Hand-Held
Devices
User Interface
LIC - License
Mandatory
Records
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Records.
2342
Out of the Box
Motorola
CHHD058-3
Hand-Held
Devices
User Interface
LIY - License Year
Mandatory
Records
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Records.
2343
Out of the Box
Motorola
CHHD058-4
Hand-Held
Devices
User Interface
LIS - License State
Mandatory
Records
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Records.
2344
Out of the Box
Motorola
CHHD058-5
Hand-Held
Devices
User Interface
LIT - License Type
Mandatory
Records
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Records.
2345
Out of the Box
Motorola
CHHD058-6
Hand-Held
Devices
User Interface
VIN - Vehicle Indentification Number
Mandatory
Records
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Records.
2346
Out of the Box
Motorola
CHHD058-7
Hand-Held
Devices
User Interface
VYR - Vehicle Year
Mandatory
Records
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Records.
2347
Out of the Box
Motorola
CHHD058-8
Hand-Held
Devices
User Interface
VMA - Vehicle Make
Mandatory
Records
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Records.
2348
Out of the Box
Motorola
CHHD058-9
Hand-Held
Devices
User Interface
VMO - Vehicle Model
Mandatory
Records
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Records.
2349
Out of the Box
Motorola
CHHD058-10
Hand-Held
Devices
User Interface
VT - Vehicle Type
Mandatory
Records
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Records.
2350
Out of the Box
Motorola
CHHD058-11
Hand-Held
Devices
User Interface
VST - Vehicle Style
Mandatory
Records
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Records.
2351
Out of the Box
Motorola
CHHD058-12
Hand-Held
Devices
User Interface
VCO - Vehicle Color
Mandatory
Records
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Records.
2352
Out of the Box
Motorola
CHHD058-13
Hand-Held
Devices
User Interface
Location Vehicle Towed from (verified location
field and searchable)
Mandatory
Records
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Records.
2353
Out of the Box
Motorola
CHHD058-14
Hand-Held
Devices
User Interface
Date of the tow
Mandatory
Records
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Records.
2354
Out of the Box
Motorola
CHHD058-15
Hand-Held
Devices
User Interface
Reason the vehicle was towed
Mandatory
Records
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Records.
2355
Out of the Box
Motorola
CHHD058-16
Hand-Held
Devices
User Interface
Tow Code (a single letter)
Mandatory
Records
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Records.
2356
Out of the Box
Motorola
CHHD058-17
Hand-Held
Devices
User Interface
Name of the Tow Company
Mandatory
Records
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Records.
2357
Out of the Box
Motorola
CHHD058-18
Hand-Held
Devices
User Interface
Phone number for the TOW company
Mandatory
Records
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Records.
2358
Out of the Box
Motorola
CHHD058-19
Hand-Held
Devices
User Interface
Owner information fields
Mandatory
Records
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Records.
2359
Out of the Box
Motorola
CHHD058-20
Hand-Held
Devices
User Interface
Driver information if different from owner.
Should include current address and phone
number.
Mandatory
Records
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Records.
2360
Out of the Box
Motorola
CHHD058-21
Hand-Held
Devices
User Interface
Miscellaneous field
Mandatory
Records
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Records.
2361
Out of the Box
Motorola
CHHD059
Hand-Held
Devices
General
The TOW form should also allow queries into
the TOW data base and ACIC/NCIC for vehicle
information and want checks
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2362
Out of the Box
Motorola
CHHD060
Hand-Held
Devices
User Interface
The user should be able to add, modify or
delete TOW entries.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2363
Out of the Box
Motorola
CHHD061
Hand-Held
Devices
User Interface
The user should have the ability to issue a
command or press a function key to bring up
the last query sent to NCIC.
Mandatory
Mobile
X
PremierOne complies with the functionality as described in the requirement with PremierOne
Mobile.
2364
Out of the Box
Motorola
CTOW-001
TOWING
(WRECKERS)
General
The system should provide a tow truck
(wrecker) messaging request functionality. The
purpose of this functionality is to provide an
easy to use form which field users can request
the services of a wrecker to a pre-defined
County dispatch position which handles such
requests.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement. PremierOne’s
Contractor Rotations allows agencies to have an ordered method to use outside resources such as
towing companies. Agencies may have more than one Contractor Rotation type within the same
geographic area. For example, in a given area, an agency may have one Contractor Rotation type
for citizen tow requests and a different Contractor Rotation for towing patrol vehicles. Agencies
may also choose to provision alternate rotations for each area.
A Contractor Request can be made when a user has established a need for an outside resource to
respond to an incident. If a user attempts to make a Contractor Request for an incident that does
not have a validated location, the user has the ability to enter an agency, a rotation type, and a
rotation name.
When the user submits the Contractor Request, PremierOne CAD builds a list of contractor
recommendations based on all search criteria entered but limited to the number of contractors
provisioned to be shown for the rotation type. The list is ordered based on the rotation method.
For example, if the agency is provisioned to rotate the recommendation list after each request,
the last used contractor would now be at the bottom of the list.
There are no limitations to the number of towing companies that can be provisioned or rotated.
2365
Out of the Box
Motorola
CTOW-002
TOWING
(WRECKERS)
General
The system should support the creation of a
form that workstations and MDC's can utilized
to request wreckers with user definable
information fields.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2366
Out of the Box
Motorola
CTOW-003
TOWING
(WRECKERS)
General
If the unit is on an event the location of the
event should be the default location of the
request. The location can be over ridden by the
user.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2367
Out of the Box
Motorola
CTOW-004
TOWING
(WRECKERS)
General
If the unit is on an event the request and the
event should be cross referenced together.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2368
Out of the Box
Motorola
CTOW-005
TOWING
(WRECKERS)
General
When submitted the form should generate a
notification to a defined workstation.
Mandatory
CAD
X
PremierOne does not have this functionality.
MCSO team stated this is not required to be met.
2369
Cannot Meet
Motorola
CTOW-006
TOWING
(WRECKERS)
General
The workstation that receives the request
should have displayed all the information
entered on the wrecker request form and any
related event information
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2370
Out of the Box
Page 100of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CTOW-007
TOWING
(WRECKERS)
General
The system should have the ability to
recommend towing companies with County
contracts and the ability to:
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2371
Out of the Box
Motorola
CTOW-007-1
TOWING
(WRECKERS)
General
Recommend towing or contractor services
based on the location where the tow truck or
contractor is required, the category of towing
or contractor service required (flat bed, heavy
tow, glass replacement, etc.), and the last time
that particular service was used.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2372
Out of the Box
Motorola
CTOW-007-2
TOWING
(WRECKERS)
General
Rotate multiple towing companies or
contractors within a single user-defined
geographic zone.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2373
Out of the Box
Motorola
CTOW-007-3
TOWING
(WRECKERS)
General
Record the time and date of each attempt to
contact a tow company or contractor for an
assignment and add comments.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2374
Out of the Box
Motorola
CTOW-007-4
TOWING
(WRECKERS)
General
Record that a tow company or contractor was
not available for an assignment and add
comments.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2375
Out of the Box
Motorola
CTOW-007-5
TOWING
(WRECKERS)
General
Sequentially display the next tow company or
contractor in run order.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2376
Out of the Box
Motorola
CTOW-008
TOWING
(WRECKERS)
General
Once a tow company or contractor has been
either assigned to an event the assignment
should be documented in the wrecker request
and any related event(s).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2377
Out of the Box
Motorola
TOWING
(WRECKERS)
General
The system shall allow for a tow company to be
placed back in the rotation list in any order by
the dispatcher due to cancellation or other
unforeseen circumstances.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2378
Out of the Box
Motorola
CTOW-009
TOWING
(WRECKERS)
General
The system should include a simple log for
recording the location where vehicles are
towed to.
Preferred
CAD
X
PremierOne complies with the functionality as described in the requirement.
2379
Out of the Box
Motorola
CTOW-010
TOWING
(WRECKERS)
General
Whenever a vehicle plate is searched the query
should search the tow and stored vehicle log
file.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2380
Out of the Box
Motorola
CTOW-011
TOWING
(WRECKERS)
General
The system should maintain a unit history log
for contractors in the same manner as for field
units. From this log it should be possible to
create a step-by-step history of notifications to
contractors and their responsiveness. This log
would be used to determine such things as how
quickly a contractor's units arrived on scene,
how often they were called, how often they
were unavailable, etc.
Mandatory
CAD
X
PremierOne does not have this functionality.
Can see chronology tow history recorded inside the
event. Can also create a report that summarizes
information by tow company.
MCSO & Motorola teams agree requirement is
met out of the box per notes in Column O.
2381
Cannot Meet
Motorola
CTOW-012
TOWING
(WRECKERS)
General
Once the appropriate wrecker company is
notified the user shall close the wrecker
request. Once closed the related events and
unit histories should display the wrecker
information to include what wrecker company
was notified, the user id and time of
notification.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2382
Out of the Box
Motorola
CTOW-013
TOWING
(WRECKERS)
General
Upon closing the wrecker request a notification
should be sent to the originating unit (either an
MDC or workstation). This message should
include the wrecker company notified, the
phone number for the wrecker company, the ID
of the person making the original request,
related event number (if any) and location
wrecker will be sent.
Mandatory
CAD
X
PremierOne does not send a notification, but the information is available immediately on the
MDC.
2383
Out of the Box
Motorola
CTOW-014
TOWING
(WRECKERS)
General
The system should allow agency definable data
elements for all tow related forms such as:
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2384
Out of the Box
Motorola
CTOW-014-1
TOWING
(WRECKERS)
General
Location of the tow
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2385
Out of the Box
Motorola
CTOW-014-2
TOWING
(WRECKERS)
General
Number of tow trucks required
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2386
Out of the Box
Motorola
CTOW-014-3
TOWING
(WRECKERS)
General
Type of tow trucks required
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2387
Out of the Box
Motorola
CTOW-014-4
TOWING
(WRECKERS)
General
Description of the auto to be towed, including
any damage
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2388
Out of the Box
Motorola
CTOW-014-5
TOWING
(WRECKERS)
General
Any contents remaining in the vehicle after it
has been towed
Mandatory
CAD
X
PremierOne does not have this functionality.
MCSO team stated this is not required to be met.
2389
Cannot Meet
Motorola
CTOW-014-6
TOWING
(WRECKERS)
General
Name or unit number of the requesting officer
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2390
Out of the Box
Motorola
CTOW-014-7
TOWING
(WRECKERS)
General
Time of request
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2391
Out of the Box
Motorola
CTOW-014-8
TOWING
(WRECKERS)
General
Time of arrival
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2392
Out of the Box
Motorola
CTOW-014-9
TOWING
(WRECKERS)
General
Comment, etc.
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2393
Out of the Box
Page 101of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CTOW-015
TOWING
(WRECKERS)
General
Users (workstation and MDC) should have the
ability to search on all wrecker requests. This
search should include, time, date, location,
group, designator, license plate, vehicle make,
vehicle model, VIN number and contract tow
company names. Multiple fields should be
searchable at one time, this would also include
searches done with a wild card
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2394
Out of the Box
Motorola
CTOW-016
TOWING
(WRECKERS)
General
At the time the wrecker request form is
completed the system should place any data
filled out in the form into the TOW form (The
TOW form is used to store vehicles that have
been towed when the owners are not aware
that their car has been towed).
Mandatory
CAD
X
PremierOne complies with the functionality as described in the requirement.
2395
Out of the Box
Motorola
CTOW-017
TOWING
(WRECKERS)
General
The text of the message should be agency
configurable, but should include the elapsed
time since the first unit arrived.
Mandatory
CAD
X
PremierOne does not have this functionality.
PremierOne supports timestamps in the incident
history related to all transactions, including towing.
MCSO & Motorola teams agree requirement is
met out of the box per notes in Column O.
2396
Cannot Meet
Motorola
TOWING
(WRECKERS)
General
Compliance With Arizona Statutes 28-3511, 28-
3512 and 28-3514
2397
0
Motorola
CTOW-018
TOWING
(WRECKERS)
General
Statute 28-3511 establishes several conditions
that when one or more are met, direct the
deputy to cause the removal and either
immobilization or impoundment of the
involved vehicle or vehicles. The vehicles are
towed to private impound lots under contract
with County. At the time of impound, MCSO
deputies should collect as much information as
possible on the vehicle, its owners and possible
lien holders. Impounded vehicles shall remain
in storage for a period of 30 days if not released
earlier under the conditions set forth in Statute
28-3512.
CAD and Records
X
PremierOne complies with the functionality as described in the requirement.
2398
Out of the Box
Motorola
CTOW-019
TOWING
(WRECKERS)
General
If a deputy removes and either immobilizes or
impounds a vehicle pursuant to section 28-
3511, the department should provide the
owner, the spouse of the owner and any other
person identified on the department's record as
having an interest in the vehicle with the
opportunity for a post storage hearing to
determine the validity of the storage or
consider any mitigating circumstances relating
to the storage or release of the vehicle before
the end of the thirty day impoundment period.
Within three business days after impoundment,
excluding weekends and holidays, the
department should send a notice by first class
mail to each person, other than the owner,
identified on the department's record as having
an interest in the vehicle. The department also
has the same three business days to mail or
personally deliver notice of storage to the
owner of the vehicle. MCSO would like the
vendor to propose a solution which provides
the automated preparation and processing of
storage notices which contain the following
information:
Preferred
Records
X
PremierOne complies with the functionality of the requiement with the use of the Advanced
Configuration Tool. PremierOne Records can be customized to meet specific agency needs
through the use of the PremierOne Records Advanced Configuration Tool (ACT). Advanced
Configuration allows the agency to make PremierOne Records their own. The ACT allows an
agency to have custom forms in existing PremierOne records modules or new agency-specific
modules with agency-specific entry forms and reports. SSRS would be used to mail notices to
vehicle owners.
2399
With Configuration
Motorola
CTOW-019-1
TOWING
(WRECKERS)
General
A statement that the vehicle was immobilized
or impounded.
Preferred
Records
X
This is a PremierOne Records function. PremierOne Records complies with the functionality of the
requirement with the use of the Advanced Configuration Tool.
2400
Out of the Box
Motorola
CTOW-019-2
TOWING
(WRECKERS)
General
The name, address and telephone number of
MCSO contact for requesting a hearing.
Mandatory
Records
X
This is a PremierOne Records function. PremierOne Records complies with the functionality of the
requirement with the use of the Advanced Configuration Tool.
2401
Out of the Box
Motorola
CTOW-019-3
TOWING
(WRECKERS)
General
The location of the place of storage and a
description of the vehicle, including, if available,
the manufacturer, model, license plate number,
and mileage of the vehicle.
Preferred
CAD and Records
X
X
PremierOne complies with the functionality as described in the requirement.
2402
Out of the Box
Motorola
CTOW-020
TOWING
(WRECKERS)
General
The system should have the ability to log
modifications to the 35-11 status of the vehicle,
including contract release, NICB (National
Insurance Crime Bureau) modifications, and
purges.
Mandatory
Records
X
This is a PremierOne Records function. PremierOne Records complies with the functionality of the
requirement with the use of the Advanced Configuration Tool.
2403
Out of the Box
Motorola
CTOW-021
TOWING
(WRECKERS)
General
The system should also provide the ability to
capture, maintain, cross-reference, and report
on the registered owner's driver's license and
ownership information and the same
information for the vehicle's driver.
Mandatory
Records
X
This is a PremierOne Records function. PremierOne Records complies with the functionality of the
requirement with the use of the Advanced Configuration Tool.
2404
Out of the Box
Page 102of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CTOW-022
TOWING
(WRECKERS)
General
Compliance with the above statutory a
provision involves record keeping, scheduling,
case management and notification processes.
Vendors are being invited to propose a solution
for automating this process. Please put
emphasis on designing a solution that ensures
that all mandated notices are delivered within
the time specified.
Preferred
Records
X
This is a PremierOne Records function. PremierOne Records complies with the functionality of the
requirement with the use of the Advanced Configuration Tool. PremierOne Records can be
customized to meet specific agency needs through the use of the PremierOne Records Advanced
Configuration Tool (ACT). Advanced Configuration allows the agency to make PremierOne
Records their own. The ACT allows an agency to have custom forms in existing PremierOne
records modules or new agency-specific modules with agency-specific entry forms and reports.
SSRS would be used to mail notices to vehicle owners.
2405
Out of the Box
Motorola
CYBS001
Cyber Security
Gap Analysis
Vendor must understand the organizational
sector, risk profile, threats, and assets.
Mandatory
Risk Assessment
X
PremierOne complies with the functionality as described in the requirement.
2406
Out of the Box
Motorola
CYBS002
Cyber Security
Gap Analysis
Vendor must measure the risk and/or
compliance in the organization against one or
more frameworks
Mandatory
Risk Assessment
X
PremierOne complies with the functionality as described in the requirement.
2407
Out of the Box
Motorola
CYBS003
Cyber Security
Gap Analysis
Vendor must evaluate and report on current
network and connectivity environment
(Internal, External)
Mandatory
PenTest
X
PremierOne complies with the functionality as described in the requirement.
2408
Out of the Box
Motorola
CYBS004
Cyber Security
Gap Analysis
Vendor must determine the existing controls
and the controls that will need to be
remediated
Mandatory
Risk Assessment
X
PremierOne complies with the functionality as described in the requirement.
2409
Out of the Box
Motorola
CYBS005
Cyber Security
Gap Analysis
Review existing policies, procedures, and
workflows to determine additional needs and
documents that will need to be enhanced.
Mandatory
Risk Assessment
X
PremierOne complies with the functionality as described in the requirement.
2410
Out of the Box
Motorola
CYBS006
Cyber Security
Gap Analysis
Create a Plan of Action that will define the
remediation needs and be used to track
remediation progress.
Mandatory
Risk Assessment
X
PremierOne complies with the functionality as described in the requirement.
2411
Out of the Box
Motorola
CYBS007
Cyber Security
System Security Plan Develop and document an organizational
understanding to manage cybersecurity risk to
systems assets, data, and capabilities.
Mandatory
System Security
Plan
X
PremierOne complies with the functionality as described in the requirement.
2412
Out of the Box
Motorola
CYBS008
Cyber Security
System Security Plan The SSP (System Security Plan) will define
MCSO’s overall program, including the
technology environment, implemented
controls, polices that support the controls,
define the assets, and support infrastructure.
Mandatory
System Security
Plan
X
PremierOne complies with the functionality as described in the requirement.
2413
Out of the Box
Motorola
CYBS009
Cyber Security
System Security Plan The SSP (System Security Plan) will
demonstrate how the implemented controls,
policies, training and maintenance process
meets the required NIST framework compliance
requirements.
Mandatory
System Security
Plan
X
PremierOne complies with the functionality as described in the requirement.
2414
Out of the Box
Motorola
CYBS010
Cyber Security
System Security Plan This document provides a centralized
repository for knowledge that is specific to
MCSO's Technology Bureau environment and
the applicable security controls employed in
the environment. The SSP reflects input from
those responsible for the maintenance and
operation of the environment, including
information owners, system operators, and
other stakeholders.
Mandatory
System Security
Plan
X
PremierOne complies with the functionality as described in the requirement.
2415
Out of the Box
Motorola
CYBS011
Cyber Security
Cyber Incident
Response Plan
Develop and document an organizational
understanding to manage cybersecurity risk to
systems assets, data, and capabilities.
Mandatory
System Security
Plan
X
PremierOne complies with the functionality as described in the requirement.
2416
Out of the Box
Motorola
CYBS012
Cyber Security
Cyber Incident
Response Plan
The SSP (System Security Plan) will define
MCSO's overall program, including the
technology environment, implemented
controls, polices that support the controls,
define the assets, and support infrastructure.
Mandatory
System Security
Plan
X
PremierOne complies with the functionality as described in the requirement.
2417
Out of the Box
Motorola
CYBS013
Cyber Security
Disaster Recovery
Plan
Develop, document, and implement
appropriate activities to act upon, contain, and
reduce the impact of an event. The CIRP
(Computer Incident Response Plan) will provide
the operation’s response personnel with a
reference guide for handling cyber incidents
that might impact the business.
Mandatory
System Security
Plan
X
PremierOne complies with the functionality as described in the requirement.
2418
Out of the Box
Motorola
CYBS014
Cyber Security
Disaster Recovery
Plan
The plan provides steps for responding to
computer security incidents and standardized
process flows that include:
a) Identify the incident response (IR)
stakeholders and establish their roles and
responsibilities.
b) Describes incident triggering sources,
incident types, and incident severity levels.
c) Provide instruction and details on required
Federal and State reporting requirements.
d) Includes requirements for annual testing,
including post-incident lessons-learned
activities.
Mandatory
System Security
Plan
X
PremierOne complies with the functionality as described in the requirement.
2419
Out of the Box
Page 103of 104
Motorola Solutions, Inc.
Exhibit F - CAD Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot Meet
responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CYBS015
Cyber Security
General
At least one (1) of the primary or lead
personnel should have at least one of the
following certifications: GIAC Certified Incident
Handler (GCIH) GIAC Continuous Monitoring
Certification (GMON) GIAC Certified Detection
Analyst (GCDA) EC-Council Certified Incident
Handler (ECIH) Software Engineering Institute
(SEI) Certificate in Incident Response Process
Computer Emergency Response Team (CERT)
Certified Computer Security Incident Response
Handler Certified Information Security Systems
Professional (CISSP) Certified Information
Security Manager (CISM) Certified in Risk and
Information Systems Controls (CRISC) Certified
Cloud Security Professional (CCSP) Certificate of
Cloud Security Knowledge (CCSK) Or equivalent
certification from other certifying organizations
Or equivalent documented experience over at
least 4 years of active work
Mandatory
System Security
Plan
X
PremierOne complies with the functionality as described in the requirement.
2420
Out of the Box
Page 104of 104
Page 11-1
Section 11
Exhibit G: RMS Functional
Response Matrix
Please reference the separate PDF version of this Matrix.
230055-Exhibit G -
RMS Functional Req
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
Motorola
RGD001
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The general design of the system should comply
with the following requirements:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1
Out of the Box
Motorola
RGD002
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The system should be designed to operate as a
component of Computer Aided Dispatch,
seamlessly integrated with external Data
Warehouse, reporting tools, and other external
Public Safety
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
2
Out of the Box
Motorola
RGD003
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The system should allow the County’s authorized
users to retrieve, enter, and modify information in
the RMS through utilizing a browser interface.
Mandatory
Records
X
PremierOne does not use a browser
interface.
MCSO team stated this is not
required to be met.
3
Cannot Meet
Motorola
RGD004
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The system should provide an Administration and
Security module that will allow the System
Administrator to control security, Audit Access,
and integrate with federated services.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
4
Out of the Box
Motorola
RGD005
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
MCSO often has to respond to new mandates
quickly that make it necessary to add new data
field to entry/retrieval masks and store their entry
content in the database. Vendors are being ask to
explain in detail how they can satisfy this
requirement.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Possibly the most
dynamic and powerful tool
available today in the industry is
Motorola Solutions’ PremierOne
Advanced Configuration Tool (ACT).
With ACT, agencies can modify
existing software modules or create
new modules, including data
elements, field edits, workflow and
reporting. This is like having a
software developer included at no
extra charge to meet the needs of
the agency, without custom
programming. PremierOne Records
is unique in its ability to allow the
creation of agency-specific
modules. These simple modules
provide a centralized location for
the traditional paper forms that all
public safety agencies maintain.
An agency can have the time
saving, cost benefits of a central
repository for the many forms that
flood the department. Since these
d l
il bl f
i
h
5
With Configuration
Motorola
RGD006
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The system should be capable of maintaining a
minimum of 20 years of incident data online
without having to retrieve archived data.
Mandatory
Records
X
This requirement can be met with
the use of best practices
encouraging the purging of data
based on State Archival
recommendations enforced at the
County.
6
Out of the Box
Motorola
RGD007
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The system should include as many labor saving
routines as possible. For example, when an officer
is preparing several reports related to a single
event the officer will not have to reenter his/her
badge number for each item, or the location
where the event occurred. Similar information will
auto-populate,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
7
Out of the Box
Motorola
RGD008
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The system should have the ability to receive,
store, and manage data contained in customized
Maricopa County Sheriffs Department report
forms.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
8
Out of the Box
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Page 1 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RGD009
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The system should include a geographically based
analytical tool (mapping) component that provides
analytical tools for viewing and accessing spatial
relationships among stored data. Any data that is
capable of having an address or coordinates
should be capable of being represented visually on
the map. This includes incidents and other events,
districts, hydrants, stations, jurisdictional
boundaries, and hospitals. The offeror's GIS
mapping system should interface with an ESRI GIS
and the offeror should be able to import the
County's GIS data into their GIS solution. The
offeror should provide means to facilitate new
uploads of GIS data into system for use with their
software. CAD spatial data should also export into
GIS.
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. PremierOne CAD
utilizes Microsoft SQL Server
Reporting Services (SSRS) for its
standard reports. SSRS is a server-
based reporting platform that is
used to create and manage tabular,
matrix, graphical, dashboards, and
free form reports that contain data
from relational and
multidimensional data sources.
Map layers may be incorporated
into these reports. The Motorola
system is capable of creating and
printing reports with information
available in the database via SSRS
reports authored by the County
9
With Configuration
Motorola
RGD010
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The system should provide the capability for an
audit trail of all transactions including records
views.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
10
Out of the Box
Motorola
RGD011
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
When a user signs on to the proposed RMS
system, the system should be capable of
displaying an agency-defined user home-page, or
summary informing the user of information such
as:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
11
Out of the Box
Motorola
RGD011-1
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
incomplete reports for which the user is
responsible
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
12
Out of the Box
Motorola
RGD011-2
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
reports that have been returned for correction or
review for which the user is responsible
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
13
Out of the Box
Motorola
RGD011-3
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
returns from delayed inquiries to RMS, NCIC, and
other resources
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
14
Out of the Box
Motorola
RGD011-4
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
persons or items of interest “hits”
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
15
Out of the Box
Motorola
RGD012
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The proposed RMS system should provide the
County with the ability to copy information and
archive selected records to off-line devices and
transmit the data to off-site MCSO owned servers.
Please explain how this functionality can be
limited to a select number of users.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Each record in
PremierOne Records can have an
associated archive date. A system
administrator or other authorized
user can list all records of a
particular type (field interview,
citation, etc.) that are marked for
archive within a specified range (or
any other search criteria for that
record type). The user can then
select all records that match the
criteria or select specific records for
archival. A report off all select
records can be run that shows all
records select for archival.
Upon confirmation of the archive,
these records will be moved to the
archive system which is a separate
database. The archive database can
be configured to be on the same
database server as the main
PremierOne Records database or
on a separate server. This allows a
system administrator to move old
records out of the production
l
i
16
Out of the Box
Motorola
RGD013
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
All information contained within the RMS should
be available for inquires and report production.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
17
Out of the Box
Page 2 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RGD014
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The system database should have the ability to
input, store and export text, sound, images, and
other objects.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
18
Out of the Box
Motorola
RGD015
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The system should have the ability to attach
scanned images, such as pictures, diagrams, audio
files, video to a case record.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
19
Out of the Box
Motorola
RGD016
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The system's report formats should be sufficiently
configurable to avoid empty space and un-used
fields on all viewed and printed reports.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
20
Out of the Box
Motorola
RGD017
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The system should have the ability to search code
tables by code or by code description.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
21
Out of the Box
Motorola
RGD018
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The system should capture relevant user-defined
data elements and perform required edit
validation for:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
22
Out of the Box
Motorola
RGD018-1
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
Uniformed Crime Reporting (UCR) (NIBRS) system
( edit to ensure that required fields are entered at
time of entry)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
23
Out of the Box
Motorola
RGD018-2
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
Master Name Index (MNI)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
24
Out of the Box
Motorola
RGD018-3
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
Master Vehicle Index (MVI)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
25
Out of the Box
Motorola
RGD018-4
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
Master Property Index (MPI)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
26
Out of the Box
Motorola
RGD018-5
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
Master Telephone Index (MTI)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
27
Out of the Box
Motorola
RGD018-6
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
Automated Field Reporting
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
28
Out of the Box
Motorola
RGD018-7
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
Investigations
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
29
Out of the Box
Motorola
RGD018-8
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
Case Management
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
30
Out of the Box
Motorola
RGD018-9
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
Crime Analysis
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
31
Out of the Box
Motorola
RGD018-10
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
Arrest and Booking
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
32
Out of the Box
Motorola
RGD018-11
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
Warrant Control
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
33
Out of the Box
Motorola
RGD018-12
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
Registrant Tracking
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
34
Out of the Box
Motorola
RGD018-13
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
Neighborhood Services
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
35
Out of the Box
Motorola
RGD018-14
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
Code Enforcement
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
36
Out of the Box
Page 3 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RGD018-15
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
Animal Control
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
37
Out of the Box
Motorola
RGD018-16
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
Accreditation.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
38
Out of the Box
Motorola
RGD018-17
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
County Probation
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
39
Out of the Box
Motorola
RGD019
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
Vendors are being asked to comment on their
systems capability to provide a standard XML data
interface API that can be used by customer as
required.
Mandatory
Records
X
PremierOne doesn't have an
external API, but we do have a
published data view. That data view
interface was included with our
solution.
40
Out of the Box
Motorola
RGD020
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The Maricopa County Attorney's Office needs to
read case reports and all attachments for cases
that have been submitted for prosecution. They
need to reports back to the detectives with
notations, and they need to import case
information into their internal system upon
request.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
41
Out of the Box
Motorola
RGD021
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The system should be designed to allow external
agencies the ability to read, write, and report. The
system should have federated services for other
agenies that MCSO is able to control security
access as well as have an audit trail.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. With permissions,
PremierOne Mobile client can be
used to perform all standard
Records functions.
42
Out of the Box
Motorola
RGD022
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The system must have the ability for Records
Division users to upload/add attachments to an
IR. TraCS has a Records Attachment form in which
is used to upload forms received by the
Operations Information Center (OIC) and the
Departmental Reports Section (DR). Such forms
include, but not limited to:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
43
Out of the Box
Motorola
RGD022-1
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
Preservation of Evidence documentation (request
to sequester, cancellation of Preservation of
Evidence (POE)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
44
Out of the Box
Motorola
RGD022-2
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
Insurance Claims/Letters of Subrogation
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
45
Out of the Box
Motorola
RGD022-3
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
Recovered, Seized, Lost Gun releases to
owners/NOK
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
46
Out of the Box
Motorola
RGD022-4
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
Investigative Alert Entries and Hits
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
47
Out of the Box
Motorola
RGD022-5
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
Public Records Requests/Requests from other
agencies (MCAO, PDs, etc.)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
48
Out of the Box
Motorola
RGD022-6
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
Items recovered and taken out of NCIC
(notification sent to initial author) (items include
recovered articles, gun, license plates, missing
person, securities, vehicle parts, stolen vehicles,
stolen boats)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
49
Out of the Box
Motorola
RGD022-7
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
Teletype transmittals
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
50
Out of the Box
Motorola
RGD022-8
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
Victim Notifications
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
51
Out of the Box
Motorola
RGD022-9
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
Stolen Property Reports received from Victims
(notification sent to initial author)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
52
Out of the Box
Page 4 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RGD022-10
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
Stolen Vehicle and Boat ACIC/NCIC entries and
MVD/Game and Fish Registrations
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
53
Out of the Box
Motorola
RGD022-11
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
Stolen Vehicle and Boat validation request letters
(sent to victim each year at last known address)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
54
Out of the Box
Motorola
RGD023
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The system shall support high availability and
distributed load balancing.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
55
Out of the Box
Motorola
RGD024
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
Data entry forms shall allow the user to change
the font size to make if more easily viewable by
those needing a larger font.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
56
Out of the Box
Motorola
RGD025
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
All data entry forms shall have a printout option
that can be modified by the agency.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
57
Out of the Box
Motorola
RGD026
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The printed outputs shall include all the data from
the entry forms.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
58
Out of the Box
Motorola
RGD027
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The printed outputs shall include agency
information including logos and agency address
information.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
59
Out of the Box
Motorola
RGD028
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
Only the printed output forms that have been
defined for a particular agency shall be displayed
to the user.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
60
Out of the Box
Motorola
RGD029
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The system shall have the ability to generate
complex Process Workflows.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
61
Out of the Box
Motorola
RGD030
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The system shall allow links to other web-sites to
be placed on RMS system menus.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
62
Out of the Box
Motorola
RGD031
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The system must be capable of a variety of
mirroring options.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
63
Out of the Box
Motorola
RGD032
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The system shall provide an open architecture
design.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
64
Out of the Box
Motorola
RGD033
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
Solution must be based on highly reusable object
oriented programming such as Microsoft .NET
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
65
Out of the Box
Motorola
RGD034
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The system must use an industry standard SQL
structure accessible by ad hoc reporting and query
tools.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
66
Out of the Box
Motorola
RGD035
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
Database backups must be performed online
without DBMS downtime.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
67
Out of the Box
Motorola
RGD036
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The system must provide the ability to store
records in an Archive database that can be housed
on a separate server.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
68
Out of the Box
Motorola
RGD037
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The system must allow a record to be saved as a
draft even if data entered in the field does not
conform to the data type. For example, allow a
name to be entered into a telephone number field.
Mandatory
Records
X
If the pre-determined data type is
correct, incorrect information may
be saved in a draft copy. The
example given of saving a name in a
phone number field is not possible
in PremierOne.
MCSO & Motorola teams agree
requirement is met out of the
box.
69
Cannot Meet
Motorola
RGD038
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
Only authorized users can access the records
stored in the Archive database.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
70
Out of the Box
Motorola
RGD039
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The RMS system must be developed as a true
Service Oriented Architecture (SOA).
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
71
Out of the Box
Page 5 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RGD040
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The system must support database replication.
Describe how this is accomplished.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
72
Out of the Box
Motorola
RGD041
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The system must provide a standard interface
connection layer.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
73
Out of the Box
Motorola
RGD042
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
No technical or physical limit shall exist for the
number of application or database servers that
can be combined into a single environment.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
74
Out of the Box
Motorola
RGD043
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The system must allow the agency to add an
unlimited number of additional fields to any
vendor delivered form. This data must populate a
separate data warehouse.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
75
Out of the Box
Motorola
RGD044
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The system must allow the agency to make any
field searchable including those added by the
agency.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
76
Out of the Box
Motorola
RGD045
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The system must allow the agency to change the
printed output of any form without vendor
assistance.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
77
Out of the Box
Motorola
RGD046
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The system must allow the agency to make
changes or create a redaction template for any
printed form.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
78
Out of the Box
Motorola
RGD047
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The system must allow the agency to create new
modules without vendor assistance. The new
module must consist of a data entry screen, search
fields, search results screens, printed output and
data populated into a separate reporting data
warehouse.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
79
Out of the Box
Motorola
RGD048
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The system must allow the agency to add external
Web URLs to the application menu without vendor
assistance.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
80
Out of the Box
Motorola
RGD049
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The RMS system must utilize the Microsoft
Windows Server operating software.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
81
Out of the Box
Motorola
RGD050
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The system must provide system administrators
the ability to set-up rules that will allow or deny
attachments of specific file types (ex. txt, jpg,
mpeg, etc.).
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
82
Out of the Box
Motorola
RGD051
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
All records in the archive database must be able to
be accessed from within the application.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
83
Out of the Box
Motorola
RGD052
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The system must auto-save data entered into a
report on a periodic basis.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
84
Out of the Box
Motorola
RGD053
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The system shall be highly-configurable by non-
technical end-users, to allow the system to meet
most agency technical, operational and functional
specifications without major software
development or hard-coding of parameters by
technical personnel.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
85
Out of the Box
Motorola
RGD054
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The Records system shall provide command line as
well as screens forms for user entry.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
86
Out of the Box
Motorola
RGD055
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The system shall be document centric.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
87
Out of the Box
Motorola
RGD056
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The system must be web based and designed with
a thin/intelligent client footprint. No other types
of systems will be considered. Any vendor
proposing an alternative type will have their
proposal rejected.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
88
Out of the Box
Motorola
RGD057
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The system must support integration of Computer-
Aided Dispatch, digitized mug shots, images, and
optical imaging of records.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
89
Out of the Box
Page 6 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RGD058
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The system shall have the ability to query external
databases to get access to information, (i.e.,
warrants, people, articles, guns).
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
90
Out of the Box
Motorola
RGD059
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
On-line help must be available from any screen.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
91
Out of the Box
Motorola
RGD060
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
Both ad hoc and preformatted on-line report
writing must be supported.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
92
Out of the Box
Motorola
RGD061
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
Automated Case Management workflow for
approvals and appropriate follow-up shall be
provided.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
93
Out of the Box
Motorola
RGD062
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The system must include case folders for case
reports. Case folders must allow various file
attachments.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
94
Out of the Box
Motorola
RGD063
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The system shall provide for a single visual
container to display all documents associated to
an investigation.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
95
Out of the Box
Motorola
RGD064
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
Formatted screens must be available for initiating
database inquiries.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
96
Out of the Box
Motorola
RGD065
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The system must be event based and RMS Case
Folders can be used to represent events.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
97
Out of the Box
Motorola
RGD066
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The RMS client software shall be self updating
without the necessity of manual updates to each
client.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
98
Out of the Box
Motorola
RGD067
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The spell check shall have the capability to check
every field in data entry forms as selected by the
agency.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
99
Out of the Box
Motorola
RGD068
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The system must record all records changes as
well as other events in the system that may not
result in a records change. Every change to the
data within the system must be recorded in the
auditing system. Describe how this is
accomplished
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
100
Out of the Box
Motorola
RGD069
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
Ability to simultaneously operate a "training"
system. The training system must have identical
functionality as the live system, but be available
for training and scenarios.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
101
Out of the Box
Motorola
RGD070
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
Data shall be able to be entered via data entry
forms without server communication until the
form is saved.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
102
Out of the Box
Motorola
RGD071
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The system administrator shall have the ability to
add ad-hoc reports to the reports menus.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
103
Out of the Box
Motorola
RGD072
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The system must be expandable via the addition of
more application servers.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
104
Out of the Box
Motorola
RGD073
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The system shall be structured to support multi-
agency data sharing.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
105
Out of the Box
Motorola
RGD074
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The system shall segregate data at the agency ORI
level.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
106
Out of the Box
Motorola
RGD075
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
Ability to simultaneously operate a "test" system.
The test system must be available to test system
changes prior to their implementation on the
training or live/production systems.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
107
Out of the Box
Page 7 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RGD076
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The system shall support multiple ORI level
agencies within a single installation instance.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
108
Out of the Box
Motorola
RGD077
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
Spell check shall be integrated into every data
entry form.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
109
Out of the Box
Motorola
RGD078
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
The Application must fully support XML including
NIEM.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
110
Out of the Box
Motorola
RGD079
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
If a LE Request version is chosen, the system
should ask for the requestor’s ORI, name, and
badge #, or other credentials and stamp the report
with a Secondary Dissemination warning.
Mandatory
Records
X
PremierOne does not have this
capability.
When creating printouts unique watermarks can be
applied. System doesn't know the number of times a
document is printed. Could create a LE print template with
unique watermark.
When printing a document cannot capture ORI, Name and
Badget # at time of printing, but could use form builder to
create a document type that is part of folder structure
called dissemination request log.
Could also use SSRS report.
MCSO & Motorola teams agree
requirement is met out of the box
per notes in Column O.
111
Cannot Meet
Motorola
RGD080
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
If a Public Records Request version is chosen, the
system should automatically redact pre-defined
fields within the IR. If a form within the IR is not
releasable to the public, that form shall not be
printed.
Mandatory
Records
X
PremierOne does not have this
capability.
Within form builder have the ability to create redaction
templates and select a redaction template to apply to
printing of document. Redaction at field level is possible.
Don't have the specific ability to restrict if a form is
released to the public, however, modifying folder
MCSO & Motorola teams agree
requirement is met out of the box
per notes in Column O.
112
Cannot Meet
Motorola
RGD081
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
Records requests should have a forms for Law
Enforcement Requests and a Public Records
Request to choose from when printing.
Mandatory
Records
X
PremierOne does not have this
capability.
System has the ability to meet multiple different print
template options.
MCSO & Motorola teams agree
requirement is met out of the box
per notes in Column O.
113
Cannot Meet
Motorola
RGD082
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
If a LE Request version is chosen, the system
should ask for the requestor’s ORI, name, and
badge #, or other credentials and stamp the report
with a Secondary Dissemination warning.
Mandatory
Records
X
PremierOne does not have this
capability.
This is a duplicate with RGD079. Explanation from RGD079
was agreed to, reference RGD079 comments for details.
MCSO & Motorola teams agree
requirement is met out of the box
per notes in Column O.
114
Cannot Meet
Motorola
RGD083
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
If a Public Records Request version is chosen, the
system should automatically redact pre-defined
fields within the IR. If a form within the IR is not
releasable to the public, that form shall not be
printed.
Mandatory
Records
X
PremierOne does not have this
capability.
This is a duplicate with RGD080. Explanation from RGD080
was agreed to, reference RGD080 comments for details.
MCSO & Motorola teams agree
requirement is met out of the box
per notes in Column O.
115
Cannot Meet
Motorola
RGD084
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
MCSO wants to make information available to
citizens about crimes occurring in their
neighborhoods. Inquiries would be based upon
postal codes or common neighborhood/area
names. Vendors are being asked to offer any
solutions that they can provide to meet this
requirement. Neighborhood watch groups need
the capability to view the crimes in their
designated areas.
Mandatory
CommandCentral
Community
X
PremierOne complies with the
functionality as described in the
requirement utilizing Microsoft SQL
Server Reporting Services (SSRS). As
part of deployment, Motorola will
apply canned reports to the system
and lead a reporting writing
workshop with County personnel.
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. MCSO can create
reports that will automatically run
and be delivered to the applicable
apartment complex management
through email, at a schedule
determined by the County.
116
With Configuration
Page 8 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RGD085
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
General
Apartment complexes that register with the Crime
Free Housing Program need to be provided with
information on calls for service at their locations.
Both the complex managers and owners are sent E-
mail or postal notices that describe what has taken
place at their complexes. The system also keeps
running totals of all activities and produces reports
showing any actions taken by the
managers/owners and whether any repeat
offenders are involved. Vendors are being asked
to offer any solutions that they can provide to
meet this requirement.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement utilizing Microsoft SQL
Server Reporting Services (SSRS). As
part of deployment, Motorola will
apply canned reports to the system
and lead a reporting writing
workshop with County personnel.
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. MCSO can create
reports that will automatically run
and be delivered to the applicable
apartment complex management
through email, at a schedule
determined by the County.
117
With Configuration
Motorola
RGD086
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
Security and User
Profile
The activity log shall record a unique serial number
of each print job that can be printed on the
physical copy.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
118
Out of the Box
Motorola
RGD087
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
Security and User
Profile
The system shall provide an activity log for each
case that allows authorized users to see who has
added, modified, deleted or printed records in that
folder.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
119
Out of the Box
Motorola
RGD088
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
Security and User
Profile
The activity log shall be separate from the system
audit log and require a different level of security to
access.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
120
Out of the Box
Motorola
RGD089
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
Security and User
Profile
The activity log shall record any changes, etc. that
are made to the records from inside or outside of
the case folder.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
121
Out of the Box
Motorola
RGD090
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
Security and User
Profile
The activity log shall record a unique serial number
of each print job that can be printed on the
physical copy to allow a user to determine who
generated the actual printout.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
122
Out of the Box
Motorola
RGD091
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
Security and User
Profile
The system must attach a digital hash value or
signature to each record for integrity verification
and non-repudiation.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
123
Out of the Box
Motorola
RGD092
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
Security and User
Profile
The digital signature must be encrypted and
stored with each record.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
124
Out of the Box
Motorola
RGD093
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
Security and User
Profile
The digital signature must be created for each
digital attachment such as image, video, Word
documents, etc.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
125
Out of the Box
Motorola
RGD094
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
Security and User
Profile
The system must check the digital signature each
time a form or attachment is opened to determine
if any unauthorized changes have been made to
the document.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
126
Out of the Box
Motorola
RGD095
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
Security and User
Profile
The system shall have the ability to provide a
single access point for master security
administration for all modules, and for agency
administration.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
127
Out of the Box
Motorola
RGD096
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
Security and User
Profile
The system requires only a single user ID log-on at
the local agency network (Windows Active
Directory).
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
128
Out of the Box
Motorola
RGD097
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
Security and User
Profile
The system can alternatively be configured to use
an internal authentication database.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
129
Out of the Box
Motorola
RGD098
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
Security and User
Profile
The system shall have the ability to provide a
secure means of viewing the audit logs in a usable
fashion for an authorized system user, so that they
can be reviewed, analyzed, printed and archived.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
130
Out of the Box
Page 9 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RGD099
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
Security and User
Profile
The system must support Active Directory
authentication across trusted domains.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
131
Out of the Box
Motorola
RGD100
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
Security and User
Profile
If using Active Directory Authentication the system
shall provide an option for a silent log-in that
passes the users credentials without prompting
them.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
132
Out of the Box
Motorola
RGD101
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
Security and User
Profile
The internal authentication model must encrypt
any stored passwords.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
133
Out of the Box
Motorola
RGD102
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
Security and User
Profile
The system must allow both Active Directory and
Internal database authentication on the same
system.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
134
Out of the Box
Motorola
RGD103
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
Security and User
Profile
The system must support SAML tokens or other
claims-based security model.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
135
Out of the Box
Motorola
RGD104
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
Security and User
Profile
All internal services called must require an
authorized token to process the request.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
136
Out of the Box
Motorola
RGD105
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
Security and User
Profile
The system shall have the ability to define user
access levels, (i.e., add, delete, modify) and to
assign these access authorizations to individuals or
to groups at the local agency.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
137
Out of the Box
Motorola
RGD106
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
Security and User
Profile
The system shall have the ability to specify access
rights for individual users or groups of users, to
individual records, groups of records, or individual
case folders at the local agency.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
138
Out of the Box
Motorola
RGD107
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
Security and User
Profile
The system shall have the ability to differentiate
between read, write and delete access to records
for each agency.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
139
Out of the Box
Motorola
RGD108
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
Security and User
Profile
The system will enable each agency to define user
and group access rights to records and the
functions that can be performed by each user or
group of users.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
140
Out of the Box
Motorola
RGD109
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
Security and User
Profile
The system shall have the ability to limit access to
specific cases based on individuals or groups
defined in the application security administration.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
141
Out of the Box
Motorola
RGD110
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
Security and User
Profile
The system shall have the ability to maintain a
detailed audit trail of all changes made to any
record in the system.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
142
Out of the Box
Motorola
RGD111
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
Security and User
Profile
The system shall have the ability to maintain an
application security system, which can be modified
quickly with no programming required.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
143
Out of the Box
Motorola
RGD112
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
Security and User
Profile
Audit records shall provide the following
information about each action; date and time,
user, IP address of workstation and before and
after values of the changed fields.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
144
Out of the Box
Motorola
RGD113
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
Security and User
Profile
The system shall notify the user when their
password has expired.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
145
Out of the Box
Motorola
RGD114
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
Security and User
Profile
The system shall prevent a single user from logging
into concurrent sessions.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
146
Out of the Box
Motorola
RGD115
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
Security and User
Profile
All login attempts; successful or failed, shall be
logged for auditing by the system.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
147
Out of the Box
Motorola
RGD116
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
Security and User
Profile
The system administrator shall have the ability to
remove administrative users from personnel
dropdown lists.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
148
Out of the Box
Motorola
RGD117
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
Workflow and
Messaging
The system must provide the ability to create
workflows for each module in the system,
including those created by the agency.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
149
Out of the Box
Page 10 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RGD118
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
Workflow and
Messaging
The system shall allow for process flows to be sent
to external sources, including cell phones pagers,
text messages, email, etc.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
150
Out of the Box
Motorola
RGD119
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
Workflow and
Messaging
The system shall have the ability to send
messages, tasks, and bulletins to a person, group,
organization, supervisor or group of supervisors,
or down the chain of command.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
151
Out of the Box
Motorola
RGD120
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
Workflow and
Messaging
The system shall support a manual override option
at any stage in the workflow.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
152
Out of the Box
Motorola
RGD121
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
Workflow and
Messaging
The system shall include a workflow stage to mark
an IBR or UCR compliant report for state
submission.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
153
Out of the Box
Motorola
RGD122
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
Workflow and
Messaging
The system shall include a workflow stage to verify
state specific IBR or UCR compliancy.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
154
Out of the Box
Motorola
RGD123
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
Workflow and
Messaging
The system shall include complete document
workflow history.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
155
Out of the Box
Motorola
RGD124
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
Workflow and
Messaging
The system shall have the ability to send any
document to a person, group, organization,
supervisor or group of supervisors, or down the
chain of command.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
156
Out of the Box
Motorola
RGD125
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
Workflow and
Messaging
The system shall include manual and automated
workflow branching.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
157
Out of the Box
Motorola
RGD126
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
Workflow and
Messaging
The system shall include a workflow tool designed
to rapidly deploy complex document and process
flows.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
158
Out of the Box
Motorola
RGD127
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
Workflow and
Messaging
The system must provide the ability to create
workflows that are either global or agency specific.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
159
Out of the Box
Motorola
RGD128
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
Workflow and
Messaging
The system shall have the ability to generate
complex process workflows.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
160
Out of the Box
Motorola
RGD129
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
Workflow and
Messaging
All information flows, whether through the
message queue or the workflow, shall be based on
the organization created in this utility.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
161
Out of the Box
Motorola
RGD130
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
Workflow and
Messaging
This utility will allow all documents, messages or
tasks to be sent to individuals, supervisors, all
subordinates of a supervisor, or the entire agency.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
162
Out of the Box
Motorola
RGD131
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
Workflow and
Messaging
This utility shall allow for the creation of templates
and organization charts.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
163
Out of the Box
Motorola
RGD132
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
Workflow and
Messaging
The system shall provide a utility to represent
each agency’s structure, hierarchies and chain of
command.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
164
Out of the Box
Motorola
RGD133
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
Workflow and
Messaging
In a multi-agency system, the system must allow
individual agencies to either use the global
workflow or configure their own.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
165
Out of the Box
Motorola
RGD134
GENERAL
REQUIREMENTS
AND DESIGN
FEATURES
Workflow and
Messaging
Workflows shall have the ability to route cases to
particular precincts, or other administrative
entities.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
166
Out of the Box
Motorola
RUD001
USER INTERFACE
DESIGN
General
The system shall provide a web-based interface for
running reports and querries.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
167
Out of the Box
Motorola
RUD002
USER INTERFACE
DESIGN
General
The design of the user interface should assist both
experienced and novice users to complete
individual forms and entire reports.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
168
Out of the Box
Page 11 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RUD003
USER INTERFACE
DESIGN
General
The mobile client should support a day and night
mode for screen display (to include day and night
mode for the map display, field based reporting,
and all other applications available on the MDC
and mobile devices).
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
169
Out of the Box
Motorola
RUD004
USER INTERFACE
DESIGN
General
The system should include drop down lists for
restricted entry fields but will not require the user
to access the list if they know and wish to enter a
correct value directly.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
170
Out of the Box
Motorola
RUD005
USER INTERFACE
DESIGN
General
The interface should utilize tabs to keep forms self-
contained, as opposed to using multiple, separate
windows to perform all available functions.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
171
Out of the Box
Motorola
RUD006
USER INTERFACE
DESIGN
General
Tabs should group all related data.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
172
Out of the Box
Motorola
RUD007
USER INTERFACE
DESIGN
General
The system should provide a clear/reset button
that removes data from all fields on the current
screen which employs a mandatory second key-
stroke to verify that the user desires to remove
the data.
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
173
Cannot Meet
Motorola
RUD008
USER INTERFACE
DESIGN
General
When a user is required to enter their name and ID
number, the system should enter the name and ID
of the user that is logged on automatically.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
174
Out of the Box
Motorola
RUD009
USER INTERFACE
DESIGN
General
User information to auto populate based upon
logged in user credentials to minimize the amount
of double data entry.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
175
Out of the Box
Motorola
RUD010
USER INTERFACE
DESIGN
General
The vendor should describe their approach to auto-
saving data that has been entered into forms and
fields including its ability to be customized.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement. PremierOne Records
Mobile has an autosave feature
that allows work to be saved in the
event of disconnection. The
PremierOne Mobile solution
supports store and forward, as well
as the ability to operate in a
disconnected mode in the event
there is no network connectivity.
Both applications can be utilized in
low connectivity areas. PremierOne
Records allows users to be
disconnected throughout the shift
while still working in the application
and completing reports. Once a
connection is established, the work
completed will be pushed (without
user intervention) to the server.
176
Out of the Box
Motorola
RUD011
USER INTERFACE
DESIGN
Incident Records
The System must display a listing of all events or
cases present in a responsible party’s work queue.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
177
Out of the Box
Motorola
RUD012
USER INTERFACE
DESIGN
Incident Records
The System must allow for supervisor rejection of
submitted reports including comments and shall
display a rejection notification symbol.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
178
Out of the Box
Motorola
RUD013
USER INTERFACE
DESIGN
Incident Records
The System must allow a supervisor to view a
subordinate’s work queue.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
179
Out of the Box
Motorola
RUD014
USER INTERFACE
DESIGN
Incident Records
The system will support the tracking of solvability
factors that are configurable by the system
administrator. These factors will have a weighted
score associated so that the agency can run a
report stating which cases have the highest scored
value.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
180
Out of the Box
Motorola
RUD015
USER INTERFACE
DESIGN
Incident Records
The system will support the association of other
events to an incident, for example a traffic report
or an arrest event.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
181
Out of the Box
Motorola
RUD016
USER INTERFACE
DESIGN
Incident Records
The system must allow all supervisors to be able to
reject completed reports and return the report to
the responsible party’s work queue.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
182
Out of the Box
Motorola
RUD017
USER INTERFACE
DESIGN
Incident Records
The system will allow the event association to be
indicated for each of these items.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
183
Out of the Box
Page 12 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RUD018
USER INTERFACE
DESIGN
Incident Records
Additional personnel for each incident must
include responding officer, assisting or secondary
responding officers, and the arresting officer.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
184
Out of the Box
Motorola
RUD019
USER INTERFACE
DESIGN
Incident Records
The system will support the addition of multiple
people, vehicles, addresses, businesses, and/or
property to an incident.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
185
Out of the Box
Motorola
RUD020
USER INTERFACE
DESIGN
Incident Records
The system must allow records to be imported
from either a mobile or CAD system.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
186
Out of the Box
Motorola
RUD021
USER INTERFACE
DESIGN
Incident Records
System must have a configurable workflow
component for routing and approval of incidents
to various operational groups within an agency
including investigators, supervisors, etc.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
187
Out of the Box
Motorola
RUD022
USER INTERFACE
DESIGN
Incident Records
The system must not limit the number of
violations that can be entered.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
188
Out of the Box
Motorola
RUD023
USER INTERFACE
DESIGN
Incident Records
Incident and Arrest Reports must be NIBRS
compliant.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
189
Out of the Box
Motorola
RUD024
USER INTERFACE
DESIGN
Incident Records
Incident records shall be able to be rejected for
corrections and re-approved.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
190
Out of the Box
Motorola
RUD025
USER INTERFACE
DESIGN
Incident Records
Free form text entry within an incident must be
provided.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
191
Out of the Box
Motorola
RUD026
USER INTERFACE
DESIGN
Incident Records
The system must provide for the entry of
addresses, units, business and home telephone
numbers, DOB’s, sex and race for each entry.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
192
Out of the Box
Motorola
RUD027
USER INTERFACE
DESIGN
Incident Records
The system must accommodate multiple entries
by role as required. Role includes complainant,
victim, witness, reporting party, suspect,
arrested/cited, named in, AKA’s, street or gang
names.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
193
Out of the Box
Motorola
RUD028
USER INTERFACE
DESIGN
Incident Records
Case numbers must be automatically generated
and formatted to meet each agency’s numbering
system.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
194
Out of the Box
Motorola
RUD029
USER INTERFACE
DESIGN
Incident Records
The citation feature must include: citation
number(s), time and date stamp, location,
violation (ordinance or statute), vehicle
description, license number and state, model and
color of vehicle.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
195
Out of the Box
Motorola
RUD030
USER INTERFACE
DESIGN
Incident Records
Approved case reports shall be able to be locked
as read-only.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
196
Out of the Box
Motorola
RUD031
USER INTERFACE
DESIGN
Incident Records
The addition of documents (and media files such
as images (e.g.- mug shots) ) shall be allowed as a
part of the record or case folder.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
197
Out of the Box
Motorola
RUD032
USER INTERFACE
DESIGN
Incident Records
Incident reports must not be editable once
approved unless they go through the
approval/workflow process.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
198
Out of the Box
Motorola
RUD033
USER INTERFACE
DESIGN
Incident Records
The system must enable local incident codes with
an automatic cross reference “translation” to
Federal UCR/NIBR codes and descriptions in order
to produce monthly State specific reports.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
199
Out of the Box
Motorola
RUD034
USER INTERFACE
DESIGN
Incident Records
When creating supplemental reports, the agency
will have the ability to configure whether the
narrative is brought forward from the case report.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
200
Out of the Box
Motorola
RUD035
USER INTERFACE
DESIGN
Incident Records
The primary case officer must have the ability to
receive notifications whenever a case folder is
accessed, added to, or modified by others.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
201
Out of the Box
Motorola
RS001
SEARCHING
Incident Records
Data entry should be minimized and search forms
user friendly. Auto Propagation (Known Data)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
202
Out of the Box
Motorola
RS002
SEARCHING
General
The system should have the ability to;
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
203
Out of the Box
Motorola
RS002-1
SEARCHING
General
Search for event records by such common criteria
as case number, incident type, date and time,
victim/witness/suspect name, address, physical
descriptors, POI, occupation, property, etc.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
204
Out of the Box
Page 13 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RS002-2
SEARCHING
General
Search for data by any field (e.g., name, phone
number, address, intersection. date of birth,
employee badge number, date, code, serial
number, etc.), or combination of fields.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
205
Out of the Box
Motorola
RS002-3
SEARCHING
General
Search for all case reports by EIN, date and time
ranges, District, Patrol Area(s), and other user
defined criteria.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
206
Out of the Box
Motorola
RS002-4
SEARCHING
General
Conduct a “free-text” search of all narrative fields
in the RMS.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
207
Out of the Box
Motorola
RS002-5
SEARCHING
General
Initiate searches and queries using full or partial
data strings.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
208
Out of the Box
Motorola
RS002-6
SEARCHING
General
Perform searches in wildcard and partial spelling
format
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
209
Out of the Box
Motorola
RS002-7
SEARCHING
General
Provide Soundex or equivalent search for all “free
text” narrative and data fields.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
210
Out of the Box
Motorola
RS002-8
SEARCHING
General
Display exact matches and close or near matches
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
211
Out of the Box
Motorola
RS002-9
SEARCHING
General
Provide advanced and flexible query and search
capabilities through user-friendly, ad-hoc
reporting.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
212
Out of the Box
Motorola
RS002-10
SEARCHING
General
Search for a case number using the date the
offense was reported.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
213
Out of the Box
Motorola
RS003
SEARCHING
General
The system should provide a universal search
engine.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
214
Out of the Box
Motorola
RS004
SEARCHING
General
The system should utilize a concept algorithm or
"fuzzy logic" to automatically compute the
strength of relationships between each possible
pair of concept descriptors identified in a search.
For example, if a user is searching for all case
reports where a "boom-box" was reported stolen,
the system will return a summary listing of all case
reports where boom-box, boom box, personal
stereo, and portable stereo, etc. were listed as
stolen. If a user is searching the RMS for all
records containing the name "Jacobson", the
system should return a summary report of records
listing names that are similar like “Jacobsen”,
“Jaycobsin” etc.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
215
Out of the Box
Motorola
RS005
SEARCHING
General
The system should have the ability to query
multiple databases, e.g., local and state name
databases, through use of a single transaction.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
216
Out of the Box
Motorola
RS006
SEARCHING
General
When a user is searching the RMS for information
a single inquiry should yield results that contain all
RMS records including associated electronic files
(e.g., scanned images, and all other available
objects) via a summary page with hyperlinks or
other similar method.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
217
Out of the Box
Motorola
RS007
SEARCHING
General
When users enter a search parameter the system
should display a summary of multiple valid records
and allow the user to select the desired record.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
218
Out of the Box
Motorola
RS008
SEARCHING
General
The system should allow users to cancel and exit a
search query while it’s active.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
219
Out of the Box
Motorola
RS009
SEARCHING
General
The system should allow individual users to save
search criteria in their profile for re-use.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
220
Out of the Box
Motorola
RS010
SEARCHING
General
The system should possess extensive “drill down”
capabilities. For example, if a name search returns
four potential candidates, the user should be able
to view each record by selecting it in some
manner. If the record displayed then had a co-
defendant, the user should be able to select that
record and see the co-defendant records, and so
on.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
221
Out of the Box
Page 14 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RS011
SEARCHING
General
The system should have the ability to retrace the
drill down steps to return to where the drill down
began. The vendor shall describe its method to
accomplishing this functionality (e.g. drill down
tree, etc.)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
222
Out of the Box
Motorola
RS012
SEARCHING
General
The system shall allow MCSO the ability to
customize required databases for the application
to consume via, MDC, Laptop or mobile devices.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
223
Out of the Box
Motorola
RS013
SEARCHING
General
It is expected that District and Patrol Area
boundaries will change in order to ensure
appropriate staffing based on workload demands.
Therefore, when conducting historical searches,
the system should:
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO & Motorola teams agree
requirement is met out of the
box.
224
Cannot Meet
Motorola
RS014
SEARCHING
General
Ensure that District and Patrol Area boundary
changes are reflected in the Master Address Index
so that historical data searches return only data
contained within the new boundaries and/or (user-
definable) data contained within the old
boundaries for comparative analysis.
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO explanation that the intent of this requirement was
that historical data is preserved as current system changes
an old record based on updates to boundary changes.
MCSO & Motorola teams agree
requirement is met out of the box
per notes in Column O.
225
Cannot Meet
Motorola
RS015
SEARCHING
General
Ensure that boundary changes are reflected in
every other proposed module. For example, when
a pre-boundary change case report is reviewed as
part of a search return, both the new and old
District and Patrol Area numerical designator will
appear in the appropriate fields.
Mandatory
Records
X
PremierOne does note have this
functionality.
MCSO team stated this is not
required to be met.
226
Cannot Meet
Motorola
RI001
INDEXES
General
The Master Name Index should incorporate
subject records from various sources. Individuals
identified in any record (suspect, victim, witness,
complainant, etc.) will be stored.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
227
Out of the Box
Motorola
RI002
INDEXES
General
MCSO is asking the vendors to detail how they will
process indexable subjects that are truly unknown
(no associated identifiers/information at all) and
indexable subjects that are unknown but have
some associated data (an MO for example).
MCSO's goal is to avoid cluttering its name index
with useless entries, but it also does not want to
lose valuable associated information for a subject
that is unknown.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
228
Out of the Box
Motorola
RI003
INDEXES
General
Information from field interview records, case
reports, warrants, and all other data sources
should be indexed to this file.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
229
Out of the Box
Motorola
RI004
INDEXES
General
The system should provide a means for name and
object search (including aliases) both by exact
spelling, diminutives and phonetic search
capability.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
230
Out of the Box
Motorola
RI005
INDEXES
General
The system should notify users of possible
matches (hits) immediately.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
231
Out of the Box
Motorola
RI006
INDEXES
General
The system should include automated and semi
automated routines to assist the application
administrator or other authorized user with
managing the indexes. The purpose of these
features will be to ensure that index associations
are correct and to prevent, as much as possible,
cases from being associated with the wrong entry
in an index. For example, the application should be
able to identify when a record does not have an
associated master index entry, or if a master index
entry has a duplicate record.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
232
Out of the Box
Motorola
RI007
INDEXES
General
Upon the entry of data into any field which is
associated with a master index the system should
automatically search the appropriate master index
for similar entries.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
233
Out of the Box
Motorola
RI008
INDEXES
General
In the event that the master index contains a
similar name or item, a summary list should
display showing the particulars of the names or
items that are similar to the one being entered.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
234
Out of the Box
Motorola
RI009
INDEXES
General
The system should allow the user to associate the
name or item being entered with one on the list
retrieved from the master index.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
235
Out of the Box
Page 15 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RI010
INDEXES
General
When a user who is completing a case report or
other form elects to associate a name or item with
an existing master index record the application
shall create a conditional association.
Mandatory
Records
X
Conditional
Association
When entering a new person into
PremierOne, a search is performed
against the Master Name index
prior to creation. A list of all names
meeting the criteria is displayed to
include Name, Sex, DOB, Current
Age, Height, Weight, Eye Color, Hair
Color and whether the person is a
Juvenile. From this initial list, the
user can open any of these name
records to verify the if a new name
record is to be created, or if one of
the items returned should be the
person record associated with the
case report.PremierOne complies
with the functionality as described
in the requirement.
236
Out of the Box
Motorola
RI011
INDEXES
General
Once a user has created a conditional association
the system will cease searching the master indexes
for that particular name or item during the
remainder of the report entry process.
Mandatory
Records
X
Conditional
Association
PremierOne complies with the
functionality as described in the
requirement.
237
Out of the Box
Motorola
RI012
INDEXES
General
Conditional associations should remain until the
system administrator or another authorized user
reviews the conditional association.
Mandatory
Records
X
Conditional
Association
PremierOne complies with the
functionality as described in the
requirement. The Records User
makes the final determination of
which person's record to use in the
case report.
238
Out of the Box
Motorola
RI013
INDEXES
General
If the two names or items refer to the same
person or item, the authorized reviewer should be
able to approve the conditional association and
make it permanent.
Mandatory
Records
X
Conditional
Association
PremierOne complies with the
functionality as described in the
requirement.
239
Out of the Box
Motorola
RI014
INDEXES
General
The system should clearly delineate between
associations that are conditional and those that
have been positively verified through a fingerprint
identification.
Mandatory
Records
Conditional
Association
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met. LiveScan
interface will handle this.
240
Cannot Meet
Motorola
RI015
INDEXES
General
If the names or items have been incorrectly
associated, the authorized reviewer should have
the ability to remove the conditional association
and create a new master index record for the
newly entered name or item.
Mandatory
Records
X
Conditional
Association
PremierOne complies with the
functionality as described in the
requirement.
241
Out of the Box
Motorola
RI016
INDEXES
General
The system should allow only authorized users to
delete or transfer master index associations from
one master index record to another.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
242
Out of the Box
Motorola
RI017
INDEXES
General
The system should allow only authorized users to
join two or more master index records that
erroneously appear in multiple master index
records. When joining two master index records
the application shall preserve the most recently
entered information.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
243
Out of the Box
Motorola
RI018
INDEXES
General
The system should also permit authorized users to
un-link permanent associations.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
244
Out of the Box
Motorola
RI019
INDEXES
General
The system should have the ability to
automatically collect information from all reports
and add them to the appropriate master indexes.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
245
Out of the Box
Motorola
RI020
INDEXES
General
The system should be able to create and maintain
basic agency-definable Master Name Index
records, including but not limited to multiple
entries for such data elements as:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
246
Out of the Box
Motorola
RI020-1
INDEXES
General
Name (transposed middle and/or first name),
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
247
Out of the Box
Page 16 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RI020-2
INDEXES
General
Address,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
248
Out of the Box
Motorola
RI020-3
INDEXES
General
Aliases,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
249
Out of the Box
Motorola
RI020-4
INDEXES
General
Date of Birth,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
250
Out of the Box
Motorola
RI020-5
INDEXES
General
Nickname(s),
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
251
Out of the Box
Motorola
RI020-6
INDEXES
General
Place of Birth,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
252
Out of the Box
Motorola
RI020-7
INDEXES
General
Sex (male, female, transgender, etc.).
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
253
Out of the Box
Motorola
RI020-8
INDEXES
General
Social security numbers,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
254
Out of the Box
Motorola
RI020-9
INDEXES
General
Ethnicity
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
255
Out of the Box
Motorola
RI020-10
INDEXES
General
Hair (color, length, style, etc.)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
256
Out of the Box
Motorola
RI020-11
INDEXES
General
Eyes (color, shape, size, etc.)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
257
Out of the Box
Motorola
RI020-12
INDEXES
General
Glasses
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
258
Out of the Box
Page 17 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RI020-13
INDEXES
General
Facial hair
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
259
Out of the Box
Motorola
RI020-14
INDEXES
General
Face shape
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
260
Out of the Box
Motorola
RI020-15
INDEXES
General
Complexion
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
261
Out of the Box
Motorola
RI020-16
INDEXES
General
Teeth (gold, missing, decayed, dentures, etc.)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
262
Out of the Box
Motorola
RI020-17
INDEXES
General
Height
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
263
Out of the Box
Motorola
RI020-18
INDEXES
General
Weight
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
264
Out of the Box
Motorola
RI020-19
INDEXES
General
Build
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
265
Out of the Box
Motorola
RI020-20
INDEXES
General
Handed
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
266
Out of the Box
Motorola
RI020-21
INDEXES
General
Body piercing(s),
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
267
Out of the Box
Motorola
RI020-22
INDEXES
General
Special Characteristics (Scars, Marks, Tattoos,
including location(s), etc.),
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
268
Out of the Box
Motorola
RI020-23
INDEXES
General
Clothing type,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
269
Out of the Box
Page 18 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RI020-24
INDEXES
General
Clothing description,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
270
Out of the Box
Motorola
RI020-25
INDEXES
General
Alcohol use/addiction,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
271
Out of the Box
Motorola
RI020-26
INDEXES
General
Drug use/addiction,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
272
Out of the Box
Motorola
RI020-27
INDEXES
General
Escape risk,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
273
Out of the Box
Motorola
RI020-28
INDEXES
General
Juvenile,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
274
Out of the Box
Motorola
RI020-29
INDEXES
General
Adult,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
275
Out of the Box
Motorola
RI020-30
INDEXES
General
Mental risk,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
276
Out of the Box
Motorola
RI020-31
INDEXES
General
Physical handicap,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
277
Out of the Box
Motorola
RI020-32
INDEXES
General
Missing/deformed limbs,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
278
Out of the Box
Motorola
RI020-33
INDEXES
General
Missing/deformed appendages,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
279
Out of the Box
Motorola
RI020-34
INDEXES
General
Sex registrant,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
280
Out of the Box
Page 19 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RI020-35
INDEXES
General
Sex offender
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
281
Out of the Box
Motorola
RI020-36
INDEXES
General
Suicidal,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
282
Out of the Box
Motorola
RI020-37
INDEXES
General
Violent offender.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
283
Out of the Box
Motorola
RI020-38
INDEXES
General
Gang association/affiliation
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
284
Out of the Box
Motorola
RI020-39
INDEXES
General
Terrorist
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
285
Out of the Box
Motorola
RI020-40
INDEXES
General
Distinguishing characteristics (County-defined),
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
286
Out of the Box
Motorola
RI020-41
INDEXES
General
Driver License number and state (multiple),
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
287
Out of the Box
Motorola
RI020-42
INDEXES
General
FBI #,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
288
Out of the Box
Motorola
RI020-43
INDEXES
General
Flag (sex offender registrant; domestic violence
flag, etc.),
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
289
Out of the Box
Motorola
RI020-44
INDEXES
General
Fingerprints on file,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
290
Out of the Box
Motorola
RI020-45
INDEXES
General
ID coding (e.g., Fingerprint, DNA, FBI#),
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
291
Out of the Box
Page 20 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RI020-46
INDEXES
General
Involvement (e.g., suspect, witness, victim, person
pawning, etc.),
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
292
Out of the Box
Motorola
RI020-47
INDEXES
General
Known associates (multiple),
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
293
Out of the Box
Motorola
RI020-48
INDEXES
General
Incarceration status
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
294
Out of the Box
Motorola
RI020-49
INDEXES
General
County booking number as assigned by the
Sheriff's Office
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
295
Out of the Box
Motorola
RI020-50
INDEXES
General
Local assigned booking number
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
296
Out of the Box
Motorola
RI020-51
INDEXES
General
Online screen name,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
297
Out of the Box
Motorola
RI020-52
INDEXES
General
E-mail address,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
298
Out of the Box
Motorola
RI020-53
INDEXES
General
Pager number,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
299
Out of the Box
Motorola
RI020-54
INDEXES
General
Phone number,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
300
Out of the Box
Motorola
RI020-55
INDEXES
General
Photo on file,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
301
Out of the Box
Motorola
RI020-56
INDEXES
General
And any other related case number(s),
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
302
Out of the Box
Page 21 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RI020-57
INDEXES
General
Subject's Employment
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
303
Out of the Box
Motorola
RI020-58
INDEXES
General
Employer (multiple),
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
304
Out of the Box
Motorola
RI020-59
INDEXES
General
Occupation,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
305
Out of the Box
Motorola
RI020-60
INDEXES
General
Employer Name,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
306
Out of the Box
Motorola
RI020-61
INDEXES
General
Employer Address,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
307
Out of the Box
Motorola
RI020-62
INDEXES
General
Employer Telephone number (multiple),
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
308
Out of the Box
Motorola
RI020-63
INDEXES
General
Relatives (Multiple),
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
309
Out of the Box
Motorola
RI020-64
INDEXES
General
Name,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
310
Out of the Box
Motorola
RI020-65
INDEXES
General
Address,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
311
Out of the Box
Motorola
RI020-66
INDEXES
General
Telephone Number (Multiple),
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
312
Out of the Box
Motorola
RI020-67
INDEXES
General
Sex,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
313
Out of the Box
Page 22 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RI020-68
INDEXES
General
Relationship,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
314
Out of the Box
Motorola
RI020-69
INDEXES
General
Employer (multiple),
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
315
Out of the Box
Motorola
RI020-70
INDEXES
General
Occupation,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
316
Out of the Box
Motorola
RI020-71
INDEXES
General
Employer Name,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
317
Out of the Box
Motorola
RI020-72
INDEXES
General
Employer Address,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
318
Out of the Box
Motorola
RI020-73
INDEXES
General
Employer Telephone number (multiple),
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
319
Out of the Box
Motorola
RI020-74
INDEXES
General
Probation officer name and contact information
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
320
Out of the Box
Motorola
RI020-75
INDEXES
General
Special restrictions
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
321
Out of the Box
Motorola
RI020-76
INDEXES
General
Associates of the subject.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
322
Out of the Box
Motorola
RI021
INDEXES
General
The system should have the ability to track agency-
defined individual changes (for an individual) for
all of the aforementioned Master Name Index
records such as but not limited to:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Entry for all items
lacking a specified field within
Master People can be done in the
Notes tab of the Master Person
record.
323
Out of the Box
Motorola
RI021-1
INDEXES
General
Physical description changes,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
324
Out of the Box
Motorola
RI021-2
INDEXES
General
Address changes,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
325
Out of the Box
Motorola
RI021-3
INDEXES
General
Phone number changes,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
326
Out of the Box
Page 23 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RI021-4
INDEXES
General
Driver License changes,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
327
Out of the Box
Motorola
RI021-5
INDEXES
General
Name changes,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
328
Out of the Box
Motorola
RI021-6
INDEXES
General
Date of birth changes.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
329
Out of the Box
Motorola
RI022
INDEXES
General
The system should be capable of identifying
duplicate records by drivers' license number, and
all other user-defined criteria.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
330
Out of the Box
Motorola
RI023
INDEXES
General
The system should be capable of consolidating
designated duplicate records.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
331
Out of the Box
Motorola
RI024
INDEXES
General
The system should be able to verify and edit
names based on agency-defined data including but
not limited to:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
332
Out of the Box
Motorola
RI024-1
INDEXES
General
Full or partial name (first name or last name),
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
333
Out of the Box
Motorola
RI024-2
INDEXES
General
Address,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
334
Out of the Box
Motorola
RI024-3
INDEXES
General
Date of birth,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
335
Out of the Box
Motorola
RI024-4
INDEXES
General
Sex
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
336
Out of the Box
Motorola
RI024-5
INDEXES
General
Race
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
337
Out of the Box
Motorola
RI024-6
INDEXES
General
Driver License number,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
338
Out of the Box
Motorola
RI024-7
INDEXES
General
Local arrest number,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
339
Out of the Box
Motorola
RI025
INDEXES
General
The system should have the capability to assign
agency-specified descriptions of an individual and
create a Master Name record without having a
specific name (e.g., person known for a nickname,
attribute).
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
340
Out of the Box
Motorola
RI026
INDEXES
General
The system should have the ability to cross
reference the Master Name file with all other
records associated with an individual i.e., case
reports, images, businesses, pawn information,
vehicles, phone numbers, warrants, co-
defendant(s), etc.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
341
Out of the Box
Motorola
RI027
INDEXES
General
The system should have the ability to combine
records of an individual if they have been entered
under different names and to automatically track
those names as aliases of the individual. This
would apply to a situation where the same person
has two identities.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
342
Out of the Box
Motorola
RI028
INDEXES
General
The system should also have the ability to combine
records of an individual if they have been entered
under different names and to reconcile those
names if a duplicate entry exists for the same
person.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
343
Out of the Box
Motorola
RI029
INDEXES
General
The system should have the ability to attach
additional/multiple identifiers (DOB, DL, user
defined, etc.) to the same name/aliases.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
344
Out of the Box
Motorola
RI030
INDEXES
General
The system should provide a means for vehicle
search by all vehicle master data. It should
perform edit validation by preventing duplicate
vehicles from being entered.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
345
Out of the Box
Motorola
RI031
INDEXES
General
The system should provide a menu for searching
for vehicles by user-selected attributes including
partial license plates.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
346
Out of the Box
Motorola
RI032
INDEXES
General
The system should create and maintain basic user-
definable Master Vehicle Index records, including
but not limited to multiple entries for each data
field below:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
347
Out of the Box
Page 24 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RI032-1
INDEXES
General
Associates (owner, driver, passenger),
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
348
Out of the Box
Motorola
RI032-2
INDEXES
General
Name,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
349
Out of the Box
Motorola
RI032-3
INDEXES
General
Address,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
350
Out of the Box
Motorola
RI032-4
INDEXES
General
Date of Birth,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
351
Out of the Box
Motorola
RI032-5
INDEXES
General
Race,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
352
Out of the Box
Motorola
RI032-6
INDEXES
General
Sex,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
353
Out of the Box
Motorola
RI032-7
INDEXES
General
Aliases (multiple),
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
354
Out of the Box
Motorola
RI032-8
INDEXES
General
Phone Number
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
355
Out of the Box
Motorola
RI032-9
INDEXES
General
Contact information,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
356
Out of the Box
Motorola
RI032-10
INDEXES
General
Date
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
357
Out of the Box
Motorola
RI032-11
INDEXES
General
Time
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
358
Out of the Box
Motorola
RI032-12
INDEXES
General
Location
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
359
Out of the Box
Motorola
RI032-13
INDEXES
General
Reason for contact (summons, warrant, field
contact, crash report, etc.)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
360
Out of the Box
Motorola
RI032-14
INDEXES
General
Reporting area (Patrol Area)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
361
Out of the Box
Motorola
RI032-15
INDEXES
General
EIN of officer conducting contact
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
362
Out of the Box
Motorola
RI032-16
INDEXES
General
Vehicle (automobile, boat, motorcycle, etc.)
information,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
363
Out of the Box
Motorola
RI032-17
INDEXES
General
Make
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
364
Out of the Box
Motorola
RI032-18
INDEXES
General
Model,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
365
Out of the Box
Motorola
RI032-19
INDEXES
General
Color,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
366
Out of the Box
Motorola
RI032-20
INDEXES
General
Year, and range of years
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
367
Out of the Box
Motorola
RI032-21
INDEXES
General
Number of doors
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
368
Out of the Box
Motorola
RI032-22
INDEXES
General
Tag number
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
369
Out of the Box
Motorola
RI032-23
INDEXES
General
VIN number
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
370
Out of the Box
Motorola
RI032-24
INDEXES
General
Other special characteristics (bumper sticker,
damage, etc.).
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
371
Out of the Box
Motorola
RI033
INDEXES
General
The system should have the ability to capture and
maintain the following minimum agency-definable
towing information for a vehicle (multiple records)
such as:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
372
Out of the Box
Page 25 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RI033-1
INDEXES
General
Date towed,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
373
Out of the Box
Motorola
RI033-2
INDEXES
General
Time towed,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
374
Out of the Box
Motorola
RI033-3
INDEXES
General
Location towed to,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
375
Out of the Box
Motorola
RI033-4
INDEXES
General
Number of days/hours stored,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
376
Out of the Box
Motorola
RI033-5
INDEXES
General
Name of tow company,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
377
Out of the Box
Motorola
RI033-6
INDEXES
General
Phone number of tow company,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
378
Out of the Box
Motorola
RI033-7
INDEXES
General
Reason towed,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
379
Out of the Box
Motorola
RI033-8
INDEXES
General
EIN of officer requesting tow,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
380
Out of the Box
Motorola
RI033-9
INDEXES
General
Date available for release,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
381
Out of the Box
Motorola
RI033-10
INDEXES
General
Release date,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
382
Out of the Box
Motorola
RI033-11
INDEXES
General
Released by,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
383
Out of the Box
Motorola
RI033-12
INDEXES
General
Released to (with contact information).
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
384
Out of the Box
Motorola
RI034
INDEXES
General
The system should have the ability to link
information related to individuals associated with
a vehicle with the Master Name Index.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
385
Out of the Box
Motorola
RI035
INDEXES
General
The system should also maintain the additional
minimum user-definable Master Indexes:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
386
Out of the Box
Motorola
RI035-1
INDEXES
General
Master Location Index (MLI)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
387
Out of the Box
Motorola
RI035-2
INDEXES
General
Master Property Index (MPI)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
388
Out of the Box
Motorola
RI035-3
INDEXES
General
Master Telephone Index (MTI)
Mandatory
Records
X
PremierOne does not contain a
master index for telephone
numbers, but all numbers stored in
Records can be queried.
Phone number is part of current master indices. Search
from P1 records does not grab Vesta data except from
phone numbers captured within CAD call for service.
Advanced search by phone number returns results where
phone number is referenced across the system. One
example discussed of a non phone search result would be
for a confidential informant, unless role has privileges to
see.
MCSO & Motorola teams agree
requirement is met out of the box
per notes in Column O.
389
Cannot Meet
Motorola
RI035-4
INDEXES
General
Master Organization Index (MOI) (businesses,
schools, gangs, etc.)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
390
Out of the Box
Motorola
RI036
INDEXES
General
The system should have the ability to associate
multiple digital mug shots with the Master Name
Index and perform a "point and click" retrieval of
the associated mugs hot at the desktop and MDC
level.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
391
Out of the Box
Motorola
RI037
INDEXES
General
Users should have the ability to make a notation of
their interest in the subject of a master index
record. (Person or Item of Interest such as a car,
telephone number, location, etc.)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
392
Out of the Box
Motorola
RI038
INDEXES
General
When a user runs a search on a person or item of
interest name (POI), the system should notify the
user making the search or updates that the record
is the subject of interest to another user.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
393
Out of the Box
Motorola
RI039
INDEXES
General
When a master index record with a POI indication
is retrieved, the system should notify the user
initiating the POI and any other user who searches
the RMS for the same POI.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
394
Out of the Box
Page 26 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RI040
INDEXES
General
The MCSO generally provides only case report
summaries to authorized parties. The system
should permit the system administrator or other
authorized users to edit report information to
filter sensitive or confidential information before
the report is released to the public or for general
use outside of the department. The type of
information that is edited includes victim names in
certain types of cases, juvenile information, or
information that is considered by the agency to be
sensitive to an investigation.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
395
Out of the Box
Motorola
RI041
INDEXES
General
In the case of formatted and structured data,
report output programs should be able to produce
a redacted version of specific report data. In the
case of narrative or otherwise unstructured
information, the redaction process may requires a
manual step to produce a public version of the
report.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
396
Out of the Box
Motorola
RI042
INDEXES
General
The proposed RMS application should also allow
the system administrator or other authorized user
to determine which fields may not be printed on
copies of reports that are to be distributed to the
public.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
397
Out of the Box
Motorola
RI043
INDEXES
General
The MCSO Legal Compliance Section requires the
ability to produce report copies for the General
Public which they often have to redact and copies
for the County Attorney without redaction.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
398
Out of the Box
Motorola
RI044
INDEXES
General
The system should provide the ability to manually
enter old case reports into the system. The original
case number and approving supervisor
information should be maintained. Process should
be limited to Central Records.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
399
Out of the Box
Motorola
RI045
INDEXES
General
The system should be capable of notifying the user
initiating the POI and/or Item of Interest via:
Mandatory
Records
Follow
X
Persons or Items of interest
notifications occur within the
PremierOne system. External
systems cannot receive alerts.
MCSO team stated this is not
required to be met.
400
Cannot Meet
Motorola
RI045-1
INDEXES
General
The County e-mail system
Mandatory
Records
Follow
X
Persons or Items of interest
notifications occur within the
PremierOne system. External
systems cannot receive alerts.
MCSO team stated this is not
required to be met.
401
Cannot Meet
Motorola
RI045-2
INDEXES
General
Any e-mail address entered by the user
Mandatory
Records
Follow
X
Persons or Items of interest
notifications occur within the
PremierOne system. External
systems cannot receive alerts.
MCSO team stated this is not
required to be met.
402
Cannot Meet
Motorola
RI045-3
INDEXES
General
A text message to any telephone or pager number
entered by the user
Mandatory
Records
Follow
X
Persons or Items of interest
notifications occur within the
PremierOne system. External
systems cannot receive alerts.
MCSO team stated this is not
required to be met.
403
Cannot Meet
Motorola
RI045-4
INDEXES
General
All or any combination of the above methods
simultaneously.
Mandatory
Records
Follow
X
Persons or Items of interest
notifications occur within the
PremierOne system. External
systems cannot receive alerts.
MCSO team stated this is not
required to be met.
404
Cannot Meet
Motorola
RI046
INDEXES
General
The system should allow the user entering a POI to
specify a “blind” notification when someone else
conducts a search for the same POI.
Mandatory
Records
X
Follow
PremierOne complies with the
functionality as described in the
requirement.
405
Out of the Box
Motorola
RI047
INDEXES
General
Hits on “blind” persons or items of interest should
notify the person who entered the “blind”
notification request but will not notify the user
conducting the search.
Mandatory
Records
X
Follow
PremierOne complies with the
functionality as described in the
requirement.
406
Out of the Box
Motorola
RI048
INDEXES
General
No one, other than the person entering the POI,
the system administrator or other authorized user,
will be able to see a list of POI entries.
Mandatory
Records
X
Follow
PremierOne complies with the
functionality as described in the
requirement.
407
Out of the Box
Motorola
RI049
INDEXES
General
The system will flag special alerts and warrants on
a person record.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
408
Out of the Box
Motorola
RI050
INDEXES
General
The system must provide a view of all active and
inactive alerts.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
409
Out of the Box
Motorola
RI051
INDEXES
General
The system will provide a master record summary
screen that contains the most recent image, alerts
and demographic information.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
410
Out of the Box
Page 27 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RI052
INDEXES
General
The system will provide a master record summary
screen on each master record screen.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
411
Out of the Box
Motorola
RI053
INDEXES
General
The system will provide a master record summary
screen that can be displayed on master index
search results.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
412
Out of the Box
Motorola
RI054
INDEXES
General
The system will provide a master record summary
screen that is displayed whenever a user is
entering a new event record and associating it
with a master record.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
413
Out of the Box
Motorola
RI055
INDEXES
General
The system must provide a mechanism to merge
one or more duplicate master records.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
414
Out of the Box
Motorola
RI056
INDEXES
General
The system will allow alerts to be associated with
any master index.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
415
Out of the Box
Motorola
RI057
INDEXES
General
The system will display associated alerts with an
agency specified color.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
416
Out of the Box
Motorola
RI058
INDEXES
General
The system will display associated alerts in an
agency specified priority order.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
417
Out of the Box
Motorola
RI059
INDEXES
General
The system must limit alerts to be set only by
authorized users.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
418
Out of the Box
Motorola
RI060
INDEXES
General
The system must allow a user to add notes to an
alert.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
419
Out of the Box
Motorola
RI061
INDEXES
General
They system must provide a master person and
master vehicle search that orders the returns with
the most likely matches.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
420
Out of the Box
Motorola
RI062
INDEXES
General
The system must expire alerts (make inactive)
after the ending date/time.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
421
Out of the Box
Motorola
RI063
INDEXES
General
The system shall allow the related master view to
be interactive allowing an investigator open source
event records as allow by security.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
422
Out of the Box
Motorola
RI064
INDEXES
General
The system will allow a qualified user to mark a
Person record as “verified”, meaning that the
information in that record has been checked and is
deemed valid.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
423
Out of the Box
Motorola
RI065
INDEXES
General
Verifying a record shall be a security role that can
be given to any security group.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
424
Out of the Box
Motorola
RI066
INDEXES
General
The system shall allow an incident record to be
associated to a master record once the record is
verified.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
425
Out of the Box
Motorola
RI067
INDEXES
General
The master record shall be an aggregate of the
most recent data about a person regardless of the
document source.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
426
Out of the Box
Motorola
RI068
INDEXES
General
The system shall allow any number of verified
Person records to be associated with a master
record.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
427
Out of the Box
Motorola
RI069
INDEXES
General
The system shall include a view of all related
master records and events.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
428
Out of the Box
Motorola
RI070
INDEXES
General
The system shall include a graphic "link analysis"
style view of all related master records.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
429
Out of the Box
Motorola
RI071
INDEXES
General
The system shall allow the related Master View to
be interactive allowing an investigator to easily
navigate through the related records.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
430
Out of the Box
Motorola
RI072
INDEXES
General
The system will track all associations of a master
entity to any other master entity.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
431
Out of the Box
Motorola
RI073
INDEXES
General
The system must identify potential duplicate
master records.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
432
Out of the Box
Motorola
RI074
INDEXES
General
The system must provide a beginning date/time
and ending date/time for each alert.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
433
Out of the Box
Motorola
RI075
INDEXES
General
The system must allow any number of known
associates.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
434
Out of the Box
Page 28 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RI076
INDEXES
General
Data must be entered only once into the system
and be automatically added to the master index as
it is entered into other parts of the system.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
435
Out of the Box
Motorola
RI077
INDEXES
General
The system must provide access to the source
documents from which the index item posted.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
436
Out of the Box
Motorola
RI078
INDEXES
General
Master name information must be accessible by
name and by other key identifiers (e.g., social
security number, driver’s license number, DOB).
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
437
Out of the Box
Motorola
RI079
INDEXES
General
The system must capture alias names, DOB’s,
SSN’s, addresses (past and present), pawns, traffic
and parking citations, field contacts/interviews,
warrants, gun registrations, known associates,
past and present employers, and arrests.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
438
Out of the Box
Motorola
RI080
INDEXES
General
The system must be able to track any number of
AKA’s, alias DOB’s and alias SSN’s.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
439
Out of the Box
Motorola
RI081
INDEXES
General
The system must maintain a history of contacts,
arrests, and citations received.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
440
Out of the Box
Motorola
RI082
INDEXES
General
The system must maintain past and present
addresses and telephone numbers.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
441
Out of the Box
Motorola
RI083
INDEXES
General
The system must maintain past and present
employers.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
442
Out of the Box
Motorola
RI084
INDEXES
General
The system must provide a master index that
references all entries for an individual, property
item, vehicle item, business, and address.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
443
Out of the Box
Motorola
RI085
INDEXES
Master Index
The system will flag special alerts and warrants on
a person record.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
444
Out of the Box
Motorola
RI086
INDEXES
Master Index
The system must provide a view of all active and
inactive alerts.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
445
Out of the Box
Motorola
RI087
INDEXES
Master Index
The system will provide a master record summary
screen that contains the most recent image, alerts
and demographic information.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
446
Out of the Box
Motorola
RI088
INDEXES
Master Index
The system will provide a master record summary
screen on each master record screen.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
447
Out of the Box
Motorola
RI089
INDEXES
Master Index
The system will provide a master record summary
screen that can be displayed on master index
search results.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
448
Out of the Box
Motorola
RI090
INDEXES
Master Index
The system will provide a master record summary
screen that is displayed whenever a user is
entering a new event record and associating it
with a master record.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
449
Out of the Box
Motorola
RI091
INDEXES
Master Index
The system must provide a mechanism to merge
one or more duplicate master records.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
450
Out of the Box
Motorola
RI092
INDEXES
Master Index
The system will allow alerts to be associated with
any master index.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
451
Out of the Box
Motorola
RI093
INDEXES
Master Index
The system will display associated alerts with an
agency specified color.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
452
Out of the Box
Motorola
RI094
INDEXES
Master Index
The system will display associated alerts in an
agency specified priority order.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
453
Out of the Box
Motorola
RI095
INDEXES
Master Index
The system must limit alerts to be set only by
authorized users.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
454
Out of the Box
Motorola
RI096
INDEXES
Master Index
The system must allow a user to add notes to an
alert.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
455
Out of the Box
Motorola
RI097
INDEXES
Master Index
They system must provide a master person and
master vehicle search that orders the returns with
the most likely matches.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
456
Out of the Box
Motorola
RI098
INDEXES
Master Index
The system must expire alerts (make inactive)
after the ending date/time.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
457
Out of the Box
Page 29 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RI099
INDEXES
Master Index
The system shall allow the related master view to
be interactive allowing an investigator open source
event records as allow by security.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
458
Out of the Box
Motorola
RI100
INDEXES
Master Index
The system will allow a qualified user to mark a
Person record as “verified”, meaning that the
information in that record has been checked and is
deemed valid.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
459
Out of the Box
Motorola
RI101
INDEXES
Master Index
Verifying a record shall be a security role that can
be given to any security group.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
460
Out of the Box
Motorola
RI102
INDEXES
Master Index
The system shall allow an incident record to be
associated to a master record once the record is
verified.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
461
Out of the Box
Motorola
RI103
INDEXES
Master Index
The master record shall be an aggregate of the
most recent data about a person regardless of the
document source.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
462
Out of the Box
Motorola
RI104
INDEXES
Master Index
The system shall allow any number of verified
Person records to be associated with a master
record.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
463
Out of the Box
Motorola
RI105
INDEXES
Master Index
The system shall include a view of all related
master records and events.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
464
Out of the Box
Motorola
RI106
INDEXES
Master Index
The system shall include a graphic "link analysis"
style view of all related master records.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
465
Out of the Box
Motorola
RI107
INDEXES
Master Index
The system shall allow the related Master View to
be interactive allowing an investigator to easily
navigate through the related records.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
466
Out of the Box
Motorola
RI108
INDEXES
Master Index
The system will track all associations of a master
entity to any other master entity.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
467
Out of the Box
Motorola
RI109
INDEXES
Master Index
The system must identify potential duplicate
master records.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
468
Out of the Box
Motorola
RI110
INDEXES
Master Index
The system must provide a beginning date/time
and ending date/time for each alert.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
469
Out of the Box
Motorola
RI111
INDEXES
Master Index
The system must allow any number of known
associates.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
470
Out of the Box
Motorola
RI112
INDEXES
Master Index
Data must be entered only once into the system
and be automatically added to the master index as
it is entered into other parts of the system.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
471
Out of the Box
Motorola
RI113
INDEXES
Master Index
The system must provide access to the source
documents from which the index item posted.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
472
Out of the Box
Motorola
RI114
INDEXES
Master Index
Master name information must be accessible by
name and by other key identifiers (e.g., social
security number, driver’s license number, DOB).
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
473
Out of the Box
Motorola
RI115
INDEXES
Master Index
The system must capture alias names, DOB’s,
SSN’s, addresses (past and present), pawns, traffic
and parking citations, field contacts/interviews,
warrants, gun registrations, known associates,
past and present employers, and arrests.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
474
Out of the Box
Motorola
RI116
INDEXES
Master Index
The system must be able to track any number of
AKA’s, alias DOB’s and alias SSN’s.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
475
Out of the Box
Motorola
RI117
INDEXES
Master Index
The system must maintain a history of contacts,
arrests, and citations received.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
476
Out of the Box
Motorola
RI118
INDEXES
Master Index
The system must maintain past and present
addresses and telephone numbers.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
477
Out of the Box
Motorola
RI119
INDEXES
Master Index
The system must maintain past and present
employers.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
478
Out of the Box
Motorola
RI120
INDEXES
Master Index
The system must provide a master index that
references all entries for an individual, property
item, vehicle item, business, and address.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
479
Out of the Box
Motorola
RPS001
PRINTER
SERVICES
General
The system should offer any authorized person the
ability to print:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
480
Out of the Box
Page 30 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RPS002
PRINTER
SERVICES
General
The entire case file, including all forms, notes,
activities, images, etc.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
481
Out of the Box
Motorola
RPS003
PRINTER
SERVICES
General
A “public" case file which includes forms defined
by the system administrator or other authorized
employee as being of public record.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
482
Out of the Box
Motorola
RPS004
PRINTER
SERVICES
General
The system should not allow a public report to be
printed before all reports are approved.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
483
Out of the Box
Motorola
RPS005
PRINTER
SERVICES
General
The system should provide the ability to print a
single user-selected form, activity, image, or note
from the case file.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
484
Out of the Box
Motorola
RPS006
PRINTER
SERVICES
General
The system should have the ability to direct output
of any inquiry or report to:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
485
Out of the Box
Motorola
RPS006-1
PRINTER
SERVICES
General
a screen (workstation and MDC)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
486
Out of the Box
Motorola
RPS006-2
PRINTER
SERVICES
General
e-mail
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
487
Out of the Box
Motorola
RPS006-3
PRINTER
SERVICES
General
printer
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
488
Out of the Box
Motorola
RPS006-4
PRINTER
SERVICES
General
PDF
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
489
Out of the Box
Motorola
RPS007
PRINTER
SERVICES
General
The printed output should be configurable by the
System Administrator.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
490
Out of the Box
Motorola
RPS008
PRINTER
SERVICES
General
Should the offeror's system impose a limit on the
amount of text that can be inputted into a
narrative field, the solution should provide a
simple option for inputting additional text into the
same report and associating data from the original
narrative field. This is especially utilized when
preparing lengthy investigations.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. The current character
limit for each case report is
322,727. To quantify, that equates
to approximately 107 pages of text
allowed per report.
491
Out of the Box
Motorola
RPS009
PRINTER
SERVICES
General
For example, when a Supplement Report is
prepared on-line, if the narrative area exceeds the
amount of space on the first page, the narrative
should continue on a subsequent page while
maintaining the original header and footers of the
report.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. The current character
limit for each case report is
322,727. To quantify, that equates
to approximately 107 pages of text
allowed per report.
492
Out of the Box
Motorola
RPS010
PRINTER
SERVICES
General
In the above instance, all information entered into
the header and footer of the first page of the
report should populate the header and footer of
the second and subsequent pages that may be
required.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
493
Out of the Box
Motorola
RPS011
PRINTER
SERVICES
General
All printed reports, whether initiated by users as
the result of a an ad-hoc search or prepared from
the system's pre-formatted report library should
provide a consistent, uniform, and organized
appearance in format, layout, size, font, etc.
whether they are printed from the system
application or printed after input to other
applications (WORD, EXCEL, etc.).
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
494
Out of the Box
Motorola
RPS012
PRINTER
SERVICES
General
The system should have the capability when
printing reports to:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
495
Out of the Box
Motorola
RPS012-1
PRINTER
SERVICES
General
determine length of report prior to printing
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
496
Out of the Box
Motorola
RPS012-2
PRINTER
SERVICES
General
select printer
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
497
Out of the Box
Motorola
RPS012-3
PRINTER
SERVICES
General
specify number of copies
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
498
Out of the Box
Motorola
RPS012-4
PRINTER
SERVICES
General
specify page ranges and multiple pages, and
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
499
Out of the Box
Motorola
RPS012-5
PRINTER
SERVICES
General
cancel print jobs and,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
500
Out of the Box
Page 31 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RPS012-6
PRINTER
SERVICES
General
have a user-definable default for printing.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
501
Out of the Box
Motorola
RPS013
PRINTER
SERVICES
General
The system should have the ability to track the
following information when a report is printed:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
502
Out of the Box
Motorola
RPS013-1
PRINTER
SERVICES
General
user ID
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
503
Out of the Box
Motorola
RPS013-2
PRINTER
SERVICES
General
number of pages printed.
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO clarified requirement is the identification of page
numbers within a report, like the standard MS Word page
number identification.
MCSO & Motorola teams agree
requirement is met out of the box
per notes in Column O.
504
Cannot Meet
Motorola
RPS013-3
PRINTER
SERVICES
General
date and time
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
505
Out of the Box
Motorola
RPS013-4
PRINTER
SERVICES
General
printer ID/name
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
506
Cannot Meet
Motorola
RFB001
FIELD BASED
REPORTING (FBR)
General
The RMS should be a user-friendly system that is
available to desktop computers and field officers
via Mobile Data Computers, and have the
capability for the County to support officers using
wireless hand-held devices. The system should
enable on-line & off line creation/submission of
field reports. It should include the ability to pre-
populate needed forms with CAD information,
allow for customizable workflow changes, and
accommodate supervisor
receipt/review/editing/approval as well as re-
routing of reports (before and after approval).
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
507
Out of the Box
Motorola
RFB002
FIELD BASED
REPORTING (FBR)
General
The offeror's FBR client should be completely
integrated with the offeror's CAD and RMS.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
508
Out of the Box
Motorola
RFB003
FIELD BASED
REPORTING (FBR)
General
Users should be able to initiate and complete all
reports and forms from:
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
509
Out of the Box
Motorola
RFB003-1
FIELD BASED
REPORTING (FBR)
General
A desktop workstation connected to the RMS via a
local or wide-area network.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
510
Out of the Box
Motorola
RFB003-2
FIELD BASED
REPORTING (FBR)
General
A mobile data computer attached to the RMS via a
wireless or cellualr connection.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
511
Out of the Box
Motorola
RFB003-3
FIELD BASED
REPORTING (FBR)
General
Any computer which supports a browser system
shall have access to the County’s local wide area
network and cellular data
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
512
Out of the Box
Motorola
RFB004
FIELD BASED
REPORTING (FBR)
General
The proposed FBR should:
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
513
Out of the Box
Motorola
RFB004-1
FIELD BASED
REPORTING (FBR)
General
Support single entry of data for all forms, reports,
and other data entry tasks.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
514
Out of the Box
Motorola
RFB004-2
FIELD BASED
REPORTING (FBR)
General
Support cut, copy, and paste functions between
applications - Mobile and FBR/RMS, and within
each individual application.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
515
Out of the Box
Motorola
RFB004-3
FIELD BASED
REPORTING (FBR)
General
Include features commonly found in word
processing software such as type ahead, spell
check, word wrap, bold, underline, tab, insert
tables and graphics, etc.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
516
Out of the Box
Motorola
RFB005
FIELD BASED
REPORTING (FBR)
General
The vendor should describe their system's
capability to copy MS WORD narratives that
include different colors, fonts, and other textual
formatting, into the FBR, while maintaining the
original source formatting.
Mandatory
Mobile Records
X
PremierOne allows for a report
template to be created that can be
used in pre-defined situations and
for pre-designated purposes (i.e.
one report for training purposes,
one report for investigation
purposes). These templates do not
include MS Word formatting
options.
Requirement states "…should describe", which Motorola
described rich text formatting capabilities. MCSO agreed
rich text format is acceptable.
MCSO & Motorola teams agree
requirement is met out of the box
per notes in Column O.
517
Cannot Meet
Motorola
RFB006
FIELD BASED
REPORTING (FBR)
General
Not have any artificial limit on the number of text
characters that can be entered into narrative
fields.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement. The current character
limit for each case report is
322,727. To quantify, that equates
to approximately 107 pages of text
allowed per report.
518
Out of the Box
Page 32 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RFB007
FIELD BASED
REPORTING (FBR)
General
Provide users with the ability to digitally capture
mug shots, pictures, audio files and other data
formats and attach them to a case record from
workstations, cellualr devices, and MDCs.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
519
Out of the Box
Motorola
RFB008
FIELD BASED
REPORTING (FBR)
General
The system should be able to accept data from
County approved and supported software
applications.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
520
Out of the Box
Motorola
RFB009
FIELD BASED
REPORTING (FBR)
General
The system should provide the ability to present
agency-defined templates of narratives and report
templates for various user-defined types of
events.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
521
Out of the Box
Motorola
RFB010
FIELD BASED
REPORTING (FBR)
General
Each authorized user should have the ability to
create and save their own report
narratives/templates to their system profile.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
522
Out of the Box
Motorola
RFB011
FIELD BASED
REPORTING (FBR)
General
The system should allow the system administrator
to remotely update with user-definable report
templates.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
523
Out of the Box
Motorola
RFB012
FIELD BASED
REPORTING (FBR)
General
The system should have the ability to receive
incident data from the CAD system and use this as
the default for report entry when a case report is
created.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
524
Out of the Box
Motorola
RFB013
FIELD BASED
REPORTING (FBR)
General
The system should have the ability to receive
information (name, address, vehicle, etc.) from
ACJIS and the RMS and transfer that information
directly into case reports, the Field Contact Card
(FI), property and evidence reports, and any other
system generated reports.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
525
Out of the Box
Motorola
RFB014
FIELD BASED
REPORTING (FBR)
General
Users should be able to begin a new case report
directly in the RMS. In this case the system will
obtain a case number from the CAD system.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
526
Out of the Box
Motorola
RFB015
FIELD BASED
REPORTING (FBR)
General
The numbering system should be designed to
verify that all cases receive a case number, and
that no case numbers are duplicated. The case
number provides a means for linking information
related to a specific event.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
527
Out of the Box
Motorola
RFB016
FIELD BASED
REPORTING (FBR)
General
Each RMS record should retain the case number
assigned by the CAD system.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
528
Out of the Box
Motorola
RFB017
FIELD BASED
REPORTING (FBR)
General
The system should have the ability to change
Incident Report numbering with the cutover to an
intelligent numbering system, building in a Julian
calendar date or similar to aid in searches in the
future. This process should also be able to clearly
identify legacy numbers from new numbers to
indicate where to find data – archive system/data
warehouse or new system.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
529
Out of the Box
Motorola
RFB018
FIELD BASED
REPORTING (FBR)
General
The system should be able to populate data fields
with the current date, and address fields with the
current County and state based on an entered zip
code.
Mandatory
Mobile Records
X
County and State are a part of the
CAD geofile. The output (Call for
Service) location data is passed to
Records, but Records does not have
direct access to the geofile for
address validation. If the specific
address information already exists
Master Locations, the user can
select the location information
without re-entering the County and
State. If the user is entering an
address that does not already exist,
the user must enter the County and
State.
530
Out of the Box
Motorola
RFB019
FIELD BASED
REPORTING (FBR)
General
The County requires that the system be initially
capable of facilitating the preparation of, and
producing all information contained in the below
reports at the desktop and MDC level:
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
531
Out of the Box
Motorola
RFB019-1
FIELD BASED
REPORTING (FBR)
General
Maricopa County Sheriffs Department's Incident
Report
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
532
Out of the Box
Motorola
RFB019-2
FIELD BASED
REPORTING (FBR)
General
Maricopa County Sheriffs Department's Field
Investigation Report
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
533
Out of the Box
Page 33 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RFB019-3
FIELD BASED
REPORTING (FBR)
General
Maricopa County Sheriffs Department's
Supplementary Interrogation Report
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
534
Out of the Box
Motorola
RFB019-4
FIELD BASED
REPORTING (FBR)
General
Maricopa County Sheriffs Department's Property
Forms/Supplemental Property Report
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
535
Out of the Box
Motorola
RFB019-5
FIELD BASED
REPORTING (FBR)
General
Traffic Statement
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
536
Out of the Box
Motorola
RFB019-6
FIELD BASED
REPORTING (FBR)
General
Pursuit Report
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
537
Out of the Box
Motorola
RFB019-7
FIELD BASED
REPORTING (FBR)
General
Blood Draw Report
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
538
Out of the Box
Motorola
RFB019-8
FIELD BASED
REPORTING (FBR)
General
Alcohol Influence Report
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
539
Out of the Box
Motorola
RFB019-9
FIELD BASED
REPORTING (FBR)
General
Property Release Authorization
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
540
Out of the Box
Motorola
RFB019-10
FIELD BASED
REPORTING (FBR)
General
Domestic Violence Supplement
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
541
Out of the Box
Motorola
RFB019-11
FIELD BASED
REPORTING (FBR)
General
Juvenile Referral
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
542
Out of the Box
Motorola
RFB019-12
FIELD BASED
REPORTING (FBR)
General
Agency Request for Scientific Examination (non-
DPS)
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
543
Out of the Box
Motorola
RFB019-13
FIELD BASED
REPORTING (FBR)
General
Arizona State Department of Transportation's
Crash Report
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
544
Out of the Box
Motorola
RFB019-14
FIELD BASED
REPORTING (FBR)
General
Photographic Film Submission Form
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
545
Out of the Box
Motorola
RFB019-15
FIELD BASED
REPORTING (FBR)
General
Use of Force Report
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
546
Out of the Box
Motorola
RFB019-16
FIELD BASED
REPORTING (FBR)
General
Property Seizure Form
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
547
Out of the Box
Motorola
RFB020
FIELD BASED
REPORTING (FBR)
General
It is expected that additional reports will be added
to the FBR in a phased implementation. The
system should also provide tools that allow the
County to create, utilize, and manage electronic
reports within the RMS that can be utilized by the
FBR. The goal is for the County to create
additional reports without vendor assistance.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement. PremierOne Records
provides the same functionality,
fields, data, and security to both
the officer in the field using a
Records Mobile Client and the
records bureau user accessing the
system through a LAN-connected
desktop computer. The PremierOne
Records Mobile Client provides a
mobile-friendly Current Activity
Dashboard which allows police
users to create new reports, view
all open work items, and mark work
items completed.
The agency can determine which
Report forms are available for the
users to complete in the Records
Mobile Client.
548
Out of the Box
Motorola
RFB021
FIELD BASED
REPORTING (FBR)
General
The proposed RMS system should minimally
support all data fields that currently appear on
County criminal offense and investigative report
forms.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
549
Out of the Box
Motorola
RFB022
FIELD BASED
REPORTING (FBR)
General
When the user prepares a report and assigns a
classification, the system should inform the user of
all related reports that should be completed in
association with the event classification. In this
example, all data entered into the original form
should be available to and automatically populate
any subsequent related forms that are completed.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
550
Out of the Box
Page 34 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RFB023
FIELD BASED
REPORTING (FBR)
General
The system should support in-vehicle printing.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
551
Out of the Box
Motorola
RFB024
FIELD BASED
REPORTING (FBR)
General
The system should support e-mailing
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
552
Out of the Box
Motorola
RFB025
FIELD BASED
REPORTING (FBR)
General
The system should provide a means of storing the
electronic signature of each employee so that their
signature appears on the report.
Mandatory
Mobile Records
X
This function is not currently
available.
MCSO team stated this is not
required to be met. It was
explained during the demo that
this is not applicable due to
security issues.
553
Cannot Meet
Motorola
RFB026
FIELD BASED
REPORTING (FBR)
User Interface
Default Values – Fields must be able to be set to
incorporate specified default values. For example,
a common value can appear in a drop-down list
such as the state in which the agency is located.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
554
Out of the Box
Motorola
RFB027
FIELD BASED
REPORTING (FBR)
User Interface
Itemized Lists – Dropdown lists must be able to be
modified to contain local agency requirements.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
555
Out of the Box
Motorola
RFB028
FIELD BASED
REPORTING (FBR)
User Interface
Required Fields – Fields must be able to be set to a
required status. Current required fields can be
turned off.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
556
Out of the Box
Motorola
RFB029
FIELD BASED
REPORTING (FBR)
User Interface
The system shall provide the capability for
redundant data storage.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
557
Out of the Box
Motorola
RFB030
FIELD BASED
REPORTING (FBR)
User Interface
The system will provide follow-up case report data
entry to leverage data from the previous report,
and to eliminate duplicate date entry.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
558
Out of the Box
Motorola
RFB031
FIELD BASED
REPORTING (FBR)
User Interface
The system shall support integration with CAD
Calls for Service data, allowing data to be
seamlessly transferred into a given report.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
559
Out of the Box
Motorola
RFB032
FIELD BASED
REPORTING (FBR)
User Interface
The system shall provide the capability for GUI
similar to the RMS system for data entry and
validation.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
560
Out of the Box
Motorola
RFB033
FIELD BASED
REPORTING (FBR)
User Interface
The system shall provide the capability for
UCR/NIBRS data validation in connected mode.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
561
Out of the Box
Motorola
RFB034
FIELD BASED
REPORTING (FBR)
User Interface
Date formats – Date formatting within fields must
be able to be set to customer preference (based
on supported formatting).
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
562
Out of the Box
Motorola
RFB035
FIELD BASED
REPORTING (FBR)
User Interface
Managed itemized lists – The system shall allow
system administrators to change, add, and delete
values in itemized lists containing crime statutes
and local codes; it shall also allow mobile users to
conduct queries of each element.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
563
Out of the Box
Motorola
RFB036
FIELD BASED
REPORTING (FBR)
User Interface
The system shall provide the capability for
validation errors to be displayed to the user
immediately.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
564
Out of the Box
Motorola
RFB037
FIELD BASED
REPORTING (FBR)
User Interface
Report names – The system must be able to
change report names (titles) to reflect local agency
names.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
565
Out of the Box
Motorola
RFB038
FIELD BASED
REPORTING (FBR)
User Interface
Auto-fill from system data – The system must be
able to further automate the report completion
process by pre-filling report fields with known
system data.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
566
Out of the Box
Motorola
RFB039
FIELD BASED
REPORTING (FBR)
User Interface
Linking data – The system shall populate duplicate
data within report pages to eliminate additional
typing and promote more accurate data.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
567
Out of the Box
Motorola
RFB040
FIELD BASED
REPORTING (FBR)
User Interface
The system shall provide the capability for
unlimited narrative entry.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement. The current character
limit for each case report is
322,727. To quantify, that equates
to approximately 107 pages of text
allowed per report.
568
Out of the Box
Motorola
RFB041
FIELD BASED
REPORTING (FBR)
User Interface
The system shall provide the capability for
unfinished documents to be saved in draft mode.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
569
Out of the Box
Motorola
RFB042
FIELD BASED
REPORTING (FBR)
User Interface
The system shall provide the capability to auto
save all documents. In the event of a power
outage, documents shall be able to be recovered.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
570
Out of the Box
Page 35 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RFB043
FIELD BASED
REPORTING (FBR)
User Interface
The system will provide for a simplified, event
specific data entry process. Only those fields
required for a specific event will be displayed for
the user to enter data. (aka: Dynamic Data
Collection)
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
571
Out of the Box
Motorola
RFB044
FIELD BASED
REPORTING (FBR)
User Interface
Data validation – The system shall allow report
fields to be validated against specified criteria
prior to report submission.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
572
Out of the Box
Motorola
RFB045
FIELD BASED
REPORTING (FBR)
User Interface
The user interface shall be in a GUI format that
conforms to the Microsoft standard by utilizing
both menus and shortcut keys for navigation.
Note: handled via tabs, drop-down menus, etc.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
573
Out of the Box
Motorola
RFB046
FIELD BASED
REPORTING (FBR)
User Interface
Workflow – The system shall allow your agency to
define report submission flows supporting your
specific review and approval process.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
574
Out of the Box
Motorola
RFB047
FIELD BASED
REPORTING (FBR)
User Interface
Data calculation – The system shall allow an
agency to have specified fields configured within
the application to perform basic calculations such
as property totals or age based on DOB.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
575
Out of the Box
Motorola
RFB048
FIELD BASED
REPORTING (FBR)
User Interface
Prompt to save – The system shall prompt the
user to save upon exiting any report such as a field
interview, citation, case report, contacts, etc.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
576
Out of the Box
Motorola
RFB049
FIELD BASED
REPORTING (FBR)
User Interface
The system must provide a 'night mode" for low
light situations.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
577
Out of the Box
Motorola
RFB050
FIELD BASED
REPORTING (FBR)
User Interface
The Field-Based Reporting system shall support
geographic designators such as zone, district, area,
agency, reporting district, and map references.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
578
Out of the Box
Motorola
RFB051
FIELD BASED
REPORTING (FBR)
User Interface
Users shall be able to search the database using
full or partial data strings.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
579
Out of the Box
Motorola
RFB052
FIELD BASED
REPORTING (FBR)
User Interface
Formatted screens shall be used for initiating
database queries.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
580
Out of the Box
Motorola
RFB053
FIELD BASED
REPORTING (FBR)
User Interface
The system shall have an on-line help function that
has the ability to include instructions from user
documentation.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
581
Out of the Box
Motorola
RFB054
FIELD BASED
REPORTING (FBR)
User Interface
The system must have a status bar indicating
connectivity and items to be uploaded.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
582
Out of the Box
Motorola
RFB055
FIELD BASED
REPORTING (FBR)
User Interface
The system must include a rapid data entry user
interface;
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
583
Out of the Box
Motorola
RFB056
FIELD BASED
REPORTING (FBR)
User Interface
a. The data entry interface shall allow the data
entry operator to enter information rapidly in a
“heads-down” mode.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
584
Out of the Box
Motorola
RFB057
FIELD BASED
REPORTING (FBR)
User Interface
b. With this interface the primary means of entry
shall be the keyboard.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
585
Out of the Box
Motorola
RFB058
FIELD BASED
REPORTING (FBR)
User Interface
The system shall allow each user to determine
whether their field format shall be displayed in a
left to right manner or as a listing of fields in a
column to promote rapid data entry.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
586
Out of the Box
Motorola
RFB059
FIELD BASED
REPORTING (FBR)
Citations
The system shall allow users to have the ability to
save citations in the RMS system without user
intervention.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
587
Out of the Box
Motorola
RFB060
FIELD BASED
REPORTING (FBR)
Citations
The system shall allow users to have the ability to
review citations.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
588
Out of the Box
Motorola
RFB061
FIELD BASED
REPORTING (FBR)
Citations
The system shall allow users to have the ability to
edit citations.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
589
Out of the Box
Motorola
RFB062
FIELD BASED
REPORTING (FBR)
Citations
The system shall allow users to have the ability to
retrieve citations.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
590
Out of the Box
Motorola
RFB063
FIELD BASED
REPORTING (FBR)
Citations
The system shall allow users to have the ability to
add citations.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
591
Out of the Box
Motorola
RFB064
FIELD BASED
REPORTING (FBR)
Field Interviews
The system shall allow users to have the ability to
save field interviews in the RMS system without
user intervention.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
592
Out of the Box
Page 36 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RFB065
FIELD BASED
REPORTING (FBR)
Field Interviews
Users shall have the ability to review field
interviews.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
593
Out of the Box
Motorola
RFB066
FIELD BASED
REPORTING (FBR)
Field Interviews
Users shall have the ability to edit field interviews. Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
594
Out of the Box
Motorola
RFB067
FIELD BASED
REPORTING (FBR)
Field Interviews
The system will enable users to retrieve a field
interview file.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
595
Out of the Box
Motorola
RFB068
FIELD BASED
REPORTING (FBR)
Field Interviews
The system shall provide a data entry point for the
following information: contact and vehicle
information.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
596
Out of the Box
Motorola
RFB069
FIELD BASED
REPORTING (FBR)
Field Interviews
Users shall have the ability to add field interviews. Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
597
Out of the Box
Motorola
RFB070
FIELD BASED
REPORTING (FBR)
Master Index
The system shall allow a search for a Person based
on first name, last name, DOB, SSN, DLN, sex, race
and person number.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
598
Out of the Box
Motorola
RFB071
FIELD BASED
REPORTING (FBR)
Master Index
The system shall allow a search for location or
entity based on entity name, address, city, state
and zip.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
599
Out of the Box
Motorola
RFB072
FIELD BASED
REPORTING (FBR)
Master Index
The system shall allow a search for property based
on property number, IBR code, status,
manufacturer, model, vehicle plate, serial number,
state, color and description.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
600
Out of the Box
Motorola
RFB073
FIELD BASED
REPORTING (FBR)
Master Index
The system shall allow a search for cases or
incidents based on case number, incident number,
date range, etc.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
601
Out of the Box
Motorola
RFB074
FIELD BASED
REPORTING (FBR)
Supervisor Review
and Approval
The system shall allow a supervisor to retrieve a
case for review and approval.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
602
Out of the Box
Motorola
RFB075
FIELD BASED
REPORTING (FBR)
Supervisor Review
and Approval
The system shall allow a supervisor to configure
the approval process.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
603
Out of the Box
Motorola
RFB076
FIELD BASED
REPORTING (FBR)
Supervisor Review
and Approval
Workflow – A configurable supervisor approval
process must be allowed for each report type.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
604
Out of the Box
Motorola
RFB077
FIELD BASED
REPORTING (FBR)
Supervisor Review
and Approval
The system shall allow for establishing supervisory
reporting groups enabling management of the
review process.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
605
Out of the Box
Motorola
RFB078
FIELD BASED
REPORTING (FBR)
Case Files/ Reports
Users shall have the ability to edit a case.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
606
Out of the Box
Motorola
RFB079
FIELD BASED
REPORTING (FBR)
Case Files/ Reports
They system shall support inclusion of documents,
images, video and audio recordings in a case
folder.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
607
Out of the Box
Motorola
RFB080
FIELD BASED
REPORTING (FBR)
Case Files/ Reports
The system shall provide a data entry point for the
following information: incident, victim, and
business information; offense information;
method of operation; investigative information;
person’s summary; vehicle and property
information; and narrative.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
608
Out of the Box
Motorola
RFB081
FIELD BASED
REPORTING (FBR)
Case Files/ Reports
Records created in field based reporting should
immediately be available in the RMS system
without requiring user intervention.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
609
Out of the Box
Motorola
RFB082
FIELD BASED
REPORTING (FBR)
Case Files/ Reports
Users shall have the ability to review a case.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
610
Out of the Box
Motorola
RFB083
FIELD BASED
REPORTING (FBR)
Case Files/ Reports
The system will allow a user to retrieve a case file
after initial submission but before it has been
approved for modification or correction.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
611
Out of the Box
Motorola
RFB084
FIELD BASED
REPORTING (FBR)
Case Files/ Reports
Users shall have the ability to add a case.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
612
Out of the Box
Motorola
RFB085
FIELD BASED
REPORTING (FBR)
General
On-line help must be available from any screen.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
613
Out of the Box
Motorola
RFB086
FIELD BASED
REPORTING (FBR)
General
The system shall provide the capability for data
encryption and compression to enable data
transfer across wireless or wire line systems.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
614
Out of the Box
Motorola
RFB087
FIELD BASED
REPORTING (FBR)
General
The system must provide dynamic “to-do” lists,
which highlight issues requiring resolution to
maintain validation or to enter missing or required
data.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
615
Out of the Box
Page 37 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RFB088
FIELD BASED
REPORTING (FBR)
General
Both ad hoc and preformatted on-line report
writing must be supported, with automatic
workflow for approvals and appropriate follow-up.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
616
Out of the Box
Motorola
RFB089
FIELD BASED
REPORTING (FBR)
General
The system must provide for common system
administration functions consistent with the RMS
(security, workflow, code tables, etc).
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
617
Out of the Box
Motorola
RFB090
FIELD BASED
REPORTING (FBR)
General
Support for version-less updates (updates sent
wirelessly) must be made using Microsoft update
service.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
618
Out of the Box
Motorola
RFB091
FIELD BASED
REPORTING (FBR)
General
Officers in the field must be able to quickly and
easily fill out and submit reports directly from
within their vehicles.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
619
Out of the Box
Motorola
RFB092
FIELD BASED
REPORTING (FBR)
General
The reports must be wirelessly submitted to
supervisors.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
620
Out of the Box
Motorola
RFB093
FIELD BASED
REPORTING (FBR)
General
Agency configured workflows must begin in the
mobile environment. The system should not
require a separate workflow for the FBR system.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
621
Out of the Box
Motorola
RFB094
FIELD BASED
REPORTING (FBR)
General
All auditing of records creation, editing or printing
must begin and be maintained in the records
mobile client.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
622
Out of the Box
Motorola
RFB095
FIELD BASED
REPORTING (FBR)
General
Field reports shall be able to be routed an
unlimited number of times for review.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
623
Out of the Box
Motorola
RFB096
FIELD BASED
REPORTING (FBR)
General
The routing process must be able to be
determined by the agency.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
624
Out of the Box
Motorola
RFB097
FIELD BASED
REPORTING (FBR)
General
The reports from the field must be able to be
utilized within the RMS.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
625
Out of the Box
Motorola
RFB098
FIELD BASED
REPORTING (FBR)
General
The option to leave ownership of the report with
the originating officer, until the report is approved,
must be provided.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
626
Out of the Box
Motorola
RFB099
FIELD BASED
REPORTING (FBR)
General
Formatted screens must be available for initiating
database inquiries.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
627
Out of the Box
Motorola
RFB100
FIELD BASED
REPORTING (FBR)
General
The system must provide the ability to re-use
Incident data from a Mobile CAD system to
populate information such as location, call times,
incident and case numbers, etc. in any module in
the records system as selected by the agency
relative to the rights of the user.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
628
Out of the Box
Motorola
RFB101
FIELD BASED
REPORTING (FBR)
General
The system shall have the ability to send messages
and tasks to a person, group, organization,
supervisor or group of supervisors, or down the
chain of command.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
629
Out of the Box
Motorola
RFB102
FIELD BASED
REPORTING (FBR)
General
The system shall have the ability to send any
document to a person, group, organization,
supervisor or group of supervisors, or down the
chain of command.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
630
Out of the Box
Motorola
RFB103
FIELD BASED
REPORTING (FBR)
General
The system shall allow the user to check out a case
investigation including all attachments to the field
based reporting system for offline processing.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
631
Out of the Box
Motorola
RFB104
FIELD BASED
REPORTING (FBR)
General
The system must allow IBR/UCR validation to
occur during data entry on a field report in
connected mode.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
632
Out of the Box
Motorola
RFB105
FIELD BASED
REPORTING (FBR)
General
The system must automatically make any module
available in the mobile environment based on user
security including new modules created by the
agency.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
633
Out of the Box
Motorola
RFB106
FIELD BASED
REPORTING (FBR)
General
All security rights must be enforced by the mobile
client regardless of network connectivity.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
634
Out of the Box
Motorola
RFB107
FIELD BASED
REPORTING (FBR)
General
The system must provide the ability to re-use
Incident data from a mobile CAD system without
network connectivity for the Records mobile
client.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
635
Out of the Box
Motorola
RFB108
FIELD BASED
REPORTING (FBR)
General
The system shall provide the capability that once
a report is approved and locked, only the
document owner may revise it.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
636
Out of the Box
Motorola
RFB109
FIELD BASED
REPORTING (FBR)
General
The system must provide the ability to re-use
query data including people, property and vehicle
information from a mobile CAD system in any
module in the Records system.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
637
Out of the Box
Page 38 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RFB110
FIELD BASED
REPORTING (FBR)
General
Field reports must import CAD incident and State
query results that intelligently populate into key
fields to ensure speed of creation and accuracy of
data entry.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
638
Out of the Box
Motorola
RFB111
FIELD BASED
REPORTING (FBR)
General
Users shall be able to create supplemental forms
and reports.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
639
Out of the Box
Motorola
RFB112
FIELD BASED
REPORTING (FBR)
General
The system requires that all items added to the
case folder must go through an automated
approval process.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
640
Out of the Box
Motorola
RFB113
FIELD BASED
REPORTING (FBR)
General
The RMS shall allow for other documents to be
added to the case folder even after approval.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
641
Out of the Box
Motorola
RFB114
FIELD BASED
REPORTING (FBR)
General
If entered directly into the law records system,
other authorized users shall have the ability to
alter the report.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
642
Out of the Box
Motorola
RFB115
FIELD BASED
REPORTING (FBR)
General
The system must allow the agency to modify the
mapping of the incident and query data in any
module, including those created by the agency.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
643
Out of the Box
Motorola
RFB116
FIELD BASED
REPORTING (FBR)
General
The system must allow all records to be
transferred via a removable device such as a
thumb drive.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
644
Out of the Box
Motorola
RFB117
FIELD BASED
REPORTING (FBR)
General
The system must use an industry standard SQL
structure accessible by ad hoc reporting and query
tools.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
645
Out of the Box
Motorola
RFB118
FIELD BASED
REPORTING (FBR)
General
The system shall enable only the record owner to
modify a document if approval has been
rescinded.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
646
Out of the Box
Motorola
RFB119
FIELD BASED
REPORTING (FBR)
General
The system must be able to operate over a
wireless network, with limited or no connectivity.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
647
Out of the Box
Motorola
RFB120
FIELD BASED
REPORTING (FBR)
General
The system must allow the user to take the client
off-line to reduce network impact on other higher
priority applications.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
648
Out of the Box
Motorola
RFB121
FIELD BASED
REPORTING (FBR)
General
The system must be able to be configured for
background uploading of reports to improve
usability in low bandwidth areas.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
649
Out of the Box
Motorola
RFB122
FIELD BASED
REPORTING (FBR)
General
The system must provide a separate upload
channel for images and other digital attachments
to allow the agency to specify the network to use
for attachments.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
650
Out of the Box
Motorola
RFB123
FIELD BASED
REPORTING (FBR)
General
The system must add a non-repudiation seal to all
new records even while working in a disconnected
mode.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
651
Out of the Box
Motorola
RFB124
FIELD BASED
REPORTING (FBR)
General
The mobile client must be auto-updating using
Windows update service.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
652
Out of the Box
Motorola
RFB125
FIELD BASED
REPORTING (FBR)
General
The system must be based on a Windows graphical
user interface (GUI).
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
653
Out of the Box
Motorola
RFB126
FIELD BASED
REPORTING (FBR)
General
The mobile client update service should notify the
user if an application restart is necessary and allow
the user to delay the restart.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
654
Out of the Box
Motorola
RFB127
FIELD BASED
REPORTING (FBR)
General
The system must provide for a full install or an
update based on the currently installed version.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
655
Out of the Box
Motorola
RFB128
FIELD BASED
REPORTING (FBR)
General
The system must allow a record to be saved as a
draft even if data entered in the field does not
conform to the data type. For example, allow a
name to be entered into a telephone number field.
Mandatory
Mobile Records
X
If the pre-determined data type is
correct, incorrect information may
be saved in a draft copy. The
example given of saving a name in a
phone number field is not possible
in PremierOne.
This is a duplicate with RGD037. RGD037 was agreed that
it is met out of the box.
MCSO & Motorola teams agree
requirement is met out of the box
per notes in Column O.
656
Cannot Meet
Motorola
RFB129
FIELD BASED
REPORTING (FBR)
General
The system must run in a Windows 10/11
environments.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
657
Out of the Box
Motorola
RFB130
FIELD BASED
REPORTING (FBR)
General
Any local storage of data must be in a relational
database such as SQL Express.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
658
Out of the Box
Motorola
RFB131
FIELD BASED
REPORTING (FBR)
General
The mobile client update service must not impact
the performance of the user operations and
leverage unused bandwidth.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
659
Out of the Box
Motorola
RFB132
FIELD BASED
REPORTING (FBR)
General
The system will enable users to work in both a
connected and disconnected mode.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
660
Out of the Box
Page 39 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RFB133
FIELD BASED
REPORTING (FBR)
Command Line
The command line must allow a user to navigate
to a specific module with a single command.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
661
Out of the Box
Motorola
RFB134
FIELD BASED
REPORTING (FBR)
Command Line
The command line must allow an existing record
to be edited with a single command and without
requiring the user to navigate to the module.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
662
Out of the Box
Motorola
RFB135
FIELD BASED
REPORTING (FBR)
Command Line
The command line must be controlled by security
including security settings that have been
manually overridden or set by the system
workflow.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
663
Out of the Box
Motorola
RFB136
FIELD BASED
REPORTING (FBR)
Command Line
The command line must support bar code readers
to execute any command. For example, a case
report could be printed with a bar code that would
allow a user to open the report by scanning a bar
code into the command line.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
664
Out of the Box
Motorola
RFB137
FIELD BASED
REPORTING (FBR)
Command Line
The command line must allow a user to navigate
to the main home screen with a single command.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
665
Out of the Box
Motorola
RFB138
FIELD BASED
REPORTING (FBR)
Command Line
The command line should be separate from the
main application window to allow it to remain
available if the application is minimized.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
666
Out of the Box
Motorola
RFB139
FIELD BASED
REPORTING (FBR)
Command Line
The command line should auto-complete
commands to reduce keystrokes required.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
667
Out of the Box
Motorola
RFB140
FIELD BASED
REPORTING (FBR)
Command Line
The system shall utilize an "intelligent command
line" such that it will prompt the user for valid
formatting of the command.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
668
Out of the Box
Motorola
RFB141
FIELD BASED
REPORTING (FBR)
Command Line
The user shall be able to enter a command on the
command line without disturbing operations in the
work areas.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
669
Out of the Box
Motorola
RFB142
FIELD BASED
REPORTING (FBR)
Command Line
The command line must allow a new record to be
created with a single command and without
requiring the user to navigate to the module.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
670
Out of the Box
Motorola
RFB143
FIELD BASED
REPORTING (FBR)
Command Line
The command line must be available in both the
desktop and mobile (FBR) clients.
Mandatory
Mobile Records
X
PremierOne complies with the
functionality as described in the
requirement.
671
Out of the Box
Motorola
RCR001
CASE REPORT
PROCESSING
General
The system should include a configuration table
which allows the application administrator or
authorized user to determine the routing of case
reports to named persons, position titles, or
groups, based on the:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
672
Out of the Box
Motorola
RCR001-1
CASE REPORT
PROCESSING
General
offense type,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
673
Out of the Box
Motorola
RCR001-2
CASE REPORT
PROCESSING
General
location of the offense, and
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO clarified this requirement is connected to RCR001.
Motorola clarified that routing of case reports can be
workflowed by beat, sector, grid to route reports for
approval, notifications, notification assignment.
MCSO requesting use of call for service type code (offense
type / radio code) for routing of case reports. Motorola
stated this is possible.
MCSO & Motorola teams agree
requirement is met out of the box
per notes in Column O.
674
Cannot Meet
Motorola
RCR001-3
CASE REPORT
PROCESSING
General
time and date of the offense.
Mandatory
Records
X
PremierOne does not have this
functionality.
Motorola clarification that routing of case report cannot
be accomplished by time and date of the offense.
MCSO & Motorola teams agree
requirement is NOT MET per
notes in Column O.
675
Cannot Meet
Motorola
RCR002
CASE REPORT
PROCESSING
General
The system should check each completed form to
ensure:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
676
Out of the Box
Motorola
RCR002-1
CASE REPORT
PROCESSING
General
that the user has entered a value in each
mandatory field, and
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
677
Out of the Box
Motorola
RCR002-2
CASE REPORT
PROCESSING
General
that entries in value restricted fields match one of
the acceptable values for that field. Users have
requested an "OR Wizard" concept that would
prompt for required fields based upon the type of
crime being reported.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
678
Out of the Box
Motorola
RCR003
CASE REPORT
PROCESSING
General
If required fields have not been completed, the
system should denote the missing or incorrect
entries in a distinctive manner.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
679
Out of the Box
Page 40 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RCR004
CASE REPORT
PROCESSING
General
The system should provide a command or function
for auditing (UCR edits, etc.) the report at any
time.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
680
Out of the Box
Motorola
RCR005
CASE REPORT
PROCESSING
General
The system should allow a user to conditionally
save a partial report or one with errors, but the
system will notify the user that required fields
have not been completed or the report contains
errors.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
681
Out of the Box
Motorola
RCR006
CASE REPORT
PROCESSING
General
The system should be capable of being configured
to ensure that a partial report or one with errors
cannot be distributed.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
682
Out of the Box
Motorola
RCR007
CASE REPORT
PROCESSING
General
The system should allow the report to be edited by
the user and saved in “conditional” mode as
necessary.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
683
Out of the Box
Motorola
RCR008
CASE REPORT
PROCESSING
General
The conditional report should be saved on the
server and the local MDC/Desktop.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
684
Out of the Box
Motorola
RCR009
CASE REPORT
PROCESSING
General
The reviewer should have the capability to return
the conditional report to the original user with
comments attached utilizing a notepad function as
described below.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
685
Out of the Box
Motorola
RCR010
CASE REPORT
PROCESSING
General
The system should allow the copying or moving of
data from one field to another without reentry.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
686
Out of the Box
Motorola
RCR011
CASE REPORT
PROCESSING
General
The routing of reports for review and approval
should occur entirely within the vendor's system
and not require the use of an external e-mail or
similar system.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
687
Out of the Box
Motorola
RCR012
CASE REPORT
PROCESSING
General
When all required fields on a report have been
completed the system should allow the reporting
officer to either route the report to a
predetermined supervisor or to a named
supervisor or group mailbox for review.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
688
Out of the Box
Motorola
RCR013
CASE REPORT
PROCESSING
General
In the event that supervisory review requires the
reporting officer to add additional information or
make changes to the report, the reviewing official
should have the ability to return the report to the
originating officer.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
689
Out of the Box
Motorola
RCR014
CASE REPORT
PROCESSING
General
The reviewing official should be able to utilize a
notepad or other similar system to attach notes to
the report that is returned.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
690
Out of the Box
Motorola
RCR015
CASE REPORT
PROCESSING
General
The County is interested in reviewing alternative
options for the supervisory review process that
allows reviewers to easily reference their
supervisory notes and/or edits to specific sections
of the report. The purpose of this functionality is
to enhance the ease of review by the both the
reviewer and the reports author.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. PremierOne Records
includes a robust workflow feature
that enables each agency to create
multiple workflows to facilitate a
review and approval process of
reports, citations, and other
documents to meet the specific
needs and current business
practices of each agency. Workflow
can be configured to route reports
automatically or manually.
Workflow can also be configured
to:
ͻ>ŽĐŬĂĚŽĐƵŵĞŶƚĂŐĂŝŶƐƚ
further modification
ͻWƌŽǀŝĚĞĂŶĂƉƉƌŽǀĂů
mechanism of a document
ͻZŽƵƚĞĚŽĐƵŵĞŶƚƐƚŽ
individuals or organizations
ͻZĞƚƵƌŶĂĨĂŝůĞĚĚŽĐƵŵĞŶƚƚŽĂ
predetermined level for correction
or additional work before being
resubmitted for approval
ͻŽŶĨŝŐƵƌĞƐĞĐƵƌŝƚLJĂƚĂƐƚĂŐĞ
that reassigns rights to individuals,
i
i
i
691
Out of the Box
Motorola
RCR016
CASE REPORT
PROCESSING
General
The system should be configurable to allow the
reviewing supervisor to make corrections/changes
to the report, if the County so desires.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
692
Out of the Box
Motorola
RCR017
CASE REPORT
PROCESSING
General
The originating officer should be able to view the
reviewing official’s notes and the returned report
on the screen simultaneously.
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met. Current
workflow is sufficient.
693
Cannot Meet
Page 41 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RCR018
CASE REPORT
PROCESSING
General
The system should maintain an audit trail of all
reports produced which captures all times and
dates related to report completion, report
submission, and any changes that are made to the
report as a result of the review and approval
process.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
694
Out of the Box
Motorola
RCR019
CASE REPORT
PROCESSING
General
The system should maintain a complete audit trail
of all changes to database records or forms
changed, including the following information:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
695
Out of the Box
Motorola
RCR019-1
CASE REPORT
PROCESSING
General
identification of the user making the change,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
696
Out of the Box
Motorola
RCR019-2
CASE REPORT
PROCESSING
General
identification of the record being changed,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
697
Out of the Box
Motorola
RCR019-3
CASE REPORT
PROCESSING
General
the old and new value of each field changed, and
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
698
Out of the Box
Motorola
RCR019-4
CASE REPORT
PROCESSING
General
the date, time and location from which the
changes were made.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
699
Out of the Box
Motorola
RCR020
CASE REPORT
PROCESSING
General
The system should be configurable to allow agency-
definable report type(s) to be reviewed for quality
control.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
700
Out of the Box
Motorola
RCR021
CASE REPORT
PROCESSING
General
The system should be configurable to allow the
system administrator to define which users and/or
user groups can be granted permission to review
reports for quality control.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
701
Out of the Box
Motorola
RCR022
CASE REPORT
PROCESSING
General
After a report is approved by a supervisor and
posted to the RMS, the report and all information
contained in the report should be available to all
authorized RMS users.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
702
Out of the Box
Motorola
RCR023
CASE REPORT
PROCESSING
General
Unapproved reports should be prominently
marked as such whether displayed on-screen or
printed.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Documents in a draft
status have not met the minimum
requirements for submission to a
supervisor. These would be working
documents that are marked as draft
in the application and show a
watermark when printed. Public
documents are finalized documents
that would need special approval to
change, but are viewable to the
other users of the system.
703
Out of the Box
Motorola
RCR024
CASE REPORT
PROCESSING
General
The system should allow the system administrator
or other authorized user to determine which
reports or forms will be reviewed and approved by
a supervisor prior to being committed to the
database.
Mandatory
Records
X
All PremierOne Records data is
housed in the same repository. All
records created in PremierOne
Records are committed to the
central database regardless of
approval status.
MCSO clarifying the requirement being that once a
report/form is reviewed and approved that version is no
longer editable. Motorola explained that the agency can
configure at what point a document is locked for editing.
One exception, auto lock done for case report after going
through mark for submission stage to state.
MCSO & Motorola teams agree
requirement is met out of the box
per notes in Column O.
704
Cannot Meet
Motorola
RCR025
CASE REPORT
PROCESSING
General
The system administrator should be able to set
parameters for bypassing the Records Division
approval process based on case report event type,
possible Master Index errors, and duplicate
entries.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
705
Out of the Box
Motorola
RCR026
CASE REPORT
PROCESSING
General
The system should allow supervisor approved
reports to be available for distribution, but the
reports should be flagged as "pending" until such
time as they are approved by Records Section QA
Clerks.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
706
Out of the Box
Motorola
RCR027
CASE REPORT
PROCESSING
General
The system administrator should be able to set
parameters to delineate which portions of any
report Records Section clerks are permitted to
modify.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
707
Out of the Box
Motorola
RCR028
CASE REPORT
PROCESSING
General
The system should be capable of being configured
to ensure that corrections by reporting officers to
approved reports are made using a Supplemental
Report.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
708
Out of the Box
Motorola
RCR029
CASE REPORT
PROCESSING
General
Certain report types (i.e. Use of Force, Dog Bite
and Pursuit) should automatically send a notice to
Internal Affairs.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
709
Out of the Box
Page 42 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RCR030
CASE REPORT
PROCESSING
General
The ability to expunge or seal records based of a
Courts ruling is REQUIRED (to include Incident
Reports, Arrest Reports, Booking Information,
etc).
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
710
Out of the Box
Motorola
RCR031
CASE REPORT
PROCESSING
General
The system shall allow for deputies to enter
supplemental reports under a case report number,
without the primary call for service being given
disposition or the original report being entered
into RMS.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Case supplements can
be entered into the system prior to
completion of the original case
report.
711
Out of the Box
Motorola
RCR032
CASE REPORT
PROCESSING
General
The system shall allow for the "locking" of reports
to approved individuals only, for high profile and
other sensitive cases.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
712
Out of the Box
Motorola
RT001
TRAFFIC
General
The system should provide the capability to enter
and manage all traffic-related reports and traffic
citation information. Requirements for traffic
analysis include the recording and correlation of
crash reports and enforcement activity. Data
collected throughout the County may affect road
upgrades and thoroughfare modifications. The
system will also provide standard and agency-
defined traffic enforcement analysis related to
moving citations, traffic arrests by location, and
other similar criteria.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
713
Out of the Box
Motorola
RT002
TRAFFIC
General
The system should have the ability to:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
714
Out of the Box
Motorola
RT003
TRAFFIC
General
Correlate traffic crashes with specific geographical
locations (e.g. street intersections, mid-block)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
715
Out of the Box
Motorola
RT003-1
TRAFFIC
General
Draw crash diagrams
Mandatory
Records
X
PremierOne does not have crash
diagramming. A third party
application would need to be used
to diagram the crash then attach to
the crash report.
MCSO team stated this is not
required to be met. Other
software is used to view/draw
crash diagrams.
716
Cannot Meet
Motorola
RT003-2
TRAFFIC
General
Generate Traffic Crash Reports by:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
717
Out of the Box
Motorola
RT003-3
TRAFFIC
General
Time and day of week
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
718
Out of the Box
Motorola
RT003-4
TRAFFIC
General
Date range
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
719
Out of the Box
Motorola
RT003-5
TRAFFIC
General
Location (Location includes: 1) all parts of a
primary road, including intersections which may
not be part of the primary road), 2) private
property, 3) parking lots, 4) service roads, 5) mid-
blocks, 6) intersections, address range, hundred
block, etc.)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
720
Out of the Box
Motorola
RT003-6
TRAFFIC
General
Officer
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
721
Out of the Box
Motorola
RT003-7
TRAFFIC
General
Generate a High Crash Locations Report, including
but not limited to:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
722
Out of the Box
Motorola
RT003-8
TRAFFIC
General
Mid block
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
723
Out of the Box
Motorola
RT003-9
TRAFFIC
General
Intersections
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
724
Out of the Box
Motorola
RT003-10
TRAFFIC
General
Distance from intersection
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
725
Out of the Box
Motorola
RT003-11
TRAFFIC
General
Patrol Area
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
726
Out of the Box
Motorola
RT003-12
TRAFFIC
General
District
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
727
Out of the Box
Motorola
RT003-13
TRAFFIC
General
Sub-Census
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
728
Out of the Box
Motorola
RT003-14
TRAFFIC
General
Generate user-definable monthly report of
operations:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
729
Out of the Box
Page 43 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RT003-15
TRAFFIC
General
Total traffic crashes
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
730
Out of the Box
Motorola
RT003-16
TRAFFIC
General
Traffic crashes by category
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
731
Out of the Box
Motorola
RT003-17
TRAFFIC
General
Fatality crashes
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
732
Out of the Box
Motorola
RT003-18
TRAFFIC
General
Number of persons killed
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
733
Out of the Box
Motorola
RT003-19
TRAFFIC
General
Injury crashes
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
734
Out of the Box
Motorola
RT003-20
TRAFFIC
General
Number of persons injured
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
735
Out of the Box
Motorola
RT003-21
TRAFFIC
General
Non-injury crashes
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
736
Out of the Box
Motorola
RT003-22
TRAFFIC
General
Crashes w/ DWI
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
737
Out of the Box
Motorola
RT003-23
TRAFFIC
General
Crashes w/ bicycle
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
738
Out of the Box
Motorola
RT003-24
TRAFFIC
General
Fatal
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
739
Out of the Box
Motorola
RT003-25
TRAFFIC
General
Injury
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
740
Out of the Box
Motorola
RT003-26
TRAFFIC
General
Non-injury
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
741
Out of the Box
Motorola
RT003-27
TRAFFIC
General
Crashes w/ pedestrian
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
742
Out of the Box
Motorola
RT003-28
TRAFFIC
General
Fatal
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
743
Out of the Box
Motorola
RT003-29
TRAFFIC
General
Injury
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
744
Out of the Box
Motorola
RT003-30
TRAFFIC
General
Non-injury
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
745
Out of the Box
Motorola
RT003-31
TRAFFIC
General
By use-definable date ranges
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
746
Out of the Box
Motorola
RT003-32
TRAFFIC
General
By user-definable driver/passenger/pedestrian age
range
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
747
Out of the Box
Motorola
RT003-33
TRAFFIC
General
By all other combination of user-definable data
elements on the FR 300
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
748
Out of the Box
Motorola
RT003-34
TRAFFIC
General
Total calls for service including traffic crashes
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
749
Out of the Box
Motorola
RT003-35
TRAFFIC
General
Citations issued by category, charge, and officer
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
750
Out of the Box
Motorola
RT003-36
TRAFFIC
General
Total citations issued (and by location, date and
time range, etc.)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
751
Out of the Box
Page 44 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RT004
TRAFFIC
General
Traffic enforcement duties include conducting
overweight/unsafe vehicle inspections, DUI
enforcement, accident investigations, issuing
traffic citations etc. These duties, especially DUI
enforcement, require the completion of numerous
different forms, many of which contain duplicate
information. The department wants a system that
will address the duplicate entry problem and allow
them to incorporate an electronic ticketing
solution.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. PremierOne Records
can be customized to meet specific
agency needs through the use of
the PremierOne Records Advanced
Configuration Tool (ACT).
Advanced Configuration allows the
agency to make PremierOne
Records their own. The ACT allows
an agency to have custom forms in
existing PremierOne records
modules or new agency-specific
modules with agency-specific entry
forms and reports.
752
Out of the Box
Motorola
RT005
TRAFFIC
General
If an electronic ticketing solution is proposed,
citation documents being uploaded to the Court
need to pass through the RMS to populate
Citation Data needed for statistical analysis and
resource allocation studies.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
753
Out of the Box
Motorola
RT006
TRAFFIC
General
The County is requesting a Forms Library that is
centrally controlled to maintain the department's
special forms templates. Forms entered into the
library would have fields that are common
between forms mapped to each other so that
once one form is completed, its mapped data can
auto-populate subsequent forms for the same
event upon request. Documents created in the
RMS should also have common fields mapped to
like fields in the Forms Library templates. The
narrative free form sections of reports in the
Forms Library need to be able to utilize features
commonly found in MS Word.
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
754
Cannot Meet
Motorola
RT007
TRAFFIC
Traffic Accident
Investigations
The MCSO Vehicular Crimes Unit (VCU) is
dispatched to an accident/whenever there is a
fatality, a potential fatality, or criminal activity is
involved. The report prepared by VCU will always
become the primary case report. In situations
where the first unit on the scene has already
submitted a report, the initial report must become
a supplement to VCU's report. A synopsis of
reports prepared by VCU need to be sent to select
members of the MCSO management team
automatically upon completion without having to
do any manual distribution. The synopsis
document will consist of event header information
along with a narrative event summary. VCU will
enter the narrative summary as the first
paragraph of the DR narrative entry section,
Vendors are ask to detail how they can best satisfy
VCU's requirements, and perhaps offer
alternatives that will require less effort.
Mandatory
Records
X
VUC would enter their information
into PremierOne Records. Once
entered an MCSO created SSRS
report can be sent to the emails of
the select members of the MCSO
management team with the event
header information and the
narrative event summary. An
alternative would be to using a
workflow notification which would
require the VCU member to
workflow the document once
completed.
755
Out of the Box
Motorola
RT008
TRAFFIC
Traffic Accident
Investigations
In situations where an accident occurs within a
neighboring jurisdiction and MCSO has some
vested interest in the accident (i.e. a MCSO
employee was involved, County property was
damaged etc.) the other jurisdiction will complete
and submit the accident report' and MCSO Traffic
Investigations will complete a DR. In these
situations the subjects involved need to be
identified as Driver, Registered Owner, Passenger
in addition to the normal descriptors of Suspect,
Victim, Witness, etc. Vendors are to describe how
they can satisfy this requirement.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. PremierOne allows a
station Informational report to be
created. This report could contain
pertinent data, but would not be
UCR/IBR reportable.
756
Out of the Box
Page 45 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RI001
INVESTIGATIONS
General
Case Agents/Detectives need the capability to
submit cases to the County Attorney when they
feel that they are ready for prosecution. See the
Interfaces Section of this document for further
detail. Once a case is submitted the system should
track the time it has been at the County Attorney's
office, and notify the Case Agents once a user
selected time period has elapsed.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. An interface (as
requested) has been included with
our solution.
Alternatively, PremierOne also has
the ability to share data via Judicial
Sharing. Using Judicial Sharing,
from your agency’s view, users can
confirm that they received the case
package and continue to update
the shared package as the case
develops. From the case manager,
the prosecutor can see when a
shared package has been updated.
They can search and filter the case
packages to locate information and
then share the case package with
the defense. If your agency has case
sharing systems in place with
partners, you can leverage your
agency’s existing investments by
downloading content and audit logs
to review and share. Due to the
initial interface request, Judicial
Sharing has not been included with
l
i
b
i
il bl
757
Out of the Box
Motorola
RI002
INVESTIGATIONS
General
The system should track associations between
persons such that it will be possible to determine
from a name search all other persons who have
been associated with that person as a co-
defendant, in a vehicle during a field interrogation,
as a witness against the person or in any other
documented criminal justice involvement.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
758
Out of the Box
Motorola
RI003
INVESTIGATIONS
General
The system should have the ability to retrieve
cases with similar modus operandi to assist
deputies and detectives in solving crimes. For
example, similar victim types, crimes occurring in
close proximity or within a given date or time
range, or in which similar kinds of property were
taken, tools used, method of entry, point of entry,
characteristic actions, evidence found, victim
type/location, or weapon used.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
759
Out of the Box
Motorola
RI004
INVESTIGATIONS
General
The system should have the capability to identify
cases with a large number of matched suspect
descriptors such as glasses, teeth, speech,
demeanor, facial hair, complexion, scars, marks,
tattoos, hair length, hair style, hair color, ethnicity,
height, weight, or gender. The system should
provide a value (e.g., high, medium, low,
statistical, etc.) rating with the number of matches
listed across the descriptors.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
760
Out of the Box
Motorola
RI005
INVESTIGATIONS
General
The system should have the ability to display and
print a list of all individuals associated with a given
case sorted by their association with the case and
then alphabetically.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
761
Out of the Box
Motorola
RI006
INVESTIGATIONS
General
The above report will include the association of
each individual to the case.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
762
Out of the Box
Motorola
RI007
INVESTIGATIONS
General
The system should allow a user to retrieve all
records for a given associate by clicking on the
name, or by some other simple method.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
763
Out of the Box
Motorola
RI008
INVESTIGATIONS
General
When an officer/detective enters a name into a
case report and then tabs to the next field, the
RMS should automatically begin searching local
records to determine if the subject name appears
in any other case reports, in any capacity (victim,
suspect, witness, etc. including associations with
addresses, phone numbers, vehicles, and other
similar attributes).
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
764
Out of the Box
Page 46 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RI009
INVESTIGATIONS
General
The user should be alerted to all possible matches
via an agency definable message, which contains a
hyperlink to a summary page listing all possible
matches, and hyperlinks to the underlying
information regarding each subject.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
765
Out of the Box
Motorola
RI010
INVESTIGATIONS
General
The system should allow authorized users to
password protect case reports and supplements so
that they cannot be read by anyone without
authorization to do so.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
766
Out of the Box
Motorola
RI011
INVESTIGATIONS
General
The system should allow authorized users to
"compartmentalize" data contained within their
case reports and supplements. For example, the
System Administrator and authorized users will be
able to configure the system so that all original
and supplemental reports prepared by the
Homicide Detail and some or all (user-definable) of
the data contained in those reports are not
accessible to any user not assigned to the
Homicide Detail.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
767
Out of the Box
Motorola
RI012
INVESTIGATIONS
General
The system must be able to track individual or
multiple investigations assigned to a case with a
primary investigator.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
768
Out of the Box
Motorola
RDPL001
DIGITAL PHOTO
LINE-UP
General
The system shall allow selecting a photo from the
thumbnail lineup and accessing the master person
record in a view-only fashion for additional details.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
769
Out of the Box
Motorola
RDPL002
DIGITAL PHOTO
LINE-UP
General
The system must be able to generate a mug book
based on search criteria entered into the master
person index search.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
770
Out of the Box
Motorola
RDPL003
DIGITAL PHOTO
LINE-UP
General
The system shall include a number of search
criteria that are available to the user to allow for
detailed and specific searching of the master
person Index for photo line-up creation.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
771
Out of the Box
Motorola
RDPL004
DIGITAL PHOTO
LINE-UP
General
They system must allow photo lineups to be
created, saved and printed in a mobile
environment.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
772
Out of the Box
Motorola
RDPL005
DIGITAL PHOTO
LINE-UP
General
The system must allow the user to record an
unlimited number of witnesses, their selections
and notes.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
773
Out of the Box
Motorola
RDPL006
DIGITAL PHOTO
LINE-UP
General
Photo line-ups shall be able to be saved and
viewed at a later time.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
774
Out of the Box
Motorola
RDPL007
DIGITAL PHOTO
LINE-UP
General
Photo line-ups shall be able to be printed with one
image per page.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
775
Out of the Box
Motorola
RDPL008
DIGITAL PHOTO
LINE-UP
General
The system must allow the user to lock the record
prior to presenting it to witnesses.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
776
Out of the Box
Motorola
RDPL009
DIGITAL PHOTO
LINE-UP
General
The system must track and display the master
person Index record number for all included
images.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
777
Out of the Box
Motorola
RDPL010
DIGITAL PHOTO
LINE-UP
General
Photo lineups shall be able to be generated from
the person index for any individual with a photo
attachment.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
778
Out of the Box
Motorola
RDPL011
DIGITAL PHOTO
LINE-UP
General
Photo line-ups shall be able to be printed with six
images per page.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
779
Out of the Box
Motorola
RCM001
CASE
MANAGEMENT
General
The proposed RMS system should provide a
variety of management and analysis tools to:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
780
Out of the Box
Motorola
RCM001-1
CASE
MANAGEMENT
General
effectively manage investigator workloads,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
781
Out of the Box
Motorola
RCM001-2
CASE
MANAGEMENT
General
monitor performance
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
782
Out of the Box
Motorola
RCM001-3
CASE
MANAGEMENT
General
allocate departmental resources.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
783
Out of the Box
Motorola
RCM002
CASE
MANAGEMENT
General
The case management module should be tightly
integrated with the other portions of the RMS
system.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
784
Out of the Box
Motorola
RCM003
CASE
MANAGEMENT
General
The system should allow authorized users to
display all new cases entered for a given date
range so that he/she can review the cases for
assignment.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
785
Out of the Box
Page 47 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RCM004
CASE
MANAGEMENT
General
The system should respond with a summary
display that shows the report number, the location
of the offense, the officer initiating the case, the
offense type, the victim name, and the date on
which it was initiated.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
786
Out of the Box
Motorola
RCM005
CASE
MANAGEMENT
General
The system should allow authorized users to
search and display all cases by:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
787
Out of the Box
Motorola
RCM005-1
CASE
MANAGEMENT
General
assigned officer/detective,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
788
Out of the Box
Motorola
RCM005-2
CASE
MANAGEMENT
General
offense type,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
789
Out of the Box
Motorola
RCM005-3
CASE
MANAGEMENT
General
date and time of offense,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
790
Out of the Box
Motorola
RCM005-4
CASE
MANAGEMENT
General
aging (how long investigation has been ongoing),
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
791
Out of the Box
Motorola
RCM005-5
CASE
MANAGEMENT
General
shift and/or squad,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
792
Out of the Box
Motorola
RCM005-6
CASE
MANAGEMENT
General
station
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
793
Out of the Box
Motorola
RCM005-7
CASE
MANAGEMENT
General
case status, and
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
794
Out of the Box
Motorola
RCM005-8
CASE
MANAGEMENT
General
division.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
795
Out of the Box
Motorola
RCM006
CASE
MANAGEMENT
General
The system should respond with a user-definable
summary display which shows the case number,
the victim name, the detective assigned to the
case, the offense type, the status of the case
(including the date when the case was last
modified).
Mandatory
Records
X
PremierOne is compliant with User
created scheduled SSRS reports. As
part of deployment, Motorola will
apply canned reports to the system
and lead a reporting writing
workshop with County personnel.
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
796
With Configuration
Motorola
RCM007
CASE
MANAGEMENT
General
Authorized users should be able to set a threshold
for case aging and be able to receive automatic
notifications whenever any active cases exceed
the pre-set case inactivity threshold.
Mandatory
Records
X
PremierOne is compliant with User
created scheduled SSRS reports. As
part of deployment, Motorola will
apply canned reports to the system
and lead a reporting writing
workshop with County personnel.
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
797
With Configuration
Motorola
RCM008
CASE
MANAGEMENT
General
The above requirement should also include the
ability for users to define case aging threshold
notifications for user-definable incident
classifications, individually, and by group (e.g. The
ability for a supervisor to set an alert that notifies
an individual or group of employees (e.g.
supervisors) when any or all active sex offense
incident reports have reached a 90 day period
from date of offense). The purpose of this
requirement is to notify users when a case
requires review per department policy.
Mandatory
Records
X
PremierOne is compliant with User
created scheduled SSRS reports. As
part of deployment, Motorola will
apply canned reports to the system
and lead a reporting writing
workshop with County personnel.
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
798
With Configuration
Page 48 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RCM009
CASE
MANAGEMENT
General
Each supervisor should have the capability to set
the case aging threshold for their individual
squads, or for any particular case and be able to
receive automatic notifications whenever any
active cases exceed the pre-set case inactivity
threshold.
Mandatory
Records
X
PremierOne is compliant with User
created scheduled SSRS reports. As
part of deployment, Motorola will
apply canned reports to the system
and lead a reporting writing
workshop with County personnel.
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
799
With Configuration
Motorola
RCM010
CASE
MANAGEMENT
General
The system should have the ability to track and
report case outcomes and crime statistics on all
records that remain in the on-line database.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
800
Out of the Box
Motorola
RCM011
CASE
MANAGEMENT
General
The system should provide the ability for users to
query by case classification (i.e. active, inactive,
suspended, etc.) and easily produce a report that
provides closure rates in summary and statistical
formats. The purpose of this requirement is to
facilitate the monitoring of arrest and other similar
metrics.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
801
Out of the Box
Motorola
RCM012
CASE
MANAGEMENT
General
The standard case management display should
include the offense type, the case number, date
and time the incident was reported, location, type
of report, case status and other user-definable
fields.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
802
Out of the Box
Motorola
RCM013
CASE
MANAGEMENT
General
It should be possible for the system administrator
or other authorized user to configure the system
so that cases are automatically assigned to a
specific detective/officer based on:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
803
Out of the Box
Motorola
RCM013-1
CASE
MANAGEMENT
General
offense location, or
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
804
Out of the Box
Motorola
RCM013-2
CASE
MANAGEMENT
General
offense type, or other user-defined criteria.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
805
Out of the Box
Motorola
RCM013-3
CASE
MANAGEMENT
General
victim
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
806
Out of the Box
Motorola
RCM013-4
CASE
MANAGEMENT
General
suspect
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
807
Out of the Box
Motorola
RCM014
CASE
MANAGEMENT
General
The system should enable an authorized user to
assign a case to a specific detective or other
member of the Department.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
808
Out of the Box
Motorola
RCM015
CASE
MANAGEMENT
General
The department currently utilizes a paper Case
Solvability Factors Assignment Form (CSFA) on
which solvability factors are reviewed in order to
determine if and to whom each case should be
assigned for follow-up investigation. The system
should have the ability to create an electronic
version of this document that can be completed by
the supervisor responsible for reviewing cases.
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
809
Cannot Meet
Motorola
RCM016
CASE
MANAGEMENT
General
The user should have the ability to link the CFSA to
the case that is being assigned so that the CFSA
form is routed to the assigned detective who
receives the notification that they are being
assigned to the case.
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
810
Cannot Meet
Motorola
RCM017
CASE
MANAGEMENT
General
The CFSA should become part of the case file and
accessible to users as part of the case file.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
811
Out of the Box
Motorola
RCM018
CASE
MANAGEMENT
General
Users should be able to enter identifying
information about assisting detectives.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
812
Out of the Box
Motorola
RCM019
CASE
MANAGEMENT
General
The system should enable any authorized user to
transfer a case to another
officer/detective/supervisor or employee for
processing.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
813
Out of the Box
Motorola
RCM020
CASE
MANAGEMENT
General
The system should track both the reassignment of
cases and changes in officer/detective/supervisor
over time in order to retain previous the data.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
814
Out of the Box
Page 49 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RCM021
CASE
MANAGEMENT
General
The system should automatically notify a detective
or other member of the department at logon
when a new case has been assigned to them for
follow-up.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
815
Out of the Box
Motorola
RCM022
CASE
MANAGEMENT
General
The system should also notify the original
reporting officer when a case has been assigned
for follow-up and the identity of the assigned
detective.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
816
Out of the Box
Motorola
RCM023
CASE
MANAGEMENT
General
The system should have the ability to notify the
original reporting officer and/or detective
whenever a supplemental report has been filed on
a case.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
817
Out of the Box
Motorola
RCM024
CASE
MANAGEMENT
General
The system should allow authorized users to block
access into selected investigations in progress.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
818
Out of the Box
Motorola
RCM025
CASE
MANAGEMENT
General
The system should allow authorized users to view
cases by all department units and sections.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
819
Out of the Box
Motorola
RCM026
CASE
MANAGEMENT
General
The system should have the ability to identify
cases without activity for a user-defined period of
time.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
820
Out of the Box
Motorola
RCM027
CASE
MANAGEMENT
General
At a minimum the system should be capable of
utilizing the following agency-defined case
statuses:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
821
Out of the Box
Motorola
RCM027-1
CASE
MANAGEMENT
General
Active (open): Cases that have been assigned and
are under current investigation.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
822
Out of the Box
Motorola
RCM027-2
CASE
MANAGEMENT
General
Inactive (open): Cases not assigned due to lack of
solvability factors or those that have had all viable
leads exhausted without results.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
823
Out of the Box
Motorola
RCM027-3
CASE
MANAGEMENT
General
Unfounded (closed): The incident does not meet
the elements of a criminal offense.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
824
Out of the Box
Motorola
RCM027-4
CASE
MANAGEMENT
General
Cleared by Arrest (closed): Cases which terminate
in the arrest of an individual or charges are filed.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
825
Out of the Box
Motorola
RCM027-5
CASE
MANAGEMENT
General
Exceptionally Cleared (closed): Cleared by
Exceptional Means. A case is exceptionally cleared
if any of the following can be answered in the
affirmative:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
826
Out of the Box
Motorola
RCM027-6
CASE
MANAGEMENT
General
A - Death of the Offender
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
827
Out of the Box
Motorola
RCM027-7
CASE
MANAGEMENT
General
B - Prosecution Denied (by the prosecutor for
other than lack of probable cause)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
828
Out of the Box
Motorola
RCM027-8
CASE
MANAGEMENT
General
C - In Custody of Other Jurisdiction (includes
extradition denied)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
829
Out of the Box
Motorola
RCM027-9
CASE
MANAGEMENT
General
D - Victim Refused to Cooperate (in the
prosecution)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
830
Out of the Box
Motorola
RCM027-10
CASE
MANAGEMENT
General
E - Juvenile/No Custody (the handling of a juvenile
without taking him/her into custody, but rather by
oral or written notice given to the
parents/guardian in a case involving a minor
offense)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
831
Out of the Box
Motorola
RCM027-11
CASE
MANAGEMENT
General
N - Not Applicable (not cleared exceptionally)
Records
X
PremierOne complies with the
functionality as described in the
requirement.
832
Out of the Box
Motorola
RCM028
CASE
MANAGEMENT
General
The system should help detectives track all activity
on a case including personal interviews, phone
calls, etc. by providing a means of recording the
date, time and description of the activity and by
providing a notes field in which the detective can
record information.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
833
Out of the Box
Motorola
RCM029
CASE
MANAGEMENT
General
The system should allow any authorized user to
view or print out a complete history of detectives
assigned to a case and activities associated with a
case.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
834
Out of the Box
Page 50 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RCM030
CASE
MANAGEMENT
General
The system should export all case documents to
include the original IR, all supplemental IRs, and all
attachments related to the IR in one-click.
Currently, with TraCS, each IR form and their
attachment(s) is printing individually to a PDF. For
large investigations (Homicides, Sex Crimes,
Robberies, etc.), this can take hours if not days to
pull the full IR from TraCS, combine them into one
PDF before any redactions can commence.
Mandatory
Records
X
PremierOne does not have this
functionality.
This functionality was added to product version 4.6.15 . At
time of RFP response and demonstrations this
functionality did not exist.
It is expected MCSO will receive 4.6.15 (or later) during
implementation.
MCSO & Motorola teams agree
requirement is met out of the box
per notes in Column O.
835
Cannot Meet
Motorola
RCM031
CASE
MANAGEMENT
General
The system must be able to enter, retrieve, and
cross reference nicknames, known associates and
vehicles.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
836
Out of the Box
Motorola
RCM032
CASE
MANAGEMENT
General
Investigative supervisors must be able to assign
cases to specific staff investigators.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
837
Out of the Box
Motorola
RCM033
CASE
MANAGEMENT
General
The system must be able to track individual or
multiple investigations assigned to a case with a
primary investigator.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
838
Out of the Box
Motorola
RCM034
CASE
MANAGEMENT
General
The system must support “inactive” and “active”
user-defined status codes.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
839
Out of the Box
Motorola
RCM035
CASE
MANAGEMENT
General
The system must support “cleared”, “exceptional
cleared” or “unfounded” clearance categories.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
840
Out of the Box
Motorola
RCM036
CASE
MANAGEMENT
General
The system must provide the ability to
immediately review all assigned cases at an
investigator level for suspects, property, or
evidence.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
841
Out of the Box
Motorola
RCM037
CASE
MANAGEMENT
General
Follow-up reporting, statements of interviews,
investigative notes or activity logs (including
charges or complaints) must be available.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
842
Out of the Box
Motorola
RCM038
CASE
MANAGEMENT
General
The system must allow investigators to input case
logs, notes, and summaries.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
843
Out of the Box
Motorola
RCM039
CASE
MANAGEMENT
General
The system must interface with the property and
evidence, arrests and incidents modules.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
844
Out of the Box
Motorola
RCM040
CASE
MANAGEMENT
General
The system must track leads and assignments.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
845
Out of the Box
Motorola
RCM041
CASE
MANAGEMENT
General
All documentation relating to a case must be
collated into one case folder for easier access.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
846
Out of the Box
Motorola
RCM042
CASE
MANAGEMENT
General
The system must provide unlimited free form
narrative that can be spell checked.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
847
Out of the Box
Motorola
RCM043
CASE
MANAGEMENT
General
All cases must be tracked from the receipt of the
original incident to disposition.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
848
Out of the Box
Motorola
RMATC001
MULTI-MEDIA
ATTACHMENTS
General
The system shall have the ability to allow the
operator to retrieve all or selected documents or
images while viewing a particular case.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
849
Out of the Box
Motorola
RMATC002
MULTI-MEDIA
ATTACHMENTS
General
The system shall have the ability to provide a
manual index assignment at the request of the
operator.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
850
Out of the Box
Motorola
RMATC003
MULTI-MEDIA
ATTACHMENTS
General
The system shall have the ability to provide
indexing of imaged documents by linking the
image with a case, booking or civil process folder.
The indexing system shall provide, at a minimum:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
851
Out of the Box
Motorola
RMATC004
MULTI-MEDIA
ATTACHMENTS
General
Case and incident numbers
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
852
Out of the Box
Motorola
RMATC005
MULTI-MEDIA
ATTACHMENTS
General
Date/Time of incident
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
853
Out of the Box
Motorola
RMATC006
MULTI-MEDIA
ATTACHMENTS
General
Date/Time reported
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
854
Out of the Box
Motorola
RMATC007
MULTI-MEDIA
ATTACHMENTS
General
Location by address/beat/agency
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
855
Out of the Box
Motorola
RMATC008
MULTI-MEDIA
ATTACHMENTS
General
Victim
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
856
Out of the Box
Page 51 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RMATC009
MULTI-MEDIA
ATTACHMENTS
General
Complainant
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
857
Out of the Box
Motorola
RMATC010
MULTI-MEDIA
ATTACHMENTS
General
Suspect
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
858
Out of the Box
Motorola
RMATC011
MULTI-MEDIA
ATTACHMENTS
General
Incident type
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
859
Out of the Box
Motorola
RMATC012
MULTI-MEDIA
ATTACHMENTS
General
The system shall have the ability to allow for the
routing and rerouting of case documents to staff
members as required for approval.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
860
Out of the Box
Motorola
RMATC013
MULTI-MEDIA
ATTACHMENTS
General
The system shall have the ability to scan
handwritten courtesy reports from outside
agencies and store within a given case.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
861
Out of the Box
Motorola
RMATC014
MULTI-MEDIA
ATTACHMENTS
General
The system shall have the ability to integrate with
a data management system such that a user can
access and view images from the data application.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
862
Out of the Box
Motorola
RMATC015
MULTI-MEDIA
ATTACHMENTS
General
The system shall have the ability to create final
document images for permanent storage in a
secure and unchangeable format.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
863
Out of the Box
Motorola
RMATC016
MULTI-MEDIA
ATTACHMENTS
General
The system shall have the ability to include
workflow management that has the capability to
route images to the appropriate staff member or
group; based on user and agency defined criteria.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
864
Out of the Box
Motorola
RCA001
CRIME ANALYSIS
General
The system should support continual
improvement of MCSO operations and
administration by providing a crime analysis
module that provides graphical and statistical tools
utilizing the CAD/RMS geofile for analyzing the
occurrence of crime and other reported incidents
within the County.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. PremierOne CAD
utilizes Microsoft SQL Server
Reporting Services (SSRS) for its
standard reports. SSRS is a server-
based reporting platform that is
used to create and manage tabular,
matrix, graphical, dashboards, and
free form reports that contain data
from relational and
multidimensional data sources. As
part of deployment, Motorola will
apply canned reports to the system
and lead a reporting writing
workshop with County personnel.
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. Map layers may be
incorporated into these reports.
865
Out of the Box
Motorola
RCA002
CRIME ANALYSIS
General
The system should provide ease of use to all users
who are familiar with a Windows environment and
will not require extensive training to conduct
standard crime analysis tasks.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
866
Out of the Box
Motorola
RCA003
CRIME ANALYSIS
General
The crime analysis functionality should permit the
easy analysis of data for the purposes of
identifying and eradicating a crime series as well
as the analysis of criminal offenses that are
thought to share the same causal factor (usually a
single offender or group of offenders) given their
descriptive, behavior, spatial, or temporal
commonality.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
867
Out of the Box
Motorola
RCA004
CRIME ANALYSIS
General
The system should have the ability to present
crime distribution statistics in graphical formats: 1)
Bar graphs, 2) Pie charts, 3) Line graphs, 4) Tabular
(Matrix) form, 5) Maps.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
868
Out of the Box
Motorola
RCA005
CRIME ANALYSIS
General
The system should allow authorized users to
graphically track and analyze crime trends on a
map (such as the frequency of drug arrests near
schools or a rash of auto thefts in a particular
neighborhood for a user-defined period of time).
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
869
Out of the Box
Page 52 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RCA006
CRIME ANALYSIS
General
The system should have the ability to map layers
utilizing multiple data sets (offenses, calls for
service, etc.).
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
870
Out of the Box
Motorola
RCA007
CRIME ANALYSIS
General
The system should have the ability to overlay
multiple GIS data layers (community pools, parks,
known gang activity, etc.).
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
871
Out of the Box
Motorola
RCA008
CRIME ANALYSIS
General
The system should present the user with a pick list
of agency-defined map layers to utilize when
conducting a mapping query.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
872
Out of the Box
Motorola
RCA009
CRIME ANALYSIS
General
The system should allow the user to select and
utilize multiple map layers simultaneously.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
873
Out of the Box
Motorola
RCA010
CRIME ANALYSIS
General
The system should allow the user to select an area
by drawing a polygon around a selected area to
initiate a user-defined search.
Mandatory
Records
X
A polygon covering a specific area
can be added to the map layers in
the reporting system. However,
users do not have the ability to
draw a polygon in SSRS.
MCSO team agrees with
explanation in column N.
874
Cannot Meet
Motorola
RCA011
CRIME ANALYSIS
General
When the user rolls their cursor over an icon
representing an offense or call for service, a small
window should appear which contains user-
defined summary information about the offense
or call for service (e.g. date, time, location,
offense).
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Calls for Service
plotted on a map can be drilled into
to pull additional information.
875
Out of the Box
Motorola
RCA012
CRIME ANALYSIS
General
When the user applies a mouse click to the icon
representing an offense of call for service, the
system should immediately link to and display the
case report and/or call for service information.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
876
Out of the Box
Motorola
RCA013
CRIME ANALYSIS
General
The system should be able to print maps produced
as a result of queries.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Screenshots of the
map may be printed, however, may
be cluttered and difficult to read
depending on the amount of data
contained in the specific query.
877
Out of the Box
Motorola
RCA014
CRIME ANALYSIS
General
The system should have the ability to conduct
crime distribution analysis by such user-defined
criteria as:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
878
Out of the Box
Motorola
RCA014-1
CRIME ANALYSIS
General
Offense Type(s)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
879
Out of the Box
Motorola
RCA014-2
CRIME ANALYSIS
General
Sub-Census, Patrol Area, District, Division,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
880
Out of the Box
Motorola
RCA014-3
CRIME ANALYSIS
General
Frequency of occurrence
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
881
Out of the Box
Motorola
RCA014-4
CRIME ANALYSIS
General
Type (residential, auto, business, etc.)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
882
Out of the Box
Motorola
RCA014-5
CRIME ANALYSIS
General
Sub-Type i.e., if business what kind (liquor store,
Peruvian restaurant, etc.)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
883
Out of the Box
Motorola
RCA014-6
CRIME ANALYSIS
General
Suspect MO (Method of Operation) (including
weapons, tools, force used, etc.)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
884
Out of the Box
Motorola
RCA014-7
CRIME ANALYSIS
General
Suspect Descriptors (name, sex, race, age, tattoos,
hair color, etc.)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
885
Out of the Box
Motorola
RCA014-8
CRIME ANALYSIS
General
Vehicle Descriptors (make, model, model year
range, coupe/sedan, convertible, etc.)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
886
Out of the Box
Motorola
RCA014-9
CRIME ANALYSIS
General
Property type involved (house, boat, car, wallet,
bike, printer, cash, etc.)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
887
Out of the Box
Motorola
RCA014-10
CRIME ANALYSIS
General
Weapon used (knife, gun, machete, pencil, lug
wrench, fist, foot, etc.)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
888
Out of the Box
Motorola
RCA014-11
CRIME ANALYSIS
General
Current period vs. previous period
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
889
Out of the Box
Motorola
RCA014-12
CRIME ANALYSIS
General
Current period vs. historical average
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
890
Out of the Box
Motorola
RCA014-13
CRIME ANALYSIS
General
Percentage of total crimes for period by Patrol
Area, District, Division
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
891
Out of the Box
Page 53 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RCA014-14
CRIME ANALYSIS
General
Percentage change from prior periods (trend)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
892
Out of the Box
Motorola
RCA015
CRIME ANALYSIS
General
The system will should have the ability to generate
user-definable ad-hoc reports by any combination
of the above criteria.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
893
Out of the Box
Motorola
RCA016
CRIME ANALYSIS
General
All crime and activity reports should be able to be
filtered and sorted by user-definable criteria such
as:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
894
Out of the Box
Motorola
RCA016-1
CRIME ANALYSIS
General
Patrol Division, District, Patrol Area, Sub-Census
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
895
Out of the Box
Motorola
RCA016-2
CRIME ANALYSIS
General
other user defined geographic area,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
896
Out of the Box
Motorola
RCA016-3
CRIME ANALYSIS
General
date and time range of occurrence, and
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
897
Out of the Box
Motorola
RCA016-4
CRIME ANALYSIS
General
crime or activity type.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
898
Out of the Box
Motorola
RCA017
CRIME ANALYSIS
General
The system should allow users to easily access and
search the following kinds of user-definable
information from crime and other reports:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
899
Out of the Box
Motorola
RCA017-1
CRIME ANALYSIS
General
Date of the offense, by date range
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
900
Out of the Box
Motorola
RCA017-2
CRIME ANALYSIS
General
Time of the offense, by time range
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
901
Out of the Box
Motorola
RCA017-3
CRIME ANALYSIS
General
Location where the offense occurred
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
902
Out of the Box
Motorola
RCA017-4
CRIME ANALYSIS
General
Type of premises
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
903
Out of the Box
Motorola
RCA017-5
CRIME ANALYSIS
General
Description of weapons or tools used
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
904
Out of the Box
Motorola
RCA017-6
CRIME ANALYSIS
General
Method and point of entry/exit
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
905
Out of the Box
Motorola
RCA017-7
CRIME ANALYSIS
General
Victim data
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
906
Out of the Box
Motorola
RCA017-8
CRIME ANALYSIS
General
Suspect data such as but not limited to:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
907
Out of the Box
Motorola
RCA017-9
CRIME ANALYSIS
General
Hair (color, length, style, etc.)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
908
Out of the Box
Motorola
RCA017-10
CRIME ANALYSIS
General
Eyes (color, shape, size, etc.)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
909
Out of the Box
Motorola
RCA017-11
CRIME ANALYSIS
General
Glasses
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
910
Out of the Box
Motorola
RCA017-12
CRIME ANALYSIS
General
Facial hair
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
911
Out of the Box
Motorola
RCA017-13
CRIME ANALYSIS
General
Face shape
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
912
Out of the Box
Motorola
RCA017-14
CRIME ANALYSIS
General
Complexion
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
913
Out of the Box
Motorola
RCA017-15
CRIME ANALYSIS
General
Teeth
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
914
Out of the Box
Motorola
RCA017-16
CRIME ANALYSIS
General
Height
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
915
Out of the Box
Motorola
RCA017-17
CRIME ANALYSIS
General
Build
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
916
Out of the Box
Motorola
RCA017-18
CRIME ANALYSIS
General
Speech
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
917
Out of the Box
Page 54 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RCA017-19
CRIME ANALYSIS
General
Handed (left/right)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
918
Out of the Box
Motorola
RCA017-20
CRIME ANALYSIS
General
Demeanor (nervous, intoxicated, etc.)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
919
Out of the Box
Motorola
RCA017-21
CRIME ANALYSIS
General
Appearance (neat, dirty, etc.)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
920
Out of the Box
Motorola
RCA017-22
CRIME ANALYSIS
General
Scars, marks, and tattoos
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
921
Out of the Box
Motorola
RCA017-23
CRIME ANALYSIS
General
Gang status (yes/no)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
922
Out of the Box
Motorola
RCA017-24
CRIME ANALYSIS
General
Gang affiliation (name of gang)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
923
Out of the Box
Motorola
RCA017-25
CRIME ANALYSIS
General
Reporting party data
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
924
Out of the Box
Motorola
RCA017-26
CRIME ANALYSIS
General
Text contained in narrative fields
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
925
Out of the Box
Motorola
RCA017-27
CRIME ANALYSIS
General
Description of property stolen
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
926
Out of the Box
Motorola
RCA017-28
CRIME ANALYSIS
General
Description of any evidence recovered
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
927
Out of the Box
Motorola
RCA017-29
CRIME ANALYSIS
General
Vehicle(s) involved/stolen description(s)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
928
Out of the Box
Motorola
RCA017-30
CRIME ANALYSIS
General
Data from all fields in all reports.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
929
Out of the Box
Motorola
RCA017-31
CRIME ANALYSIS
General
The system should be able to create visual
representations of:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
930
Out of the Box
Motorola
RCA017-32
CRIME ANALYSIS
General
Crime statistics
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
931
Out of the Box
Motorola
RCA017-33
CRIME ANALYSIS
General
Links between persons (victim, suspects)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
932
Out of the Box
Motorola
RCA017-34
CRIME ANALYSIS
General
Links between property and locations
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
933
Out of the Box
Motorola
RCA017-35
CRIME ANALYSIS
General
Links between people, places, vehicles, telephone
numbers, other object types, and
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
934
Out of the Box
Motorola
RCA018
CRIME ANALYSIS
General
The system should have the ability to retrieve
cases with similar modus operandi to assist
officers and detectives in solving crimes. For
example, similar victim types, crimes occurring in
close proximity or within a given date or time
range, or in which similar kinds of property were
taken, tools used, method of entry, point of entry,
characteristic actions, evidence found, victim
type/location, weapon used, etc.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
935
Out of the Box
Page 55 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RCA019
CRIME ANALYSIS
General
The system should allow authorized users to set
thresholds for certain kinds of activities within a
particular geographic area. If the activity threshold
is exceeded the system will notify the crime
analyst. For example, if the user sets a threshold
for burglaries of five per month in a specific Patrol
Area, the system will send a notice to the user if
more than five burglaries are committed in one
month within that Patrol Area.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. PremierOne CAD
utilizes Microsoft SQL Server
Reporting Services (SSRS) for its
standard reports. SSRS is a server-
based reporting platform that is
used to create and manage tabular,
matrix, graphical, dashboards, and
free form reports that contain data
from relational and
multidimensional data sources. As
part of deployment, Motorola will
apply canned reports to the system
and lead a reporting writing
workshop with County personnel.
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. Map layers may be
incorporated into these reports.
936
With Configuration
Motorola
RCA020
CRIME ANALYSIS
General
The system should allow authorized users to set
thresholds for offenses that were committed
within user-definable dates, times, and locations
based on:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
937
Out of the Box
Motorola
RCA020-1
CRIME ANALYSIS
General
Suspect M.O. (including weapons, tools, force
used, method of entry etc.) and/or
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
938
Out of the Box
Motorola
RCA020-2
CRIME ANALYSIS
General
Suspect Descriptors (sex, race, age, tattoos, hair
color, etc.)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
939
Out of the Box
Motorola
RCA021
CRIME ANALYSIS
General
The system should allow for the integration of
industry standard link analysis tools, i.e. i2 Analyst
Notebook, LinX, CrimeView.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. PremierOne data can
be exported from the RDW for
analysis from third party software.
940
Out of the Box
Motorola
RCA022
CRIME ANALYSIS
General
The system should be capable of being configured
to send notification to the crime analyst of
selected offenses that were committed within user-
definable dates, times, and location based on:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
941
Out of the Box
Motorola
RCA022-1
CRIME ANALYSIS
General
Suspect M.O. (including weapons, tools, force
used, method of entry etc.) and/or
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
942
Out of the Box
Motorola
RCA022-2
CRIME ANALYSIS
General
Suspect Descriptors (sex, race, age, tattoos, hair
color, etc.)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
943
Out of the Box
Motorola
RCA023
CRIME ANALYSIS
General
The notification should include a summary listing
of offenses that were reported during the user-
defined time and date range.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
944
Out of the Box
Motorola
RCA024
CRIME ANALYSIS
General
Authorized users should be able to point and click
on any of the cases listed in the summary to open
the case report associated with the offense.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
945
Out of the Box
Motorola
RCA025
CRIME ANALYSIS
General
Authorized users should be able to save the
notification parameters and set the notification
report to run continuously or for a user-defined
time period.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
946
Out of the Box
Motorola
RCA026
CRIME ANALYSIS
General
For example, authorized users should be able set
the system to submit a notification of all user-
definable events (e.g. Robberies, Homicides,
Larcenies) that occur between any-user definable
time period.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
947
Out of the Box
Motorola
RUC001
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Uniformed Crime Reporting (UCR) system. Please
note that MCSO is required to switch from UCR
reporting to NIBRS based reporting based on a FBI
mandate. In order to be able to account for the
increase in overall crime. MCSO needs to do both
UCR and NIBRS based reporting for a to be
determined time period.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
948
Out of the Box
Page 56 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RUC002
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
The RMS shall provide for the collection of all
information as required by the Uniform Crime
Reporting (UCR)/NIBRS data elements.
(https://le.fbi.gov/informational-tools/ucr/ucr-
technical-specifications-user-manuals-and-data-
tools#NIBRS)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
949
Out of the Box
Motorola
RUC003
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
The system should be able to update case
information that has previously been submitted.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
950
Out of the Box
Motorola
RUC004
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
The system should provide "wizard" type
functionality that ensures all reports prepared in
the vendor's field based reporting system are
audited for compliance to UCR standards during
report preparation by assisting the user in properly
completing all necessary fields in the incident
report.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
951
Out of the Box
Motorola
RUC005
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
MCSO's goal is to reduce much of the duplicate
data entry that is currently required by this
process. MCSO wants to reduce data entry by
means of an interface to the MCSO Pre-Booking
System. This interface will allow arrest and
booking information that is captured in the RMS to
auto-populate the County Pre-Booking Form. See
the Interfaces Section of this document for further
detail.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Motorola has
provided an Inmate Booking Bi-
Directional interface with our
solution.
952
Out of the Box
Motorola
RUC006
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
The Arrest and Booking Module should:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
953
Out of the Box
Motorola
RUC007
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Provide an arrest processing module for entering
and storing information about all persons
arrested. .
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
954
Out of the Box
Motorola
RUC008
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Provide the ability to capture, maintain, track, and
report on numerous user-definable data fields of
information on arrested persons.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
955
Out of the Box
Motorola
RUC009
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Provide database access to all persons arrested as
well as provide all criminal, contact, and available
court information on persons processed.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
956
Out of the Box
Motorola
RUC010
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Arrest information should be linked to the
associated event report and CAD event
information.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
957
Out of the Box
Motorola
RUC011
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
The MCSO Records Section receives felony
warrants/warrant quashes from other County
agencies/municipalities and is responsible for
entering them into the States ACJIS database.
MCSO misdemeanor warrants are also entered.
MCSO is entering the warrants into a system called
Justice Web Interface (JWI). JWI passes the
warrants on to ACJIS, and will also need to feed
them (new warrants and quashes) to the new
RMS. See the Interfaces Section of this document
for further detail.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Motorola has
provided a State Query interface
with our solution.
958
Out of the Box
Motorola
RUC012
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Provide a means for tracking the physical location
of wanted persons warrants
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
959
Out of the Box
Motorola
RUC013
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Track recall (quash) information about a warrant
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
960
Out of the Box
Motorola
RUC014
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
The system should have the ability to maintain,
search, and report on numerous categories of
agency-definable data elements including but not
limited to:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
961
Out of the Box
Motorola
RUC015
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Warrant Information such as:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
962
Out of the Box
Motorola
RUC016
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Issuance and expiration dates
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
963
Out of the Box
Motorola
RUC017
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Maricopa County Court, Criminal, or Traffic (Court
of Issuance)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
964
Out of the Box
Motorola
RUC018
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Name of issuing judge
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
965
Out of the Box
Page 57 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RUC019
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Name of defendant
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
966
Out of the Box
Motorola
RUC020
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Status
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
967
Out of the Box
Motorola
RUC021
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Date of issuance
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
968
Out of the Box
Motorola
RUC022
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Date of entry by the Warrant Desk
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
969
Out of the Box
Motorola
RUC023
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Employee Identification Number
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
970
Out of the Box
Motorola
RUC024
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Physical Location of the Warrant
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
971
Out of the Box
Motorola
RUC025
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Misdemeanor, Felony, Undersignated, or Civil
(such as Child Support)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
972
Out of the Box
Motorola
RUC026
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Agency Case Number
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
973
Out of the Box
Motorola
RUC027
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Extradition limitations
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
974
Out of the Box
Motorola
RUC028
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
County and/or State Offense Code
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
975
Out of the Box
Motorola
RUC029
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Service Information such as:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
976
Out of the Box
Motorola
RUC030
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Date and time of service
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
977
Out of the Box
Motorola
RUC031
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Name of arresting/serving officer
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
978
Out of the Box
Motorola
RUC032
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Badge Number
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
979
Out of the Box
Motorola
RUC033
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
EIN
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
980
Out of the Box
Motorola
RUC034
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Agency
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
981
Out of the Box
Motorola
RUC035
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Jurisdiction
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
982
Out of the Box
Motorola
RUC036
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Local/State
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
983
Out of the Box
Motorola
RUC037
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Location of arrest
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
984
Out of the Box
Motorola
RUC038
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Location of booking
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
985
Out of the Box
Motorola
RUC039
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Type of Warrant (court, officer, citizen, outside
jurisdiction, etc.)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
986
Out of the Box
Motorola
RUC040
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Person Information such as:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
987
Out of the Box
Motorola
RUC041
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Name
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
988
Out of the Box
Motorola
RUC042
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Driver's License Information i.e., date of issuance
and expiration, state, type, restrictions, etc.)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
989
Out of the Box
Motorola
RUC043
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Address
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
990
Out of the Box
Motorola
RUC044
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Social Security Number
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
991
Out of the Box
Page 58 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RUC045
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Date of Birth
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
992
Out of the Box
Motorola
RUC046
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Race
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
993
Out of the Box
Motorola
RUC047
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Height
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
994
Out of the Box
Motorola
RUC048
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Weight
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
995
Out of the Box
Motorola
RUC049
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Eye color
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
996
Out of the Box
Motorola
RUC050
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Hair color
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
997
Out of the Box
Motorola
RUC051
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Sex
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
998
Out of the Box
Motorola
RUC052
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Characteristics such as armed and dangerous,
mental case, suicidal, gang affiliation, etc.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
999
Out of the Box
Motorola
RUC053
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Person types associated with a warrant are subject
(defendant), alias, and complainant.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1000
Out of the Box
Motorola
RUC054
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Photograph (hyperlink to the booking photograph) Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1001
Out of the Box
Motorola
RUC055
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Recall (Quash) information such as:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1002
Out of the Box
Motorola
RUC056
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Name of agency requesting recall
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1003
Out of the Box
Motorola
RUC057
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Name of person requesting recall
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1004
Out of the Box
Motorola
RUC058
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Telephone number of person requesting recall
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1005
Out of the Box
Motorola
RUC059
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Person contacted regarding recall
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1006
Out of the Box
Motorola
RUC060
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Agency notified of the recall
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1007
Out of the Box
Motorola
RUC061
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Date the agency was advised
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1008
Out of the Box
Motorola
RUC062
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
EIN of processing clerk
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1009
Out of the Box
Motorola
RUC063
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Date of the recall request
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1010
Out of the Box
Motorola
RUC064
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Time of the recall request
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1011
Out of the Box
Motorola
RUC065
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Civil Process information such as:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1012
Out of the Box
Motorola
RUC066
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Issuance and expiration dates
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1013
Out of the Box
Motorola
RUC067
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
General County Court (Traffic or Criminal)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1014
Out of the Box
Motorola
RUC068
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Juvenile and Domestic Relations
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1015
Out of the Box
Motorola
RUC069
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Other Jurisdiction
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1016
Out of the Box
Motorola
RUC070
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Town
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1017
Out of the Box
Page 59 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RUC071
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
County
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1018
Out of the Box
Motorola
RUC072
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Ordinances of County, County, or Town type
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1019
Out of the Box
Motorola
RUC073
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Last, First, and Middle name
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1020
Out of the Box
Motorola
RUC074
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Mailing Address
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1021
Out of the Box
Motorola
RUC075
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Residential Address
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1022
Out of the Box
Motorola
RUC076
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Physical descriptors listed under Warrant Detail
Information above
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1023
Out of the Box
Motorola
RUC077
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Notation of execution
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1024
Out of the Box
Motorola
RUC078
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Notation of service pursuant to AZ Code
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1025
Out of the Box
Motorola
RUC079
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Notation of certified mailing address
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1026
Out of the Box
Motorola
RUC080
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Name of serving officer
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1027
Out of the Box
Motorola
RUC081
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Badge number
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1028
Out of the Box
Motorola
RUC082
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
EIN
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1029
Out of the Box
Motorola
RUC083
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Agency
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1030
Out of the Box
Motorola
RUC084
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Jurisdiction
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1031
Out of the Box
Motorola
RUC085
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
The system should support numerous data entry
fields related to judicial activities taken on each
civil service.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1032
Out of the Box
Motorola
RUC086
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
The system should support an agency-defined
number of data fields for entering and
automatically totaling cost information regarding
court-related costs and other Maricopa County
information such as:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Costs can be
calculated utilizing an SSRS report.
As part of deployment, Motorola
will apply canned reports to the
system and lead a reporting writing
workshop with County personnel.
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1033
With Configuration
Motorola
RUC087
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Case Disposition
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1034
Out of the Box
Motorola
RUC088
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Hazardous Materials
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1035
Out of the Box
Motorola
RUC089
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
CDL (Commercial Driver's License)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1036
Out of the Box
Motorola
RUC090
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Sentence
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1037
Out of the Box
Motorola
RUC091
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Fine
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1038
Out of the Box
Motorola
RUC092
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Cost
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1039
Out of the Box
Page 60 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RUC093
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
and agency-definable codes such as:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1040
Out of the Box
Motorola
RUC094
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
I.D.#
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1041
Out of the Box
Motorola
RUC095
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Incident#
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1042
Out of the Box
Motorola
RUC096
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Arrestee#
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1043
Out of the Box
Motorola
RUC097
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Weapons at Arrest
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1044
Out of the Box
Motorola
RUC098
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Type of Criminal Activity
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1045
Out of the Box
Motorola
RUC099
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Drug Type
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1046
Out of the Box
Motorola
RUC100
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Mult. CL Indic.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1047
Out of the Box
Motorola
RUC101
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Ethnicity
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1048
Out of the Box
Motorola
RUC102
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Residence
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1049
Out of the Box
Motorola
RUC103
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
Disposition if Under 18, and
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1050
Out of the Box
Motorola
RUC104
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
The ability to track all information related to
attempts to serve Warrants, Orders. Patrol has
requested that this information be available by
location.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1051
Out of the Box
Motorola
RUC105
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
The ability to track all information related to
attempts to serve Warrants, Orders. If there is an
active warrant on someone with a Maricopa
County address, a map layer should be made
available that presents Icons/symbols at these
locations. If an officer clicks on a warrant location
symbol, he or she should see information on the
last time service was attempted at the location.
Since warrant service attempts often do not result
in an IR or FI being created, this information may
require a new disposition code for "Attempted
Warrant Service". If this is the method
recommended by the offeror, we would also want
the officer's disposition notes included in the
retrieval displays.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. PremierOne CAD
utilizes Microsoft SQL Server
Reporting Services (SSRS) for its
standard reports. SSRS is a server-
based reporting platform that is
used to create and manage tabular,
matrix, graphical, dashboards, and
free form reports that contain data
from relational and
multidimensional data sources. As
part of deployment, Motorola will
apply canned reports to the system
and lead a reporting writing
workshop with County personnel.
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. Map layers may be
incorporated into these reports.
1052
With Configuration
Motorola
RUC106
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
The ability to import and attach scanned images of
Warrants, Orders, and Summons to their related
records.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1053
Out of the Box
Motorola
RUC107
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
The ability to capture, store, audit, and track all
information in all data fields contained in each
type of County document above and,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1054
Out of the Box
Motorola
RUC108
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
The ability to easily produce user-defined pre-
formatted and ad-hoc management reports based
on all data fields in the subsystem.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1055
Out of the Box
Motorola
RUC109
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
The system should provide the ability to send
automatic notifications to user-defined persons
when a warrant or civil process order is about to
reach its court ordered expiration date.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1056
Out of the Box
Page 61 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RUC110
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
The system should additionally provide the ability
for users to define the period of time prior to an
expiration date that they desire to be notified.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1057
Out of the Box
Motorola
RUC111
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
When a warrant is served the officer should be
able to retrieve a Warrant Supplement Sheet and
auto-populate it form corresponding fields in the
OR.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1058
Out of the Box
Motorola
RUC112
NIFORM CRIME
REPORTING
(UCR/NIBRS)
General
The system must provide IBR/UCR data validation
in connected mode.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1059
Out of the Box
Motorola
RQDA001
QUERY DATA
ACCESS
General
Simple forms must be provided to the user with
the ability to perform advance forms searches or
keyword searches.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1060
Out of the Box
Motorola
RQDA002
QUERY DATA
ACCESS
General
The free text search must allow users to select
documents created in a specific time period.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1061
Out of the Box
Motorola
RQDA003
QUERY DATA
ACCESS
General
The free text search must allow users to search by
all included words.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1062
Out of the Box
Motorola
RQDA004
QUERY DATA
ACCESS
General
The free text search must allow authorized users
to search for records in a specific agency in a multi-
agency system.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1063
Out of the Box
Motorola
RQDA005
QUERY DATA
ACCESS
General
The free text search must allow authorized users
to search for records in all agencies in a multi-
agency system.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1064
Out of the Box
Motorola
RQDA006
QUERY DATA
ACCESS
General
The free text search must allow authorized users
to search archived records.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1065
Out of the Box
Motorola
RQDA007
QUERY DATA
ACCESS
General
The free text search must allow users to search by
an exact phrase.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1066
Out of the Box
Motorola
RQDA008
QUERY DATA
ACCESS
General
The system must provide the ability for authorized
users to query state and federal databases.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1067
Out of the Box
Motorola
RQDA009
QUERY DATA
ACCESS
General
The query service must record the user, ID, agency
ID, date/time and the queries run.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1068
Out of the Box
Motorola
RQDA010
QUERY DATA
ACCESS
General
The query service must be CJIS compliant.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1069
Out of the Box
Motorola
RQDA011
QUERY DATA
ACCESS
General
The free text search must be able to search for
data in any field including narratives.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1070
Out of the Box
Motorola
RQDA012
QUERY DATA
ACCESS
General
The system must restrict the free text search
results to only include those records which the
user is authorized to access.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1071
Out of the Box
Motorola
RQDA013
QUERY DATA
ACCESS
General
The system shall have the ability to embed digital
photos from all sources and link them with
incident records where applicable.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1072
Out of the Box
Motorola
RQDA014
QUERY DATA
ACCESS
General
The system shall have the ability to perform free
text searches.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1073
Out of the Box
Motorola
RQDA015
QUERY DATA
ACCESS
General
The system must provide soundex or spell-like
search capability.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1074
Out of the Box
Motorola
RQDA016
QUERY DATA
ACCESS
General
The system must provide a single search point for
information retrieval from police records.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1075
Out of the Box
Motorola
RQDA017
QUERY DATA
ACCESS
General
The system shall provide a graphic user interface
that provides user-friendly access to the RMS data.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1076
Out of the Box
Motorola
RQDA018
QUERY DATA
ACCESS
General
The free text search must allow users to search by
any included words.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1077
Out of the Box
Motorola
RQDA019
QUERY DATA
ACCESS
General
The system must provide for the ability to build
and maintain interfaces to multiple, dissimilar,
external data sources.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1078
Out of the Box
Motorola
RRPTNG001
REPORTING
General
The system shall provide standard ODBC
connectivity for any customer provided third party
application.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1079
Out of the Box
Motorola
RRPTNG002
QUERY DATA
ACCESS
General
Reports shall be able to be displayed on-screen or
printed.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1080
Out of the Box
Motorola
RRPTNG003
QUERY DATA
ACCESS
General
The system must provide a separate reporting
database to reduce impact on the production
system.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1081
Out of the Box
Page 62 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RRPTNG004
QUERY DATA
ACCESS
General
The system shall provide the ability to schedule
reports to be run at a specified time.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1082
Out of the Box
Motorola
RRPTNG005
QUERY DATA
ACCESS
General
The system must have the ability to post data to
ancillary crime reporting products such as Crime
Reports or Command Central
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1083
Out of the Box
Motorola
RRPTNG006
QUERY DATA
ACCESS
General
The system shall provide tools to generate user-
defined, customized screens, forms and reports.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1084
Out of the Box
Motorola
RRPTNG007
QUERY DATA
ACCESS
General
The system must automatically generate report
data model files to assist users in creating reports.
These must be generated for all modules including
those configured by the agency.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1085
Out of the Box
Motorola
RRPTNG008
QUERY DATA
ACCESS
General
The system must automatically synchronize data
between the production and reporting databases.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1086
Out of the Box
Motorola
RRPTNG009
QUERY DATA
ACCESS
General
The reporting database must limit access to
personally identifiable information (name, DOB,
SSN, etc.) to reduce the chance of improper
dissemination.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1087
Out of the Box
Motorola
RRPTNG010
QUERY DATA
ACCESS
General
The reporting database must provide a database
schema optimized for reporting and not simply a
copy of the production database.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1088
Out of the Box
Motorola
RRPTNG011
QUERY DATA
ACCESS
General
The system must not allow any reports, queries or
third party applications that are run against the
reporting database to affect the performance of
the production system.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1089
Out of the Box
Motorola
RRPTNG012
QUERY DATA
ACCESS
General
The reporting database must be able to be located
on a separate database server if desired to reduce
storage costs.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1090
Out of the Box
Motorola
RRPTNG013
QUERY DATA
ACCESS
General
The system shall provide the ability to download
statistical data to an off-the-shelf spreadsheet
program (such as 'xls' or 'dbf' format).
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1091
Out of the Box
Motorola
RRPTNG014
QUERY DATA
ACCESS
General
The system shall have the ability to perform free
text searches.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1092
Out of the Box
Motorola
RRPTNG015
QUERY DATA
ACCESS
General
The system must provide soundex or spell-like
search capability.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1093
Out of the Box
Motorola
RRPTNG016
QUERY DATA
ACCESS
General
The system must provide a single search point for
information retrieval from police records.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1094
Out of the Box
Motorola
RRPTNG017
QUERY DATA
ACCESS
General
The system shall provide a graphic user interface
that provides user-friendly access to the RMS data.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1095
Out of the Box
Motorola
RRPTNG018
QUERY DATA
ACCESS
General
The free text search must allow users to search by
any included words.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1096
Out of the Box
Motorola
RRPTNG019
QUERY DATA
ACCESS
General
The system must provide for the ability to build
and maintain interfaces to multiple, dissimilar,
external data sources.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1097
Out of the Box
Motorola
RPE001
PROPERTY AND
EVIDENCE
General
MCSO is presently using QueTel barcode and
property management/tracking systems that are
meeting their current needs. Vendors who can bid
their barcode and property management modules
as optional separately priced systems are being
asked to do so. MCSO wants to determine if
vendors can offer property management systems
with enough additional functionality/value to
warrant replacing their current systems. Vendors
who can offer their property systems as optional
modules, are being asked to bid converting the
legacy data in the QueTel system.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1098
Out of the Box
Motorola
RPE002
PROPERTY AND
EVIDENCE
General
At minimum the RMS solution needs to properly
integrate with Quetel - Digital evidence capabilities
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Motorola has
included an interface to QueTel
Property and Evidence.
1099
Out of the Box
Page 63 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RPE003
PROPERTY AND
EVIDENCE
General
The proposed system's Property Module should
provides users with a central repository for
recording, tracking, and reporting detailed
information about all property that comes into the
custody of the department. The desired functions
of this module include the following.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1100
Out of the Box
Motorola
RPE004
PROPERTY AND
EVIDENCE
General
Barcode Tracking: The utilization of barcodes
should provide quick, key-less, and error-free
retrieval and transfer capability to the user. The
system should be capable of managing property
and evidence items, boxes, and storage locations
using barcodes.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1101
Out of the Box
Motorola
RPE005
PROPERTY AND
EVIDENCE
General
Barcode Label Design and Printing: The system
should have the capability to automatically
generate a unique barcode for each item entered
into the system.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1102
Out of the Box
Motorola
RPE006
PROPERTY AND
EVIDENCE
General
The system should provide the ability to
automatically define the starting number for item
barcodes to be generated.
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met. Requirement
will be met by interface with Qtel.
1103
Cannot Meet
Motorola
RPE007
PROPERTY AND
EVIDENCE
General
The system should also provide the ability for
property and evidence management staff to
define the starting numbers for barcodes to be
generated.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1104
Out of the Box
Motorola
RPE008
PROPERTY AND
EVIDENCE
General
The system should provide a barcode label design
wizard that allows for the designing of barcode
labels with text for property and evidence items,
boxes, and locations. These labels should be
capable of being printed - one at a time or in
batches - directly from the application to any user-
defined printer.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1105
Out of the Box
Motorola
RPE009
PROPERTY AND
EVIDENCE
General
Importing: The system should have an import
utility that allows records to be imported
seamlessly from all reports produced in the RMS
and FBR applications
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1106
Out of the Box
Motorola
RPE010
PROPERTY AND
EVIDENCE
General
The system should also allow for the updating of
current records within the application.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1107
Out of the Box
Motorola
RPE011
PROPERTY AND
EVIDENCE
General
The importing of existing data from the RMS (FBR
for example) should also provide field data type
validation, duplicated record validation, and data
validation. To ensure data integrity the import
utility should enforce the same data entry rules
established by the system's user interface for
related functional modules.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1108
Out of the Box
Motorola
RPE012
PROPERTY AND
EVIDENCE
General
Exporting: The application should have an export
utility that allows users to create, save, and run
any number of export routines. Any and all data
should be able to be exported from the
application’s database.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1109
Out of the Box
Motorola
RPE013
PROPERTY AND
EVIDENCE
General
The system should have the following minimum
search and request capabilities:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1110
Out of the Box
Motorola
RPE014
PROPERTY AND
EVIDENCE
General
Query-by-Example: The system should provide the
ability to search from the main screen by providing
an example – including wildcards -- for a single
field or for multiple fields. This functionality
should include the use of such tools as date
ranges, pick lists, and free form text.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1111
Out of the Box
Motorola
RPE015
PROPERTY AND
EVIDENCE
General
Query-by-Date: The system should provide the
ability to perform searches including, but not
limited to, by date ranges for Date Created, Edit
Date, Transfer Date, Check-out Date, Recovering
Officer, Incident Report Number, etc.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1112
Out of the Box
Motorola
RPE016
PROPERTY AND
EVIDENCE
General
Query-by-Location: The system should provide
the ability to perform searches by locations. A
location may be defined as a place such as a
freezer, a rifle rack, drug lab, shelf, etc.
(Individuals can also be defined as locations, such
as Captain Smith, County attorney, or prosecuting
attorney).
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1113
Out of the Box
Page 64 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RPE017
PROPERTY AND
EVIDENCE
General
Query by Identification Number: The system
should have the ability to enter, maintain, track,
and query other agency property
tracking/identification numbers, or any other
system administrator defined tracking numbers.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1114
Out of the Box
Motorola
RPE018
PROPERTY AND
EVIDENCE
General
The results of all queries performed should be
exportable into industry standard common
formats including EXCEL, CSV, etc.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1115
Out of the Box
Motorola
RPE019
PROPERTY AND
EVIDENCE
General
The system should provide the ability for users to
search and request items within the system. For
example, this function should identify the
requestor, date requested, reason, and date
required.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1116
Out of the Box
Motorola
RPE020
PROPERTY AND
EVIDENCE
General
The system should also provide the ability for
evidence technicians to view, sort and print a
“pending requests” report – complete with
location barcodes of the requestors -- in order to
fulfill incoming requests using portable barcode
scanners.
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met. Requirement
will be met by interface with Qtel.
1117
Cannot Meet
Motorola
RPE021
PROPERTY AND
EVIDENCE
General
This “request” functionality should be able to be
configured to automatically print in-coming
requests based on identified requestors and/or
dates.
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met. Requirement
will be met by interface with Qtel.
1118
Cannot Meet
Motorola
RPE022
PROPERTY AND
EVIDENCE
General
The “request" screen should also have the ability
to be left open in a separate window while a user
is performing other functions within the
application.
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met. Requirement
will be met by interface with Qtel.
1119
Cannot Meet
Motorola
RPE023
PROPERTY AND
EVIDENCE
General
Standard Reports: The system should provide
standard and configurable property and evidence
management reports including but not limited to:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1120
Out of the Box
Motorola
RPE024
PROPERTY AND
EVIDENCE
General
Inventory Report: Lists all of the items located at
each location specified in the report.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1121
With Configuration
Page 65 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RPE025
PROPERTY AND
EVIDENCE
General
Query Report: Reports on the specific selection of
records returned as a result of a query or a search.
For example the number of handguns taken into
custody for a specified date range, etc.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1122
With Configuration
Motorola
RPE026
PROPERTY AND
EVIDENCE
General
Audit Report: Shows the audit trail for all items by
location and lists every location the item has been,
the user who transferred the item, and the date &
time the item was transferred.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1123
With Configuration
Motorola
RPE027
PROPERTY AND
EVIDENCE
General
Items Out Report: Lists all items checked out of
the default locations (set in the workstation
settings), typically the main property room.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1124
With Configuration
Motorola
RPE028
PROPERTY AND
EVIDENCE
General
Wait List Report: Lists the items that are flagged
with a pending action, e.g., all items that have an
action or are on a waiting list.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1125
With Configuration
Page 66 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RPE029
PROPERTY AND
EVIDENCE
General
User Report: Shows a list of users and all of their
permissions.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1126
With Configuration
Motorola
RPE030
PROPERTY AND
EVIDENCE
General
Retention Code: Lists all of the
retention/disposition codes and the rules that are
listed in the system that can be applied to
individual items.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1127
With Configuration
Motorola
RPE031
PROPERTY AND
EVIDENCE
General
Retention Review: Report based on the
retention/disposition code assigned to them, lists
all items within a selected date range that are
eligible for review and possible destruction.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1128
With Configuration
Motorola
RPE032
PROPERTY AND
EVIDENCE
General
The system should be capable of automatically
preparing and submitting (via e-mail) user-
definable reports including e-mail notifications, to
system users. This includes notifications to users
informing them that action is required on their
part with respect to property that is in storage
(e.g. to obtain a property release or that a stored
property is about to reach its maximum required
storage time).
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1129
With Configuration
Page 67 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RPE033
PROPERTY AND
EVIDENCE
General
The system should provide the ability to send user-
definable notifications to alert (remind) employees
that property is being held in temporary storage
locations (evidence drying room, vehicle bay, etc.)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1130
With Configuration
Motorola
RPE034
PROPERTY AND
EVIDENCE
General
Forms and Letters: The system should provide the
ability to automate the generation and timing of
Forms and Letters that the department currently
produces manually and electronically.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1131
With Configuration
Motorola
RPE035
PROPERTY AND
EVIDENCE
General
Box/Container Tracking: The system should utilize
barcodes to track property and evidence items in
and out of boxes and/or containers, as well as, the
boxes/containers themselves as they move back
and forth between locations. This will allow the
department to know exactly which items are in
which boxes/containers -- eliminating the need to
retrieve and search through a series of
boxes/containers in order to find an item
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met. Requirement
will be met by interface with Qtel.
1132
Cannot Meet
Motorola
RPE036
PROPERTY AND
EVIDENCE
General
Retention/Disposition: Users should to be able to
apply the department's retention and disposition
schedule to their property and evidence items. A
retention and disposition schedule declares the
length of time items should be kept in order to
comply with state and federal regulatory
requirements. The retention and disposition
schedule ensures that items are maintained as
long as they are needed or as the law requires.
The schedule then provides approved directives
for the review and disposition of property and
evidence items at appropriate intervals. The
system should provide the following
retention/disposition functionality:
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met. Requirement
will be met by interface with Qtel.
1133
Cannot Meet
Motorola
RPE037
PROPERTY AND
EVIDENCE
General
The ability for users to create and maintain
retention/disposition codes, such as:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1134
Out of the Box
Motorola
RPE037-1
PROPERTY AND
EVIDENCE
General
Code
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1135
Out of the Box
Motorola
RPE037-2
PROPERTY AND
EVIDENCE
General
Category
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1136
Out of the Box
Motorola
RPE037-3
PROPERTY AND
EVIDENCE
General
Description
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1137
Out of the Box
Motorola
RPE037-4
PROPERTY AND
EVIDENCE
General
Retention period definable in years, months, and
days,
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met. Requirement
will be met by interface with Qtel.
1138
Cannot Meet
Page 68 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RPE037-5
PROPERTY AND
EVIDENCE
General
Calculation triggers using item’s creation date or
another defined date, such as date case was
closed
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1139
Out of the Box
Motorola
RPE037-6
PROPERTY AND
EVIDENCE
General
Ability to apply a retention/disposition code to
each item logged into the system
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1140
Out of the Box
Motorola
RPE037-7
PROPERTY AND
EVIDENCE
General
System to automatically calculate a review date
for an item based on its retention/disposition code
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1141
Out of the Box
Motorola
RPE037-8
PROPERTY AND
EVIDENCE
General
Ability to put a “hold” on an item scheduled for
destruction, forfeiture, department use.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1142
Out of the Box
Motorola
RPE037-9
PROPERTY AND
EVIDENCE
General
Report to list all items eligible for destruction or
auction, filtered by retention/disposition code and
review date range
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1143
With Configuration
Motorola
RPE037-10
PROPERTY AND
EVIDENCE
General
Report to list all retention/disposition codes
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1144
With Configuration
Motorola
RPE038
PROPERTY AND
EVIDENCE
General
Home Location: Each item should to have a clearly
defined Home Location (a location where it should
be returned after a user is finished with it.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1145
Out of the Box
Motorola
RPE039
PROPERTY AND
EVIDENCE
General
Audit Trail/Chain of Custody: The system should
have the ability to automatically create, store, and
update a complete and unalterable audit trail for
each item logged into the system. For chain of
custody purposes it should keeps track of the
current location of an item, as well as every
location the item has resided since it was
collected. With each transfer -- initiated either
with a barcode scanner or through any other
transfer process -- the system should
automatically record the date and time when an
item was moved, to whom or where, and by
whom. The audit trail should be unalterable in
order to preserve the integrity of an item’s chain
of custody.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1146
Out of the Box
Page 69 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RPE040
PROPERTY AND
EVIDENCE
General
Field-level Auditing: The system should be able to
track any and all changes made to an index field. If
a change is made to an index field, the system
needs to record and store the date and time the
change was made, the name of the user who
made the change, and the old value, as well as, the
new value for that field. This field audit
information should be unalterable in order to
preserve the integrity of an item’s chain of
custody. A report to print out this audit
information should also be provided.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1147
Out of the Box
Motorola
RPE041
PROPERTY AND
EVIDENCE
General
Signature Capture: The system should have the
ability to capture a digital signature, on a signature
pad connected to the computer via a serial port,
when performing a Check-in/Check-out of an
item(s). The captured signature should be stored
as part of the audit trail for an item. The system
should also be able to print out a receipt listing the
items transferred and the signature of the person
receiving the items through the Check-in/Check-
out process.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1148
Out of the Box
Motorola
RPE042
PROPERTY AND
EVIDENCE
General
E-Mail Integration: The system should be capable
of integration with the County’s Microsoft
exchange server to allow for distribution of
property notices such as; Fail to Return Items
Notice, Evidence Disposition Updates, and
Destruction Notices.
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met. Requirement
will be met by interface with Qtel.
1149
Cannot Meet
Motorola
RPE043
PROPERTY AND
EVIDENCE
General
Electronic Document Management: The system
should have the ability to save, request view,
deliver and manage documents that are in
electronic format such as scanned images, digital
pictures, word processor documents, voice clips
such as 911 calls and digital video. Examples of
capabilities desired are the abilities to:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1150
With Configuration
Motorola
RPE043-1
PROPERTY AND
EVIDENCE
General
Attach, Save, Check-in/Check-out, version control
and audit of digital media.
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met. Evidence.com
API will be used for this
requirement.
1151
Cannot Meet
Motorola
RPE043-2
PROPERTY AND
EVIDENCE
General
Attach digital photos, voice and video recordings.
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met. Evidence.com
API will be used for this
requirement.
1152
Cannot Meet
Motorola
RPE043-3
PROPERTY AND
EVIDENCE
General
Scan, save and attach reports to the record for
quick retrieval and viewing
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met. Scan and
attach would be handled via link
on the Evidence.com vault and
shared via link on RMS.
1153
Cannot Meet
Motorola
RPE043-4
PROPERTY AND
EVIDENCE
General
Produce forms for tracking a history of drug
weights and currency value throughout the chain
of custody
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1154
Out of the Box
Motorola
RPE043-5
PROPERTY AND
EVIDENCE
General
Capture an image of signed paper documents.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.PremierOne Records
Users can scan and attach
documents.
1155
Out of the Box
Motorola
RPE044
PROPERTY AND
EVIDENCE
General
The system should have the ability to link case and
property information. For example, to permit one
officer who is retrieving evidence from several
different cases to sign-out the property, linking all
case property information to the retrieving officer
for property tracking and searching.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1156
Out of the Box
Page 70 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RPE045
PROPERTY AND
EVIDENCE
General
Automobiles and other vehicle types that are
impounded as evidence must also be managed by
MCSO Property. Vendors are asked to provide
detailed information on how their systems process
vehicles. How are they processed similar to an
ordinary property item, and how are they process
differently.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Vehicles are
processed the same way as other
evidence items.
1157
Out of the Box
Motorola
RPE046
PROPERTY AND
EVIDENCE
General
The system must enable releasing and disposition
tracking of all categories of property.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1158
Out of the Box
Motorola
RPE047
PROPERTY AND
EVIDENCE
General
The system must manage categories of property,
including pawned, evidence, recovered, and
found.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1159
Out of the Box
Motorola
RPE048
PROPERTY AND
EVIDENCE
General
Categories of property must be interrelated within
the system.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1160
Out of the Box
Motorola
RPE049
PROPERTY AND
EVIDENCE
General
The system must track and index stolen and lost
property.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1161
Out of the Box
Motorola
RPE050
PROPERTY AND
EVIDENCE
General
The system must assign property identification
numbers.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1162
Out of the Box
Motorola
RPE051
PROPERTY AND
EVIDENCE
General
The system must allow the agency to modify bar
code labels to meet the agency's policies.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1163
Out of the Box
Motorola
RPE052
PROPERTY AND
EVIDENCE
General
The system must allow authorized users to print a
property receipt on scene without network
connectivity.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1164
Out of the Box
Motorola
RPE053
PROPERTY AND
EVIDENCE
General
The system must allow the agency to modify the
property receipt to meet the agency's policies.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1165
Out of the Box
Motorola
RPE054
PROPERTY AND
EVIDENCE
General
The system must allow authorized users to dispose
of or release items and track the details of the
disposal or release.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1166
Out of the Box
Motorola
RPE055
PROPERTY AND
EVIDENCE
General
All property and person information from a case
must be able to be pulled into a property sheet
without reentry of data.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1167
Out of the Box
Motorola
RPE056
PROPERTY AND
EVIDENCE
General
Tags must be capable of being created for all
property items complete with bar code labels for
easier tracking and auditing.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1168
Out of the Box
Motorola
RPE057
PROPERTY AND
EVIDENCE
General
The system must have the ability to capture
location and tag numbers so that property can be
located in the property room.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1169
Out of the Box
Motorola
RPE058
PROPERTY AND
EVIDENCE
General
The system must have the ability to track the
location of all evidence related to a given case
number.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1170
Out of the Box
Motorola
RPE059
PROPERTY AND
EVIDENCE
General
The system must be able to track all names of
persons associated with the property and the
relationship of the persons to the property.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1171
Out of the Box
Motorola
RPE060
PROPERTY AND
EVIDENCE
General
The property room management module shall
allow the user to search for a property item by
descriptive data (make, module, serial number) or
by case number.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1172
Out of the Box
Motorola
RPE061
PROPERTY AND
EVIDENCE
General
The system will allow the user to select several
items within a case for movement, check-out,
check-in, and/or disposal.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1173
Out of the Box
Motorola
RPE062
PROPERTY AND
EVIDENCE
General
The system must allow authorized users to mark
items for disposal / release individually or in a
batch based on sheet or case number.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1174
Out of the Box
Motorola
RPE063
PROPERTY AND
EVIDENCE
General
The system must allow authorized users to create
a property sheet in the Field Based Reporting
system.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1175
Out of the Box
Motorola
RPE064
PROPERTY AND
EVIDENCE
General
The system must provide a property sheet to
record information about the property collected.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1176
Out of the Box
Motorola
RPE065
PROPERTY AND
EVIDENCE
General
The system shall track the chain of custody for all
items within the property room management
module.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1177
Out of the Box
Motorola
RPE066
PROPERTY AND
EVIDENCE
General
The system must be able to generate transactions
for individual items or user selected groups of
items.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1178
Out of the Box
Motorola
RPE067
PROPERTY AND
EVIDENCE
General
The system must provide the ability to capture
information about lost / stolen property and
evidence.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1179
Out of the Box
Motorola
RPE068
PROPERTY AND
EVIDENCE
General
The system must allow authorized users to create
a property sheet on-scene without network
connectivity.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1180
Out of the Box
Page 71 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RPE069
PROPERTY AND
EVIDENCE
General
The items entered into the property sheet must
automatically post to the Master Property Index.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1181
Out of the Box
Motorola
RPE070
PROPERTY AND
EVIDENCE
General
The system mustt indentify numbers including
serial numbers, owner applied numbers, license
numbers, etc.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1182
Out of the Box
Motorola
RPE071
PROPERTY AND
EVIDENCE
General
The property sheet shall contain information
specific to motor vehicles.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1183
Out of the Box
Motorola
RPE072
PROPERTY AND
EVIDENCE
General
The property sheet shall contain information
about where the property was recovered from
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1184
Out of the Box
Motorola
RPE073
PROPERTY AND
EVIDENCE
General
The property sheet shall contain the ability to
display the entire chain of custody for each item of
property.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1185
Out of the Box
Motorola
RPE074
PROPERTY AND
EVIDENCE
General
The system must provide the ability to send a
notification to the investigative officer or others
after an agency determined time period.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1186
Out of the Box
Motorola
RPE075
PROPERTY AND
EVIDENCE
General
The property sheet shall contain information
about the offense associated with the item of
property.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1187
Out of the Box
Motorola
RPE076
PROPERTY AND
EVIDENCE
General
A user entering data into the property sheet must
be able to see potential matching property items
in the Master Property Index.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1188
Out of the Box
Motorola
RPE077
PROPERTY AND
EVIDENCE
General
The system must allow a user to perform actions
on the items individually or in batches.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1189
Out of the Box
Motorola
RPE078
PROPERTY AND
EVIDENCE
General
The system must allow a user to select items for
processing by tag number, property sheet number
or case number.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1190
Out of the Box
Motorola
RPE079
PROPERTY AND
EVIDENCE
General
The system must allow authorized users to check-
in one or more items of property.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1191
Out of the Box
Motorola
RPE080
PROPERTY AND
EVIDENCE
General
The system must allow authorized users to check-
out one or more items of property.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1192
Out of the Box
Motorola
RPE081
PROPERTY AND
EVIDENCE
General
The system must allow authorized users to change
locations (move) one or more items of property at
a time.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1193
Out of the Box
Motorola
RPE082
PROPERTY AND
EVIDENCE
General
The system must allow authorized users to print a
disposal order individually or in a batch based on
sheet or case number.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1194
Out of the Box
Motorola
RPE083
PROPERTY AND
EVIDENCE
General
The system must allow authorized users to print
bar code labels individually or in batch based on
sheet or case number.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1195
Out of the Box
Motorola
RPE084
PROPERTY AND
EVIDENCE
General
The system must be able to perform an inventory
audit using a bar code reader.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1196
Out of the Box
Motorola
RPE085
PROPERTY AND
EVIDENCE
General
The user must have the ability to pull in all items
of property entered into a property sheet into a
case report.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1197
Out of the Box
Motorola
RPE086
PROPERTY AND
EVIDENCE
General
The system must allow the agency to modify
recovery letters.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1198
Out of the Box
Motorola
RPE087
PROPERTY AND
EVIDENCE
General
The system must provide an audit function that
will track missing or misplaced items.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1199
Out of the Box
Motorola
RPE088
PROPERTY AND
EVIDENCE
General
The user must have the ability to pull in all items
of property already entered into a case report into
the property sheet.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1200
Out of the Box
Motorola
RPE089
PROPERTY AND
EVIDENCE
General
When checking-in an item the system should
default to the home location.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1201
Out of the Box
Motorola
RPE090
PROPERTY AND
EVIDENCE
General
The system must allow authorized users to print a
chain of custody report individually or in a batch
based on sheet or case number.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1202
Out of the Box
Motorola
RPE091
PROPERTY AND
EVIDENCE
General
The system must allow authorized users to print
disposal notification letters individually or in a
batch based on sheet or case number.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1203
Out of the Box
Motorola
RPE092
PROPERTY AND
EVIDENCE
General
The system must allow the agency to modify
disposal notification letters
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1204
Out of the Box
Motorola
RPE093
PROPERTY AND
EVIDENCE
General
The system must allow authorized users to print
bar code labels on scene and without network
connectivity.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1205
Out of the Box
Page 72 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RPE094
PROPERTY AND
EVIDENCE
General
The property sheet shall contain information
including the case number, subject, type Incident
number and submitting officer.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1206
Out of the Box
Motorola
RPE095
PROPERTY AND
EVIDENCE
General
The property sheet shall contain information
about assisting officers, case officer and
submission date.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1207
Out of the Box
Motorola
RPE096
PROPERTY AND
EVIDENCE
General
The property sheet shall provide the ability to
capture information about the initial holding
location, locker number and other information
about the property prior to its acceptance by the
property room.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1208
Out of the Box
Motorola
RPE097
PROPERTY AND
EVIDENCE
General
The system must track both the home and current
location.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1209
Out of the Box
Motorola
RPE098
PROPERTY AND
EVIDENCE
General
The system must allow authorized users to print
recovery letters individually or in a batch based on
sheet or case number.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1210
Out of the Box
Motorola
RPE099
PROPERTY AND
EVIDENCE
General
The property sheet shall provide the ability to
capture information about all involved people and
their relationship to the property, owner, dealer,
etc.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1211
Out of the Box
Motorola
RPE100
PROPERTY AND
EVIDENCE
General
The property sheet shall contain the following
information about each item of property:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1212
Out of the Box
Motorola
RPE101
PROPERTY AND
EVIDENCE
General
Storage Location
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1213
Out of the Box
Motorola
RPE102
PROPERTY AND
EVIDENCE
General
Recovered for other Jurisdiction and the other
agency identifier
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1214
Out of the Box
Motorola
RPE103
PROPERTY AND
EVIDENCE
General
Lab Processing Required
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1215
Out of the Box
Motorola
RPE104
PROPERTY AND
EVIDENCE
General
Scheduled Purge Date
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1216
Out of the Box
Motorola
RPE105
PROPERTY AND
EVIDENCE
General
Disposal Method
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1217
Out of the Box
Motorola
RPE106
PROPERTY AND
EVIDENCE
General
Biohazard
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1218
Out of the Box
Motorola
RPE107
PROPERTY AND
EVIDENCE
General
Value
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1219
Out of the Box
Motorola
RPE108
PROPERTY AND
EVIDENCE
General
Quantity
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1220
Out of the Box
Motorola
RPE109
PROPERTY AND
EVIDENCE
General
Manufacturer
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1221
Out of the Box
Motorola
RPE110
PROPERTY AND
EVIDENCE
General
Next Review Date
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1222
Out of the Box
Motorola
RPE111
PROPERTY AND
EVIDENCE
General
Property Type, Category and Description
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1223
Out of the Box
Motorola
RPE112
PROPERTY AND
EVIDENCE
General
Lab Number
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1224
Out of the Box
Motorola
RPE113
PROPERTY AND
EVIDENCE
General
Expected Return date if out
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1225
Out of the Box
Motorola
RPE114
PROPERTY AND
EVIDENCE
General
The property sheet shall contain information
about each piece of property including an auto or
manually generated tag number.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1226
Out of the Box
Motorola
RPE115
PROPERTY AND
EVIDENCE
General
Each agency shall have the ability to configure
property and evidence printouts
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1227
Out of the Box
Motorola
RRR001
REGISTRANT AND
REGISTRATION
TRACKING /
LICENSEE AND
LICENSEE
TRACKING
General
MCSO is presently using a vendor supplied Sex
Offender Tracking System that is meeting it needs.
Vendors who can offer registrant tracking systems
are asked to propose solutions for
registering/tracking pawn shops, adult businesses,
marijuana dispensaries, and other needs not
associated with sex offenders. MCSO is required
by State Statute to license and register Pawn
Shops and track their business activities.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1228
Out of the Box
Page 73 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RRR002
REGISTRANT AND
REGISTRATION
TRACKING /
LICENSEE AND
LICENSEE
TRACKING
General
MCSO's Pawnshop responsibilities are as follows:
Mandatory
Records
X
PremierOne does not have this
functionality. Motorola has
included a Pawn inbound interface
with the solution for reviewing
Pawned items.
MCSO team stated this is not
required to be met.
1229
Cannot Meet
Motorola
RRR002-1
REGISTRANT AND
REGISTRATION
TRACKING /
LICENSEE AND
LICENSEE
TRACKING
General
The ability for users to create and maintain
retention/disposition codes, such as:
Mandatory
Records
X
PremierOne does not have this
functionality. Motorola has
included a Pawn inbound interface
with the solution for reviewing
Pawned items.
MCSO team stated this is not
required to be met.
1230
Cannot Meet
Motorola
RRR002-1-1
REGISTRANT AND
REGISTRATION
TRACKING /
LICENSEE AND
LICENSEE
TRACKING
General
Coordinates all license suspension hearings
between pawnshops and other law enforcement
agencies.
Mandatory
Records
X
PremierOne does not have this
functionality. Motorola has
included a Pawn inbound interface
with the solution for reviewing
Pawned items.
MCSO team stated this is not
required to be met.
1231
Cannot Meet
Motorola
RRR002-1-2
REGISTRANT AND
REGISTRATION
TRACKING /
LICENSEE AND
LICENSEE
TRACKING
General
Enters pawn tickets into the Maricopa County
Pawn System (system to be replaced,
specifications herein).
Mandatory
Records
X
PremierOne does not have this
functionality. Motorola has
included a Pawn inbound interface
with the solution for reviewing
Pawned items.
MCSO team stated this is not
required to be met.
1232
Cannot Meet
Motorola
RRR002-1-3
REGISTRANT AND
REGISTRATION
TRACKING /
LICENSEE AND
LICENSEE
TRACKING
General
Checks pawned items and pawn customers
through ACIC/NCIC for stolen property hits and
outstanding warrants.
Mandatory
Records
X
PremierOne does not have this
functionality. Motorola has
included a Pawn inbound interface
with the solution for reviewing
Pawned items.
MCSO team stated this is not
required to be met.
1233
Cannot Meet
Motorola
RRR002-1-4
REGISTRANT AND
REGISTRATION
TRACKING /
LICENSEE AND
LICENSEE
TRACKING
General
Assists Property Crimes Detectives with their cases
and prepares paperwork to facilitate property
being released to its rightful owners.
Mandatory
Records
X
PremierOne does not have this
functionality. Motorola has
included a Pawn inbound interface
with the solution for reviewing
Pawned items.
MCSO team stated this is not
required to be met.
1234
Cannot Meet
Motorola
RRR002-1-5
REGISTRANT AND
REGISTRATION
TRACKING /
LICENSEE AND
LICENSEE
TRACKING
General
Inspects Pawn Shops for stolen property and
proper documentation.
Mandatory
Records
X
PremierOne does not have this
functionality. Motorola has
included a Pawn inbound interface
with the solution for reviewing
Pawned items.
MCSO team stated this is not
required to be met.
1235
Cannot Meet
Motorola
RRR002-1-6
REGISTRANT AND
REGISTRATION
TRACKING /
LICENSEE AND
LICENSEE
TRACKING
General
Completes administrative duties related to the
recovery of stolen property recovered in
Pawnshops, including the placing of holds on such
property.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1236
Out of the Box
Motorola
RRR002-1-7
REGISTRANT AND
REGISTRATION
TRACKING /
LICENSEE AND
LICENSEE
TRACKING
General
Flags stolen property in the MCSO Pawn System as
having matched a pawned entry.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1237
Out of the Box
Motorola
RRR002-1-8
REGISTRANT AND
REGISTRATION
TRACKING /
LICENSEE AND
LICENSEE
TRACKING
General
Mails out license renewal letters annually.
Mandatory
Records
X
PremierOne does not have this
functionality. Motorola has
included a Pawn inbound interface
with the solution for reviewing
Pawned items.
MCSO team stated this is not
required to be met.
1238
Cannot Meet
Motorola
RRR002-1-9
REGISTRANT AND
REGISTRATION
TRACKING /
LICENSEE AND
LICENSEE
TRACKING
General
Tracks and responds to situations where Pawn
Shops are operating without being licensed.
Mandatory
Records
X
PremierOne does not have this
functionality. Motorola has
included a Pawn inbound interface
with the solution for reviewing
Pawned items.
MCSO team stated this is not
required to be met.
1239
Cannot Meet
Page 74 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RRR003
REGISTRANT AND
REGISTRATION
TRACKING /
LICENSEE AND
LICENSEE
TRACKING
General
Vendors are being asked to respond to the MCSO's
Pawn Shop administrative requirements either
within this Section or within their response to a
new Pawn Subsystem below. Any response to this
Section should include the following functionality:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1240
Out of the Box
Motorola
RRR003-1
REGISTRANT AND
REGISTRATION
TRACKING /
LICENSEE AND
LICENSEE
TRACKING
General
The system should provide an automated process
to monitor the application, approval and past
history of permits and licenses.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1241
Out of the Box
Motorola
RRR003-2
REGISTRANT AND
REGISTRATION
TRACKING /
LICENSEE AND
LICENSEE
TRACKING
General
The system should provide the ability to create,
maintain, and search numerous data elements of
agency-definable information on all permits and
licenses issued by the MCSO..
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1242
Out of the Box
Motorola
RRR003-3
REGISTRANT AND
REGISTRATION
TRACKING /
LICENSEE AND
LICENSEE
TRACKING
General
Maintain complaints and inspection memoranda
for all licensee locations.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1243
Out of the Box
Motorola
RRR003-4
REGISTRANT AND
REGISTRATION
TRACKING /
LICENSEE AND
LICENSEE
TRACKING
General
Be able to schedule events tied to any licensee
and/or licensee location and obtain event
reminders.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1244
Out of the Box
Motorola
RRR003-5
REGISTRANT AND
REGISTRATION
TRACKING /
LICENSEE AND
LICENSEE
TRACKING
General
Allow notices to be created and sent to other
internal (MCSO) and external County agencies.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1245
Out of the Box
Motorola
RRR003-6
REGISTRANT AND
REGISTRATION
TRACKING /
LICENSEE AND
LICENSEE
TRACKING
General
Automate the creation of documents that must be
mailed and generate notices that can be sent vie E-
Mail.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1246
Out of the Box
Motorola
RRR003-7
REGISTRANT AND
REGISTRATION
TRACKING /
LICENSEE AND
LICENSEE
TRACKING
General
Allow all actions (i.e. placing a verbal hold on a
piece of property) to be recorded as a memo entry
and associated with the business/licensee address.
Allow all actions to be tracked and reported.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1247
Out of the Box
Motorola
RRR003-8
REGISTRANT AND
REGISTRATION
TRACKING /
LICENSEE AND
LICENSEE
TRACKING
General
Allow receipts for payments to be created and
recorded. The system should capture and record
all funds received and transferred to Fiscal
Management.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. The PremierOne
Records Advanced Configuration
Tool (ACT) and Microsoft SQL
Server Reporting Services (SSRS) are
included in this solution and can be
used to meet this requirement.
ACT provides agencies with the
ability to create their own fully
functional modules, as well as
modify existing PremierOne
modules without source code
changes, reducing your total cost of
ownership.
PremierOne reports can be
developed by MCSO report
developers or analysts using SSRS
to provide any necessary billing
reports.
1248
With Configuration
Page 75 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RRR003-9
REGISTRANT AND
REGISTRATION
TRACKING /
LICENSEE AND
LICENSEE
TRACKING
General
The system should have the ability to maintain
user-definable registrant conviction and location
information by such agency definable data as:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1249
Out of the Box
Motorola
RRR003-9-1
REGISTRANT AND
REGISTRATION
TRACKING /
LICENSEE AND
LICENSEE
TRACKING
General
Conviction, jurisdiction, and case number,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1250
Out of the Box
Motorola
RRR003-9-2
REGISTRANT AND
REGISTRATION
TRACKING /
LICENSEE AND
LICENSEE
TRACKING
General
Prior addresses,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1251
Out of the Box
Motorola
RRR003-9-3
REGISTRANT AND
REGISTRATION
TRACKING /
LICENSEE AND
LICENSEE
TRACKING
General
Current address,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1252
Out of the Box
Motorola
RRR003-9-4
REGISTRANT AND
REGISTRATION
TRACKING /
LICENSEE AND
LICENSEE
TRACKING
General
Type of registrant (sex, narcotics, arson, etc.),
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1253
Out of the Box
Motorola
RRR003-9-5
REGISTRANT AND
REGISTRATION
TRACKING /
LICENSEE AND
LICENSEE
TRACKING
General
Last registration date.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1254
Out of the Box
Motorola
RRR004
REGISTRANT AND
REGISTRATION
TRACKING /
LICENSEE AND
LICENSEE
TRACKING
General
Permits and Licensing records shall allow permit
details, licensee details, and affiliations to be
documented.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1255
Out of the Box
Motorola
RRR005
REGISTRANT AND
REGISTRATION
TRACKING /
LICENSEE AND
LICENSEE
TRACKING
General
The Permits and Licensing module shall allow an
agency to track the issuance of all permits and
licenses.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1256
Out of the Box
Motorola
RRR006
REGISTRANT AND
REGISTRATION
TRACKING /
LICENSEE AND
LICENSEE
TRACKING
General
Permit codes, permit types, and license types shall
be able to be defined by an agency and are used in
the permits and licensing module.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1257
Out of the Box
Motorola
RRR007
REGISTRANT AND
REGISTRATION
TRACKING /
LICENSEE AND
LICENSEE
TRACKING
General
Previous arrests and employment history shall be
able to be tracked for both licensee and affiliated
persons.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1258
Out of the Box
Motorola
RPS001
PAWN SUB-
SYSTEM
General
The County wishes to have responding vendors to
offer replacement alternatives for it current and
ageing Regional Pawn System. All vendors need to
bid interfacing their RMS with the existing system
whether or not a replacement system is bid. See
the Interfaces Section of this RFP for further detail.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Motorola has
included a Pawn inbound interface
with the solution.
1259
Out of the Box
Page 76 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RPS002
PAWN SUB-
SYSTEM
General
MCSO is statutorily responsible for registering and
licensing Pawn Shop establishments in the county.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1260
Out of the Box
Motorola
RPS003
PAWN SUB-
SYSTEM
General
MCSO is statutorily responsible for tracking and
managing all Pawn Shop transactions.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1261
Out of the Box
Motorola
RPS004
PAWN SUB-
SYSTEM
General
MCSO has an agreement with other county law
enforcment agencies (Municipal Police Depts.) to
track second hand store sales too. These county
law enforcement agencies currently manage the
registration of second hand stores (MCSO does
not).
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1262
Out of the Box
Motorola
RPS005
PAWN SUB-
SYSTEM
General
The system should include the capability to display
and print a list of potential matches of stolen
property against Pawn subsystem records.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1263
Out of the Box
Motorola
RPS006
PAWN SUB-
SYSTEM
General
The system should include the capability to display
and print a list of potential matches of persons
(customers) or items (property) of interest.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1264
Out of the Box
Motorola
RPS007
PAWN SUB-
SYSTEM
General
MCSO seeks a Pawn Shop application that will:
Mandatory
Records
X
PremierOne does not have this
functionality. Motorola has
included a Pawn inbound interface
with the solution.
MCSO team agrees with
explanation in column N.
1265
Cannot Meet
Motorola
RPS007-1
PAWN SUB-
SYSTEM
General
Conform data entry edits and checking to meet
data requirements of ACIC/NCIC standards.
Mandatory
Records
X
PremierOne does not have this
functionality. Motorola has
included a Pawn inbound interface
with the solution.
MCSO team agrees with
explanation in column N.
1266
Cannot Meet
Motorola
RPS007-2
PAWN SUB-
SYSTEM
General
Provide the ability to Add, Manage, Track, and
Report Pawn Shop registration and licensing
activities.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1267
Out of the Box
Motorola
RPS007-3
PAWN SUB-
SYSTEM
General
Provide the ability to Add, Manage, Track, and
Report Second Hand Store registration.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1268
Out of the Box
Motorola
RPS007-4
PAWN SUB-
SYSTEM
General
Ability to differentiate between Pawn Shop
Facilities and Second Hand Store Facilities (flag).
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1269
Out of the Box
Motorola
RPS007-5
PAWN SUB-
SYSTEM
General
Provide security such that only MCSO users can
Add/Maintain Pawn Shop facilities.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1270
Out of the Box
Motorola
RPS007-6
PAWN SUB-
SYSTEM
General
Allow for other county law enforcement agencies
to Add/Maintain Second Hand Shop facilities.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. With PremierOne
Mobile, other authorized users can
add registrations into the system.
1271
Out of the Box
Motorola
RPS007-7
PAWN SUB-
SYSTEM
General
Provide the ability to Add, Manage, Track and
Report Pawn Ticket Entries
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1272
Out of the Box
Motorola
RPS007-8
PAWN SUB-
SYSTEM
General
Provide for Customer and Item checks during
Pawn Ticket Entry
Mandatory
Records
X
PremierOne does not have this
functionality. Motorola has
included a Pawn inbound interface
with the solution.
MCSO team agrees with
explanation in column N.
1273
Cannot Meet
Motorola
RPS007-9
PAWN SUB-
SYSTEM
General
An internal comparison of the individual to the
Pawnshop System customer filestop information.
Mandatory
Records
X
PremierOne does not have this
functionality. Motorola has
included a Pawn inbound interface
with the solution.
MCSO team agrees with
explanation in column N.
1274
Cannot Meet
Motorola
RPS007-10
PAWN SUB-
SYSTEM
General
An internal comparison of each identifiable item
of property (i.e. each item having a serial
number and/or owner applied number) to the
Pawnshop System property filestop information.
Mandatory
Records
X
PremierOne does not have this
functionality. Motorola has
included a Pawn inbound interface
with the solution.
MCSO team agrees with
explanation in column N.
1275
Cannot Meet
Motorola
RPS007-11
PAWN SUB-
SYSTEM
General
An external query forwarded to ACIC/NCIC, for
each individual meeting the NCIC requirements.
(Unless overridden by the user.)
Mandatory
Records
X
PremierOne does not have this
functionality. Motorola has
included a Pawn inbound interface
with the solution.
MCSO team agrees with
explanation in column N.
1276
Cannot Meet
Motorola
RPS007-12
PAWN SUB-
SYSTEM
General
An external query forwarded to ACIC/NCIC, for
each item of property meeting the NCIC
requirements.
Mandatory
Records
X
PremierOne does not have this
functionality. Motorola has
included a Pawn inbound interface
with the solution.
MCSO team agrees with
explanation in column N.
1277
Cannot Meet
Motorola
RPS007-13
PAWN SUB-
SYSTEM
General
Provide the ability to Add, Manage, Track and
Report Property related to Pawn (Second Hand
Store) transaction activities
Mandatory
Records
X
PremierOne does not have this
functionality. Motorola has
included a Pawn inbound interface
with the solution.
MCSO team agrees with
explanation in column N.
1278
Cannot Meet
Motorola
RPS007-14
PAWN SUB-
SYSTEM
General
Provide the ability to Add, Manage, Track and
Report FileStops for both Customers and Property.
Mandatory
Records
X
PremierOne does not have this
functionality. Motorola has
included a Pawn inbound interface
with the solution.
MCSO team agrees with
explanation in column N.
1279
Cannot Meet
Page 77 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RPS007-15
PAWN SUB-
SYSTEM
General
FileStops provide the ability to search of persons
or items "of interest" within the MCSO (only) Pawn
System database. It's similar to doing a
Wants/Warrants check or Stolen Items check at
the State level - but only locally.
Mandatory
Records
X
PremierOne does not have this
functionality. Motorola has
included a Pawn inbound interface
with the solution.
MCSO team agrees with
explanation in column N.
1280
Cannot Meet
Motorola
RPS007-16
PAWN SUB-
SYSTEM
General
Customer FileStops provide the ability to register
persons of interest to be checked by all
subsequent Pawn Ticket entry transactions.
Mandatory
Records
X
PremierOne does not have this
functionality. Motorola has
included a Pawn inbound interface
with the solution.
MCSO team agrees with
explanation in column N.
1281
Cannot Meet
Motorola
RPS007-17
PAWN SUB-
SYSTEM
General
Property FileStops provide the ability to register
items of interest (by serial number, OAN, etc.) to
be checked by all Pawn Ticket and Property entry
transactions.
Mandatory
Records
X
PremierOne does not have this
functionality. Motorola has
included a Pawn inbound interface
with the solution.
MCSO team agrees with
explanation in column N.
1282
Cannot Meet
Motorola
RPS007-18
PAWN SUB-
SYSTEM
General
The system should include the ability to prepare
and maintain agency-definable Pawned Property
Reports including but not limited to:
Mandatory
Records
X
PremierOne does not have this
functionality. Motorola has
included a Pawn inbound interface
with the solution.
MCSO team agrees with
explanation in column N.
1283
Cannot Meet
Motorola
RPS007-19
PAWN SUB-
SYSTEM
General
A list of pawned property for a given date range
sorted by category, then by brand name, with the
serial number and description for each piece
listed.
Mandatory
Records
X
PremierOne does not have this
functionality. Motorola has
included a Pawn inbound interface
with the solution.
MCSO team agrees with
explanation in column N.
1284
Cannot Meet
Motorola
RPS007-20
PAWN SUB-
SYSTEM
General
A list of frequent pawners, sorted in descending
order by the number of items pawned.
Mandatory
Records
X
PremierOne does not have this
functionality. Motorola has
included a Pawn inbound interface
with the solution.
MCSO team agrees with
explanation in column N.
1285
Cannot Meet
Motorola
RPS007-21
PAWN SUB-
SYSTEM
General
A list of addresses from which a user definable
number of pawn activities have originated within a
user definable time period.
Mandatory
Records
X
PremierOne does not have this
functionality. Motorola has
included a Pawn inbound interface
with the solution.
MCSO team agrees with
explanation in column N.
1286
Cannot Meet
Motorola
RPS007-22
PAWN SUB-
SYSTEM
General
The subsystem should have the ability to display
both exact and similar items. For example, if the
item pawned is the same brand, make and model
but a different color or serial number it should
return a notification to the designated user.
Mandatory
Records
X
PremierOne does not have this
functionality. Motorola has
included a Pawn inbound interface
with the solution.
MCSO team agrees with
explanation in column N.
1287
Cannot Meet
Motorola
RPS007-23
PAWN SUB-
SYSTEM
General
Provide reports and ad-hoc query ability to
search/filter (Name, Item, Date, Location, ID, etc.)
and report on all aspects of the Pawn Shop
system:
Mandatory
Records
X
PremierOne does not have this
functionality. Motorola has
included a Pawn inbound interface
with the solution.
MCSO team agrees with
explanation in column N.
1288
Cannot Meet
Motorola
RPS007-24
PAWN SUB-
SYSTEM
General
Pawn Shop and Second Hand Store registration /
status
Mandatory
Records
X
PremierOne does not have this
functionality. Motorola has
included a Pawn inbound interface
with the solution.
MCSO team agrees with
explanation in column N.
1289
Cannot Meet
Motorola
RPS007-25
PAWN SUB-
SYSTEM
General
Pawn Ticket entries
Mandatory
Records
X
PremierOne does not have this
functionality. Motorola has
included a Pawn inbound interface
with the solution.
MCSO team agrees with
explanation in column N.
1290
Cannot Meet
Motorola
RPS007-26
PAWN SUB-
SYSTEM
General
Customers with Wants/Warrants (ACIC/NCIC
check)
Mandatory
Records
X
PremierOne does not have this
functionality. Motorola has
included a Pawn inbound interface
with the solution.
MCSO team agrees with
explanation in column N.
1291
Cannot Meet
Motorola
RPS007-27
PAWN SUB-
SYSTEM
General
Customers by Name or ID
Mandatory
Records
X
PremierOne does not have this
functionality. Motorola has
included a Pawn inbound interface
with the solution.
MCSO team agrees with
explanation in column N.
1292
Cannot Meet
Motorola
RPS007-28
PAWN SUB-
SYSTEM
General
Property entries
Mandatory
Records
X
PremierOne does not have this
functionality. Motorola has
included a Pawn inbound interface
with the solution.
MCSO team agrees with
explanation in column N.
1293
Cannot Meet
Motorola
RPS007-29
PAWN SUB-
SYSTEM
General
Property found on ACIC/NCIC stolen items
database
Mandatory
Records
X
PremierOne does not have this
functionality. Motorola has
included a Pawn inbound interface
with the solution.
MCSO team agrees with
explanation in column N.
1294
Cannot Meet
Motorola
RPS007-30
PAWN SUB-
SYSTEM
General
Customer and Property FileStops
Mandatory
Records
X
PremierOne does not have this
functionality. Motorola has
included a Pawn inbound interface
with the solution.
MCSO team agrees with
explanation in column N.
1295
Cannot Meet
Motorola
RPS007-31
PAWN SUB-
SYSTEM
General
Property (of interest) entries that match FileStops
Mandatory
Records
X
PremierOne does not have this
functionality. Motorola has
included a Pawn inbound interface
with the solution.
MCSO team agrees with
explanation in column N.
1296
Cannot Meet
Motorola
RPS007-32
PAWN SUB-
SYSTEM
General
Customers (of interest) that match Customer
FileStops
Mandatory
Records
X
PremierOne does not have this
functionality. Motorola has
included a Pawn inbound interface
with the solution.
MCSO team agrees with
explanation in column N.
1297
Cannot Meet
Motorola
RPS007-33
PAWN SUB-
SYSTEM
General
As with other RMS system activities, provide full
user and transactional auditing for all activities
within the Pawn Shop application.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1298
Out of the Box
Page 78 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RPS007-34
PAWN SUB-
SYSTEM
General
Comment on their willingness to assist a third
party (i.e. Leads Online, Business Watch
International, USA Software INC) with
implementing software to extract and upload
stolen property data from their RMS, and would
the County be charged for this assistance. If
charges would be involved, please include them in
your proposal.
Mandatory
Records
X
Motorola has included a Data View
with our solution. The third party
can query against the PremierOne
database utilizing this Data View.
1299
Out of the Box
Motorola
RPS007-35
PAWN SUB-
SYSTEM
General
Please describe any additional Pawn Shop
functionality that your system provides.
Mandatory
Records
X
PremierOne does not have this
functionality. Motorola has
included a Pawn inbound interface
with the solution.
MCSO team agrees with
explanation in column N.
1300
Cannot Meet
Motorola
RPS008
PAWN SUB-
SYSTEM
General
The system must be able to track pawn shops and
other second hand dealers.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1301
Out of the Box
Motorola
RPS009
PAWN SUB-
SYSTEM
General
The system must associate the pawn shop with
the master entity index.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1302
Out of the Box
Motorola
RPS010
PAWN SUB-
SYSTEM
General
The system must associate the pawn shop location
with the master location index.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1303
Out of the Box
Motorola
RPS011
PAWN SUB-
SYSTEM
General
The system must associate the pawn shop owner
or key employee with the master person Index.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1304
Out of the Box
Motorola
RPS012
PAWN SUB-
SYSTEM
General
Pawns
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1305
Out of the Box
Motorola
RPS013
PAWN SUB-
SYSTEM
General
The system must be able to cross reference
pawned item records to name and property
functions.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1306
Out of the Box
Motorola
RPS014
PAWN SUB-
SYSTEM
General
The system must be able to identify an individual’s
pawn activity (history).
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1307
Out of the Box
Motorola
RPS015
PAWN SUB-
SYSTEM
General
The system must record the following information
and provide the ability to display and report
information accordingly; name of person, DOB,
sex, pawned item date, telephone number
(business and home), property description, serial
number(s), ID number(s).
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1308
Out of the Box
Motorola
RTR001
TRAINING
RECORDS
General
MCSO is interested in reviewing the capabilities of
an RMS module which provides for automated
maintenance and reporting of training related files
and materials as part of a comprehensive
Personnel, Training, and Recruiting Administration
sub-system.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. PremierOne Records
can interface with third-party
personnel/workforce management
software. An interface has not been
included with our solution.
1309
With Third Party Vendor
Motorola
RTR002
TRAINING
RECORDS
General
The County is interested in a system which
possesses capabilities such as:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1310
Out of the Box
Motorola
RTR002-1
TRAINING
RECORDS
General
The capability to be flexible and adapt to the
County's needs, including one-time training,
special training, recurring training, firearms
proficiency, etc.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Attended trainings
can be recorded in PremierOne.
1311
Out of the Box
Motorola
RTR002-2
TRAINING
RECORDS
General
An automated weekly, monthly and annual
training calendar to prepare the training staff and
participants for upcoming training events.
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team agrees with
explanation in column N.
1312
Cannot Meet
Motorola
RTR002-3
TRAINING
RECORDS
General
The ability to provide prompts when a scheduled
training dates are nearing, missed, or are
rescheduled (utilizing a notification in the RMS and
or the County's e-mail system) that is agency
configurable
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met. Functionality
will be replaced with PowerApp
1313
Cannot Meet
Motorola
RTR003
TRAINING
RECORDS
General
The ability to maintain agency-definable training
data including but not limited to:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1314
Out of the Box
Motorola
RTR003-1
TRAINING
RECORDS
General
Schools Attended
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1315
Out of the Box
Motorola
RTR003-2
TRAINING
RECORDS
General
Certificates of Training
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1316
Out of the Box
Motorola
RTR003-3
TRAINING
RECORDS
General
Courses and Seminars Attended (internal and
external)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1317
Out of the Box
Page 79 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RTR003-4
TRAINING
RECORDS
General
Dates
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1318
Out of the Box
Motorola
RTR003-5
TRAINING
RECORDS
General
Course Name/Title
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1319
Out of the Box
Motorola
RTR003-6
TRAINING
RECORDS
General
Course Number
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1320
Out of the Box
Motorola
RTR003-7
TRAINING
RECORDS
General
Hours Completed
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1321
Out of the Box
Motorola
RTR003-8
TRAINING
RECORDS
General
Instructor/School
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1322
Out of the Box
Motorola
RTR003-9
TRAINING
RECORDS
General
Special Skills
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1323
Out of the Box
Motorola
RTR003-10
TRAINING
RECORDS
General
Firearms Qualification History
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1324
Out of the Box
Motorola
RTR003-11
TRAINING
RECORDS
General
Issued Weapon Type
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1325
Out of the Box
Motorola
RTR003-12
TRAINING
RECORDS
General
Off-Duty Weapon Type
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1326
Out of the Box
Motorola
RTR003-13
TRAINING
RECORDS
General
Scores
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1327
Out of the Box
Motorola
RTR003-14
TRAINING
RECORDS
General
Dates
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1328
Out of the Box
Motorola
RTR003-15
TRAINING
RECORDS
General
Serial Number of Agency Issued Weapon
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1329
Out of the Box
Motorola
RTR003-16
TRAINING
RECORDS
General
Serial Number of Personally Owned Weapon
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1330
Out of the Box
Motorola
RTR003-17
TRAINING
RECORDS
General
State Mandated Training Completion and Dates
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1331
Out of the Box
Motorola
RTR003-18
TRAINING
RECORDS
General
Ability to Track Course Information by All Fields
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1332
Out of the Box
Motorola
RTR003-19
TRAINING
RECORDS
General
Ability to Set Up and Maintain a Schedule for
Different Types of Training
Mandatory
Records
X
PremierOne does not have this
functionality.
Motorola explained out of the box training module is
generic and basic. Can use configuration form builder tool.
Out of the box system is configured to complete a person,
a course and when that course was completed and
expiration. Some agencies have changed to one record per
employee with a grid of courses completed. Some capture
training course and a grid of all employees assigned to one
course. System is flexible to capture data per MCSO needs
and use dashboards, SSRS reports to be alerted on
entered training data.
MCSO & Motorola teams agree
requirement is met out of the box
per notes in Column O.
1333
Cannot Meet
Motorola
RTR003-20
TRAINING
RECORDS
General
Ability to Obtain Information on Personnel in Need
of Training by:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1334
With Configuration
Page 80 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RTR003-21
TRAINING
RECORDS
General
Person
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1335
With Configuration
Motorola
RTR003-22
TRAINING
RECORDS
General
Training Type
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1336
With Configuration
Motorola
RTR003-23
TRAINING
RECORDS
General
Date
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1337
With Configuration
Motorola
RTR003-24
TRAINING
RECORDS
General
Special Skills (CDU, Rifle, CDL, etc.)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1338
With Configuration
Page 81 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RFT001
FIELD TRAINING
General
The system should include integrated Field
Training functionality which possess automated
tools designed to enhance the employee training
and evaluation process by providing the ability to
document training throughout a shift and save the
information electronically in a standardized
evaluation format. The intent is to improve
efficiency, as the evaluation is written during the
shift while the training is taking place, rather than
at the end of the shift.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1339
Out of the Box
Motorola
RFT002
FIELD TRAINING
General
The system should be able to produce a
consolidated virtual Field Training "folder" that
contains agency-definable employee information
such as:
Mandatory
Records
X
PremierOne does not comply with
this requirement. Users do not have
the capability to create custom
folder structures within
PremierOne.
MCSO team stated this is not
required to be met. Functionality
will be replaced with PowerApp
1340
Cannot Meet
Motorola
RFT002-1
FIELD TRAINING
General
summary and detailed information concerning all
hours worked (imported from CAD)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1341
With Configuration
Motorola
RFT002-2
FIELD TRAINING
General
summary and detailed information concerning all
employee activities (calls for service, field
interviews, officer initiated activities, court
appearances, etc. imported from the CAD)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1342
With Configuration
Motorola
RFT002-3
FIELD TRAINING
General
copies of all case and other reports prepared, and
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1343
With Configuration
Page 82 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RFT002-4
FIELD TRAINING
General
can be produced for any employee by date range.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1344
With Configuration
Motorola
RFT003
FIELD TRAINING
General
The folder should provide the ability to view a
summary page of employee field training
information that allows users to drill down (via
hyperlinks) to specific activity details and view
such underlying information as case reports, unit
histories, and call for service details.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1345
With Configuration
Motorola
RFT004
FIELD TRAINING
General
The system should have the ability to consolidate
and import all information contained in the folder
to a removable media format (such as a CD) for
easy viewing of all information from the summary
page.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1346
With Configuration
Motorola
RFT005
FIELD TRAINING
General
The system should provide automated daily and
weekly observation, comparison and other agency-
definable reports to assist in evaluating
recruitment, hiring, and training practices.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1347
With Configuration
Page 83 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RFT006
FIELD TRAINING
General
The system should provide tools that allow the
County to create, utilize, and manage electronic
"Observation" reports within the RMS that can be
utilized by authorized end-users in the desktop
and mobile environment.
Mandatory
Records
X
PremierOne Records can be
customized to meet specific agency
needs through the use of the
PremierOne Records Advanced
Configuration Tool (ACT).
Advanced Configuration allows the
agency to make PremierOne
Records their own. The ACT allows
an agency to have custom forms in
existing PremierOne records
modules or new agency-specific
modules with agency-specific entry
forms and reports.
1348
With Configuration
Motorola
RFT007
FIELD TRAINING
General
The reports should include radio buttons, drop-
down menus, narrative fields, and data fields for
entering numerical values.
Mandatory
Records
X
PremierOne Records can be
customized to meet specific agency
needs through the use of the
PremierOne Records Advanced
Configuration Tool (ACT).
Advanced Configuration allows the
agency to make PremierOne
Records their own. The ACT allows
an agency to have custom forms in
existing PremierOne records
modules or new agency-specific
modules with agency-specific entry
forms and reports. Radio buttons
cannot be created through ACT.
1349
With Configuration
Motorola
RFT008
FIELD TRAINING
General
When the report is completed and saved, data
fields containing numerical values should
automatically calculate any necessary sums and
averages.
Mandatory
Records
X
The PremierOne Records Advanced
Configuration Tool (ACT) and
Microsoft SQL Server Reporting
Services (SSRS) are included in this
solution and can be used to meet
this requirement. ACT provides
agencies with the ability to create
their own fully functional modules,
as well as modify existing
PremierOne modules without
source code changes, reducing your
total cost of ownership.
1350
With Configuration
Motorola
RFT009
FIELD TRAINING
General
All "Observation" report data should be available
for user-definable searching and summary report
preparation. It should be possible, for example, to
prepare a summary report illustrating the number
of officers, by Field Training Officer, who have
achieved a user-definable average score range in a
specific user-defined competence area.
Mandatory
Records
X
PremierOne Records can be
customized to meet specific agency
needs through the use of the
PremierOne Records Advanced
Configuration Tool (ACT).
Advanced Configuration allows the
agency to make PremierOne
Records their own. The ACT allows
an agency to have custom forms in
existing PremierOne records
modules or new agency-specific
modules with agency-specific entry
forms and reports. Radio buttons
cannot be created through ACT.
1351
With Configuration
Motorola
RFT010
FIELD TRAINING
General
The system will be fully accessible to workstation
and MDC users.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1352
Out of the Box
Page 84 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
ROA001
OFFICER ACTIVITY
TRACKING
General
Officer Activity Reports capture summary
information that is typically created as a result of
routine activity by Officers and other County
personnel. Statistics from calls for service, event
responses, reports, field interviews, and officer
initiated activities imported from the CAD will
provide summary information for management to
review and analyze.
Mandatory
Records
X
PremierOne will meet the County's
requirement for robust data
analysis, reporting, and dashboard
capabilities. In addition,
PremierOne is deployed with a
Reporting Data Warehouse (RDW)
which is a near real time copy
(mirror) of the production
database.
PremierOne CAD utilizes Microsoft
SQL Server Reporting Services
(SSRS) for its standard reports. SSRS
is a server-based reporting platform
that is used to create and manage
tabular, matrix, graphical,
dashboards, and free form reports
that contain data from relational
and multidimensional data sources.
A sample of the standard reports
include Average Response Times by
Incident Type, BOLO Messages,
Various Calls For Service reports,
various Incident reports (grouped
by type, by area, etc), Login and
Logoff, various Provisioning reports,
Purge schedule, various Query
d Offi
A i i
A
1353
With Configuration
Motorola
ROA002
OFFICER ACTIVITY
TRACKING
General
The County is interested in evaluated a sub-system
which can provide the ability to capture, maintain,
and report on officer activity, including but not
limited to:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1354
Out of the Box
Motorola
ROA002-1
OFFICER ACTIVITY
TRACKING
General
Reports filed and type
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1355
Out of the Box
Motorola
ROA002-2
OFFICER ACTIVITY
TRACKING
General
Arrest types:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1356
Out of the Box
Motorola
ROA002-3
OFFICER ACTIVITY
TRACKING
General
Felony
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1357
Out of the Box
Motorola
ROA002-4
OFFICER ACTIVITY
TRACKING
General
Misdemeanor
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1358
Out of the Box
Motorola
ROA002-5
OFFICER ACTIVITY
TRACKING
General
Citation
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1359
Out of the Box
Motorola
ROA002-6
OFFICER ACTIVITY
TRACKING
General
Traffic tickets written
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1360
Out of the Box
Motorola
ROA002-7
OFFICER ACTIVITY
TRACKING
General
Warning tickets written
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1361
Out of the Box
Motorola
ROA002-8
OFFICER ACTIVITY
TRACKING
General
Parking tickets written
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1362
Out of the Box
Motorola
ROA002-9
OFFICER ACTIVITY
TRACKING
General
Field interviews conducted
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1363
Out of the Box
Motorola
ROA002-10
OFFICER ACTIVITY
TRACKING
General
CAD Calls For Service, assigned
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1364
Out of the Box
Motorola
ROA002-11
OFFICER ACTIVITY
TRACKING
General
CAD Calls For Service, assisted
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1365
Out of the Box
Motorola
ROA002-12
OFFICER ACTIVITY
TRACKING
General
CAD Calls For Service, self initiated
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1366
Out of the Box
Motorola
ROA002-13
OFFICER ACTIVITY
TRACKING
General
False Alarms
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1367
Out of the Box
Motorola
ROA002-14
OFFICER ACTIVITY
TRACKING
General
Court time
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1368
Out of the Box
Motorola
ROA002-15
OFFICER ACTIVITY
TRACKING
General
Training time
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1369
Out of the Box
Motorola
ROA002-16
OFFICER ACTIVITY
TRACKING
General
Track actual participation time (by person)
including but not limited to such activities as:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1370
Out of the Box
Page 85 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
ROA002-17
OFFICER ACTIVITY
TRACKING
General
Foot Patrol
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1371
Out of the Box
Motorola
ROA002-18
OFFICER ACTIVITY
TRACKING
General
Special event time
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1372
Out of the Box
Motorola
ROA002-19
OFFICER ACTIVITY
TRACKING
General
Community meeting
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1373
Out of the Box
Motorola
ROA002-20
OFFICER ACTIVITY
TRACKING
General
Other down time
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1374
Out of the Box
Motorola
ROA003
OFFICER ACTIVITY
TRACKING
General
The system should provide the ability to
summarize officer activity by, but not limited to,
the following criteria:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1375
Out of the Box
Motorola
ROA003-1
OFFICER ACTIVITY
TRACKING
General
Individual
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1376
Out of the Box
Motorola
ROA003-2
OFFICER ACTIVITY
TRACKING
General
Squad
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1377
Out of the Box
Motorola
ROA003-3
OFFICER ACTIVITY
TRACKING
General
Division
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1378
Out of the Box
Motorola
ROA003-4
OFFICER ACTIVITY
TRACKING
General
Bureau
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1379
Out of the Box
Motorola
ROA003-5
OFFICER ACTIVITY
TRACKING
General
Date and Time range
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1380
Out of the Box
Motorola
ROA003-6
OFFICER ACTIVITY
TRACKING
General
Shift
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1381
Out of the Box
Motorola
ROA003-7
OFFICER ACTIVITY
TRACKING
General
By Officer activity and date range
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1382
Out of the Box
Motorola
ROA004
OFFICER ACTIVITY
TRACKING
General
The system should be able to generate statistical
and graphical reports on any captured data and,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1383
Out of the Box
Motorola
ROA005
OFFICER ACTIVITY
TRACKING
General
Prepare agency and user-definable activity and
management reports.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1384
Out of the Box
Motorola
ROA006
OFFICER ACTIVITY
TRACKING
General
The system should provide the ability to view a
summary page of user-definable employee/squad
statistics from which users can drill down (via
hyperlinks or other suitable method) to specific
statistic details and view underlying information
regarding the statistics concerning number and
types of arrests and citations, etc. by user-
definable time and date ranges.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1385
Out of the Box
Motorola
RPE001
PERFORMANCE
EVALUATION
General
The County is interested in reviewing the
capabilities of an RMS module which can maintain,
track, and report employee Performance
Evaluation information via an integrated
Performance Evaluation Sub-System/Module.
Mandatory
Records
X
PremierOne Records can interface
with third-party
personnel/workforce management
software. An interface has not been
included with our solution.
MCSO team stated this is not
required to be met. Functionality
will be replaced with PowerApp
1386
Cannot Meet
Motorola
RPE002
PERFORMANCE
EVALUATION
General
The system should track when performance
evaluations are due, at each user-definable level of
the organization, and be capable of providing an e-
mail notification to agency definable employees
when evaluations are due.
Mandatory
Records
X
PremierOne Records can interface
with third-party
personnel/workforce management
software. An interface has not been
included with our solution.
MCSO team stated this is not
required to be met. Functionality
will be replaced with PowerApp
1387
Cannot Meet
Motorola
ROD001
OFF-DUTY
EMPLOYMENT
General
The system should use basic personnel
information and supplement it with agency-
definable information in order to track the off-
duty employment of uniform and plain clothes
officers including but not limited to:
Mandatory
Records
X
PremierOne Records can be
customized to meet specific agency
needs through the use of the
PremierOne Records Advanced
Configuration Tool (ACT).
Advanced Configuration allows the
agency to make PremierOne
Records their own. The ACT allows
an agency to have custom forms in
existing PremierOne records
modules or new agency-specific
modules with agency-specific entry
forms and reports.
1388
With Configuration
Motorola
ROD001-1
OFF-DUTY
EMPLOYMENT
General
An automatically generated permit number
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1389
Cannot Meet
Page 86 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
ROD001-2
OFF-DUTY
EMPLOYMENT
General
Approval Date
Mandatory
Records
X
PremierOne Records can be
customized to meet specific agency
needs through the use of the
PremierOne Records Advanced
Configuration Tool (ACT).
Advanced Configuration allows the
agency to make PremierOne
Records their own. The ACT allows
an agency to have custom forms in
existing PremierOne records
modules or new agency-specific
modules with agency-specific entry
forms and reports.
1390
With Configuration
Motorola
ROD001-3
OFF-DUTY
EMPLOYMENT
General
Name of the Approving Commander or supervisor. Mandatory
Records
X
PremierOne Records can be
customized to meet specific agency
needs through the use of the
PremierOne Records Advanced
Configuration Tool (ACT).
Advanced Configuration allows the
agency to make PremierOne
Records their own. The ACT allows
an agency to have custom forms in
existing PremierOne records
modules or new agency-specific
modules with agency-specific entry
forms and reports.
1391
With Configuration
Motorola
ROD001-4
OFF-DUTY
EMPLOYMENT
General
The system will also be capable of maintaining
employer information such as:
Mandatory
Records
X
PremierOne Records can be
customized to meet specific agency
needs through the use of the
PremierOne Records Advanced
Configuration Tool (ACT).
Advanced Configuration allows the
agency to make PremierOne
Records their own. The ACT allows
an agency to have custom forms in
existing PremierOne records
modules or new agency-specific
modules with agency-specific entry
forms and reports.
1392
With Configuration
Motorola
ROD001-5
OFF-DUTY
EMPLOYMENT
General
Approved Employer Name
Mandatory
Records
X
PremierOne Records can be
customized to meet specific agency
needs through the use of the
PremierOne Records Advanced
Configuration Tool (ACT).
Advanced Configuration allows the
agency to make PremierOne
Records their own. The ACT allows
an agency to have custom forms in
existing PremierOne records
modules or new agency-specific
modules with agency-specific entry
forms and reports.
1393
With Configuration
Motorola
ROD001-6
OFF-DUTY
EMPLOYMENT
General
Approved Employer Location
Mandatory
Records
X
PremierOne Records can be
customized to meet specific agency
needs through the use of the
PremierOne Records Advanced
Configuration Tool (ACT).
Advanced Configuration allows the
agency to make PremierOne
Records their own. The ACT allows
an agency to have custom forms in
existing PremierOne records
modules or new agency-specific
modules with agency-specific entry
forms and reports.
1394
With Configuration
Page 87 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
ROD001-7
OFF-DUTY
EMPLOYMENT
General
Contact Person's Name
Mandatory
Records
X
PremierOne Records can be
customized to meet specific agency
needs through the use of the
PremierOne Records Advanced
Configuration Tool (ACT).
Advanced Configuration allows the
agency to make PremierOne
Records their own. The ACT allows
an agency to have custom forms in
existing PremierOne records
modules or new agency-specific
modules with agency-specific entry
forms and reports.
1395
With Configuration
Motorola
ROD001-8
OFF-DUTY
EMPLOYMENT
General
Contact Person's Phone Number
Mandatory
Records
X
PremierOne Records can be
customized to meet specific agency
needs through the use of the
PremierOne Records Advanced
Configuration Tool (ACT).
Advanced Configuration allows the
agency to make PremierOne
Records their own. The ACT allows
an agency to have custom forms in
existing PremierOne records
modules or new agency-specific
modules with agency-specific entry
forms and reports.
1396
With Configuration
Motorola
ROD001-9
OFF-DUTY
EMPLOYMENT
General
Approval Date
Mandatory
Records
X
PremierOne Records can be
customized to meet specific agency
needs through the use of the
PremierOne Records Advanced
Configuration Tool (ACT).
Advanced Configuration allows the
agency to make PremierOne
Records their own. The ACT allows
an agency to have custom forms in
existing PremierOne records
modules or new agency-specific
modules with agency-specific entry
forms and reports.
1397
With Configuration
Motorola
ROD001-10
OFF-DUTY
EMPLOYMENT
General
Is the officer working uniform or plain clothes
Mandatory
Records
X
PremierOne Records can be
customized to meet specific agency
needs through the use of the
PremierOne Records Advanced
Configuration Tool (ACT).
Advanced Configuration allows the
agency to make PremierOne
Records their own. The ACT allows
an agency to have custom forms in
existing PremierOne records
modules or new agency-specific
modules with agency-specific entry
forms and reports.
1398
With Configuration
Motorola
ROD002
OFF-DUTY
EMPLOYMENT
General
Work address and work schedule. The County
would like to make this information available
when a call comes in at or near a location where
an officer may be working. Vendor to detail how
this will be met.
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1399
Cannot Meet
Motorola
RIE001
INVENTORY AND
EQUIPMENT
MANAGEMENT
General
The system should provide for the administration
and maintenance of property issued to employees.
Issued equipment includes protective clothing,
weapons, tools, keys, etc. Where appropriate,
reports of loss or damage to issued equipment
should be linked to any associated case report.
Mandatory
Records
X
The Equipment Management
module manages all departmental
equipment. It allows an agency to
track its entire equipment
inventory and equipment
assignments. Details are
maintained for each inventory item
and equipment issue history is
available for each personnel
member. Equipment management
allows a department to easily keep
track of the current location and
condition of all departmental
equipment.
1400
Out of the Box
Page 88 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RIE002
INVENTORY AND
EQUIPMENT
MANAGEMENT
General
The system should provide the ability to capture
and maintain all County issued equipment data
including, but not limited to:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1401
Out of the Box
Motorola
RIE002-1
INVENTORY AND
EQUIPMENT
MANAGEMENT
General
Item number
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1402
Out of the Box
Motorola
RIE002-2
INVENTORY AND
EQUIPMENT
MANAGEMENT
General
Description
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1403
Out of the Box
Motorola
RIE002-3
INVENTORY AND
EQUIPMENT
MANAGEMENT
General
Make
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1404
Out of the Box
Motorola
RIE002-4
INVENTORY AND
EQUIPMENT
MANAGEMENT
General
Model
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1405
Out of the Box
Motorola
RIE002-5
INVENTORY AND
EQUIPMENT
MANAGEMENT
General
Type
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1406
Out of the Box
Motorola
RIE002-6
INVENTORY AND
EQUIPMENT
MANAGEMENT
General
Cost
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1407
Out of the Box
Motorola
RIE002-7
INVENTORY AND
EQUIPMENT
MANAGEMENT
General
Manufacturer
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1408
Out of the Box
Motorola
RIE002-8
INVENTORY AND
EQUIPMENT
MANAGEMENT
General
Manufacture Date
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1409
Out of the Box
Motorola
RIE002-9
INVENTORY AND
EQUIPMENT
MANAGEMENT
General
Warranty period
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1410
Out of the Box
Motorola
RIE002-10
INVENTORY AND
EQUIPMENT
MANAGEMENT
General
Warranty start/end dates
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1411
Out of the Box
Motorola
RIE002-11
INVENTORY AND
EQUIPMENT
MANAGEMENT
General
Size/caliber of weapon issued
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1412
Out of the Box
Motorola
RIE002-12
INVENTORY AND
EQUIPMENT
MANAGEMENT
General
Serial number
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1413
Out of the Box
Motorola
RIE002-13
INVENTORY AND
EQUIPMENT
MANAGEMENT
General
Accessories (case, charger, battery charger, car
charger, photo scale, grease pencil etc.)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1414
Out of the Box
Motorola
RIE002-14
INVENTORY AND
EQUIPMENT
MANAGEMENT
General
Specialty Issue (CNT, SWAT, Mobile Field Force,
Honor Guard etc.)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1415
Out of the Box
Motorola
RIE002-15
INVENTORY AND
EQUIPMENT
MANAGEMENT
General
Asset/property tag number
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1416
Out of the Box
Motorola
RIE002-16
INVENTORY AND
EQUIPMENT
MANAGEMENT
General
Radio ID number
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1417
Out of the Box
Motorola
RIE002-17
INVENTORY AND
EQUIPMENT
MANAGEMENT
General
Date purchased
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1418
Out of the Box
Motorola
RIE002-18
INVENTORY AND
EQUIPMENT
MANAGEMENT
General
Date issued
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1419
Out of the Box
Page 89 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RIE002-19
INVENTORY AND
EQUIPMENT
MANAGEMENT
General
Condition issued
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1420
Out of the Box
Motorola
RIE002-20
INVENTORY AND
EQUIPMENT
MANAGEMENT
General
Issued by
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1421
Out of the Box
Motorola
RIE002-21
INVENTORY AND
EQUIPMENT
MANAGEMENT
General
Date returned
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1422
Out of the Box
Motorola
RIE002-22
INVENTORY AND
EQUIPMENT
MANAGEMENT
General
Condition returned
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1423
Out of the Box
Motorola
RIE002-23
INVENTORY AND
EQUIPMENT
MANAGEMENT
General
Received by
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1424
Out of the Box
Motorola
RIE002-24
INVENTORY AND
EQUIPMENT
MANAGEMENT
General
Maintenance
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1425
Out of the Box
Motorola
RIE002-25
INVENTORY AND
EQUIPMENT
MANAGEMENT
General
Equipment type (weapons, etc.)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1426
Out of the Box
Motorola
RIE002-26
INVENTORY AND
EQUIPMENT
MANAGEMENT
General
Repair dates and comments
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1427
Out of the Box
Motorola
RIE002-27
INVENTORY AND
EQUIPMENT
MANAGEMENT
General
Status code (lost, missing, etc.) include purchased,
awarded, donated to ______, destroyed, auction
p/u date_______, Hold IA, Hold Case #_________
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1428
Out of the Box
Motorola
RIE002-28
INVENTORY AND
EQUIPMENT
MANAGEMENT
General
Status code (lost, missing, etc.)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1429
Out of the Box
Motorola
RIE002-29
INVENTORY AND
EQUIPMENT
MANAGEMENT
General
Replacement dates
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1430
Out of the Box
Motorola
RIE002-30
INVENTORY AND
EQUIPMENT
MANAGEMENT
General
Keys and lockers, locker numbers and
combinations
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1431
Out of the Box
Motorola
RIE002-31
INVENTORY AND
EQUIPMENT
MANAGEMENT
General
Other
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1432
Out of the Box
Motorola
RIE003
INVENTORY AND
EQUIPMENT
MANAGEMENT
General
The system should provide the ability to:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1433
Out of the Box
Motorola
RIE003-1
INVENTORY AND
EQUIPMENT
MANAGEMENT
General
Display and print summary of equipment by
Officer in a checklist form with blocks to check off
equipment as turned in (resignation/retirement
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1434
Out of the Box
Motorola
RIE003-2
INVENTORY AND
EQUIPMENT
MANAGEMENT
General
List all equipment due for inspection and/or
maintenance for any given time period by
individual, unit or district
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1435
Out of the Box
Motorola
RIE003-3
INVENTORY AND
EQUIPMENT
MANAGEMENT
General
Print equipment issued and in-stock inventory
listings
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1436
Out of the Box
Motorola
RIE004
INVENTORY AND
EQUIPMENT
MANAGEMENT
General
List equipment scheduled for inspection by:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1437
Out of the Box
Motorola
RIE004-1
INVENTORY AND
EQUIPMENT
MANAGEMENT
General
Type of equipment
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1438
Out of the Box
Page 90 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RIE004-2
INVENTORY AND
EQUIPMENT
MANAGEMENT
General
District (North or South)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1439
Out of the Box
Motorola
RIE004-3
INVENTORY AND
EQUIPMENT
MANAGEMENT
General
Employee
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1440
Out of the Box
Motorola
RIE004-4
INVENTORY AND
EQUIPMENT
MANAGEMENT
General
Date range
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1441
Out of the Box
Motorola
RIE005
INVENTORY AND
EQUIPMENT
MANAGEMENT
General
The system should provide users the ability to
search for and print equipment lists by all available
data fields such as item number, serial number,
location, equipment type, employee, district, etc.
w/multiple variables (date issued and equipment
type; make and model etc.)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1442
Out of the Box
Motorola
RIE006
INVENTORY AND
EQUIPMENT
MANAGEMENT
General
The system should have the ability to retrieve and
print equipment records by all available data fields
such as serial number, equipment type, location,
employee assigned to, location, etc.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1443
Out of the Box
Motorola
RIE007
INVENTORY AND
EQUIPMENT
MANAGEMENT
General
The system should have the ability to maintain,
track, calculate and report on replacement
lifecycles for specific issued equipment including
but not limited to such criteria as:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1444
Out of the Box
Motorola
RIE008
INVENTORY AND
EQUIPMENT
MANAGEMENT
General
Date range, individual, District station, etc.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1445
Out of the Box
Motorola
RIE009
INVENTORY AND
EQUIPMENT
MANAGEMENT
General
The system should support barcode entry, tracking
and maintenance of inventoried items.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1446
Out of the Box
Motorola
RIE010
INVENTORY AND
EQUIPMENT
MANAGEMENT
General
Barcode Support should include each item and
each employee by employee number
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1447
Out of the Box
Motorola
RIE011
INVENTORY AND
EQUIPMENT
MANAGEMENT
General
The system should allow users to scan item's
barcode and enter the quantity, after which the
system will assign the item to the employee, who
can then print a receipt. or electronic copy for
electronic signature to email to individual to sign
and return for file copy.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1448
Out of the Box
Motorola
RIE012
INVENTORY AND
EQUIPMENT
MANAGEMENT
General
In the above instance, the system should also
provide the ability to prepare and forward an
electronic receipt via e-mail, for the assigned
employee to electronically acknowledge as a "file
copy".
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1449
Cannot Meet
Motorola
RNW001
NEIGHBORHOOD
WATCH
General
The system should have the ability to maintain a
list of community members involved in
neighborhood watch or other community policing
initiatives. At a minimum this list should include
the following agency-definable data elements:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1450
Out of the Box
Motorola
RNW001-1
NEIGHBORHOOD
WATCH
General
Community group name
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1451
Out of the Box
Motorola
RNW001-2
NEIGHBORHOOD
WATCH
General
Group leader
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1452
Out of the Box
Motorola
RNW001-3
NEIGHBORHOOD
WATCH
General
Street/Area
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1453
Out of the Box
Motorola
RNW001-4
NEIGHBORHOOD
WATCH
General
Contact name
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1454
Out of the Box
Motorola
RNW001-5
NEIGHBORHOOD
WATCH
General
Contact address
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1455
Out of the Box
Motorola
RNW001-6
NEIGHBORHOOD
WATCH
General
Contact home phone number
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1456
Out of the Box
Page 91 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RNW001-7
NEIGHBORHOOD
WATCH
General
Contact Business phone number
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1457
Out of the Box
Motorola
RNW001-8
NEIGHBORHOOD
WATCH
General
Community group members' names
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1458
Out of the Box
Motorola
RNW001-9
NEIGHBORHOOD
WATCH
General
Community group members' phone numbers
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1459
Out of the Box
Motorola
RNW001-10
NEIGHBORHOOD
WATCH
General
Community group members' e-mail addresses
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1460
Out of the Box
Motorola
RNW002
NEIGHBORHOOD
WATCH
General
The system should have the ability to print form
letters and send email mailings to some or all of
the persons listed in a neighborhood watch list or
other community initiative.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1461
Out of the Box
Motorola
RNW003
NEIGHBORHOOD
WATCH
General
The Community Group and Neighborhood Watch
data should be available for analysis by the system
and link to the system's mapping system and
available as a user-definable mapped data layer.
Mandatory
Records
X
PremierOne complies with the
functionality if these layers are
available in the GIS for SSRS.
1462
Out of the Box
Motorola
RPR001
PRINCIPAL
REPORTS
General
GENERAL REQUIREMENTS
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1463
Out of the Box
Motorola
RPR001-1
PRINCIPAL
REPORTS
General
The vendor shall permit the system administrator
and other authorized user(s) to determine the
source (tables, etc.) that form the basis of all
available reports delivered by the vendor.
Mandatory
Records
X
The PremierOne Records Advanced
Configuration Tool (ACT) and
Microsoft SQL Server Reporting
Services (SSRS) are included in this
solution and can be used to meet
this requirement.
ACT provides agencies with the
ability to create their own fully
functional modules, as well as
modify existing PremierOne
modules without source code
changes, reducing your total cost of
ownership.
1464
Out of the Box
Motorola
RPR001-2
PRINCIPAL
REPORTS
General
The system should utilize a built-in report writer
for standard and/or ad-hoc report creation that
can be used by a non-technical professional to
create, use, save, and print searches and reports.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1465
Out of the Box
Motorola
RPR001-3
PRINCIPAL
REPORTS
General
For example, the system should provide the
capability to generate a summary of warning
tickets issued by vehicle state registration.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1466
With Configuration
Motorola
RPR001-4
PRINCIPAL
REPORTS
General
The system data files should be compatible with
3rd party reporting tools such as Crystal Reports.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1467
Out of the Box
Motorola
RPR001-5
PRINCIPAL
REPORTS
General
The offeror should list and describe all reports
offered as part of their system. Please provide
samples.
Mandatory
Records
X
A copy of PremierOne CAD
Standard Reports and PremierOne
Records Standard Reports have
been included in Exhibit 6.
1468
Out of the Box
Motorola
RPR001-6
PRINCIPAL
REPORTS
General
The system should be capable of posting to a web
page, all reports (statistical, graphical, etc.)
including selected MCSO DR reports and the
results of selected RMS queries
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1469
Out of the Box
Motorola
RPR002
PRINCIPAL
REPORTS
General
SYSTEM ADMINISTRATOR REPORTS
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1470
Out of the Box
Page 92 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RPR002-1
PRINCIPAL
REPORTS
General
A logon Report which shows the time and location
of each user logging on or off of the RMS system
for a given date.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1471
With Configuration
Motorola
RPR002-2
PRINCIPAL
REPORTS
General
A workstation Logon Report which shows all users
logging on or off of the system from a given
workstation for a given date.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1472
With Configuration
Motorola
RPR002-3
PRINCIPAL
REPORTS
General
An audit trail of all changes made to an incident
report including the date, time, workstation, and
associated employee.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1473
With Configuration
Motorola
RPR002-4
PRINCIPAL
REPORTS
General
A report which lists all persons who have printed
any or all forms associated with a given case.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1474
With Configuration
Page 93 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RPR002-5
PRINCIPAL
REPORTS
General
A report which shows the system administrator or
authorized user all master index entries added for
a user specified date and time range.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1475
With Configuration
Motorola
RPR003
PRINCIPAL
REPORTS
General
CRIME AND EVENT REPORTS
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1476
Out of the Box
Motorola
RPR003-1
PRINCIPAL
REPORTS
General
A temporally configurable (e.g. 24 hour, 8 hour,
etc.) automated report, which provides a
summary of reported offenses during the previous
calendar day(s) for a user-defined area. This
report will include the:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1477
With Configuration
Motorola
RPR003-1-1
PRINCIPAL
REPORTS
General
Offense classification
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1478
With Configuration
Motorola
RPR003-1-2
PRINCIPAL
REPORTS
General
Date
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1479
With Configuration
Page 94 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RPR003-1-3
PRINCIPAL
REPORTS
General
Time
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1480
With Configuration
Motorola
RPR003-1-4
PRINCIPAL
REPORTS
General
Location of the offense
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1481
With Configuration
Motorola
RPR003-1-5
PRINCIPAL
REPORTS
General
Complainant's Name
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1482
With Configuration
Motorola
RPR003-1-6
PRINCIPAL
REPORTS
General
Reporting Officer
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1483
With Configuration
Page 95 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RPR003-1-7
PRINCIPAL
REPORTS
General
Summary of Offense
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1484
With Configuration
Motorola
RPR003-1-8
PRINCIPAL
REPORTS
General
Suspect Description
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1485
With Configuration
Motorola
RPR003-1-9
PRINCIPAL
REPORTS
General
Vehicle Description
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1486
With Configuration
Motorola
RPR003-1-10
PRINCIPAL
REPORTS
General
Case Status
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1487
With Configuration
Page 96 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RPR003-1-11
PRINCIPAL
REPORTS
General
Name, Age, Race, Sex, Residential Address of
Arrestee (if closed by arrest)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1488
With Configuration
Motorola
RPR003-1-12
PRINCIPAL
REPORTS
General
Quarter Section Map
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1489
With Configuration
Motorola
RPR003-1-13
PRINCIPAL
REPORTS
General
Patrol District, and
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1490
With Configuration
Motorola
RPR003-1-14
PRINCIPAL
REPORTS
General
Patrol Area for each case.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1491
With Configuration
Page 97 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RPR003-2
PRINCIPAL
REPORTS
General
The report should be capable of being prepared by
numerous data elements including but not limited
to:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1492
With Configuration
Motorola
RPR003-2-1
PRINCIPAL
REPORTS
General
Patrol District
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1493
With Configuration
Motorola
RPR003-2-2
PRINCIPAL
REPORTS
General
Patrol Area
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1494
With Configuration
Motorola
RPR003-2-3
PRINCIPAL
REPORTS
General
Any user defined date and time range.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1495
With Configuration
Page 98 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RPR003-3
PRINCIPAL
REPORTS
General
The report should list offenses beginning with the
most serious offense or in any other user-
definable order.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1496
With Configuration
Motorola
RPR003-4
PRINCIPAL
REPORTS
General
Non-criminal incidents will follow offenses.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1497
With Configuration
Motorola
RPR003-5
PRINCIPAL
REPORTS
General
The system should include a report listing offenses
and calls for service by address and/or disposition
by Patrol district and Patrol area.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1498
With Configuration
Motorola
RPR003-6
PRINCIPAL
REPORTS
General
The system should include a Summary of Offenses
Report which provides a summary of each offense
including the date, time, type, location of
occurrence, and status for each offense for a user
defined date and time range.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1499
With Configuration
Motorola
RPR004
PRINCIPAL
REPORTS
General
MANAGEMENT REPORTS
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1500
Out of the Box
Motorola
RPR004-1
PRINCIPAL
REPORTS
General
The County desires the management reporting
capabilities:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1501
Out of the Box
Page 99 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RPR004-2
PRINCIPAL
REPORTS
General
Patrol: Capable of preparing user configurable
Monthly and Annual reports by Patrol District,
Area, and Quarter Section Map on various user-
definable statistics such as arrests, citations, case
reports, crash reports, and miscellaneous
administrative activities.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1502
With Configuration
Motorola
RPR004-3
PRINCIPAL
REPORTS
General
Traffic Summary: Capable of preparing user-
definable Monthly and Annual summary reports of
traffic citations, crash reports, fatalities, etc.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1503
With Configuration
Motorola
RPR004-4
PRINCIPAL
REPORTS
General
Arrests: The system should be capable of
preparing user definable Monthly and Annual
reports of total arrests and by category: felony,
misdemeanor, County Code, etc.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1504
With Configuration
Motorola
RPR004-5
PRINCIPAL
REPORTS
General
Investigations (CIS): Capable of preparing the
following kinds of user-definable reports: Monthly
case status report, offense by UCR code, case
clearance, warrants, arrests, employee, etc.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1505
With Configuration
Page 100 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RPR004-6
PRINCIPAL
REPORTS
General
Juvenile: Capable of preparing user-definable
reports such as monthly cases by classification,
referrals, arrests, domestic violence cases, etc.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1506
With Configuration
Motorola
RPR004-7
PRINCIPAL
REPORTS
General
Vice: Capable of preparing user-definable Monthly
and Annual reports summarizing drug seizures by
type. The system should also track asset
forfeitures by federal and state, search warrants,
etc.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1507
With Configuration
Motorola
RPR004-8
PRINCIPAL
REPORTS
General
Demographic Profiling: Capable of providing user-
definable statistical data on officer-initiated
contacts, etc.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1508
With Configuration
Motorola
RPR004-9
PRINCIPAL
REPORTS
General
CAD Event Reporting: Management reports
concerning agency activities will be required after
the CAD data has been transferred to the RMS.
Therefore, the RMS should be capable of providing
a the full range of management reporting detailed
in CAD Functional Requirements, Query and
Reporting Section.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1509
With Configuration
Page 101 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RPR004-10
PRINCIPAL
REPORTS
General
The system should include agency-definable
statistical reports of complaints (calls for service
that do not result in a case report) and crimes
including but not limited to such criteria as:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1510
With Configuration
Motorola
RPR004-10-1
PRINCIPAL
REPORTS
General
User-defined address
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1511
With Configuration
Motorola
RPR004-10-2
PRINCIPAL
REPORTS
General
District
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1512
With Configuration
Motorola
RPR004-10-3
PRINCIPAL
REPORTS
General
Patrol Area
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1513
With Configuration
Page 102 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RPR004-10-4
PRINCIPAL
REPORTS
General
Any user-defined geographical area,
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1514
With Configuration
Motorola
RPR004-10-5
PRINCIPAL
REPORTS
General
Day of week
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1515
With Configuration
Motorola
RPR004-10-6
PRINCIPAL
REPORTS
General
Time range
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1516
With Configuration
Motorola
RPR004-10-7
PRINCIPAL
REPORTS
General
Date range, or
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1517
With Configuration
Page 103 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RPR004-10-8
PRINCIPAL
REPORTS
General
Any combination of the above.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1518
With Configuration
Motorola
RPR004-11
PRINCIPAL
REPORTS
General
The "complaints" report will require data from the
CAD.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1519
With Configuration
Motorola
RPR004-12
PRINCIPAL
REPORTS
General
The user should be able to define the radius or
proximity inside which all addresses will be
considered a single address when searching for
"hot spots".
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1520
With Configuration
Motorola
RPR004-13
PRINCIPAL
REPORTS
General
Case Management Reporting: The ability to
generate Case Assignment and Monthly Clearance
Reports (offense description, current month, total
cleared, percent cleared) by officer/detective
and/or squad/detective unit.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1521
With Configuration
Page 104 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RPR004-14
PRINCIPAL
REPORTS
General
The Clearance report should be capable of being
prepared by any user-defined period (month or
number of months, year) for any assigned
officer/detective and/or squad/detective unit,
and/or any Patrol District, or Patrol Area
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1522
With Configuration
Motorola
RPR004-15
PRINCIPAL
REPORTS
General
The ability to generate a Case List Summary report
by user-definable criteria including but not limited
to:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1523
With Configuration
Motorola
RPR004-15-1
PRINCIPAL
REPORTS
General
Status
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1524
With Configuration
Motorola
RPR004-15-2
PRINCIPAL
REPORTS
General
Report Date(s)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1525
With Configuration
Page 105 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RPR004-15-3
PRINCIPAL
REPORTS
General
Assigned Officer/Detective
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1526
With Configuration
Motorola
RPR004-15-4
PRINCIPAL
REPORTS
General
Squad/Detective Unit
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1527
With Configuration
Motorola
RPR004-15-5
PRINCIPAL
REPORTS
General
Patrol Division
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1528
With Configuration
Motorola
RPR004-15-6
PRINCIPAL
REPORTS
General
Patrol District
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1529
With Configuration
Page 106 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RPR004-15-7
PRINCIPAL
REPORTS
General
Patrol Area
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. As part of
deployment, Motorola will apply
canned reports to the system and
lead a reporting writing workshop
with County personnel. The
Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County. In additional to the
standard reports contained within
PremierOne, The County can
develop an SSRS report to meet this
requirement.
1530
With Configuration
Motorola
ROR001
OTHER
REQUESTED
FUNCTIONALITY
General
TRESPASS CONTROL
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1531
Out of the Box
Motorola
ROR001-1
OTHER
REQUESTED
FUNCTIONALITY
General
Persons found in violation of ARS 13-1502 are
usually given a warning for a first violation. If the
individual refuses to leave when instructed to do
so, he or she will be arrested. Patrol is requesting
the capability to determine if a violator has
previous violations at or nearby a particular
address/business. Business locations can report
that they have advised a disruptive person or
someone who has committed a crime that they
have trespassed, must leave immediately and
never return. The documented warning allows the
previously warned person to be arrested if they do
return. The Sheriff's Office is asking for a way to
document a trespass situation at a given location
so the information is available if and when there is
a repeat occurrence. The information must be
stored so that it is available by location and/or
subject name. The Sheriff's Office does not want
to create a DR unless an arrest occurs. Vendors
are being asked to explain in detail how they can
provide this functionality.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1532
Out of the Box
Motorola
ROR002
OTHER
REQUESTED
FUNCTIONALITY
General
TRESPASS CONTROL
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1533
Out of the Box
Motorola
ROR002-1
OTHER
REQUESTED
FUNCTIONALITY
General
Gang members and their associates/affiliates now
use monikers, or nicknames, so dependably that
these pseudonyms can provide a reliable source of
investigative information. Gang members and
their affiliates use monikers on the streets as
graffiti; tattoo them on their bodies; and write
them on such personal items as school yearbooks,
clothing and jewelry. Care must be taken not to
label a suspect as being a gang member unless at
least two of the established gang member criteria
are met. Once two of the criteria are met, the
individual is entered into Gang Net. They cannot
be labeled a Gang Member in the RMS simply
because they use or display a gang moniker, or
have an association with those who do. Moniker
use or involvement, and/or the fact that they
satisfy one of the gang member criteria only make
them a person of interest to law enforcement.
The MCSO is requesting the ability to inquire on a
moniker and retrieve all persons having previously
used the moniker, or have any
affiliations/associations to those using the
moniker, or any event in which the moniker was
displayed (i.e. graffiti, tattoos etc.). The offeror is
being asked to propose a method of providing this
requested functionality.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1534
Out of the Box
Page 107 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
ROR002-2
OTHER
REQUESTED
FUNCTIONALITY
General
Citizens can report graffiti by using a County
website, a County Hotline, or by calling
Communications. As a result of a report/complaint
a civilian technician responds and removes or
paints over the graffiti. The technician completes a
"MCSO Graffiti Report" that contains a report
number, date, time, location, moniker, suspect's
name, suspect's DOB (if known), and suspect's
address and phone number (if known). Fields for a
brief narrative and signatures are also provided.
The form will be expanded to capture the
suspect's "Crew" association (if known). MCSO
wants to capture this information and associate
the suspect and/or moniker information as
described above.. A Crew inquiry should be
treated similar to a Moniker inquiry and return all
events, and or associations. Although the graffiti
technician is not dispatched, the graffiti
occurrence should be treated similar to an event
at the location specified, and photos of the graffiti
should be able to be attached. The offeror is being
asked to propose a method of providing this
requested functionality.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1535
Out of the Box
Motorola
ROR003
OTHER
REQUESTED
FUNCTIONALITY
General
FORMS CONTROL LIBRARY
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1536
Out of the Box
Motorola
ROR003-1
OTHER
REQUESTED
FUNCTIONALITY
General
In several sections of this requirements document
MCSO has asked to populate data from a forms
template or input screen to one or more additional
forms templates. The intent of this section is to
provide additional clarification on exactly what is
being requested. The County is creating one or
more committees to design, approve, and manage
all official forms documents. Once forms are
approved, their templates would be housed in a
Forms Library that would be centrally controlled.
Most forms capture information that is redundant
to information already captured to properly
document an event. A DUI related arrest for
example requires the suspect's information to be
captured on several different forms. The Use of
Force form is another example of having to
capture numerous data fields that have already
been input to the DR.. Data entry fields contained
in any form template approved and housed in the
Forms Library would have commonly redundant
data entry fields mapped one to the other and to
information entered into OR and FI entry screens.
Mandatory
Records
X
PremierOne does not have this
functionality. PremierOne cannot
auto-populate information from
one form to another. We do
provide various ways a user can pull
forward Master or People
information from one document to
another.
MCSO team stated this is not
required to be met.
1537
Cannot Meet
Motorola
ROR003-2
OTHER
REQUESTED
FUNCTIONALITY
General
MCSO is asking for the capability to retrieve a
forms template from the Forms Library, and ask
that information already entered into a report or
other form be used to auto-populate the form just
requested. This process will not value all fields in
the form being auto-populated, nor will the
results of the transfer always be correct. Once a
form template is auto-populated the user must be
able to enter missing information and edit the
transferred data. When the user considers the
auto-populated a form complete and accurate, it
can be stored and associated with a DR, printed,
and/or routed to a destination point. The form
type will dictate how the form is further
processed. In providing this explanation MCSO is
not trying to specify how this functionality must be
provided. The intent is to simply specify what
needs to be provided to reduce a serious problem
of having to enter the same information into
multiple forms.
Mandatory
Records
X
PremierOne does not have this
functionality. PremierOne cannot
auto-populate information from
one form to another. The pull-
forward functionality can be used
to pull master records into forms.
Calls for Service information can be
mapped into different forms.
MCSO team stated this is not
required to be met.
1538
Cannot Meet
Page 108 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
ROR003-3
OTHER
REQUESTED
FUNCTIONALITY
General
Vendors are also being asked to offer their
solutions to this duplicate data entry problem. If
an approach similar to the one above is proposed,
please specify in detail how MCSO would go about
adding new forms templates to the Library and
mapping their common fields for auto-population.
The intent is to be able to fully manage the
process without requiring vendor support.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. New forms can be
added using our Advanced
Configuration Tool (ACT). Master
information can be mapped to pull
and push.
1539
With Configuration
Motorola
ROR004
OTHER
REQUESTED
FUNCTIONALITY
General
CASH ACCOUNT MANAGEMENT
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1540
Cannot Meet
Motorola
ROR004-1
OTHER
REQUESTED
FUNCTIONALITY
General
The MCSO maintains cash accounts within
multiple specialty units to make cash immediately
available for drug buys, to pay confidential
informants, and transact other authorized
purchases. MCSO needs to acquire a Cash
Management System with the following
capabilities and features:
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1541
Cannot Meet
Motorola
ROR004-1-1
OTHER
REQUESTED
FUNCTIONALITY
General
The system needs a robust security front end that
limits the use of the system to only those
individuals authorized to have access and make
entries. Two levels of access need to be provided.
Comptroller Level would have access to all cash
accounts maintained by the MCSO. The
Comptroller would have the capability to run audit
reports on all accounts and would receive monthly
reconciliation reports for each cash account. Only
the Comptroller can enter a reconciliation entry
into the system adjusting the system balance to
the cash on hand. The Comptroller would be able
to check the current status of all accounts at any
time. A Cash Account Manager Level would be
assigned to select individuals within each detail
that manages a cash account. Only the designated
Cash Account Managers can enter deposit,
withdrawal, and transfer transactions for their
detail's cash account. They are not provided access
to the accounts in other details. Access should
require a user ID, a robust password (FBI CJIS
compliant) and a challenge response if equipment
outside the normal work area is being used.
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1542
Cannot Meet
Motorola
ROR004-1-2
OTHER
REQUESTED
FUNCTIONALITY
General
All deposit entries must identify the person
transacting the deposit, the source of the funds,
the amount being deposited, data and time, and
the reason for the deposit. The reason can default
to "Fund Replenishment" if the deposit is not
earmarked for a specific purpose. A return of
money previously issued to an officer that is now
returning all or a portion of the money must also
identify the officer returning the money, the
reason for the return, and the original event for
which the money was withdrawn.
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1543
Cannot Meet
Motorola
ROR004-1-3
OTHER
REQUESTED
FUNCTIONALITY
General
All withdrawals must identify the person
transacting the withdrawal, the amount being
withdrawn, the person receiving the cash, the date
and time, and the reason for the withdrawal.
MCSO has developed codes for the more common
reasons for withdrawal, but a freeform text field
must be available for situations that are not code
identified.
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1544
Cannot Meet
Motorola
ROR004-1-4
OTHER
REQUESTED
FUNCTIONALITY
General
A transfer from one cash account to another is a
rare event, but the capability to do so is being
requested. The transaction would be similar to a
withdrawal except that a flag would be set in the
receiving account system and the Cash Account
comptroller would be notified if a deposit equal to
the withdrawal is not made into the receiving
account with 24 hours.
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1545
Cannot Meet
Page 109 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
ROR004-1-5
OTHER
REQUESTED
FUNCTIONALITY
General
At the end of each month the Cash Account
Managers must reconcile the remaining balances
shown by the system with the actual cash on
hand. If there is an imbalance, the Cash Account
Comptroller is notified and is provided a reason for
the imbalance if one is known. The Cash Account
Comptroller with debit or credit the system to
clear the imbalance. The reconciliation will appear
on the monthly report sent to the MCSO Finance.
If the cash on hand is equal to the balance
reported by the system, the Cash Account
Managers need to make a memo entry that is
date and time stamped by the system that reports
that a reconciliation was completed and the
amounts are in balance.
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1546
Cannot Meet
Motorola
ROR004-1-6
OTHER
REQUESTED
FUNCTIONALITY
General
If a unit's cash account involves multiple types of
cash funds (Under Cover and RICO for example)
separate cash handing and reporting is required
for each type.
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1547
Cannot Meet
Motorola
ROR004-1-7
OTHER
REQUESTED
FUNCTIONALITY
General
The capability to scan in cash receipts and other
supporting expenditure documents that can be
liked back to their originating withdrawal
transactions is needed.
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1548
Cannot Meet
Motorola
ROR004-1-8
OTHER
REQUESTED
FUNCTIONALITY
General
The department will work with the vendor
selected to build valid code tables and design
report formats and screen displays. Vendors are
asked to include samples of their standard report
formats and screen displays.
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1549
Cannot Meet
Motorola
ROR005
OTHER
REQUESTED
FUNCTIONALITY
General
ELECTRONIC TICKETING
Mandatory
CommandCentral
Responder
X
PremierOne complies with the
functionality as described in the
requirement.
1550
Out of the Box
Motorola
ROR005-1
OTHER
REQUESTED
FUNCTIONALITY
General
Vendors who have integrated mobile ticketing
solutions into their CAD/RMS are asked to bid
functionality to enable officers to issue traffic
citations from their mobile computers in patrol
vehicles.
Mandatory
CommandCentral
Responder
X
PremierOne complies with the
functionality as described in the
requirement.
1551
Out of the Box
Motorola
ROR005-2
OTHER
REQUESTED
FUNCTIONALITY
General
The system offered must be able to import
information needed to complete an Arizona
approved citation from data returned from
ACIC/NCIC, motor vehicle queries and from
scanning the offender's drivers license.
Mandatory
CommandCentral
Responder
X
PremierOne complies with the
functionality as described in the
requirement.
1552
Out of the Box
Motorola
ROR005-3
OTHER
REQUESTED
FUNCTIONALITY
General
The system offered must be able to determine the
appropriate court, statute number and fine from
the violation code and location of the offense.
Mandatory
CommandCentral
Responder
X
PremierOne complies with the
functionality as described in the
requirement.
1553
Out of the Box
Motorola
ROR005-4
OTHER
REQUESTED
FUNCTIONALITY
General
Print solutions for printing the current multi-part
citation and a single offender copy using thermal
paper should be provided and priced separately.
Include recommended printers of both type and
pricing.
Mandatory
CommandCentral
Responder
X
PremierOne complies with the
functionality as described in the
requirement. Printers to be used by
Windows mobile devices need to
be Windows compatible.
CommandCentral Responder
supports specific printers: Brother
PocketJet 8 (Model PJ863) or Zebra
(ZQ521) with Zebra Link-OS.
Motorola recommends purchasing
printers through state contract.
1554
Out of the Box
Motorola
ROR005-5
OTHER
REQUESTED
FUNCTIONALITY
General
The capability to issue multiple citations by pulling
data from the initial citation created is needed.
Mandatory
CommandCentral
Responder
X
PremierOne complies with the
functionality as described in the
requirement.
1555
Out of the Box
Motorola
ROR005-6
OTHER
REQUESTED
FUNCTIONALITY
General
The citations need to be edited while they are
being created and no citation can be finalized that
contains errors or omissions.
Mandatory
CommandCentral
Responder
X
PremierOne complies with the
functionality as described in the
requirement.
1556
Out of the Box
Motorola
ROR005-7
OTHER
REQUESTED
FUNCTIONALITY
General
The County has a requirement to attempt to
obtain the offender's signature on a criminal cite
and release citation. Vendors are asked to
recommend and include pricing for wireless
signature capture devices.
Mandatory
CommandCentral
Responder
X
PremierOne complies with the
functionality as described in the
requirement. CommandCentral
Responder utilizes an Android/iOS
device. Signatures are captured
directly on the device, therefore, no
additional signature device is
required.
1557
Out of the Box
Page 110 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
ROR005-8
OTHER
REQUESTED
FUNCTIONALITY
General
Once a citation is completed the citation data
must be electronically transmitted to the RMS and
Court systems.
Mandatory
CommandCentral
Responder
X
PremierOne complies with the
functionality as described in the
requirement. Motorola has
included a citation interface to the
court system with our solution.
1558
Out of the Box
Motorola
ROR005-9
OTHER
REQUESTED
FUNCTIONALITY
General
Vendors are being ask to price software and
hardware components separately and to provide
volume purchase discount thresholds for each
Mandatory
CommandCentral
Responder
X
PremierOne complies with the
functionality as described in the
requirement.
1559
Out of the Box
Motorola
ROR006
OTHER
REQUESTED
FUNCTIONALITY
General
ENTERPRISE DOCUMENT IMAGING
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement partnering with
Laserfiche. Motorola Solutions has
included a Laserfiche File
Attachment interface.
1560
With Third Party Vendor
Motorola
ROR006-1
OTHER
REQUESTED
FUNCTIONALITY
General
In several of the requirement sections of this
request the need to image documents and index
them to case numbers, names, and other fields
has been listed as a requirement. Because much
of the information being collected is criminal
history by definition the system proposed must
have security requirement equal to those applied
to criminal histories in the RMS. By this we mean
that if a scanned document is indexed to one or
more other RMS identifiers, it must take on the
security afforded the identifier with the highest
security provisions. Document stored by the Civil
Division would be in separate account from
documents stored by GIB and not shared unless
authorization is provided by the account owner.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement partnering with
Laserfiche. Motorola Solutions has
included a Laserfiche File
Attachment interface.
1561
With Third Party Vendor
Motorola
ROR006-2
OTHER
REQUESTED
FUNCTIONALITY
General
Documents can be entered from any authorized
scanner on the network.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement partnering with
Laserfiche. Motorola Solutions has
included a Laserfiche File
Attachment interface.
1562
With Third Party Vendor
Motorola
ROR006-3
OTHER
REQUESTED
FUNCTIONALITY
General
The system proposed must provide secure central
storage, versioning, metadata, and security, as
well as advanced indexing and retrieval
capabilities.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement partnering with
Laserfiche. Motorola Solutions has
included a Laserfiche File
Attachment interface.
1563
With Third Party Vendor
Motorola
ROR006-4
OTHER
REQUESTED
FUNCTIONALITY
General
Metadata must capture the documents type,
date/time the document was stored, by whom,
and the capability to describe why the document is
germane to the case, person, event or other
field(s) it is being indexed to.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement partnering with
Laserfiche. Motorola Solutions has
included a Laserfiche File
Attachment interface.
1564
With Third Party Vendor
Motorola
ROR006-5
OTHER
REQUESTED
FUNCTIONALITY
General
County would like to see the document imaging
solution tightly integrated with the CAD/RMS so
that documents can be accessed from the
document management system, updated if not
classed as evidence, and returned to the image
repository without leaving the CAD/RMS. It should
be transparent to the user that a second system is
involved.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement partnering with
Laserfiche. Motorola Solutions has
included a Laserfiche File
Attachment interface.
1565
With Third Party Vendor
Motorola
ROR006-6
OTHER
REQUESTED
FUNCTIONALITY
General
Should support common integration standards
such as ODMA, SOAP, LDAP, WebDAV.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement partnering with
Laserfiche. Motorola Solutions has
included a Laserfiche File
Attachment interface.
1566
With Third Party Vendor
Motorola
ROR006-7
OTHER
REQUESTED
FUNCTIONALITY
General
Users should be able to retrieve documents by
their index topology and by unique document
identifiers when available, and by partial search
terms expected in the metadata.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1567
Out of the Box
Page 111 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
ROR006-8
OTHER
REQUESTED
FUNCTIONALITY
General
The proposed system should include a rights
manager module that allows an administrator to
give access to documents based upon type to only
a certain people or details.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1568
Out of the Box
Motorola
ROR006-9
OTHER
REQUESTED
FUNCTIONALITY
General
Documents identified as evidence must be marked
at the time of creation to preclude alteration or
unintended use. Vendors are to explain in detail
how this is to be accomplished.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. The document would
be placed into the Property and
Evidence module as seized then
placed into QueTel.
1569
Out of the Box
Motorola
ROR006-10
OTHER
REQUESTED
FUNCTIONALITY
General
Some documents in Civil Process for example need
to be sent to someone else for review and
approval within an established period of time. The
County would like to see a rules base workflow
component that can route documents based upon
the rule set established.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1570
Out of the Box
Motorola
ROR006-11
OTHER
REQUESTED
FUNCTIONALITY
General
The system should provide an audit trail of all
changes made to a document (i.e. Date, time,
changes made, and by whom).
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1571
Out of the Box
Motorola
ROR006-12
OTHER
REQUESTED
FUNCTIONALITY
General
The system proposed should allow versioning, and
allow users to retrieve previous versions.
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1572
Cannot Meet
Motorola
ROR006-13
OTHER
REQUESTED
FUNCTIONALITY
General
The system must provide the capability for its
designated owner to seal a document by signature
or other process. Once sealed a document can no
longer be modified.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1573
Out of the Box
Motorola
RCP001
CIVIL PROCESS
DIVISION
General
The Civil Division performs several distinct
functions:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1574
Out of the Box
Motorola
RCP001-1
CIVIL PROCESS
DIVISION
General
The MCSO Civil Process Division serves all Superior
Court civil processes including: civil
summons/subpoenas, Orders of Protection, writs
of execution, garnishment, restitution, replevin,
and attachments, as well as various other in-state
and out-of-state court documents and process.
Levy on real and personal property to dispose of
by Sheriff’s auction or other means as ordered by
the court. Complete affidavits of service on all
process showing the type of service made, actions
taken, and if the documents were not served an
accurate report of the actions taken.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1575
Out of the Box
Motorola
RCP002
CIVIL PROCESS
DIVISION
General
Civil Process:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1576
Out of the Box
Motorola
RCP002-1
CIVIL PROCESS
DIVISION
General
Serves all Superior Court civil process including:
civil summons subpoenas, Orders of Protection,
writs of execution, garnishment, restitution,
replevin, and attachments, as well as various other
In and out of court documents and processes.
Levy on real and personal property to dispose of
by Sheriff's auction or other means as ordered by
the court. Complete affidavits of service on all
processes showing the type of service made,
actions taken, and if documents were not served
an accurate report on the actions taken.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1577
Out of the Box
Page 112 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RCP002-2
CIVIL PROCESS
DIVISION
General
To automate the above functions the Civil Process
Division requires a system that will capture the
following information when entering documents
and deposit information, and include the following
functionality:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Possibly the most
dynamic and powerful tool
available today in the industry is
Motorola Solutions’ PremierOne
Advanced Configuration Tool (ACT).
With ACT, agencies can modify
existing software modules or create
new modules, including data
elements, field edits, workflow and
reporting. This is like having a
software developer included at no
extra charge to meet the needs of
the agency, without custom
programming. PremierOne Records
is unique in its ability to allow the
creation of agency-specific
modules. These simple modules
provide a centralized location for
the traditional paper forms that all
public safety agencies maintain.
An agency can have the time
saving, cost benefits of a central
repository for the many forms that
flood the department. Since these
d l
il bl f
i
h
1578
With Configuration
Motorola
RCP002-2-1
CIVIL PROCESS
DIVISION
General
Case number(s)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1579
Out of the Box
Motorola
RCP002-2-2
CIVIL PROCESS
DIVISION
General
State where paperwork originates
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1580
Out of the Box
Motorola
RCP002-2-3
CIVIL PROCESS
DIVISION
General
Designation if paperwork is a warrant
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1581
Out of the Box
Motorola
RCP002-2-4
CIVIL PROCESS
DIVISION
General
Identification type of attorney/Pro per (i.e. driver’s
license, bar number, social security #)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1582
With Configuration
Motorola
RCP002-2-5
CIVIL PROCESS
DIVISION
General
Driver’s license #, bar # or social security #
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1583
Out of the Box
Motorola
RCP002-2-6
CIVIL PROCESS
DIVISION
General
State where identification type originates
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1584
Out of the Box
Motorola
RCP002-2-7
CIVIL PROCESS
DIVISION
General
Plaintiff’s first, middle, & last name
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1585
Out of the Box
Motorola
RCP002-2-8
CIVIL PROCESS
DIVISION
General
Plaintiff’s company name
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1586
Out of the Box
Motorola
RCP002-2-9
CIVIL PROCESS
DIVISION
General
Attorney’s firm or Pro per’s name
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1587
With Configuration
Motorola
RCP002-2-10
CIVIL PROCESS
DIVISION
General
3 additional lines for attorney’s/Pro per’s address
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1588
With Configuration
Motorola
RCP002-2-11
CIVIL PROCESS
DIVISION
General
Phone number for attorney/Pro per
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1589
With Configuration
Motorola
RCP002-2-12
CIVIL PROCESS
DIVISION
General
Code for common attorney’s/plaintiff’s name &
addresses
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1590
With Configuration
Motorola
RCP002-2-13
CIVIL PROCESS
DIVISION
General
Defendant’s first, middle & last name
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1591
With Configuration
Page 113 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RCP002-2-14
CIVIL PROCESS
DIVISION
General
Defendant’s company name
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1592
With Configuration
Motorola
RCP002-2-15
CIVIL PROCESS
DIVISION
General
Person(s) being served
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1593
Out of the Box
Motorola
RCP002-2-16
CIVIL PROCESS
DIVISION
General
3 lines for person(s)’ address being served
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1594
Out of the Box
Motorola
RCP002-2-17
CIVIL PROCESS
DIVISION
General
3 lines for person(s)’ phone number(s) being
served
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1595
Out of the Box
Motorola
RCP002-2-18
CIVIL PROCESS
DIVISION
General
# of Defendant(s)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1596
With Configuration
Motorola
RCP002-2-19
CIVIL PROCESS
DIVISION
General
Designation if paperwork is a real estate sale
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1597
With Configuration
Motorola
RCP002-2-20
CIVIL PROCESS
DIVISION
General
Designation if fees are waived
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1598
Out of the Box
Motorola
RCP002-2-21
CIVIL PROCESS
DIVISION
General
Designation if fees are deferred
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1599
Out of the Box
Motorola
RCP002-2-22
CIVIL PROCESS
DIVISION
General
Date document(s) received
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1600
Out of the Box
Motorola
RCP002-2-23
CIVIL PROCESS
DIVISION
General
Time document(s) received
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1601
Out of the Box
Motorola
RCP002-2-24
CIVIL PROCESS
DIVISION
General
Beat number of deputy serving
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1602
With Configuration
Motorola
RCP002-2-25
CIVIL PROCESS
DIVISION
General
Zip code of place paperwork being served
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1603
Out of the Box
Motorola
RCP002-2-26
CIVIL PROCESS
DIVISION
General
Type of document(s) being served
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1604
Out of the Box
Motorola
RCP002-2-27
CIVIL PROCESS
DIVISION
General
# of original(s), copy(ies), and file copy(ies) being
served
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1605
With Configuration
Motorola
RCP002-2-28
CIVIL PROCESS
DIVISION
General
Designation if paperwork is main paper
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1606
With Configuration
Motorola
RCP002-2-29
CIVIL PROCESS
DIVISION
General
Court date or serve by date of paperwork
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1607
Out of the Box
Motorola
RCP002-2-30
CIVIL PROCESS
DIVISION
General
Special service instructions
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1608
Out of the Box
Motorola
RCP002-2-31
CIVIL PROCESS
DIVISION
General
Deposit type
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1609
With Configuration
Motorola
RCP002-2-32
CIVIL PROCESS
DIVISION
General
Deposit amount
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1610
Out of the Box
Motorola
RCP002-2-33
CIVIL PROCESS
DIVISION
General
Receipt number from cash register
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1611
Out of the Box
Motorola
RCP002-2-34
CIVIL PROCESS
DIVISION
General
Information about cash/check/money
order/cashier’s check/credit/debit payment
received
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1612
With Configuration
Page 114 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RCP002-2-35
CIVIL PROCESS
DIVISION
General
Automatic internal control number (called docket
number) assigned by computer after information
is entered
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1613
With Configuration
Motorola
RCP002-3
CIVIL PROCESS
DIVISION
General
The System should print a worksheet with some of
the pertinent information above for each set of
paperwork entered
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1614
Out of the Box
Motorola
RCP002-4
CIVIL PROCESS
DIVISION
General
The System should capture the following pertinent
information when recording disposition of
paperwork being processed after being returned
from deputy:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1615
Out of the Box
Motorola
RCP002-4-1
CIVIL PROCESS
DIVISION
General
# of attempts
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1616
Out of the Box
Motorola
RCP002-4-2
CIVIL PROCESS
DIVISION
General
Date being returned as served, not served, etc.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1617
Out of the Box
Motorola
RCP002-4-3
CIVIL PROCESS
DIVISION
General
# of each document being returned
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1618
Out of the Box
Motorola
RCP002-4-4
CIVIL PROCESS
DIVISION
General
Deputy’s badge number
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1619
Out of the Box
Motorola
RCP002-4-5
CIVIL PROCESS
DIVISION
General
Designation if paperwork is being transferred
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1620
With Configuration
Motorola
RCP002-4-6
CIVIL PROCESS
DIVISION
General
If paperwork being transferred, record beat
paperwork is being transferred to
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1621
With Configuration
Motorola
RCP002-4-7
CIVIL PROCESS
DIVISION
General
Code designating paperwork is served, not served,
etc.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1622
Out of the Box
Motorola
RCP002-4-8
CIVIL PROCESS
DIVISION
General
Designation if paperwork is in-state, out-of-state,
or a Writ
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1623
Out of the Box
Motorola
RCP002-4-9
CIVIL PROCESS
DIVISION
General
Sufficient lines to designate service or non-service
information
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1624
Out of the Box
Motorola
RCP002-4-10
CIVIL PROCESS
DIVISION
General
An information screen to record any additional
information received regarding this case
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1625
Out of the Box
Motorola
RCP002-5
CIVIL PROCESS
DIVISION
General
The System should have the capabilities below and
capture the following pertinent information when
recording the fees for paperwork being processed
after being returned from deputy:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1626
Out of the Box
Motorola
RCP002-5-1
CIVIL PROCESS
DIVISION
General
System should be able to determine whether fees
can be entered based on information inputted
when documents were received
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1627
With Configuration
Motorola
RCP002-5-2
CIVIL PROCESS
DIVISION
General
Billing code for service, handling, mileage, etc.
and the corresponding fee for each type
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1628
With Configuration
Motorola
RCP002-5-3
CIVIL PROCESS
DIVISION
General
Statistical information regarding mileage, cash levy
information, sale information, etc.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1629
With Configuration
Motorola
RCP002-5-4
CIVIL PROCESS
DIVISION
General
A bill or refund check should be generated based
on the input of the above information
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1630
With Configuration
Motorola
RCP002-5-5
CIVIL PROCESS
DIVISION
General
Ability to close account or keep it open in order to
pay the Maricopa County Treasurer statutory fees
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1631
With Configuration
Page 115 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RCP002-5-6
CIVIL PROCESS
DIVISION
General
Ability of the system to bill each outstanding
account every 30 days up to 4 months and then
turn over to collections with information provided
above
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1632
Cannot Meet
Motorola
RCP002-6
CIVIL PROCESS
DIVISION
General
Ability to correct the following information in
screens:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1633
Out of the Box
Motorola
RCP002-6-1
CIVIL PROCESS
DIVISION
General
Case number
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1634
Out of the Box
Motorola
RCP002-6-2
CIVIL PROCESS
DIVISION
General
Plaintiff/Pro per/Defendant/Person being served
information
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1635
Out of the Box
Motorola
RCP002-6-3
CIVIL PROCESS
DIVISION
General
Document status
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1636
Out of the Box
Motorola
RCP002-6-4
CIVIL PROCESS
DIVISION
General
Ability to inquire a certain case by:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1637
Out of the Box
Motorola
RCP002-6-5
CIVIL PROCESS
DIVISION
General
Company name
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1638
Out of the Box
Motorola
RCP002-6-6
CIVIL PROCESS
DIVISION
General
Case number
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1639
Out of the Box
Motorola
RCP002-6-7
CIVIL PROCESS
DIVISION
General
Document status
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1640
Out of the Box
Motorola
RCP002-6-8
CIVIL PROCESS
DIVISION
General
Plaintiff name
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1641
Out of the Box
Motorola
RCP002-6-9
CIVIL PROCESS
DIVISION
General
Defendant name
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1642
With Configuration
Motorola
RCP002-6-10
CIVIL PROCESS
DIVISION
General
Person being served name
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1643
Out of the Box
Motorola
RCP002-6-11
CIVIL PROCESS
DIVISION
General
Address where being served
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1644
Out of the Box
Motorola
RCP002-6-12
CIVIL PROCESS
DIVISION
General
Comment inquiry
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1645
Out of the Box
Motorola
RCP002-6-13
CIVIL PROCESS
DIVISION
General
Ability to add charges or payments:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1646
Out of the Box
Motorola
RCP002-6-14
CIVIL PROCESS
DIVISION
General
Cash & fees entry
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1647
Out of the Box
Motorola
RCP002-6-15
CIVIL PROCESS
DIVISION
General
Charges entry
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1648
Out of the Box
Motorola
RCP002-7
CIVIL PROCESS
DIVISION
General
Correct/Maintain Financial Information:
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1649
Cannot Meet
Motorola
RCP002-7-1
CIVIL PROCESS
DIVISION
General
Financial adjustments
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1650
Cannot Meet
Motorola
RCP002-7-2
CIVIL PROCESS
DIVISION
General
Billing maintenance
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1651
Cannot Meet
Motorola
RCP002-8
CIVIL PROCESS
DIVISION
General
Ability to inquire financial transactions by:
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1652
Cannot Meet
Motorola
RCP002-8-1
CIVIL PROCESS
DIVISION
General
Check detail record
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1653
Cannot Meet
Motorola
RCP002-8-2
CIVIL PROCESS
DIVISION
General
Account information
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1654
Cannot Meet
Motorola
RCP002-8-3
CIVIL PROCESS
DIVISION
General
transaction information
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1655
Cannot Meet
Motorola
RCP002-8-4
CIVIL PROCESS
DIVISION
General
Bills outstanding
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1656
Cannot Meet
Motorola
RCP002-8-5
CIVIL PROCESS
DIVISION
General
Daily transaction inquiry
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1657
Cannot Meet
Motorola
RCP002-8-6
CIVIL PROCESS
DIVISION
General
Docket financial transaction
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1658
Cannot Meet
Motorola
RCP002-9
CIVIL PROCESS
DIVISION
General
Ability to maintain supervisory functions:
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1659
Cannot Meet
Motorola
RCP002-9-1
CIVIL PROCESS
DIVISION
General
Check reconciliation
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1660
Cannot Meet
Page 116 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RCP002-9-2
CIVIL PROCESS
DIVISION
General
Bank balancing work page
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1661
Cannot Meet
Motorola
RCP002-9-3
CIVIL PROCESS
DIVISION
General
Open/Close of business day
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1662
Cannot Meet
Motorola
RCP002-9-4
CIVIL PROCESS
DIVISION
General
Retire checks over 90 days old
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1663
Cannot Meet
Motorola
RCP002-9-5
CIVIL PROCESS
DIVISION
General
Pay State of Arizona Department of Revenue for
retired checks
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1664
Cannot Meet
Motorola
RCP002-9-6
CIVIL PROCESS
DIVISION
General
Deposit reconciliation
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1665
Cannot Meet
Motorola
RCP002-10
CIVIL PROCESS
DIVISION
General
Ability to inquire certain supervisory functions:
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1666
Cannot Meet
Motorola
RCP002-10-1
CIVIL PROCESS
DIVISION
General
Checks to be written
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1667
Cannot Meet
Motorola
RCP002-10-2
CIVIL PROCESS
DIVISION
General
Hand posted checks
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1668
Cannot Meet
Motorola
RCP002-10-3
CIVIL PROCESS
DIVISION
General
Closed cases
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1669
Cannot Meet
Motorola
RCP002-11
CIVIL PROCESS
DIVISION
General
Receive automatic reports after supervisory
functions:
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1670
Cannot Meet
Motorola
RCP002-11-1
CIVIL PROCESS
DIVISION
General
Total fees to Maricopa County Treasurer
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1671
Cannot Meet
Motorola
RCP002-11-2
CIVIL PROCESS
DIVISION
General
Print checks
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1672
Cannot Meet
Motorola
RCP002-12
CIVIL PROCESS
DIVISION
General
Create codes for frequently used records:
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1673
Cannot Meet
Motorola
RCP002-12-1
CIVIL PROCESS
DIVISION
General
Common billing code
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1674
Cannot Meet
Motorola
RCP002-12-2
CIVIL PROCESS
DIVISION
General
Account code
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1675
Cannot Meet
Motorola
RCP002-12-3
CIVIL PROCESS
DIVISION
General
Document type
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1676
Cannot Meet
Motorola
RCP002-12-4
CIVIL PROCESS
DIVISION
General
Officer maintenance
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1677
Cannot Meet
Motorola
RCP002-12-5
CIVIL PROCESS
DIVISION
General
Beat maintenance
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1678
Cannot Meet
Motorola
RCP002-12-6
CIVIL PROCESS
DIVISION
General
Documents to print
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1679
Cannot Meet
Motorola
RCP002-13
CIVIL PROCESS
DIVISION
General
Ability to make inquiries regarding common billing
codes
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1680
Out of the Box
Motorola
RCP002-14
CIVIL PROCESS
DIVISION
General
Ability of system to create and print affidavits,
returns and envelopes in Microsoft Word using
information inputted into system (and the ability
to make changes once affidavits/returns are
created)
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1681
With Configuration
Motorola
RCP002-15
CIVIL PROCESS
DIVISION
General
Ability of system to create and print daily
transaction reports for audit purposes
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1682
With Configuration
Motorola
RCP002-16
CIVIL PROCESS
DIVISION
General
Ability of system to create and print the following
reports in Microsoft Office products automatically
at the end of each month/period:
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1683
With Configuration
Motorola
RCP002-16-1
CIVIL PROCESS
DIVISION
General
# of service attempts
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1684
With Configuration
Motorola
RCP002-16-2
CIVIL PROCESS
DIVISION
General
Monthly activity report
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1685
With Configuration
Motorola
RCP002-16-3
CIVIL PROCESS
DIVISION
General
Order of Protection & Injunction Prohibiting
Harassment served & not served report
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1686
With Configuration
Motorola
RCP002-16-4
CIVIL PROCESS
DIVISION
General
Roster of checks written for the month
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1687
Cannot Meet
Motorola
RCP002-16-5
CIVIL PROCESS
DIVISION
General
Roster of checks over 60 days old
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1688
Cannot Meet
Page 117 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RCP002-16-6
CIVIL PROCESS
DIVISION
General
# of miles attempted for each set of paperwork
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1689
With Configuration
Motorola
RCP002-16-7
CIVIL PROCESS
DIVISION
General
Beat recap
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1690
With Configuration
Motorola
RCP002-16-8
CIVIL PROCESS
DIVISION
General
Zip code recap
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1691
With Configuration
Motorola
RCP002-16-9
CIVIL PROCESS
DIVISION
General
Outstanding bills report
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1692
With Configuration
Motorola
RCP002-16-10
CIVIL PROCESS
DIVISION
General
Bills outstanding over 90 days old
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1693
With Configuration
Motorola
RCP002-16-11
CIVIL PROCESS
DIVISION
General
Monthly master control
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1694
With Configuration
Motorola
RCP002-17
CIVIL PROCESS
DIVISION
General
Ability to create adhoc reports of any of the above
reporting information
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1695
With Configuration
Motorola
RCP002-18
CIVIL PROCESS
DIVISION
General
The System should be able to interact with the
cash register, debit/credit machine(s)
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1696
Cannot Meet
Motorola
RCP003
CIVIL PROCESS
DIVISION
General
Tax Collections
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1697
Cannot Meet
Motorola
RCP003-1
CIVIL PROCESS
DIVISION
General
Collection of delinquent personal property and
mobile home taxes including the seizure and sale
of personal property to satisfy the tax bill.
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1698
Cannot Meet
Motorola
RCP003-2
CIVIL PROCESS
DIVISION
General
The system should provide access to the County
Assessor’s records showing Account Number,
Name Fields, Address Fields, Property Information,
Resolution History, Comments, Delinquent Date,
Valuation Date
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1699
Cannot Meet
Motorola
RCP003-3
CIVIL PROCESS
DIVISION
General
The system should provide access to the County
Treasurer’s records showing Account Number,
Name Fields, Address Fields, Property Information,
Payment History, Comments, Total Due – broken
down by year, fees and interest.
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1700
Cannot Meet
Motorola
RCP003-4
CIVIL PROCESS
DIVISION
General
The system should allow Sheriff’s Office comments
to be entered for a history of the account. The
Treasurer & Assessor would also be able to view
the comments entered.
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1701
Cannot Meet
Motorola
RCP003-5
CIVIL PROCESS
DIVISION
General
The system should able to have fees added to the
account that would also reflect on the Treasurer’s
system.
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1702
Cannot Meet
Motorola
RCP003-6
CIVIL PROCESS
DIVISION
General
The system should be able to generate Tax Bills,
Seizure Notices, Sale Notices, Affidavits, Deputy
Worksheets and Bill of Sales. There would also
need to be comments as to what notices have
been sent out and a “tickler” that would bring the
account to attention when the next step in the
process needs to be generated.
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1703
Cannot Meet
Motorola
RCP003-7
CIVIL PROCESS
DIVISION
General
The system should be able to provide statistical
information as to how many accounts have been
billed, how much as been billed, what
Deputy/Clerk is doing the work, etc.
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1704
Cannot Meet
Motorola
RCP003-8
CIVIL PROCESS
DIVISION
General
The system would need to show immediately
when payments from the Treasurer’s system are
applied.
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1705
Cannot Meet
Page 118 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RCP003-9
CIVIL PROCESS
DIVISION
General
The system would need to be able to be query by
name, address, years delinquent, and amounts
due
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1706
Out of the Box
Motorola
RCP003-10
CIVIL PROCESS
DIVISION
General
The system should be able to interact with the
cash register, debit/credit, payment processing,
etc. in the event that the Tax Unit starts taking
payments again.
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1707
Cannot Meet
Motorola
RCP004
CIVIL PROCESS
DIVISION
General
Subpoenas
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1708
Out of the Box
Motorola
RCP004-1
CIVIL PROCESS
DIVISION
General
Service of criminal summons/subpoenas for the
Superior Court. A subpoena being a process
commanding a witness to appear and give
testimony in a matter before the court. A
Subpoena Duces Tecum being a process by which
the court commands a witness who has in his/her
possession or control some document or paper
that is pertinent to the issues of a pending
controversy, to produce it at trial.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1709
Out of the Box
Motorola
RCP004-2
CIVIL PROCESS
DIVISION
General
The System should capture the following pertinent
information when inputting subpoenas:
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1710
With Configuration
Motorola
RCP004-2-1
CIVIL PROCESS
DIVISION
General
Case number(s)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1711
Out of the Box
Motorola
RCP004-2-2
CIVIL PROCESS
DIVISION
General
Court code
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1712
Out of the Box
Motorola
RCP004-2-3
CIVIL PROCESS
DIVISION
General
Attorney’s bar number
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1713
With Configuration
Motorola
RCP004-2-4
CIVIL PROCESS
DIVISION
General
Attorney’s first, middle, and last name, including
suffix
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1714
With Configuration
Motorola
RCP004-2-5
CIVIL PROCESS
DIVISION
General
Title of attorney
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1715
With Configuration
Motorola
RCP004-2-6
CIVIL PROCESS
DIVISION
General
Attorney’s phone number
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1716
With Configuration
Motorola
RCP004-2-7
CIVIL PROCESS
DIVISION
General
Attorney’s extension
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1717
With Configuration
Motorola
RCP004-2-8
CIVIL PROCESS
DIVISION
General
2 address lines for attorney
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1718
With Configuration
Motorola
RCP004-2-9
CIVIL PROCESS
DIVISION
General
City
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1719
With Configuration
Motorola
RCP004-2-10
CIVIL PROCESS
DIVISION
General
State
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1720
With Configuration
Motorola
RCP004-2-11
CIVIL PROCESS
DIVISION
General
Zip code
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1721
With Configuration
Page 119 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RCP004-2-12
CIVIL PROCESS
DIVISION
General
Designation if county attorney or not
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1722
With Configuration
Motorola
RCP004-2-13
CIVIL PROCESS
DIVISION
General
Defendant(s) name(s), including suffixes
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1723
With Configuration
Motorola
RCP004-2-14
CIVIL PROCESS
DIVISION
General
Defendant(s) alias(as), including suffixes
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1724
With Configuration
Motorola
RCP004-2-15
CIVIL PROCESS
DIVISION
General
Charges against Defendant(s)
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1725
With Configuration
Motorola
RCP004-2-16
CIVIL PROCESS
DIVISION
General
Witness’ first, middle, last name(s), including
suffixes
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1726
Out of the Box
Motorola
RCP004-2-17
CIVIL PROCESS
DIVISION
General
Serial # (if witness is law enforcement)
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1727
With Configuration
Motorola
RCP004-2-18
CIVIL PROCESS
DIVISION
General
“In care of” box
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1728
With Configuration
Motorola
RCP004-2-19
CIVIL PROCESS
DIVISION
General
P.O. Box #
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1729
Out of the Box
Motorola
RCP004-2-20
CIVIL PROCESS
DIVISION
General
Address #
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1730
Out of the Box
Motorola
RCP004-2-21
CIVIL PROCESS
DIVISION
General
Direction
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1731
Out of the Box
Motorola
RCP004-2-22
CIVIL PROCESS
DIVISION
General
Street Name
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1732
Out of the Box
Motorola
RCP004-2-23
CIVIL PROCESS
DIVISION
General
Suffix
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1733
Out of the Box
Motorola
RCP004-2-24
CIVIL PROCESS
DIVISION
General
Apartment #
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1734
Out of the Box
Motorola
RCP004-2-25
CIVIL PROCESS
DIVISION
General
City
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1735
Out of the Box
Motorola
RCP004-2-26
CIVIL PROCESS
DIVISION
General
State
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1736
Out of the Box
Motorola
RCP004-2-27
CIVIL PROCESS
DIVISION
General
Zip Code (which will fill in the “beat” entry below)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1737
Out of the Box
Motorola
RCP004-2-28
CIVIL PROCESS
DIVISION
General
Beat
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1738
Out of the Box
Motorola
RCP004-2-29
CIVIL PROCESS
DIVISION
General
Home Phone
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1739
Out of the Box
Motorola
RCP004-2-30
CIVIL PROCESS
DIVISION
General
Work Phone
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1740
Out of the Box
Motorola
RCP004-2-31
CIVIL PROCESS
DIVISION
General
Work Extension
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1741
Out of the Box
Motorola
RCP004-2-32
CIVIL PROCESS
DIVISION
General
Area for warnings and special service instructions
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1742
Out of the Box
Motorola
RCP004-2-33
CIVIL PROCESS
DIVISION
General
Date subpoena received
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1743
Out of the Box
Page 120 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RCP004-2-34
CIVIL PROCESS
DIVISION
General
Designate if subpoena is to be mailed, personally
served, or faxed
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1744
Out of the Box
Motorola
RCP004-2-35
CIVIL PROCESS
DIVISION
General
Designate if subpoena is mental health or regular
subpoena
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1745
With Configuration
Motorola
RCP004-2-36
CIVIL PROCESS
DIVISION
General
Court date
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1746
Out of the Box
Motorola
RCP004-2-37
CIVIL PROCESS
DIVISION
General
Court time
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1747
Out of the Box
Motorola
RCP004-2-38
CIVIL PROCESS
DIVISION
General
Designate type of subpoena (criminal, juvenile,
etc.)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1748
Out of the Box
Motorola
RCP004-3
CIVIL PROCESS
DIVISION
General
The system should print deputy worksheets or
postcards & envelopes for each subpoena entered
(including bar code to identify each worksheet or
postcard printed)
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1749
With Configuration
Motorola
RCP004-4
CIVIL PROCESS
DIVISION
General
The System should capture the following pertinent
information when recording disposition of the
subpoena being processed after being returned
from deputy or in mail:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1750
Out of the Box
Motorola
RCP004-4-1
CIVIL PROCESS
DIVISION
General
Use bar code to identify postcard or worksheet
being returned
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1751
With Configuration
Motorola
RCP004-4-2
CIVIL PROCESS
DIVISION
General
Return disposition line (served, not served,
witness dead, moved, etc.)
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1752
Out of the Box
Motorola
RCP004-4-3
CIVIL PROCESS
DIVISION
General
Date and time returned
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1753
Out of the Box
Motorola
RCP004-4-4
CIVIL PROCESS
DIVISION
General
Deputy serial number
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1754
Out of the Box
Motorola
RCP004-4-5
CIVIL PROCESS
DIVISION
General
Deputy last name
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1755
Out of the Box
Motorola
RCP004-4-6
CIVIL PROCESS
DIVISION
General
Deputy first name
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1756
Out of the Box
Motorola
RCP004-4-7
CIVIL PROCESS
DIVISION
General
Mileage
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1757
Out of the Box
Motorola
RCP004-4-8
CIVIL PROCESS
DIVISION
General
Activity Comments section
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1758
Out of the Box
Motorola
RCP004-5
CIVIL PROCESS
DIVISION
General
The System should allow the ability to update, edit
and print the following items:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1759
Out of the Box
Motorola
RCP004-5-1
CIVIL PROCESS
DIVISION
General
Post cards
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1760
With Configuration
Motorola
RCP004-5-2
CIVIL PROCESS
DIVISION
General
Envelopes
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1761
With Configuration
Motorola
RCP004-5-3
CIVIL PROCESS
DIVISION
General
Worksheets
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1762
Out of the Box
Motorola
RCP004-6
CIVIL PROCESS
DIVISION
General
The System should allow the following items to be
used as shortcuts to enter information
automatically :
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1763
Cannot Meet
Motorola
RCP004-6-1
CIVIL PROCESS
DIVISION
General
Activity Result
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1764
Cannot Meet
Motorola
RCP004-6-2
CIVIL PROCESS
DIVISION
General
Activity Type
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1765
Cannot Meet
Motorola
RCP004-6-3
CIVIL PROCESS
DIVISION
General
Attorney/Justice Courts
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1766
Cannot Meet
Motorola
RCP004-6-4
CIVIL PROCESS
DIVISION
General
Class Type
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1767
Cannot Meet
Page 121 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RCP004-6-5
CIVIL PROCESS
DIVISION
General
Court Codes
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1768
Cannot Meet
Motorola
RCP004-6-6
CIVIL PROCESS
DIVISION
General
Service Type
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1769
Cannot Meet
Motorola
RCP004-6-7
CIVIL PROCESS
DIVISION
General
Beat Information
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1770
Cannot Meet
Motorola
RCP004-6-8
CIVIL PROCESS
DIVISION
General
Exception Beat
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1771
Cannot Meet
Motorola
RCP004-6-9
CIVIL PROCESS
DIVISION
General
Subpoena Beat
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1772
Cannot Meet
Motorola
RCP004-6-10
CIVIL PROCESS
DIVISION
General
Subpoena Statistics
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1773
Cannot Meet
Motorola
RCP004-6-11
CIVIL PROCESS
DIVISION
General
Beat Zip Code
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1774
Cannot Meet
Motorola
RCP004-7
CIVIL PROCESS
DIVISION
General
The System should allow the following reports to
be generated:
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1775
With Configuration
Motorola
RCP004-7-1
CIVIL PROCESS
DIVISION
General
Defendant/Witness Court Date
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1776
With Configuration
Motorola
RCP004-7-2
CIVIL PROCESS
DIVISION
General
No Results Activity Over 60 Days
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1777
With Configuration
Motorola
RCP004-7-3
CIVIL PROCESS
DIVISION
General
Mailed Pending by Date Selection
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1778
With Configuration
Motorola
RCP004-7-4
CIVIL PROCESS
DIVISION
General
Personal Pending by Date Selection
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1779
With Configuration
Motorola
RCP004-7-5
CIVIL PROCESS
DIVISION
General
Witness Future Court Dates
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1780
With Configuration
Motorola
RCP004-7-6
CIVIL PROCESS
DIVISION
General
Witness Select by Court Date
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1781
With Configuration
Motorola
RCP004-7-7
CIVIL PROCESS
DIVISION
General
Witness Select by Last Name
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1782
With Configuration
Motorola
RCP004-7-8
CIVIL PROCESS
DIVISION
General
Check Address For Prior’s
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1783
With Configuration
Motorola
RCP004-7-9
CIVIL PROCESS
DIVISION
General
Run Statistics Report
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1784
With Configuration
Motorola
RCP004-7-10
CIVIL PROCESS
DIVISION
General
Subpoena Beat Totals
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1785
With Configuration
Motorola
RCP004-7-11
CIVIL PROCESS
DIVISION
General
Subpoena Beat List
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1786
With Configuration
Motorola
RCP004-7-12
CIVIL PROCESS
DIVISION
General
Subpoena By Address
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1787
With Configuration
Page 122 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RCP004-7-13
CIVIL PROCESS
DIVISION
General
Print Single Case
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1788
With Configuration
Motorola
RCP005
CIVIL PROCESS
DIVISION
General
PERSONAL & REAL PROPERTY SEIZURES & SALES
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1789
With Configuration
Motorola
RCP005-1
CIVIL PROCESS
DIVISION
General
The System should capture the following
information and additional information regarding
personal or real property seizures and sales:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1790
With Configuration
Motorola
RCP005-1-1
CIVIL PROCESS
DIVISION
General
Plaintiff
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1791
Out of the Box
Motorola
RCP005-1-2
CIVIL PROCESS
DIVISION
General
Defendant
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1792
With Configuration
Motorola
RCP005-1-3
CIVIL PROCESS
DIVISION
General
Defendant body from writ
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1793
With Configuration
Motorola
RCP005-1-4
CIVIL PROCESS
DIVISION
General
Case number
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1794
Out of the Box
Motorola
RCP005-1-5
CIVIL PROCESS
DIVISION
General
Docket number
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1795
With Configuration
Motorola
RCP005-1-6
CIVIL PROCESS
DIVISION
General
Document issued
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1796
Out of the Box
Motorola
RCP005-1-7
CIVIL PROCESS
DIVISION
General
Day document issued
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1797
Out of the Box
Motorola
RCP005-1-8
CIVIL PROCESS
DIVISION
General
Month and year document issued
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1798
Out of the Box
Motorola
RCP005-1-9
CIVIL PROCESS
DIVISION
General
Judgment day issued
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1799
With Configuration
Motorola
RCP005-1-10
CIVIL PROCESS
DIVISION
General
Month and year judgment issued
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1800
With Configuration
Motorola
RCP005-1-11
CIVIL PROCESS
DIVISION
General
Amount of judgment
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1801
With Configuration
Motorola
RCP005-1-12
CIVIL PROCESS
DIVISION
General
Amount of interest
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1802
With Configuration
Motorola
RCP005-1-13
CIVIL PROCESS
DIVISION
General
Costs
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1803
With Configuration
Motorola
RCP005-1-14
CIVIL PROCESS
DIVISION
General
Judgment sum
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1804
With Configuration
Page 123 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RCP005-1-15
CIVIL PROCESS
DIVISION
General
Interest day started
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1805
With Configuration
Motorola
RCP005-1-16
CIVIL PROCESS
DIVISION
General
Month and year interest started
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1806
With Configuration
Motorola
RCP005-1-17
CIVIL PROCESS
DIVISION
General
Percent interest
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1807
With Configuration
Motorola
RCP005-1-18
CIVIL PROCESS
DIVISION
General
Levy day
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1808
With Configuration
Motorola
RCP005-1-19
CIVIL PROCESS
DIVISION
General
Month and year levy
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1809
With Configuration
Motorola
RCP005-1-20
CIVIL PROCESS
DIVISION
General
Property one
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1810
With Configuration
Motorola
RCP005-1-21
CIVIL PROCESS
DIVISION
General
Property two
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1811
With Configuration
Motorola
RCP005-1-22
CIVIL PROCESS
DIVISION
General
Property three
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1812
With Configuration
Motorola
RCP005-1-23
CIVIL PROCESS
DIVISION
General
Property four
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1813
With Configuration
Motorola
RCP005-1-24
CIVIL PROCESS
DIVISION
General
Property five
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1814
With Configuration
Motorola
RCP005-1-25
CIVIL PROCESS
DIVISION
General
Sale day
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1815
With Configuration
Motorola
RCP005-1-26
CIVIL PROCESS
DIVISION
General
Month and year of sale
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1816
With Configuration
Motorola
RCP005-1-27
CIVIL PROCESS
DIVISION
General
Place of sale
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1817
With Configuration
Motorola
RCP005-1-28
CIVIL PROCESS
DIVISION
General
Day typed
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1818
With Configuration
Motorola
RCP005-1-29
CIVIL PROCESS
DIVISION
General
Month and year typed
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1819
With Configuration
Motorola
RCP005-1-30
CIVIL PROCESS
DIVISION
General
Deputy
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1820
Out of the Box
Page 124 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RCP005-1-31
CIVIL PROCESS
DIVISION
General
cc
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1821
With Configuration
Motorola
RCP005-1-32
CIVIL PROCESS
DIVISION
General
A number
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1822
Out of the Box
Motorola
RCP005-1-33
CIVIL PROCESS
DIVISION
General
Plaintiff body from writ
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1823
With Configuration
Motorola
RCP005-1-34
CIVIL PROCESS
DIVISION
General
Bidder’s name
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1824
With Configuration
Motorola
RCP005-1-35
CIVIL PROCESS
DIVISION
General
Bid sum spelled
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1825
With Configuration
Motorola
RCP005-1-36
CIVIL PROCESS
DIVISION
General
Bid amount
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1826
With Configuration
Motorola
RCP005-1-37
CIVIL PROCESS
DIVISION
General
Day document received
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1827
Out of the Box
Motorola
RCP005-1-38
CIVIL PROCESS
DIVISION
General
Month and year document received
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1828
Out of the Box
Motorola
RCP005-1-39
CIVIL PROCESS
DIVISION
General
Number of parcels
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1829
Out of the Box
Motorola
RCP005-1-40
CIVIL PROCESS
DIVISION
General
Wholly or partially
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1830
With Configuration
Motorola
RCP005-1-41
CIVIL PROCESS
DIVISION
General
Accrued costs
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1831
With Configuration
Motorola
RCP005-1-42
CIVIL PROCESS
DIVISION
General
Accrued costs written
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1832
With Configuration
Motorola
RCP005-1-43
CIVIL PROCESS
DIVISION
General
Interest
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1833
With Configuration
Motorola
RCP005-1-44
CIVIL PROCESS
DIVISION
General
Attorney fees
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1834
With Configuration
Motorola
RCP005-1-45
CIVIL PROCESS
DIVISION
General
Additional costs
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1835
With Configuration
Motorola
RCP005-1-46
CIVIL PROCESS
DIVISION
General
IC
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1836
With Configuration
Motorola
RCP005-1-47
CIVIL PROCESS
DIVISION
General
Balance due
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1837
With Configuration
Page 125 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RCP005-1-48
CIVIL PROCESS
DIVISION
General
Overpayment
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1838
With Configuration
Motorola
RCP005-1-49
CIVIL PROCESS
DIVISION
General
Lien holder
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1839
With Configuration
Motorola
RCP005-1-50
CIVIL PROCESS
DIVISION
General
Lien holder extra line
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1840
With Configuration
Motorola
RCP005-1-51
CIVIL PROCESS
DIVISION
General
Lien holder street
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1841
With Configuration
Motorola
RCP005-1-52
CIVIL PROCESS
DIVISION
General
Lien holder P.O. Box
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1842
With Configuration
Motorola
RCP005-1-53
CIVIL PROCESS
DIVISION
General
Lien holder city
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1843
With Configuration
Motorola
RCP005-1-54
CIVIL PROCESS
DIVISION
General
Lien holder state
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1844
With Configuration
Motorola
RCP005-1-55
CIVIL PROCESS
DIVISION
General
Lien holder zip code
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1845
With Configuration
Motorola
RCP005-1-56
CIVIL PROCESS
DIVISION
General
Lien amount
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1846
With Configuration
Motorola
RCP005-1-57
CIVIL PROCESS
DIVISION
General
Lien date
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1847
With Configuration
Motorola
RCP005-2
CIVIL PROCESS
DIVISION
General
The System should be able to create and print the
following documents seizures and sales:
Mandatory
Records
X
As part of deployment Motorola
will apply canned reports to the
system and lead a reporting writing
workshop with County personnel.
1848
With Configuration
Motorola
RCP005-2-1
CIVIL PROCESS
DIVISION
General
Levy
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1849
With Configuration
Motorola
RCP005-2-2
CIVIL PROCESS
DIVISION
General
Sale notices
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1850
With Configuration
Motorola
RCP005-2-3
CIVIL PROCESS
DIVISION
General
Various returns
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1851
With Configuration
Motorola
RCP005-2-4
CIVIL PROCESS
DIVISION
General
Certificates of sale
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1852
With Configuration
Page 126 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RCP005-2-5
CIVIL PROCESS
DIVISION
General
Deeds
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1853
With Configuration
Motorola
RCP005-2-6
CIVIL PROCESS
DIVISION
General
Release letters
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1854
With Configuration
Motorola
RCP005-2-7
CIVIL PROCESS
DIVISION
General
Form letters to MVD, FAA, Game & Fish, etc.
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1855
With Configuration
Motorola
RCP005-2-8
CIVIL PROCESS
DIVISION
General
Lien letters
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1856
With Configuration
Motorola
RCP005-2-9
CIVIL PROCESS
DIVISION
General
Demand letters
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1857
With Configuration
Motorola
RCP005-2-10
CIVIL PROCESS
DIVISION
General
Envelopes
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1858
With Configuration
Motorola
RCP005-2-11
CIVIL PROCESS
DIVISION
General
Sale notice posting information sheets
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1859
With Configuration
Motorola
RCP005-2-12
CIVIL PROCESS
DIVISION
General
Sale book information
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1860
With Configuration
Motorola
RCP005-2-13
CIVIL PROCESS
DIVISION
General
Affidavits of service
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1861
With Configuration
Motorola
RCP006
CIVIL PROCESS
DIVISION
General
Orders of Protection/Warrants
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1862
Out of the Box
Motorola
RCP006-1
CIVIL PROCESS
DIVISION
General
Orders of Protection or injunctions against
harassment may be obtained through all Justice
Courts, Municipal Courts, and the Maricopa
County Superior Court. The Sheriff's Office serves
orders issued by the Superior Court, while
municipal police handle orders issued by the
Municipal Courts, and orders issued by Justice
Courts are served by the appropriate Constable.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. Motorola interprets
this requirement as uploading of
the document(s) and recording of
serving of those documents.
1863
Out of the Box
Motorola
RCP006-2
CIVIL PROCESS
DIVISION
General
Add to the information page. Check box when
background completed. Add second page with
template matching existing memo showing
background investigation results. Forward
information to OIC.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1864
With Configuration
Motorola
RCP006-3
CIVIL PROCESS
DIVISION
General
Scanning to add out of state information i.e.
driver’s license photo/booking photo.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. The system excepts
attachments of this nature.
1865
Out of the Box
Motorola
RCP006-4
CIVIL PROCESS
DIVISION
General
Need the capability to log all orders served and
orders pending service. This information should
be able to be retrieved by subject serverd. Subject
being protected, addresses of either party etc.
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1866
Cannot Meet
Motorola
RCP006-5
CIVIL PROCESS
DIVISION
General
Ability to query how many Orders of Protections
processed on a monthly basis, and year to year.
Same with warrants.
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1867
With Configuration
Motorola
RCP007
CIVIL PROCESS
DIVISION
General
Pawnshop and Second Hand Store Sub-System
Mandatory
Records
X
PremierOne does not have this
functionality.
MCSO team stated this is not
required to be met.
1868
Cannot Meet
Page 127 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RCP007-1
CIVIL PROCESS
DIVISION
General
Issuance of Pawnshop/Second Hand licenses for
Maricopa County. Coordinating hearings for the
suspension or revocation of pawnshop licenses.
Investigating the recovery of property reported
stolen within the SO's jurisdiction that is recovered
in any pawnshop within the County, and the
coordination of the subsequent release of the
property. Investigating the recovery of property
reported stolen from outside of Arizona and
recovered in pawnshops in the SO's jurisdiction,
and coordinating the subsequent release of that
property. Investigating administrative and
criminal violations regarding the operation of
pawnshops and second hand stores in the SO's
jurisdiction. Vendors are being asked to include
functionality for pawnshop and second hand store
requirements when completing their responses to
the REGISTRANT AND REGISTRATION TRACKING /
LICENSEE AND LICENSEE TRACKING Section of this
request. Vendors are further ask to bid a total
replacement of the current County Pawn Sub-
System in their response to the section titled Pawn
Sub-System herein. Vendors who cannot offer a
total replacement system are asked to bid an
interface from their RMS to the county's current
Pawn Sub-System to export stolen property with
proper identifying numbers. See the Interfaces
S
i
f hi d
f
f
h
d
il
Mandatory
Records
X
PremierOne does not have this
functionality. Motorola has
included a Pawn inbound interface
with the solution. See "Pawn"
section of this matrix for further
details.
MCSO team stated this is not
required to be met.
1869
Cannot Meet
Motorola
RCP008
CIVIL PROCESS
DIVISION
General
ATF Class III Firearms
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1870
With Configuration
Motorola
RCP008-1
CIVIL PROCESS
DIVISION
General
The Bureau of Alcohol Tobacco and Firearms
requires that the Maricopa County Sheriffs Office,
as the Chief Law Enforcement Officer, certify that
no information is available that would disqualify
an ATF form 4 applicant (transferee) from
receiving or possessing the firearm described in
Item 4 of the application being considered. The
process leading to an approval or denial is as
follows:
Mandatory
Records
X
Motorola's PremierOne RMS
system is not designed to be public
facing. This can be accomplished
by County personnel gathering
required information from the
applicant and entering it in the RMS
system.
1871
With Configuration
Motorola
RCP008-1-1
CIVIL PROCESS
DIVISION
General
The application packet is checked to see if it has
been completed properly, contains the required
two copies, signatures are notarized, contains a
photograph, contains a valid picture identification
such as a Driver's License or Passport.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1872
With Configuration
Motorola
RCP008-1-2
CIVIL PROCESS
DIVISION
General
Photocopies are made of the valid identification
documents to allow their return to the owner.
Mandatory
Records
X
The system can accept document
uploads.
1873
With Configuration
Motorola
RCP008-1-3
CIVIL PROCESS
DIVISION
General
Verify current contact information and write it on
the photocopy. Date and time stamp the
photocopy.
Mandatory
Records
X
The system can accept document
uploads.
1874
With Configuration
Motorola
RCP008-1-4
CIVIL PROCESS
DIVISION
General
The MCSO employee processing the application
writes their A number on the photocopy.
Mandatory
Records
X
The system can accept document
uploads.
1875
With Configuration
Motorola
RCP008-1-5
CIVIL PROCESS
DIVISION
General
If the application packet is not in proper order it is
returned to the applicant for correction.
Mandatory
Records
X
Validation of fields can be utilized in
the configuration.
1876
With Configuration
Motorola
RCP008-1-6
CIVIL PROCESS
DIVISION
General
If the application packet is in order automated and
manual queries are made to other municipal,
county, state and federal systems seeking
information on the applicant. Queries are made to
MVD (KQ), Interstate Identification Index-National
Criminal History (AHQH-III), MCSO JMS, MCSO
RMS, Warrants (ACQW), State Criminal History
(AHSR), MCSO Jail Visitation (DNB1) and PACE
Phoenix Police RMS (phone call to check for
Warrants and recent criminal involvement), CAIS,
County Attorney's Information System, and other
systems as necessary.
Mandatory
Records
X
Queries for this functionality have
been scoped for the system.
1877
With Third Party Vendor
Motorola
RCP008-1-7
CIVIL PROCESS
DIVISION
General
The results of these inquiries are attached to a
Face Sheet Document used to track the
verification process. Each hit must list the agency
name, the charges, whether a suspect or victim,
incident date and location, and disposition if
available.
Mandatory
Records
X
Queries for this functionality have
been scoped for the system.
1878
With Configuration
Page 128 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RCP008-1-8
CIVIL PROCESS
DIVISION
General
If a hit occurs the agency having the hit is
contacted and asked to fax the supporting
documentation. A record of the contact is noted
on the face sheet. If a response is not returned
within one week, re-contact the agency. This
process is repeated until a response is received.
Mandatory
Records
X
Queries for this functionality have
been scoped for the system.
1879
With Configuration
Motorola
RCP008-1-9
CIVIL PROCESS
DIVISION
General
Once the requested report is received, update the
face sheet with all pertinent information, including
disposition if available, and any anomaly or
peculiarity.
Mandatory
Records
X
The face sheet would be updated
by the user(s) after receiving the
requested report.
1880
With Configuration
Motorola
RCP008-1-10
CIVIL PROCESS
DIVISION
General
Once it is apparent that the application is being
denied; the draft face sheet with notations is used
to prepare a final document, the packet is
transferred to a red folder with the final face sheet
and supporting documents placed in an
established order, and a denial letter is prepared
for the Captain's signature. The applicant will be
contacted and given/sent a copy of the denial
letter. A notation is made in the ATF log indicating
the disposition. The packet is retained on file to
be available if there is an appeal of the denial.
Otherwise it is retained until it can be legally
disposed of.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1881
With Configuration
Motorola
RCP008-1-11
CIVIL PROCESS
DIVISION
General
Once it is apparent that no disqualifying
information has been found; the draft face sheet is
used to prepare a final document, the packet is
transferred to a blue folder, ATF Forms are
prepared for signature, a Thank You letter is
prepared, sign here postems are attached to the
signature locations, and the blue folder with all
documents arranged in the established order is
sent up a three step chain of command for
signatures. The packet is retained along with a
copy of the ATF Form 4.
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1882
With Configuration
Motorola
RCP008-2
CIVIL PROCESS
DIVISION
General
Vendor's are being asked to offer solutions for
automating the above process. Third party
applications will be considered if they will be
supported under one maintenance agreement
with the primary vendor. Functionality should
include:
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1883
Out of the Box
Motorola
RCP008-2-1
CIVIL PROCESS
DIVISION
General
Record keeping of applicants similar to pawn
system. Ability to query by name, address,
telephone and id numbers.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1884
With Configuration
Motorola
RCP008-2-2
CIVIL PROCESS
DIVISION
General
Template matching existing memo showing
background investigation results and pending
information. Update and add to the information
to include new application date for repeat
applicants. Be part of the applicants file as listed
above.
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1885
With Configuration
Motorola
RCP008-2-3
CIVIL PROCESS
DIVISION
General
Approved/Disapproved section with reasons/
comments
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1886
With Configuration
Motorola
RCP008-2-4
CIVIL PROCESS
DIVISION
General
Tracking received date, signatures and completion,
how many applications approved, disapproved and
pending monthly basis
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1887
With Configuration
Motorola
RCP008-2-5
CIVIL PROCESS
DIVISION
General
Scanning ability for reports.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1888
Out of the Box
Motorola
RCP008-2-6
CIVIL PROCESS
DIVISION
General
Payments received. Same format as Civil.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1889
With Configuration
Motorola
RCP008-2-7
CIVIL PROCESS
DIVISION
General
The capability to list an applicant and his/her
history of weapons acquired by date ranges,
overall, by address, and by surname only to help
track unusual buying patterns.
Mandatory
Records
X
The Motorola system is capable of
creating and printing reports with
information available in the
database via SSRS reports authored
by the County.
1890
With Configuration
Page 129 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RCP009
CIVIL PROCESS
DIVISION
General
Extradition
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1891
With Configuration
Motorola
RCP009-1
CIVIL PROCESS
DIVISION
General
Extradition is the official process whereby one
nation or state surrenders a suspected or
convicted criminal to another nation or state. …
Mandatory
Records
X
The following requirements
(RCP009-x) are understood as the
ability to document such
occurances in the master record(s).
1892
With Configuration
Motorola
RCP009-2
CIVIL PROCESS
DIVISION
General
Interstate Extradition - The term applied to the
process of removing a person from one state to
face charges in another state. Federal law and the
US Constitution govern interstate extradition, but
the process still varies from state to state. The
process timeline begins when a person is arrested,
either based upon a "fugitive of justice" warrant or
when they are detained for an infraction in
another state. It is standard operating procedure
for agencies to run a "wants and warrants"
computer check looking for "fugitive of justice'\"
wants and warrants. The moment the requesting
state is notified of the presence of their fugitive in
custody a timeline starts for the state to process
their extradition request. The timeline for the
request starts with the notification of detention
and will expire at the end of 90 days. If an Arizona
agency is holding the detainee and he or she is not
picked up within the 90 day period the detainee
must be released from custody.
Mandatory
Records
X
This requirement is understood as
the ability to document such
occurance in the master record(s).
1893
With Configuration
Motorola
RCP009-3
CIVIL PROCESS
DIVISION
General
The detainee may waive the issuance and service
of the warrant and all other procedures incidental
to the extradition proceedings buy prescribing in
the presence of a judge of a court of record within
the state a writing which stated that he/she
consents to the return to the demanding state. If
consent is duly execute, the judge shall direct the
officer who has custody to deliver the detainee
promptly to the accredited agent or agents of the
demanding state along with a copy of the consent.
Mandatory
Records
X
This requirement is understood as
the ability to document such
occurance in the master record(s).
1894
With Configuration
Motorola
RCP009-4
CIVIL PROCESS
DIVISION
General
A law enforcement agency holding a person who is
alleged to have broken the terms of his/her
probation, parole, bail or other release shall
immediately deliver the person to the duly
authorized agent of the demanding state without
the requirement of a Governor's warrant if the
detainee has signed a prior waiver of extradition
as a term of his/her current probation, bail or
other release in the demanding state, and the law
enforcement agency holding the person has
received an authenticated copy of the prior waiver
of extradition signed by the detainee, and the
demanding state submits a photograph and
fingerprints identifying the person who signed the
waiver. This provision does not constitute a waiver
by the detaining state of its right, power or
privilege to try the fugitive for a criminal offense
committed in in the detaining sate. If a local
criminal charge is pending against the fugitive in a
court in the detaining state, the fugitive's transfer
of custody is subject to the discretion of the
Governor. Delivery of a fugitive to an agent of the
demanding state does not constitute a waiver of
the state's right, power or privilege to regain
custody of the person by extradition, detainer
proceedings, or other process for the purpose of
trial for any offense charged against the person in
h
i i
l d
i i
Mandatory
Records
X
This requirement is understood as
the ability to document such
occurance in the master record(s).
1895
With Configuration
Page 130 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RCP009-5
CIVIL PROCESS
DIVISION
General
If a criminal prosecution has been instituted
against such person under the laws of the
detaining state and is still pending the Governor
may either surrender the person on demand of the
Governor of another state or may continue to
hold the person until the person has been tried
and discharged or convicted and punished in the
detaining state. This action would not constitute
a waiver by the demanding state of its right,
power or privilege to extradite when the fugitive is
released.
Mandatory
Records
X
This requirement is understood as
the ability to document such
occurance in the master record(s).
1896
With Configuration
Motorola
RCP009-6
CIVIL PROCESS
DIVISION
General
If the demanding state wishes to obtain custody of
a person charged in the demanding state with a
criminal offense and the person was convicted or
is imprisoned or held under criminal proceedings
then pending in a third state, the Governors of the
detaining and demanding states may agree on the
extradition before the criminal proceedings have
terminated or the persons sentence has been
served. A Governors' agreement of this type is
conditioned upon the return of the person to the
original detaining state at the demanding state's
expense as soon as the prosecution is terminated,
unless the person is sentenced to death.
Mandatory
Records
X
This requirement is understood as
the ability to document such
occurance in the master record(s).
1897
With Configuration
Motorola
RCP009-7
CIVIL PROCESS
DIVISION
General
Extradition Documents - A warrant of extradition
will not be issued by the detaining state unless the
documents presented by the demanding state's
executive authority clearly show - except in cases
that fall under ARS 13-3845, the accused was
present in the demanding state at the time of the
commission of the alleged crime, and thereafter
fled the state, and the accused is now in the
detaining state ( photo and fingerprints), and the
accused is lawfully charged by indictment found or
by information filed by a prosecuting officer and
supported by affidavit to the facts, or by affidavit
made before a magistrate in that state, with
having committed a crime under the laws of that
state, or has been convicted of a crime in that
state and has escaped confinement or broken
parole.
Mandatory
Records
X
This requirement is understood as
the ability to document such
occurance in the master record(s).
1898
With Configuration
Motorola
RCP009-8
CIVIL PROCESS
DIVISION
General
Recovery of Expenses - On conviction of the crime
that caused a person to be extradited to the
demanding state, the state or political subdivision,
either jointly or severally, may recover from the
convicted person the actual expenses incurred by
the extraditing agency.
Mandatory
Records
X
This requirement is understood as
the ability to document such
occurance in the master record(s).
1899
With Configuration
Page 131 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RCP009-9
CIVIL PROCESS
DIVISION
General
Interstate Agreement on Detainers - This
agreement applies to transfers of sentenced
prisoners for unrelated trials between two States,
and to transfers from the Federal Government to
the States, and from States to the Federal
Government. The agreement permits a prisoner
to initiate final disposition of any untried
indictment, information, or complaint against
him/her in another State on the basis of which a
detainer has been lodged against him/her. Upon
return of the prisoner, and without good cause
continuances granted by the court in the presence
of the prisoner and his/her attorney, trial shall be
commenced within one hindered and twenty five
days of the arrival of the prisoner in the receiving
State. If this time limitation requirement is not
met the receiving states' indictment shall be
dismissed with prejudice. Article III of the
Agreement also establishes that trial must
commence within 180 days of receipt by
prosecuting State of prisoner's request for final
disposition of charges identified in the detainer.
These two time constraints narrow the time
available for physically extraditing prisoners.
Mandatory
Records
X
This requirement is understood as
the ability to document such
occurance in the master record(s).
1900
With Configuration
Motorola
RCP009-10
CIVIL PROCESS
DIVISION
General
The Supreme has further complicated the
extradition process by ruling that prisoners have
extradition rights under the laws of the State of
incarceration. This entitles the prisoner to a
hearing before he/she can be transferred from the
custody of the State of incarceration.
Mandatory
Records
X
This requirement is understood as
the ability to document such
occurance in the master record(s).
1901
With Configuration
Motorola
RCP009-11
CIVIL PROCESS
DIVISION
General
The Agreement also allows a Governor only 30
days in which to disapprove a request or transfer
on his/her motion or that of the prisoner.
Mandatory
Records
X
This requirement is understood as
the ability to document such
occurance in the master record(s).
1902
With Configuration
Motorola
RCP009-12
CIVIL PROCESS
DIVISION
General
Vendors are being asked to offer solutions for
automating the above processes. Third party
applications will be considered if they will be
supported under one maintenance agreement
with the primary vendor. The system should
provide the capability to establish an event file for
each extradition activity. The type of request and
the requesting agency should prompt "action
reminders" to the officer or officers assigned
based upon the time constraints involved. The
system should support access to the queries
required to determine if a prisoner is
"extraditable". The system should also provide the
capability of tracking all travel expenses incurred
per event, and reports should be supported that
will aggregate costs by geographic area of the
country and distance from Phoenix by selected
dates. Reports are needed that will compare
expenses by year and report percentage of
increase and decline. Cash Account Management
is also a requirement that vendors need to address
for this section, or when responding to the Cash
Account Management Section of this document.
Mandatory
Records
X
This is understood as a distinct
module (or combination of) that
records the parameters that make
up this process with appropriate
timestamps and expirations
dependent on parameters outlined
above.
Motorola cannot comply with
tracking and aggregating costs as
depicted in the requirement.
MCSO team stated this is not
required to be met.
1903
Cannot Meet
Motorola
RCP010
CIVIL PROCESS
DIVISION
General
Each agency shall have the ability to customize the
“canned” reports, and where practical to direct
the output of reports to Microsoft mail merge.
Mandatory
Records
X
Canned reports are availabile as
well as Microsoft SQL Reporitng
tools, dissemination of reports can
be done through exports of the
data from the reporting tool
1904
Out of the Box
Motorola
RCP011
CIVIL PROCESS
DIVISION
General
The system shall allow for multiple paper types.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1905
Out of the Box
Motorola
RCP012
CIVIL PROCESS
DIVISION
General
The system shall track the mileage related to each
service attempt.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1906
Out of the Box
Motorola
RCP013
CIVIL PROCESS
DIVISION
General
The system shall track costs and payments
associated with service.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1907
Out of the Box
Page 132 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
RCP014
CIVIL PROCESS
DIVISION
General
The system shall track service attempts and
completions as well as notes.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1908
Out of the Box
Motorola
RCP015
CIVIL PROCESS
DIVISION
General
The system shall capture change of address
information obtained during the service attempt.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1909
Out of the Box
Motorola
RCP016
CIVIL PROCESS
DIVISION
General
The system must provide for the indexing and
cross-referencing of persons involved in these
papers.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1910
Out of the Box
Motorola
RCP017
CIVIL PROCESS
DIVISION
General
Associated events information must update all
master indices
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1911
Out of the Box
Motorola
RCP018
CIVIL PROCESS
DIVISION
General
The systems must be able to attach external
documents such as Court orders and doctor’s
reports.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1912
Out of the Box
Motorola
RCP019
CIVIL PROCESS
DIVISION
General
The system must access all master indices for the
creation of a civil process record.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1913
Out of the Box
Motorola
RCP020
CIVIL PROCESS
DIVISION
General
The system shall produce a deputy work list
including a listing of papers that are assigned to
either a specific deputy or to a geographic
area/shift.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1914
Out of the Box
Motorola
RCP021
CIVIL PROCESS
DIVISION
General
The system must provide browse, maintain, and
enter capabilities into the civil process module
based upon log-on security.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1915
Out of the Box
Motorola
RCP022
CIVIL PROCESS
DIVISION
General
The system shall have access to a common ad hoc
reporting tool that is shared by all applications.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1916
Out of the Box
Motorola
RCP023
CIVIL PROCESS
DIVISION
General
The completion of service shall remove this paper
from the deputy’s workload assignment.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1917
Out of the Box
Motorola
RCP024
CIVIL PROCESS
DIVISION
General
The officer shall be able to update the service
attempts/completions by selecting each paper
from this list.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1918
Out of the Box
Motorola
RCP025
CIVIL PROCESS
DIVISION
General
The system shall save the paper list of the process
papers that were assigned to each officer.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1919
Out of the Box
Motorola
RCP026
CIVIL PROCESS
DIVISION
General
If the paper is served by substitute service, the
deputy shall be able to enter the reason for the
substitute service and the person served.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1920
With Configuration
Motorola
RCP027
CIVIL PROCESS
DIVISION
General
When a paper is served, the deputy shall be able
to enter the service information including the
date/time of service, the person served, the
location of the service and notes.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1921
Out of the Box
Motorola
RCP028
CIVIL PROCESS
DIVISION
General
The system must provide advisory information,
such as gang member or sex of offender.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1922
With Configuration
Motorola
RCP029
CIVIL PROCESS
DIVISION
General
The system shall contain a subpoena tracking
capability that tracks officer’s receipt of both civil
and criminal subpoenas.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1923
Out of the Box
Motorola
RCP030
CIVIL PROCESS
DIVISION
General
The system shall provide a free-text narrative area
for the deputy to enter instructions for
subsequent service attempts.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1924
Out of the Box
Motorola
RCP031
CIVIL PROCESS
DIVISION
General
The system shall record the receipt of a restraining
order, including the person who is being served,
the person who has received it, the address of the
person and the restrictions associated to the
order.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement.
1925
Out of the Box
Motorola
RCP032
CIVIL PROCESS
DIVISION
General
The system shall record if a foreclosure
announcement has been advertised, the
newspaper used, and the date/time.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1926
With Configuration
Motorola
RCP033
CIVIL PROCESS
DIVISION
General
The system shall record foreclosures that are
issued by a court.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1927
With Configuration
Motorola
RCP034
CIVIL PROCESS
DIVISION
General
The system shall record a judgment from a court
for an individual or a business.
Mandatory
Records
X
PremierOne complies with the
functionality as described in the
requirement. If all fields are not
already present, they can be
created utilizing ACT.
1928
With Configuration
Page 133 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CYBS001
Cyber Security
Gap Analysis
Vendor must understand the organizational
sector, risk profile, threats, and assets.
Mandatory
Risk Assessment
X
PremierOne complies with the
functionality as described in the
requirement.
1929
Out of the Box
Motorola
CYBS002
Cyber Security
Gap Analysis
Vendor must measure the risk and/or compliance
in the organization against one or more
frameworks
Mandatory
Risk Assessment
X
PremierOne complies with the
functionality as described in the
requirement.
1930
Out of the Box
Motorola
CYBS003
Cyber Security
Gap Analysis
Vendor must evaluate and report on current
network and connectivity environment (Internal,
External)
Mandatory
PenTest
X
PremierOne complies with the
functionality as described in the
requirement.
1931
Out of the Box
Motorola
CYBS004
Cyber Security
Gap Analysis
Vendor must determine the existing controls and
the controls that will need to be remediated
Mandatory
Risk Assessment
X
PremierOne complies with the
functionality as described in the
requirement.
1932
Out of the Box
Motorola
CYBS005
Cyber Security
Gap Analysis
Review existing policies, procedures, and
workflows to determine additional needs and
documents that will need to be enhanced.
Mandatory
Risk Assessment
X
PremierOne complies with the
functionality as described in the
requirement.
1933
Out of the Box
Motorola
CYBS006
Cyber Security
Gap Analysis
Create a Plan of Action that will define the
remediation needs and be used to track
remediation progress.
Mandatory
Risk Assessment
X
PremierOne complies with the
functionality as described in the
requirement.
1934
Out of the Box
Motorola
CYBS007
Cyber Security
System Security Plan Develop and document an organizational
understanding to manage cybersecurity risk to
systems assets, data, and capabilities.
Mandatory
System Security
Plan
X
PremierOne complies with the
functionality as described in the
requirement.
1935
Out of the Box
Motorola
CYBS008
Cyber Security
System Security Plan The SSP (System Security Plan) will define MCSO’s
overall program, including the technology
environment, implemented controls, polices that
support the controls, define the assets, and
support infrastructure.
Mandatory
System Security
Plan
X
PremierOne complies with the
functionality as described in the
requirement.
1936
Out of the Box
Motorola
CYBS009
Cyber Security
System Security Plan The SSP (System Security Plan) will demonstrate
how the implemented controls, policies, training
and maintenance process meets the required NIST
framework compliance requirements.
Mandatory
System Security
Plan
X
PremierOne complies with the
functionality as described in the
requirement.
1937
Out of the Box
Motorola
CYBS010
Cyber Security
System Security Plan This document provides a centralized repository
for knowledge that is specific to MCSO's
Technology Bureau environment and the
applicable security controls employed in the
environment. The SSP reflects input from those
responsible for the maintenance and operation of
the environment, including information owners,
system operators, and other stakeholders.
Mandatory
System Security
Plan
X
PremierOne complies with the
functionality as described in the
requirement.
1938
Out of the Box
Motorola
CYBS011
Cyber Security
Cyber Incident
Response Plan
Develop and document an organizational
understanding to manage cybersecurity risk to
systems assets, data, and capabilities.
Mandatory
System Security
Plan
X
PremierOne complies with the
functionality as described in the
requirement.
1939
Out of the Box
Motorola
CYBS012
Cyber Security
Cyber Incident
Response Plan
The SSP (System Security Plan) will define MCSO's
overall program, including the technology
environment, implemented controls, polices that
support the controls, define the assets, and
support infrastructure.
Mandatory
System Security
Plan
X
PremierOne complies with the
functionality as described in the
requirement.
1940
Out of the Box
Motorola
CYBS013
Cyber Security
Disaster Recovery
Plan
Develop, document, and implement appropriate
activities to act upon, contain, and reduce the
impact of an event. The CIRP (Computer Incident
Response Plan) will provide the operation’s
response personnel with a reference guide for
handling cyber incidents that might impact the
business.
Mandatory
System Security
Plan
X
PremierOne complies with the
functionality as described in the
requirement.
1941
Out of the Box
Motorola
CYBS014
Cyber Security
Disaster Recovery
Plan
The plan provides steps for responding to
computer security incidents and standardized
process flows that include:
a) Identify the incident response (IR) stakeholders
and establish their roles and responsibilities.
b) Describes incident triggering sources, incident
types, and incident severity levels.
c) Provide instruction and details on required
Federal and State reporting requirements.
d) Includes requirements for annual testing,
including post-incident lessons-learned activities.
Mandatory
System Security
Plan
X
PremierOne complies with the
functionality as described in the
requirement.
1942
Out of the Box
Page 134 of 135
Motorola Solutions, Inc.
Exhibit G - RMS Functional Matrix
Vendor
Requirement ID
Requirement
Category
Requirement Sub-
Category
Requirement Description
Priority (Mandatory,
Preferred, Optional)
Module
Out of the Box
With
Configuration
With
Programmin
g
Future
Release
With Third
Party
Vendor
Cannot
Meet
Explanation
Motorola / MCSO Review Notes
Disposition of Motorola's Cannot
Meet responses
Sort ID
Translation
MCSO and Motorola Agreement to Requirements Responded to as "Cannot Meet"
Original Motorola Response
Motorola
CYBS015
Cyber Security
General
At least one (1) of the primary or lead personnel
should have at least one of the following
certifications: GIAC Certified Incident Handler
(GCIH) GIAC Continuous Monitoring Certification
(GMON) GIAC Certified Detection Analyst (GCDA)
EC-Council Certified Incident Handler (ECIH)
Software Engineering Institute (SEI) Certificate in
Incident Response Process Computer Emergency
Response Team (CERT) Certified Computer
Security Incident Response Handler Certified
Information Security Systems Professional (CISSP)
Certified Information Security Manager (CISM)
Certified in Risk and Information Systems Controls
(CRISC) Certified Cloud Security Professional
(CCSP) Certificate of Cloud Security Knowledge
(CCSK) Or equivalent certification from other
certifying organizations Or equivalent documented
experience over at least 4 years of active work
Mandatory
System Security
Plan
X
PremierOne complies with the
functionality as described in the
requirement.
1943
Out of the Box
Page 135 of 135
Exhibit H: Exhibit Reserved
Use or disclosure of this proposal is subject to the restrictions on the cover page.
Page 12-1
Section 12
Exhibit H: Exhibit Reserved
“Reserved”
Use or disclosure of this proposal is subject to the restrictions on the cover page.
Motorola Solutions
Page 2
Section 13
Exhibit I – Service Level
Agreement
Maintenance and Support Agreement
Motorola Solutions Inc., (Motorola), a Delaware corporation, having a place of business located at 7237
Church Ranch Blvd, Suite 406 Westminster, CO 80021 and Maricopa County, AZ (County), having a
place of business located at 301 W. Jefferson St., Phoenix, AZ 85003, enter into this Maintenance and
Support Agreement (Agreement), pursuant to which County will purchase and Motorola will sell the
maintenance and support services as described below and in the attached exhibits. Motorola and
County may be referred to individually as “party” and collectively as “parties.”
For good and valuable consideration, the parties agree as follows:
Section 1
Attachments
The Attachments listed below are incorporated into and made a part of this Agreement. In interpreting
this Agreement and resolving any ambiguities, the main body of this Agreement will take precedence
over the Attachments and any inconsistency between the Attachments will be resolved in the order in
which they are listed below.
3.
Attachment A “Covered Products, Support Options and Pricing”
4.
Attachment B “Customer Support Plan”
5.
Attachment C “Advanced Services Statement of Work”
6.
Attachment D “Labor Rates”
7.
Attachment E “Hardware Refresh”
8.
Attachment F “Summit Tickets”
Section 2
Definitions
“Equipment” means the physical hardware purchased by County from Motorola pursuant to a separate
System Agreement, Products Agreement, or other form of Agreement.
“MCSO” means Maricopa County Sheriff’s Office.
“Motorola” means Motorola Solutions, Inc., a Delaware corporation.
“Motorola Software” means Software that Motorola owns. The term includes Product Releases,
Standard Releases, Cumulative Updates, and On Demand Releases.
“Non-Motorola Software” means Software that a Third Party other than Motorola owns.
“Optional Technical Support Services” means fee-based technical support services that are not covered
as part of the standard Technical Support Services.
“Principal Period of Maintenance” or ”PPM” means the specified days and times during the days, that
maintenance and support services will be provided under this Agreement. The PPM is indicated in the
Covered Products, Support Options and Pricing Attachment.
“Patch” means a specific change to the Software that does not require a Release.
Use or disclosure of this proposal is subject to the restrictions on the cover page.
Motorola Solutions
Page 3
“Products” means the Equipment (as indicated in the Covered Products Attachment) and Software
provided by Motorola.
“Releases” means an Update or Upgrade to the Motorola Software and are characterized as “On
Demand Releases,” “Cumulative Updates,” “Standard Releases,” or “Product Releases.” The content
and timing of Releases will be at Motorola’s sole discretion.
A “Cumulative Update” is defined as a release of Motorola Software that contains error corrections to
an existing Standard Release that do not affect the overall structure of the Motorola Software.
Cumulative Updates will be superseded by the next issued Cumulative Update.
A “Standard Release” is defined as a release of Motorola Software that may contain product
enhancements and improvements, such as new databases, modifications to databases, or new
servers, as well as error corrections. A Standard Release may involve file and database conversions,
System configuration changes, hardware changes, additional training, on-site installation, and System
downtime. Standard Releases will contain all the content of prior On Demand Releases and Cumulative
Updates that is reasonably available (content may not be reasonably available because of the proximity
to the end of the release cycle and such content will be included in the next release).
A “Product Release” is defined as a release of Motorola Software considered to be the next generation
of an existing product or a new product offering. If a question arises as to whether a Product offering is
a Standard Release or a Product Release, Motorola’s opinion will prevail, provided that Motorola treats
the Product offering as a new Product or feature for its end user customers generally.
On Demand Releases are identified by the fourth character of the release number, shown here as
underlined: “1.2.0.4.a,” Cumulative Updates by the third digit: “1.2.0.4.a,” Standard Releases by the
second digit: “1.2.0.4.a,” and Product Releases by the first digit: “1.2.0.4.a.”
“Residual Error” means a software malfunction or a programming, coding, or syntax error that causes
the Software to fail to conform to the Specifications.
“Services” means those maintenance and support services described in the Customer Support Plan
Attachment and provided under this Agreement.
“Software” means the Motorola Software and Non-Motorola Software (Third Party) that is furnished with
the System or Equipment.
“Specifications” means the design, form, functionality, or performance requirements described in
published descriptions of the Software, and if also applicable, in any modifications to the published
specifications as expressly agreed to in writing by the parties.
“Standard Business Day” means Monday through Friday, 8:00 a.m. to 5:00 p.m. local time, excluding
established Motorola holidays. Motorola Holidays include (but are subject to annual updates): New
Year’s Day, Martin Luther King, Jr. Day, Memorial Day, Juneteenth, July 4, Labor Day, Thanksgiving
Day, Day after Thanksgiving, Christmas Eve, Christmas Day.
“Standard Business Hour” means a sixty (60) minute period of time starting at notification within a
Standard Business Day(s).
“Start Date” means the date upon which this Agreement begins. The Start Date is specified in the
Covered Products, Support Options and Pricing Attachment.
“System” means the Products and Services provided by Motorola as a system and are more fully
described in the Technical and Implementation Documents attached as Exhibits to the applicable
system agreement between County and Motorola.
Use or disclosure of this proposal is subject to the restrictions on the cover page.
Motorola Solutions
Page 4
“Technical Support Services” means the remote support provided by Motorola on a standard and
centralized basis concerning the Covered Products, including diagnostic services and troubleshooting
to assist MCSO in ascertaining the nature of a problem being experienced by MCSO. Technical
Support Services includes minor assistance concerning the use of the Software (including advising or
assisting MCSO in attempting data/database recovery, database set up, client-server advice), and
minor assistance or advice on installation of Releases provided under this Agreement.
“Update” and “Upgrade” means an On Demand Release, Cumulative Update, or Standard Release.
Section 3
Scope of Service
In accordance with the provisions of this Agreement and in consideration of the payment by County of
the price for the Services, Motorola will provide to County the Services as described in the Statement of
Work Exhibit for the Support Services package listed above and as indicated in the Covered Products,
Support Options and Pricing Attachment. Services will apply only to the Products described in the
Covered Products Attachment.
When Motorola performs Services at the location of installed Products, County agrees to provide to
Motorola, at no charge, a non-hazardous environment for work with shelter, heat, light, and power, and
with full and free access to the covered Products. MCSO will provide all information pertaining to the
hardware and software with which the Products are interfacing to enable Motorola to perform its
obligations under this Agreement.
All MCSO requests for covered Services will be made initially with the call intake center identified in the
Covered Products, Support Options and Pricing Attachment.
Motorola will provide to MCSO Technical Support Services and Releases as follows:
Motorola will provide Technical Support Services and correction of Residual Errors during the PPM in
accordance with the Attachments. The level of Technical Support depends upon County’s selection as
indicated in this agreement and the Covered Products, Support Options and Pricing Attachment. Any
Technical Support Services that are performed by Motorola outside the contracted PPM and any
Residual Error corrections that are outside the scope will be billed at the then current hourly rates. The
objective of Technical Support Services will be to investigate specifics about the functioning of covered
Products and to determine whether there is a defect in the Product. Technical Support Services will not
be used in lieu of training on the covered Products.
Unless the Covered Products, Support Options and Pricing Attachment expressly provides to the
contrary, Motorola will provide to MCSO without additional license fees an available Cumulative
Update, or Standard Release for Motorola’s PremierOne Applications after receipt of a request from
MCSO. County must pay for any installation or other services and any necessary Equipment or third
party software or training provided by Motorola in connection with Standard Releases. On Demands
and Cumulative Updates are designed to be delivered remotely. Services for onsite delivery related to
On Demands and Cumulative Updates as requested by MCSO will be quoted at the time of the request.
Any services will be performed in accordance with a mutually agreed schedule.
Motorola will provide to County an available Product Release after receipt of a request from MCSO, but
County must pay for all additional license fees, any installation or other services, and any necessary
Equipment provided by Motorola in connection with such Product Release. Motorola’s duty as
described in this paragraph is contingent upon MCSO’s then-current installation at the time of MCSO’s
request being within two (2) Standard Release versions of the new Standard Release available for
general release. Any services will be performed in accordance with a mutually agreed schedule.
Notwithstanding the foregoing, County is entitled to such a Product Release that supports the complete
Cloud migration to which County is entitled as described in Attachment C (entitlement to adopt Cloud
Use or disclosure of this proposal is subject to the restrictions on the cover page.
Motorola Solutions
Page 5
functionality which replaces contracted on-premises functionality as it becomes available and meets the
needs of MCSO), at no cost to County.
Along with maintenance Software Releases, Motorola will make available new purchasable products,
features and modules which are separate and distinct from the mainstream PremierOne line of
Products. Newly released Products may have PremierOne as a pre-requisite and/or share some portion
of the PremierOne code base. Customers are not entitled to these products, features and modules, or
upgrades to them within this Maintenance and Support Agreement, if they have not purchased the
required licenses.
As part of the Software development process Motorola makes every reasonable effort to lessen impact
to MCSO operations. Any change to existing functionality is done after thorough review of customer
feedback and with announcement of said change. When it’s not technically feasible to meet a particular
requirement Motorola will proactively communicate the changes. Beyond these efforts Motorola does
not warrant that a Release will meet MCSO’s particular requirement, be uninterrupted or error-free, be
backward compatible, or that all errors will be corrected. Errors addressed as part of the Software
Release will be corrected. Full compatibility of a Release with the capabilities and functions of earlier
versions of the Software may not be technically feasible. If it is technically feasible, Motorola will make
available services to integrate these capabilities and functions to the updated or upgraded version of
the Software, which services may be fee based.
Motorola’s responsibilities under this Agreement to provide Technical Support Services in accordance
with the package selected by County and as further detailed in the Services Statement of Work and
Customer Support Plan will be limited to the current Standard Release plus the two (2) prior Standard
Releases (collectively referred to in this section as “Covered Standard Releases”). Notwithstanding the
preceding sentence, Motorola will provide Technical Support Services for a Severity Level 1 or 2 error
concerning a Standard Release that precedes the Covered Standard Releases unless such error has
been corrected by a Covered Standard Release (in which case County will need to have the Standard
Release that fixes the reported error installed or terminate this Agreement as to the applicable
Software).
The maintenance and support Services described in this Agreement are the only covered services.
Unless optional or a la carte Technical Support Services are purchased, these Services specifically
exclude and Motorola will not be responsible for:
Any service work required due to incorrect or faulty operational conditions, including but not limited to
Equipment not connected directly to an electric surge protector, or not properly maintained in
accordance with the manufacturer’s guidelines. Other services may be available for an additional fee
and will be addressed with an amendment to the Agreement.
The repair or replacement of Products or parts resulting from failure of MCSO’s facilities, MCSO’s
personal property and/or devices connected to the System (or interconnected to devices) whether or
not installed by Motorola’s representatives.
The repair or replacement of Equipment that has become defective or damaged due to physical or
chemical misuse or abuse, MCSO’s negligence, or from causes such as lightning, power surges, or
liquids.
Any transmission medium, such as telephone lines, computer networks, or the worldwide web, or for
Equipment malfunction caused by such transmission medium.
Accessories, custom or Special Products; modified units; or modified Software.
The repair or replacement of parts resulting from the tampering by persons unauthorized by Motorola or
the failure of the System due to extraordinary uses.
Use or disclosure of this proposal is subject to the restrictions on the cover page.
Motorola Solutions
Page 6
Operation and/or functionality of MCSO’s personal property, equipment, and/or peripherals and any
application software not provided by Motorola.
Services for any replacement of Products or parts directly related to the removal, relocation, or
reinstallation of the System or any System component.
Services to diagnose technical issues caused by the installation of unauthorized components or misuse
of the System.
Services to diagnose malfunctions or inoperability of the Software caused by changes, additions,
enhancements, or modifications in MCSO’s platform or in the Software.
Services to correct errors found to be caused by MCSO-supplied data, machines, or operator failure.
Operational supplies, including but not limited to, printer paper, printer ribbons, toner, photographic
paper, magnetic tapes and any supplies in addition to that delivered with the System; battery
replacement for uninterruptible power supply (UPS); office furniture including chairs or workstations.
Third-party software unless specifically listed on the Covered Products Attachment.
Support of any interface(s) beyond Motorola-provided port or cable, or any services that are necessary
because third party hardware, software or supplies fail to conform to the specifications concerning the
Products.
Services related to MCSO’s failure to back up its data or failure to use a UPS system to protect against
power interruptions.
Any design consultation such as, but not limited to, configuration analysis, consultation with MCSO’s
third-party provider(s), and System analysis for modifications or Upgrades or Updates which are not
directly related to a Residual Error report.
County hereby agrees to:
Maintain any and all electrical and physical environments in accordance with the System
manufacturer’s specifications.
Provide standard industry precautions (e.g. back-up files) ensuring database security, per Motorola’s
recommended backup procedures.
Ensure System accessibility, which includes physical access to buildings as well as remote electronic
access. Remote access can be stipulated and scheduled with MCSO; however, remote access is
required and will not be substituted with on-site visits or proxies if access is not allowed or available.
Appoint one or more qualified employees to perform System Administration duties, including acting as a
primary point of contact to Motorola’s Technical Support organization for reporting and verifying
problems and performing System backup. At least one member of the System Administrators group
must have completed Motorola’s End-User training and System Administrator training (if available). The
combined skills of this System Administrators group includes proficiency with: the Products, the system
platform upon which the Products operate, the operating system, database administration, network
capabilities such as backing up, updating, adding, and deleting System and user information, and the
client, server and stand-alone personal computer hardware. The System Administrator will follow the
Residual Error reporting process described herein and make all reasonable efforts to duplicate and
verify problems and assign a Severity Level according to definitions provided herein. County agrees to
use reasonable efforts to ensure that all problems are reported and verified by the System
Administrator before reporting them to Motorola. MCSO will assist Motorola to confirm that errors are
not the product of the operation of an external system, data links between system, or network
Use or disclosure of this proposal is subject to the restrictions on the cover page.
Motorola Solutions
Page 7
administration issues. If a Severity Level 1 or 2 Residual Error occurs, any MCSO representative may
contact Motorola’s Customer Support by telephone, but the System Administrator must follow up with
Motorola’s Customer Support as soon as practical thereafter. A full list of MCSO system management
responsibilities is provided in Attachment B Customer Support Plan.
In performing repairs under this Agreement, Motorola may use parts that are not newly manufactured
but which are warranted to be equivalent to new in performance. Parts replaced by Motorola will
become Motorola’s property.
MCSO will permit and cooperate with Motorola so that Motorola may periodically conduct audits of
MCSO’s records and operations pertinent to the Services, Products, and usage of application and
database management software. If the results of any such audit indicate that price has been
understated, Motorola may correct the price and immediately invoice County for the difference (as well
as any unpaid but owing license fees).
If County replaces, upgrades, or modifies equipment, or replaces, upgrades, or modifies hardware or
software that interfaces with the covered Products, Motorola will have the right to adjust the price for
the Services to the appropriate current price for the new configuration.
County agrees not to attempt or apply any update(s), alteration(s), or change(s) to the database
software without the prior approval of Motorola.
Section 4
Right to Subcontract and Assign
Except as provided herein, neither party may assign this Agreement or any of its rights or obligations
hereunder without the prior written consent of the other party, which consent will not be unreasonably
withheld. Any attempted assignment, delegation, or transfer without the necessary consent will be void.
Notwithstanding the foregoing, Motorola may assign this Agreement to any of its affiliates or its right to
receive payment without the prior consent of County. In addition, in the event Motorola separates one
or more of its businesses (each a “Separated Business”), whether by way of a sale, establishment of a
joint venture, spin-off or otherwise (each a “Separation Event”), Motorola may, without the prior written
consent of the other Party and at no additional cost to Motorola, assign this Agreement such that it will
continue to benefit the Separated Business and its affiliates (and Motorola and its affiliates, to the
extent applicable) following the Separation Event. Motorola may subcontract any of the work; however,
subcontracting will not relieve Motorola of its duties under this Agreement.
Section 5
Terms
Maintenance of third-party products will increase annually based on a current vendor supplied
maintenance and support quote. In addition, if the Covered Products or Support Options change, the
pricing will correspondingly change.
If County requests, Motorola may provide services outside the scope of this Agreement or after the
termination or expiration of this Agreement and County agrees to pay for those services. These terms
and conditions in effect at the time such services are rendered will apply to those services.
Section 6
Intentionally Omitted
Section 7
Default/Termination
Upon the expiration or earlier termination of this Agreement, and unless otherwise required by
applicable law or by a court order from a court with competent jurisdiction, County and Motorola will
immediately deliver to the other Party, as the disclosing Party, all Confidential Information of the other,
including all copies thereof, which the other Party previously provided to it in furtherance of this
Agreement. Confidential Information includes: (a) proprietary materials and information regarding
technical plans; (b) any and all other information, of whatever type and in whatever medium including
Use or disclosure of this proposal is subject to the restrictions on the cover page.
Motorola Solutions
Page 8
data, developments, trade secrets and improvements, that is disclosed by Motorola to County in
connection with this Agreement; (c) all geographic information system, address, telephone, or like
records and data provided by County to Motorola in connection with this Agreement that is required by
law to be held confidential.
Section 8
Certification Disclaimer
Motorola specifically disclaims all certifications regarding the manner in which Motorola conducts its
business or performs its obligations under this Agreement, unless such certifications have been
expressly accepted and signed by an authorized signatory of Motorola.
Section 9
Compliance with Applicable Laws
The Parties will at all times comply with all applicable regulations, licenses and orders of their
respective countries relating to or in any way affecting this Agreement and the performance by the
Parties of this Agreement. Each Party, at its own expense, will obtain any approval or permit required in
the performance of its obligations. Neither Motorola nor any of its employees is an agent or
representative of County.
Page 9
Attachment A: Covered Products
Maintenance and Support Agreement
Note: To be completed during transition from implementation to warranty/maintenance. SA/USC
Term: {{Month Day, Year}}
Customer Agency
Billing Agency
{{Customer Agency Name}}
{{Billing Agency Name}}
Address
Address
City, State, Zip
City, State, Zip
Contact Name
Contact Name
Accounts Payable
Telephone Number
Telephone Number
Email Address
Email Address
For support and updates on products below, please contact Motorola’s Public Safety Application’s
Customer Support: (800) MSI-HELP (800-674-4357).
Site Identification Numbers
Product Group
Site Identification Number
PremierOne CAD
PremierOne Mobile
PremierOne Records
Motorola Advanced Support Services Include:
x
Access to Users Group Site
x
Case Management 24x7
x
On-site Support (when applicable)
x
Software Releases, as defined
x
Technical Support 9x5
x
Third-party Vendor Coordination
x
Virtual Private Network VPN Tool
x
Managed Detection Response (MDR)
x
Security Update Services (SUS)
x
Remote Application Administrators
x
Hardware Refresh
x
Summit Attendance
Motorola Supported Products
Products
Description
Service Level
Qty
PremierOne CAD Software
Page 10
PremierOne
CAD
Advanced
PremierOne Interfaces
PremierOne
Interfaces
Advanced
PremierOne Records Software
PremierOne
Records
Advanced
PremierOne Mobile Software
PremierOne
Mobile
Advanced
Third-Party Vendor Supported Products
Vendor
Description
Vendor
Service Level
HPE
HPE Servers
AristaStorage
F5
F5 Load Balancers
Esri
Esri Embedded Software
Alletra
Alletra Network Switches
Fortinet
Fortigate Devices
CommSys
CommSys Software
VMWare
VMWare Licenses
Page 11
Third-Party Vendor Equipment List
Vendor
Description
Serial Numbers
HPE
(Qty) DL360 Gen10 Servers
(Qty) Nimble Storage
CDW
(Qty) F5 Load Balancers
Extreme Network
(Qty) Extreme Network Switches
Fortinet
(Qty) Fortigate Devices
CommSys
CommSys Software
VMWare
(Qty) vCenter, (Qty) vSphere with 2 CPUs, (Qty)
vSphere with 1 CPU
N/A
{{Vendor}}
{{Description}}
{{Serial Numbers}}
Summit Attendance
Summit Advanced Purchase
Summit Attendance
Year
Attendees
Qty
Standard Attendance1
10
Registration Only
Standard Attendance Fees Include the following:
ƒ Registration fee
ƒ Round trip travel for event (booked by Motorola)
ƒ Hotel accommodations (booked by MCSO per Motorola website instructions)
ƒ Ground Transportation (booked by Motorola)
ƒ Daily meal allowance2
1 Standard Attendance includes above accommodations for the regular conference days. Any offer for
pre-training outside of the standard conference days is not included in this offer. Customers who wish
to attend pre-conference training may do so at their own lodging and food expense. Adjustment to
travel dates and times to attend pre-conference training is allowed.
2 Daily meal allowance is determined by Motorola based on published guidelines. In no event will the
amount provided exceed attendee’s applicable Agency rules regarding meal expenses, provided the
attendee or his/her agency notifies Motorola in advance of the conference of any restrictions,
prohibitions or limitations that apply.
Additional Support Services
Service
Description
SOW Reference
Qty
SW Upgrade Services
Professional Standard Release Software Upgrade
Services (Up to 4 over 10 year term)
Attachment C
Up to 4
Page 12
Attachment B: PremierOne Customer Support Plan
Quick Contact Matrix
Support Center
Toll Free Phone#
1-800-MSI-HELP (1-800-674-4357)
Email
PSACASE@Motorolasolutions.com
Motorola Portal
Customer Support Portal
Provide the following information:
Site Name
Your Name
Your Call Back Number
A Brief Description of the Problem
Priority (Critical, High, Medium, Low)
Warranty and/or Service Agreement Information
Customer Name:
Contract #:
Service Agreement Start/End Date:
Service Level: Advanced
Account Manager
Customer Success Advocate
Name:
Name:
Mobile:
Mobile:
Email:
Email:
Escalation Plan
Our goal is to ensure our customers receive the best possible support from Motorola. If you feel that
your support or maintenance needs are not being met, as a direct Motorola Customer, we provide an
escalation process for your request to the next Motorola department or manager.
Your initial call should always be to the first department or person on the list below. If, after making this
initial contact you still have unresolved issues, please see below for escalation contact information.
Escalation Plan
Level 1
Level 2
Level 2
Support
Center
Support Center
Brian Radinsky
Front Office Technical Support
Manager
Mobile: (240) 457-7892
Brian.Radinsky@MotorolaSoluti
ons.com
Tim Heddleston
Senior Manager, Technical
Support
Mobile: (206) 427.8230
tim.heddlesten@motorolasolutio
ns.com
Jeremy Smith
Head of Software Enterprise
Centralized Managed and
Support Operations
Mobile: (951) 216.8827
Jeremy.Smith@motorolasolutio
ns.com
On-Site
and
Remote
Support
Technicia
ns
On-Site Support Technicians
Tyler McCullough
Manger, Technical Support
Mobile: (571) 329.1790
Tyler.McCullough@motorolasoluti
ons.com
Tim Heddleston
Senior Manager, Technical Support
Mobile: (206) 427.8230
tim.heddlesten@motorolasolutio
ns.com
Jeremy Smith
Head of Software Enterprise
Centralized Managed and Support
Operations
Mobile: (951) 216.8827
Jeremy.Smith@motorolasolutions.
com
Page 13
Customer Support Plan Overview
Serving Our Customer’s Needs
Motorola is committed to helping people be their best in the moments that matter. We appreciate the
opportunity to provide the following support services (Support Services) pursuant to this Customer
Support Plan (CSP), which has been tailored specifically for your PremierOne. Our Service Delivery
Team is focused on the health, system performance and reliability of the PremierOne (PremierOne).
You will work with an account manager or service contract manager who will maintain regular
communications with you and will continually monitor and assess our service deliveries over the full
lifecycle of the engagement. They will be your single point of contact for any questions on Motorola
products or support.
Your Support Plan may be amended from time to time to align with industry best practices and
customer needs. Our goal is to build a service relationship you can trust.
PremierOne Support Services
Motorola Advanced Support Services provides basic support delivered through a combination of
centralized resources within Motorola’s Centralized Managed Support Operations (CMSO) Technical
Services Organization (TSO) team collaborating with product development resources that are
experienced in managing mission critical systems and associated technologies. The TSO team
operates 24/7/365, leveraging remote access to customer systems for complete resolution methods.
Open communication is the key to effective support service delivery and relationship building.
The Support Plan covers MCSO locations in the table below.
Site ID
Product Group
Site Name
PremierOne CAD
PremierOne Mobile
PremierOne Records
Motorola CMSO and Service Desk
The CMSO TSO is the central point of contact to report PremierOne incidents and submit change
requests. The TSO team can be reached 24/7 to assist with your service needs via:
x
Toll Free Telephone: 1-800-MSI-HELP (800-647-4357) and convey the request
x
Customer Support Portal: low priority requests only, (estimated 24 hour turnaround)
x
Email: PSACASE@motorolasolutions.com (estimated 24 hour turnaround)
NOTE: Critical and high priority incidents should not be reported via email or the Customer Portal.
Product and system technical resources are ready to receive and take action on requests for service.
Priority Level Response Table
The CMSO TSO will respond to reporting incidents according to the priority levels and response times
defined in the following table.
Table 1-1: PremierOne Priority Level Definitions and Response Times
Priority
Level
Incident Definition
Response Time
Page 14
Priority
Level
Incident Definition
Response Time
Critical P1
An incident is deemed CRITICAL if one or multiple critical functions
are unavailable, or severely degraded such that MCSO’s core
business functions and capabilities are no longer delivered or
capable. The resulting critical impact to MCSOs’ business is such
that focus and resources must be applied to restoration or mitigation
Full system outage, systemic inability to process mission-critical
commands (e.g. incident creation), extreme systemic slowness, or
majority of clients unable to connect to the system, etc.
Telephone conference
within 1 Hour of initial
voice notification
High P2
An incident is determined HIGH if a business function is unavailable
and normal MCSO business activity is impacted or degraded, and a
workaround may be available to mitigate the effects of the service
impact; however, overall efficiency or effectiveness is degraded.
This may apply to both critical and non-critical functions.
Loss of a critical redundancy, subsystem, or critical interface (e.g.
CommSys Query, Paramount ProQA, Fire Station Alerting, etc.)
systemic ARL failure, systemic recurring disruptive issues that
frequently impact users.
Telephone conference
within 3 hours of initial
voice notification during
normal business hours.
Medium P3
An incident is deemed MEDIUM if business functions are available,
however, there is a deviation from the expected or agreed upon
level of service or other service condition not aligned with the other
defined impact levels.
Issues impacting a single client, intermittent issues, non-critical
subsystems or interfaces (e.g. interfaces installed on RDW), RDW
or reporting problems, etc.
*System must be within N-2 standards for these tickets
Telephone conference
within 8 Hours of initial
notification during normal
business hours
Low P4
A request is deemed LOW for minor requests.
This level is meant to represent minor issues, such as cosmetic
issues, documentation errors, general usage questions,
configuration questions, and product or service update requests.
*System must be within N-2 standards for these tickets.
Telephone conference
within 2 business days of
initial notification.
Case Management via Customer Support Portal
The Customer Support Portal provides customers with an interface into our Incident Management
system. The Customer Support Portal gives valuable system and service information whenever you
need it along with complete case management details from submission to close.
x
Customer Support Portal provides the ability to:
x
Create low priority tickets
x
Obtain status updates on existing tickets
x
Supply additional information on tickets 24/7
x
When updating ticket notes, please provide contact information, which includes phone number,
email, etc.
Motorola does not recommend using this tool for opening Priority 1 or 2 tickets. The same guidelines
apply to updating tickets with critical information. For any critical issues or updates, customers should
contact the TSO by calling 1-800-MSI-HELP (800-647-4357)
Page 15
Ticket Initiation via Email
An alternative customer support tool is available for PremierOne customers. Along with the toll-free
phone number and Customer Support Portal, customers can request technical support by email. For
many customers who use their handheld devices as a means to open tickets, email provides additional
flexibility for initiating tickets.
For proper ticket management and contractual response, email ticketing is only available for priority
levels 3 or 4. To process a ticket via email, the email must be formatted exactly as described below:
1.
Address email to: PSACASE@motorolasolutions.com
2.
Email Subject: Type “PSA Service Request” and a brief description of the system issue (this will
become the ticket title)
3.
Use the following template for the body of the email. Copy and paste from below, adding the
accurate and specific needs of the request following the bold items listed:
A.
Site ID: Site ID
B.
Product Type: followed by the product family type. Choose from the following
list:
i.
PremierOne CAD
ii.
PremierOne Mobile (including Handheld or PMDC)
iii. PremierOne Records
C.
Contact First Name: first name or the person support personnel are to contact
D.
Contact Last Name: last name or the person support personnel are to contact
E.
Phone Number: phone number, including area code, where the contact person may
be reached
F.
Priority Level: indicate either priority level 3 or 4. All priority level 1 or 2 tickets must
be opened via the toll-free TSO number.
G.
Problem Description: a comprehensive description of the problem
4.
Once the email is sent, MCSO will receive an email with a ticket number for future reference. If
an email response is not received, or if a priority level 1 or 2 ticket needs to be opened, please
contact the toll-free TSC number.
CJIS Compliance
Motorola will maintain industry standard security measures to protect the Solution from intrusion,
breach, corruption or security risks. MCSO is responsible for maintaining security controls for their
managed networks and infrastructure, including but not limited to servers, boundary protection devices
and information flow enforcement. During the term of the Agreement, if the Solution enables direct or
indirect access to FBI defined Criminal Justice Information (CJI), Motorola will comply with the FBI
Criminal Justice Information (CJI) Security Policy. Any additional security measures desired by MCSO
may be available for an additional fee.
Motorola will provide the necessary information for its personnel that access MCSO CJI to submit to a
background check based on submission of FBI fingerprint cards, complete CJIS Security Awareness
Training and execute the CJIS Security Addendum. It is MCSO's responsibility to determine when the
background credentialing process is required by Motorola personnel.
MCSO is independently responsible for due diligence and establishing and maintaining its own policies
and procedures and for ensuring compliance with CJIS and other security requirements that are outside
the scope of the Service provided. MCSO must also establish and ensure compliance with access
control and identification and authentication policies and procedures, including password security
Page 16
measures, lost and stolen credentials, account disabling, account validation, log retention capacity
planning and MCSO jurisdiction specific data retention requirements. Further, MCSO must maintain
industry standard security and protective data privacy measures. Motorola disclaims any responsibility
or liability whatsoever for the security or preservation of MCSO Data or Solution Data once accessed,
viewed or removed from the information system by MCSO or its representatives. Motorola further
disclaims any responsibility or liability whatsoever for MCSO's failure to maintain industry standard
security and data privacy measures and controls, or their role in CJIS Security Policy compliance.
Motorola reserves the right to terminate the Service if MCSO’s failure to maintain or comply with
industry standard security and control measures negatively impacts the Service, Solution or Motorola
own security measures.
Both parties will maintain and follow a breach response plan consistent with the standards of their
respective industries to include CJIS Security Policy reporting.
Summary
Our Support Plan includes the following key services elements:
x
Single point of contact - Customer Success Advocate who maintains close communication with
you and serves as a point of escalation when service or support levels are not meeting
expectations.
x
Systems Support Center: One place to report incidents and place requests - Reported incidents
are correlated with alerts received from the NOC for reduced root cause determination.
x
Emergency Call Management Portal: Enhanced access to case status and resolution details.
x
Network Security Operations Center: Continuous monitoring and response of the Motorola
PremierOne as well as providing notification of critical and high security alerts.
x
Technical Support Center: Staffed with subject matter experts to handle escalated tickets.
Benefits to Your Agency
x
Maximize Performance. Increase system uptime and quality of service through fast detection
of service disruptions and restoration of services
x
Save Time. Take back valuable minutes and better allocate resources with proactive monitoring
that helps reduce truck rolls and IT support requests
x
Rely on a Trusted Support Team. Depend on our skilled team to be the first line of defense
and have greater peace of mind
x
Reduce Risk. Gain visibility, enhance performance and increase cyber security with our full
suite of NSOC offerings.
Attachment C: PremierOne Advanced Services Statement of Work
Overview
Motorola’s PremierOne Advanced Services provides an integrated and comprehensive sustainment
program for PremierOne systems. Advanced Services do not include mobile devices, portable devices,
or network backhaul equipment maintenance.
Advanced Services consist of the following service elements:
x
Remote Technical Support
x
Hardware Repair Coordination
x
Software Maintenance
Page 17
x
Software Upgrade Services
x
Standard Release Software Upgrades
x
Remote Application Administrators
Each of these elements is summarized below and expanded upon in Advanced Services Detailed
Description below. In the event of a conflict between the descriptions below and an individual
subsection of Advanced Services Detailed Description, the individual subsection prevails.
This Statement of Work (SOW), including all of its subsections and attachments is an integral part of the
applicable agreement (Agreement) between Motorola Solutions, Inc. (Motorola) and the Agency (Agency).
In order to receive the services as defined within this SOW, MCSO is required to keep the system within a
standard support period as described in Master Support Agreement.
Remote Technical Support
Motorola CMSO Technical Support Center (TSC) provides remote consultation with technical and
product development resources skilled with diagnosing and resolving PremierOne platform
performance and operation issues.
Hardware Repair
Motorola will coordinate repair of select third-party infrastructure equipment supplied by Motorola.
Motorola CMSO coordinates the equipment repair logistics process with the vendor if it is sourced from
Motorola as a part of the contract.
Software Maintenance
As new software becomes available for your PremierOne system, Motorola will provide access to the
latest software updates so that software performance and equipment operates to its specifications and
functionality. Software releases can be scheduled by MCSO and are delivered through the customer
support portal. The delivery of the software releases under the Software Maintenance does include
resources to perform the Software Upgrade.
System Monitoring
The service includes real-time, continuous monitoring and event management of the PremierOne
system, using sophisticated tools for remote monitoring and event characterization. Motorola will
assess events, determine the appropriate response, and initiate that response. Possible responses
include remotely addressing the issue, escalation to product technical support groups, and dispatch of
designated field technical resources.
Security Update Services
Motorola’s PremierOne Security Update Service (SUS) provides pretested security updates, minimizing
cyber risk and software conflicts. These security updates contain operating system security patches,
Microsoft SQL security updates, firmware, and other key system component security updates validated
for compatibility with PremierOne systems.
Remote Application Administration
The service includes remote resource(s) from Motorola’s global support and managed services
organization to support PremierOne applications (excluding infrastructure). The fully trained resource(s)
augment MCSO’s existing team as it relates to troubleshooting and initiating support tickets on software
issues, supporting user training, maintaining provisioning, introducing software upgrades, SSRS
reporting, Records modules and workflows.
Page 18
Motorola Service Delivery Ecosystem
Support Services are delivered through a tailored combination of centralized teams equipped with a
sophisticated service delivery platform, a customer support portal, and applicable third party vendors.
These service entities will collaborate to swiftly analyze issues, accurately diagnose root causes, and
promptly resolve issues to restore MCSO’s PremierOne systems to normal operations.
Centralized Managed Support Operations
The cornerstone of Motorola’s support process is the Centralized Managed Support Operations
(CMSO) organization, which includes the Service Desk and technical support teams. The CMSO is
staffed 24/7/365 by experienced personnel, including service desk specialists, security analysts, and
operations managers.
The Service Desk provides a single point of contact for all service-related items, including
communications between MCSO, Motorola, and third-party subcontractors. The Service Desk
processes service requests, service incidents, change requests, and dispatching, and communicates
with stakeholders in accordance with predefined response times.
All incoming transactions through the Service Desk are recorded, tracked, and updated through the
Motorola Customer Relationship Management (CRM) system. The Service Desk also documents
MCSO inquiries, requests, concerns, and related tickets.
Account Manager
A Motorola Account Manager (AM) will be MCSO’s key point of contact for defining and managing
services. The AM’s initial responsibility is to provide maintenance and support contract and the
Customer Support Plan (CSP) in collaboration with MCSO.
The CSP functions as an operating document that personalizes the services described in this
document. The CSP contains MCSO-specific information, such as site names, site access directions,
key contact persons, incident handling instructions, and escalation paths for special issues. The
division of responsibilities between MCSO and Motorola are detailed in this SOW.
Customer Success Advocate
The Customer Success Advocate is MCSO’s ongoing trusted advisor for Motorola products and
services. They will establish a quarterly communications cadence during which they will review support
issues, performance metrics (based on the Performance Reporting described below), keep MCSO
apprised of PremierOne product enhancements, new product and service offerings, and identify the
release of new cloud-based functionality to which MCSO is entitled under Cloud Entitlement.
Customer Support and Maintenance Expectations
In order to successfully deliver the services outlined in this SOW, MCSO is expected to assist Motorola
with performing tasks related to administration, maintenance, and support. MCSO will provide a
properly trained technical resource who is familiar with the operation of the PremierOne solution.
Motorola remote application administrators will support MCSO’s trained technical resource with the
mutually agreed upon responsibilities outlined below.
The customer technical resource will be suitably skilled and trained as the on-site expert when
requested by the TSC. They will validate issue resolution prior to close of the ticket in a timely manner.
In order to successfully deliver the services outlined in this Attachment C, MCSO is expected to assist
Motorola with performing tasks related to administration, maintenance, and support.
MCSO support personnel are responsible for the following:
Page 19
x
Initiate Service Request Tickets. Contact Motorola through authorized tools and processes
outlined in the Motorola CSP to initiate technical support tickets.
x
Assess Priority Level. Assist in assessing the urgency and impact of the issue so the correct
Priority Level is assigned, as found in the SOW and CSP.
x
Escalate Appropriately. Contact Motorola to add information, make changes to existing technical
support tickets or escalate service requests to Motorola management. Motorola CMSO TSC
contact information is provided in the CSP.
x
VPN connectivity. Provide VPN connectivity and telephone access to Motorola personnel, if
applicable.
x
Physical Workstation Maintenance. Perform periodic reboots and ongoing performance tuning,
hardware upgrades, and resource optimizations as required. Inspect physical equipment for
damage or wear, replace parts as per contractual agreement.
x
CAD client maintenance. Apply upgrades such as OS patches, administrative tools, and utilities.
-
Maintain and upgrade software that supports infrastructure applications (IE, Esri, etc.).
-
Perform periodic reboots and ongoing performance tuning, hardware upgrades, and
resource optimizations as required.
-
Upgrade and maintain antivirus software, appropriately configure and maintain exclusion list
(Refer to PremierOne Products latest published Anti-Virus Exclusions List.).
-
Apply any Microsoft Critical Security patch to their PremierOne that fits within the security
and sustainability processes of the agency. Motorola recommends agencies follow
Microsoft’s guidance related to the application of Critical Security patches.
If Security Patching Services are purchased from Motorola, MCSO will be responsible
for rebooting servers and workstations to apply the deployed patches.
x
Mobile Client Maintenance: Apply upgrades such as OS patches, administrative tools and
utilities.
-
Maintain and upgrade software that supports infrastructure applications (IE, Esri, etc.).
-
Perform periodic reboots and ongoing performance tuning, hardware upgrades, and
resource optimizations as required.
-
Upgrade and maintain antivirus software, appropriately configure and maintain exclusion list
(Refer to latest released PremierOne Products Anti-Virus Exclusions List.).
-
Configure and maintain all products relevant to mobile network connectivity (NetMotion,
Verizon, VPN related products, etc.).
-
Note: The Mobile Client Maintenance will be completed by the OSA if the OSA has been
purchased.
x
Custom Reports: Build/Modify/Support all custom reports in a manner that will not adversely
impact RDW Server/Database functionality. Custom reports are the sole responsibility of the
creator and not supported by Motorola. In an event that Motorola is creating reports for MCSO,
it will be supported by Motorola Support teams.
x
CAD Client Upgrade Testing: Test PremierOne Software Releases (includes Standard,
Cumulative Upgrades (CU) and On Demand Releases (OD)). Report and supply data for any
problems that are discovered with the software to Motorola for review and correction. Ensure
that minimum software/hardware requirements are met.
x
Third-Party Maintenance:
-
Net - Install, upgrade, configure, and maintain .net framework software as per minimum
requirements outlined by Motorola.
Page 20
-
Server - Install, upgrade, configure, and maintain all servers hosting third-party products that
interface to Motorola products. See Physical Server Maintenance section above for
additional explanation.
-
SQL - Install, upgrade, configure, and maintain MS SQL application. Make resource
optimization changes pertaining to best practices as required by Motorola.
-
SQL Express - Install, upgrade, configure, and maintain MS SQL Express application. Make
resource optimization changes pertaining to best practices as required by Motorola.
-
Unembedded Third-Party Licensing - Maintain and apply all third-party licensing for products
not specifically embedded within a Motorola proprietary product.
x
Mobile Client Install and Testing: Test PremierOne Software Releases (includes Standard, CU,
and ODs). Report and supply data for any problems that are discovered with the software to
Motorola for review and correction. Ensure that minimum software/hardware requirements are
met.
x
GIS Updates: PremierOne Map Maintenance
-
Ensure validity and integrity of all GIS related data introduced to the system.
-
Record modifications made to GIS files, and confirm expected behavior within the
PremierOne.
-
Perform all server mapping updates, geoset transitions, and distribute updated map files to
CAD/Mobile clients.
x
Anti-Virus and Windows UAC: Install, configure, and upgrade chosen anti-virus software.
Appropriately configure the user account control settings in a manner that ensures the files are
accessible for system stability and successful operation. If system instability occurs after
changing any system element pertaining to UAC or AV, report changes to Motorola via ticket
entry. If unexpected behavior is experienced while UAC or AV are enabled, and does not occur
after disabling UAC or AV, MCSO will be responsible for diagnosing and correcting the issue.
Per request, Motorola will make every reasonable effort to test and verify specific anti-virus
patches against a replication of MCSO’s application if a problem cannot be resolved internally.
x
System Backups: With the assistance of the OSA, perform and confirm successful completion of
daily backup operations. Ensure that all required system files and data are successfully backed
up to the appropriate media. Monitor health of all backup related hardware, including but not
limited to HP tape library, recovery tapes, and disk drives. Maintain and upgrade backup related
software, such as HP Data Protector. Prior to performing system or database upgrades, create
a backup of the system and/or database to maintain a restoration point. Ensure that
PremierOne SQL Server Management Studio (SSMS) full and incremental database backups
completing successfully, report related SCOM notifications to Motorola.
-
Note: Tape Backups and HD Backups are the sole responsibility of MCSO, even if a
dedicated OSA is purchased.
x
Provisioning knowledge of the system: MCSO must ensure that adequate provisioning training
and knowledge has been provided to those authorized to access and/or make changes within
PremierOne Provisioning. Provisioning changes should be tracked. This information should be
supplied to Motorola to aid in troubleshooting efforts should a problem be experienced. Motorola
now provides a tool to aid in provisioning change identification, but changes should be tracked
internally by MCSO as a failsafe.
x
Gathering Issue Logs (Server and Client): During non-business hours, supply all requested logs
for problems that need to be diagnosed and resolved. In some circumstances, log automation
will be implemented, however anything that is not automatically gathered, and deemed
necessary by Motorola, must be furnished. Absence of requested data may lead to ticket
closure. (The OSA will assist with this task during normal business hours).
Page 21
x
MCSO Data Archiving: MCSO is responsible for all PremierOne Data Archival as per their
internal requirements and needs. Adequate storage space should be maintained, and data must
not be stored in a manner that adversely impacts the PremierOne or component operations.
x
Network Bandwidth and Stability: Install, monitor, and maintain network systems that provide
stable operations and adhere to bandwidth requirements to ensure the effective operation of
Motorola products and related system components.
x
Remote Access: MCSO must provide remote access to requesting Motorola personnel for
troubleshooting purposes. This includes, but is not limited to, VPN account access, remote
hosting, PremierOne domain access, and access to all system elements that pertain to the
operation of the PremierOne and functionality.
x
Backup Power: Install and maintain backup power source to ensure the effective operation of
the PremierOne System and all its components in the event of a primary power source failure.
x
End User Training: Ensure that all end users of Motorola products are trained to perform their
duties and not cause harm or upset of system functionality. Motorola does offer additional
training if necessary for an additional cost.
x
Change Management: Notify Motorola of any changes made to the PremierOne, associated
interfaces, related hardware, software, network, or any other system element that may
adversely impact operation or system functionality.
x
Note - Motorola is not liable for any loss of functionality related to any changes or updates made
to the solution by MCSO or third parties. We strongly recommend that MCSO advise Motorola
of any proposed changes or third party integrations before undertaking same to ensure that
functionality will not be adversely affected.
Advanced Services (System Monitoring)
Due to the interdependence between deliverables within the detailed sections, any changes to or any
cancellation of any individual section may require a scope review and price revision. The Advanced
Services package requires available internet connectivity provided by MCSO. A minimum connection of
2 Mbps is necessary to enable remote monitoring and update services. If the design requires an
additional network bandwidth, it will be discussed during the design phase.
System Monitoring provides continuous real-time fault monitoring for PremierOne system elements.
Motorola uses a defined set of tools to remotely monitor MCSO’s PremierOne system and characterize
network events. When an actionable event takes place, it becomes an incident. CMSO technologists
acknowledge and assess these incidents, and initiate a defined response.
Description of Service
With System Monitoring, Motorola uses a Managed Services Suite of Tools (MSST) to detect events
24/7 as they occur, analyze them, and escalate them to the Technical Support Organization (TSO)
Incidents will be generated automatically based on preset rules of continuous failure or multiple
bounces in the Motorola Fault management system.
The CMSO technical support agent assigns a priority level to an incident, then initiates a response in
accordance with the priority definitions found in Table 1-1. Depending on the incident, Motorola’s
response may include continued monitoring for further incident development, remote remediation
technical support, dispatching a field service technician, or other actions Motorola determines
necessary.
To prevent duplicate incidents from being generated by the same root cause, Motorola employs an
auto-triage process that groups related incidents. The auto triage process therefore automatically
Page 22
assigns grouped incidents to a field service technician, enabling the resolution of these incidents
together if the root alarm has been addressed.
Scope
System Monitoring is available 24/7. Incidents generated by the monitoring service will be handled in
accordance with Tables 1-1: Priority Level Definitions and Response Times. System Monitoring is a
globally provided service unless limited by data export control or other applicable local and regional
regulations. Timeframes are based on MCSO’s local time zone.
Inclusions
System Monitoring is available for the devices listed below “Motorola Monitored Elements under
System Monitoring Service”.
Motorola Responsibilities
x
Provide a dedicated network connection necessary for monitoring MCSO’s communication
network
x
Verify connectivity and event monitoring prior to system acceptance or start date.
x
Monitor system continuously during hours designated in the CSP, and in accordance with
Tables 1-1 and 1-6: Priority Level Definitions and Response Times.
x
Remotely access MCSO’s system to perform remote diagnosis as permitted by MCSO pursuant
to MCSO Responsibilities.
x
Create an incident, as necessary. Gather information to perform the following:
-
Characterize the issue.
-
Determine a plan of action.
-
Assign and track the incident to resolution.
x
Provide MCSO with a link to access system configuration information, site information, system
notifications, and system notes.
x
Cooperate with MCSO to coordinate the transition of monitoring responsibilities between
Motorola and MCSO as specified in MCSO Responsibilities below.
x
Maintain communication as needed with MCSO in the field until incident resolution.
x
Provide available information on incident resolution to MCSO.
Limitations and Exclusions
The following activities are outside the scope of the System Monitoring service:
x
Motorola will not monitor any elements outside of MCSO’s PremierOne Environment such as
infrastructure provided by a third party, unless specifically stated. Monitored elements must be
within MCSO’s network and elements should be capable of sending alerts to the Motorola Fault
Management Platform. Additional support charges above contracted service agreement fees
may apply if Motorola determines that system faults were caused by MCSO making changes to
critical system parameters without written agreement from Motorola.
x
System installations, upgrades, and expansions.
x
MCSO training.
x
Hardware repair and/or replacement.
x
Network security services.
x
Information Assurance.
Page 23
MCSO Responsibilities
x
Allow Motorola continuous remote access to enable the monitoring service.
x
Provide continuous utility service to any Motorola equipment installed or used at MCSO’s
premises to support delivery of the service. MCSO will take reasonable due care to secure the
Motorola equipment from theft or damage while on MCSO’s premises.
x
Provide Motorola with information necessary to complete a CSP, including:
-
Incident notification preferences as applicable.
-
Repair verification preference as applicable.
-
Database and escalation procedure forms.
x
Submit timely changes in any information supplied to Motorola and included in the CSP to the
Account Manager or Customer Success Manager(s) as applicable.
-
Notify the CMSO TSC Team prior to MCSO performing any activity that impacts the system. Activity
that impacts the system may include but is not limited to: installing software or hardware upgrades,
performing upgrades to the network, renaming elements or devices within the network, and taking
down part of the system to perform maintenance.
x
Send system configuration change requests through Motorola Account Manager or Customer
Success Manager to CMSO Team.
x
Allow Motorola’s onsite field service technician, if assigned as a part of service contract and is
designated in the CSP to access equipment, including any connectivity or monitoring
equipment, if remote service is not possible.
x
Allow Motorola’s onsite field service technician, if assigned as a part of service contract to
remove Motorola-owned monitoring equipment upon cancellation of service.
x
Provide Motorola with all MCSO-managed passwords required to access MCSO’s system upon
request (if applicable), when opening a request for service support, or when needed to enable
response to a technical issue.
x
Cooperate with Motorola and perform reasonable or necessary acts to enable Motorola to
provide these services.
x
Acknowledge that incidents will be handled in accordance with Tables 1-1 and 1-6: Priority
Level Definitions and Response Times.
Motorola Monitored Elements under System Monitoring Service
Monitored Elements
App Server
Monitoring Server
Firewall
Switches
SAN
NAS
Loadbalancer
Database server
SCOM
Remote Technical Support
Motorola’s Remote Technical Support service provides telephone consultation for technical issues that
require a high level of PremierOne network knowledge and troubleshooting capabilities. Remote
Technical Support is delivered through the Motorola CMSO TSC by a staff of technical support
specialists skilled in diagnosis and swift resolution of infrastructure performance and operational issues.
Motorola applies industry standards in recording, monitoring, escalating, and reporting for technical
support calls from its contracted customers to provide the support needed to maintain mission-critical
systems.
Page 24
Description of Service
The CMSO’s primary goal is Customer Issue Resolution (CIR), providing incident restoration and
service request fulfillment for Motorola’s currently supported infrastructure. This team of highly skilled,
knowledgeable, and experienced specialists is an integral part of the support and technical issue
resolution process. The TSC supports MCSO remotely using a variety of tools, including fault
diagnostics tools, simulation networks, and fault database search engines.
Calls indicating incidents or service requests will be logged in Motorola’s CRM system, and Motorola
will track the progress of each incident from initial capture to resolution. This helps ensure that technical
issues are prioritized, updated, tracked, and escalated as necessary, until resolution. Motorola will
advise and inform MCSO of incident resolution progress and tasks that require further investigation and
assistance from MCSO’s technical resources.
The CMSO classifies and responds to each technical support request in accordance with Table 1-1:
PremierOne Priority Level Definitions and Response Times.
This service requires MCSO to provide a suitably trained technical resource that delivers maintenance
and support to MCSO’s system, and who is familiar with the operation of that system. Motorola
provides technical consultants to support the local resource in the timely closure of infrastructure,
performance, and operational issues.
Scope
Motorola primary objective is to restore your PremierOne to normal operations as quickly as possible
and minimize the adverse impact of service events on our customers and their mission. This serves our
primary goal of maintaining quality of service and availability. The PremierOne team of highly skilled,
knowledgeable and experienced specialists are available to MCSO as an integrated part of the
essential support and technical issue resolution process.
All MCSO requests for service and change requests are tracked centrally in Motorola IT Service
Management (ITSM) toolset, resulting in a ticket number. All TSC support activity that occurs after the
cutover of the system into production is tracked in this system to promote consistent visibility of all
activities.
All calls requiring incidents or service requests are assigned a priority in accordance with Table 1-1:
PremierOne Priority Level Definitions and Response Times. Via the ITSM, Motorola will track the
progress of each ticket from initial capture to resolution. Motorola will advise and inform MCSO of the
ticket progress and tasks that require further investigation and assistance from MCSO’s technical
resources.
Upon notification of the incident, the TSC will supply a ticket number for reference. For each reported or
alert generated incident, the TSC will apply a “Priority Level” classification, which has an assigned
target response time objective. This classification provides the means to manage the appropriate
response and engagement processes.
Incident Reporting and Response
The CMSO Technical Support team is available via telephone 24/7/365 to receive and log requests to
address issues with PremierOne systems. Remote Technical Support service is provided in accordance
with Table 1-1: PremierOne Priority Level Definitions and Response Times.
At a minimum, when reporting an incident using the toll-free number (800-MSI-HELP, the TSC will
require:
x
Customer name (Site)
Page 25
x
Caller’s name
x
Caller’s contact number (supply alternate call back number)
x
Description of the problem or request
x
Operational impact of the problem (Priority Level)
The CMSO will respond to incident reports according to the priority levels defined in Table 1-1:
PremierOne Priority Level Definitions and Response Times.
Reporting Trouble – The TSC number is provided to all customers for PremierOne issues. If the issue
cannot be resolved through our remote diagnostics by the TSC, then MCSO’s technician will be
required to report on-site to assist with the troubleshooting effort.
Response Time – shall be defined as the amount of time expired between the time in which the issue
is either (a) detected by monitoring or (b) reported to TSC by MCSO to the time that a qualified
technician is actively troubleshooting the issue.
For all incidents reported that are not determined to be a Critical P1 or High P2 incident, the response
time is related to the below office hours:
Note - Business Days is defined as Monday – Friday excluding holidays.
Business Hours is defined as Monday – Friday 9 a.m. – 6 p.m. Central Standard Time.
Incident Time – means the period of time during which the service or any service component suffers
an Incident. Incident Time shall commence when the issue is either (a) detected by monitoring or (b)
reported to the TSC by MCSO. Incident Time shall end upon completion of the repair or restoration of
the service or service component. Incident Time shall not include downtime attributable to (a) Force
Majeure conditions (as defined in the applicable agreement); or (b) scheduled preventive maintenance
that MCSO was notified of and consented to in advance.
Inclusions
Remote Technical Support service will be delivered for Motorola-provided equipment, including
integrated third-party products.
Motorola Responsibilities
x
Maintain availability of the Motorola CMSO TSC via telephone (800-MSI-HELP) 24/7/365 to
receive, log, and classify MCSO requests for support.
x
Open a ticket and categorize the reported issue or request.
x
Respond to and resolve incidents and technical service requests in accordance with Table 1-1:
PremierOne Priority Level Definitions and Response Times.
x
Perform analysis to assist in identifying a corrective action plan.
x
Provide the caller a corrective action plan outlining additional requirements, activities, or
information required to achieve restoral/fulfillment.
x
Maintain communication with MCSO as needed until resolution of the incident.
x
Coordinate technical resolutions with agreed upon third-party vendors, as needed.
x
Escalate support issues to additional Motorola technical resources, as applicable.
x
Determine, in its sole discretion, when an incident requires more than the Remote Technical
Support services described in this SOW and notify MCSO of an alternative course of action.
x
Provide regular status updates for incidents.
Page 26
Limitations and Exclusions
The following activities are outside the scope of the Remote Technical Support service:
x
Customer training.
x
Remote Technical Support for third-party equipment or APIs not sold by Motorola or listed in
Attachment A.
x
Any maintenance and/or remediation required as a result of a virus or unwanted cyber intrusion.
Customer Responsibilities
x
Prior to contract start date, provide Motorola with pre-defined information necessary to complete
CSP.
x
Submit timely changes in any information supplied in the CSP to the SCM.
x
Contact the CMSO Technical Support team to engage the Remote Technical Support service
when needed, providing the necessary information for proper entitlement services. This
information includes, but is not limited to, the name of contact, name of Customer, system ID
number, site(s) in question, and a brief description of the problem that contains pertinent
information for initial issue classification.
x
Maintain suitably trained technical resources familiar with the operation of MCSO’s system to
provide field maintenance and technical maintenance services for the system.
x
Supply suitably skilled and trained on-site personnel when requested.
x
Validate issue resolution in a timely manner prior to close of the incident.
x
Acknowledge that incidents will be addressed in accordance with Table 1-1: PremierOne Priority
Level Definitions and Response Times.
x
Cooperate with Motorola and perform all acts that are reasonable or necessary to enable
Motorola to provide Remote Technical Support.
x
In the event that Motorola agrees in writing to provide supplemental Remote Technical Support
to third-party elements provided by County, County agrees to obtain all third-party consents or
licenses required to enable Motorola to provide the service.
x
Pay additional support charges above the contracted service agreements that may apply if it is
determined that system faults were caused by MCSO making changes to critical system
parameters without written agreement from Motorola.
x
In the event that MCSO requires repair of equipment that is not contracted under this service at
the time of request, MCSO acknowledges that charges may apply to cover shipping, labor, and
parts. Motorola and County will collaborate to agree on a payment vehicle that most efficiently
facilitates the work, commensurate with the level of urgency that is needed to complete the
repair.
Performance Reporting
Motorola will provide a methodology by which monthly reports will be generated/provided to
demonstrate 99.999% availability of the PremierOne CAD system and 99.99% availability of the
PremierOne Records system. Motorola deploys Prometheus, a popular open-source time-series
database optimized and used worldwide for the purposes of telemetry of various applications, systems,
and infrastructure. Prometheus is used for monitoring various PremierOne components within the
system including:
x
Status of hardware such as power utilization, node availability, disk space, and environmental
conditions.
Page 27
x
Conditions platform components such as Active Directory health, SQL cluster health, and
overall operating system performance.
x
Crucial application telemetry such as transaction timings, critical errors, or even extended
tracing.
Grafana, a data visualization tool, is deployed alongside Prometheus. Motorola will provide starter
dashboards that provide charts, graphs, and other visual indicators of system health and performance.
Both pieces of software run on a virtual machine running Red Hat Enterprise Linux that is explicitly
hardened to appropriate cybersecurity standards.
One of the largest benefits to this solution is the ability to leverage Motorola's cloud platform. Data in
Prometheus is automatically forwarded to this platform at regular intervals to allow engineering teams
to better understand what is happening in customer environments.
As PremierOne products evolve over time, it is expected that Prometheus will stay constant even as
operating systems and deployment mechanisms change. For ongoing updates and support of the
solution, Motorola is developing an automated tool suite that will be available to MCSO resources. The
tool allows the continuous delivery of applicable updates and monitoring configuration packages.
Hardware Repair Coordination
Motorola will collaborate on the hardware repair of PremierOne system components that are supplied
by Motorola with third party vendors as listed on Attachment A (Covered Products, Support Options and
Pricing).
Description of Service
At Motorola’s discretion, the third-party infrastructure may be sent to the original equipment
manufacturer or vendor for repair.
Network Hardware Repair is also known as Infrastructure Repair.
Scope
Repair requests are assessed by the CMSO Technical Support team, which is available on a 24/7
basis. The Technical Support team will coordinate repairs with applicable third party vendors as listed in
Attachment A (Covered Products, Support Options and Pricing).
Inclusions
This service is available on Motorola-provided infrastructure components, including integrated third-
party products. Motorola will make a commercially reasonable effort to repair Motorola manufactured
infrastructure products after product cancellation. The post-cancellation support period of the Motorola
sourced product will be noted in the product’s end-of-life (EOL) notification published by the product
team.
Motorola Responsibilities
x
Provide MCSO access to the CMSO TSC, operational 24/7 to request repair service.
x
CMSO TSC will work with third-party vendors to coordinate the repair process and enable
remote work for the service.
x
Create a ticket with third-party vendors to initiate the repair process of faulty equipment.
Page 28
Limitations and Exclusions
Motorola may return infrastructure equipment that is no longer supported by Motorola, the original
equipment manufacturer, or a third-party vendor without repairing or replacing it. The following items
are excluded from this service:
x
All Motorola infrastructure components over the post-cancellation support period.
x
All third-party infrastructure components over the post-cancellation support period.
x
All broadband infrastructure components over the post-cancellation support period.
x
Physical, lightning, water, or shock damaged infrastructure components.
x
Third-party equipment not shipped by Motorola.
x
Consumable items including, but not limited to, batteries, connectors, cables, toner or ink
cartridges, tower lighting, laptop computers, monitors, keyboards, and mouse.
x
Video retrieval from digital in-car video equipment.
x
Non-standard configurations, MCSO-modified infrastructure, and certain third party
infrastructure.
x
Firmware or software upgrades.
MCSO Responsibilities
x
Contact or instruct servicer to contact the Motorola CMSO to request the third party repair
process.
x
Provide model description, model number, serial number, type of system, software and firmware
version, symptom of problem, and address of site location for spare infrastructure components.
x
Indicate if Motorola or third-party infrastructure components being sent in for service were
subjected to physical, lightning, shock, or water damage.
x
Follow Motorola and third-party vendors instructions regarding including or removing firmware
and software applications on infrastructure components being sent in for service.
x
Properly package and ship the malfunctioning component, at County’s expense. MCSO is
responsible for properly packaging the malfunctioning infrastructure component to ensure it is
not damaged in-transit and arrives in repairable condition.
x
Clearly print the return authorization number on the outside of the packaging.
x
Maintain versions and configurations for software, applications, and firmware to be installed on
repaired equipment.
x
Provide third-party with proper software and firmware information to reprogram equipment after
repair, unless current software has caused this malfunction.
Note - Inaccurate or incomplete information provided by MCSO or other delay by MCSO will result in delay of
repair by the third party vendor and may incur additional charges.
Software Maintenance
Description of Service
Motorola Advanced Services includes remote upgrades of any On Demand (OD) and Cumulative
Update (CU) Motorola software releases that may be available. Motorola will only provide releases that
have been analyzed, pre-tested and certified in a dedicated test lab.
MCSO will be responsible for scheduling remote support for the application of upgrades with the
Motorola TSC.
Page 29
Scope
Software releases, as well as any detailed documentation needed to implement the release, are posted
to the customer support portal for MCSO retrieval.
Releases means an Update or Upgrade to the Motorola Software and are characterized as “On
Demand (“OD”) Releases,” “Cumulative Updates (“CU”),” “Standard Releases,” or “Product Releases.”
The content and timing of PremierOne releases will be at Motorola sole discretion.
x
An “On Demand Release” is a release of Motorola Software that is done on demand to address
critical issues like stability, performance or priority 1 or 2 functional issues.
x
A “Cumulative Update” is defined as a release of Motorola Software that contains error
corrections to an existing Standard Release that do not affect the overall structure of the
Motorola Software. Cumulative Updates may contain product enhancements and
improvements. Cumulative Updates will be superseded by the next issued Cumulative Update.
x
A “Standard Release” is defined as a release of Motorola Software that may contain product
enhancements and improvements, such as new databases, modifications to databases, or new
servers, as well as error corrections. A Standard Release may involve file and database
conversions, System configuration changes, hardware changes, additional training, on-site
installation, and System downtime. Standard Releases will contain all the content of prior On
Demand Releases and Cumulative Updates that are reasonably available (content may not be
reasonably available because of the proximity to the end of the release cycle and such content
will be included in the next release).
x
A “Product Release” is defined as a release of Motorola Software considered the next
generation of an existing product or a new product offering. If a question arises as to whether a
Product offering is a Standard Release or a Product Release, Motorola opinion will prevail, if
Motorola treats the Product offering as a new Product or feature for its end user customers
generally.
Motorola Responsibilities
x
Provide access to software release via the customer support portal.
x
Provide access to detailed documentation to support the application of software releases.
Limitations and Exclusions
x
Provisioning efforts.
x
Motorola implementation or on-site upgrade and expansion services.
Customer Responsibilities
Ɣ
Schedule remote support for software release application.
Software Upgrade Services
Standard Release Software Upgrade Services
Software Upgrade Services are defined as the labor services required to execute on the planning,
delivering, testing and training of Motorola PremierOne standard releases of software to MCSO when
and if standard releases of software become available for those solutions components purchased as
part of the Motorola Maintenance and Support Agreement.
Page 30
Standard Release Software Upgrade Timing and Delivery Overview
x
When and if a standard release version becomes available, Motorola will upgrade the
PremierOne suite up to four times over the ten (10) year term, commencing from year one of
warranty/maintenance term.
x
For software upgrades, existing hardware and the existing PremierOne interfaces will be re-
utilized with the upgraded PremierOne software.
x
All upgrade activities will be coordinated and scheduled to occur at times that are mutually
agreeable to MCSO and Motorola. Scheduling of upgrade events will be completed at a
minimum of thirty (30) business days prior to the commencement of upgrade activities.
x
PremierOne CAD update activities are not expected to require downtime. The rolling update
approach is employed where one application server is taken offline, updated, then placed back
online. The process is repeated until all application servers are updated, followed by the RDW
server and the SCOM. While CAD updates are taking place, the system is up and operational;
however, unforeseen circumstances may result in temporary unavailability of the System.
x
Following the update of the production system, Motorola will update the Disaster Recovery
system in the same manner as the production system update, including those interfaces
supported on the Disaster Recovery system. Such tasks may be performed remotely.
x
MCSO will act as liaison with all user agencies and other outside agencies and/or organizations,
if/as necessary.
Upgrade Kickoff Teleconference
In order to finalize the upgrade project schedule and procedures, the upgrade event will be initiated with
an Upgrade Kickoff Teleconference that includes key MCSO and Motorola project participants.
The objectives of this task are:
x
To introduce all project participants.
x
Review roles of key participants.
x
Review overall upgrade scope and objectives.
x
Review resource and scheduling requirements.
x
Review testing methodology.
x
Review and finalize project schedule with MCSO.
x
Create testing plan to test PremierOne upgrades on staging environment.
x
Review testing plan and acceptance criteria.
x
Review features/functions introduced in the new software release version.
Motorola Responsibilities
Motorola Project Manager will direct Motorola efforts and serve as the primary point of contact for
MCSO. The responsibilities of the Motorola Project Manager include:
x
Maintain project communications with MCSO’s Project Manager primary point of contact for
MCSO. The responsibilities of the Motorola Project Manager include:
x
Maintain project communications with MCSO’s Project Manager.
x
Manage the efforts of Motorola project team and coordinate Motorola activities with MCSO’s
project team members.
x
Coordinate and oversee the installation of all licensed Motorola application software.
Page 31
x
Review and manage the scope of work for the upgrade activities.
x
Review the upgrade acceptance criteria.
MCSO Responsibilities
MCSO will designate a Project Manager who will direct MCSO’s efforts and serve as the primary point
of contact for the Motorola Project Manager. The responsibilities of MCSO’s Project Manager include:
x
Maintain project communications with the Motorola Project Manager.
x
Identify the efforts required of MCSO staff and assign appropriate resources to meet MCSO’s
task requirements described in this Statement of Work.
x
Liaison and coordinate with other MCSO agencies, other governmental agencies and MCSO’s
vendors, contractors and common carriers, as applicable.
x
Review and mutually approve upgrade acceptance criteria.
x
Completion Criteria.
This task is considered complete upon conclusion of the Upgrade Kickoff Teleconference.
Upgrade Preparation
The objective of this task is to perform the preparatory steps necessary for the PremierOne upgrade.
Motorola Responsibilities
x
Perform scheduling and coordination tasks necessary to obtain required resources that will
perform the upgrade of the PremierOne server software.
x
Confirm resource availability with MCSO and reconfirm task dates.
MCSO Responsibilities
x
Perform backup of PremierOne software and data files.
x
Completion Criteria
This task is considered complete when MCSO has completed the on-site data backup.
Staging Environment
The objective of this series of tasks is to install the upgrade software on a staged system environment
and validate release functionality.
Motorola Responsibilities
x
Remotely create a staging environment on MCSO’s PremierOne server(s) to conduct initial
installation of the release software.
x
Travel to MCSO site to perform upgrade tasks.
x
Install the release version of software on the staging environment.
x
Verify PremierOne functionality in accordance with release criteria.
x
Notify MCSO of availability of the staging environment enabling MCSO to perform MCSO-
specific testing activities.
MCSO Responsibilities
x
Observe testing on staging environment and acknowledge the delivery of the functionality
introduced in the release.
Page 32
x
Conduct testing on staging environment and notify Motorola of any functional errors or
anomalies.
x
Completion Criteria
This task is considered complete when the staging environment is available for MCSO testing.
On-Site Upgrade Implementation
The objective of this task is to conduct on-site activities required to complete the upgrade of the
PremierOne software.
Motorola Responsibilities
x
Travel to MCSO site to perform upgrade tasks.
x
Bring down the production system.
x
Reconfigure the data volumes on each of the existing-HP Blade Server as needed.
x
Convert PremierOne CAD system files and or provisioning data files as required.
x
Test each interface connection to ensure operational use of the each with the newly installed
Standard Release version.
x
Modify those interfaces affected by the installation of the Standard Release version and modify
each as needed to provide same functionality as was provided prior to the installation of the
Standard Release version.
x
Test system and subsystem interfaces to validate operation in accordance with the originally
installed interface requirement document.
x
Assist in MCSO testing as requested by MCSO and verify that each PremierOne subsystem
component is ready to resume production operations.
x
Install the applicable PremierOne subsystem client, application upgrades on client workstations
as listed in the Attachment A Covered Product, Support Pricing and Options.
x
Train MCSO on client upgrade process.
x
Train MCSO’s trainers/supervisors on new or changed features and functions introduced
through the standard release of the PremierOne.
MCSO Responsibilities
x
With Motorola assistance, coordinate the activities necessary to bring the production
PremierOne down, i.e. close incidents, sign units and users off duty.
x
Support Motorola software upgrade installation activities.
x
Provide and make available (during business hours, 8:00am to 5:00pm) the appropriate lines for
the testing of interfaces, to include 911, WWVB, Toning, etc.
x
Verify that the system is ready to resume production operations.
x
Install the PremierOne subsystem client on workstations beyond those upgraded by Motorola.
x
Train MCSO’s users on new or changed features and functions introduced through the standard
release of the PremierOne.
x
Completion Criteria.
This task is considered complete when each PremierOne subsystem component upgrade is verified by
MCSO to be available to resume production operation.
Page 33
PremierOne Production Cutover
Upon verification that the upgraded PremierOne is operational and ready to resume production use,
Motorola will assist MCSO with resuming operations on the upgraded system.
Motorola Responsibilities
x
Assist MCSO staff in resuming production operations on the upgraded system.
x
Provide up to eight hours of on-site support the day each upgraded subsystem component has
resumed production use.
MCSO Responsibilities
x
Schedule personnel to support the resumption of production use on the upgraded system.
x
Completion Criteria.
This task is considered complete upon MCSO resuming production operation of each PremierOne
subsystem component.
PremierOne Upgrade Acceptance
x
The objective of this task is to certify completion of the PremierOne subsystem upgrade.
x
Completion Criteria.
This task is considered complete upon MCSO resuming productive use of each affected PremierOne
subsystem component.
Remote Application Administrators
Motorola’s offer provides two application administrator (AA) resources, one for CAD, one for Records,
who are responsible for remotely delivering application administration and maintenance services as
herein defined. Each resource will be remotely available to MCSO for up to eighty (80) hours per
month. Motorola will work with the County to establish a work schedule and prioritize tasks to perform
during the monthly allotment. Upon mutual agreement between Motorola and MCSO, these resources
may provide on-site support to work with end-user staff directly (training, troubleshooting user
concerns/issues, meeting on configuration changes, understanding workflows, etc.). MCSO shall
provide at least two (2) weeks notice for on-site visits.
The remote AAs will be provided the reasonably necessary training to accomplish the tasks outlined in
this document. The AAs, with County’s guidance, will develop an understanding of the agency’s specific
environment, County-specific requirements, and configurations. AAs will act as the interface between
Motorola CMSO technical support teams to achieve the goals outlined by MCSO. The resource will
provide support for system provisioning, client software applications, and software upgrades and will be
equipped to perform workstation and/or client based diagnostic assistance.
Motorola and MCSO will meet on a quarterly basis, or on such cadence as agreed to, to review the
tasks performed over the previous quarter, discuss planned activities for the next quarter and overall
resource utilization of the AAs.
Remote CAD Application Administrator
The CAD AA’s responsibilities are:
x
Possess knowledge of the business practices of each end user area and how to use their
respective modules within the PremierOne CAD and Mobile system.
x
Assist MCSO with training plan development for users and system functionalities. Engage
appropriate Motorola Solutions subject matter experts when necessary.
Page 34
x
Coordinate with Motorola Solutions and/or MCSO Project Management as applicable.
x
Assist in assessing and assigning the initial and the correct priority level per the priority level
definitions in Table 1-1: PremierOne Priority Level Definitions and Response Times.
x
Diagnose, triage and coordinate with Motorola Solutions technical support to resolve reported
system incidents/problems.
x
This includes troubleshooting issues, which may include collecting application logs at the client
level.
x
This resource is not a technical system administrator and cannot resolve defects or troubleshoot
past configuration and application level logs.
x
This resource cannot resolve outages. If an outage or event that is degrading the system
occurs, it is advised MCSO calls support first and then call their AA for further involvement and
coordination. This will ensure the event gets resolved as quickly as possible.
x
Diagnose, triage and coordinate with the on-site IA, Motorola Solutions technical support,
Motorola Solutions engineering teams, for interface issues related to the Motorola System
responsibilities.
x
Follow MCSO required change management procedures prior to making any system change.
This may include seeking formal approval, coordination, user notifications, etc.
x
Assist in the development and maintenance of internal documentation pertaining to system
configuration, administration, and troubleshooting.
x
Possess knowledge of the business practices of each end-user area and use of their respective
modules within the PremierOne system CAD.
x
Possess knowledge of the PremierOne CAD and PremierOne CAD database schema in order
to support the SSRS Reporting System and be able to create end-user reports as requested.
x
Enter and maintain users within the PremierOne CAD.
x
Present newly available CAD system features and provide advice/assistance during need and
usability review.
x
Assist in establishing “pilot groups” for new system enhancements or problem resolution
analysis in order to review and provide feedback.
x
Assist County personnel with test plans.
x
Provide incident/problem information to track reported issues and progress towards resolution.
x
Create security groups and user roles to appropriately grant/limit system privileges as directed
by MCSO.
Remote Records Application Administrator
The Records AA’s responsibilities are:
x
Possess knowledge of the business practices of each end user area and how to use their
respective modules within the PremierOne Records system.
x
Assist MCSO with training plan development for users and system functionalities. Engage
appropriate Motorola Solutions subject matter experts when necessary.
x
Coordinate with Motorola Solutions and/or MCSO Project Management as applicable.
x
Assist in assessing and assigning the initial and the correct priority level per the priority level
definitions in Table 1-1: PremierOne Priority Level Definitions and Response Times.
x
Diagnose, triage and coordinate with Motorola Solutions’ technical support to resolve reported
system incidents/problems.
Page 35
-
This resource is not a technical system administrator and cannot resolve defects or
troubleshoot past configuration and application level logs.
-
This resource cannot resolve outages. If an outage or event that is degrading the system
occurs, it is advised MCSO calls support first and then call their AS for further involvement
and coordination. This will ensure the event gets resolved as quickly as possible
x
Diagnose, triage and coordinate with Motorola Solutions technical support for interface issues
related to the Motorola System responsibilities.
x
Follow MCSO required change management procedures prior to making any system change.
This may include seeking formal approval, coordination, user notifications, etc.
x
Assist in the development and maintenance of internal documentation pertaining to system
configuration, administration, and troubleshooting.
x
Possess knowledge of the business practices of each end-user area and use of their respective
modules within the PremierOne system Records.
x
Possess knowledge of the PremierOne Records and PremierOne Records database schema in
order to support the SSRS Reporting System and be able to generate and create end-user
reports as requested.
x
3HUIRUPXSGDWHVFKDQJHVWRH[LVWLQJௗ35HFRUGVZRUNIORZV
x
3HUIRUPXSGDWHVFKDQJHVWRH[LVWLQJௗPRGXOHFRQILJXUDWLons completed during deployment
x
Complete ACT work to setup new modules as needed by MCSO (note: an assessment will be
made with MCSO on if the work can be completed according to the expectations/desire of
MCSO. If it requires a 3rd party, or further integration not supported by the system, the work will
not be able to be completed).
x
Present newly available Records system features and provide advice/assistance during need
and usability review.
x
Assist in establishing “pilot groups” for new system enhancements or problem resolution
analysis in order to review and provide feedback.
x
Assist County personnel with test plans.
x
Provide incident/problem information to track reported issues and progress towards resolution.
x
Create security groups and user roles to appropriately grant/limit system privileges as directed
by MCSO.
Security Update Services
Motorola’s PremierOne Security Update Service (SUS) provides pretested security updates for
PremierOne system components, minimizing cyber risk and software conflicts. The security updates
contain operating system security patches, Microsoft SQL security updates, network infrastructure
device updates, firmware and other key system component updates. The SUS deliverables have been
validated for compatibility with PremierOne systems.
In order to receive the Security Update Services as defined within this section, MCSO is required to
maintain their PremierOne system at a release level consistent with the PremierOne support policy.
Description of Service
Motorola uses a dedicated information assurance environment to test and validate security updates.
Motorola deploys and tests security updates to check for and prevent potential service degradation.
Motorola releases tested, compatible security updates for download and installation. Once security
updates are verified, the patching solutions are made available on a secure website. Additionally, a
Page 36
release notification email is sent to relevant contacts to inform them that a security update release is
available for download. If there are any recommended configuration changes, warnings, or
workarounds, the SUS team will provide information with the security updates on the secure website.
MCSO’s representative is responsible for downloading security updates, installing them on applicable
components, and rebooting updated components as required to complete the patching process.
Scope
SUS includes pretested security updates for the software listed in Table 1-3: Update Cadence. This
table also describes the release cadence for security updates.
Table 1-3: Update Cadence
Software
Update Release Cadence
Microsoft Windows
Monthly
Microsoft Windows SQL Server
Quarterly
Fortinet Firewall
Quarterly
Extreme Network Switches*
Quarterly
HPE SAN
Annually
StoreOnce or TrueNAS Backup appliance
Annually
VMWare Hypervisor
Quarterly
HP SPP Firmware
Quarterly
F5 Big-IP
Quarterly
*Only 2023 configurations or later. Applies only to customers with Extreme switches.
Inclusions
Supported releases for PremierOne SUS are shown in the table below, Table 1-4: PremierOne SUS.
Motorola reserves the right to determine which releases are supported as business conditions dictate.
Additional charges may apply in the event of supporting older releases. Contact Motorola’s PremierOne
product technical support at 800-MSI-HELP for the latest supported releases.
Table 1-4: PremierOne SUS
Service
PremierOne SUS
Supported Releases
PremierOne Security Update Service
MCSO Self-installed
Current Release
Current Release -2
Responsibilities for downloading and installing security updates and rebooting applicable hardware are
detailed in Installation and Reboot Responsibilities below.
Motorola Responsibilities
x
On the release cadence in Table 1.3, review relevant and appropriate security patches released
by Original Equipment Manufacturer (OEM) vendors.
x
Release tested and verified security patches via Motorola’s secure website.
x
Publish documentation for installation, recommended configuration changes, any identified
issue(s), and remediation instructions for each security update release.
Page 37
x
Send notifications by email when security updates are available to download from the secure
website. Limitations and Exclusions
x
Systems with non-standard configurations such as non-standard MCSO provided hardware are
specifically excluded from this service, unless otherwise agreed in writing by Motorola.
x
Interim or unplanned releases outside the supported release cadence.
x
Service does not include some network infrastructure elements. Updates to these devices will
be undertaken at the time of PremierOne software update or on an ad-hoc basis as required
during business hours.
x
Service does not include updates to the Cloud Connect Server.
x
Motorola product updates are not included in these services.
x
Motorola does not represent that it will identify, fully recognize, discover, or resolve all security
events or threats, system vulnerabilities, malicious codes or data, backdoors, or other system
threats or incompatibilities as part of the service, or that the agreed upon cadence/time of
delivery will be sufficient to identify, mitigate or prevent any cyber incident.
MCSO Responsibilities
x
Provide Motorola with predefined information necessary to onboard the service prior to the
Agreement start date.
x
Provide timely updates on changes of information supplied to Motorola’s assigned Customer
Support Advocate (CSA).
x
Update Motorola with any changes in contact information, specifically for authorized users of
Motorola’s secure website.
x
Provide means for accessing Motorola’s secure website to collect the pretested files.
x
Download and apply only to MCSO's system as applicable, based on the Customer Agreement
and the scope of the purchased service. Distribution to any other system or user other than the
system/user contemplated by the Customer Agreement is not permitted.
x
Implement Motorola Technical Notices (MTN) to keep the system current and patchable.
x
Upgrade system to a supported system release when needed to continue service. Contact
Motorola’s assigned CSA for the latest supported releases.
x
Comply with the terms of applicable license agreements between County and non-Motorola
software copyright owners.
Installation and Reboot Responsibilities
Installation and Reboot responsibilities are determined by the specific SUS package being purchased.
Table 1-5: Installation and Reboot Responsibilities Matrix contains the breakdown of responsibilities.
Table 1-4 Inclusions indicates which services are included.
Microsoft Windows servers and workstations often need to be rebooted before security updates take
full effect and mitigate vulnerabilities.
Table 1-5: Installation and Reboot Responsibilities Matrix
SUS Package
Motorola
Responsibilities
MCSO Responsibilities
PremierOne Security
Update Service
Customer Self-
installed
ƒ Deploy pretested files to MCSO’s system as instructed in the
“Read Me” text provided on Motorola’s secure website.
ƒ When a security update requires a reboot, reboot servers and
workstations after security updates are installed.
Page 38
Disclaimer
This service tests OEM security updates. Delivering security updates for specific software depends on
OEM support for that software. If an OEM removes support (e.g. end-of-life) from deployed software,
Motorola may work with the OEM to reduce the impact but may remove support for the affected
software from this service without notice.
OEMs determine security update schedules, supportability, or release availability without consultation
from Motorola. Motorola will obtain and test security updates when they are made available and
incorporate those security updates into the next appropriate release.
All security updates are important. This service is intended to balance the security and compatibility of
tested updates with agreed upon time/cadence of delivery. County assumes the risk of this inherent
tradeoff.
Motorola disclaims any warranty with respect to pretested database security updates, hypervisor patches,
operating system software patches or other third-party files, express or implied. Further, Motorola disclaims any
warranty concerning non-Motorola software and does not guarantee MCSOs' systems will be error-free or
immune to security breaches as a result of these services.
Conditions and Exclusions
Conditions
Motorola services enhance performance of your CAD systems. In order to provide a consistent level of
quality services, the following conditions and limitations apply:
x
Remote monitoring, troubleshooting and restoration require that MCSO provides direct remote
access to all locations and equipment and that you have the necessary equipment and
connectivity available for the remote access session.
x
MCSO must operate hardware and software in accordance with the applicable Agreement
between Motorola and County. Equipment may not be covered if exposed to misuse, damage,
unauthorized modification or other abuse or used in a manner for which it was not designed.
x
Equipment must be operated in a normal environment and protected from adverse conditions,
which may impact performance and/or damage equipment.
Exclusions
Motorola service and support obligations hereunder will not apply to any Motorola supported software
or hardware if correction of an error, adjustment, repair or parts replacement is required because of:
x
Accident, neglect, tampering, misuse, improper / insufficient grounding, failure of electric power,
electric surge, shock, water damage, failure of MCSO and/or others to provide appropriate
environmental conditions, relocation of hardware or software, or causes other than ordinary use.
x
Repair or alteration, or attempted repair or alteration of any supported hardware and/or software
by MCSO or others, unless otherwise approved in writing by Motorola.
x
Connection of another machine, device, application or interface to Motorola supported
equipment (hardware and/or software) by MCSO or others, which has caused damage to
Motorola supported equipment.
x
Damage or destruction caused by natural or man-made acts or disasters.
x
Failure or degradation in performance of Motorola supported equipment (hardware and/or
software) due to the installation of another machine, device, application, or interface not
specifically certified and approved by Motorola for use in MCSO’s environment.
Page 39
x
The operation of the software in a manner other than that currently specified in applicable
product documentation.
x
Incompatible or faulty MCSO hardware and/or software interfaces.
x
Modifications made without Motorola written approval to the OS, network, hardware or software
environment or software applications.
x
Cosmetic repairs, furnishing consumables, supplies, or accessories, making accessory
changes, system administration, or adding additional devices or non-approved Motorola
software applications.
Cloud Entitlement
x
Cloud entitlement (migration to/adoption of Cloud functionality which replaces contracted
PremierOne on premise functionality) is included in this contract at no additional cost to the
County as it becomes available and meets the needs of MCSO users. The Cloud solution and
migration will adhere to the County’s cyber security requirements. This migration entitlement
enables the following:
x
During the contract term, if and when on premise products covered by this Agreement become
available in native Cloud environments and MCSO determines such products can replace a
covered on-premise application, MCSO and Motorola will work in good faith to mutually develop
an implementation plan, migration schedule, and training plan (train-the-trainer), for product(s)
which suit MCSO's needs in the Cloud environment. If services described in this Appendix are
no longer required as a result of the migration to a Cloud solution, Motorola and MCSO will
mutually agree to update this Appendix accordingly.
x
This agreement creates no obligation of County to pay additional amounts above and beyond
the costs agreed hereto. In the event no acceptable, correlated Cloud product(s) suitable for
MCSO become available, MCSO shall continue to operate the products and Motorola will
continue to support and maintain such products as described in this Agreement.
GIS Managed Services
Premium GIS Managed Services provide geodata management and geoprocessing of Customer-
provided input data. Geodata management is a collection of activities including organizing and editing
GIS spatial and attribute data (location and attributes of features, including their shapes and
representation) to maintain current and accurate location information. Geoprocessing performs
operations on the dataset and returns the results as an output dataset used in the Motorola system for
location validation, CAD recommendations, and visual maps.
This GIS managed services solution does not include the creation or maintenance of data into the
NENA NG911 schema. Any NG911 work is out of the scope of this contract. Service delivery is limited
to that presented in this Statement of Work. While Motorola is responsible for executing data updates in
accordance with direct MCSO requests, Motorola is not responsible for data errors stemming from
MCSO’s source data. Requests for service outside of this SOW will be considered by Motorola in
accordance with Motorola’s contract change process.
GIS Managed Services Premium provides a quarterly service delivery cadence. The duration of the
service is three (3) years commencing in the first quarter following Go-Live of the PremierOne system.
Data Types and Frequency Table
The Data Types and Frequency Table presents the layer types and update cadence provided by
Motorola that will be processed as described in this SOW.
Page 40
Layer classifications defined as:
x
External – layers that are supplied to Motorola that are used for processing/publishing or visual
map display.
x
Agency – layers that are either managed by Motorola on behalf of MCSO or hosted by Motorola
for MCSO to manage.
x
Routing – layer(s) that is used specifically for quickest routing and managed by either Motorola
on behalf of MCSO or by the customer as an external source.
Defined Layers
Update Frequency
External Layers
At minimum, Address Points and Street Centerlines
Quarterly
Agency Layers
Limited to zones/beats polygons, common place
points, points of interest, and city polygon.
Quarterly
Routing Layers
Limited to a network enabled Street layer
Quarterly
Service Delivery Environment
MCSO will provide the following environment required to support the delivery of the service:
x
Dedicated GIS server or desktop with unattended access by Motorola, exclusively used to
support the PremierOne solution that meets or exceeds current Esri ArcGIS Server system
requirements.
x
Installation of PremierOne full client on GIS Server or desktop.
x
ArcGIS Desktop/Pro Basic license. MCSO will supply authorization files to Motorola.
x
If MCSO is unable to provide authorization numbers, they will work directly with an Esri
account representative to acquire license authorization numbers.
x
If the PremierOne Quickest Route module is purchased, an Esri ArcGIS Desktop/Pro
Network Analyst Extension license will be provided by the Customer.
x
MCSO is responsible for staying current with Esri ArcGIS Desktop/Pro + Extensions annual
software maintenance.
x
A local user account with local administrator permissions on the GIS Server or desktop.
x
Request necessary patches required to support the GIS Managed Service delivery.
Motorola will provide to the following environment items required to deliver the service:
x
A non-production refresh if not previously completed within three months of the term
Effective date.
x
Validate Esri software version(s) and authorizations inclusive of ArcGIS Server, ArcGIS
Desktop/Pro and Network Analyst Extension license (for use with PremierOne Quickest
Route module) on the GIS Server or desktop.
x
Remote Access appliance (i.e. Bomgar) installation file used for unattended remote access.
x
An ArcGIS Enterprise account used by MCSO to maintain identified agency layers via the
Motorola-provided local data web application.
MCSO acknowledges that change in the access method will cause Motorola delays or inability to
complete delivery of service. In such instances, service delivery will resume at such time that
Page 41
remote access is restored. Delays resulting from a change in access method will not result in a
change in the service term.
GIS Managed Services Welcome Call
The objective of the GIS Managed Services Welcome Call is to review the processes and procedures
involved in delivering the service, the delivery cadence and engagement process, and the scope of the
service.
Motorola Responsibilities
x
Initiate the welcome teleconference.
x
Review the roles of the project participants to identify communication flows and decision-making
authority between project participants.
x
Review unattended GIS data access method to the GIS Server or desktop with MCSO.
x
Review the Service Delivery Environment requirements.
x
Review Motorola and MCSO responsibilities, expectations, scope, and terms of the service.
x
Review existing visual maps.
x
Discuss MCSO’s access to and knowledge of the Motorola-provided local data web application.
x
Discuss and agree upon recurring dates that Motorola will deliver GIS updates. Delivery date
could be plus or minus five business days from the agreed upon date.
x
Request and receive the most up to date copy of existing GIS Data (as determined by Motorola)
in an Esri supported format.
MCSO Responsibilities
x
Acknowledge the need for MCSO data edit requests to be clearly defined, communicated, and
delivered to Motorola in accordance with the agreed upon schedule.
x
Name a GIS knowledgeable person who will serve as the single point of contact and be
responsible for communication of data edits and clarification of data edit requests.
x
Acknowledge the unattended GIS data access method to the GIS Server.
x
Confirm network access of GIS Server or desktop for use by the PremierOne system.
x
Review the layers included in the updates noted in the Data Types and Frequency Table.
x
Provide the recurring dates that Motorola will deliver the GIS updates.
x
Provide requested GIS data within ten business days of the conclusion of the GIS Services
Welcome Call.
Data Update and Publishing
All GIS data layers are sourced by the Customer and supplied to Motorola. GIS layers include location
verification, zone and routing data represented in point, line and polygon feature classes. GIS data and
map updates are completed with the update frequency presented in the Data Type and Frequency
table.
For each update, the ArcGIS Server services used by the PremierOne system will be refreshed with the
updated data and activated for the Customer. The Customer will be notified before and after the update
is applied to confirm the update is functional after completion.
Page 42
Motorola Responsibilities
x
Perform symbology and labeling updates to map services as requested by MCSO and
published per the update frequency.
x
Create mobile map packages (MMPK) for offline use of the PremierOne Mobile Map, all
associated locators and, if present, network dataset will be included in MMPK package.
x
Update MCSO’s practice database and transmit email correspondence to MCSO confirming
delivery of an update.
x
Prior to updating MCSO’s live database, email MCSO to inform them of the time the live
database will be switched to the updated services.
x
Email MCSO upon completion of live database and map services updates confirming
completion of the delivery cadence.
MCSO Responsibilities
x
Provide Motorola with consistent GIS data upon request at least ten business days before the
scheduled update.
x
Use Motorola-provided local data web application to update agency GIS data layers.
x
Provide Motorola with clear and specific agency data layer update changes that are not
available in Motorola provided local data web application.
x
Within five business days of Motorola notification of an update being applied to the practice
database, test location and zone assignments.
x
Notify Motorola of any issues with the updates on the practice database that cause MCSO to
reject the update and prevent Motorola from applying the update to the live system.
x
Distribute MMPKs to Customer devices that have PremierOne Mobile Map installed.
x
If MCSO fails to notify Motorola of the rejection of an update within the allotted time, Motorola
will apply the update to the live database and consider the service delivery complete.
Esri and PremierOne GIS Service Environment Updates
Maintaining the Esri and PremierOne GIS Service environment is a collaborative set of tasks to be
fulfilled by each party.
MCSO will update the Esri ArcGIS Desktop/Pro software as needed to support the operation of the
PremierOne solution. In the event the Customer cannot update the Esri ArcGIS Desktop/Pro software,
the Customer will provide the Esri authorization information to Motorola. Motorola will perform and
authorize the update.
In the event an Esri version update to ArcGIS Server is required for ongoing support of the PremierOne
system, Motorola will perform the update and authorization of ArcGIS Server (stand-alone application
only) in conjunction with a PremierOne CAD upgrade in accordance with the terms and conditions of
support.
Page 43
Attachment D: Labor Rates
The following are Motorola’s current labor rates for services outside of the scope of the Maintenance
and Support Agreement, subject to an annual change.
The following rates apply to Customers with a current, active Maintenance and Support Agreement.
SERVICE HOURS
LABOR RATES
8 a.m.-5 p.m. M-F (local time)
$223 per hour, 2 hours minimum
After 5 p.m., Saturday, Sunday, Motorola Holidays
$334 per hour, 2 hours minimum
The following rates apply to Customers without a current, active Maintenance and Support Agreement
and apply to services available on a Time and Material basis:
SERVICE HOURS
LABOR RATES
8 a.m.-5 p.m. M-F (local time)
$446 per hour, 2 hours minimum
After 5 p.m., Saturday, Sunday, Motorola Holidays
$668 per hour, 2 hours minimum
Above rates reflect labor rate only. Additional fees for on-site travel expenses, third party expenses and
/or materials will be quoted at the time of customer request for services.
Page 13-1
Attachment E: Hardware Refresh Services Statement of Work
General Information
This document describes the scope of work for providing PremierOne system hardware refresh and to
upgrade MCSO to the latest generally available release of PremierOne application software at the time
of the hardware implementation, hereinafter referred to as Hardware Refresh.
Per the terms of the Agreement, Motorola will perform services described in this Statement of Work to
upgrade the system hardware one time during terms of this agreement.
Nothing in this Statement of Work is meant to supersede, replace or amend the terms and conditions
stated in the Motorola Inc. Contract or Maintenance and Support agreement.
Upgrade Considerations
The scope of work described herein is based on the following considerations:
x
All parties recognize that the SOW is not necessarily formatted chronologically with contractual
obligations defaulting to the project schedule.
x
Only those interfaces covered under the terms of the contract will be validated and or modified
to ensure operational use with the hardware refresh and upgraded PremierOne System
software. Supported interface functionality is that which is described in the original interface
functional documents (IFD).
x
Prior to cutover, there may be periods of time during which interface functionality will not be
available for production operations while testing is conducted with the new hardware.
x
If the upgraded software version supports enhanced interface functionality that is desired but
not supported by the original interface, such enhanced functionality shall not be available unless
specifically included in the scope described herein.
x
CAD user interface (UI) customization will be replicated from the current CAD UI.
x
MCSO should be prepared to go to a “manual” mode during the periods of time when operations
are moving from the existing system to the upgraded system.
x
SQL upgrades are not included.
Hardware and Software Upgrade Implementation
The objective of this task is to conduct activities required for the upgrade of the PremierOne hardware
and software. Motorola will procure and deliver the new system hardware and software to the primary
site.
The new system equipment will be installed at the primary site where it will be tested and made
available to MCSO for additional user testing and training. Upon acknowledgement that testing and
training has been successfully completed, users will transition to the upgraded production system.
Kickoff Teleconference
In order to finalize the project schedules and procedures, the hardware refresh event will be initiated
with a kickoff teleconference that includes key MCSO and Motorola project participants.
The objectives of this task are:
x
To introduce all project participants.
x
Review roles of key participants.
x
Review overall upgrade scope and objectives.
Page 13-2
x
Review the list of equipment
x
Review the list of interfaces.
x
Discuss client upgrade procedures and coordination.
x
Review resource and scheduling requirements.
x
Review and finalize project schedule with MCSO.
x
Review operational readiness and resumption of use criteria.
Motorola Responsibilities
x
Assign a Project Manager that will direct Motorola’s efforts and serve as the primary point of
contact for MCSO.
x
Schedule and facilitate the kickoff teleconference.
x
Discuss GIS requirements, if applicable.
x
Maintain project communications with MCSO’s project manager.
x
Manage the efforts of Motorola project team and coordinate Motorola activities with MCSO’s
project team members.
x
Coordinate and oversee the installation of hardware and all licensed Motorola application
software.
x
Deliver product release documentation.
MCSO Responsibilities
x
Designate a project manager who will direct MCSO’s efforts and serve as the primary point of
contact for the Motorola Project Manager.
x
Provide input to the final project schedule dates.
x
Identify the efforts required of MCSO staff and assign appropriate resources to meet MCSO’s
task requirements described in this Statement of Work.
x
Liaison and coordinate with other partner agencies, other governmental agencies and MCSO’s
vendors, contractors and common carriers, as applicable.
x
Provide all network infrastructures. Motorola makes no provision for cabling or capital
improvements to the installation environment and power consumption considerations that may
be required to support the PremierOne solution.
x
Maintain responsibility for connectivity to all external systems.
x
In the event modifications to 3rd party systems to which PremierOne interfaces are required to
maintain or enhance interface functionality, is responsible for engaging and/or contracting with
the 3rd party and any associated costs associated to effect such changes.
x
Act as liaison with all user agencies and other outside agencies, organizations and 3rd party
vendors, if/as necessary.
Completion Criteria
This task is considered complete upon conclusion of the Upgrade Kickoff Teleconference.
PremierOne Hardware Refresh Project
Motorola Responsibilities
x
Order hardware and software.
x
Stage system at Motorola facility.
Page 13-3
x
Integrate and configure server and hardware components.
x
Backup and restore production database from existing system.
x
Ship system to MCSO site.
x
Travel to perform installation tasks.
x
Configure interface connections, depending on connections MCSO makes available.
x
Remotely review new features and functions.
x
Remotely conduct provisioning and functionality upgrade training.
x
Provide remote support for up to ten (10) business days while MCSO tests system.
MCSO Responsibilities
x
Provide and make available (during business hours, 8:00am to 5:00pm) remote connectivity and
access to 3rd party systems for initial testing of environment.
x
Perform testing on system (up to 10 business days).
x
Train users on new or changed features and functions.
x
MCSO will ensure all firmware and BIOS on all MCSO provided hardware are at a currently
supported level or County may elect to contract with MSI for the services to perform such
updates.
Cutover To Production System
Motorola Responsibilities
x
Assist MCSO in developing cut-over plan to include plan for CAD and Mobile client updates.
x
Perform final backup and transfer of CAD database to new system.
x
Test system and subsystem interfaces with production connections to validate operation in
accordance with the original ISDs.
x
Verify system readiness for Go-Live.
x
Support the transition of production operations to the upgraded system. Support will be provided
on the day of the upgrade and during business hours for two days following the upgrade.
MCSO Responsibilities
x
Provide and make available (during business hours, 8:00am to 5:00pm) the appropriate lines for
production testing of interfaces.
x
Acknowledge system readiness for production cutover.
x
Execute the plan to install upgraded client software on CAD workstations and mobile devices.
x
Facilitate the transition of production operations to the upgraded primary system.
Completion Criteria
This task is considered complete when the production operations have transitioned to the upgraded
primary PremierOne system.
Proposed or Equivalent Equipment
At the time of planning for the Hardware Refresh, Motorola will review the as-built equipment list and
update it based on current technology and MCSO’s current storage needs, etc.
Page 13-4
Attachment F: Summit Pre-Paid Tickets Solution Description
Motorola Solutions, Inc. (Motorola) invites you to attend our annual users’ conference, Summit. This
document outlines details and policies for using pre-paid tickets to attend the event.
Please contact software.summit@motorolasolutions.com if you have any questions about Summit pre-
paid tickets or this policy.
Summit Overview
Summit is Motorola’s largest annual gathering of public safety customers. Attendees convene for in-
depth classes, hands-on training, product vision, networking, and feedback sessions. Summit offers
hundreds of hours of educational courses designed for every customer role, including technical
administrators, call takers, dispatchers, records and corrections personnel, analysts, patrol, and
command staff.
The Purpose of Pre-Paid Tickets
To ensure that personnel get the critical training they need to improve adoption of their solutions, many
customers pay for Summit ahead of time, as part of a contract or annual maintenance agreement.
Under this approach, Motorola applies the fees already paid by the customer to cover all reasonable,
business-related expenses for that customer to attend the conference.
Types of Pre-Paid Tickets
x
County has elected to purchase the Pre-Paid Travel Package.
Pre-Paid Travel Package: Includes the conference registration fee; hotel; either choice of
airfare with airport transportation OR car rental; and additional meals not included by the
conference.
Redemption of Pre-Paid Tickets
Registration for Summit opens approximately 4-5 months prior to the event. MCSO should work with
their Customer Success Advocate to make sure that agency personnel receive the regularly emailed
invitations to register. MCSO attendees should select the Pre-Paid Travel Package registration option.
The registration will go through a hold process while funds are verified. Once funds are confirmed, the
attendee’s conference registration will be completed. MCSO attendees will then receive instructions to
complete their travel arrangements.
Once available pre-paid tickets are depleted, MCSO can send additional attendees at the regular
conference rate and should register using the Standard Registration option.
Assumption of Agency Permission
When MCSO begins their registration, they will be cautioned that they are about to exercise an option
that will reduce the applicable pre-paid tickets from their available balance. It is MCSO’s responsibility
to ensure that only authorized attendees select this option.
Pre-Paid Travel Details and Policies
A Pre-Paid Travel Attendee is defined as a Motorola customer who has opted to use the agency’s
available pre-paid tickets to pay for the Pre-Paid Travel Package registration option.
This option includes the conference registration fee, the attendee’s choice of either airfare with airport
transfer OR car rental, hotel lodging, and additional meals not covered by the conference.
Page 13-5
Note: Due to multi-year contracts, some customers have locked-in pre-paid attendance at different prices from
those published with each year’s conference. Each agency’s rate will be determined by the price listed in its own
agreement.
Travel Package Inclusion
The Pre-Paid Travel Package includes the following reasonable and necessary business-related travel
expenses as defined below:
x
Summit conference registration fee, which includes access to all training sessions, breakfasts
and lunches, and all special events and meals.
x
The attendee’s choice of the following, both to be booked with Motorola’s approved travel
partner (Travel Partner), within parameters approved by Motorola:
-
Round-trip airfare with airport transfers.
OR
-
Round-trip car rental.
x
Hotel accommodations at a Summit host hotel, booked with Travel Partner.
x
Stipend for additional meals not covered through the conference (see Covered Meals below).
Travel Package Policies
General
x
Upon registration and confirmation of available pre-paid tickets, Pre-Paid Travel Attendees will
receive detailed instructions for booking travel logistics.
x
Attendees are only to book travel through Travel Partner and are not to book hotel, airfare, or
transportation on their own. Reimbursement for travel expenses incurred by any customer
attendee is not allowed.
Hotel
x
The Pre-Paid Travel Package covers hotel nights directly associated with the conference dates.
It may be possible to make adjustments to arrival and departure dates, but attendees are
responsible for any additional hotel nights (before and after the official conference dates). Travel
Partner may be able to assist with additional pre- or post-conference travel plans, but the
attendee will be responsible to pay for additional hotel room nights and will need to put a
personal card on file upon check-in at the hotel.
x
Hotel accommodations at a Summit host hotel (single/double occupancy only) include hotel
room and applicable state and local taxes at a discounted Motorola conference rate. Additional
services (e.g. additional phone charges, laundry, entertainment, amenities, etc.) are at the
attendee’s expense.
x
A personal credit card WILL be required upon check-in to the hotel. PLEASE NOTE THAT THE
PERSONAL CREDIT CARD WILL NOT BE CHARGED for the room and tax expenses. This is a
standard hotel requirement to cover any incidental expenses that may be incurred.
x
Attendees staying in their rooms past checkout time may be billed one (1) additional night’s stay
to their personal credit card. Late checkout may be provided based on availability and upon
request through the hotel, although some charges may apply. Early departure fees may apply if
a group attendee checks out prior to the confirmed dates. Motorola is not responsible for this
charge, which will be applied to the personal credit card on file for incidentals.
Page 13-6
Airfare
x
The Pre-Paid Travel Package will cover round-trip airfare (using Motorola’s negotiated rates
with major airlines), as well as airport transfers to and from the destination airport. Air
reservations must be made ONLY through Travel Partner.
x
Airfare must be economy class or standard coach with a fare cap of $600. Any travel above
$600 will be routed by Travel Partner to Motorola for approval and must be accompanied by a
valid business reason. Attendees are encouraged not to delay making their airfare selections,
as selections made closer to the travel dates will likely fall outside of the allowed range.
x
Any airfare changes must be made through Travel Partner.
x
Pre-approved travel dates are for the official conference dates. Attendees choosing to travel
outside these parameters will require additional approval from Motorola. Any resulting fare
differences due to altered travel dates are the responsibility of the traveler (including airfare and
hotel and ground transportation).
x
Additional fees, tips, and surcharges, including (but not limited to) remote access charges,
change fees, upgrade fees, and baggage fees are not covered as part of the Motorola Solutions
travel policy.
x
Airport transfers to and from the destination airport will be provided to attendees. If an attendee
chooses to extend their stay either pre- or post-conference, that attendee will be responsible to
pay for additional transportation required for the extended stay.
Car Rental
x
MCSO may opt for car rental coverage instead of airfare. The Pre-Paid Travel Package will
cover the expense of a rental car using Motorola’s negotiated rates. Reservations must be
made ONLY through Travel Partner.
x
When renting a vehicle for Summit, Motorola will include the Loss Damage Waiver covering the
vehicle at the base rate at participating locations.
x
The rental will also include the Prepaid Gas Option providing the first tank of gas to the renter
and allowing the renter to return the vehicle with less than a full tank. Additional Liability
Insurance (ALI), Personal Effects Protection (PEP), and Personal Accident Insurance (PAI) are
not covered by Motorola, but the attendee may purchase them at the time of the reservation or
rental with a personal credit card.
Covered Meals
As part of this event, Motorola will provide meals to all attendees as part of the regular conference
registration fee according to the published Summit agenda.
In addition to the covered conference meals, any attendee registering with a Pre-Paid Travel Package
will receive a credit, voucher, or meal access to any breakfast, lunch, or dinner not provided on official
conference dates. The method used to cover these additional meals may vary from year to year, based
on venue, but will be communicated in advance to Pre-Paid Travel Attendees.
Daily meal allowance is determined by Motorola, based on published guidelines. In no event will the
amount provided exceed attendee’s applicable agency rules regarding meal expenses, provided that
the attendee or agency notifies Motorola Solutions in advance of the conference of any restrictions,
prohibitions, or limitations.
Expenses Not Covered
Non-reimbursable expenses include, but are not limited to:
x
Hotel telephone charges (local as well as long distance)
Page 13-7
x
Personal travel (e.g., gas, side trips, extended stay outside official conference dates)
x
Traffic or parking violations
x
Additional travel accident insurance
x
Personal entertainment
x
Airline upgrades
x
Spouse or guest expenses
x
Alcoholic beverages (minibar), non-food related items
x
Gift shop
x
Movies
x
Laundry
x
Late checkout, hotel early departure, or no-show fees
x
Valet parking
x
Baggage handling
x
Airport parking fees
x
Miscellaneous tips
x
Upgraded hotel internet connection
x
Transportation to and from home airport
x
Change in airline departure dates, times, or names
x
Excess baggage fees charged by airlines
x
Additional equipment on rental cars (e.g. GPS, baby seat, etc.)
x
Gas
x
Tolls
x
Additional guests staying in the same guest room, which results in additional hotel charges
Note: Motorola reserves the right to decline any expense that is not within the scope of this policy. It is not
Motorola’s intent to ever exceed an attendee’s applicable agency policies or guidelines regarding any related
travel accommodation. It is the customer agency or attendee’s responsibility to notify Motorola in advance of any
booking, if any restrictions, prohibitions, or limitations apply.
Page 14-1
Section 14
Exhibit J: Motorola Proposal
(Reference Document)
Motorola’s response to the “MARICOPA COUNTY, AZ SERIAL # 230055-RFP REQUEST FOR
PROPOSALS FOR CAD, RMS, AND MOBILE SYSTEMS, SUPPORT, AND MAINTENANCE” is
incorporated by reference.
Certificate Of Completion
Envelope Id: 33D2E3CF91244946BF098EB3930AD1E5
Status: Completed
Subject: Complete with Docusign: MARICOPA COUNTY FINAL CONTRACT DOCS 090624.pdf
Source Envelope:
Document Pages: 559
Signatures: 1
Envelope Originator:
Certificate Pages: 5
Initials: 0
Robin Bradshaw Ginther
AutoNav: Enabled
EnvelopeId Stamping: Enabled
Time Zone: (UTC-06:00) Central Time (US & Canada)
500 West Monroe
Chicago, IL 60661
robin@motorolasolutions.com
IP Address: 72.200.103.29
Record Tracking
Status: Original
9/6/2024 2:46:49 PM
Holder: Robin Bradshaw Ginther
robin@motorolasolutions.com
Location: DocuSign
Signer Events
Signature
Timestamp
Travis Boettcher
travisb@motorolasolutions.com
Corporate Vice President, Command Center
Software
Security Level: Email, Account Authentication
(None)
Signature Adoption: Pre-selected Style
Using IP Address: 68.225.205.56
Sent: 9/6/2024 3:10:18 PM
Viewed: 9/6/2024 3:30:24 PM
Signed: 9/6/2024 3:34:41 PM
Electronic Record and Signature Disclosure:
Accepted: 9/6/2024 3:30:24 PM
ID: 472c555b-3d01-4141-bd27-de6589365cef
In Person Signer Events
Signature
Timestamp
Editor Delivery Events
Status
Timestamp
Agent Delivery Events
Status
Timestamp
Intermediary Delivery Events
Status
Timestamp
Certified Delivery Events
Status
Timestamp
Carbon Copy Events
Status
Timestamp
Brian Walsh
brian.walsh@maricopa.gov
Security Level: Email, Account Authentication
(None)
Sent: 9/6/2024 3:35:40 PM
Viewed: 9/6/2024 3:55:12 PM
Electronic Record and Signature Disclosure:
Not Offered via DocuSign
Witness Events
Signature
Timestamp
Notary Events
Signature
Timestamp
Envelope Summary Events
Status
Timestamps
Envelope Sent
Hashed/Encrypted
9/6/2024 3:10:19 PM
Certified Delivered
Security Checked
9/6/2024 3:30:24 PM
Signing Complete
Security Checked
9/6/2024 3:34:41 PM
Completed
Security Checked
9/6/2024 3:35:40 PM
Payment Events
Status
Timestamps
Electronic Record and Signature Disclosure
ELECTRONIC RECORD AND SIGNATURE DISCLOSURE
From time to time, Motorola Solutions, Inc. (we, us or Company) may be required by law to
provide to you certain written notices or disclosures. Described below are the terms and
conditions for providing to you such notices and disclosures electronically through the DocuSign
system. Please read the information below carefully and thoroughly, and if you can access this
information electronically to your satisfaction and agree to this Electronic Record and Signature
Disclosure (ERSD), please confirm your agreement by selecting the check-box next to ‘I agree to
use electronic records and signatures’ before clicking ‘CONTINUE’ within the DocuSign
system.
Getting paper copies
At any time, you may request from us a paper copy of any record provided or made available
electronically to you by us. You will have the ability to download and print documents we send
to you through the DocuSign system during and immediately after the signing session and, if you
elect to create a DocuSign account, you may access the documents for a limited period of time
(usually 30 days) after such documents are first sent to you. After such time, if you wish for us to
send you paper copies of any such documents from our office to you, you will be charged a
$0.00 per-page fee. You may request delivery of such paper copies from us by following the
procedure described below.
Withdrawing your consent
If you decide to receive notices and disclosures from us electronically, you may at any time
change your mind and tell us that thereafter you want to receive required notices and disclosures
only in paper format. How you must inform us of your decision to receive future notices and
disclosure in paper format and withdraw your consent to receive notices and disclosures
electronically is described below.
Consequences of changing your mind
If you elect to receive required notices and disclosures only in paper format, it will slow the
speed at which we can complete certain steps in transactions with you and delivering services to
you because we will need first to send the required notices or disclosures to you in paper format,
and then wait until we receive back from you your acknowledgment of your receipt of such
paper notices or disclosures. Further, you will no longer be able to use the DocuSign system to
receive required notices and consents electronically from us or to sign electronically documents
from us.
All notices and disclosures will be sent to you electronically
Unless you tell us otherwise in accordance with the procedures described herein, we will provide
electronically to you through the DocuSign system all required notices, disclosures,
authorizations, acknowledgements, and other documents that are required to be provided or made
available to you during the course of our relationship with you. To reduce the chance of you
inadvertently not receiving any notice or disclosure, we prefer to provide all of the required
notices and disclosures to you by the same method and to the same address that you have given
us. Thus, you can receive all the disclosures and notices electronically or in paper format through
the paper mail delivery system. If you do not agree with this process, please let us know as
described below. Please also see the paragraph immediately above that describes the
consequences of your electing not to receive delivery of the notices and disclosures
electronically from us.
How to contact Motorola Solutions, Inc.:
You may contact us to let us know of your changes as to how we may contact you electronically,
to request paper copies of certain information from us, and to withdraw your prior consent to
receive notices and disclosures electronically as follows:
To contact us by email send messages to: bryan.kurzynski@motorolasolutions.com
To advise Motorola Solutions, Inc. of your new email address
To let us know of a change in your email address where we should send notices and disclosures
electronically to you, you must send an email message to us
at bryan.kurzynski@motorolasolutions.com and in the body of such request you must state: your
previous email address, your new email address. We do not require any other information from
you to change your email address.
If you created a DocuSign account, you may update it with your new email address through your
account preferences.
To request paper copies from Motorola Solutions, Inc.
To request delivery from us of paper copies of the notices and disclosures previously provided
by us to you electronically, you must send us an email
to bryan.kurzynski@motorolasolutions.com and in the body of such request you must state your
email address, full name, mailing address, and telephone number. We will bill you for any fees at
that time, if any.
To withdraw your consent with Motorola Solutions, Inc.
To inform us that you no longer wish to receive future notices and disclosures in electronic
format you may:
i. decline to sign a document from within your signing session, and on the subsequent page,
select the check-box indicating you wish to withdraw your consent, or you may;
ii. send us an email to bryan.kurzynski@motorolasolutions.com and in the body of such request
you must state your email, full name, mailing address, and telephone number. We do not need
any other information from you to withdraw consent.. The consequences of your withdrawing
consent for online documents will be that transactions may take a longer time to process..
Required hardware and software
The minimum system requirements for using the DocuSign system may change over time. The
current system requirements are found here: https://support.docusign.com/guides/signer-guide-
signing-system-requirements.
Acknowledging your access and consent to receive and sign documents electronically
To confirm to us that you can access this information electronically, which will be similar to
other electronic notices and disclosures that we will provide to you, please confirm that you have
read this ERSD, and (i) that you are able to print on paper or electronically save this ERSD for
your future reference and access; or (ii) that you are able to email this ERSD to an email address
where you will be able to print on paper or save it for your future reference and access. Further,
if you consent to receiving notices and disclosures exclusively in electronic format as described
herein, then select the check-box next to ‘I agree to use electronic records and signatures’ before
clicking ‘CONTINUE’ within the DocuSign system.
By selecting the check-box next to ‘I agree to use electronic records and signatures’, you confirm
that:
x
You can access and read this Electronic Record and Signature Disclosure; and
x
You can print on paper this Electronic Record and Signature Disclosure, or save or send
this Electronic Record and Disclosure to a location where you can print it, for future
reference and access; and
x
Until or unless you notify Motorola Solutions, Inc. as described above, you consent to
receive exclusively through electronic means all notices, disclosures, authorizations,
acknowledgements, and other documents that are required to be provided or made
available to you by Motorola Solutions, Inc. during the course of your relationship with
Motorola Solutions, Inc..