Request for Proposal On Replacement Public Safety Software ...

Request for Proposal On Replacement

Public Safety Software For Portage County & Surrounding Agencies

Proposal # 2020-01

Issued by: Portage County

Purchasing Department

Proposals must be submitted No later than 2 PM Thursday, March 19, 2020 to:

Portage County Purchasing

1462 Strongs Ave Stevens Point WI 54481

LATE PROPOSALS WILL BE REJECTED There will not be a public opening for this Proposal

For further information regarding this RFP contact Christopher Schultz

At (715) 346-1393 Email: [email protected]

Issued: Tuesday, February 4, 2020

1. General Information ............................................................................................................................. 4

1.1. Introduction and Purpose ............................................................................................................. 4

1.2. Definitions ..................................................................................................................................... 4

1.3. Current Operations, Software and Hardware Environment ......................................................... 4

1.4. Scope- ............................................................................................................................................ 7

1.5. Clarifications and/or Revisions to this RFP ................................................................................... 7

1.6. Calendar of Events ........................................................................................................................ 8

1.7. Contract Term ............................................................................................................................... 8

2. Preparing and Submitting a Proposal ................................................................................................... 8

2.1. General Instructions ...................................................................................................................... 8

2.2. Incurring Costs .............................................................................................................................. 8

2.3. Submitting Proposals .................................................................................................................... 8

2.4. Proposal Organization and Format ............................................................................................... 9

2.5. Multiple Proposals ........................................................................................................................ 9

2.6. Withdrawal of Proposals ............................................................................................................... 9

3. Proposal Selection and Award Process ............................................................................................... 10

3.1. Evaluation Committee ................................................................................................................ 10

3.2. Preliminary Evaluation ................................................................................................................ 10

3.3. Right to reject proposals ............................................................................................................. 10

3.4. Proposal Scoring .......................................................................................................................... 10

3.5. Evaluation Criteria ....................................................................................................................... 10

3.6. Interviews/Presentations and/or Site Visits- .............................................................................. 10

3.7. Final Evaluation ........................................................................................................................... 11

3.8. Award and Final Offers ............................................................................................................... 11

3.9. Notification of Intent to Award ................................................................................................... 11

3.10. Appeals Process .......................................................................................................................... 11

3.11. Negotiate Contract Terms ........................................................................................................... 11

4. Requirements ...................................................................................................................................... 11

4.1. Mandatory Requirements ........................................................................................................... 11

4.2. Contract Requirements ............................................................................................................... 12

5. Proposer Information and Solutions ................................................................................................... 17

5.1. Proposer References ................................................................................................................... 17

5.2. Organization Capabilities ............................................................................................................ 17

5.3. Staff Qualifications ...................................................................................................................... 17

5.4. Hardware and Software System Overview: ................................................................................ 17

5.5. Implementation & Training- ....................................................................................................... 17

5.6. User Licenses ............................................................................................................................... 18

5.7. Warranty, Maintenance, and Support- ....................................................................................... 18

5.8. Status Reports, Testing, and Final Acceptance- .......................................................................... 18

6. Cost Proposal ...................................................................................................................................... 19

6.1. General Instructions for the Cost Proposal and how it will be Scored ....................................... 19

6.2. Format for Submitting Cost Proposal. ........................................................................................ 19

6.3. Fixed Price Period ........................................................................................................................ 19

6.4. Payment-Payments shall be made as follows: ............................................................................ 19

Attachment A- Signature and Authority Affidavit Form Page 20 Attachment B- References Page 21 Attachment C- Designation of Confidential & Proprietary Info Form Page 22 Attachment D- Mandatory Requirements Page 23 Attachment E- Functional Specifications Page 24 Attachment F- Standard Terms and Conditions Page 213 Attachment G- Cost Proposal Page 216

Portage County Wisconsin RFP #2020-01 of 220

1. General Information

1.1. Introduction and Purpose

Portage County is seeking proposals for replacement of the current multi-jurisdictional public safety software system (s) utilized by Portage County, The City of Stevens Point, The Village of Plover, and The University of Wisconsin-Stevens Point, hereinafter referred to as “Requesting Agencies”. The replacement system will include, at a minimum, a Computer Aided Dispatch System (CAD), a Records Management System (RMS), a Field Based Mobile Reporting System (FBR), a Jail Management System (JMS), and a Mobile Data Computer System (MDC). The successful vendor will provide a system whereas all base components are supplied by a single vendor, integrated with minimal utilization of third-party interfaces to meet Portage County’s requirements. The Requesting Agencies are seeking to replace its existing public safety systems. The Requesting Agencies are looking for a contemporary, completely integrated solution that is one application, with one database, provided by one vendor. The public safety software system should allow for customizable information sharing definable by security permission between the Requesting Agencies. In addition, the Requesting Agencies would like the public safety software system vendor to not only provide, but to also maintain the software and hardware under the vendor’s maintenance and service agreement. The County of Portage as represented by the Purchasing Department intends to use the results of this Request for Proposal (RFP) to award a contract for the above listed project. The contract administrator will be determined at the time of the contract award. Retain a copy of these proposal documents for your files. Should you receive an award, these documents become your contract terms and conditions.

Contract Execution: Portage County utilizes a web based electronic signature program (DocuSign) for the execution of contracts that do not require notarization. By submitting your proposal, you are agreeing to the use of this program to sign documents should you receive an award. There is no cost to the proposer associated with this process.

1.2. Definitions

The following definitions are used throughout the RFP: CAD-Computer Aided Dispatch System Contractor means proposer awarded the contract. County means the County of Portage in Wisconsin. FBR-Field Based Reporting System JMS-Jails Management System MDC-Mobile Data Computer System Proposer/Vendor/Bidder means a company or individual submitting a proposal in response to this RFP. Purchasing means the County of Portage Purchasing Department. RFP means Request for Proposal. RMS-Record Management System State means the State of Wisconsin. VendorNet means the State of Wisconsin’s electronic purchasing information system.

1.3. Current Operations, Software and Hardware Environment The Portage County Sheriff’s Office, Portage County Communications Center, Portage County Jail, the Plover Police Department, and the Stevens Point Police Department currently contract with the Public Safety software vendor, Tritech Software Systems (formerly VisonAir). The following applications are currently in


use: VisionCAD – Computer Aided Dispatch (CAD), VisionMobile – Mobile Data Computer System (Mobile), Inform FBR – Field Based Reporting (FBR), Inform RMS -Records Management System (RMS), Inform Jail – Jail Management System, and Vision Inform and TriTech IQ for web-based queries. Portage County Dispatch is the PSAP for all currently connected agencies, thus sharing and interfacing data from the CAD system to all other applications in the TriTech environment. The Portage County Communications Center uses Geolynx Mapping System which integrates with CAD, both of which were implemented in 2007. CAD and Mobile were implemented in 2007, RMS and Jail were implemented in 2008. Portage County went live with FBR in 2012 while the Village of Plover PD implemented FBR in 2016. The Stevens Point Police Department migrated to use Tritech Software Systems in 2013. The Portage Count Sheriff’s Office uses custom programs developed on the iseries for Civil Process entry and reporting. The iseries is also used to manage employee data and to search legacy records prior to the Tritech Software Systems implementation in 2008. The Medical Examiner has been using iseries to manage records since 1994. Participating entities gain access application data via network trusts that have been established between the agencies. Mobile connectivity is allowed through a VPN connection using NetMotion Mobility software. The applications are hosted on SQL servers in a virtual environment provided and supported by Portage County. Servers are backed up nightly to an offsite Veem repository. There is currently not a real time redundancy site for critical applications, but Portage County is in the process of creating a secondary Hot/Hot Disaster Recovery environment by 2021. In addition to the above environment, legacy records not converted to TriTech during that implementation are maintained on an iSeries server using RPG code. This includes the current processing of Civil Process and Sheriff Sales. While we will continue to maintain these legacy records, we do not intend to maintain a secondary legacy system with our current records. All data currently stored in the TriTech environment needs to convert to the next Public Safety software chosen. The University of Wisconsin, Stevens Point (UWSP) uses SLEET as their Records Management System and FBR Reports are entered in templates on Microsoft Word. SLEET was implemented in 2002.

Portage County Sheriff & EMS

Description Details

Population served 70,474 (Includes all other Jurisdictions

Number of sworn officers 48

Total number of full-time employees (sworn and non-sworn) 108

Maximum number of concurrent users 47 (includes 7 EMS)

Average number of concurrent users 33 (Includes 3 EMS)

Total number of employees working at the jail (this number is included in both the sworn and non-sworn employee counts)

32

Number of jail beds 92

Number of full dispatch stations 5


Description Details

Total number of dispatchers (this number is included in both the sworn and non-sworn employee counts)

16

Number of dispatchers typically on-call per shift 4

Number of Public Safety Answering Points (PSAP) 5

Number of police agencies dispatched 4

Number of mobile units 27 (includes EMS)

Number of RMS data entry stations 15

Number of Stations Using FBR 30

City of Stevens Point Police Department

Description Details

Population served 26,293



Maximum number of concurrent users 25

Average number of concurrent users 10-15

Number of mobile units 12


Number of FBR Stations 37

City of Stevens Point Fire

Description Details

Population served 26,200



Average number of concurrent users 8-10



Village of Plover Police

Description Details Population served 13,298




Average number of concurrent users 13


Number of RMS data entry stations/Stations Using FBR 5/19


University of Wisconsin-Stevens Point Police

Description Details Population served 9,000




Average number of concurrent users 6


Number of RMS data entry stations/Stations Using FBR 2/8

1.4. Scope- See Requirements and Specifications (Section 4 and 5), Functional Specifications (Attachment E), and Cost Proposal Forms (Attachment G) for the minimum acceptable specifications for the products and services desired. Any estimated item quantities identified in this document are for proposal purposes only. The County does not guarantee to purchase any specific quantity or dollar amount. This contract must not be construed as mandatory upon any County, State agency or municipality. The County reserves the right to issue separate proposals when deemed in the best interest of the County. The County reserves the right to negotiate with any contracted vendor(s) to establish additional discounts and/or lower prices for products determined to meet the requirements of a County-led initiative to set product standards. Contracted vendor may be asked to provide new, lower prices for these standard products and configurations for a limited, fixed term, to fall within the term of the contract resulting from this Request for Proposal.

1.5. Clarifications and/or Revisions to this RFP Portage County Purchasing is the sole point of contact for the County during the selection process. Contact with anyone else involved with this process without the prior authorization of Purchasing may result in the disqualification of your proposal. Proposers are expected to raise any questions, noted errors, discrepancies, ambiguities, exceptions, additions, or deficiencies they have concerning this proposal in writing through email by 2 PM Thursday, February 18, 2020, to: Chris Schultz, Purchasing, Email: [email protected] If a proposer discovers any significant ambiguity, error, conflict, discrepancy, omission, or other deficiency in this proposal after the above date, it shall immediately notify the above named individual of such error and request modification or clarification of the proposal document before the proposal opening date. If a proposer fails to notify the County prior to the proposal due date of any condition stated above that reasonably should have been known to the proposer, and if a contract is awarded to that proposer, the proposer shall not be entitled to additional compensation or time by reason of the error or its correction. Revisions to this request for proposal or answers to questions will be made only by an official written addendum issued by Purchasing. Addenda will be posted on VendorNet and on the Portage County Website. Proposers are responsible for checking these websites for any addenda before submitting a proposal. Failure to acknowledge addenda may disqualify your proposal. https://vendornet.wi.gov http://www.co.portage.wi.us

http://www.co.portage.wi.us/


1.6. Calendar of Events Listed below are specific and estimated dates and times of actions related to this Request for Proposal. The actions with specific dates must be completed as indicated unless otherwise changed by the County. In the event that the County finds it necessary to change any of the specific dates and times, it will do so by issuing addenda to this RFP. There may or may not be a formal notification issued for changes of the estimated dates and times.

DATE EVENT

Tues, Feb 4, 2020 Bid 2020-01 Public Safety Software Release

Tues, Feb 18, 2020 Last Day to submit questions or request clarifications by 2PM

Thu, Feb 27, 2020 Questions and Any Addenda posted to https://vendornet.wi.gov/ and http://www.co.portage.wi.us

Thu, Mar 19, 2020 Proposals due at or before 2:00 p.m.

Early May Interviews/Presentations Demonstration (Week of May 4?? )

Mid May Reevaluation

May-June Notification of intent to award sent proposers (estimated)

July-August Contract Initiated Contract award (estimated)

Late 2020-Early 2021 Implementation, UAT, Evaluation, Contract start date (estimated)

1.7. Contract Term The contract shall be effective on the date indicated on the purchase order or contract and shall continue for Three (3) years from that date. By mutual agreement of the agency and the contractor, the contract may be renewed up to Three (3) additional two-year periods.

2. Preparing and Submitting a Proposal

2.1. General Instructions The evaluation and selection of a contractor will be based on the information submitted in the proposal plus references and any required on-site visits, interviews/presentations or demonstrations. Proposers should respond clearly and completely to all requirements. Failure to respond to each of the requirements in the RFP may be the basis for rejecting a proposal. Elaborate proposals (e.g. expensive artwork), beyond that sufficient to present a complete and effective proposal, are not necessary or desired. The County encourages all proposers to print their submission double-sided to save paper.

2.2. Incurring Costs The County is not liable for any cost incurred by proposers in replying to this RFP.

2.3. Submitting Proposals Proposers must submit, in a sealed package, One Original (identify) PLUS six (6) identical copies of all materials required for acceptance of their proposal on or before 2:00 p.m. Thursday, March 19, 2020 to:

Portage County Purchasing 1462 Strongs Ave Stevens Point, WI 54481

https://vendornet.wi.gov/

http://www.co.portage.wi.us/


All proposals must be received by the Purchasing Department by the stated time. Late proposals will not be accepted. Receipt of the proposal by the U.S. mail system does not constitute receipt of the proposal by Purchasing. The County does not accept facsimile machine or email submitted proposals. All proposals must be packaged, sealed, and show the following information on the outside of the package:

Proposer's Name and Address Request for Proposal Title Request for Proposal Number Proposal Due Date

COST PROPOSAL: Submit Original plus one (1) identical copy of Attachment G. Seal in an envelope and submit within the proposal package. The outside of the envelope should clearly state “Cost Proposal” and the name of proposer.

2.4. Proposal Organization and Format Proposal should be typed and submitted on 8.5” by 11” paper bound securely with page numbers clearly indicated. Proposers responding to this RFP must comply with the following format requirements: Tab 1 - COVER LETTER, RFP SIGNATURE PAGES: Include here any cover letter, Attachment A - RFP Signature and Authority Affidavit Form, any addenda signature pages, and Attachment C - Designation of Confidential & Proprietary Information Form. The Signature and Authority Affidavit submitted in response to this RFP must be signed by the person in the Proposer's organization who is responsible for the decision as to the prices being offered or by a person who has been authorized in writing to act as agent for the person responsible for the decision on prices and services. Failure to provide these forms and information with your bid submittal may disqualify your proposal. Tab 2 – MANDATORY REQUIREMENTS: Include Attachment D Mandatory Requirements, W-9, and Certificate of Insurance. Tab 3 – REFERENCES, CONTRACT REQUIRMENT, RESPONSE TO PROPOSER INFORMATION, FUNCTIONAL QUESTION & SPECIFICATIONS: Attachment B-References (5.1), Company overview (5.2), Staff Qualifications (5.3), and solutions to sections 5.4-5.8 that also address all the contract requirements from sections 4.2.1-4.2.12. Please match the sequence and numbered as they appear in section 5 of this RFP. Finally followed by all the question and requirement charts in Attachment E. Last Tab Separate Envelope - COST PROPOSAL: Provide cost information as detailed in Section 6 in this RFP. Include all the charts filled out and documented from Attachment G. All costs, as requested, for furnishing the product(s) and/or service(s) must be included in this proposal. The cost proposal must NOT be listed in any other part of the proposal response.

2.5. Multiple Proposals Multiple proposals from a proposer will be permissible; however, each proposal must conform fully to the requirements for proposal submission. Each such proposal must be separately submitted and labeled as Proposal #1, Proposal #2, etc. on each page included in the response.

2.6. Withdrawal of Proposals Proposals shall be irrevocable until contract award unless the proposal is withdrawn. Proposers may withdraw a proposal, in writing, at any time up to the proposal due date and time or upon expiration of 240


days after the due date and time. The written withdrawal notice must be received by Purchasing. The notice must be signed by an authorized representative of the proposer. If a previously submitted proposal is withdrawn before the proposal due date and time, the proposer may submit another proposal at any time up to the proposal due date and time.

3. Proposal Selection and Award Process

3.1. Evaluation Committee The County’s evaluation committee will consist of members who have been selected because of their special expertise and knowledge of the service(s) and/or product(s) that are the subject of this RFP. Proposers may not contact members of the evaluation committee except at the request of the Purchasing Department.

3.2. Preliminary Evaluation The proposals will be initially reviewed to determine if mandatory requirements are met. Failure to meet mandatory requirements may result in the proposal being rejected. In the event all proposers do not meet one or more of the mandatory requirements, the County reserves the right to continue the evaluation of the proposals that most closely meet the mandatory requirements of this RFP.

3.3. Right to reject proposals The County reserves the right to reject any and all proposals.

3.4. Proposal Scoring Accepted proposals will be reviewed by an evaluation committee and scored against the stated criteria. The committee may review references, request interviews/presentations, conduct demonstrations and/or conduct on-site visits. The resulting information will be used to score the proposals. The evaluation committee's scoring will be tabulated, and proposals ranked based on the numerical scores received.

3.5. Evaluation Criteria The proposals will be scored using the following criteria:

Description Points

Company & Organization Capabilities (5.2) 75 Points

Staff Qualifications (5.3) 75 Points

Proposal Response (5.4-5.8) 300 Points

Functional Specifications (Questions & Requirements Attachment E) 300 Points

Cost Proposal 250 Points

Total 1000 Points

3.6. Interviews/Presentations and/or Site Visits- Top-scoring proposers, based on the evaluation of the written proposal, will be required to have interviews/presentations to support and clarify their proposals, if requested by the County. The County will make every reasonable attempt to schedule the interview/presentation within the date range specified in the Calendar of Events. Failure of a proposer to complete a scheduled interview/presentation to the County may result in rejection of that proposer's proposal. The County may conduct site visits of proposer and/or references’ facilities to clarify or confirm proposal information.


3.7. Final Evaluation

Upon completion of any interviews/presentations and/or demonstrations by proposers, the County's evaluation team will review their evaluations and adjust the scores based on the information obtained in the interview/presentation, demonstration, possible reference checks, and any other pertinent proposer information.

3.8. Award and Final Offers Award will be granted in one of two ways. The award may be granted to the highest scoring responsive and responsible proposer after the original evaluation process is complete. Alternatively, the highest proposer or proposers may be requested to submit best and final offers. If the County requests best and final offers, they will be evaluated against the stated criteria, scored, and ranked by the evaluation committee. The award will then be granted to the highest scoring proposer following that process. However, a proposer should not expect that the County will request a best and final offer.

3.9. Notification of Intent to Award All proposers who respond to this RFP will be notified in writing of the County's intent to award the contract(s) as a result of this RFP.

3.10. Appeals Process Notices of intent to protest and protests must be made in writing. Protestors should make their protests as specific as possible and should identify Wisconsin Statutes or Portage County Ordinance provisions that are alleged to have been violated. The written notice of intent to protest the intent to award a contract must be filed with Chris Schultz, Procurement Director, Portage County Wisconsin, 1462 Strongs Ave, Stevens Point, WI 54481, and received in his office no later than five (5) working days after the notice of intent to award is issued. The written protest must be received in his office no later than ten (10) working days after the notice of intent to award is issued. The decision of the Procurement Director may be appealed to the Corporation Counsel Office within (5) working days of issuance. The appeal must allege a violation of a Wisconsin Statute or a Portage County Ordinance provision.

3.11. Negotiate Contract Terms The County reserves the right to negotiate the terms of the contract, including the award amount, with the selected proposer prior to entering into a contract. If contract negotiations cannot be concluded successfully with the highest scoring proposer, the County may negotiate a contract with the next highest scoring proposer.

4. Requirements

4.1. Mandatory Requirements Submit response using Attachment D Mandatory Requirements under Tab 2 of proposal - see section 2.4 for proposal submittal format. The following requirement(s) are mandatory, and the proposer must satisfy them as a pass/fail pre-screening requirement. Any proposal submitted not in compliance with mandatory requirements may be rejected and not evaluated or scored. 4.1.1. Vendor Background: Proposing vendors must have a minimum of ten years of experience

performing the work as described in the RFP. Proposing vendors must have minimum of ten (10)


clients with integrated, multi-jurisdiction, multi-discipline Public Safety Software Systems operating on the same version and platform as the system proposed.

4.1.2. Integrated System: Proposer must provide fully-integrated comprehensive software to satisfy all Public Safety Software System computer needs from a single vendor.

4.1.3. Single Point of Contact: The single prime Vendor will be the single point of contact for all

communications regarding the project and will be responsible for the success of the complete solution. The single prime Vendor will be the single point of contact for warranty, support and maintenance issues throughout the lifecycle of the project as well as for support of continued operation through the terms of the negotiated contract.

4.1.4. Training: Vendor must offer online and hands on training for all users on a yearly basis, including having an established training within the Midwest or State of Wisconsin.

4.1.5. Proof of Insurance-The contractor performing services for Portage County shall: Maintain worker's compensation insurance as required by Wisconsin Statutes, for all employees

engaged in the work.

Maintain commercial liability, bodily injury and property damage insurance against any claim(s) which might occur in carrying out this agreement/contract. Minimum coverage shall be one million dollars ($1,000,000) liability for bodily injury and property damage including products liability and completed operations.

The county reserves the right to require higher or lower limits where warranted.

4.1.6. Work in US-All work, training, customer support, storage of data, and services must be performed in the United States.

4.2. Contract Requirements The awarded contractor is expected to fulfill the following contract requirements 4.2.1. Have a single comprehensive system where all modules and subsections are completely integrated.

4.2.2. Increase Officer, Medical, and Fire personnel safety

4.2.3. Provide easy to use analysis tools that support individual and Department accountability and

provide statistics that will support grant writing and funding activities

4.2.4. Overall Hardware and Software Requirements- The proposed system shall be the manufacturer's most recent version available for installation that meets the requirements of this RFP. Bidders shall describe the model proposed and its associated components. Bidders shall include a configuration diagram as a graphical representation of the system to be provided. Bidders shall furnish detailed minimum and recommended specifications regarding all hardware and related components, including operating systems, required for the installation of a complete, working system.


Vendors must describe the availability architecture of the proposed solution, including database mirroring and failover, network load balancing, exception handling, system logging, and system management.

Vendors must describe the recommended minimum and optimum specifications – including the redundant and fault-tolerant capabilities – for the system hardware that the County will purchase, including servers, storage, power, and networking equipment.

4.2.5. Specific Software Systems-The following paragraphs describe the systems that are expected to be included in the Proposer’s solution: Computer Aided Dispatch (CAD) – Portage County and Requesting Agencies desire a Law Enforcement and Fire/EMS CAD application integrated with other System Application Components and meeting the functional and performance requirements identified in this RFP. The CAD solution should also include real-time mapping, Automated Vehicle Location (AVL), and support the identified interfaces. Additionally, the CAD configuration must address system redundancy factors, and incorporate backup, failover and recovery solutions. The training environment must mirror the live environment. Mobile Data Computer System (MDC) – Portage County and Requesting Agencies desire a Mobile application with real-time mobile mapping and AVL functionality. The Mobile application must be fully integrated with CAD and the proposed Automated Reporting System to ensure a seamless transition from incident management to case reporting, and to allow field access to hazards, premises information, and call details for situational awareness. Law Enforcement Records Management Systems (RMS) – A Law Enforcement Records Management System is requested that can provide a broad range of functionality including tracking arrests, training, personnel, civil document tracking, and property/evidence data. The system should have tools to assist with data integrity and accuracy, and users should be able to access multiple databases from a single query, as well as easily develop reports and analyze data. Further, as the RMS will be used by several law enforcement agencies, it must support a multi-jurisdictional configuration Field Based Reporting System (FBR) – The Field Based Reporting application should allow field users to complete law enforcement reports in either a mobile or a desktop environment and submit those reports electronically to the RMS. At a minimum, the FBR software should provide for the pre-population of report forms, member agency-defined workflow for online routing of reports, supervisor receipt and review of reports, editing and re-routing of reports, case assignment/management and automatic report distribution. Like RMS, FBR will be used by several law enforcement agencies; therefore, it must also support a multi-jurisdictional configuration. Jail Management System (JMS) – Portage County and Requesting Agencies desire a JMS to manage bookings and inmate housing, tracking, and incidents as well as support other duties required as part of corrections operations.

Vendors must describe the failover process of the proposed solution, including the estimated time for the failover process to complete. The proposal will include the capability of remote workstations that are web-based and will include a description of the solution for remote web-based access


4.2.6. Data Migration

Complete legacy data migration will be required, from the current TriTech systems to the selected Vendor’s system, including CAD, RMS, and Jail. This also includes photo and document attachments within the system. The County understands that intermediate steps may be required. This function includes system tables and historic data. The County expects that data migration will be completed prior to go-live.

System table data migration will occur prior to the start of system configuration.

The County expects that the migrated data will be available to all workstations and integrated with the selected system application.

4.2.7. Required Documentation. The bidder will provide a network diagram with the proposal for the proposed system. Prior to final system acceptance, the successful Bidder will provide an as-built network diagram for the installed system components. The successful Bidder will provide a complete database schema and data description for all data elements for all components and data sets. The successful Bidder will provide a complete set of application User’s Guides prior to the start of User training. The successful Bidder will provide a complete set of system Administrative guides prior to the start of Administrator training. The final copies of User and Administration guide will be provided prior to system go-live. The successful bidder will provide a complete set of interface operation and administration guides prior to Final System Acceptance. The successful bidder will provide all documentation and licenses that came with all software purchased for use in this system, e.g., third-party and operating system licenses. The successful bidder will provide a complete set of operation and administration guides related to backup and recovery processes prior to Final System Acceptance. All documentation and reference materials are updated with each version release. The successful bidder will provide a complete set of release notes and resulting changes to documentations prior to each system version update.

4.2.8. Implementation & Training Requirements Portage County expects that the selected vendor will provide customized training to each agency regarding the use and configuration of the system and associated interfaces. The training will include operational and functional training to all users from each agency; train-the trainer sessions


selected from each agency; and administrative training to each agency’s administrative staff, which covers all aspects of operating and managing systems. All vendor provided training will be completed prior to system go-live and on the application version to be implemented.

4.2.9. Warranty The following requirements are applicable to all maintenance and repair services supplied by Vendor or Vendor’s subcontractors, both under and outside of warranty. Vendors shall warrant that all components supplied by the Vendor and the integration thereof will be free from defects in material, design and workmanship for the warranty and maintenance period purchased. Vendors shall provide a minimum one-year warranty period from the date of final system acceptance. Vendors shall warrant that all components supplied will be free from defects in material, design and workmanship for the warranty period and any extended warranty or maintenance period purchased. This warranty shall cover all parts, labor and travel necessary to affect a repair related to any and all components supplied under this contract.

During the warranty period, Vendors must provide support services 24 hours a day and seven days a week (24 x 7) for critical applications. This service must be available any hour of the day. A Web-based trouble reporting system shall be available for non-critical issues. Vendors or their subcontractors must have the ability to access the system remotely using the County’s secure VPN facility for troubleshooting and to perform system diagnostics. Vendors also shall provide a detailed statement of warranty exclusions. The County reserves the right to reject any proposal based upon stated exclusion of warranties.

4.2.10. Maintenance and Support

Vendors must provide support services 24 x 7 for critical applications. This service must be available any hour of the day. Portage County expects that a Web-based trouble reporting system will be available for non-critical issues and is the preferred method for reporting non-critical issues. Vendors or their subcontractors must have the ability to access the system remotely using the County’s secure VPN facility for troubleshooting and to perform system diagnostics. For all critical system problems reported, Vendors shall provide an immediate response to the incident and shall initiate corrective action no longer than 30 minutes from time of notification. Within two hours of any major failure, reporting personnel must be either onsite or logged into the system to analyze the cause of the problem and to effect corrective action. Equipment or components required onsite for emergency maintenance must be specified and provided. In all instances of a critical system failure, the Vendor must affect corrective action within one hour of problem reporting or escalate the problem to their senior support staff for their immediate resolution, at no added cost to the County.

Vendors shall warrant that the system supplied under any contract will be operational and available 99.999 percent of the time during the warranty and support periods. The warranty period or support period will be extended on a day-for-day basis for each day the system performance falls below this level.


The cost of the support and maintenance periods will be itemized on the Cost Data Forms (Attachment G). The County reserves the right to purchase one or more additional years of support. The proposed system must include, at a minimum, a first-year warranty, and specify the availability of a multi-year support and maintenance agreements. Operating software updates for corrections, enhancements and refinements to purchased capabilities shall be provided by the Vendor as part of the price for maintenance for those years in which the County has purchased maintenance from the Vendor. The software components purchased by the Vendor must be purchased in the name of the County, and the licenses transferred to the County at system acceptance. There shall be no system downtime for routine maintenance or system backups. Vendors must explain in detail any required (scheduled) system processes that may require downtime.

The cost of software upgrades should be included in the annual maintenance plan.

The County reserves the right to accept or reject any proposed services, Vendors, and/or the use of any proposed service facilities, at the sole discretion of the County.

4.2.11. Project Status

During the project, until final acceptance, the proposer project manager will submit regular status reports covering the following:

• Progress

• Resources Expended

• Problems encountered

• Goals attained

• Project Status Calls and Meeting Summaries

4.2.12. Testing and Final Acceptance- Portage County and Requesting Agencies shall require the vendor to conduct a final acceptance test in conjunction with Portage County representatives. The purpose of acceptance test shall be to demonstrate to the satisfaction of Portage County and Requesting Agencies that all components of the software system(s) function as specified. Final acceptance of the system if based upon the system operating as expected in the anticipated operated environment. The vendor, in cooperation with the Requesting Agencies, shall perform testing as described below: 1. No less than (45) days prior to the start of final testing the vendor will provide to Portage County a

detailed test plan outlining expected results and how each software component will be tested to ensure full operational functionality.

2. Within 14 days after completion of final testing the vendor will provide a report outlining the results of the testing and a plan and timeline to remedy any deficiencies.

3. Testing shall include every component of every required system, including interfaces and any hardware provided by the vendor. Testing will also include all third-party interfaces utilized and ancillary program modules.

4. Portage County and Requesting Agencies will conduct a ninety (90) day operational test of the system. This test shall be compromised of normal, everyday utilization by the Requesting Agencies.


5. In the event of known software/hardware issues prior to testing, the vendor shall communicate the

issues and the planned remediation to Portage County.

5. Proposer Information and Solutions Submit response under Tab 3 of proposal - see section 2.4 for proposal submittal format.

5.1. Proposer References Proposer must supply references of three firms to which similar products/service have been provided within the past five years to a comparable sized institution or company. If contacted, all those references must verify that a high level of satisfaction was provided. Please try to include at least one reference from the State of Wisconsin

5.2. Organization Capabilities Provide a Company profile. Also include a description of the organization’s capabilities providing similar services to those required. Be specific and detail no more than three projects/contracts: description of work, dates, locations, challenges and results.

5.3. Staff Qualifications Identify key staff your organization/company will assign to fulfill the contract requirements. Detail who would be contract manager(s), etc. Provide a synopsis describing the educational and work experience for each of the key staff who would be assigned to the project/program. Detail the number of hours for each key staff member that you estimate will be needed to fulfill the contract requirements.

5.4. Hardware and Software System Overview-In addition to addressing the contract requirements from 4.2.1-4.2.7 in your response to this section please also include information pertaining to the below inquires:

5.4.1. Specify how may current public safety agencies have purchased the vendor’s software in the last 5

years, 10 years, etc. respectively.

5.4.2. Provide a detailed overview of the proposed system. Include a list of all proposed modules included in the system and identify if any are priced optional.

5.4.3. Describe the Database structure. Do all system modules query a single database? Describe the internal interfaces, if any, between proposed modules.

5.4.4. Describe how agency administrators establish security privileges and permissions within the system.

5.5. Implementation & Training- In addition to addressing the contract requirements from 4.2.8 in your response to this section please also include information pertaining to the below inquires:

5.5.1. Describe the typical implementation process for a project of this scope including the roles of key

members on the implementation team

5.5.2. Describe the vendor’s training services during implementation

5.5.3. Describe all vendor training services after implementation

5.5.4. Describe the methodology and schedule for data conversion from the current system


5.5.5. Provide a detailed list of documentation that will be provided to support the implementation and

use of the requested software and what formats it will be available in. Also provide brief descriptions of the what documentation is and what areas of the Requesting Agencies they are meant for.

5.6. User Licenses 5.6.1 Describe the proposed licensing structure (user, concurrent, site etc) and the number of proposed

licenses for each proposed component that requires a license.

5.6.2 Specify if there will ever be additional charges for workstation or mobile licenses as the agency

expands and more users are added to the system

5.6.3 Using agency-defined privileges, specify whether the requesting agencies will be able to grant

unlimited view-only licenses to outside departments, such as the District Attorney’s Office, without incurring

additional license fees

5.6.4 If outside agency view-only licenses are permitted, what is the term limit of such licenses prior to

having to purchase additional licensing?

5.7. Warranty, Maintenance, and Support- In addition to addressing the contract requirements from 4.2.9-4.2.10 in your response to this section please also include information pertaining to the below inquires:

5.7.1. Describe how Requesting Agencies receive new enhancements, releases. Indicate if the Requesting Agencies are required to update their system when a new enhancement is released.

5.7.2. When an enhancement becomes available, and an Agency elects to retain a previous release, define how long the vendor will provide maintenance for the original release.

5.7.3. Describe the vendor’s standard support services.

5.7.4. Describe in detail, the offered warranty and any available extended warranty. This description must include a description of support services and system upgrades to be provided. The names, addresses, telephone numbers and contact person for all service facilities must be identified in the proposal

5.7.5. Describe a detailed statement or warranty exclusions. Note: (Requesting Agencies reserve the right to reject any proposal based upon stated exclusions of warranties.)

5.7.6. Describe vendor’s support services and response time for critical system failure

5.8. Status Reports, Testing, and Final Acceptance- In addition to addressing the contract requirements from 4.2.11-4.2.12 in your response to this section please also include information pertaining to the below inquires:

5.8.1. Indicate how often and what formats the vendor uses to inform the Requesting Agencies of Status Reports and updates.

5.8.2. Indicate if the structure the county provided will work for testing and final acceptance. Please also indicate if you, the provider, has a set structure that is different for testing and final acceptance? If so, please provide your timetable and structure for that process.


6. Cost Proposal

6.1. General Instructions for the Cost Proposal and how it will be Scored All prices must be quoted in U.S. Dollars. Purchasing will score the cost proposals by prorating with the lowest cost proposal given the highest score. The formula is as follows: Calculation of points awarded to subsequent proposals will use the lowest dollar proposal amount as a constant numerator and the dollar amount of the firm being scored as the denominator. This number is then multiplied by the number of points given to the cost section of the RFP, resulting in the cost proposal score.

Lowest Cost Proposed Constant _ X Maximum Points Assigned to Cost = Score Other Proposed Cost

6.2. Format for Submitting Cost Proposal. Use Attachment G Cost Proposal. Submit one marked original plus one copy. Seal in an envelope and submit within the proposal package. The outside of the envelope should clearly state “Cost Proposal” and the name of proposer.

6.3. Fixed Price Period The awarded contractor must hold the accepted prices and/or costs for the entire contract period. The county is also requiring that you hold the prices firm on your bid for up to 240 days during the testing and implementation period of the software. Any adjustment to prices and/or costs at the beginning of a contract renewal period will be negotiated between the County and the Contractor.

6.4. Payment-Payments shall be made as follows: 25% After contract execution and approval of project plan 25% After delivery and installation of software solution 25% Upon Go-Live 25% After Final Acceptance, completion of outstanding issues (or an agreed upon plan for remediation) and delivery of documentation If the bidder has a structure different from above, they may include that as part of their cost proposal. This can then be negotiated at the time of contract acceptance and execution.


ATTACHMENT A SIGNATURE AND AUTHORITY AFFIDAVIT FORM

PROPOSING COMPANY NAME: _________________________________________________________ FEIN (Federal Employer ID Number) OR Social Security # (if Sole Proprietorship) __________________________________ ___________________________________ Address: __________________________________________________________________________ City _____________________________ State ________ Zip + 4 _______________________ Number of years in Business _______ Name the person to contact for questions concerning this proposal. Name ___________________________ Title ______________________________ Phone ( ) _______________________ Toll Free Phone ( ) __________________________ Fax ( ) _______________________ Email Address ___________________________

In signing this proposal, we also certify that we have not, either directly or indirectly, entered into any agreement or participated in any collusion or otherwise taken any action in restraint of free competition; that no attempt has been made to induce any other person or firm to submit or not to submit a proposal; that this proposal has been independently arrived at without collusion with any other proposer, competitor or potential competitor; that this proposal has not been knowingly disclosed prior to the opening to any other proposer or competitor; that the above statement is accurate under penalty of perjury. The undersigned, having familiarized themselves with the conditions affecting the cost of the work, having read completely the requirements, hereby proposes to perform everything required and to provide and furnish labor, materials, equipment, tools and all other services and supplies necessary to produce in a complete and workmanlike manner all of the materials or products described in the project relating to this proposal. I further certify that I have carefully examined the proposal documents and all terms herein, and site where the work is to be done and have no agreements to prevent the completion of said work. ______________________________________________ ___________________________ Signature Title _______________________________________________ ___________________________ Name (type or print) Date This firm herby acknowledges receipt / review of the following addendum(s) (If any)

Addendum #_____ Addendum #_____Addendum #_____Addendum #_____


ATTACHMENT B REFERENCES

Proposer: _______________________________________________________________________ Provide company name, address, contact person, telephone number, and appropriate information on the product(s) and/or service(s) provided to customers similar to those requested in this solicitation document. Potential subcontractors cannot be references. Any subcontractor arrangement for the completion of this work shall be listed on a separate page.

Company Name: _________________________________________________________________________ Address (include Zip + 4) ____________________________________________________________________ Contact Person: ____________________________________ Phone No. __________________________ E-Mail Address: __________________________________________________________________________ Product(s) Used and/or Service(s) Provided: ____________________________________________________





ATTACHMENT C DESIGNATION OF CONFIDENTIAL AND PROPRIETARY INFORMATION

The attached material submitted in response to Bid/Proposal # includes proprietary and confidential information which qualifies as a trade secret, as provided in s. 19.36(5), Wis. Stats., or is otherwise material that can be kept confidential under the Wisconsin Open Records Law. As such, we ask that certain pages, as indicated below, of this bid/proposal response be treated as confidential material and not be released without our written approval. Prices always become public information when bids/proposals are opened, and therefore cannot be kept confidential. Other information cannot be kept confidential unless it is a trade secret. Trade secret is defined in s. 134.90(1)(c), Wis. Stats. as follows: "Trade secret" means information, including a formula, pattern, compilation, program, device, method, technique or process to which all of the following apply:

1. The information derives independent economic value, actual or potential, from not being generally known to, and not being readily ascertainable by proper means by, other persons who can obtain economic value from its disclosure or use.

2. The information is the subject of efforts to maintain its secrecy that are reasonable under the circumstances. We request that the following pages not be released: Section Page # Topic __________________________________________________________________________________________________________ __________________________________________________________________________________________________________ __________________________________________________________________________________________________________ __________________________________________________________________________________________________________ __________________________________________________________________________________________________________ __________________________________________________________________________________________________________ IN THE EVENT THE DESIGNATION OF CONFIDENTIALITY OF THIS INFORMATION IS CHALLENGED, THE UNDERSIGNED HEREBY AGREES TO PROVIDE LEGAL COUNSEL OR OTHER NECESSARY ASSISTANCE TO DEFEND THE DESIGNATION OF CONFIDENTIALITY AND AGREES TO HOLD THE STATE HARMLESS FOR ANY COSTS OR DAMAGES ARISING OUT OF THE COUNTY'S AGREEING TO WITHHOLD THE MATERIALS. Failure to include this form in the bid/proposal response may mean that all information provided as part of the bid/proposal response will be open to examination and copying. The County considers other markings of confidential in the bid/proposal document to be insufficient. The undersigned agrees to hold the County harmless for any damages arising out of the release of any materials unless they are specifically identified above. Company Name ______________________________________________ Authorized Representative ______________________________________________

Signature

Authorized Representative ________________________________________________

Type or Print Date ___________________________________________


ATTACHMENT D MANDATORY REQUIREMENTS

Proposer: _______________________________________________________________________ Meet mandatory requirement 4.1.1? Vendor Background. Yes______ No_______ *Please provide your W-9 after this response sheet in your packet Meet mandatory requirement 4.1.2? Integrated System Yes______ No_______ Meet mandatory requirement 4.1.3? Single Point of Contact Yes______ No_______ Meet mandatory requirement 4.1.4? Training Yes______ No_______ Meet mandatory requirement 4.1.5? Proof of Insurance Yes______ No_______ **Please provide your Certificate of Insurance after this response sheet in your packet Meet mandatory requirement 4.1.6? Work done in United States Yes______ No_______


ATTACHMENT E FUNCTIONAL SPECIFICATIONS

E-1 Response Instructions

Portage County Public Safety Software Replacement RFP

Response Instructions Detailed functional requirements for the modules desired by Portage County are provided in the tabs throughout this workbook. The following codes should be used to indicate the level at which the proposed system meets the requirements. Each tab refers to the functionality requested of the identified module. Proposer must complete the workbook for all modules included in the response. For components not proposed, vendor should label the section as N/P.

The Priority column indicates where the functionality is considered Critical (C), Desirable (D) or Optional (O) by Portage County.

Code Response

M Proposed system meets or exceeds the requirement.

N Proposed system does meet requirement.

A Proposer recommends an alternative no-cost way to meet requirement. Proposer must provide an explanation in the "Comments" column as to how this would be accomplished.

C

Proposed system requires a custom software modification to comply with requirement but does not require third party software. Proposer must provide an explanation in the Comments column and list additional costs, cross-referencing the requirement, in the Cost Proposal.

T

Proposed system requires third party software to comply with requirement. Proposer must provide an explanation in the Comments column and list additional costs, cross-referencing the requirement, in the Cost Proposal. Within the Cost Proposal, the Third Party should be listed under the applicable section (for example, if a third party is required for CAD Mapping, it should be listed under the CAD Table in the Cost Proposal).

Enter the appropriate response code for each requirement. Where applicable and where requested, provide additional information that describes the way in which the proposed system fulfills the given requirement or how an alternative to the requirement will meet the needs of Portage County. Short responses may be provided in the "Comments" column, while longer answers may be provided on a separate page. Do not insert rows into any portion of the document or modify the functional requirements numbering or description.

Please respond to each requirement. Omitted responses will be evaluated as response codes of "N" (proposed system does not meet the requirement).


E-2 General System Functional Requirements E-2.1 Questions

Reporting Inquires

1 Do you provide any pre-written reports? Provide list.

2 What tool is used to develop reports?

E-2.2 Requirements

Portage County Publlic Safety Software Replacement RFP

Global Administration System Requirements

Priority Codes (C=Critical, D=Desireable, O=Optional)

Item #

Description of Requirement Priority Response Comments

1 Notifications

2 System should support "if", "then", "when" business rules for notifications throughout the system.

C

3 System should include system-wide business rules that allow authorized users to configure notification scenarios for users and groups.

C

4

System should include system-wide business rules that allow authorized users and groups to be notified via multiple communication channels including internal system messaging, email, and SMS.

C

5 System should warn users of unfinished taskes when they attempt to log out.

C

6 Audit Trails

7 Ability to date and time stamp all:

8 System transactions C

9 User transactions C

10 Ability to create a security group defining who has audit trail access permissions.

C

11 Ability to prevent the override of time stamps and record the attempt in the audit trail.

C

12 Ability to maintain an audit trail at the following levels:

13 User C

14 Field C

15 Record C

16 Module C


17 Application C

18 Ability to log all actions including, but not limited to :

19 Adds C

20 Changes C

21 Deletions C

22 Updates C

23 Errors D

24 Security violations C

25 Inquiries to all internal and external systems C

26 Views C

27 Print D

28 Override C

29 Successful sign-on C

30 Unsuccessful sign-on attempts C

31 Password Changes C

30 Create audit record each time an attached audio or video is exported from the system.

C

31 Ability for Agency to configure which transactions are recorded in the audit log.

C

32 Ability to store audit trail data including, but not limited to:

33 User ID C

34 User name C

35 Workstation ID C

36 Printer ID C

37 Date and time stamp C

38 Action taken (e.g., print, edit, deletion) C

39 Before and after values of modified data C

40 Ability to review all system activity performed by a specified user during a period of time.

C

41 Ability to log all vendor access to system (e.g., record a description of all vendor activity). C

42 Ability to maintain historical audit trail data based on an agency-defined length of time.

C

43 Ability to maintain file history so that field value changes can be viewed both before and after change occurred.

C

44 Ability to visually distinguish data fields that were modified in the audit trail.

D

45 Ability to extract reports from the audit log. C

46 Ability to set notifications on specific activity to designated email address.

C

47 Code Table Administration


48 Code Table Modifications

49 Ability for Agency to maintain code tables (add/change/delete) without vendor intervention where not State mandated codes.

C

50 Ability to create a new code and merge/link historical records to a new code. C

51 Ability to store the date a code table value becomes obsolete.

D

52 Ability to store the date a code table value becomes effective.

D

53 Ability to maintain code table history when a code table is modified so that the Agency may run historical queries/searches.

D

54 Ability to re-use expired/deleted codes. O

55 Ability to prevent display of obsolete code table values on drop down lists.

D

56 Code Table Transfer

57 Ability to import tables created in other applications (e.g., Excel).

D

58 Ability to export code tables into other applications (e.g., Excel) for the purpose of updating and editing the tables.

D

59 Ability to mass modify codes throughout the system (e.g., converting codes).

D

60

Ability for code table updates to propagate throughout the system (e.g., an update in a code table for one application component updates the same code table in other application components) where applicable.

O

61 Ability to designate code table values as obsolete and unavailable for current use, preventing further entry of that value, yet retain the value in the table to maintain data integrity for previous records.

C

62 Ability to copy code tables across member agencies (e.g., eliminate need to re-enter identical data for separate agencies). D

63 Statutes

64 System ahould include federal, state and local statutes.

C

65 System should allow authorized users to create and update local statutes/ordinances.

C

66 Attachments


67

The system should allow the attachment of files (for example, .PDF, .DOC , .XLS, .JPG, .WAV) to specified record types. Attached files should be able to be opened or viewed on any workstation by authorized users who have the necessary third-party applications (such as MS Word or MS Excel).

C

68 The system should support scanning and attaching documents directly to records in the system without the need to first save them elsewhere.

C

69

The system should store attached files on the vendor’s server within the vendor’s software (not on an open network folder) for security and ease of access.

C

70 Queries and Reports

71 Queries

72 Ability to conduct searches based on:

73 Soundex C

74 "Wild cards" C

75 Exact match C

76 Partial information C

77 Boolean operators ("and," "if", "or," "not") C

78 Ranges (Date, Location, Time) C

79 Ability to query the following ranges:

80 Date C

81 Time C

82 Location (block range) D

83 Ability to select any result from a query and drill down for detailed information (e.g., hyperlink).

C

84 Ability to perform global search functions for names, addressess, phone numbers and vehicles.

C

85 Ability to search narrative fields. C

86 Ability to restrict searches that result in large volumes of data by providing a warning of the size of records found with option to continue or cancel.

D

87 Ability to clearly indicate when additional information (e.g., more search results) is available.

C

88 Ability to name and save a query. C

89 Reports

90 Ability for the report generating tool to handle:

91 Aggregate math functions, fractiles and percentiles C


92 Logic operations C

93 Time operations C

94 Grouping/sorting on any data element C

95 Ability for users to create ad hoc reports without an in-depth knowledge of databases and query structure. C

96 Ability to maintain a library of user-created reports.

C

97 Ability to preserve all user-created reports during updates and upgrades.

C

98 Ability for all authorized users to access the library of user-created reports.

C

99 Ability to assign permissions to a report (e.g., who may view report, modify report, etc.)

C

100 Ability for users to put their own reports in a "dashboard" for later use.

D

101

Ability to create report templates that can be used to apply standardized layout and formatting to reports for each agency using system. (e.g. different headers/logos per agency)

D

102 Ability to designate authorized users the ability to create/modify templates.

D

103

Ability to automatically generate reports on a pre-determined schedule to be uploaded to a designated file location, emailed or printed on specified dates/times.

C

104 Ability to schedule recurring reports based on user-defined dates, times, days of week, days of month (e.g., every 1st Monday of month).

C

105 Ability to save generated reports. C

106 Ability to export results into standard formats, including:

107 XLS C

108 PDF C

109 CSV C

110 Report Display

111 Ability for reports to display header information, including:

112 Name of individual generating the report C

113 Date/Time report was generated C

114 Agency Name, Address, Phone or Agency Header C

115 Ability to prevent user name from displaying on report. C


116 Ability to define the layout of a report, including but not limited to:

117 Field arrangement D

118 Column Width D

119 Font D

120 Font Size D

121 Spacing D

122 Custom Forms

123

The system should allow authorized users to create custom data collection forms to support agency specified functionality, without any intervention from the vendor.

O

124 The system should allow authorized users to create custom forms.

O

125 The system should support printing the data from custom forms via an agency defined output template and process similar to a mail merge.

O

126

The system should allow authorized users to include as many fields for data collection as are necessary within custom forms, including new fields.

O

127

The system should support the following types of agency-defined fields for custom forms: - Address - Automatic record sequence numbers - Multiple item select boxes - Vehicles/Dates/Times - Dollar Value - Free form text - Names - Numbers - Signatures (for electronic signatures) - Checkboxes - Yes/No drop-downs - Drop-downs from agency-defined lists

O

128

The system should allow a custom form to create a relationship on master name or master address records when those fields are specified within the custom form.

O

129 The system should allow authorized users to specify the label for each field on a custom form.

O

130 The system should allow authorized users to specify if each field on a custom form is required or not required.

O


131 The system should alloow for setting the default value for each field.

O

132 The system should allow the authorized users to arrange the data items and fields in any order on the form.

O

133 Custom Modules

134

The system should permit authorized users to create custom modules designed to meet specific data collection, management, reporting, and output needs without intervention from the vendor or any additional costs.

D

135

The system should permit authorized users to create custom modules designed to meet specific data collection, management, reporting, and output needs without intervention from the vendor or any additional costs.

D

136 The system should allow authorized users to create as many custom modules as desired.

D

137 The system should allow information captured in custom modules to be output from the system in accordance with agency-defined output templates.

D

138

The system should allow authorized users to include as many fields for data collection as are necessary within custom modules, including entirely new fields (not previously stored in the database) as well as fields already existing in the vendor developed database. (i.e. master index fields)

D

139

The system should support the following types of agency-defined fields for custom modules: - Dates/times - Dollar value - Free form text - Names - Numbers - Signatures (for electronic signatures) - Checkboxes - Yes/No drop-downs - Drop-downs from agency-defined lists

D

140 The system should allow authorized users to specify all of the field labels for a custom module.

D


141 The system should allow authorized users to arrange and display custom module fields in any order.

D

142 The system should allow all data included in a custom module to be searched and included in statistical reports.

D

143

The system should allow a custom module to create an relationship on master name or master address records when those fields are specified within the custom module.

D

144 The system should allow authorized users to define and filter the list view of the data included within the custom module.

D

145 Online Documentation

146 Ability to access an online help menu. D

147 Ability to provide context-sensitive help that may be accessed from anywhere within the application.

D

148 Ability for agency to edit text in help files. D

149 Ability for help file to automatically update at the time of all version/release updates.

D

150 Ability to prevent software updates from overriding agency-specific online documentation and help files.

D

151 Ability to track revisions to online documentation and help files by:

152 User O

153 Date and time O

154 Ability to bookmark topics. D

155 Ability to search help file by:

156 Keywords D

157 Topics D

158 Ability to include a built-in glossary. D

159 Ability to print help topics. D


E-3 General Technical Requirements E-3.1 Questions

1 Virtual Server Recommendations

2 Number of concurrent users supported

3 Operating system(s) supported.

4 Number of processors

5 Number of cores.

6 Total memory.

7 Required/recommended storage.

8 Specific drive configurations.

9 Specific RAID requirements

10 Additional Requirements

11 Required Physical Servers

12 Number of concurrent users supported


14 Number of processors

15 Number of cores.

16 Total memory.

17 Required/recommended storage.

18 Specific drive configurations.

19 Specific RAID requirements


18 Network Communications

19 Application (Client to Server) bandwidth requirement (if differ from mobile to non-mobile applications then list differences)

20 Application (Client to Server) latency requirement (if differ from mobile to non-mobile applications then list differences)

21 Backup (Server to SAN) Bandwidth requirement

22 Any other network communication requirements

23 Firewall requirements

24 Describe client functionality when communication to server fails

25 Dispatch Workstations


27 Processor

28 Memory

29 Storage

30 Screen size/number/resolution

31 Network card


33 Non-Dispatch Workstations


35 Processor


36 Memory

37 Storage


39 Network card


41 Mobile Computer/Tablet Requirements


43 Processor

44 Memory

45 Storage


47 Network card


49 Stationary Printer Requirements

50 Make/Model

51 Feature Set

52 Memory

53 Purpose

54 Quantity


56 Mobile Printer Requirements

57 Make/Model

58 Feature Set

59 Memory

60 Purpose (other than mobile printing - if applicable)

61 Quantity if greater than 1 per vehicle


63 Software Requirements

64 List all the recommended and required software necessary to operate the Application Software. Include the manufacturer, version, and any hardware specifications. Make as many copies of this form or add rows as needed.

65 Description Manufacturer

Version Required

# of Licenses Needed

66

67

68

69

70

71

72

73

74

75

76 User Access/Permissions


77 Does your system allow for public access for inquiries?

78 How does system handle if user attempts to login on more than one device?

79 Do you provide clear definitions of what permissions entail?

80 Do you provide predefined roles that are typical?

81 Demonstrate User creation and permission assignments.

78 GIS/Geo File Information

79 What platform/software does CAD mapping use?

80 What platform/software does Mobile mapping use?

81 How does address validation work within your solution?

82 How are Geo File changes maintained?

83 Does your solution support shape files?

84 Does your solution support centralized geo files on a network?

85 Can you provide an example of a fully functional geo file?

86 How does your solution map wireless calls?

87 Data Conversion

88 Define data converted from CAD

89 Define data converted from RMS

90 Define data converted from JMS

91 Will attachments convert?

92 If any data does not convert, what is the legacy data solution?

93 How are code discrepancies handled?

94 Describe the process used to scrub the data.

95 Describe the software transition plan.

95 Database Application

96 Do you use one centralized database for all applications?

97 What backend database is used?

98 What is the front-end programmed in?

99 Upgrades and Updates

100 Briefly describe the upgrade process.

101 Are upgrades performed by the client or the vendor?

102 What is the expected upgrade frequency?

103 Do you mandate installation of new releases? How Often?

104 Do you mandate the installation of updates? How Often?

105 Do updates need to be scheduled or automatically pushed?

106 Is user required to be local admin on pc to run updates?

107 How many versions are supported and what is end of life formula?

108 Pre-requisites and 3rd party software needed to run applications.

109 Installation

110 Are instructions provided for all install processes?

111 Demonstrate install of each product.

112 Licensing

113 What are you client licensing options?


114 Support

115 What is your standard response time?

116 High priority tickets

117 Low priority tickets

E-3.2 Requirements

Technical Requirements


Item #


1 Server Requirements

2

Any services running on servers do not require a service account logged in at all times in order to maintain process C

3

Technical installation services of software upgrades are included with active maintenance agreements C

4

The bidder, along with the appropriate Portage County staff will perform all tasks required to implement the system C

5 Multiple Environments

6 Ability to support multiple environments, including:

7 Production C

8 Test C

9 Training C

10 Backup/Disaster Recovery C

11

Ability to modify the test environment and transfer modifications to the production environment. D

12

Ability to modify the production environment and transfer modifications to the test environment. D

13

Ability for user to operate both a production, test and training environment simultaneously. C

14

Ability to provide visual distinction of environment user is operating. C

15 Backup Requirements

16 Full nightly backups performed C

17 Ability to schedule full system backups. C


18

Incremental backups multiple times daily. How many times daily? C

19

System functions be available during backups including but not limited to inquiries and updates. C

20 Disaster Recovery

21

System should inlcude warm failover environment in the event that the primary system becomes unavailable. C

22

System should replicate the production data to failover system in near real time. C

23

System automatically fails over to the backup environment in the event of a failure in the production environment. C

24

System fails over without any manual intervention on the Servers C

25

System should allow end-users to easily connect to failover environment in the event the production server is unavailable. C

26

System should resync production data when production environment is available, in the event that failover environment was used. C

27 Upgrades and Patches

28

System software upgrades are included with active maintenance contract. C

29

The vendor should include all updates, enhancements, new versions, and upgrades of the server operating system software and database software as part of its standard software maintenance agreement. C

30

The vendor should ensure that the agency will not have to purchase any third-party server operating system software updates and/or newer versions as long as its software maintenance agreement is maintained. C

31

The vendor should install all software updates on the testing/training server(s) before installing them on the production servers. C

32

System can have all patches applied with minimal system downtime. C

33

The vendor should install all system software updates to the server and then automatically install updates to each client machine at next startup without any intervention from the vendor or IT. D


34

Vendor releases no less than quarterly application patches, to both Primary and Disaster Recovery Equipment. D

35

Vendor provides ability for client to refresh training and test environments as desired. D

36 Data Conversion

37 Ability to convert data from TriTech Vision product line. C

38 Ability to view and report on converted data. C

39 Integration

40

System should ensure that all modules integrate with each other (CAD, RMS, JMS, etc.), are provided by the same vendor and are not third-party applications. C

41

System should allow all modules (CAD, RMS, JMS, etc.) to be accessible to authorized users from the same application window. C

42

Integrated modules should provide automatic transfer of critical information (e.g. CFS from CAD to RMS, Arrest and Warrant from RMS to JMS). C

43

System should integrate alerts between all modules so that they are accessible by all using any module in the system. (e.g. outstanding warrants) C

44

System should ensure that all modules share the same master records for names, addresses, property and vehicles and these master indices are located within a single database. C

45 Desktop Application

46

Application is browser based List compatible browsers C

47 Application runs on Win 10 C

48 Mobile Laptop Application

49

Application is browser based List compatible browsers C

50 Runs on current laptops (Getac, Tougbook) C

51 Application runs on Win 10 C

52 Compatible with NetMotion Mobility VPN C

53 Mobile (Smartphones/Tablets) Applications

54 Compatible with NetMotion Mobility VPN C

55

Mobile clients are able to run the application without being joined to a domain D

56 Application runs on Apple IOS D

57 Application runs on Android D


58 User Interface

59

System should have consistent user interface design throughout all modules. C

60

System should perform data validation/error checking for fields in the system. C

61

System should allow specific fields to be designated as required data entry. C

62

System should provide auto-completion for frequently entered data. D

63

System should include a spellchecker for text fields throughout the system. D

64

Ability for the agency to add, delete and rename data fields. D

65

System should provide an agency and user customizable dashboard to display summary information from modules to which the user has permissions. D

66

User dashboard should display overdue tasks and reminders. D

67

User dashboard should allow customization of adding website links. D

68 GIS/Mapping Requirements

69

The ability to use agency maintained ESRI based GIS layers to populate and maintain the geofile. C

70

The vendor should test the GIS data to ensure proper functionality. C

71

The ability to maintain geofile layers in a current release of ESRI’s products (10.5 and above) C

72

The ability to import geofile updates into CAD/RMS using standard ESRI tools or vendor supplied models or scripts. C

73

The ability to publish geofile layers to ArcGIS Server map services that can be used by Mobile clients. C

74

The ability to have live geofile updates available to CAD/RMS. C

75

The vendor should be capable of providing additional GIS services without involving a third party. D

76

Ability to integrate with Tracker for ArcGIS for location tracking services. D

77 GPS Requirements

78 Ability to configure GPS through ethernet or comm port. C


79

Ability to accept NMEA and TAIP device message protocol. C

80

Ability for GPS to display real time unit location of mobile client on CAD and Mobile map display. C

81

Ability for multi-unit display of GPS location on CAD and Mobile map display. C

82 Ability for AVL to use real time GPS location. C

83 Printing

84 Ability to support network printer configuration C

85 Ability for user to select applicable printer. C

86 Ability to estabish default printer based on:

87 User ID C

88 Device D

89 Training

90

IT system administration training is provided on the system being deployed C

91 On-site end-user training is available C

92 Online end-user training is available C

93 Support

94

The currently available version of software will be supported for a minimum of 3 years from the installation date C

95

CAD Technical Support is available 24 x 7 and is included in the pricing of the RFP. If not included, then list annual cost in Comment field. C

96

All other product Technical Support is available 8 x 5 and is included in the pricing of the RFP. If not included, then list annual cost in Comment field. C

97 Technical Support is based in the United States C

98 Security

99 Ability to meet all CJIS security requirements. C

100 Ability to maintain compliance with CJIS requirements. C

101

System should be FIPS 140 compliant for all network communication, includinged wired and wireless communication.

C

102

System should allow multiple agencies to share host server yet have the ability to limit access to sensitive information.

C

103 User Accounts/Passwords

104

Ability to provide Active Directory integration with support of multiple domains. (multiple agencies utilizing software on separate networks)

C


105 Ability to support multi-factor authentication. C

106

System should provide centralized user management so each user has a single username and password for the entire system, incorporated across all applications, ensuring that changes made to a user account are made in a single place.

C

107 Ability to mask passwords when typed. C

108 Ability to encrypt passwords when stored. C

109 Ability to maintain a history of de-activated user IDs. C

110 Ability to do the following if not associated with AD:

111

Allow authorized users to create and maintain user accounts.

C

112 Allow users to change their own passwords. C

113

Allow agency configurable password parameters including:

114 Minimum length C

115 Case sensitive C

116 Require uppercase and lowercase C

117 Require numeral C

118 Frequency of password changes C

119 Number of previous passwords which cannot be reused C

120 Ability for system administrator to disable an account:

121 Temporarily C

122 Permanently C

123

Ability to capture the following information associated with each unique Login ID:

124 Name C

125 Title C

126 Badge Number (not unique - can change) C

127 Agency C

128 Email Address C

129 Security Permissions/Roles C

130

Ability to change Badge number associated with user as needed. C

131 User Access

132

Ability to automatically logoff a user after an agency-defined predetermined period of inactivity, based on:

133 User type D


134 Location D

135

Ability to remotely log out a workstation (mobile or desktop).

C

136

Ability to provide system generated message to system administrator when an agency-defined number of unsuccessful sign-on attempts have occurred. The message must include, at a minimum:

137 Date and time C

138 User ID C

139 Workstation ID C

140

Ability to “lock out” a user after agency-defined number of attempted logons.

C

141

Ability to designate authorized users to reset passwords and/or unlock user accounts.

D

142 Ability to log the following related to user logons:

143 Logon attempts C

144 Attempts to modify password C

145 Logon Date/Times C

146 Logoff Date/Times C

147

Ability to grant outside users restricted access to inquiry with login (i.e. DA)

D

148 Permissions

149

Ability to support group/role-based security permissions.

C

150

Allow authorized users to create and maintain user groups/roles. C

151 Allow authorized users to assign users to groups/roles. C

152 Ability to assign permissions to individual user or roles. C

153 Ability to assign users to multiple groups/roles. C

154

Provide access levels, including view, add, edit, delete and admin for each component of the system for users and user groups.

C

155

Ability to define permissions for each group/role, including but not limited to:

156 Application Access C

157 Module Access C

158 Jurisdiction C

159

Allow authorized user to designate user/users as a System Administrator.

C


E-4 Records Management System (RMS) Functional Requirements E-4.1 Questions-None

E-4.2 Requirements-

Portage County Public Safety Software Replacement RFP Record Management System


1 General Requirements

123 RMS Master Indicies

251 Calls for Service

276 Data Analysis

361 Supplies and Equipment Assignment

428 Property and Evidence

627 Case Management

712 Traffic - Citations and Accidents

761 Mug Shots and Line ups

802 False Alarm Billing

882 Internal Affairs

960 Personnel

1002 Officer Activitiy

1067 Training

1135 Fleet Maintenance

1260 Intelligence

1283 Gang Members

1364 K9

1391 Receipt and Billing

1439 Warrants and Protection Orders

1482 Civil Process

Item #


1 Ability to access the RMS from:

2 Browser C

3 Mobile C

4 Desktop C

5 Ability to support simultaneous access to records. C

6

Ability to support multiple agencies within the RMS, separating records as defined by member agencies.

C

7

Ability to support multiple code tables for each member agency (each agency can have it's own code tables).

C


8

Ability to share code tables amongst each member agency.

D

9

Ability for vendor to provide code tables compliant with the following standards:

10 NCIC C

11 UCR and IBR C

12 Ability to reuse previously stored information when entering new records. C

13 Ability to populate fields in the RMS from data returned from external sources (NCIC, State Inquiries etc.) C

14

Ability to populate fields in the RMS from data in other application components (e.g., Field Reporting Software, CAD, JMS etc.) C

15

Ability to provide narrative/comment fields of unlimited length (if limited, indicate the maximum permissible in the "comments" field).

C

16 Ability for narrative/comment fields to be searchable. C

17

Ability to provide word processing capabilities on narrative and comment fields, including, but not limited to:

18 Text wrap C

19 Paragraph formatting C

20 Use of bullets and numbering C

21 Spell check C

22 Copy and paste C

23 Grammar check C

24 Ability to perform the following functions for all records related to a query return:

25 Retrieve C

26 Display C

27 Export C

28 Print C

29

Ability to restrict user access to query specific databases (e.g., allow County to search County only, or allow a user full rights).

C

30

Allow authorized users to build unlimited case report output templates (such as an internal report, a media report, and a state’s attorney report) and to specify which data is printed for each.

C

31

Allow case reports to be generated without a corresponding call for service

C


32 General Data Quality Controls

33

The system should include the following default involvement types for case reports: offender, suspect, victim, and witness.

C

34 Ability to define mandatory fields in data entry screens:

35 By Agency (e.g., single set-up system wide) C

36

By Member Agency (e.g., County defines mandatory fields differently than City)

C

37

Ability to identify mandatory fields based on previously entered data (e.g., crime type).

C

38

Ability to limit available values in subsequent code tables based on previously entered data (e.g., crime type).

D

39

Ability to visually distinguish between mandatory and optional fields.

D

40

Ability to prompt user to complete any mandatory fields not completed.

C

41 Data Validation

42 Ability to perform data validation:

43 At time of entry C

44 At time of submission C

45

Ability to validate data to ensure that only valid codes have been used.

C

46

Ability to validate any data field that includes master index data against master indices.

C

47

Ability for corrected data in a field (e.g., address) to auto populate across related modules

D

48

Ability to validate location information at time of data entry.

C

49 Ability to indicate unverified locations. C

50

The system should auto-populate case reports generated from calls for service data such as address, nature of the incident, complainant/reporter data, beat/zone, and NCIC queries and results.

C

51

Ability to validate location information against CAD geofile.

C

52 Allow the case narratives to include unlimited text C

53

The system should allow an unlimited number of involvement types to be set up for and used on case reports.

C


54

Allow case reports to include unlimited case notes which are stamped with the date, time and name of the user who created them.

D

55

Support multiple case reports for the same event, with access to the reports restricted by user permissions. For example, a patrol report and an investigative report may be created about a single event and linked to each other.

C

56

The system should group case reports based on agency-defined criteria (for example, a string of car break-ins). Links should be provided between grouped case reports.

C

57

The system should support intelligent full-text searching of case report narrative fields

D

58 RMS/JMS/CAD Integration

59

Ability to share master name indices across the RMS and JMS (if proposed).

C

60 Ability to query any data captured in the JMS. C

61 Ability to support a query from the JMS. C

62

The system should allow call-takers and dispatchers to perform an automatic transfer of CFS data from CAD to the RMS when needed. This transfer should not be a one-time transfer but should be kept up to date as the CFS progresses

C

63 Redaction

64 Ability to electronically redact information from reports. C

65

Ability to electronically redact selected information in a narrative.

C

66 Ability to electronically redact information from reports prior to printing a public copy. C

67 Ability to include agency-defined language in header of redacted report (e.g. Original Report, Redacted Report). C

68 Ability to provide an audit trail of redactions. D

69 Ability for agency to establish an automatic redaction process in which agency-defined fields are automatically excluded from reports. (e.g., SSN)

D

70 Ability to save a copy of the redacted report. C

71 Seal Records

72 Ability to seal records. C

73

Ability for expungement utility to automatically seal appropriate entries.

D


74 Ability to seal a case without sealing an entire person. C

75

Ability to prevent all users without the authority to see a sealed record from seeing that the record exists.

C

76 Alerts and Flags

77

Ability to create an alert based on records matching specified criteria.

C

78 Ability to create a flag on:

79 Individual C

80 Location C

81 Vehicle C

82 Ability to create alerts:

83 Audible Alerts C

84 Visual Alerts C

85 Ability to limit ability for users to create alerts. C

86

Ability for agency to create business rules for flag categories (e.g., length of time before expiration by type of flag).

C

87

Ability for Agency to define flag/alert categories (e.g., violent, weapon history, etc.)

C

88

Ability to attach an alert to a specific record so that if a record is updated in any other context, the appropriate user is alerted.

C

89

Ability to flag a data element as confidential information for security purposes.

C

90 Ability to provide alerts/notifications via:

91 Email C

92 User Sign-on C

93 Sex Offenders

94

The system should allow for tracking sex offenders.

95

The system should ensure that names and addresses entered into sex offender records are checked against the master indices and then added to those indices if they do not already exist.

96

The system should provide a list of registered sex offenders that is accessible by authorized users from any product.

97

The system should alert users to sex offender status whenever a sex offender’s name appears anywhere in the system.


98

The system should track sex offender check-in dates and alert users to an offender’s next required check-in date.

99

The system should be able to generate a printable list of sex offenders who are soon due to check in or who are overdue.

100

Agency-defined custom fields should be available in Sex Offenders.

101 UCR/WIBR Reporting

102 Ability to comply with Wisconsin UCR/IBR standards. C

103

Ability to maintain compliance with State and Federal reporting changes as they are modified. Indicate how vendor distributes UCR/IBR updates.

C

104 Ability to configure the system to either UCR or WIBRS. C

105 Ability to associate local classifications/statute numbers to UCR/IBR classification. D

106 Ability to perform monthly UCR audits. C

107 Ability to support online submission of monthly reports. C

108

Ability to submit a "trial" version of case information for UCR review that identifies potential errors prior to submission. C

109

Ability to provide an error message describing corrections that need to be made.

C

110

Ability to prevent reports from being submitted to UCR/IBR until all errors have been corrected.

C

111 Ability to identify UCR/IBR mandatory fields. C

112 Ability to prompt user to complete mandatory fields. C

113 Ability to submit a "final" version of case information for UCR/IBR review. D

114

Ability to flag any data elements that are edited by an authorized user other than the original author (e.g., UCR review personnel change a data element from the original report). D

115 Ability to maintain a version history of each case that identifies any edits to a case report over time. D

116 Ability for subsequent submissions for UCR review to include any case changes. C


117

The system should perform IBR error checking and validation on the case report, including detailed error messages.

118 Digital Media Management

119 Ability to store digital files. C

120

Ability to index digital files (e.g., incident information, CR#, call type, date and time, involved person).

C

121 Ability to search digital files. C

122

Ability to access stored digital media directly from associated records.

C

123 Ability to distinguish between evidentiary and non-evidentiary digital media. D

124 RMS Master Indices

125 General Master Index Requirements

126 Ability to maintain the following master indices:

127 People C

128 Locations C

129 Property C

130 Vehicles C

131 Organizations (including businesses and gangs) C

132

Ability to automatically query master indices upon entry of information in a master index category (e.g., enter name system queries MNI). C

133 Ability for agency to define the rules for identifying potential master index matches. C

134

Ability to maintain historical information upon entry of updated information into a master record (previous address, phone etc.) C

135

Ability to automatically update master indices upon entry of information into the RMS (or transfer from a field report). C

136 Ability for user to decide whether to link information to an existing master index record or add a new record. C

137

Ability for user to create a new entry if it is determined a master record does not exist.

C

138 Ability to support linkages among any information. C

139

Ability to run a report to identify potential duplicate master indexes/files.

C

140 Ability to merge master records C

141 Ability to unmerge master records. C


142 Ability to search RMS by any data element in a master index. C

143 Ability to associate files, images, documents etc. to master records. C

144 Ability to link across master indices(e.g., link MNI to MVI) C

145 Master Name Index

146 Ability to link an individual master name record to every event in which the individual is involved or associated. C

147 Ability to give a master name record to every person associated with an event. C

148 Ability to link a new event to an existing master name record if the person is involved in the new event. C

149

Ability to link alias names to an individual master name record.

C

150 Ability to produce and display or print a synopsis of all RMS records associated with an individual. C

151 Ability to view all related records when querying an individual MNI record. C

152 Ability to capture, at a minimum, the following information in the master name index: C

153 Physical characteristics, including, but not limited to:

154 Height C

155 Weight C

156 Gender C

157 Race C

158 Eye Color C

159 Hair color C

160 Scars, marks, tattoos C

161 Age C

162 Alias C

163 Monikers C

164 Address C

165 Address history C

166 Telephone numbers C

167 Involvements C

168 Associates C

169 All available mug shots and photographs C

170 Modus operandi C

171 Warrants C

172 Custody Status D


173 Identification information, including, but not limited

to:

174 Social security number C

175 Driver's license number and state C

176

Ability to track changes for an individual over time for pieces of information that are subject to change (e.g. weight, address, phone number,) C

177

Ability to provide user entering a name with a list of potential existing master name records based on a variety of criteria and to define the criteria, including:

178 Exact spelling C

179 Partial name C

180 Sound-alike searching C

181 Phonetic replacement C

182 Diminutive first names C


184 Driver's license number C

185 Ability to identify an individual as a juvenile. C

186 Master Vehicle Index

187

Ability to give a master vehicle record to every vehicle associated with an event.

C

188

Ability to link a new event to an existing master vehicle record if the vehicle is involved in the new event.

189 Ability to capture, at a minimum, the following information in the master vehicle index: C

190 Vehicle identification number C

191 License plate number C

192 License plate state C

193 License plate year C

194 Registered owner C

195 Vehicle description, including:

196 Make C

197 Model C

198 Year C

199 Color C

200 Ability to populate year, make, and model fields based on VIN (automated decryption of VIN). D

201 Ability to associate multiple owners with one vehicle. D

202 Ability to track previous vehicle owners. D

203

Ability to produce all RMS records associated with (linked to) a vehicle.

C


204 Ability to view all related records (vehicle, address etc) when querying an individual MVI record. C

205

Ability to provide user entering a vehicle with a list of potential existing master vehicle records based on a variety of criteria, including:

206 Vehicle license plate number C

207 Partial license plate number C


209 Partial vehicle identification number C

210 Master Property Index

211 Ability to give a master property record to every piece of property associated with an event. C

212 Ability to link a new event to an existing master property record if the property is involved in the new event. D

213 Ability for agency to define which data elements are to be captured as part of the master property index. D

214

Ability for property fields to incorporate conditional logic in which subsequent fields are determined by previous entry. O

215

Ability for the information in the property table central to the system in order to eliminate duplicate entry of property information.

C

216

Ability for property information to be easily accessible from other system tables as part of an involvement. C

217

Ability to provide the capability to link related records to the property record in such a way that the user can display a list of related records directly from the property record and display a full record from that list.

C

218 Ability to capture property information. C

219 Please list any additional property entry fields. C

220

Ability to provide for a custody record for each property item, showing a history of custody transfers for the item. C

221

Ability to provide the ability to easily duplicate a change-of-custody entry for items under the same tag. C

222

Ability to accommodate IBRS/WIBRS mandated amount recovered and accumulative amount recovered for each item.

C


223

Ability for the owner name to be an integrated part of the master names table. C

224

Ability to clearly display why the property item is in the system (e.g. stolen, recovered, lost, found, evidence, attached by civil officers, etc.).

C

225

Ability for a modificationto be made to the property record, the system preserves the previous data from fields in a history record.

C

226

Ability to attach digital images to the property record. C

227

Ability for the generation of pre-formatted reports of property information, including a summary of property released.

C

228

Ability to accommodate the needs of all jurisdictions. C

228

Ability to allow the ability to enter property prior to case info/details being completed. C

229

Ability to create owner letters from the property module for return or destruction. C

230 Master Location Index

231 Ability to aggregate information throughout the RMS based on any of the following:

232 Specific address C

233 Address range C

234 Geographic area (as defined in the geofile) D

235

Ability to give a master location record to every location associated with an event.

C

236

Ability to link a new event to an existing master location record if the location is involved in the new event.

C

237 Ability to parse address fields into the following:

238 Street number (including fractions, alphas, etc.) C

239 Street C

240 Street type C

241 Prefix directional C

242 Subdivision D

243 Suffix directional C

244 Suite or apartment number C

245 City C

246 Zip C

247 Master Organization Index


248

Ability for agency to define organization categories (e.g., gangs, businesses, schools, shopping centers).

C

249

Ability to give a master organization record to every organization associated with an event.

C

250

Ability to link a new event to an existing master organization record if the organization is involved in the new event.

C

251 Calls for Service

252 General Calls for Service Requirements

253

Ability to receive call for service data transferred from the CAD application, including but not limited to the following:

254 Incident number C

255 Initial call time C

256 Units dispatched D

257

Call for service activity time stamps (e.g., en route, at scene)

C

258 Initial call type D

259 Final call type C

260 Call disposition D

261 Call comments C

262 Ability to link call for service data to:

263 Master Indices C

264 Records/Reports C

265

Ability to transfer call for service data either when a report number is assigned or when the call is closed, depending on the call type.

C

266

Ability for call for service to indicate whether or not an associated report is required.

C

267

Ability for call for service record to indicate officer responsible for completing a report.

C

268 Standard Calls for Service Outputs

269 Ability to produce calls for service reports over a user-defined time period by any combination of the following:

270 Agency C

271 Individual C

272 Unit C

273 Individual Incident C

274 Incident Type C

275 Geographic Area C

276 Data Analysis

277 General Data Analysis Requirements


278

Ability to analyze activity using the following analysis options, including, but not limited to:

279

Frequency analyses (e.g., analyses with only one variable)

C

280 Spatial analysis D

281 Time analysis C

282 Link analysis C

283 Comparative Analysis C

284

Simple relational analysis (e.g., seeking relationships between two data fields)

C

285

Complex relational analysis (e.g., seeking relationships among three or more data fields)

C

286 Ability to filter crime analysis by responding agency. C

287 Ability to save searches. C

288 Ability to export search results to Excel. D

289 Ability for agency to establish incident/crime thresholds. D

290

Ability to alert designated users when incidents/crimes exceed thresholds.

D

291 Ability for incident/crime thresholds to be set by:

292 Agency-Wide D

293 Member Agency D

294 Specific incident/crime types D

295

Ability to set crime thresholds and alert designated users when crime exceeds said threshold.

D

296 Ability for threshold alerts to notify individuals via:

297 Email D

298 Other (define in "comments") O

299 Ability to present statistics in graphical formats, including, but not limited to the following:

300 Bar graphs C

301 Pie charts C

302 Line graphs C

303 Map Analysis

304 Ability to plot incident data on a map. C

305 Ability to produce density maps. D

306 Ability to produce hot spot maps. D

307 Ability to drill down for incident details from any incident plotted on the map. C

308 Ability to conduct a radius search on a map. C


309 Ability to conduct a polygon search on a map. C

310

Ability to use different icons to display different incident types.

C

311 Ability for agency to define its own pin map icons (size, color, symbols, callouts, etc.). C

312 Ability to plot the following data elements:

313 Method of entry C

314 Method of Attack Person C

315 Method of Attack Property C

316 Suspect physical description D

317 Suspect Demeanor D

318 Property Type C

319 Call Type C

320 Offense Code C

321 Weapon Type C

322 Weapon Use C

323 Day of Week C

324 Date Range C

325 Time of Day C

326 Time Range C

327 User-defined shifts D

328 Location C

329 Location radius C

330 Ability to print map analysis. C

331

Ability to provide a public interface to the crime mapping application that allows the public to plot and search for Agency-identified incident types.

C

332 Link Analysis

333 Ability to analyze linkages among data elements. C

334

Ability to click on a linked element to show links based on that element.

C

335 Aggregate Reporting

336

Ability to aggregate data contained in records to create summary reports showing:

337 Totals C

338 Averages C

339 Frequencies C

340 Percentages C

341 Ability to aggregate data by:

342 Date range C

343 Time of day C

344 Day of week C

345 Geographical area C


346 Officer ID C

347 Shift C

348 Agency C

349 Unit O

350 Type of Call C

351

Uniform Crime Reporting (IBRS)/Wisconsin & National Incident-Based Reporting System (WIBRS & NIBRS)

352

Ability to provide for reporting State of Wisconsin IBRS/WIBRS and federally-approved NIBRS consistent with federal and State of Wisconsin requirements. C

353

Ability for the IBRS/WIBRS program to automatically pull from information routinely entered through the application software and not require special data entry immediately prior to IBRS/WIBRS generation.

C

354

Ability to update periodically to meet required changes mandated by the FBI and/or State of Wisconsin. C

355

Ability for the software to be capable of running IBRS/WIBRS simultaneously to provide for the migration to WIBRS.

C

356

Ability to perform an audit/validation on each case entered for errors. C

357

Ability to generate a monthly audit/validation report, searching offenses and arrests for errors. C

358

Ability to have an alert for potential incorrect errors (e.g. Reported date is prior to the date of incident). C

359 Ability tocreate monthly IBRS/WIBRS reports. C

361 Supplies and Equipment Assignment

362 Ability to identify inventory for multiple agencies. C

363

Ability to provide dedicated fields to capture, maintain and track equipment assigned to personnel, including, but not limited to, the following:

364 Issued to C

365 Equipment type C

366 Serial number C

367 Make C


368 Model C

369 Description C

370 Condition C

371 Cost D

372 Replacement date(s) C

373 Service date C

374 Repair/Service History D

375 Comments D

376 Asset Number C

377 Date Purchased D

378 Date Issued C

379 Condition C

380 Quantity C

381 Warranty Information D

382 Vendor D

383 Ability to capture history of equipment assigned to an:

384 Individual C

385 Vehicle C

386

Ability to track multiple pieces of the same type of equipment assigned to one individual.

C

387

Ability to associate life cycles with equipment (e.g., equipment expires after 5 years of issuance).

C

388

Ability to track status of equipment (e.g., destroyed, out for repair).

C

389 Inventory

390

Ability to track inventoried items (e.g., equipment/supplies not yet assigned to individuals).

D

391 Ability to update inventory totals:

392 Upon receipt of new inventory D

393 Upon assignment of inventoried items D

394

Ability to generate an automatic alert to designated personnel when inventory levels fall below member agency-defined level (e.g., threshold levels).

D

395 Ability to track vendor information:

396 Company name D

397 Point of contact D

398 Telephone number D

399 Order history D


400

Ability to generate budget life cycle based upon user-defined time period and associated costs of equipment.

D

401 Equipment Return

402 Ability to check equipment back into inventory. D

403 Ability to unlink equipment from personnel upon check-in. D

404 Ability to track replaced equipment:

405 Date replaced D

406 Reason replaced D

407 Disposition of equipment D

408 Equipment Maintenance and Replacement

409

Ability to create maintenance schedules for equipment requiring regular maintenance.

C

410

Ability to generate reports listing equipment due for maintenance during a user-defined time period (e.g., generate a report on the first of every month for equipment that needs to be replaced by the end of that month).

C

411

Ability to generate reports listing expired equipment during a user-defined time period.

C

412

Ability to document maintenance for a piece of equipment.

C

413

Ability to create replacement schedules for equipment requiring replacement after a period of time (e.g., bullet-proof vests every five years).

C

414

Ability to generate reports listing equipment due for replacement during a user-defined time period (e.g. generate a report on the first of every month for equipment that needs to be replaced by the end of that month).

C

415

Ability to automatically generate and print, at a user-defined interval, reports listing equipment overdue for replacement (e.g. generate a report on the first of every month for equipment for which replacement is overdue).

C

416

Ability to generate alerts to individuals that their equipment is due for maintenance or replacement.

C

417 Bar Code Tracking System

418

Ability to manage and track inventory using a bar code system.

D

419

Ability to automatically update (e.g., download) inventory information into system.

D


420 Ability to print bar code labels. D

421 Standard Asset Management Outputs

422 Ability to generate a physical inventory report based on:

423 Member Agency D

424 Officer D

425 Location D

426 Equipment Type D

427

Ability to generate a report showing asset history (e.g., assigned to whom, statuses, etc.)

D

428 Property and Evidence

429

General Property and Evidence Management Requirements

430

Ability to identify property and evidence for multiple agencies.

C

431 Ability for agency to configure item numbering sequence. C

432 Ability for agency to override numbering sequence. C

433 Ability for system to generate a unique number for each case. C

434

Ability to indicate when property is associated across multiple member agencies.

C

435 Ability to designate property/evidence type:

436 Evidence C

437 Found property C

438 Safekeeping C

439 Lost C

440 Stolen C

441 Recovered C

442 Agency Defined C

443 Ability to associate UCR/IBR codes with Property. C

444 Ability to link a property record to an incident report. C

445

Ability for property related to the identical incident to be logically associated (e.g., Incident is 1, property may be labeled as 1-A, 1-B, etc.) C

446 Ability for agency to define storage locations:

447 Storage types (shelf, refrigerator, etc.) C

448 Storage location identifiers (e.g., shelf, bin, bag) C

449

Allow for property reports to be exported into excel

D

450 Bar Coding


451

Ability to provide a bar code scanning system that will allow property to be scanned and bar codes printed.

C

452

Ability for agency to configure which data fields are printed on bar code.

C

453

Ability to capture a date and time stamp with any bar code activity.

C

454 Ability to print multiple bar code labels at one time. C

455

Ability to generate a single bar code label for all items under a property number.

C

456

Ability to generate a bar code label with property information:

457 Item number C

458 Property number C

459 Case number C

460 Property description C

461 Property and Evidence Collection

462

Ability to support multiple dates of evidence collection per case.

C

463 Ability to import property information from the incident report into the property record. C

464 Ability to generate a receipt for items taken into property and evidence for any reason C

465 Ability to associate an unlimited number of property items to a case (if limited identify upper limit in comments). C

466 Ability to support mass entry of property in which multiple items are uploaded to the module without re-keying data. C

467 Ability to query the RMS to determine the appropriate incident with which to link property. C

468 Ability to add investigator responsible for a case to the property record upon case assignment to the investigator. C

469

Ability for system to automatically assign storage locations based on:

470 Available locations D

471 Property type D

472

Ability for user to enter a storage location (e.g., location suggestions not generated).

D

473

Ability to perform the following related to Property information (including vehicles and guns) related to NCIC:


474 Enter C

475 Modify C

476 Supplement C

477 Cancel C

478 Query C

479

Ability to capture the following information related to a drug intake:

480 Drug Type C

481 Quantity C

482 Weight C

483

Ability to capture the following information related to a vehicle:

484 Make C

485 Model C

486 Color C

487 Owner Information C

488 Insurance Information O

489 Incident/Offense C

490 VIN C

491 License Plate C

492

Ability to capture the following information related to a weapon:

493 Type C

494 Description C

495 Owner Information C

496 Size C

497 Caliber C

498 Serial Number C

499 Manufacturer C

500

Ability to keep a balance of currency held in property and evidence.

C

501 Ability for agency to create property types. C

502

Ability for agency to define associated data fields corresponding to specific property types.

C

503 Ability to track forfeited currency. C

504

Ability to generate a receipt for currency taken into property and evidence.

C

505

Ability for property and evidence intake officer to add information to the property record, including but not limited to:

506 Date and time evidence collected C

507 Evidence pick up location C

508 Evidence technician picking up item name and ID C


509 Date and time picked up C

510 Date and time checked into property room C

511 Location in property room C

512

Outside Analysis Information (Location, Date, Outcome)

C

513 Digital Evidence Management

514 Ability to accommodate digital evidence (e.g., photographs, video, emails). C

515 Ability to track users who have viewed digital evidence, including but not limited to:

516 User ID C

517 Date/Time viewed C

518 Actions taken (e.g., viewed, printed, etc.) C

519 Ability to associate digital evidence with an incident. C

520 Ability to print digital evidence. C

521 Ability to batch upload digital evidence. D

522 Ability to restrict access to digital evidence based on:

523 Evidence Type C

524 Case/Incident C

525 User Permissions C

526 Member Agency C

527 Ability to support digital evidence stored in a non-proprietary format (e.g., jpg, .pdf, etc.) C

528 Ability to purge digital evidence C

529 Ability to email digital evidence and record the email in chain of custody. C

530 Rejected Evidence/Property

531 Ability to reject submitted evidence. C

532

Ability to indicate reason for rejection (e.g., improperly packaged or documented).

C

533 Ability to track rejected evidence. C

534 Ability to notify submitting officer of rejected evidence. C

535

Ability to generate a report showing number of rejected pieces of evidence by officer.

D

536

Ability to resubmit evidence after required corrections have been made.

C

537 Chain of Custody

538

Ability to track chain of custody data for any piece of property entered into the system as evidence, including but not limited to:

539 Name C


540 Purpose of Collection C

541 Destination C

542 Storage Location C

543 Date/Time (check-in/Check-out) C

544 Ability to capture electronic signatures. C

545 Ability to track chain of custody for blood kits:

546 Date kit is mailed to State C

547 Date results are received C

548 Ability to notify user of changes in chain of custody status for a user-defined property item. C

549 Ability to notify multiple users of changes in chain of custody status for a user-defined property item. D

550

Ability to track viewing of a property item, including but not limited to:

551 Start and end time of viewing D

552 Evidence viewed D

553 Location of viewing D

554 Persons present during viewing (multiple) D

555 Reason for viewing D

556 Ability to include due dates for items to be returned. C

557

Ability to provide automatic reminders, at agency defined intervals, that checked-out items are overdue.

C

558

Ability to scan bar code during check-out and check-in to update chain of custody (e.g., time and date information are populated and the user only adds information not in the system).

C

559

Ability to generate a chain of custody report for a property item entered into the system as evidence.

C

560

Ability to query a property item and identify its location from the chain of custody information.

C

561 Inventory and Audits

562 Ability to document person conducting an audit. C

563

Ability to view all property items attached to a single incident.

C

564

Ability to display person conducting an audit on all related audit reports.

C

565

Ability to document on a property record that the item was included in an inventory or audit, including:


566 Indicator that property was inventoried/audited C

567 Date and time stamp of inventory/audit C

568

Result of inventory/audit (e.g., found in correct location, not found, found in wrong location)

C

569 Ability to generate a list of all property located in a given:

570 Property room area C

571 Shelf C

572 Bin C

573 Any agency-defined location C

574

Ability to scan all items in a given location to check that items on a list of property are in the proper location.

D

575 Ability to generate a report of missing property items. C

576 Ability to conduct a full inventory of property by:

577 Date entered C

578 Location C

579 Case number C

580 Member Agency C

581 Officer C

582 Type of property C

583

Ability to enter in a case number and have the system display:

584 A list of associated evidence C

585 The location of associated evidence C

586 Property and Evidence Disposition

587 Ability to classify property for disposal through:

588 Return to owner C

589 Destruction C

590 Agency Defined Method(s) C

591 Retention Files C

592 Auction C

593

Ability for agency to identify review dates for different types of property.

C

594

Ability to capture approving party of disposition (name, date/time, etc.) for the following:

595 Member Agency Representative C

596 District Attorney C

597 Ability for agency to configure disposition types. C

598

Ability to maintain property records after property disposal.

C


599 Ability to notify investigators of items that require review:

600 Manually C

601

Automatically (based on agency-defined business logic)

C

602

Ability to alert property and evidence personnel of items that require review.

C

603

Ability to generate an owner notification letter based on disposition status.

C

604 Ability to alert property and evidence personnel of property items eligible for disposition. C

605

Ability to add disposal information to a property record, including but not limited to:

606 Disposal method C

607 Disposal date C

608 Disposal reason C

609

Ability to track the information associated with property released to an owner, including but not limited to:

610 Released to C

611 Released by C

612 Date of release C

613 Electronic signature C

614

Ability to generate a property destruction report that identifies:

615 All Property C

616 Property Associated with a Case C

617 Specific property C

618 Eligible Destruction Date C

619 Review Date C

620

Ability to require multiple levels of approval prior to property becoming eligible for disposal.

D

621

Ability to produce scheduled reports showing property eligible for disposal.

C

622

Ability to generate a report of property eligible for return to owner.

C

623

Ability to assign a batch disposition of all items by the following:

624 Date D

625 Bin location D

626

Ability to assign disposition of all items attached to a case at the same time.

C

627 Case Management

628 General Case Management Requirements


629

Ability for users to electronically send reports/updates to an investigator supervisor.

C

630

Ability for reports to be automatically sent to an investigator supervisor based on built-in agency business logic (e.g., crime type, last follow-up, ages of case...).

D

631

Ability for case management system to link all associated reports (e.g., incident report, supplemental reports, investigation reports).

C

632 Ability to establish case priority levels. C

633

Ability to establish case management work flow based on built-in business logic (e.g. incident type, priority or case type).

C

634

Ability to track member agency-defined case management activities.

C

635

Ability to provide narrative fields associated with each case.

C

636 Ability for each member agency to define the specific case management activities it wants to track. C

637 Ability to limit access to case information by security profile at the following levels:

638 Case level C

639 Case document level C

640 Field level C

641 Ability to limit modification rights to a case, including assigning rights to:

642 View C

643 Edit C

644 Print C

645 Delete C

646 Ability to provide an audit trail of case file access. C

647 Ability to support solvability ratings. O

648 Ability for each member agency to assign solvability rates and the system to calculate solvability. D

649 Have a feature within case reports which allows for tracking all tips, leads, and tasks associated with the case. O

650

Ability to provide a way to associate the person’s name record with all information related to that person and not require the user to back out of the name record to reach related information. C


651 Ability for the user to be able to view related records in full.

652

Ability to include a case management feature to track all cases assigned to officers, from initial incident through the completed investigation. D

653 Investigation Assignment

654 Ability for investigator supervisor to view unassigned cases online. C

655 Ability for investigator supervisors to review unassigned cases (e.g. read the reports) online. C

656 Ability for system to identify next due investigator when assigning a case. O

657 Ability to assign cases based on specialty area of investigation. D

658 Allow a user to assign leads to other users who are helping to gather information on the case. D

659

Allow for assigning a lead to an individual who doesn't have access to the full case report. The assignor can determine how much information about the case and lead should be granted to the assignee. The assignee will be allowed to add information to the leads assigned to them. D

660 Ability for an investigator supervisor to electronically assign case responsibility to an officer. C

661 Ability to assign multiple investigators to a case. C

662 Ability to assign review dates with an investigation assignment. D

663 Ability to distinguish roles for investigators (e.g. primary, secondary, etc.). D

664 Ability to assign solvability upon case assignment. O

665 Ability for investigators to receive electronic notification that they have been assigned a new case. D

666

Ability for investigator supervisors to reassign cases to different investigators.

C

667

Ability for investigator supervisors to reassign cases to different units.

C

668

Ability for investigator supervisors to electronically notify investigators of case reassignments.

D

669

The system should allow the priority or urgency of each lead to be assigned.

D


670

The system should allow leads assigned to individuals to be displayed on their dashboards

D

671 Case Monitoring

672 Ability for investigator supervisors to monitor case activity including, but not limited to:

673 Case status C

674 Responsible investigator C

675 Pending activities C

676 Overdue activities C

677 Ability for investigator supervisor to monitor investigators' workloads. D

678

Ability to support an internal case management communications/messaging system.

D

679

Ability to visually distinguish case status (e.g., by color, font, underline, italics, etc.).

D

680

Ability to visually distinguish case priority (e.g., by color, font, underline, italics, etc.).

D

681 Ability to produce a list of cases pending or past due. C

682 Ability to include a work-flow chart. C

683 Investigation Management

684 Ability for user to document member agency-defined case activity. C

685

Ability for all case activities to note user making entry into the system.

C

686 Ability to associate time with activities. C

687

Ability for an investigator to place an alert on an individual:

688

To send a notification to the investigator through the system of any query involving the individual

C

689

To send a notification via text message to the investigator's cell phone of any query involving the individual

D

690

To send a notification of any query on that individual without alerting the person making the query

C

691

To tell the person making a query on that individual to follow user inputted instructions (e.g., investigator placing the flag notes "call this number")

C

692

Ability to flag a property item such that the assigned investigator is notified when person makes inquiries on their property.

C


693

Ability to create an alert to determine when additional action is due (e.g., supplement report is due within 30 days of assignment).

C

694 Ability to query associated evidence with a case. C

695

Ability to link all associated reports to a single master file (e.g., a single search/location view of all reports related to the identical incident).

C

686

The system should ensure that intelligence case reports include all of the standard functionality and workflow as regular case reports.

D

687

The system should lock down the intelligence case reports so that only specified users have access to any of the data stored in those case reports. D

688

Ability to ensure that the intelligence case reports include links to warrants, protection orders, field identifications, other intelligence case reports and standard case reports. D

689

Connect to master name records which are associated with an intelligence report have an additional section of information which records information such as informant ID and the MO.

D

690

The system will allow authorized personnel to add and track notes on Informants to document all contacts with the individual.

D

691

The system should ensure that authorized users may choose to not submit intelligence cases to state reporting (IBR/UCR).

D

692

The system should allow Names, Offenses and Vehicles to be copied from an Intelligence Case into a normal case without the need to re-enter the information. D

693 Case Disposition

694 Ability to provide dedicated fields to track case disposition. C

695 Ability to provide dedicated fields to track Court case disposition. D

696 Ability to generate a face sheet that imports/includes Agency-defined data fields (such as to be provided to DA). D

697 Integration with eProtect (REQUIRED)

698

Ability to systematically choose which file types are attached to cases.

C

699 Ability to customized forms by agency. C


700

Ability for DA Referral and booking sheet to be created based off of subject sheet and charges.

C

701

Ability to create DA letters for "release" of property for felony, juvenile or property seized with a warrant.

C

697 Standard Case Management Module Outputs

698 Ability to produce the following standard reports:

699 Case aging report C

700 Assigned cases and status C

701 Cases pending assignment C

702 Activity follow-up C

703 Overdue activity (e.g. case assignment, follow-up) C

704 Pending activity by:

705 Investigator C

706 Case C

707 Unit D

708 Law enforcement case disposition C

709 Court case disposition D

710 Time/date range C

711 Cases by due date C

712 Traffic - Citations and Accidents

713 General Citations Requirements

714

Ability to capture all data required of citations as required by the State of Wisconsin

C

715

Ability to maintain compliance with State of Wisconsin data collection requirements as modifications are made by the state.

C

716

Ability to import citation data from the Wisconsin Badger TrACS citation system.

C

717 Ability to manually enter/update citation data. C

718

Ability to Manually add Humane Society and written citations and add attachements to the citation files

C

719

Ability to update citations with court disposition from Courts System.

D

720

Ability to import citation disposition information from Wisconsin Courts System.

D

721 Ability to produce a summary of citations by:

722 Location C

723 Offense code C

724 Date C


725 Time C

726 Officer C

727 allow citations to be associated with case reports or

created without a case report. D

728 allow users to save, print or email a summary list of

the citation records directly from the list-view window. O

729 support intelligent full-text searching of citation

narrative fields. O

730 allow citations to be manually linked to existing case

reports. D

731 Agency-defined custom fields should be available in

Field Identifications. O

732 Arrests

733 Allow users to create and maintain arrest forms. C

734

Support multiple charges for a given person on a single arrest form. C

735

Allow to add multiple counts of each statute on the arrest forms D

736

Arrests and multiple clearances automatically as specified for IBR reporting and link several cases to one arrest in the instance of multiple clearnaces C

737

Allow users to add an arrest form to a case report at the time of the original incident or any time after that. D

738

Allow users to add supplemental arrest narratives to the original case report in the event of an arrest at a later date.

D

739

Make the arrest information from the RMS available to the JMS for auto-populating the booking record. D

740 Parking Tickets

741

The system should allow parking tickets to be tracked. C

742

The system should allow authorized users to change the status of a parking ticket for any number of reasons defined by the agency.

D

743

The system should ensure that the name, vehicle and/or address entered into parking ticket records use the master records. Parking ticket records should also use the name and address validation provided with the master name and master address records.

D


744

The system should allow parking ticket statuses to be changed in bulk. D

745

The system should allow users to attach documents to parking ticket records. D

746

The system should track invoices, fees, and receipts associated with parking tickets. D

747

The system should allow for an agency-defined sliding fee scale based on parking ticket age. D

748

The system should provide a list of parking tickets that can be searched. D

749

The system should allow authorized users to create unlimited custom form templates which are used to associate agency-specified data with individual parking tickets.

D

750

The system should allow users with access to parking tickets to use the custom forms to enter and maintain the associated data.

D

751

Agency-defined custom fields should be available in Parking Tickets. D

752 General Crash Requirements

753

Ability to capture all crash data required as required by the State of Wisconsin

C

754

Ability to maintain compliance with State of Wisconsin data collection requirements as modifications are made by the state.

C

755 Ability to manually enter/update accident data. C

756

Ability to accept the import of accident data from the Wisconsin Badger TrACS system.

C

757 Ability to print imported accident reports. C

758 Ability to link citation records and accident records. C

759 Mug shot and Lineups

760 Ability to access mug shot photos from within the RMS that are stored in the JMS. C

761 Ability to select photos to create a line-up. C

762 Ability to drag and drop photos into a line-up. C

763 Ability to view a lineup as a slide show. D

764 Ability to replace a photo in a lineup. D

765 Ability to pre-select suspect for inclusion in photo line-up. C

766

Ability to select whether to print name and other data (law enforcement copy) or not (witness copy).

C


767

Ability for user to select which photo to use if individual has multiple photos on file.

C

768

Ability to indicate the most recent photo if an individual has multiple photos on file.

C

769

Ability to enter a photo and produce similar images for photo line-up purposes.

D

770 Ability for system to generate a line-up based on user criteria. D

771 Ability to view demographics on a person within the lineup. C

772

Ability to select and print discrete photos to print from mug shot query return:

773 6 Photos D

774 More than 6 Photos D

775

Ability to indicate in which position a suspect should be located.

C

776 Ability for system to randomly assign suspect position. D

777

Ability to prevent juvenile photos from being displayed in adult photo line-ups.

C

778 Ability to save line-ups and associate line-up with a case. C

779 Ability to print line-up. C

780 Ability to export line-ups (e.g., made available for email). C

781

Ability to save line-ups to alternative media (e.g., CD, thumb drive).

C

782 Ability to generate photo line-ups in black and white. C

783

Ability to query the mug shot database from the RMS for photos that are stored in the JMS by:

784 Name C

785 Age Range C

786 Gender C

787 Race C

788 Facial Hair C

789 Hair color C

790 Eye color C

791 Height C

792 Weight C

793 Height Range D

794 Weight Range D

795 Scars, marks, and tattoos C

796 Any physical characteristic D


797 Glasses C

798

Ability to generate a lineup based on any physical characteristic.

D

799

Ability to query lineups by any information associated with an individual, regardless if it is a physical characteristic (e.g., search on employer).

D

800 False Alarm Billing

801 General False Alarm Information

802

Ability to accept false alarm incident data from the CAD system.

C

803 Ability to manually add a false alarm incident. C

804

Ability to support a database of alarm systems with the following information:

805 Account Number C

806 Date registered C

807 Alarm Activity History C

808 Site Location/Address C

809 Billing Address C

810 Owner C

811 Tenants O

812 Alarm Company C

813 Alarm Company Contact Information C

814 Alarm Location C

815 Alarm Type C

816 Alarm status (active or suspended) C

817 Other agency-defined criteria D

818 Ability for system to generate an account number. C

819 Ability to delete a false alarm account. D

820 Ability to copy account history to another account. C

821

Ability to support multiple contact addresses and phone numbers for each account.

C

822 Ability to maintain a history of false alarms. C

823 False Alarm Billing/Receipt

824

Ability for the system to automatically generate associated costs for each false alarm and export information to Tyler-Munis Financial Application.

D

825

Ability for agency to define a fee schedule for false alarms (e.g., Alarm 1 = $0, Alarm 2 = $50, etc.)

C

826

Ability for the Agency to configure costs (i.e., Billing Rate) associated with each false alarm:

827 During implementation O


828

Following implementation, without vendor intervention

C

829

Ability to automatically "Zero" out the number of alarms at the beginning of each calendar year.

C

830

Ability for the system to dynamically maintain fees due to the Agency (e.g., individual has false three false alarm bills [$50, $100, $200], system shows $350 as opposed to the three individual totals).

C

831

Ability to record receipt of payment, including but not limited to the following information:

832 Account ID O

833 Incident number O

834 Amount paid O

835 Payment made by O

836 Method of Payment (multiple) O

837 Check/Money Order Number O

838 Invoice Number O

839 Date O

840 Ability to receipt partial payments O

841 Ability to void a bill. O

842 Ability to override fee schedule. C

843 Invoice & Form Generation

844

Ability to import invoice and payment information from financial system (Tyler-Munis)_.

D

845

Ability for any data element captured as part of the False Alarm module to become part of the invoice.

O

846

Ability for the Agency to determine which data elements must be captured as part of the invoice.

O

847 Ability for each invoice to have a unique invoice number O

848

Ability for the invoice generator to automatically extract necessary data to complete invoice including but not limited to:

849 Account Name O

850 Account Number O

851 Billing Address O

852 Address of Incident O

853 Date of Incident O

854 Time of incident O

855 Amount Due O


856 Number of Alarms for the Period O

857 Number of Alarms at no charge O

858 Number of alarms at each billing rate O

859 Fee Schedule O

860 Case number O

861 Date the invoice was generated O

862

Ability for generated invoice to include a narrative template designed by the Agency (e.g., to indicate instructions on how to submit payment). O

863 Ability to format invoices to fit in standard window envelope. O

864 Ability to re-print an invoice. O

865 Standard False Alarm Reports

866

Ability to generate a report of false alarms by any combination of information captured in the alarm tracking database, including but not limited to:

867 Date C

868 Account number C

869 Invoice number C

870 Name on Account C

871 Address of Account C

872 Case Number C

873 Incident Location C

874 Responding Agency C

875

Ability to generate reports on an on-demand basis, including but not limited to:

876 Daily C

877 Weekly C

878 Monthly C

879 Calendar year C

880 Internal Affairs

881 Ability to record the following against an employee:

882 Citizen Complaints O

883 Department Infractions O

884 Awards O

885 Accidents O

886 Use of Force O

887

Ability for each member agency to maintain its internal affairs database completely separate from each other agency

O


888

Ability to have a unique master name file in the Internal Affairs System.

O

889

Ability to support the import of data from other RMS modules but not share data to other RMS modules.

O

890

Ability to support a threshold alerting feature for different offense types, including but not limited to:

891 Accidents O

892 Complaints O

893 Discipline O

894 Use of Force O

895 Ability for threshold alerts to be unique for:

896 Each Member Agency O

897 Offense type O

898

Ability to alert a specified user when threshold has been met.

O

899 Ability to capture the following accident information:

900 Date of accident O

901 Time of accident O

902 Location of Accident O

903 Type of accident O

904 Officer name/rank/division O

905 Shift of accident O

906 Case Number O

907 Supervisor that investigated the accident O

908 Member agency that investigated the accident O

909 Disposition O

910

Indicate if the accident should be included in the threshold

O

911

Ability to capture the following information on commendations/awards:


913 Type of the commendation/award O

914 Date of the commendation/award O

915

Indicate if a copy of the commendation/award is on file

O

916

Ability to capture the following information on complaints:


918

Complaint type (formal, informal, fact finding, admin review, etc.)

O

919 Date the complaint was assigned O


920 Who the complaint was assigned to O

921 Date the investigation was completed O

922 Narrative O

923 Case Number O

924 How the complaint was reported O

925 Date the incident occurred O

926 Date the incident was reported O

927 How the incident was reported O

928 Indicate if the incident occurred off duty O

929 Name of person that took the complaint O

930

Complainant Name, Gender, Race, Address, Phone Number

O

931

Witness Name, Gender, Race, Address, Phone Number

O

932 Date Witness was contacted O

933 Type of Witness O

934 Name/Rank/Division of other officers involved O

935 Disposition of complaint O

936 Ability to capture the following information on disciplines:

937 Officer/rank/division O

938 Date O

939 Type of Discipline O

940 Incident Type O

941 Violation O

942 Description O

943 Outcome O

944 Internal Affairs Report Attachments

945 Ability to scan and attach documents to each record O

946

Ability to link (e.g., hyperlink, attach, etc.) a report to the internal affairs incident.

O

947

Ability to link all reports written by an officer to their Internal Affairs incident.

O

948

Ability to directly view incident reports from Internal Affairs module (e.g., through a hyperlink or attached file).

O

949 Internal Affairs Security

950

Ability to view and print a summary of all activity for an officer

O

951

Ability to record user name, date, and time each record was added, changed, viewed and printed in an audit trail.

O


952

Ability for the internal affairs module to have separate security access.

O

953 Internal Affairs Reports

954

Ability to view and print a summary of all activity during a user-specified time for:

955 Officer O

956 Agency O

957 Unit/Section O

958 Personnel

959 General Personnel Requirements

960

Ability to maintain separate personnel databases for each member agency.

O

961 Ability to provide fields to capture personnel information including, but not limited to:

962 Name O

963 Unit ID O

964 Employee ID O

965 Driver's License Number O

966 Driver's License Status O

967 Agency O

968 Hire Date O

969 Termination Date O

970 Promotion History (Start/End Dates) O

971 Emergency Contact Information O

972 Disciplinary Action:

973 Type O

974 Start O

975 Expiration O

976 Active/Inactive O

977 Rank O

978 Employee Status O

979 Evaluation Dates O

980 Address O

981 Phone Number O

982 Email Address O

983 Assignment O

984 Injury History O

985 Exposure History O

986 Date of hire O

987 Special Skills O

988 Ability to assign an employee to a "role". O

989

Ability for user to generate a report of pending Evaluation Dates.

O


990 Ability to attach a photo to a personnel record. O

991

Ability to generate a report of disciplinary action history (both active and/or inactive).

O

992 Ability to associate expirations with disciplinary action. O

993

Ability to generate a report of pending expiration dates for disciplinary action.

O

994

Ability to track all changes to personnel information (e.g., promotions, transfers), including but not limited to:

995 Date of change O

996 Person making change O

997 Before/after values O

998 Ability to attach files to a personnel record. D

999

Ability to maintain history of personnel information that may change over time (e.g., address, phone, etc.)

O

1000 Officer Activity

1001 General Officer Activity Requirements

1002

Ability to capture and maintain agency-defined officer activity information, including, but not limited to:

1003 Arrests

1004 Felony C

1005 Misdemeanor C

1006 Citations

1007 Traffic C

1008 Warnings C

1009 Parking C

1010 Misdemeanor C

1011 Field interviews C

1012 Warrants Served C

1013 Evidence Submittal D

1014 Self-initiated activity C

1015 Dispatched activity C

1016 Directed patrol activity C

1017 Reports filed (including type of report) C

1018 Role in response efforts (primary or backup) C

1019 False alarms D

1020 Administrative time D

1021 Time on duty C

1022 Overtime D

1023 Court time D

1024 Training time C


1025

Unlimited special activities, listed in an agency-defined drop down menu

C

1026 Ability to track the following call information by officer:

1027 Call type C

1028 Dispatch time C

1029 Call received time C

1030 Arrival time C

1031 Call clearance time C

1032 Disposition C

1033

Ability for CAD Call for Service information to automatically populate and update officer activity information.

C

1034

Ability for officers to add to their logs information that does not come from CAD.

C

1035

Ability to track officer time spent on agency-defined events (e.g., community meetings, training, foot patrol, special events) for statistical purposes (e.g., internal or grant related).

C

1036 Standard Officer Activity Module Outputs

1037 Ability to generate reports summarizing patrol activity by:

1038 Individual C

1039 Division C

1040 Timeframe (e.g., hour range) C

1041 Unit/Squad D

1042 Geographic Area (e.g., beat, grid) C

1043 Shift C

1044 Officer activity C

1045

Self-initiated or directed patrol versus dispatched activity

C

1046 Date range C

1047 Activity type C

1048

Ability to account for number of days working in summary statistics (e.g., arrests/day; tickets/day).

C

1049 Ability to generate reports itemizing patrol activity by:

1050 Type of activity C

1051 Date range C

1052 Officer non-committed time C

1053

Response times (based on dispatch, received, and arrival times)

C

1054 Ability to query individual officer activity by:


1055 Officer name C

1056 Officer assignment C

1057 Officer ID C

1058 Beat C

1059 Reporting district C

1060 Date/Time range C

1061 Incident type C

1062 Shift C

1063 Unit/Squad O

1064 Unit ID (call sign) O

1067

Ability to Query RMS Activity for the Records Division by date on the following:

1068 Incident Reports Completed D

1069 Crash Reports completed D

1070 Citations Entered D

1071 Civil Process Services Entered D

1072 Records Requests Completed D

1073 Background Checks Completed D

1074 911/Radio Traffic call request Completed D

1075 Training

1076 General

1077

Ability to support separate training databases by member agency.

D

1078 Ability to document training received by employee. D

1079 Ability to track mandatory training. D

1080

Ability to allow individuals to view (not edit) their training records.

D

1081

Ability to designate personnel with edit rights to modify training records (e.g., Training Officer).

D

1082 Ability to track certifications (e.g., TIME) D

1083 Training Documentation

1084 Ability to document the following Training information:

1085 Attendee D

1086 Hours D

1087 Cost D

1088 Course Description D

1089 Narrative D

1090 Location D

1091 Score (Pass/Fail) D

1092 Ability to associate costs with each training course. D


1093 Ability to associate reimbursable costs with training. O

1094

Ability to identify source of funding (e.g., grant, department funded).

O

1095 Ability to identify training provider (e.g., local, USDOJ, etc.) D

1096

Ability for costs to be associated with expenditures for each training course (e.g., meals, registration, etc.)

O

1097 Ability to associate expiration dates of training. D

1098

Ability to generate a report of training and associated expiration dates by:

1099 Member Agency C

1100 Individual C

1101 Ability to attach files to training records. C

1102 Instructors

1103 Ability to maintain a list of instructors. D

1104

Ability to document hours of instructional time per instructor.

D

1105 Ability to track recertification dates. D

1106

Ability to identify how an instructor became an instructor (e.g., Agency-funded, self-funded, third-party funded).

O

1107 Training Requirements

1108 Ability to track mandatory training requirements. D

1109 Ability to track mandatory training for each job category. D

1110

Ability to generate and print reports indicating upcoming training needs (i.e., who needs what training by what date).

D

1111

Ability to alert users and supervisors of upcoming certification expirations.

D

1112

Ability to track follow-up training for personnel who do not pass certification tests.

D

1113 Training Scheduling

1114 Ability to assign training to:

1115 Individual O

1116 Unit O

1117

Ability to generate a notification to participants of upcoming class information (e.g. class location, time, date, etc.)

O

1118

Ability to define type of training (e.g., in-service, specialized)

O


1119

Ability when entering attendees of training to generate a list of individuals that were scheduled but did not attend.

O

1120 Electronic Management

1121 Ability for individuals to request training electronically. D

1122

Ability for each member agency to define required supervisor approvals for training.

D

1123 Ability to post training information online. D

1124 Ability to associate files to training (e.g., .ppt, videos, etc.) D

1125 Training Reports

1126 Ability to retrieve training records by:

1127 Name D

1128 Group/Unit O

1129 Course D

1130 Assignment D

1131 Shift O

1132 Member Agency D

1133 Provider of Training D

1134 Ability to generate a report on training costs by:

1135 Individual D

1136 Group/Unit D

1137 Assignment D

1138 Shift O


1140 Course D

1141 Source (e.g., Grants, Department-funded) D

1142 Provider of Training D

1143 Fleet Maintenance

1144 General

1145 Ability to track Fleet maintenance C

1146 Ability to differentiate Fleet by member agency. C

1147 Ability to generate reports in accordance with Federal Automotive Statistical annual reporting requirements. D

1148 Ability to track multiple engines on one vehicle O

1149 Ability to provide Parent/Child asset tracking for asset components. O

1150 Ability to link vehicles with individuals. C

1151 Maintenance Tracking

1152

Ability to track all maintenance activity associated with a vehicle.

C


1153

Ability for agency to define the type of maintenance activities that are tracked.

C

1154

Ability to set agency-defined intervals for vehicles requiring maintenance by:

1155 Mileage C

1156 Date C

1157 Mileage and Date C

1158 Hours D

1159 Ability to associate warranty expirations with equipment. C

1160 Ability to designate warranty start dates. C

1161 Ability to associate equipment with vehicle. C

1162 Ability to maintain history of equipment assigned to a vehicle. C

1163 Ability to track vehicle damage, including but not limited to:


1165 Operator C

1166 Member Agency C

1167 Vehicle Type (e.g., make, model) C

1168 Type of Damage C

1169 Location of Damage C

1170 Cost of Damage C

1171 Repair Location (e.g., in-house or out sourced) C

1172 Ability to track out sourced repairs for vehicles. C

1173 Inventory

1174 Ability to track inventoried items.

1175

Ability for agency to define what type of items are tracked.

D

1176 Ability to associate inventoried items by member agency. C

1177

Ability to track location of equipment/inventory (e.g., bin #, shelf #).

D

1178 Ability to associate warranty expirations with inventory. D

1179

Ability for system to cross-reference vendor part numbers for identical pieces of inventory.

D

1180 Ability to track status of inventory:

1181 Active D

1182 Inactive D

1183 Issued D

1184 Ability to update inventory totals:

1185 Upon receipt of new inventory D

1186 Upon assignment of inventoried items D


1187

Ability to generate an automatic alert to designated personnel when inventory levels fall below member agency-defined level (e.g., threshold levels).

D

1188

Ability for agency to establish threshold levels per specific equipment/inventory/part.

D

1189 Ability to track vendor information:

1190 Company name D

1191 Contact Information D

1192

Ability to generate budget life cycle based upon user-defined time period and associated costs of Parts

D

1193 Ability to store images of parts. D

1194

Ability to manage and track inventory using a bar code system including, but not limited to, the following functions:

1195 Perform a mass update D

1196 Locate item by bar code O

1197 Generate bar code O

1198

Read bar code using remote or connected hand-held device

O

1199 Track specific item information O

1200

Ability to automatically update (e.g., download) inventory information into system.

D

1201 Ability to print bar code labels. D

1202 Ability to generate an inventory report by:

1203 Member Agency Assigned to D

1204 Vehicle Assigned to D

1205 Inventory on hand D

1206 Ability to track disposal of inventory. D

1207 Ability to track disposal methods specific to inventory type (e.g., how battery was disposed). O

1208

Ability to generate reports from disposed inventory (e.g., Run a report to identify number of wiper fluids used in a month) O

1209 Cost

1210 Ability to associate costs to:

1211 Inventory (e.g., equipment/parts) D

1212 Labor D

1213

Ability to generate a cost report associated to each member agency over a user-defined time period.

O

1214 Ability to associate a core value with inventory. O


1215

Ability to associate the receipt of core value of a returned item.

O

1216

Ability to establish a pre-determined report generation schedule for cost reports (e.g., once a month, generate a report for all repairs made to KSD vehicles). O

1217 Ability to generate a report of costs over a user-defined time frame by:

1218 Member Agency O

1219 Vehicle Type D

1220 Vehicle identification number D

1221 Vehicle Operator D

1222 Cost Category (e.g., Labor type) D

1223 Labor Scheduling and Assignment

1224 Ability to track the following for labor:

1225 Labor category (e.g., oil change) D

1226 Mechanic D

1227 Estimated Time for Completion D

1228 Actual Time Required D

1229 Parts used D

1230 Total Cost D

1231 Ability to run a report comparing actual time of repair vs. estimated time of repair. D

1232 Ability to track status of repair (in progress, pending, etc.) O

1233 Ability to stored recalled inventory/equipment/part information. D

1234

Ability for system to notify user, when performing maintenance on applicable vehicle, of applicable recall information. O

1235 Ability to provide a view (e.g., not a generated report) of work in progress, identifying:

1236 Status of Repair O

1237 Time Spent on Repair O

1238 Individual Conducting Repair O

1239 Estimated Time for Completion O

1240 Ability to track certifications of mechanics. O

1241 Ability for agency to define estimated lengths of required labor (e.g., oil change = 30 minutes) O

1242 Ability to assign labor tasks to specific individuals. O

1243 Ability to enter labor required and automatically generate time required for completion. O


1244 Ability for labor assignments to automatically populate a labor calendar. O

1245

Ability for system to automatically generate a labor schedule based on required labor and associated due date. O

1246 Ability to print work orders. O

1247 Ability to generate a labor workload report by:

1248 Labor Type O

1249 Member Agency Vehicle O

1250 Time Frame O

1251 Mechanic O

1252 Labor Status (e.g., in progress, complete) O

1253 Labor Requests

1254 Ability for member agencies to electronically request service. O

1255 Ability for individuals to electronically request service via the Mobile. D

1256 Ability for labor request to include:


1258 Vehicle Number D

1259 Repair Request D

1260 Narrative D

1261 User Requesting Service D

1262 Requested Date D

1263 Priority D

1264 Ability for each member agency to define required supervisor approval for repair request. O

1265 Fuel Management

1266 Ability to track fuel related data and costs within the software D

1267 Ability to provide an interface to Phoenix Systems to import fuel and vehicle usage. D

1268 Intelligence

1269 General Intelligence Requirements

1270 System is 28 CFR Part 23 Compliant. C

1271

Ability to support separate intelligence databases per member Agency. C

1272 Ability to limit access to intelligence database. C

1273

Ability for intelligence to place an alert on an individual (e.g. for deconfliction purposes):

1274

To send a notification to intelligence user through the system of any query involving the individual

C


1275

To send a notification of any query on that individual without alerting the person making the query

C

1276

To tell the person making a query on that individual to follow user inputted instructions (e.g., investigator placing the flag notes "call this number")

C

1277

Ability for intelligence to place an alert on a location (e.g. for deconfliction purposes):

1278

To send a notification to intelligence user through the system of any query involving the location

C

1279

To send a notification of any query on that location without alerting the person making the query

C

1280

To tell the person making a query on that location to follow user inputted instructions (e.g., investigator placing the flag notes "call this number")

C

1281

Ability to track tips including but not limited to the following:

1282 Date C

1283 Source C

1284 Narrative C

1285 Category (e.g., Gang) C

1286 Intelligence Investigations Activity

1287

Ability to provide case management functionality for intelligence-related investigations, but have intelligence-related investigations secured separately from other investigation types. C

1288

Ability to establish Intelligence investigations groups/units (e.g., Gangs, Narcotics). C

1289 Ability to track workload activity of each specialty unit.

C

1290

Ability to provide message board functionality for each Intelligence investigation unit. C

1291 Gang Members

1292

Ability to flag individuals as confirmed or suspected gang records in the Master Name Index.

O

1293

Ability to distinguish between confirmed and suspected gang members. O

1294

Ability to capture criteria used to identify an individual as a gang member. O


1295

Ability for gang information to be made available in the JMS. O

1296

Ability to auto-populate the gang database with information from the MNI once an individual is identified as a gang member. O

1297

Ability to prompt officer to forward gang information to an investigator when new information is entered into member agency-defined fields.

O

1298 Ability to manually remove gang flags. O

1299 Ability to provide security provisions at the user level to:

1300 Create gang records O

1301 Modify gang records O

1302 Label individual as a gang member O

1303

Ability to prevent gang information from displaying on main name record. O

1304

Ability to support an interface to NCIC to transfer agency-defined gang information based on Agency-defined criteria. O

1305

Ability to provide dedicated fields to capture the following gang-related data:

1306 Member Name O

1307 Date of Birth O

1308 Gender O

1309 Race O

1310 Ethnicity O

1311 Known Associates O

1312 Height O

1313 Weight O

1314 Hair Color O

1315 Eye Color O

1316 Gang Name O

1317 Street Name/Nickname O

1318 Street Address O

1319 Phone Number O

1320 Employer O

1321 Employer Address O

1322 Work Phone O

1323 Occupation O

1324 Active Member (Y/N) O

1325 Physical Appearance

1326 Hand Use O

1327 Teeth O


1328 Build O

1329 Glasses O

1330 Demeanor O

1331 Speech O

1332 Physical Condition O

1333 Scars, marks and tattoos O

1334 Facial Hair O

1335 Appearance O

1336 Clothing O

1337 Hair Style O

1338 Ability to track associates of gang members. O

1339

Ability to provide dedicated fields to capture the following gang associate data:

1340 Name O

1341 Aliases O

1342 Date of Birth O

1343 Social Security Number O

1344 Gender O

1345 Race O

1346 Ethnicity O

1347 Height O

1348 Weight O

1349 Hair Color O

1350 Eye Color O

1351 Relationship O

1352 Address O

1353 Phone Number O

1354 Employer O

1355 Employer Address O

1356 Work Phone O

1357 Occupation O

1358

Ability to limit access to member agency-specified fields, including photos, within the gang database by:

1359 Individual O

1360 Rank O

1361 Agency O

1362 Ability to identify juvenile gang members. O

1363 Pawn Property

1364

Allow users to create and maintain pawn property records. D


1365

Allow users to attach digital photos to a pawn property record, either via an upload or directly from a camera. D

1366

Allow pawn property records to have files attached to them via upload or scanner. D

1367

Allow users to save, print or email a summary list of the pawn property records directly from the list-view window. D

1368

Allow users to save, print or email a pawn property record directly from the record window. D

1369

Support intelligent full-text searching of pawn property narrative fields. D

1370

Agency-defined custom fields should be available in Pawn Property. D

1371 K9

1372 K9 Training and General Features

1373 Ability to track K9 training within the RMS. D

1374 Ability to provide dedicated fields to capture K9 tracking information including, but not limited to: D

1375 K9 Name D

1376 Handler Name D

1377 Date of Birth D

1378 Medical History D

1379 Date of Vaccinations D

1380 Skills (e.g., drugs, bomb, etc.) D

1381 Retirement Date D

1382

Ability to document the following training related to each K9:

1383 Training Hours Received D

1384 Training Type D

1385 Training Provider Name D

1386 K9 Certifications D

1387 K9 Activity

1388 Ability to track incidents in which K9 was involved. D

1389

Ability for field reporting software to automatically update K9 module whenever a K9 is involved with an incident that results in a report. D

1390 K9 GPS Capability O

1391 Standard K9 Reports

1392 Ability to generate a report of individual K9 details.

D


1393 Ability to generate a report summarizing K9 activity by:

1394 K9 Name D

1395 Handler Name D

1396 Time of Day D

1397 Specified Geographical Area D

1398 Receipt and Billing

1399 General

1400 Ability to provide an Accounts Receivable module. O

1401 Ability for system to exchange information with Tyler-Munis financial system O

1402 Ability for system to link billable activities with individuals and/or businesses. O

1403 Ability to provide a dynamic ledger. O

1404 Ability for ledger to generate a balancing report at end of shift. O

1405 Ability to receipt unlimited number of types of transactions O

1406

Ability for transaction/billable activity to link to report regarding specific activity (e.g., warrant cost could access warrant information). O

1407

Ability for the data elements of a linked report (related to a transaction/billable activity) to be eligible for a data export. O

1408 Ability for each transaction to record:

1409 Receipt number O

1410 Applicable Court (for fee forwarding) O

1411 Future Court Dates O

1412 Payer Information (e.g., name, address, etc.) O

1413 Defendant Information O

1414 Date O

1415 Amount Due O

1416 Method of Payment O

1417 Actual Payment Receipt O

1418 Comments O

1419 Billing

1420 Ability to create user accounts. O

1421 Ability to produce quarterly detailed billing statements O

1422 Ability to produce quarterly detailed (or itemized) billing statements O

1423 Ability to choose to assess postage and handling costs or not O


1424 Allow for multiple costs per page O

1425 Receipting

1426 Ability to print a receipt for a charge transaction O

1427 Ability to receipt Copies O

1428 Ability to print receipts and duplicate receipts O

1429 Ability to set permissions by user and agency O

1430 Ability to void a receipt O

1431 Ability to receipt multiple forms of payments per receipt (i.e., cash, check, money order, credit cards) O

1432 Ability to assign each bond receipt transaction to a Court. O

1433 Ability for each Court Officer to print duplicate individual receipts. O

1434 Trust Accounts

1435 Ability to set up trust accounts. O

1436 Ability to follow proper accounting procedures O

1437 Receipt and Billing Reports

1438

Ability to generate a report against a user-defined time range of bonds and fines displaying any combination of the following information:

1439 Agency O

1440 Court Number O

1441 Citation Number O

1442 Ordinance Violation O

1443 Payer Information O

1444 Payment Record O

1445 Ability to generate a receipt report against a user-defined time range that documents fee activities. O

1446 Warrants and Protection Orders

1447 Ability to enter warrants for multiple agencies. C

1448 Ability to enter caution/risk information on an individual .

C

1449

Ability to visually notify users when there is a caution/risk associated with an individual. C

1450

Ability to enter an unlimited number of warrants and protective orders associated with an individual.

C

1451

Ability to associate mug shots with an individual regarding Warrants and Protection Orders. C

1452

Ability when entering a Warrant or Protection Order to automatically query the JMS for incarceration status.

C


1453

Ability to associate status with Warrants and Protection Orders. C

1454

Ability to enter user-defined warrant status codes to each warrant (i.e. reactivate, pending, inactive, active, recalled)

C

1455

Ability to import documents and attach them to a warrant or protection order record. C

1456

Warrant application has all fields necessary for completion of NCIC/CIB entry C

1457 Ability to submit NCIC/CIB data directly from the RMS.

C

1458

Ability to capture the circumstances of service (i.e. voluntary, law-enforcement initiated, etc.) C

1459 Ability to associate multiple statutes to a single warrant.

C

1460

allow separate numbers, such as NCIC, docket, state case, or OCA to be included in the warrant record.

D

1461

Generate standard letters for warrants indicating different types D

1462

Reports on Open and Cancelled Warrants within specifice timeline D

1463

Automatically alert call takers and officers when they come in contact with someone with a warrant

D

1464 Users should be allowed ot make notes on the warrant

O

1465

Allow for creating workflow for warrants to go to validators O

1466

1467

1468 Warrant and Protection Order Service

1469 Ability to provide dedicated fields to track due diligence/service attempt history:

1470 Date of attempt C

1471 Time of attempt C

1472 Location of service C

1473 Person(s) served C

1474 Attempt successful (y/n) C

1475 How served (personal, substitute, etc.) C

1476 Service (attempt or actually served) C

1477 Officer number C

1478 Number of attempts C

1479 Method of service C


1480

Ability to automatically query the following CIB/NCIC databases when entering a name into a warrant document:

1481 NCIC D

1482 WI DOT D

1483 Out of State DOT D

1484 WI Criminal History D

1485 Out of State Criminal History D

1486 FBI Criminal History (III) D

1487 Ability to submit, supplement, modify and cancel warrant information into the TIME system from the RMS. D

1488 Ability to support an in interface with C-CAP to import information regarding orders of protection. D

1489 Civil Process Service

1490

Ability for agency to define Civil Document types (e.g., Foreclosure orders, Divorces, Subpoena, etc.)

C

1491 Ability for system to generate Civil document service numbers. C

1492 Ability to add/modify information after original civil service data entry. C

1493

Ability to provide dedicated fields to capture the following Civil Document information:

1494 Civil/Case Number C

1495 Plaintiff C

1496 Defendant C

1497 State C

1498 County C

1499 Date Issued C

1500 Expiration Date C

1501 Court Information C

1502 Type (Civil, Criminal) C

1503 Description C

1504 Status C

1505 Date Served C

1506 Employer Information C

1507 Attorney Information:

1508 Attorney Name C

1509 Firm C

1510 Phone Number C

1511 Address C

1512 Number to Serve C


1513 Entered by C

1514 Information regarding person being served:

1515 Phone Number C

1516 Address C

1517 Date of Birth C

1518 Sex C

1519 Race C

1520 Height C

1521 Weight C

1522 Hair Color C

1523 Eye Color C

1524 Aliases C

1525 Driver's License Number C

1526 Special Instructions C

1527 Caution Data or Officer Safety Informaton D

1528

Ability to determine which fields are required based on civil document type. C

1529

Ability for Agency to add or modify data fields as necessary. C

1530

Ability to document person entering Civil Paper document:

1531 Name C

1532 Date Entered C

1533 Time Entered C

1534 Ability to attach a file to a civil document. C

1535 Ability to track status of civil documents. C

1536

Ability to capture and maintain protection order data as required to conform to NCIC 2000 Protection Order File format (or later) and meet TIME system requirements.

O

1537

Ability to update master indices upon entry a civil document or protective order. C

1538

Ability to automatically flag an individual in the master name index upon entry of an associated civil document.

D

1539

Ability to automatically remove flag when associated civil document has been successful served.

D

1540

Ability for the system to automatically query the RMS when entering a name into the Civil module.

C

1541 Ability to associate Civil documents with issuing agency.

O


1542 Ability to associate civil documents with an address.

C

1543

Ability to automatically query the JMS to identify custody status of individual when entering name into the Civil module. D

1544 Civil Process Service Accounting

1545 Ability for agency to define service fees and associate fee with civil document type. C

1546 Ability to generate associated cost fee when document has been served. O

1547

Ability to associate fees with specific tasks related to civil document service (e.g., Deputy standby time, Extra Charge, etc.). D

1548 Ability for system to total all fees associated with civil document service. C

1549 Ability to capture civil process prepaid payments (and associated accounts). O

1550 Ability to capture deposits on civil process papers. O

1551 Ability to capture the following in regards to the payment:

1552 Person Providing Payment O

1553 Payment Type (Cash, Credit, etc.) O

1554 Associated Case Number O

1555 Associated Civil Information (e.g., plaintiff,

defendant) O

1556 Activity Type (e.g., Deposit) O

1557 Amount O

1558 Comments D

1559 Ability to generate a unique number for each transaction. O

1560 Ability to associate TYLER-MUNIS a ledger account number with the pre-payment and/or deposit C

1561 Ability to automatically apply pre-payments to an invoice O

1562 Ability to automatically apply deposit amounts to an invoice . O

1563 Ability to print receipts for payments. O

1564 Ability to define a ledger account for each civil process paper. O

1565 Ability to apply partial payments to invoices. O

1566 Ability to support multiple forms of payments. O


1567 Ability for payments occurring (i.e., receipt for deposit) on different dates to be noted within the system. O

1568 Ability to zero out an invoice when a civil process is returned as uncollectible O

1569 Ability to apply a payment to multiple invoices O

1570 Ability to easily query customer balances O

1571 Ability to print customer statements individually or in bulk O

1572 Civil Control Sheet

1573 Ability to print a cover sheet containing the following:

1574 Civil paper type C

1575 Date received C

1576 Case number C

1577 Instructions C

1578 Defendant Information C

1579 Court date and Time C

1580

Ability for any data element captured as part of the Civil Paper module to be printed on the cover sheet.

O

1581 Civil Document Service

1582 Ability to provide dedicated fields to track due diligence/service attempt history:

1583 Date of attempt C

1584 Time of attempt C

1585 Location of service C

1586 Person(s) served C

1587 Attempt successful (y/n) C

1588 Indicate type service (Personal, Corporate) D

1589 How served (personal, substitute, etc.) C

1590 Service (attempt or actually served) C

1591 Officer number C

1592 Number of attempts (Should be virtually unlimited)

C

1593 Method of service C

1594 Notes Areas for misc information C

1595

Ability to generate and print a history of civil document service. C

1596

Ability for administrative officer to input notes/instructions onto the document for view by public safety officer serving the document. C

1597

Ability to generate affidavits after service of civil documents. C


1598 Ability to store multiple affidavit types. C

1599 Ability for agency to define affidavit types. C

1600 Ability to print affidavit information. C

1601 Service in Mobile Environment

1602

Ability for deputies to receive service assignments on their mobile computers. D

1603 Ability for deputies in the field to document service activity on their mobile computers. D

1604 Ability for deputies to search service activity based on civil process/case number in the mobile environment. D

1605

Ability for data entered in the mobile environment to update the Civil Paper record in the JMS.

D

1606 Letter & Form Generation

1607

Ability to have a letter generator within the Civil Service module C

1608

Ability to Merge information into the letter from the law firm or requestor C

1609

Ability for any data element captured as part of the Civil service module to be used on the letter. C

1610

Ability for the Agency to determine which data elements must be captured as part of the letter. C

1611

Ability for the letter generator to automatically extract necessary data to complete letter including but not limited to:

1612 Name C

1613 Document Type C

1614 Date Due C

1615 Fee C

1616 Description C

1617

Ability for generated letter to include a narrative template designed by the Agency (e.g., to indicate instructions on how to submit payment). C

1618 Civil Queries and Reports

1619 Ability to query Civil Paper records by any combination of:

1620 Assigned deputy C

1614 Entry Person (who ever entered Civil Process) C

1615 Geographic area C

1616 Date range C

1617 Type of document C

1618 Process expiration date C

1619 Involved party C


1620 Service status C

1621 Court case number C

1622 Ability to generate the following standard reports:

1623 Expired protection orders C

1624 Soon-to-expire protection orders (based on user-

defined time period) C

1625 Soon to expire all Civil Process Documents C

1626 Protection orders that have been served C

1627 Cancelled protection orders C

1628 Summary of deputy service for a date and time range D

1629 Summary of civil papers served C

1630 Summary of civil papers that were not served C

1631 Sheriff Sales

1632 Report on open and closed foreclosure Sales C

1633 Sheriff Sale Template for Services Sheet D

1634 Customize defined fields for Sheriff Sales D

1635 Ability to add bids to the Sheriff Sales in the system

and save documentation from law firm O

1636

System integrates with County Website to upload Sheriff Sale Documents as they are entered and removes them at the date of the sale O

E-5 Computer Aided Dispatch (CAD) Functional Requirements E-5.1 Questions- None

E-5.2 Requirements-


CAD Software Requirements


Item #


1 General CAD Requirements

2 Ability to accommodate multi-disciplinary call taking and dispatching Law Enforcement, Fire, EMS

C

3 Ability to dispatch both fire/EMS and law enforcement units from the same CAD window.

C


4 Ability to limit dispatch to only fire/EMS or only law enforcement from a single CAD window.

C

5 Ability to comply and maintain compliance with published NENA NG-911 standards.

C

6 Ability to capture all CAD transactions in an audit log.

C

7 Ability to support multiple monitors. C

8 Ability to swap users without logging off system. D

9 Ability for system to automatically generate an incident number.

C

10 Ability for each member agency to have a unique identifier regarding incident numbers (e.g., all PTSO related events have "S20-" as prefix).

C

12

Ability to designate workstation roles and limit modification/data entry features (e.g., a member agency supervisor may view incidents only but not modify incidents).

C

13 Ability to support remote access to the CAD. C

14 Ability to perform the following via remote access:

15 Monitor and create Incidents C

16 Run Queries, Monitor AVL units, Dispatch

Incidents C

17 Application User Interface

18 Ability to customize the graphical interface at the following levels:

19 User and Agency C

20

Ability to customize the following: (Note: if certain features are customizable at only the user or agency level, indicate as such in the "Comments" field):

21 Font size, type, colors C

22 Window background color, sizes, and

locations C

23 Order in which fields are displayed C

24 Ability for agency to configure which options are configurable by the user.

C

25 Ability for agency to define fields that are mandatory to display in status windows.

C

26 Ability for user to enlarge and shrink columns in their status windows.

C

27 Ability to save windows configurations based on user IDs (e.g., not workstation-specific).

C

28 Ability to reset configuration to default settings. C


29 Ability to maintain configuration settings during upgrades.

C

30 Ability to support Windows-like functionality, including but not limited to:

31 Minimize/Maximize Windows C

32 Multiple Windows open simultaneously C

33 Tile/Cascade Windows. C

34 Ability to display system messages without affecting work in progress.

C

35 Ability to display one or more status windows at the same time.

C

36 General Data Entry

37 Ability to support data entry via:

38 Mouse (point and click) C

39 Command line entry C

40 Preformatted data entry screens (e.g.,

dedicated data fields) C

41 Ability to click on the map and pull the location into the address field.

C

42 Ability to provide type ahead capability such that the user can continue entering data while the system is processing a previous transaction.

C

43 Ability to support drop down menus and auto completion

C

44

Ability to provide word processing capabilities on narrative and comment fields, including, but not limited to Text Wrap, paragraph formatting, bullets, and numbering, copy and paste, grammar check.

C

45 Ability for new call notes to appear at the top of the call notes section.

C

46 Time Stamps

47 Ability to automatically time stamp all activities. C

48 Timers

49

Ability to configure incident timers and alerts based upon member agency-defined parameters (e.g., type of incident, unit arrival time, priority status which are unique to each dispatched agency) and times.

C

50 Ability to associate timers with: Unit Status updates, Incident type, response time, Incident status and priority type.

C

51 Ability to alert user to the expiration of the timer via:


52 Audible and visual alert C

53 Ability to configure the alerts to repeat at member agency-defined intervals until the timer has been reset. C

54 Ability to manually set incident timers and alerts. C

55 Ability to display call timers on CAD screens. C

56 Ability to record acknowledgement of timer alert.

C

57 Ability to Modify to new time value, reset or

stop timer. C

58 Flags and Alerts

59

Ability, upon entering an address, to automatically present user any visual or audible flags/alerts associated with the address, including but not limited to:

60 Hazard and Premise history information C

61 Ability to require dispatchers to acknowledge that they have viewed hazards.

C

62 Ability when querying a name for user to be notified of an associated alert (e.g., if a person was flagged in the RMS, if a person is wanted via NCIC).

C

63 Ability for flags/alerts to be dynamic (e.g., user can click on flag for additional information).

C

64 Ability to provide incident history of address when creating an incident.

C

65 Ability for users to sort summary of past incidents by:

66 Chronological order (most recent call shown

first) C

67 Call type C

68 Ability to add a temporary flag, comment or note to a location.

C

69 Ability for user to add a flag/alert. C

70 Ability to associate an expiration with a flag/alert. C

71 Ability to notify personnel of pending expiration of a temporary flag.

D

72 Ability to include flagged information with dispatches sent to responding units.

C

73 Ability to flag an incident. C

74 Ability to forward a flagged incident to a specific user.

C

75 Call Taking

76 Call Receipt


77 Ability to receive call data from:

78 E9-1-1 phone system C

79 Private alarm companies (ASAP) C

80 TDD/TTY C

81 Call Data Entry

82 Ability to enter incidents using preformatted screens.

C

83 Ability for Agency to determine order of fields in preformatted screen.

C

84 Ability for Agency to determine what data elements are captured as part of the preformatted screen.

C

85

Ability to capture all incoming call information from the E9-1-1 system (Note: Information that cannot be transferred into the CAD application should be indicated in the "comments" field).

C

86 Ability to automatically populate CAD screen with information from E9-1-1 application (no manual intervention required).

C

87 Ability to populate CAD screen with information from E9-1-1 application via manual intervention (e.g., function key, mouse click).

C

88 Ability for narrative fields to have the following attributes unlimited number of characters

C

89 Ability to enter standard information in defined fields for the following:

90 Individuals (caller, witness, suspect) C

91 Vehicle C

92 Location C

93 Ability for Agency-defined fields to automatically query the Wisconsin TIME system and attach to call record.

C

94 Ability to generate an incident from a previous incident.

C

95 Ability for call taker and dispatcher to work on the same call for service simultaneously.

C

96 Ability for call taker to add comments to a call after it has been dispatched and automatically update the dispatchers screen.

C

97 Ability to alert dispatcher that the call taker has added information by:

98 Audible alert C

99 Visible alert C

100 Location Capture


101 Ability to receive geographic coordinates from a cellular telephone carrier.

C

102 Ability to relate X/Y coordinates to an actual address.

C

103 Ability to transform X/Y coordinates to a map for display.

C

104 Ability to capture incident location separately from caller location.

C

105 Ability to capture multiple locations outside of caller location.

C

106 Ability to enter a location for an event via:

107 Street address C

108 Block number or address range C

109 Commonplace name C

110 Intersections C

111 X/Y coordinates C

112 Point and click on a map C

113 Ability to type in either street first when entering intersections.

C

114 Ability to save identical intersection names with different address points.

C

115 Ability to parse address data into the following elements:

116 Street number C

117 Street name C

118 Street prefix C

119 Street suffix C

120 Street type (Ave, Ln) C

121 Unit type C

122 Unit number C

123 City C

124 Ability to capture the following information upon receipt of a wireless 9-1-1 call:


126 Closest street address C

127 Nearest cross street C

128 Location Verification

129 Ability to geoverify location of all entered addresses.

C

130 Ability to override geoverified location. C

131 Ability to validate an entry upon:

132 Operator request (e.g., press a button) C

133 Entry into location field C


134 Ability to create a report of all overridden geoverified locations.

C

135 Ability upon address verification for system to auto-populate associated fields (e.g., zip code, town, etc.)

C

136 Ability for addresses entered by field units (e.g., on a self-dispatch) to correctly populate all address fields in the CAD record. C

137 Ability to support Phase I wireless location validation from cellular callers.

C

138 Ability to support Phase II wireless location validation from cellular callers.

C

139 Ability to use the ALI reported location address for address verification.

C

140 Ability to use the coordinate-based geofile to determine if there are premise or hazard records within a defined radius of the call.

C

141 Ability to enter a street name and be presented with:

142 Aliases C

143 Associated address ranges C

144 List of cross streets C

145 Ability to automatically display the following upon entry of a verified address:

146 High/low cross streets C

147 Common place names C

148 Business name C

149 Police Response Area C

150 Fire Response Area C

151 EMS Response Area C

152 Apartment complex names D

153 Ability to translate call location to appropriate public safety geographical boundary (e.g., district, beat, sector).

C

154 Ability to translate alias names to actual street names or addresses.

C

155 Ability to enter a commonplace name and be presented with a list of addresses with that commonplace name (e.g., McDonald's search)

C

156 Ability to notify user through a visual and/or audible flag if multiple street addresses/street names/intersections are found in geofile.

C


157 Ability to offer a list of address options if multiple similar addresses/intersections/street names are found in geofile.

C

158 Ability to display, on a map, the incident location in relation to other active incidents on the map during the incident entry process.

C

159 Ability to manually verify an address without creating an event.

C

160 Call Classification and Prioritization

161 Ability to display a drop-down list containing call types.

C

164 Ability for user to override associated priority. C

165 Ability to change call type without impacting active call data. C

166 Incident Initiation

167 Ability to initiate an incident from the input of location and type code.

C

168 Ability to input all call and narrative information on one screen.

C

169 Ability to display a blank form for entering new incidents with a single keystroke, mouse click or function key upon initiation of a CAD incident.

C

170 Ability to enter incidents using:

171 Standard call entry screen form C

172 CAD command on a command line C

173 Ability to suspend the entry of an incident prior to initiation

C

174 Ability to support multiple partially complete incidents.

C

175 Ability for call for service record to indicate if call data entry was suspended.

C

176 Ability to timestamp suspension and reactivation of call entry.

C

177 Duplicate Call Management

178 Ability to identify and flag potential duplicate calls. C

179 Ability to display proximity calls on a map (e.g., to assist dispatchers in identifying possible duplicate calls).

C

180 Ability for Agency to define parameters of duplicate call identification (e.g., defined proximity, definition of "recently closed", etc.).

C

181 Ability to provide the user with incident details about possible duplicate incidents

C


182 Premise Information Retrieval

183 Ability to automatically initiate, upon address verification, an address inquiry to search for associated premise information in CAD.

C

184 Ability for premise information searches to query for flagged information in the Law RMS.

C

185 Ability to search for premise information based on:

186 Address C

187 Sub-address (e.g., unit number, building floor,

apartment number) C

188 Partial address information (e.g., all addresses

with apartment 14) C

189 Block ranges C

190 Current business name C

191 Historic business name (unlimited number) C

192 Common place names C

193 Intersections C

194 Ability to search for premise information on locations not associated with incidents.

C

195 Ability to automatically show premise history related to a current incident.

C

196 Ability to indicate the number of past incidents at a location.

C

197 Ability to retrieve and attach to a CAD call any information associated with the premise (e.g., pre-plan information, previous calls for service).

C

198 Ability for map to display all known hazards within a user-defined radius.

C

201

Ability for premise information to be available to user but not prevent operator from continuing current work (e.g., window does not cover entire workstation screen).

C

202 Incident Scheduling

203 Ability to enter incidents scheduled for dispatching at a later time, maintaining the original time of entry.

C

204 Ability to modify incidents scheduled for dispatching at a later time, maintaining the original time of entry.

C

205 Ability for scheduled incident to automatically enter the pending queue.

C


206 Ability to cancel incidents scheduled for dispatching at a later time maintaining the original time of entry.

C

207 Ability to stack scheduled incident calls. C

208 Ability for officers to self-dispatch to scheduled incidents. C

209 Ability to visually distinguish and display scheduled incidents.

C

210 Non-Dispatched Incidents

211 Ability to record incidents in which no dispatch occurs.

C

212 Ability to re-open a non-dispatched incident. C

213 Ability for non-dispatched incidents to be excluded from status windows (e.g., pending).

C

214 Ability to associate a unit with a non-dispatched incident.

C

215 Differential Response Questionnaire

216

Ability to support an interface with an EMD system in which the EMD system is automatically launched upon entry of a call type and actions taken are associated with the incident record. In the "comments" field, indicate with which EMD products the vendor has successfully provided an interface.

C

217 Dispatching

218 CAD Incident Retrieval

221

Ability to cause a distinct audible and/or visual alert on the dispatcher's screen to indicate any change in the incident (e.g., comments added, location change): D

222 Ability to retrieve a CAD incident and review all available information already entered up to the point of incident retrieval.

C

223 Ability to keep incidents in pending queue indefinitely.

C

224 Ability to sort pending incidents by priority, location, incident type, and time in pending.

C

225

Ability to associate timers with call priority in pending queue (e.g., alert user after 5 minutes in pending queue if Priority 3 call, 2 minutes if Priority 2 call, etc.).

C

226 Resource Recommendation


227 Ability to automatically provide appropriate resource recommendations based on any combination of:

228 AVL location C

229 Beat/Location responsibility C

230 Natural boundaries C

231 Obstacles C

232 Traffic C

233 Speed limits C

234 Street network C

235 Street direction C

236 Equipment Required C

237 Incident location C

238 Incident type C

239 Occupancy type (e.g. residential, office

building) C

240 Priority C

241 Pre-defined response plans (response area

plan) C

242 Run order C

243 Special conditions (e.g., heightened response) C

244 Special Skills required C

245 Type of units required C

246 Number of units required C

247 Unit status C

248

Ability to determine resource recommendation factors based on unique response plans per Member Agency (e.g., PTSO recommends 2 units for an incident SPPD recommends 3 units).

C

249 Ability to prioritize unit response based on incident type so that appropriate units are automatically recommended and/or dispatched in priority order. C

250 Ability to recommend units from multiple agencies. C

251

Ability for each member agency to have a unique identifier, but share the same incident number when dispatched to the same event (e.g., in responding to the same incident, PTSO receives "WPD-001" while SPPD receives "MNSO-001"). C

252 Ability to re-recommend closest units (e.g., a new unit comes into service). C


253

Ability for system to update the unit recommendation if user makes relevant incident information changes (e.g., call type, location, alarm level).

C

254 Ability to visually alert user when system updates unit recommendation.

C

255 Ability to record the unit recommendation as it was presented to the dispatcher.

C

256 Ability to query the system for unit recommendation without creating an incident (e.g., verifying a response plan).

C

258 Ability to create and track temporary units (e.g., mutual aid response).

C

259 Run Orders

260 Ability to enter response plans or run cards with predefined responses to any combination of the following:

261 Specific Address C

262 Address Type C

263 Address Range C

264 Incident Type C

265 Agency-defined geographic areas C

266 Ability to enter response plans or run cards specific to a member agency. C

267 Ability for agency to define response areas using polygon/drawing tool. C

268 Ability to have multiple levels of response or alarm levels for each incident.

C

269 Ability to incorporate move-ups as part of a run order.

C

270 Ability to print run cards. C

271 Ability to assign multiple alarm levels for run cards. C

272 Ability to define a date/time range that a run card is active.

C

273 Ability to have multiple backups continually checked so that backup units are always recommended in the order set up.

C

274 Ability to add special response narratives to run cards (e.g., pre-arrival instructions).

C

275 Ability to modify run cards. C

276 Ability to support multiple sets of run cards and run orders and allow agency to swap run cards/run orders on-the-fly.

C


277 Ability to associate MABAS (Mutual Aid Box Alarm System) recommendations with Run order.

C

278 Special Skills

279 Ability to bring up a list of special skills/equipment for all personnel logged on, specific person or vehicle

C

280 Ability to identify all personnel with a specific skill (e.g., language, training) by logged on and available/not available or not logged on.

C

281 Ability to identify all personnel with a specific skill (e.g., language, training) by logged on and available/not available or not logged on.

C

282 Assigned to a CAD call, or available. C

283 Resource Dispatch

284 Ability for dispatcher to select and assign/re-assign recommended units using Command line, mouse, preformatted data entry screens.

C

285 Ability to dispatch units by:

286 Accepting the proposed application

recommended units C

287 Selecting and dispatching units other than

those recommended by the application C

288 Selecting some, but not all, of the

recommended units C

289 Ability to log recommendation overrides in the audit trail (e.g., log recommended units versus dispatched units).

D

290 Ability for CAD application to do the following upon dispatch:

291 Assign the recommended or requested units C

292 Initiate any alphanumeric paging C

293 Initiate radio paging D

294 Hiplink or other interface C

295 Activate Rip and Run printers D

296 Remove the incident from the pending queue C

297 Send the incident to the assigned unit's

mobile computer C

298 Start the status timers C

299 Update the status display C

300 Ability to dispatch more than one unit at a time to the same call.

C

301 Ability to assign or add multiple units to an incident with a single command. C


302 Ability to assign a unit to an incident to which it was not originally recommended. C

303 Ability to dispatch multiple member agency units (e.g., PTSO and SPPD) to the same call. C

304 Ability to provide sender notification that dispatches have been successfully delivered.

C

305 Field-Initiated Calls for Service

306 Ability for dispatcher to enter field-initiated incidents (e.g., traffic stop). C

307 Ability to add additional units to a field-initiated incident (e.g., traffic stop, subject stop). C

308 Ability to capture unit ID number when incidents are initiated by a unit in the field.

C

309 Ability for dispatcher to use one command to enter a field-initiated incident and place the initiating unit on-scene.

C

310 Ability for dispatcher to record the following information when a unit is placed in a traffic stop status and the information is available:

311 Location of the stop C

312 Number of occupants in the vehicle C

313 Vehicle license plate C

314 State of registration C

315 Vehicle identifier (make, model, color) C

316 Driver Information C

317 Ability for dispatcher to put a unit on a traffic stop and run the plate in one step.

C

318 Ability to geo-validate locations. C

319 Ability for field personnel to initiate a call for service from the mobile computer.

C

320 Ability to capture AVL coordinates when field personnel initiate a call for service from the mobile computer.

C

321 Unit Assignment to CAD Incident

322 Ability to update unit status to associate the dispatched unit or units with the CAD incident.

C

323 Ability to take a unit off a call and reassign the unit to a new call via:

324 Single command C

325 Drag and drop C

326 Preformatted data entry screens (e.g.,

dedicated data fields) C

327 Ability to use one command to both dispatch and put "on scene" field personnel.

C


328 Pre-Arrival Instructions

329 Ability to associate pre-arrival instructions based upon:

330 Incident Type C


332 Chief Complaint C

333 Ability to transfer pre-arrival instructions to dispatched units.

C

334 Ability to modify pre-arrival instructions by:

335 System Administrator (or individual with

appropriate security rights) C

336 Operator (on-the-fly modifications) C

337 Ability to track all modifications to pre-arrival instructions.

C

338 Call Stacking/Queuing

339 Ability to hold an incident for a specific unit. C

340 Ability to automatically (without user intervention) notify the dispatcher of a held incident when the unit becomes available.

C

341 Ability for dispatcher to hold more than one incident to a given unit or resource (call stacking).

C

342 Ability for administrator to turn call stacking on and off.

C

343 Ability to stack calls based on priority. C

344 Call Preemption

345 Ability to pull a unit off an incident and reassign the unit to a new incident. C

346 Ability to return CAD incident to the pending dispatch queue if all units are removed from an active incident. C

347 Ability to visually indicate a preempted call (e.g., color code).

C

348 Ability to support a swap feature to allow two units to swap incidents with a single command.

C

349 Standard Operating Procedures

350 Ability to access SOPs from the CAD application. D

351 Ability to display SOPs without overriding the CAD display. D

352 Ability to access the SOP based on call type and/or location. D

353 Unit Management

354 Unit Placement in Service


355 Ability to log one or more units on-duty/off-duty with a single command.

C

356 Ability to require Member Agency defined criteria upon log-on.

C

357 Ability to automatically assign a beat to a unit upon log-on.

C

358 Ability to define a roster (e.g. squad, company). C

359 Ability to place all units in a previously defined roster on or off-duty.

C

360 Ability to log a fire apparatus into service without tying individuals to the apparatus. C

361 Ability to identify fire units by special equipment. C

362 Ability to designate a unit available for only certain types of calls.

C

363 Ability for Mobile units to log themselves onto CAD.

C

364 Ability for personnel to be associated with any mobile unit (e.g., vehicle, apparatus).

C

365 Ability to associate multiple individuals with a unit. C

366 Ability to visually distinguish units with multiple individuals.

C

367 Ability to indicate a unit that does not have a mobile computer.

C

368 Ability to manage units without a mobile computer.

C

369 Ability to place an apparatus back in service when it is within an agency-defined radius of its station.

C

370 Ability to assign a unit to a defined area (e.g., beat).

C

371 Ability to associate units with beats. C

372 Ability to assign a unit to multiple beats. C

373 Ability to modify a unit's assignment during a shift. C

374 Cross Staffing

375 Ability to identify company personnel capable of staffing multiple resources. C

376 Ability to assign company personnel to the appropriate apparatus depending on the nature of the emergency.

C

377 Ability to prioritize which apparatus is staffed first based on call type.

C


378 Ability to remove an apparatus from service if personnel are not available to staff the apparatus.

C

379 Ability to place an apparatus back in service when personnel are available to staff the apparatus.

C

380 Ability to recognize an apparatus for multiple purposes (e.g., apparatus serving as both truck and engine).

C

381 Ability for CAD system to recognize the purpose for which the multi-purpose apparatus is responding as.

C

382 Unit Status Display

383 Ability to monitor an unlimited number of units. C

384 Ability to update unit status (indicate methods for updating unit status in "comments" field).

C

385 Ability to display all unit statuses. C

386 Ability for Agency to define unit status types. C

387 Ability to associate a default availability with each status (e.g., unit available when in particular status).

C

388 Ability to pair unit statuses (e.g., when a unit goes on training, his paired unit automatically transfer the identical unit status).

C

389 Ability to display the following unit information:

390 Beat C

391 Call type C

392 Current incident number C

393 Current location C

394 Status C

395 Elapsed time in status C

396 Last known location C

397 Logged onto Mobile (Y/N) C

398 Original location C

399 Radio ID C

400 Special skills/equipment C

401 Station D

402 Unit ID/call sign C

403 Member Agency C

404 Ability to automatically update and display unit status.

C

405 Ability for user to refine/filter which Member Agency units to display.

C


406

Ability to divide window views by any unit information (e.g., all units assigned to a special assignment could be displayed in a separate window).

C

407

Ability to sort displayed data by any unit information (e.g., station, shift, incident, unit, location, status).

C

408 Ability to visually differentiate, through color, text and/or symbol, units in varying status or conditions.

C

409 Ability to visually differentiate, through color, text and/or symbol, types of units at incident.

C

410 Ability to use symbols or characters in the unit status display to supplement unit status color.

C

411 Ability to show units on the CAD mapping display. C

412 Ability to use color to distinguish unit type and status on the CAD mapping display. C

413 Unit Activity Tracking

414 Ability to record all unit assignments. C

415 Ability to record all unit locations. C

416 Ability to record all unit status changes. C

417 Ability to review unit status history within the CAD application.

C

418 Ability for all unit activity to be linked to the call for service record.

C

419 Ability to search upon unit activity by:

420 Unit C

421 Location C

422 Ability to track multiple locations associated with a single incident (e.g., in the event a call is open but an officer is going to additional locations).

C

423 Ability to search any address associated with an incident.

C

424 Ability to access the original call for service record when researching an address with an associated incident.

C

425 On-Scene Arrival Tracking

426 Ability to record multiple arrival times associated with different statuses (e.g., arrival at a staging area, arrival at the scene). C

427 Ability to record multiple units arriving:

428 At one time (all at once) C

429 At different times C


430

Ability to automatically mark an assigned unit on-scene when it comes within a certain number of feet of the incident location (with AVL functionality).

C

431 Status Monitoring

432 Ability to initiate status changes via the following methods:

433 Data fields C

434 Function key C

435 Mouse click (e.g., screen icon) C

436 Ability to automatically notify users monitoring or displaying the incident that information has changed via a visual alert or audible alert.

C

437 Unit Clearance

438 Ability to clear one unit from a CAD incident while allowing the other assigned units to remain on the call. C

439 Ability to select any number of units to clear from CAD incident. C

440 Ability to clear all units simultaneously from a CAD incident.

C

441 Ability to require a disposition to be entered prior to clearing the last unit from a CAD incident. C

442 Incident Management

443 CAD Call Display

444 Ability to monitor an unlimited number of incidents

C

445 Ability to add an unlimited number of units to an incident (if limited, indicate the maximum in the "comments" field).

C

446 Ability to allow agency-defined incident statuses C

447 Ability to allow for an unlimited number of agency-defined incident statuses (if limited, indicate the maximum number in the "comments" field).

C

448 Ability to display a window listing pending and holding incidents entered from any CAD workstation.

C

449 Ability to view incident details of one or more incidents at a time.

C

450 Ability to click on an active incident and highlight all assigned units in the unit monitoring window.

C

451 Ability to show incidents on the CAD mapping display.

C


452 Ability to use Agency-defined colors to distinguish call priority and status.

C

453 Ability to accommodate multiple locations for one call.

C

454 Ability to accommodate different units at different locations within one call.

C

455 CAD Incident Updates

456 Ability for any authorized user to add new or additional information to a CAD incident.

C

457 Ability for one or more users to simultaneously add incident information to an incident.

C

458 Ability to automatically identify (e.g., ID stamp) the operator adding information to a call.

C

459 Ability upon entry of a name to automatically query:

460 RMS C

461 TIME System C

462 Ability to update the status of the call as new information is received including, but not limited to:

463 Call type C

464 Call priority C


466 Fire alarm level C

467 Comments C

468 Ability to display updated call information immediately after new information is added to an open call.

C

469 Ability to filter narrative information to display narrative information in chronological order.

C

470 Ability for narrative information to display in reverse chronological order by default.

C

471 Ability to simultaneously notify dispatcher and dispatched units of updated information.

C

472 Ability for dispatcher screen to update automatically as new information is added to a call.

C

473 Ability to show a timestamp with all updates to CAD incident record.

C

474 Ability to show user identification information with updates to CAD incident records.

C

475 Ability to attach all TIME system returns to incident records.

C

476 Ability to attach information to a closed call. C


477 Reopening CAD Incidents

478 Ability to reopen closed incidents. C

479 Ability to reopen a closed call without losing previously recorded date and timestamps.

C

480 Ability to assign units to reopened calls. C

481 Ability for dispatchers to add comments to a CAD call record after the call is closed without reopening the incident.

C

482 Cross-Referencing Calls

483 Ability to cross-reference two or more active incidents.

C

484 Ability to cross-reference active and closed incidents.

C

485 CAD Mapping

486 General Mapping Requirements

487 Ability for mapping functionality to be integrated into CAD starting at call receipt and continuing through to the conclusion of a CAD incident.

C

488 Ability to view map in a separate window. C

489 Ability to allow users to configure map views including, but not limited to:

490 Font size C

491 Level of detail C

492 Screen size C

493 Ability to use a mouse to "click on" a point at any zoom level and have the street name and latitude/longitude information displayed.

C

494 Ability to display street information on map. C

495 Ability to support the import of mapping information from an ESRI ArcGIS Server.

C

496 Ability for GIS data to be continually updated from an ESRI ArcGIS Server.

C

497 Ability to integrate oblique aerial photography layers.

C

498 Map Layers

499 Ability for users to define which map layers are displayed.

C

500 Ability for Agency to define which map layers are mandatory to display.

C

501 Ability to indicate that additional information (e.g., attached files or additional map layer data) is associated with a location displayed on the map.

C


502 Ability to display links to additional information associated with a location displayed on the map.

C

503 Ability to access additional information associated with a location displayed on the map by clicking on the links.

C

504

Ability to click on a location on a map and pull up any supplemental information (e.g. fire pre-plan, hazards, incident history) associated with an agency-defined perimeter around the location (address, building, block).

C

505 Call Management Support

506 Ability to map incoming 911 calls. C

507 Ability to label all call locations with the call number.

D

508 Ability to distinguish between Phase I and Phase II on map by using different symbols, colors and/or text.

D

509 Ability for map to display certainty data regarding Phase II. C

510 Ability to display incident location on map when incident is retrieved.

C

511 Ability to view on map the locations of:

512 All pending and dispatched calls for service C

513 Units based on AVL or last known locations C

514 Ability to retrieve a call for service and have it automatically show up on the map.

C

515 Ability to select a unit and have its location automatically display on the map.

C

516 Ability to drill down into the specific information on the map (e.g., mouse click on icon).

C

517 Ability to obtain call history of an address through drill down functionality on the map.

C

518 Ability to display on-scene unit ID with incident number and call type.

C

519 Ability to hover/click on map and display:



522 Units assigned to call C

523 Ability to click on a map, and generate a query based on the selected address.

C

524 Ability for operator to modify an incident's address and subsequently undergo the address verification procedure.

C

525 Map Navigation


526 Ability to provide users with the following map navigation functionality:

527 Pan from given area to adjacent area C

528 Return back to previous view C

529 Zoom in on area for enhanced detail C

530 Zoom out of an area C

531 Move up and down C

532 Move left and right C

533 Ability for user to update/modify map displays (e.g., preset default zoom levels and views).

C

534 Ability to utilize color, text, and/or symbols to distinguish status of unit.

535 Incident Type C

536 Unit Status C

537 Ability for map to center on and zoom to location upon incident entry.

C

538 Ability to center map display on:

539 CAD incident location C

540 Last known location of vehicle (AVL or unit

status) C

541 Specified geographic area C

542 Specified vehicle/unit C

543 Vehicle activating emergency button C

544 Ability to zoom to relevant map location by searching on available map layer information.

C

545 Routing Directions

546 Ability to provide directions to an incident from a unit's last known location or, if available, current location based on AVL.

C

547 Ability to adjust routing recommendations based on closed streets.

C

548 Ability to close streets by clicking on a specific area (e.g., street, hundred block area) from the CAD map.

C

549 Ability for user to define an expected duration for street closures.

C

550 Ability to push closed street information to mobile computers.

C

551 Ability to project anticipated response times between two points on a map. C

552 Geofile Administration

553 Ability to accommodate an unlimited number of map layers.

C

554 Ability to add geofile layers as needed. C


555 Ability to turn map layers off and on. C

556 Ability to associate geofile data with:

557 Address C

558 Response zone C

559 Geopolitical boundary C


561 Property Owner C

562 Ability for agency to assign addresses to grids. C

563 Ability for agency to assign multiple grids to a response area.

C

564 Ability to force adherence to user-defined addressing standards (e.g., abbreviations and directions).

C

565 Ability for geofile administrator to change reporting boundaries (e.g., areas, beats and districts).

C

566 Ability to support agency-defined location fields, including, but not limited to:

567 Apartment building name C

568 Apartment number (e.g., ½, #5, 2D, D2) C

569 Block range C

570 Business name C

571 City C

572 Common place name C

573 Exact address C

574 Intersections C

575 Limited access roadways and highways C

576 Mile markers C

577 On ramps, off ramps, exit numbers (including

direction) C

578 Overpasses C

579 Prefix C

580 Route number C

581 Street abbreviation C

582 Street alias C

583 Street name C

584 Street type C

585 Subdivisions C

586 Suffix C


588 Ability to update the system with a new geofile without system downtime or degradation.

C


589 Ability to test new geofile updates "offline" for accuracy and errors, prior to updating the "live" geofile.

C

590 Ability for geofile updates to be recognized without requiring logging off and logging back on to the system.

C

591 Ability to include overlays and overhead photography in mapping application.

C

592 Ability to attach premise information (e.g., hazards and gate codes) to addresses.

C

593 Automatic Vehicle Location (AVL)

594 Ability to support the use of a continuous, real-time AVL system via a CAD interface.

C

595 Ability to utilize AVL cross county/jurisdictional lines with agencies who are not on the same CAD system.

C

596 Ability to recommend agencies via AVL that are not on the same CAD system.

C

597 Ability for each member agency of the Consortium to choose to use or not use AVL.

C

598 Ability to prevent individual units from turning off AVL.

C

599 Ability for system administrator to turn AVL on/off by:

600 Member Agencies of the Consortium C

601 Unit C

602 Ability to default to member agency-defined defaults for dispatching when the unit's AVL is turned off.

C

603 Ability to display average speed of vehicle between two points when data is polled.

C

604 Ability to prevent use of on-scene function if unit is not within an agency-defined radius of incident.

C

605 Ability to prevent use of on-scene function if unit is not within a Member Agency-defined radius of incident (e.g., PTSO different than SPPD).

C

606 Ability to capture, save and report on the average vehicle speed between two points.

C

607 Ability to generate reports from AVL data, including:

608 Vehicle route C

609 Speeds along the route C

610 Ability to provide an AVL playback utility. C


611 Ability for playback utility to support a multiple squad playback.

C

612 Contractor Rotation List

613 Ability to maintain multiple contractor rotation lists.

C

614 Ability for system to recommend a contractor based on any combination of the following:

615 Equipment Required C

616 Type of tow C

617 Order in Rotation C


619 Time of day (e.g., hours of operation) C

620 By Member Agency C

621

Ability to store multiple tow lists by member agency (e.g., member agencies have special tow companies based upon type of tow, PTSO and SPPD have separate tow companies).

C

622 Ability to include reason for the tow. C

623 Ability to designate eligible tow companies based upon incident location.

C

624 Ability to attach tow history to a call for service record.

C

625 Ability to automatically place a contractor at the end of the rotation list after selected for service.

C

626 Ability to record that a contractor was selected from the service rotation list.

C

627 Ability to recommend the next available contractor if the initial contractor is unavailable.

C

628 Ability to record reason why a contractor was not selected.

C

629 Ability to suspend a contractor from the rotation. C

630 Ability to associate a timed re-activation from suspension for a contractor (e.g., suspension expiration).

C

631 Ability to manually re-activate a suspended contractor.

C

632 Ability to document the reason for a suspended contractor.

C

633 Ability to record contractor response. C

634 Ability to define timeframe for Contractor rotation list.

C

635 Ability to associate a timer with a contractor request.

C


636 Ability to start a timer upon requesting a contractor.

C

637 Ability for agency to set a default time to a contractor timer.

C

638 Ability to timestamp a contractor's arrival on scene C

639 Ability to place contractor at top of list if incident is cancelled.

C

640 Ability to override contractor recommendation. C

641 Ability to enter a contractor that is not part of the rotation.

C

642 Ability to associate multiple vehicles with a single tow incident.

C

643 Ability for all actions regarding the contractor rotation and selection be associated with an incident record.

C

644 Call Disposition

645 Disposition Recording

650 Ability to require a disposition code before an incident can be cleared.

C

651 Ability for either dispatchers or field personnel to enter the disposition code.

C

652 Ability to enter comments of unlimited-length along with a disposition (if limited, entered the maximum in the "comments" field). C

653 Ability to attach a file to a call for service record. C

654 Report Need Determination

655 Ability to identify whether a report is required based on disposition type and/or call type. C

656 Ability to transfer call for service data to:

657 Law Enforcement RMS C

658 Law Enforcement Field Reporting (e.g., to

initiate a report) C

659 Fire RMS C

660 Ability to transfer call for service data:

661 Upon transfer to dispatcher C

662 Upon incident closure C

663 On demand (i.e., manual initiation of transfer) C

664 Communications Supervisor Support

665

Ability for a communications supervisor to monitor system configuration and current staffing (e.g., who is signed-on, at what position, and with what responsibilities).

C


666 Ability for a CAD workstation to be configured as a supervisor workstation upon logon of a user with a CAD supervisor profile.

C

667 Ability for a supervisor to choose logon type (supervisor vs. dispatcher) upon workstation logon.

C

668 Ability for a communications supervisor to monitor activity on any user workstation.

C

669 Ability for supervisor to override actions taken by any other operator.

C

670 Ability to notify dispatcher of any changes made by supervisor.

D

671 Ability to identify dispatch origin (e.g., dispatcher or dispatch supervisor) of modifications.

D

672 Operational Queries

673 Ability to query the TIME system from within the CAD application.

C

674 Ability to query the Police RMS from within the CAD application.

C

675 Ability for external queries to be performed automatically when entered into a CAD incident record.

C

676 Ability to notify user of associated alerts from external queries.

C

677 Ability to attach query returns to the call for service record.

C

678 Ability to visually distinguish query returns (e.g., information is highlighted).

C

679 Ability to visually distinguish agency-defined key words (e.g., TIME query returns information as stolen, the word "stolen" is highlighted")

C

680 Ability to populate the TIME query mask with data in the incident record:

681 Person Information C

682 Vehicle Information C

683 Ability to automatically run a registered vehicle owner in TIME upon return of a license plate query.

C

684 Ability to query and view the following by any public safety boundary layer (e.g., beat, sector):

685 Active calls C

686 Assigned calls C

687 Closed calls C


688 Priority calls C

689 Waiting (pending) calls C

690 Ability to query unit history by any combination of:

691 Date and time range (e.g., start and end date

and time parameters) C

692 Unit ID, field personnel ID, or employee

number C

693 Dispatcher C

694 Location C

695 Member Agency, incident number C

696 Ability to review historical information related to:

697 Call C

698 Location C

699 Employee ID C

700 Vehicle C

701 Subject C

702 Tow C

703 Ability to query response area activity by:

704 Unit ID C

705 Call source (field personnel initiated, dispatch,

agency, type of phone line, etc.) C

706 Date and time range C

707 Disposition C

708 Incident Type C

709 Ability to isolate queries in the database to a single member agency's incidents (e.g., PTSO vs. SPPD).

C

710 False Alarms

711 Ability to create an incident from information obtained from an alarm monitoring unit.

C

712 Ability to create a false alarm disposition. C

713 Ability to transfer false alarms to a false alarm billing module in the RMS with the following information:

714 Incident Address C

715 Business name C

716 Date/Time C

717 Incident Number C

718 Be-On-The-Lookouts (BOLOs)

719 Ability to create and maintain BOLOs. C

720 Ability to provide an audit trail for BOLOs. C


721 Ability to provide the following fields for a BOLO record:

722 Date issued/expired C

723 Nature of the BOLO, priority C

724 Subject/Vehicle information C

725 Narrative C

726 Ability to search for BOLO based upon any of the above-mentioned items.

C

727 Ability to accommodate multiple subjects/vehicles in a BOLO.

C

728 Ability to attach a file, photo and update a BOLO. C

729 Ability to set time limits for BOLO retention. C

730 Ability to designate groups or individuals to whom BOLOs should be sent.

C

731 Ability to link BOLOs to an address such that the BOLO is retrieved when that address is referenced (e.g., in a call for service or report).

C

732 Ability to link BOLOs to an incident. C

733 Ability to transfer BOLO information fields from an incident.

C

734 Ability to query BOLOs by address. C

735 Ability to view history of recent, archived, and expired BOLOs.

C

736 Ability to search expired BOLO records. C

737 Management Reporting

738 CAD Reporting

739

Ability to create ad hoc CAD reports based on any data fields in the CAD database. Reports based on officer activity or response times, Incident types, or any incident creation or analysis times, dispatch user, or geographical related.

C

740 Ability to run CAD reports without exiting the operational CAD application.

C

741 Ability to capture a snap shot, based on day and time parameters, of:

742 A workstation C

743 General CAD system C

744 Ability to print a chronological incident report. C

745 Ability to print audit report of changes to incident records including:

746 Transaction type (deletion, edit, etc.) C

747 Unit ID C

748 Workstation/terminal ID C

749 Before and after value C


750 Ability to export reports. C

751 Ability to view requested reports prior to printing. C

752 Sending Messages

753 Ability to create and save message groups. C

754 Ability to send messages across agencies (e.g., law enforcement to fire and vice versa).

C

755 Ability to send broadcast messages. C

756 Ability of users to select any number of people as part of a message group with no limitation on the number of people in a group.

C

757 Ability to enter unlimited narrative with wrap-around feature (if characters are limited, indicate the maximum in the "comments" section).

C

758 Ability to automatically populate the "To" field on the message mask when selecting recipients.

C

759 Ability to select a recipient by a single command to create a message (e.g., double click on a logged on user and message screen pops up).

C

760 Ability to attach files to messages. C

761 Ability to embed photos in messages. C

762 Ability to set agency-defined file size limit. C

763 Ability to send a message to all units handling a specific incident.

C

764 Ability to transmit a reply message to the originator of a currently displayed message without having to reenter the originator's address.

C

765 Ability to transmit a "reply all" message to multiple recipients that were part of the originator's message group.

C

766 Ability to forward a message. C

767 Ability to create messages that are retained in the system and sent at pre-specified times.

C

768 Ability to provide a notification for delivery of messages to the device.

C

769

Ability to provide a notification for non-delivery of messages (i.e., a message sent to a device or group of devices could not be delivered if a user is not signed-on to the device(s)).

C

770 Ability to identify which users are currently logged on.

C

771 Receiving Messages


772 Ability to notify receiver via an audible and/or visual flag that a new message has arrived in mailbox.

C

773 Ability to prevent incoming messages from interfering with current work.

C

774 Ability to notify receiver of total number of unread messages.

C

775 Ability to prevent incoming messages from overlaying the screen.

C

776 Ability for messages to be queued in an "inbox" for later viewing at the convenience of users.

C

777 Ability to query message logs by agency-defined criteria (e.g., date/time range, sender, recipient, device).

C

778 Ability to note time opened/read by receiver. C

779 Ability to clear a message from the queue. C

780 Ability to retain a message in the queue. C

781 Ability for supervisors to monitor messages. C

782 Ability for supervisors to search messages by a text string (e.g., to identify inappropriate language use)

C

783 Ability to archive messages. C

784 Ability to save message logs for an agency-determined period of time.

C

785 Ability to purge message logs for an agency-determined period of time.

C

786 Paging

787 Ability to generate a page from within CAD. C

788 Ability for system to automatically page appropriate personnel dependent upon:

789 Incident Type C


791 Responding member agency C

792 Responding units C

793 Ability for Agency to determine which data elements are transferred as part of page.

C

794 Ability to create paging groups within CAD. C

795 Ability to page multiple groups simultaneously. C

796 Ability to perform a broadcast page to all users. C

797 Ability for user to select which groups or individuals to page from within CAD.

C

798 CAD System Administration

799 CAD Table Maintenance


800 Ability to include, at a minimum, the following data tables:

801 Call source (e.g., officer-initiated, 911, 10-

digit) C

802 Call types and priorities C

803 Commands C

804 Dispositions C

805 Equipment C

806 Event error logs (so vendor can identify and

troubleshoot errors) C

807 Patrol and command area definitions C

808 Personnel, including emergency contact

information and current assignment C

809 Timers C

810 Unit status types (i.e., assigned, unassigned,

assigned but available) C

811 Units C

812 Ability to allow the agency to define the following:

813 Category codes for pull-down lists C

814 Codes for each valid call disposition used

when clearing a call C

815 Codes for the methods the agency receives

calls (e.g., 911, cell phone) C

816 Codes used to identify areas for statistical

reporting reasons C

817 Dispatch codes C

818 Priorities assigned to calls codes C

819 Response procedures C

820 Subtypes of calls C

821 Ability to configure status code colors. C

822 CAD Configuration

823 Ability for agency to create data entry screens. C

824 Ability for agency to define data fields within entry screens.

C

825 Ability for agency to define mandatory data fields. C

826 Ability to configure the field entry sequence. C

827 Ability to create agency-defined data lists for all configurable drop-down menus.

C

828 Ability for agency to configure alerts:

829 Associated message displayed C

830 Audible indicator C

831 Visual indicator C


832 Premise File Maintenance

833 Ability to update/create CAD premise history files. C

834 Ability to automatically update premise history when an incident occurs.

C

835 Ability to capture the following information when creating premise history:

836 Date and time stamp C

837 Date of incident C

838 Disposition C

839 Type of incident C


841 Narrative text of unlimited length (if limited,

indicate maximum in the "comments" field) C

842

Ability to capture and maintain specific premise information by groups of addresses (e.g., all apartments in an apartment complex, all houses in a subdivision).

C

843 Ability to store premise information for an agency-defined length of time.

C

844 Ability to purge premise information from a location (e.g., if it is known that the tenant/owner generating the incidents has moved).

C

845 Ability to store premise information for a specific apartment unit/suite number.

C

846

Ability to define valid date ranges for time limited premise information at a given location (e.g., information valid between <start date> and <end date>).

C

847 Ability to archive expired premise file information. C

848 Ability to include in a premise record the following information when premise information is added or changed:

849 Expiration date C

850 Unit ID of person entering information C

851 Ability to attach files to a premise record (e.g., floor plans, building diagrams, special instructions).

C

852 Ability to access files attached to a premise record:

853 In CAD environment C

854 In Mobile environment C


855 Hazard File Maintenance

856 Ability to enter hazards associated with:

857 Persons C

858 Specific locations C

859 Address ranges C

860 Vehicles C

861 Ability to record with an entered hazard:

862 Expiration date C

863 Time and date stamp at time of entry C

864 ID of person entering information C

865 Ability to assign expiration dates to hazards. C

866 Ability to create lists of hazards by category C

867 Ability to print hazards and hazard lists C

868 Flags and Notifications Maintenance -

869 Ability to provide narrative information with flags. C

870 Ability to keep hazard and event flags in CAD system for an unlimited length of time until manually removed by administrator/supervisor.

C

871 Ability to notify system administrator when flags exceed an agency-defined time period.

C

872 Ability to archive deleted hazards and event flags. C

873 Ability to set an expiration date for a flag or notification.

C

874 Ability to maintain a record of deleted hazards and event flags.

C

875 Emergency Contacts

876 Ability to maintain a list of emergency contacts. C

877 Ability to link emergency contacts with an address. C

E-6 Jail Management System Functional Requirements E-6.1 Questions-None

E-6.2 Requirements-


JAIL Software Requirements


Item # Description of Requirement Priority Response Comments


1 General

2 Ability to date and time stamp all application transactions.

C

3 Ability to auto-populate all date and time fields with date and time stamp (e.g., booking date and time or release date and time).

C

4 Ability for system to automatically adjust number sequencing for new calendar years.

C

5 Ability for system to automatically account for daylight savings time and any required parameter changes to daylight savings.

C

6 Ability to automatically calculate the day of week for any entered date.

C

7 Ability to override action date and time stamp and also record actual entry date and time stamp, if making a retroactive entry.

D

8 Ability to attach files to a record. C

9 Ability to accept digital signatures. C

10 Ability to accept digital fingerprints. C

11 Ability to provide word processing capabilities on narrative and comment fields, including, but not limited to:

12 Text wrap C



15 Spell check C

16 Copy and paste C

17 Grammar check C

18 Ability to designate mandatory fields. C

19 Ability to visually distinguish mandatory fields. C

20 Ability to perform data validation at time of:

21 Data Entry C

22 Data Submission C

23 Ability to validate data entry to ensure all required fields have been completed.

C

24 Ability for agency to modify data fields:

25 Add C

26 Delete C

27 Rename C

28 Ability for the Agency to modify data fields:

29 During implementation C

30 Following implementation, without vendor intervention

C


31 Ability to limit the fields on the screen to only those in use.

C

32 Ability for agency to determine which data fields may be modified after original entry.

C

33 Jail Website

34

Ability to automatically update a jail website at an agency-defined time interval with the following information related to each inmate (agency defined):

35 Name C

36 Booking number C

37 Gender C

38 Date of Birth C

39 Booking Date C

40 Facility C

41 Offense C

42 Address C

43 Release Date C

44 Arresting Agency C

45 Classification (Felony, Misdemeanor, Civil etc) D

46 Charges D

47 Charge Description(s) D

48 Bond/Fine D

49 Court File Number O

50 Disposition of Charge O

51 Disposition Date O

52 Ability to search for historical information via the jail website.

O

53 Ability to view a roster of inmates in custody by:

54 Alphabetical Order D

55 Offense D

56 Ability for user to select an inmate from the roster and view detailed information

D

57 Ability for agency to incorporate hyperlinks on the website.

C

58 Ability to search inmates that are/have been:

59 Released C

60 In Custody C

61 Ability to search inmates by:

62 Name C

63 DOB C

64 DOB Range C

65 Date Booked C

66 Date Booked Range C


67 Jail ID C

68

Ability for agency to determine which inmates are eligible for display as part of the jail website (e.g., restrict "under investigation" inmates from displaying on jail website).

C

69 General JMS Reports

70 Ability to search on any data element in the JMS.

C

71 Ability to generate reports on any defined parameter within the system.

C

72 Ability to generate aggregate reports of inmates across a user defined time range identifying the following information:

73 Gender

74 Race C

75 Location (e.g., facility) C

76 Ability to run comparison reports of any aggregated data (e.g., male vs. female population)

C

77 Federal Compliance

78 ICE

79 Jail Census

80 Ability to generate a report of Inmates in Custody with Non-US Citizenship for a user-defined date range.

C

81 Ability for jail census reports to be broken down by:

82 Federal Agencies D

83 Other Counties C

84 General Population C

85 Total Population C

86 Ability to generate a report of release data by date range for convicted and not convicted for the following date ranges:

87 Less than 1 Day C

88 1 - 2 Days C

89 3 - 7 Days C

90 8 - 30 Days C

91 31 - 180 Days C

92 180+ Days C

93 Ability to generate a report of release data by date range by any of the following parameters:

94 Release hours and days C

95 Day of week C


96 Gender C

97 Ability for report of release data to include aggregate (total and subtotals).

C

98 Ability for report of release data to include average length of stay.

C

99 Ability to generate confidential reports specific to juveniles.

C

100

Ability for juvenile reports to contain any defined parameter as part of the JMS (e.g., booking information, stay information, gender information, etc.)

C

101 JMS Master Name Index

102 Ability to access master name information in the RMS.

C

103 Ability to provide a single master name index for the JMS and RMS applications.

C

104

Ability to distinguish between verified (e.g., positive identification via fingerprints) and unverified records (e.g., names not run through the LiveScan system).

C

105 Ability to maintain historical information upon entry of updated information into a master record.

C

106 Ability to automatically update master indices upon entry of booking information.

C

107 Ability to notify a user entering a new master record that there is potentially an existing master record match.

C

108 Ability for user to decide whether to link information to an existing master name record or add a new master name record.

C

109 Ability for user to add a new master name record.

C

110 Ability to link an individual master name record to every event in which the individual is involved or associated.

C

111 Ability to link alias names to an individual master name record.

C

112 Ability to produce a synopsis of all JMS records associated with that person by querying that person's name.

C

113 Ability to view all related records when querying an individual MNI (Master Name Information) record.

C


114 Ability to provide dedicated fields to capture, at a minimum, the following information in the master name index:

115 Name (Last, First, Middle, Suffix) C

116 Date of birth C

117 Physical characteristics, including, but not limited to:

118 Citizenship C

119 Date of birth C

120 Ethnicity C

121 Eye color C

122 Hair color C

123 Height C

124 Race C

125 Complexion C

126 Sex C

127 Weight C

128 Scars, marks and tattoos, including:

129 Type (scar mark or tattoo) C

130 Location C

131 Description C

132 Age at time of incident C

133 Address C

134 Martial Status C

135 Gang affiliation C

136 All available mug shots and photographs C

137 Identification information, including, but not limited to:


139 Driver's license number and state C

140 Alien registration number D

141 Immigration status D

142 INS number D

143 USM Number D

144 DOC Number C

145 State ID Number C

146 FBI number C

147 Ability to associate alias identifiers with a master name record, including, but not limited to:

148 Alias names C

149 False names C

150 Monikers C


151 Dates of birth C



154 Ability to provide user entering a name with a list of potential existing master name records based on a variety of criteria, including:

155 Exact spelling C

156 Partial name C



159 Date of Birth C



162 Ability to merge two or more MNI records into one MNI record.

C AUTHORIZED USERS

163 Ability when linking multiple MNI records to maintain historical information.

C

164 Ability to run a canned report identifying potential duplicate MNI records.

C

165 Ability to store "keep separate" information in the MNI.

D

166 Flags and Alerts

167 Ability for the system to automatically generate a flag for individuals in custody.

C

168 Ability to establish alerts:

169 Visual C

170 Audible O

171 Ability for agency to define alert types. C

172 Ability for alerts to contain agency-defined special instructions and response requirements before proceeding.

C

173 Ability for special instructions to be associated with alert type (e.g., special diets).

C

174 Ability for user, when presented an alert, to be presented associated special instructions.

C

175

Ability to associate alerts with the unique identifier of the inmate (e.g., alert carries over to the inmate from a previous incarceration until deactivated by Agency).

C

176 Ability to view history of alerts associated to an inmate.

C

177 Ability to set alerts on an inmate at any time (e.g., booking, post-booking), including, but not limited to:


178 Escape risk C

179 Suicide risk C

180 Medical Risk C

181 Observation Risk C

182 Violent Risk C

183 Agency-Defined C

184 Ability to associate the following with an alert:

185 Type of alert C

186 Person Entering Alert C

187 Alert Authorizer C

188 Reason for the alert C

189 Start date for the alert C

190 Re-Start dates (e.g., special observations during holidays)

C

191 Alert expiration date C

192 Associated Special Instructions C

193 Ability to update alerts/flags. C

194 Ability to cancel alerts/flags. C

195 Ability to set an alert/requirement on persons who need to be kept separate from other persons.

C

196 Ability to indicate people from whom an inmate should be kept separate.

C

197 Ability to include alerts/requirements in any printed or electronically displayed inmate list.

C

198 Ability to visually distinguish type of alert (e.g., # = combat alert, & = suicide risk)

C

199 Ability for agency to define the symbols for alerts.

C

200 Ability to include alerts in any screen reference to the inmate.

C

201 Inmate Booking

202 General Booking Features

203 Ability to enter individual booking information. C

204 Ability to generate a report of all individuals being held at the facility (e.g., roster report).

C

205 Ability for roster report to include any agency-defined parameter selected by the user generating the report (e.g., gender, race, etc.)

C

206 Ability to track juvenile bookings separately from adult bookings.

C

207 Ability for system to automatically generate a unique MNI and/or booking number for each individual.

C


208 Ability for the system to automatically generate the appropriate booking number if MNI exists.

C

209 Booking Data Entry

210 Ability to accept pre-booking information electronically (e.g., from a Field Reporting application).

C

211 Ability to populate initial booking screen with electronically received pre-booking information.

C

212 Ability to require different booking data entry fields based upon the type of booking (e.g., juvenile has different data fields than adult).

C

213

Ability to re-use previously entered booking information when entering information associated with next of kin (e.g., when entering address for next of kin, ability to import address data from inmate).

C

214 Ability to provide dedicated fields to capture the following booking information including, but not limited to:

215 Inmate Information:

216 Name C

217 Date of Birth C

218 Sex C

219 Race C

220 Origin C


222 Address C

223 Place of Birth C

224 US Citizenship C

225 Phone Number C

226 Marital Status C

227 Scars, marks and tattoos C

228 Annual Income O

229 Home Ownership information (Rent, Own) O

230 Children O

231 US Veteran Status (Y/N) D

232 State ID Number C

233 FBI Number C

234 Passport Information O

235 Literacy Information D

236 Primary Language C

237 Ability to speak English C

238 Religion O


239 Alias C

240 Next of Kin Name C

241 Next of Kin Address C

242 Next of Kin Relationship C

243 Next of Kin Phone Number C

244 SSA Class C

245 Emergency Contact C

246 Occupation C

247 Employer C

248 Classification C

249 Appearance Information:

250 Hand Use O

251 Teeth O

252 Build C

253 Demeanor O

254 Speech O

255 Complexion O

256 Physical Condition C

257 Appearance C

258 Clothing O

259 Height C

260 Weight C

261 Hair color C

262 Eye color C

263 Complexion O

264 Arresting Information:


266 Arresting Officer C

267 Arrest Location C

268 Case Number C

269 Date/Time of Arrest C

270 Offense Code C

271 Ability to record the following information specific to a juvenile arrest:

272 School Attending C

273 School of Residence C

274 Counseling Information C

275 Parent/Guardian Information C

276 Ability to re-use information from a past booking for the same person.

C

277 Ability for classification to limit specific charcters.

D


278 Ability to display any alerts/flags associated with the individual.

C

279 Booking Inquiries

280 Ability to query the following from within the booking module:

281 Wisconsin TIME System (including CIB/NCIC) C

282 Law enforcement RMS C

283 Civil (including Warrants) D

284 Booking Deletions

285 Ability to delete a booking made in error (with appropriate security level).

C

286 Ability to generate a report showing deleted bookings for a user-defined date and time range and includes the following fields:

287 Booking number C

288 Booking name C

289 Operator ID/name C

290 Time and date stamp C

291 Reason for deletion C

292 Booking Reports

293 Ability to prepare a daily booking log listing all inmates booked during a user-defined period.

C

294 Ability to generate a booking report with any combination of the following information:

295 Age breakdown:

296 0 - 21 C

297 22-30 C

298 31 - 50 C

299 50+ C

300 Gender C

301 Race C

302 Residency C


304 Hour of Date Booked C

305 Priors:

306 0 C

307 1 C

308 2 to 5 C

309 6 to 9 O

310 10 to 19 O

311 10 Plus O

312 Day of Week O

313 Questionnaires


314 Ability for agency to define multiple types of questionnaires (including questions and valid answers), including but not limited to:

315 Medical C

316 Suicide C

317 Observation C

318 Ability for the Agency to create and modify questionnaires:

319 During implementation C

320 Following implementation, without vendor intervention

C

321 Ability to support conditional logic in which subsequent questions are determined by previous answers.

C

322 Ability to maintain historical information for questionnaires if questionnaires are modified.

C

323

Ability for an officer to complete a questionnaire without requiring the inmate to be booked (e.g., prior to booking, a deputy completes a visual observation report) AND the ability to complete a partial booking later (e.g, uncooperatrive subject).

C

324 Ability when booking an inmate, to access and import previously completed questionnaires OR limit access.

C

325 Ability for questionnaires to include agency defined language upon printing.

C

326 Ability to document the following related to each questionnaire:

327 Inmate C

328 Person Conducting Questionnaire C

329 Date C

330 Time C

331 Ability for questionnaire answer fields to include:

332 Drop Down Menus (e.g., Yes/No/Refused) C

333 General Comments Field C

334 Comments field specific to each question C

335 Ability to notify user during booking required questionnaires that must be completed.

C

336 Mug shots

337 General

338 Ability to link a mug shot to an MNI C


339 Ability to associate all images with a specified inmate's file, along with the date and time at which it was recorded.

C

340 Ability to keep a historical record of mug shots (e.g., for each booking).

C

341 Ability to trigger print of mug shots C

342 Ability to print an Inmate Form that includes an inmate's mug shot, name and booking number.

C

343 Ability for Inmate Form to include fields for manual data entry (e.g., hand written) that categorizes the following:

344 Crime C

345 Term C

346 Assignment C

347 Health Restrictions C

348 Security Restrictions C

349 Assignment History C

350 Detainer Information C

351 Comments C

352 Conduct History C

353 Ability for Inmate Form information fields to be populated with information previously entered into the system.

C

354 Ability to generate labels that identify the following inmate information:

355 Mug shot C

356 Booking Number C

357 Inmate Name C

358 Height C

359 Weight C

360 Eye Color C

361 Hair color C

362 Gender C

363 Race C

364 Ability to display the most recent mug shot when a query returns an MNI record.

C

365 Ability to export a mug shot with identification information.

D

366 Ability to export a mug shot without identification information.

D

367 Ability for booking photos to be made available to the Mobile application.

C

368 Ability to preview an image prior to final image acceptance.

D


369 Ability to track history of an individual's mug shots.

C

370 Ability to index photos of persons based on basic features including, but not limited to (Inconjunction with SI3000):

371 Name C

372 Age Range C

373 Gender C

374 Race C

375 Facial Hair C

376 Hair color C

377 Eye color C

378 Height C

379 Weight C

380 Height Range C

381 Weight Range C

382 Scars, marks, and tattoos C

383 Any physical characteristic C

384 Glasses C

385 Ability to separately capture scars, marks and tattoos and associate these photos with a mug shot.

C

386

Ability to capture an unlimited number of scars, marks and tattoos. If limited, indicate the maximum number of permissible in the "comments" section.

C

387 Ability to query mug shots by indexed features. C

388 Ability to crop photographs. D

389

Ability to support an unlimited number of photos associated with an individual (if limited, indicate the maximum permissible in the "comments" section).

D

390 Ability to view photos by:

391 List C

392 Thumbnail C

393 Ability to create a BOLO with mugshot and associated information for distribution.

D

394 Inmate Property

395 Ability to auto-populate the property record with information from the booking module, as appropriate.

C

396 Ability to generate and complete an inmate property report prior to booking completion.

C


397 Ability when booking an inmate, to access and import previously completed inmate property reports.

D

398 Ability to maintain historical information regarding inmate property by:

399 Bin Number/Property Bag Number C

400 Inmate C

401 Ability to support a parent-child property tracking format (e.g., multiple bags assigned to a single bin).

O

402 Ability to assign property to the child container (e.g., assigning to the bags within the bin).

O

403 Ability to assign property to a facility. O

404 Ability to transfer property across facilities. O

405 Ability to record individual conducting property search.

C

406 Ability to provide dedicated fields to capture any combination of the following:

407 Bin Number/Bag Numbers C

408 Property Type C

409 Property Description C

410 Color C

411 Quantity C

412 Ability for agency to assign Bin Number/Bag Numbers

C

413 Ability to support alphanumeric characters for bin/bag numbers and shelf numbers.

C

414 Ability to assign separate bin numbers to each facility.

O

415 Ability to assign separate bin numbers to each facility.

O

416 Ability to capture electronic signature C

417 Ability to inventory property by:

418 Facility O

419 Inmate C

420 Time Range C

421 Bin/Bag C

422 Ability to attach files to property record. C

423 Ability to print property sheet. C

424 Ability to add property after initial intake. C

425 Ability to track chain of custody of property. C

426 Ability to support digital signatures. C

427 Ability to record history of disposed property. C


428 Ability to record an audit trail of all actions taken regarding property (e.g., transfer, intake, disposal, etc.)

C

429 Ability to generate a receipt of inmate property:

430 Intake C

431 Release C

432 Ability for receipt to include:

433 Inmate Name C

434 Inmate Signature C

435 Date C

436 Time C

437 Property Information C

438 Witness C

439 Property Release

440 Ability to notify user of property to be released as part of inmate release.

C

441 Ability to record receipt of released property. C

442 Ability to release property one at a time. C

443 Ability to release property at a single time. C

444 Ability to release "child" containers at a single time (e.g., not releasing entirety of property, but only portions of property).

C

445 Ability to track history of property bin use after release.

C

446 Ability to record inmate acceptance or refusal of property at time of release.

C

447 Ability to release property to someone that is not the inmate.

C

448 Ability to record property release information, including:

449 Property Information C

450 Property Released to Information C

451 Inmate Classification

452 Ability to interface with Northpoint/Compass C

453 Ability to provide an inmate classification system.

C

454 Ability to accommodate a temporary classification.

C

455 Ability to provide different algorithms for gender.

C

456 Ability to manually input a classification. C

457 Ability to identify inmates that have not been classified or that need to be reclassified.

C


458 Ability to identify inmates that are mishoused (i.e., placed in a location that does not meet their classification).

C

459 Ability for user to supplement responses to classification questions with narrative text entry (e.g., explanations).

C

460

Ability for agency to define the algorithm that generates classification code recommendations based on responses to the classification questions.

C

461 Ability to assign inmates to housing based on:


463 Gender C

464 Keep Separate Status C

465 Ability to provide an alert if inmate records have any "Keep Separate" restrictions.

C

466 Ability to prevent any inmates that should be kept separate from being placed in the same housing unit.

C

467 Ability to provide a visual indication of the inmate's classification on any screen reference to the inmate.

C

468 Inmate Housing

469 Ability to define housing locations as:

470 Cell Blocks C

471 Floor O

472 Cell Number C

473 Bed C

474 Facility O

475 Supported Gender (e.g., female only) C

476 Ability to associate a narrative with a housing location (e.g., Cell Number - Available for female holding).

C

477

Ability to identify and display all available beds within a facility that meet the inmate’s needs (e.g., in terms of classification, gender, special handling needs, alerts, etc.).

C

478 Ability to recommend a housing location, based on an Agency-defined algorithm.

C

479 Ability to assign classification to all cells C

480 Ability to define maximum number of occupants for each cell.

C

481 Ability for booking officer to override housing recommendations.

C


482 Ability to temporarily suspend the availability of a bed.

C

483 Ability to change assignments of facility, unit, cell, and/or cell letter, and record the reason for the change.

C

484 Ability to maintain historical information of facility, unit, and cell.

C

485 Ability to maintain a history of an inmate’s cell and cell letter assignment for:

486 Present bookings C

487 Past bookings C

488 Ability to link housing assignments to an inmate's record.

C

489 Ability to generate a consolidated report of an individual inmate's housing history.

C

490 Ability to inquire on bed availability by:

491 Block C

492 Dorm C


494 Cell Type C

495 Ability to generate a report on all inmates that have shared housing for a user-defined date range, including but not limited to:

496 Cell C

497 Block C

498 Dorm C

499 Housing Monitor

500 Ability to monitor booking and releases on a single screen (e.g., housing monitor).

D

501 Ability for housing monitor to automatically refresh/update.

D

502 Ability to manually refresh the housing monitor. D

503 Ability to sort on any column in the booking monitor.

D

504 Ability to exclude inmates from the booking monitor.

D

505 Ability to provide drill down capabilities from the housing monitor screen (e.g., click on an inmate to view inmate details)

D

506 Ability to separate the booking monitor by housed facility.

D

507 Classification Override

508 Ability to override system classification recommendation.

C


509 Ability to document Administrator approval of override.

C

510 Ability to require an explanation (free-text narrative) when system classification is overridden.

C

511 Ability to maintain a history of the inmate’s classification for all bookings, present and past.

C

512 Re-Classification

513 Ability to accept an unlimited number of reclassifications.

C

514 Ability to establish a periodic review of classification based on agency-defined time limits.

C

515 Ability to record re-classification requests C

516 Ability to generate a report of inmates due for classification review.

C

517 Ability to maintain an audit trail of all classification and reclassification actions.

C

518 Ability to track a classification appeal filed by an inmate.

C

519 Jail Billing

520

Ability to create detailed housing invoices/billings for federal, state and local agencies based on agency-defined parameters Export to Tyler-Munis Financial System .

D

521 Ability to interace with Stellar Services C

522 Ability for housing invoices to include any combination of the following:

523 Identifying Number C

524 Days Billing C

525 Dollar Amount C

526 Total C

527 Inmate Name C

528 Booking Date C

529 Release Dates C

530 Agency-identified field D

531 Begin Date Sentencing C

532 End Date Sentencing C

533 Ability to deduct days from the invoice/billing if an inmate is out of the facility.

C

534 Ability to export billing information to an excel spreadsheet.

C

535 Ability to convert invoice to .pdf format. D


536 Ability to generate outside agency Inmate invoices.

C

537 Ability for system to calculate billable amount due by an agency-defined reimbursement rate.

C

538 Classification Reports

539 Ability to generate a Primary Classification Report that includes any combination of the following information:

540 Inmate Name C


542 Aliases C

543 Date of Birth C

544 Cell Location C

545 Booking Date C

546 Address C

547 Phone Number C

548 Sex C

549 Race C

550 Marital Status C


552 Height C

553 Weight C

554 Scars, marks and tattoos C

555 Next of Kin D

556 Occupation D

557 Employer D

558 Employer address D

559 Employer Phone D

560 Charges C

561 Discipline record C

562 Ability to generate the following reports:

563 Listing by next review date C

564 Listing by assessment date C

565 Listing by assessment type C

566 Listing by classification officer C

567 Listing by Booking date C

568 Inmate Requests

569 Ability to record all inmate requests and/or grievances.

C

570 Ability to enter action taken (including review) regarding inmate requests.

C

571 Key Tracking

572 Ability to track the distribution of keys. O


Ability to Interface with Keywatcher C

573 Ability to record the following information related to the distribution of keys:

574 Name of individual receiving key O

575 Rank O

576 Title O

577 Division O

578 Department O

579 Key number O

580 Date/Time Issued O

581 Date/Time Returned O

582 Ability to associate an unlimited number of keys with an individual.

O

583 Inmate Worker Management

584 Ability to assign an inmate to work position. D

585 Ability to record approval for inmate worker position.

D

586 Ability to generate a report of approved inmates for work positions.

D

587 Ability to record location of work positions. D

588 Ability to generate a report that identifies a worker and the location of his/her corresponding work location.

O

589 Ability to generate a report of work locations and corresponding workers at that location.

O

590 Ability to record an inmate's request for work. C

591 Ability to record approval or denial of request for work.

C

592 Ability to define work privileges for an inmate (e.g., location of work, type of work, etc.)

C

593

Ability for agency to define an algorithm that associates number of hours worked with credited days served (e.g., inmate works 24 hours total, they are granted 1 day of credit served).

C

594 Ability to track inmates that are serving time outside of the facility.

C COMMUNITY SERVICE

595 Huber

596 Ability to approve/deny an inmate’s request for Huber privileges.

C

597 Ability to document the following related to an inmate's Huber request:

598 Date and Time C

599 Person Approving/Denying Request C


600 Outcome C

601 Comments C

602 Ability to record if the inmate was approved for work, counseling, child/family/parent care, medical, school or work crew.

C

603 Ability to record if an inmate is serving time at Portage County facility for a sentence from another county.

C

604 Ability to record inmate appointments outside of agency facilities.

C

605 Ability to document the following related to each appointment:

606 Location C

607 Date C

608 Time C

609 Inmate C

610 Verification of Attendance C

611 Purpose/Reason C

612 Mode of Transportation C

613 Person Verifying Attendance C

614 Person Approving Request C

615

Ability to provide unlimited comments fields related to verification fields. If limited, indicate the maximum permissible in the "comments" field.

C

616 Ability to record inmates mode of transportation.

C

617 Ability to record driver of transportation, including:

618 Name C


620 Driver's License Type (i.e., Occupational) C

621 Ability to alert user if driver does not have appropriate license following automated TIME check.

D

622 Ability to provide electronic time keeping for workers (e.g., inmate worker card swipe).

D

623 Ability for time keeping system to automatically calculate hours worked for an agency-defined time period.

D

624

Ability for time keeping system to incorporate agency parameters (e.g., travel time) to compare against actual time worked vs. scheduled time worked.

D


625 Ability to provide a notification when actual time worked varies from scheduled time worked.

D

626 Ability to capture drug/alcohol screening results, including but not limited to:

627 Inmate C

628 Person/Agency conducting test C

629 Date C

630 Results C

631 Comments C

632 Ability to capture Huber violations, including but not limited to:

633 Inmate C

634 Violation C

635 Date C

636 Comments C

637 Ability to record if an inmate has been revoked from Huber (including comments field).

C

638 Ability to record that all required Huber paperwork was signed by the inmate and the person that witnessed the inmate’s signature.

C

639 Inmate Issuance

640 Ability to record all items issued to an inmate. O

641 Ability to generate a report of all items issued to an inmate.

O

642 Ability to track the following related to each item:

643 Color O

644 Size O

645 Description O

646 Type O

647 Cost O

648 Expiration Date O

649 Quantity O

650 Ability to generate a report notifying users of items:

651 Approaching Expiration O

652 That have expired O

653 Ability to alert a user if items have expired. O

654 Ability to alert a user if an item has previously been issued (e.g., inmate is only 1 item per week, they are requesting 2nd item that week).

O

655 Ability to assign a zero dollar cost to an item issued.

O


656 Ability to manage an inventory of items not yet issued.

O

657 Ability for agency to set thresholds of inventory. O

658 Ability to alert user if items fall below defined threshold.

O

659 Ability to generate inventory reports by the following parameters:

660 Date O

661 Time O

662 Associated Inmate O

663 Inventory Type O

664 Pass-on Log

665 Ability to maintain an electronic log for reporting activities and information on inmates to other staff.

C

666 Ability to add unlimited narrative to the electronic log (if limited, indicate the maximum permissible in the "comments" section).

C

667 Ability to capture the following related to the pass on log:

668 Date/Time of Entry C

669 Person entering data C

670 Cell C

671 Inmate information (name, booking number) C

672 Location C

673 Log Type C

674 Ability to generate user-defined reports with any combination of data captured in the Pass on log.

C

675 Inmate Incidents

676 General Inmate Incident Requirements

677 Ability to record jail incidents C

678 Ability for incident report to include the following information:

679 Facility C

680 Name C

681 Role:

682 Officer C

683 Witness C

684 Inmate C

685 Staff C

686 Force C

687 Force description (Taser, ECD etc.) C

688 Chemical Agent C


689 Reaction Team Deployed (y/n) C

690 Restraint Chair Used (y/n) C

691 Injuries C

692 Injured Party C

693 Weapons C

694 Description (unlimited characters) C

695 Type (e.g., physical, verbal) C

696 Date Occurred C

697 Time Occurred C

698 Date Reported C

699 Time Reported C


701 Incident Report C

702 Ability to attach a file to an incident record. C

703 Ability to incorporate spell check into any free text field.

C

704 Ability to for incident reports to cause an incident to be documented in the daily jail activity log.

C

705 Ability to add supplemental reports to incident records.

C

706

Ability to link an unlimited number of incident reports to inmate records. If limited, indicate the maximum permissible in the "comments" section.

C

707 Ability to submit a report to a supervisor. C

708 Ability to alert supervisors that a report is ready for review via:

709 Email O

710 Other (describe in "Comments" section) O

711 Ability for defined supervisors to perform the following electronically when logged onto the System:

712 Receive Reports O

713 Review a log of reports requiring approval (e.g., pending report approval queue)

O

714 Review a specific report O

715 Edit a Report O

716 Approve a report O

717 Reject a report O


718

Ability to record if disciplinary action is recommended with the ability to enter an unlimited amount of disciplinary codes. If limited, indicated the maximum permissible in the "comments" section.

C

719 Ability to record if charges were filed against any individual associated with the incident.

C

720 Ability to record the following related to an incident:

721 If an officer was defending another officer C

722 If an officer was defending an inmate C

723 If an officer had to restrain an inmate for the inmate's safety

C

724 Comments C

725 Ability to record the investigative officer for an incident.

C

726 Ability for Agency to create custom forms and reports, including but not limited do:

727 Supplemental Report C

728 Disciplinary Report C

729 Hearing Number C

730 Discipline

731 Ability for agency to define violation types. C

732 Ability for agency to classify violation types as:

733 Major C

734 Minor C

735 Ability to record a penalty for each discipline. C

736 Ability to capture multiple violation types pertaining to the identical event.

C

737 Ability to capture the following related to each violation:

738 Date and Time C

739 Location C

740 Reporting officer C

741 Witness information C

742 Others involved C

743 Inmate behavior C

744 Evidence C

745 Disposition of evidence C

746 Use of force C

747 Narrative C

748 Prisoner Information C

749 Violation (and description) C

750 Sub-violations (and descriptions) C


751 Penalties C

752 Ability to generate a report that incorporates captured violation information.

C

753 Ability for each violation to generate a unique number.

C

754 Ability to associate comments with specific violations.

C

755 Ability to associate the violation number with the inmate's identification number.

C

756 Ability to duplicate violation reports to multiple inmates.

C

757 Ability to capture the following related hearing information:

758 Waived (y/n) C

759 Date/Time C

760 Location C

761 Investigating officer C

762 Disposition C

763 Time loss C

764 Start/End dates of discipline C

765 Privileges lost C

766 Hearing Officer C

767 Comments (indicate maximum permissible in the "comments" section)

C

768 Ability to generate a report that incorporates captured hearing information.

C

769 Ability for agency to create custom hearing form, capturing agency-specified fields.

C

770 Inmate Incident Standard Outputs

771 Ability to generate an inmate discipline record, containing the following information:

772 Inmate information C

773 Violations C

774 Date/Time C


776 Discipline Log by Booking Number C

777 Date/Time C

778 Reporting officer C

779 Violation type code C

780 Violation Location C

781 Facility/Agency D

782 Inmate Grievances

783 Ability provide fields to capture inmate grievances, including:


784 Date/Time C

785 Grievance Type C

786 Entered by C

787 Narrative (indicate maximum permissible in "comments" field)

C

788 Staff Response C

789 Responded by C

790 Date Responded C

791 Expiration to Appeal C

792 Ability for agency to define grievance types. C

793 Ability to document investigation of grievance. C

794 Ability to alert supervisor upon entry of a new grievance.

C

795 Ability to specify particular staff members when entering a grievance.

C

796 Ability to provide a drop-down menu of staff members from which the user may enter the appropriate officer.

C

797 Ability for user to enter (via free text) an officer if they do not appear in the drop down menu.

C

798 Ability to specify multiple staff members when entering a grievance.

C

799 Ability to assign a grievance to an individual for investigation.

C

800 Ability to document outcome of grievance investigation:

801 Disposition C

802 Narrative C

803 Investigating officer C

804 Appeal Date C

805 Ability to document outcome of grievance investigation:

806 Appeal Officer C

807 Disposition C

808 Narrative C

809 Date Responded to Appeal C


811 Grievances by Date C

812 Grievances by Inmate C

813 Grievances by Facility C

814 Court Appearances and Transactions

815 Ability to capture sentence begin and end date. C

816 Ability to perform good time calculation. C


817 Ability to calculate time to be served and provide a release date.

C

818 Ability for release date and calculations to include multiple charges.

C

819 Ability to override time calculations. C

820 Ability to track the following inmate information related to court appearances:

821 Attorney C

822 Scheduled Release Date C

823 Scheduled Time Served date C

824 Date Convicted C

825 Sentencing Date C

826 Status Code (Agency Defined) C

827 Hold For C

828 Sentence Begin Date C

829 Sentence End Date C

830 Court C

831 Sentenced by C

832 Alternate ID Number O

833 Alternate ID Type (e.g., Federal) O

834 Ability to track court appearances by:

835 Inmate C

836 Date C

837 Time C

838 Location C

839 Type (Civil, Criminal) C

840 Ability to flag upcoming court appearances on inmate record.

C

841 Ability to show court appearances in the master jail schedule.

C

842 Court Transactions

843 Ability to capture unlimited court appearances. C

844 Ability to link court transactions to the applicable charge.

C

845 Ability for court transactions to automatically populate (from CCAP):

846 Court file number D

847 Bond Amount (Tranfer to Stellar System) D

848 Inmate Information D

849 Ability for bond amount to automatically generate based on court transaction type.

D

850 Ability to maintain bond history. C


851 Ability for charge information to be automatically updated based on modifications to bond amount in Court Transactions.

C

852 Ability to record the following related to court transactions:

853 Date and Time Entered C

854 Date of Appearances C

855 Time of Appearances C

856 Courtroom/Branch C

857 Bond Amount C


C

859 Ability to generate court transaction reports against the following parameters:

860 Entry Clerk C

861 Inmate List C

862 Ability to require entry clerk to enter user ID when providing modifications to court transactions.

C

863 Transportation Log

864 Ability to provide dedicated fields to log all transportation including, but not limited to:

865 Inmate court appearances D

866 Inmate medical appointments D

867 Inmate education programs D

868 Inmate work release D

869 Transportation events (pick-ups, transports) D

870 Prisoner releases D

871 Disciplinary and grievance hearings O

872 Transported inmate destination D

873 Ability to track inmate hazards in the transportation log.

D

874 Ability for transportation log to be populated with data from other modules in the System.

D

875 Ability to record the following for all transports involving vehicles, including but not limited to the following:

876 Inmates O

877 Drivers O

878 Vehicle used O

879 Locations (to and from) O

880 Ability to generate agency-defined transport sheets.

D


881 Ability to generate report of transportation activity by individual vehicle.

D

882 Ability to associate a transporting officer with a specific transport.

D

883 Charges

884 Ability to enter an unlimited number of charges for each inmate.

C

885 Ability to link statute numbers and descriptions to each charge.

C

886 Ability to import the modifier table from CCAP/NCIC into a statute code table.

C

887 Ability to import the statute table from CCAP/NCIC into a modifier code table.

C

888 Ability to add agency charge codes to the statute code table.

C

889 Ability to enter a statute that is not available in the statute code table (e.g., free text in drop down field).

C

890 Ability to associate a description with a statute entry (e.g., in the event entering a statute that is not available in the code table).

C

891 Ability to support modifiers to charges. C

892

Ability to support an unlimited number of modifiers to a charge. If limited, indicate the maximum permissible in the "comments" section

C

893 Ability to satisfy a charge and include the following:

894 User Entering Information C

895 Reason for Satisfying/Disposition C

896 Receipt Number C

897 Date Satisfied C

898 Ability to distinguish which charges are satisfied.

C

899 Ability to capture the following related to each charge:

900 Date of Offense C

901 Date of Arrest C

902 Date of Entry C

903 User Entering Information C


905 Issuing Agency C

906 Citation Number C

907 Case Number C


908 Court File Number C

909 Severity C

910 Charge Type C

911 Counts C


C

913 Ability to capture bond amount as part of charge.

C

914 LiveScan Transfer

915 Ability to transfer booking information to LiveScan for fingerprinting.

C

916

Ability to create an OCA (Originating Case Number) number and ATN (Automatic Tracking Number) number as required to capture fingerprints and transfer the information to the State.

C

917

Ability to create a new OCA(Originating Case Number) number and ATN(Automatic Tracking Number) number as required to capture fingerprints and transfer the information to the State when an inmate has charges added.

C

918

Ability to assign a previous OCA(Originating Case Number) number and ATN(Automatic Tracking Number) number as required to capture fingerprints and transfer the information to the State from a previous charge to a new charge

C

919 Ability to record the TCN number that is returned from the state in response to a LiveScan submission

C

920 Medical (Compliance with any applicable HIPAA)

PREA

921 Ability to track medication information. O

922 Ability to track the following information related to medication:

923 Amount O

924 Frequency O

925 Begin Date O

926 End Date O

927 Prescribing Doctor O

928 Inmate O

929 Prescription number O

930 Ability to track the disposal of medication. D

931 Ability to capture all psychiatric treatment information.

D


932 Ability to log inmate doctor or nurse visits. D

933 Ability to record if medical treatment was paid for.

D

934 Ability to generate a report of unpaid medical treatment by:

935 Inmate O

936 Bill To O

937 Ability to track medical tests, including the following information:

938 Test Type (blood, urine, etc.) O

939 Date/Time Test Taken O

940 Inmate O

941 Result O

942 Cost O

943 Bill To O

944 Quantity O

945 Date/Time Test Read O

946 Person conducting test O

947 Scheduling/Calendar

948 Ability to create a master schedule for all inmate activities.

D

949 Ability to define times that events can be scheduled.

D

950 Ability for court transactions that specify dates and times (e.g., scheduled hearings) automatically populate a master calendar.

D

951 Ability to enter an unlimited number of scheduled events for each inmate.

D

952 Ability to create pre-scheduled events on the master schedule:

953 One-time D

954 Recurring D

955 Ability to provide fields to capture the following information for each scheduled event:

956 Date and Time of start D

957 Date and Time of completion D

958 Reason for event D

959 Location transfer from D

960 Location transport to D

961 Transporting officer D

962 Writ D

963 Court File Number D

964 Entered by D

965 Comments D


966 Ability to filter master schedule by:

967 Date D

968 Inmate D

969 Activity category D

970 Facility Information (From or To) D

971 Ability to search for an event on the master schedule by:

972 Date and time D

973 Activity category D

974 Event location D

975 Inmate D

976 Ability to modify an event on the master schedule.

D

977 Ability to delete an event on the master schedule.

D

978 Ability to provide security provisions to limit who is able to add, modify and delete events on the master schedule.

D

979 Ability for inmate association/keep separate/hazards/alerts to be printed on the calendar.

D

980 Ability to merge the information into specific columns on a Word document for printing.

D

981 Ability to print court dispositions for each inmate that is going to court.

D

982 Ability to generate an inmate court calendar report that details the following information:

983 Time of Transport D

984 Officer Transporting O

985 Inmate D

986 Cell Number O

987 Location Transporting To D

988 Reason for Transport D

989 Notes D

990 Date Prepared D

991 Prepared By D

992 Verified By D

993 Ability to identify if an inmate is on the court calendars as previously scheduled (included aliases).

C

994 Ability to associate aliases with inmates. C

995 Ability to capture the clerk that verified the court calendar.

C


996 Ability to generate an inmate disposition report that identifies the following information:

997 Inmate name C

998 Cell Number C

999 Booking Number (and suffix) C

1000 Date C

1001 Time C

1002 Judge C

1003 Charge(s) C

1004 Disposition(s) C

1005 New Charge(s) C

1006 Disposition(s) C

1007 Next Scheduled Court Appearance C

1008 Officer Information C

1009 Inmate Programs

1010 Ability to review and approve inmate participation in programs.

D

1011 Ability to maintain program schedules including and start and end times.

D

1012 Ability to schedule inmate transport based on program facility and start and end time.

D

1013 Ability to produce a report of inmates scheduled to participate in programs.

D

1014 Ability to record the names of instructors. C

1015 Ability to assign multiple inmates to a program with one transaction.

D

1016 Ability to re-enroll an inmate in a program that was previously dropped.

D

1017 Ability to identify the type of referral of an inmate to a program.

D

1018 Ability to associate comment fields with inmate referral.

D

1019 Program Attendance and Performance Tracking

1020 Ability to track program attendance. D

1021 Ability to record information regarding an inmate's program attendance, including, but not limited to:

1022 Start date D

1023 Finish date D

1024 Discharge/Drop Information Date D

1025 Certification received/Completion Date D

1026 Ability to add notes to an inmate's program class participation.

D


1027 Ability to identify when inmate has completed a program.

D

1028 Visitor Management

1029 Ability to schedule visitors/PROFESSIONAL VISITS

C

1030 Ability to provide dedicated fields to capture visitor data, including, but not limited to the following:

1031 Name C

1032 Address C

1033 Date of Birth C

1034 Sex C

1035 Race C

1036 Relationship C


1038 Date and time of visit C

1039 Area of Visit C

1040 Duration of Visit C

1041 Ability to maintain agency rules regarding visits to an inmate (e.g., no children, no contact, victims).

C

1042 Ability to maintain a list of visitors that have been preapproved per inmate.

C

1043 Ability to check visitors against list of approved visitors.

C

1044 Ability for visitation list to be generated based on:


1046 Discipline Status (e.g., inmates that are not permitted visitors)

C

1047 List of approved visitors (per inmate) C

1048 Ability to maintain a list of visitor(s) who are prohibited from visiting any inmate.

C

1049 Ability to check visitors against lists of prohibited visitors.

C

1050 Ability to alert user if visitor has previously visited that day.

C

1051 Ability to assign a role to a visitor including but not limited to:

1052 Family C

1053 Attorney C

1054 Clergy C

1055 Law Enforcement C

1056 Agency Defined C


1057 Ability to view history of visitors by:

1058 Visitor name C

1059 Inmate name C

1060 Date C

1061 Inmate Detainers

1062 Ability to capture and record detainer/hold information for an inmate that is housed at another facility.

C

1063 Ability for agency to define detainer types. C

1064 Ability to enter booking number for an inmate and auto-populate associated fields (e.g., name, DOB, etc.)

C

1065 Ability to record detainer information without a booking number (e.g., allow user to enter if booking number is unavailable).

C

1066 Ability to capture the following related to detainers:

1067 Booking/Inmate Information C

1068 Date and Time of Entry C

1069 Entry Operator C

1070 Facility C

1071 Court C

1072 Bond/Find Amount C

1073 Court File Number C

1074 Charge Information C

1075 Location of Paperwork C

1076 Issuing Agency C


C

1078 Ability to capture the following related to cancelled detainers:

1079 Date and Time of Cancellation C

1080 Reason for Cancellation C

1081 Entry Operator C

1082 Keep Separate

1083 Ability to track inmate affiliations, including but not limited to:

1084 Gangs C

1085 Co-Defendants C

1086 Enemy Lists C

1087 Housing Locations C

1088 Victims C

1089 Ability for agency to define inmate affiliation types.

C


1090 Ability to display current housing location and name when entering an inmate's booking number.

C

1091 Ability for "Keep Separate" information to remain active until manually deleted.

C

1092 Ability for "Keep Separate" information to be maintained after inmate release (e.g., in case of subsequent bookings).

C

1093 Ability to record the following regarding "Keep Separate" information:

1094 Inmate C

1095 Person entering information C

1096 Activated Date/Time C

1097 Authorized by C

1098 Reason for Activation C

1099 Entry Clerk C

1100 Date/Time Deactivated C

1101 Reason for Deactivation C

1102

Ability to record "Keep Separate" information for individuals that have not yet been booked (assuming the not yet been booked individual has been booked previously and exists historically within the system).

C

1103 Inmate Release

1104 Release Processing

1105 Ability to process the release of inmates. C

1106 Ability to capture the following information related to each release:

1107 Date C

1108 Time C

1109 Entry Operator

1110 Reason for Release C

1111 Ability to prevent release of an inmate if charges have not been satisfied.

C

1112

Ability, when attempting to release an inmate with unsatisfied charges, to prompt user to satisfy charges as part of release process without aborting the release.

C

1113 Ability to provide a release checklist to ensure that all appropriate release criteria and actions have been taken.

C

1114 Ability to display the current status of the release checklist and identify outstanding tasks necessary to complete the release process.

C


1115 Ability for release of an inmate to trigger appropriate alerts (e.g., victim notification, property return).

C

1116 Ability to prevent release of inmate prior to checking for warrants.

C

1117 Ability to automatically generate a print release sheet containing agency defined data elements.

C

1118

Ability to alert user to generate a Circuit Court Bond Form following release (WI Form cr203) dependent on an agency-defined reason for release (i.e., Bond Posted).

C

1119 Ability automatically update inmate log upon release of inmate.

C

1120 Ability for system to automatically assign Court Date dependent on defined reason for release (i.e., Bond Posted)

C

1121 Ability for agency to configure the algorithm to determine appropriate Court Date.

C

1122 Ability for court date algorithm to incorporate any combination of the following parameters:

1123 Length since release (e.g., 4 weeks) C

1124 Excluded days (e.g., No Mondays) C

1125 Ability to manually enter/override recommended court date.

C

1126

Ability to export inmate release information (Booking Number and suffix, Inmate Name, DOB, etc.) at an agency-defined time interval in an ASCII file format for interface purposes.

C

1127 Victim Notification

1128 Ability to associate victims with inmates. C

Ability to Interface with VINE C

1129 Ability to track the following victim information:

1130 Name C

1131 Phone number C

1132 Email addresses C

1133 Address C

1134 Associated Inmate C

1135 Ability to automatically alert user at time of release of associated victims to be notified.

C

1136 Ability to run the victim information reports by any combination of the following:

1137 Date Range C


1139 Associated inmate C


1140 Agency defined fields C

1141 Ability to automatically generate victim notification letters upon release of an inmate.

O

1142 Ability for agency to determine which information is included as part of notification letter.

C

1143 Ability to capture notification activities, including but not limited to:

1144 Date/Time Notified C

1145 Notifier C

1146 Method of Notification C

1147 Action required (drop down list) C

1148 Narrative documentation of findings) C

1149 Ability to run the following reports regarding victim notifications by any combination of the following:

1150 Date Range C


1152 Notifier C

1153 Agency defined fields C

1154 Misc Requirements

1155

Does the JMS accommodate initial and supplemental booking, express (no-name) booking for uncooperative persons, and criminal history booking for non-custody arrests?

C

1156 Will the system generate wristbands, ID cards, and/or wanted/missing posters without the images being integrated to the JMS module?

O

1157 Does the system automatically assign a booking number?

C

1158 Is the format of the booking number segregated by agency?

C

1159 Does the system allow interruption of the booking process and continuance later?

C

1160 Does the system allow the agency to define restricted entry fields during the booking process?

C

1161 Is the system able to relate a booking to a law incident?

C

1162

Does the system provide for generation of pre-formatted reports, such as dissemination log, individual arrest report, arrest summary report, arrests by day and hour, etc.?

C


1163 Can the system generate an identification wristband for each inmate booked into the jail?

C

1164

Does the system display any pre-existing information about the person being booked, including medical history and fingerprint classification, with any previous risk assessment performed available for review and updating?

C

1165

Does the system also provide the ability to automatically duplicate offenses to save the user the time of re-keying (e.g. a person being charged with 14 counts of theft)?

C

1166

Does the system allow the entry of virtually unlimited items of personal property taken from the inmate and print a receipt that both the inmate and the jailer sign, confirming property and cash taken from the inmate?

C

1167

Does the system accommodate entry of the property storage location/locker and warn the user if the location is already being used for another inmate's property?

C

1168

Does the system allow standard jail property issue (e.g. blankets, sheets, etc.) with different issues definable for male and female inmates and risk factors?

C

1169 Does the system provide for recording of return of jail-issued property upon release?

C

1170 Does the system enable the user to limit issue based on risk assessment?

C

1171 Does the system provide the ability to enter the responsible agency for billing purposes?

C

1172

Does the system have the ability to automatically compute agency billings for housing of inmates from other agencies at a specified rate?

C

1173 Does the system allow the agency to pre-define jail cells and capacities for the purpose of inmate location assignment?

C

1174 Does the system accommodate multiple housing facilities in determining housing assignment?

O

1175 Does the system accommodate restriction in housing by gender?

C


1176

Does the system account for an inmate’s assigned housing location, as well as temporary locations in/out of the facility, allowing a user to check on an inmate's location by a name inquiry?

C

1177 During the booking process, does the system provide the following inmate assessments:

1178 Check for Outstanding Civil and Criminal Wants in the System

C

1179 Check for Juvenile Status C

1180 Suicide and Medical Assessment C

1181 Risk Evaluation/Classification C

1182 If the system finds outstanding wants upon booking, does the system allow the user to add the offense to the booking and clear the want?

C

1183

If the system finds an outstanding civil process upon booking, does the system allow the user to enter service information if the process is served at booking?

C

1184 Does the system provide suicide, medical, and risk assessment questions that are agency-definable, with no programming involved?

C

1185

Does the system accommodate automatic scheduling of commitments for inmates serving their sentence in increments, such as on weekends or work release programs?

C

1186 Does the system provide safeguards against releasing an inmate who should not be released if:

1187 Outstanding Holds Exist for the Inmate C

1188 The Inmate's Scheduled Release Date and Time is in the Future

C

1189 Bonds Have Not Been Cleared C

1190 Jail Issued Property has not Been Returned or Otherwise Accounted for

C

1191 Does the system provide for appropriate release documents, such as property receipt and a release and hold harmless agreement?

C

1192

Does the system accommodate entry of jail visitor names and linking of name and descriptive information to the visited inmate's record?

C

1193 If the visitor’s name is already in the central names table, does the system display any existing wants and alerts?

C


1194 Does the system accommodate logging of all events occurring in the jail, including the following:

1195 Bookings C

1196 Releases C

1197 Meal Times C

1198 Visits C

1199 Please list additional event log fields. C

1200

Does the system accommodate scheduling of events in the jail, including inmate movement, so that once the scheduled events are completed, the system allows the event records to be posted to the event history log without requiring re-entry of information?

C

1201 Does the system provide pre-formatted reports for condensing jail information, including the following categories:

1202 Booking Summaries C

1203 Inmate Population C

1204 Jail Events by Day and Hour C

1205 Demographic Reports C

1206 Medical Reports and PREA C

1207

Does the system provide the ability to facilitate quick movement of an inmate or group of inmates into temporary locations or back to assigned housing, including narrative/comments with spell check?

C

1208

Does the system allow/disallow juvenile bookings and provide special instructions for the booking of juveniles to appear at the beginning of the booking process?

C

1209 Does the system allow the ability to redact certain information prior to dissemination, such as juvenile information?

C

1210

Does the system enable the automatic creation of a hold for an inmate who has committed certain crimes that require a conditional release?

C

1211 Does the system allow the entry of good time and bad time when calculating the release date?

C


1212

Does Fingerprint Interface let users extract biographical and arrest data from the system and populate the data automatically on fingerprint cards?

C

1213 Does the Live Scan Fingerprint Interface help prepare fingerprint files for electronic transfer to state and federal agencies?

C

1214 Does the interface enable officers to revise data formats to conform to changing federal, state, or other requirements?

C

1215 Do officers have the ability to set up “tags” that define the data formats and fields that agencies want to appear on the fingerprint cards?

D

1216 Does the system have easily customizable reports for local data while being searchable on any field?

C

1217 Does the system allow for templates or officer specific permissions surrounding access and entry?

D

1218 Does the system restrict viewing, field entry, printing, and dissemination of information to permissions?

C

1219 Does the system automatically verify map locations for address entries (ex. Huber addresses or home addresses)?

D

1220 Is the system compatible with other area agencies running the same system?

C

1221 Does the system easily allow for partial name searches?

C

1222 Does the system easily allow combining of names without automatically saving data folders as aliases?

C

1223 Does the system allow for multiple entries of body anomalies, with photos (i.e. tattoos and piercings)?

C

1224 Does the system automatically populate bonds when the charge is chosen, but still allows the officer to override if necessary?

C

1225 Does the system allow for multiple court comment entries?

C

1226

Does it have its own required standalone photo capture or can it utilize a third party solution. Is this photo connected to the current booking for easy reference/retrieval?

C


1227 Does it have the capacity for disciplines and hearing to be entered and logged that links to inmates and can be retrieved?

C

1228 Is it able to generate reports for meal restrictions and keep apart lists? Future events such as work out/work in, transports, notes?

C

1229 Does the system have a place to document “keep aparts” and notify user if they attempt to house conflicting inmates together?

C

1230

Does the system store some information from previous bookings or contacts; such as height, weight, eye color, hair color, address, and emergency contact, place of birth and education level?

C

1231

Does the system have the ability to document Scar, Marks, and Tattoos by type and location, along with a description; and a way to search SMTs by type, location, description?

C

1232 Can incident reports be written within the system and does the system allow linking of report to inmate by ID #?

C

E-7 Field Reporting Functional Requirements E-7.1 Questions-None

E-7.2 Requirements


Field Base Recording Requirements


Item #


1 Ability to enter incident reports either:

2 In a desktop environment C

3 In a mobile environment C

4 Ability to support a multi-jurisdictional environment.

C

5 Field Based Reporting fields and workflow are configurable by the system administrator for each individual agency and can be viewed by approvers.

C


6 Ability to capture information required for UCR reporting.

C

7 Ability to capture information required for NIBRS reporting.

C

8 Ability to capture name information for:

9 Suspects C

10 Witnesses C

11 Victims C

12 Other persons C

13 Ability to capture location information for:

14 Involved persons C

15 Involved incident locations C

16 Ability to enter multiple locations and addresses for incident location

D

17 Ability to capture property information from the field.

C

18 Ability to enter an unlimited number of:

19 Persons C

20 Property C

21 Vehicles C

22 Offenses C

23 Identification types (SSN, driver's license, ID

card, etc.). C Ability to redact Information

upon approval of cases

24 Ability to provide a day/night mode. C

25 Ability to initiate queries into one or more databases from within the field reporting application.

C

26 Ability to attach files to reports. C

27 Ability to alert Records in the report where media and other related files can be found

D

28 Ability for vendor to provide code tables compliant with the following standards:

29 NCIC C

30 UCR/IBR C

31 Ability to support digital signatures. C

32 Dictation capability for narrative D

33 System Integration

34 Ability to automatically logon to the field reporting application upon logon to the Mobile application.

C


35

Ability to populate field report fields with required information captured in CAD (e.g., in the event a user is completing an incident report in a desktop environment). If any information cannot be transferred to the field reporting application, indicate the data fields in the "comments" section.

C

36 Ability to Capture and update information from RMS side for Master names, addresses and vehicles

C

Pop up to Avoid duplicating master names

37 Ability to receive dispatch alerts and/or indicators while field reporting application is in use.

C

38 Ability to incorporate coordinates from mobile mapping into field report.

C

39 Ability to link a case report to related call for service record in the CFS module.

C

40 Ability to handle multiple case reports (e.g., originals, supplemental) per CAD incident.

C

41 Ability to provide external system query functionality and features available in the RMS in the field reporting software.

C

42 Ability to enter booking data and submit the data to the JMS prior to report finalization:

43 Subject information C

44 Offense information C

45 Case Report Number C

46 Incident Information C

47 Ability to send subject information to JMS in real-time.

C

48 Ability to update data in the RMS application as soon as the report approval process is completed.

C

49 Data Entry

50 Ability for multiple officers to simultaneously provide input to a single case report after a case report number is assigned.

C

51 Ability to support input via:

52 Bar code readers C

53 Card swipe device C

54 Keyboard C

55 Touch screen C

56 Voice Dictation D

57 Ability to accelerate routine data entry tasks (i.e., workflow functionality) with the following:


58 Auto-population based on matches on

identification fields within the MNI (e.g., name, social security number, driver's license number)

C

59 Code-driven drop-down menus C

60 Shortcut keys (e.g., BRO = Brown) C

61 Ability to provide user entering a name with a list of potential existing master name records based on a variety of criteria, including:

62 Exact spelling C

63 Partial name C



66

Ability to include codes for non-criminal activity in offense code table (e.g., for incidents that do not involve criminal activity but which the agency would like to track).

C

67 Ability for each member agency to update codes at their discretion.

C

68 Ability to support the population of data fields from query returns (e.g., Master Name Index, NCIC)

C

69 Ability to query the following applications, databases and systems upon entry of a name:

70 RMS C

71 JMS C

72 Wisconsin TIME System C

73 TraCs O

74 General Data Quality Controls

75 Ability to provide word processing capabilities on narrative and comment fields, including, but not limited to:

76 Text wrap C



79 Spell check C

80 Copy and paste C

81 Grammar check C

82 Ability for drop down lists to incorporate NCIC codes where applicable.

D

83 Ability to define mandatory fields in data entry screens:



85 By Member Agency (e.g., PTSO defines

mandatory fields differently than SPPD) C

86 Ability to identify mandatory fields based on previously entered data (e.g., crime type).

C

87 Ability to limit available values in subsequent code tables based on previously entered data (e.g., crime type).

C

88 Ability to visually distinguish between mandatory and optional fields.

C

89 Ability to prompt user to complete any mandatory fields not completed.

C

90 Ability to create mutiple templates per agency indicating required and optional options

91 Data Validation

92 Ability to perform data validation:

93 At time of entry - prior to submission D

94 At time of submission C

95 Ability to not prevent a user from entering data into subsequent data fields if data fails validation (or is missing).

D

96 Ability for agency to designate which fields require data validation.

C

97 Ability to validate data to ensure that only valid codes have been used.

C

98 Ability to validate location information at time of data entry.

C

99 Ability to indicate unverified locations. D

100 Ability to validate location information against CAD geofile.

D

101 Ability to validate arrest times and dates are always after incident times and dates

102 Report Writing and Development

103 General

104 Ability to capture offense information for multiple offenses.

C

105 Ability to assign multiple offenses to multiple individuals within an incident report (e.g., two offenses go to person A, one goes to person B).

C

106 Ability to translate offenses codes into UCR/IBR codes.

C

107 Ability to accommodate reports for non-criminal activity (e.g., informational).

C


108

Ability to create a dictionary of standard language templates for reports that officers input frequently (e.g., standard language for domestic violence situations).

C

109 Ability to enter narratives of unlimited length in all report types. If limited, enter the maximum permissible in the "comments" section.

C

110 Ability to identify all required forms/reports based on offense type.

C

111 Ability to populate data across report forms to eliminate redundant data entry.

C

112 Ability for corrected data in a field (e.g., address) to auto populate across related report forms.

C

113 Ability to link incident reports (e.g., arrest report and use of force report).

C

114 Ability to automatically populate relevant fields of the arrest module with data already in the Master Name Index (MNI).

C

115 Form Generation and Modification

116 Ability for Agency to create custom reports (e.g., form generator):

117 During Implementation C

118 Following Implementation, without vendor

intervention C

119 Ability for Agency to modify vendor provided reports (e.g., re-name data fields, add data fields, delete data fields, etc.)

C

120 Ability to modify any reports (vendor provided or created by Agency) over the lifetime of the System.

C

121 Ability for vendor develop all Agency-specific reports during implementation.

D

122 Ability for all reports to have the ability to automatically import appropriate data elements from other reports and/or master indices.

C

123 Ability to develop unique agency-defined questionnaires for specific reports (e.g., Runaway)

C

124 Ability to print questionnaires for signatures D

125 Ability to capture digital signatures D

126 Arrest/Incident Reporting

127 Ability to document incident and arrest information that captures all UCR/IRB required fields.

C


128 Ability for document to capture county ordinances

C

129 Ability for Agency to add data fields to the arrest report (e.g., for non-UCR data elements that the Agency would like to track).

C

130 Ability for Agency to delete data fields on the arrest report.

D

131 Ability for Agency to modify data fields to the arrest report.

D

132

Ability to document arrests for multiple agencies.

C

There will need to be requirements that force the report writers to indicate which agencies should count which arrests for reporting purposes

133 Ability to enter individual arrest information. C

134 Ability to enter mass arrest information. C

135 Ability to support multiple charges per individual. C

136 Ability to link information entered in the arrest database to all other applicable modules to eliminate the potential for duplicate data entry.

C

137 Ability to link an arrest report number with an incident report number.

C

138 Ability to export arrest information for pre-population into the booking module of the JMS.

C

139 Ability to provide arrest forms specific to adults and juvenile arrests.

C

140 Ability to capture parent/guardian information for juvenile arrests.

C

141 Dictation capability for narrative portion

142 Missing Person/Runaway Reports

143 Ability to capture all data required for missing person submission to CIB/NCIC

C

144 Ability to submit missing person data to CIB/NCIC

D Notifcation will still need to be sent to dispatch for validation

145 Ability for modification to missing person information to appropriately update CIB/NCIC.

D

146 Ability to cancel a missing person submission. D

147 Ability to capture all data required for runaway submission to CIB/NCIC

C

148 Ability to submit runaway data to CIB/NCIC D

149 Ability for modification to runaway person information to appropriately update CIB/NCIC.

D


150 Ability to cancel a runaway person submission. D

151 Field Interviews

152 Ability to log field contacts from the field reporting software.

C

153 Ability to automatically query the master name index upon entering a field contact.

C

154 Ability for field interview names to be added to the MNI.

C

155 Ability for user to be automatically notified of any alerts associated with the individual from the master name index search.

C

156 Ability to automatically update master indices upon submittal of a field contact, including but not limited to:

157 Names C

158 Vehicles C

159 Locations C

160 Ability to create and maintain field contact records with agency-defined data elements, including but not limited to the following:


162 Time of contact C

163 Name C

164 Location C

165 Vehicle information C

166 Property C

167 Clothing C

168 Narrative C

169 Ability to auto populate the following field contact fields from CAD:


171 Time of contact C

172 Location C

173 Name information C

174 Vehicle information C

175 Ability to track and associate a field contact record with an incident/case number.

C

176 Dictation capability O

177 Use of Force

178 Ability to capture the following information on use of force:

179 Officer Name C

180 Case Number C

181 Date of Incident C


182 Agency C

183 Unit C

184 Location of incident C

185 Suspect Injuries C

186 Officer Injuries C

187 Narrative C

188 Reason force was used C

189 Type of force (e.g., taser, pepper spray, etc.) C

190 Potential danger factors C

191 Medical Disposition C

192 Supervisor Notification Information (e.g., who,

when) C

193 Final Field Disposition C

194 Indicate if K9 participated C

195 Indicate if drugs or alcohol were involved C

196 Person involved (e.g., Name, Gender, Race,

Address, Phone Number) C

197 Ability for use of force report incidents to automatically link an individual's personnel record.

O

198 Ability to link use of force reports to original incident report.

C

199 Ability to automatically enter Use of Force into TraCs

D

The state is now requiring use of Force involving death or firearm discharge to be entered inot TraCs, I'm guessing that evenutally all use of force will need to be entered

200 Ability for use of force to automatically be forwarded to approvers through work flow

O

201 Citations and Accident Reporting

202 Ability to support an interface to Badger TrACS to transfer incident information from the Badger TrACS System.

C

203 False Alarm Reports

204 Ability to capture the following information from CAD regarding False Alarm Reports (if available):

205 Agency C

206 Date/Time C

207 Incident Number C

208 Address C

209 Owner Name C

210 Key holder Information C

211 Alarm Company C


212 Individuals on-site D

213 Contact Information C

214 License Number(s) D

215 Narrative C

216 Officer Name C

217 Supervisor O

218 Unit O

219 Supplemental Reports

220 Ability to add new information to a report after the initial case report has been submitted and approved.

C

221 Ability when writing a supplemental report to view the original incident report.

C

222 Ability to permit users to complete supplemental reports in the Field Reporting system before the original report is submitted to RMS.

C

223 Ability for multiple officers to simultaneously create and add supplemental reports regarding the same event.

C

224 Ability to link supplemental reports to the original report.

C

225 Ability to populate supplemental reports with information already in system.

C

226 Report Workflow

227 Report Initiation

228 Ability for each member agency to define call types that require an incident report to be written.

C

229 Ability to initiate a field report for the primary officer upon entry in the CAD application of a disposition code for a call type requiring a report.

C

230 Ability for CAD incident data to automatically populate a report template.

C

231 Ability for agency to define which CAD data populates a report template.

C

232 Report Submission

233 Ability to submit reports from the field. C

234 Ability to send confirmation indicating automated field reporting upload was completed successfully.

C

235 Ability to save a copy of an active report locally until the user receives confirmation of receipt of data from the RMS.

C


236 Ability to automatically maintain a log of automated field reporting transactions, including, but not limited to the following information:

237 Date and time of transmission C

238 User ID C

239 Report ID C

240 Ability to ensure that reports are compliant with UCR/IBR reporting requirements prior to submission.

C

241 Ability to prevent submission of a report with UCR/IBR errors.

C

242 Ability to ensure that reports are compliant with agency-defined reporting requirements (e.g., mandatory fields) prior to submission.

C

243 Ability to prevent submission of a report with missing information in agency-designated fields.

C

244 Ability to prompt officer as to which fields require correction.

C

245 Ability to describe the nature of the correction required.

C

246 Ability to route report to other individuals and entire divisions

C

247

Ability to set alerts that allow records staff to route reports to other agencies and office (HHS, DA's office, P&P) with the ability to enter e-mail addresses, fax and phone numbers

D

248 Report Approval

249 Ability for officers to submit reports electronically to a report approval queue (i.e., not to specific individual)

C

250 Ability to configure the automated field reporting system to support agency-specific processes/workflow at the following levels:

251 By Agency (e.g., single set-up for all law

enforcement agencies) C

252 By Member Agency (e.g., PTSO defines

process/workflow differently than SPPD) C

253 Ability to determine which type of reports require approval (e.g., arrest/incident vs. field interview) at the following levels:

254 By Agency (e.g., single set-up for both law

enforcement agencies) C


255 By Member Agency (e.g., PTSO defines which

reports require approval differently than SPPD) C

256 By Writing officer rather than template

If workflow were determined by the writing officer there will be far less templates required

257 Ability to alert supervisors that a report is ready for review via:

258 Email C

259 Mobile Message D

260 Ability for officers to indicate that a report requires immediate supervisor attention.

C

261 Ability for supervisors to perform the following electronically when logged onto the System:

262 Receive Reports C

263 Review a log of reports requiring approval (e.g., pending report approval queue)

C

264 Review a specific report C

265 Approve a report C

266 Reject a report C

267 Ability to lock a report from edits following report approval.

C Ability for next in workflow to override if chosen by error

268 Ability to provide the supervisor the option of approving the report or returning the report to an officer for corrections.

C

269 Ability for supervisors to attach electronic to notes to a report to indicate to the officer areas that need to be corrected.

C

270 Ability to for system to automatically delete corrective messages after a report has been approved by a supervisor.

C

271 Ability to track the status of reports (e.g., unwritten, incomplete, awaiting approval, approved).

C

272 Ability to provide separate approval process workflows dependent upon report type (e.g., primary vs. supplemental).

C

273

Ability for records personnel to complete an accuracy review for reporting requirement compliance prior to adding report to the RMS database.

C

274 Ability for records personnel to send reports back to supervisors if reports do not comply with reporting requirements.

C


275 Ability to designate personnel with the capability to modify submitted reports (e.g., supervisor/records personnel modify data fields).

C

276 Ability to communicate with Records when a report is high priority

C

277 Ability to designate what data fields may be modified by individuals that are not the report author.

C

278 Ability to electronically route reports to:

279 Specific Individuals (e.g., particular supervisor) C

280 Role Type (e.g., Supervisor group as opposed

to individual) C

281 Group/Special Unit (e.g., Detective Unit) C

282 Report Workload Management

283 Ability to work on multiple reports and multiple incidents simultaneously and toggle among them at the user's discretion.

D

284 Ability to save reports in progress. C

285 Ability to save reports locally. O

286

Ability to automatically save incomplete reports at the network level so that a user can access the report at a later time from a computer other than the one used to start the original report.

C

287 Ability to enter data when offline. C

288 Ability to begin to write and pre-populate a report at any time (following dispatch but prior to incident closure).

C

289 Ability to display the following field reporting information upon logon to the field reporting system:

290 Rejected reports C

291 Reports outstanding C

292 Ability to notify officers of rejected reports. C

293

Ability to send a rejected report to another officer or supervisor in a case when the writer of the report is out it needs to be fixed in a timely manner

D

294 Ability to notify officers of outstanding reports before logging off the Field Reporting system.

C

295 Ability for supervisors to see which reports have not been completed at the end of the shift.

C


296

Ability for Records to see audit trails and workflow so they can access where reports are in the workflow and communicate with other departements (DA/HHS) and agencies

C

E-8 Mobile Computing Functional Requirements E-8.1 Questions- None

E-8.2 Requirements


MOBILE Software Requirements


Item #


1 General Mobile Data Computing Features

2 Ability to support automatic screen refreshes of information.

C

3 Ability to support mobile devices via:

4 Laptops C

5 Tablets O

6 Smartphones O

7 Ability to require manual intervention for screen refresh.

D

8 Ability to log all mobile activities (e.g., chats, queries, uploads/downloads of field reports) with the following information:

9 Agency C

10 Date and time of transmission C


12 Mobile Workstation ID D

13 User ID/name C

14 Vehicle ID O

15 Ability to provide a visual alert if Mobile is receiving negative response from CAD system (no connection to CAD).

D

16 Ability to continuously attempt to reconnect to CAD system in the event connectivity is lost.

C

17 Mobile Application User Interface

18 Ability to support touch-screen functionality. C

19 Ability to accept input from:

20 Barcode reader O


21 Card swipe device O

22 Command entries on a command line O

23 Function keys (one touch keys) D

24 Point-and-click devices D

25 Ability to configure Mobile screen display (including layout) by:

26 Agency Wide C

27 Member Agency O

28 Agency Type (Fire vs. Law) D

29 Ability for users to configure their own mobile screen displays, including:

30 Font color C

31 Font size C

32 Day/Night mode C

33 Audible alerts C

34 Ability to restrict user configurable fields/displays at the following levels:


36 By Member Agency (e.g., WPD vs. MNSO vs.

WFD) D

37 Ability for user configuration's to be associated with user log-on (e.g., configurations are not workstation specific).

C

38 Ability to allow users to return to application default settings.

C

39 Ability to prevent incoming messages from preempting current work.

D

40 Logon/Logoff

41 Ability to require both user identification and password to logon.

C

42 Ability to meet and comply with all CJIS security requirements (including data encryption requirements per FIPS 140-2).

C

43 Ability to save data entered into user logon fields that remains the same from session to session (e.g., all information other than password).

C

44 Ability for each member agency to define mandatory logon fields.

C

45 Ability to automatically notify Communications of logon/logoff.

C

46 Ability to logon multiple individuals per unit. C

47 Application Integration

48 CAD/Mobile Integration


49 Ability to support a real-time data transmission between the CAD system and Mobile Computer.

C

50 Ability to continually receive call for service updates from Dispatch following initial dispatch.

C

51 Ability to log onto the CAD system from the Mobile.

C

52 Ability to support a single password sign-on to CAD, the Mobile and the operating system.

C

53 Ability for a unit logged on to automatically default to "available" status.

D

54 Ability to view all incident information available in CAD on the Mobile.

C

55 Ability to display all timers:

56 Generated from within the CAD application O

57 Created by a CAD operator O

58

Ability to run multiple applications (e.g., mobile, automated field reporting) on the Mobile at the same time, with CAD operations having precedence over reporting operations.

C

59 Ability to query CAD data from the Mobile. C

60 Ability to query any system interfaced to the CAD application.

C

61 Ability for Mobile user to update CAD call for service information.

C

62 Ability for call for service record to indicate the source of data entry.

C

63 RMS/Mobile Integration

64 Ability to query all RMS modules from within the Mobile application.

C

65 Ability to automatically query the Law Enforcement RMS upon dispatch:

66 Persons associated with call C

67 Locations associated with call D

68 Vehicles associated with call C

69 Ability for alerts created in CAD to be made available to users in the Mobile environment.

C

70 Ability for alerts created in the RMS to be made available to users in the Mobile environment.

C

71 Unit Status and Incident Information

72 Ability to display the following information on the screen during normal operations:

73 Availability of wireless connectivity D

74 Call status C

75 Current unit C


76 Current unit status C

77 Date and time C


79 Incident status C

80 Message information C

81 Unit ID C

82 Individuals assigned to unit (e.g., multiple fire

personnel on apparatus) O

83 Ability to update unit status from the Mobile application via:

84 Function Keys O

85 On-screen buttons (e.g., touch screen) C

86 Ability to define unit statuses by:

87 Agency-Wide C

88 Member Agency O

89 Agency Type O

90 Ability to view multiple calls simultaneously (e.g., in different windows).

C

91 Ability to open any incident to view dispatch data, units and incident notes.

C

92 Ability for Mobile user to view the following:

93 Logged on units D

94 Pending calls C

95 Active calls C

96 Ability to display incident status based on incident priority.

D

97 Ability to alert responding units when additional units are cleared or added to a call.

C

98 Ability for each unit status to be displayed in a unique color.

O

99 Ability to identify other units assigned to same call/incident.

C

100 Ability to uniquely display (e.g., color, symbol) different unit statuses of other units assigned to same call/incident (e.g., en route, on-scene).

C

101 Ability for Mobile user to add to call comments. C

102 Mobile Mapping

103 Map Navigation

104 Ability to provide users with the following map navigation functionality:

105 Pan from given area to adjacent area C

106 Return back to previous view D

107 Zoom in on area for enhanced detail C

108 Zoom out of an area C


109 Move up and down C

110 Move left and right C

111 Ability for user to update/modify map displays (e.g., preset default zoom levels and views).

D

112 Ability to support an internet mapping program. C

113 Ability to utilize color, text, and/or symbols to distinguish status of unit:

114 Incident Type C

115 Unit Status D

116 Ability to center map display on:

117 CAD incident location C

118 Specified geographic area O

119 Specified vehicle/unit O

120 Vehicle activating emergency button C

121 Ability to zoom to relevant map location by searching on available map layer information.

O

122 Ability to view map and mobile application on the screen at the same time.

O

123 Ability to cache map layers to minimize the amount of data transmitted wirelessly.

O

124 Ability for map to function without wireless connectivity.

C

125 Ability for user to select map layers for display. D

126 Ability to view other unit locations and last known locations in real time.

C

127 Ability to automatically refresh current vehicle location at agency-defined intervals.

C

128 Ability to update map with:

129 Unit locations C

130 Incident locations C

131 Ability to right click on a location to display information associated with that location.

D

132 Ability to display user-specified map layers (e.g., hydrants, hazards) surrounding an incident location.

O

133 Ability to click on a unit or incident in the incident queue or unit status bar and have it displayed on the map.

D

134 AVL Integration

135 Ability to support AVL/GPS functionality. C

136 Ability to display other field units on mobile map (assuming AVL and sufficient bandwidth).

C

137 Ability to filter display of field units on mobile map by:


138 Units associated with an incident O

139 Member agency (e.g., display only KSD units) O

140 Defined geographical area O

141 All units D

142 Ability to display vehicle location on a map and view progress toward incident location.

C

143 Ability to send the AVL location for calls initiated from the mobile computer.

O

144 Routing

145 Ability to automatically calculate directions from user's current location (on Mobile using AVL) to dispatched location.

O

146 Ability to support quickest-time routing for all dispatches.

O

147 Ability to recalculate directions to incident/specified location on the fly.

O

148 Ability to provide audible routing information. O

149 Ability to provide text-based routing information. O

150 Ability to provide closest cross streets. O

151 Ability to take into account the following when calculating routing directions:

152 Street speed limits O

153 Closed streets O

154 Ability to highlight on the map the recommended route from current location to a dispatched incident site.

O

155 Ability for Mobile user to turn recommended route ability on/off.

O

156 Emergency Key Functionality

157 Ability to initiate an emergency message transmission from a touch screen button or hot key.

C

158 Ability to automatically transmit the following information in an emergency situation:

159 Last known location C

160 Current location (with AVL) C

161 User ID C

162 Unit ID C

163 Ability for dispatcher to reset emergency key. D

164 Ability for the following to be notified upon emergency key activation:

165 Units within a defined proximity C


166 Member agency associated units (e.g.,

MNSO activates emergency key, only MNSO units are notified)

N/A

167 All units (regardless of member agency) C

168 Dispatch C

169 Mobile Dispatch Operations

170 Ability to receive dispatches in the Mobile environment.

C

171 Ability for dispatches to open automatically upon receipt in the mobile client.

C

172 Ability to alert mobile users that a new dispatch has arrived.

C

173 Ability for all personnel dispatched to an incident to receive notification when other dispatched personnel are en route.

D

174 Ability for all personnel dispatched to a call to receive notification of status and location changes of other personnel dispatched to the call.

O

175 Ability to see multiple locations for one call on mobile display.

O

176 Ability for Mobile users to add themselves to an incident.

C

177 Ability to access and read all call comments associated with a call regardless of whether assigned to the call.

C

178 Ability for mobile users to add information to a CAD incident.

C

179 Ability to display narrative information in reverse chronological order.

C

180 Ability to alert user of availability of information associated with a location (gate codes, hazards, premise history, pre-plans, etc.).

C

181 Ability to view previous call history for a location. D

182 Ability to view associated queries run within the Mobile system (e.g., if another user ran a identical plate earlier in the shift) pertaining to:

183 Name D

184 License Plate D

185 Ability to drill down in premise history to find links to:

186 Incidents D

187 Person D

188 Vehicles D


189

Ability to receive supplemental incident information (e.g., information not originally associated with call on initial dispatch) without interrupting or overlaying current screen.

O

190

Ability to indicate type of information that is attached to a call (e.g., gate code, hazard) so that user can decide whether or not to retrieve the information.

O

191 Ability to indicate to dispatcher that mobile device has received the dispatch.

O

192 Ability to alert user that supplemental incident information is available for viewing.

D

193 Ability for mobile screen to update automatically as new information is added to a call (e.g., without user intervention).

C

194 Ability to transmit status information to the CAD system in real time.

C

195 Ability to initiate a call for service from the Mobile. C

196 Ability for agency to define the types of calls that can be initiated by a field unit from a mobile device.

O

197 Call Dispositions

198 Ability to clear calls from the Mobile. C

199 Ability to require a call clearance code in order to clear a call from the Mobile.

D

200 Ability to provide a drop down menu for call dispositions.

D

201 Ability for each of the following to have unique Disposition codes:

202 Agency (e.g., universal) C

203 Agency Type (Fire vs. Law) N/A

204 Ability to prevent the appearance of non-applicable disposition codes.

D

205 Ability to provide a text field for disposition comments.

C

206 Ability to add comments to an active call. C

207 Ability for field personnel to clear from call. C

208 Ability to require a Mobile user to enter a disposition prior to clearing the last unit from the Mobile.

N/A

209 Be-On-The-Lookouts (BOLOs)

210 Ability to view BOLOs in the mobile environment. C

211 Ability for field personnel to generate BOLOs. N/A


212 Ability for BOLOs to contain identical information as generated in CAD.

N/A

213 Ability to search BOLOs in the field. C

214 Ability to view photos within a BOLO D

215 Ability to view attachments with a BOLO. D

216 Queries

217 Ability to provide a window from which officers can run common queries.

C

218 Ability to query and view pending calls. C

219 Ability to query and view active calls. C

220 Ability to query and view unit status by:

221 Geographic area (beat, sector, etc.) O

222 Individual unit/apparatus O

223 Ability to query and retrieve premise information for an address not associated with a call for service.

O

224 Ability to query the following systems from the mobile computer, assuming appropriate permissions:

225 CAD C

226 Law Enforcement RMS C

227 Wisconsin TIME System C

228 JMS D

229 Ability to search and query all appropriate databases with one query request.

C

230 Ability to support a query system that does not require information to be re-entered when searching across multiple databases.

C

231 Ability to conduct the following types of queries in the mobile environment:

232 Wild card D

233 Partial word D

234 Soundex D

235 Ability for the system to automatically run VIN and plates when information is entered into the appropriate fields.

C

236 Ability to automatically run the registered owner of the vehicle in a license plate query return.

C

237 Ability to save all query returns until user clears data.

C

238 Ability to produce an alert when a query return contains a record marked as potentially hot (e.g., flagged information in RMS or TIME System):

239 Audible alert C


240 Visual alert C

241 Ability to drill down into query returns regarding a potentially hazardous subject, vehicle, and/or location to find the details of that hazard.

D

242 Ability to sort query results on any returned field. D

243 Ability to notify user of a failed query (e.g., access to a database is unavailable)

D

E-9 Interface Functional Requirements E-9.1 Questions

Interface Pricing

1 What interfaces are included as part of the application package?

2 Are interfaces included in standard support?

E-9.2 Requirements-

Portage County Public Safety Software Replacement RFP

Interface Functional Requirements


Item

# Interface Functional Requirements Priority Response Comments

1 CAD Interfaces

2 E911

3 The system should include an interface to the 911 service provider to automatically populate CAD calls with 911 information when selected by dispatcher. C

4 The system should receive the raw spill data from the 911 service and import and properly parse it into the CFS via a serial or IP connection. C

5 The system should intelligently handle ANI/ALI rebids through the interface.

C

6 Ability to geoverify the E911 imported address immediately upon transfer.

C

7 Ability to determine a physical address from X/Y coordinates imported from the E911 phone system. C

8 Ability to transfer E911 call receipt time to CAD to track E911 time stamps. C


9 Ability to plot incoming E911 calls on the CAD and Mobile application map.

C

10 Next Generation 911 Capabilities C

11 Priority Dispatch

12 Ability to provide bi-directional interface with dispatch protocol software, Priority Dispatch ProQA, for medical call taking questions. C

13 PulsePoint

14 Ability to interface with PulsePoint software to provide current CAD calls requiring CPR. C

15 IamResponding

16 Ability to interface with IamResponding to notify subscribers of dispatched calls via text or page. C

17 Zoll ePCR

18 Ability to interface with Zoll to populate patient care records with data from EMS related CAD calls. C

19 ImageTrend

20 Ability to interface with ImageTrend Software to transfer CAD Call For Service data. D

21 G2 Phoenix

22 Ability to interface with Phoenix G2 Software to transfer CAD call event data.

D

23 RMS Interfaces

24 BadgerTraCS

25 Ability to import form data from the Wisconsin Badger TraCS10 system into the RMS module. C

26 Ability to transfer NCIC query information from the CAD/Mobile to the Wisconsin Badger TraCS10 system. C

27 Vendor stay current with code changes mandated by State TraCs system and update RMS software accordingly to accommodate changes. C

28 Ability to accommodate TraCs imports from multiple jurisdictions C

29 Protect

30 Ability to interface with WI Protect software to transfer referred incidents and arrests to the DA's system. C

31 Ability to submit cases via eReferral from RMS. C

32 Ability to choose which cases should be submitted through interface. C

33 Ability to include all case attachments. C


34 Ability to choose which attachments get submitted at the time of each case submission. C

35 Ability to send failure reports via email for any cases which did not submit successfully. C

36 JMS Interfaces

37 LiveScan

38 Ability to transfer booking information to LiveScan. C

39 Equivant Compas

40 Ability to interface with Compas classification software. C

41 Appriss VINE

42 Ability to interface with VINE to send booking information.

C

43 Securus AIS

44 Ability to send current inmate data to AIS ftp server on scheduled intervals.

C

45 Stellar Lockdown

46 Ability to interface with Stellar Lockdown to send inmate information for receipting, billing, fees and inmate account.

D

47 CCAP

48 Ability to capture court schedule data and compare to current inmates for court appearances.

D

49 Multiple Applications

50 NCIC

51 System should include an interface to the state/NCIC system.

C

52 Allow ability for authorized users to run NCIC queries from:

53 CAD C

54 Mobile C

55 RMS C

56 JMS D

57 System should restrict access to run NCIC queries to authorized users and/or user groups.

C

58 Ability to alert user of CIB/NCIC returns. C

59 System should allow NCIC query returns to populate Master Name and Master Vehicle records:

60 CAD C

61 Mobile C

62 RMS C


63

System should provide a list of all state/NCIC queries which have been run and the associated returns, filterable by date, query type, user and/or workstation.

D

64 National Data Exchange

65 The system should include an N-Dex IEPD compliant interface. D

66 Tyler (Financial)

67 Ability to interface with Tyler Munis financial software to export receipt data. O

68 Ability to export customer defined file of select fields to CSV or Excel file that could be imported into Financial System. D

69 Ability to customize receipt types and include that in export. D

70 Ability to track and export payment type received. D

71 Ability to process payments via credit card with county designated merchant processor. D

72 Web Interface

73 Ability to select and post specified data elements to a webpage for public information. (i.e. Warrants, Sheriff Sales)

O

74 Ability to export specified data elements to table to be posted to website

D


ATTACHMENT F

STANDARD TERMS AND CONDITIONS 1.0 SPECIFICATIONS: The specifications in this request are the minimum acceptable. When specific manufacturer and model

numbers are used, they are to establish a design, type of construction, quality, functional capability and/or performance level desired, unless otherwise specified. When alternates are bid/proposed, they must be identified by manufacturer, stock number, and such other information necessary to establish an acceptable equivalency. The County shall be the sole and final judge of equivalency.

2.0 HOW TO AMEND A REQUEST FOR BID, PROPOSAL OR QUOTE:

2.1 Public Works Projects are subject to Wis Stats 66.0901(5): If a person submits a bid or proposal for the performance of public work under any public contract to be let by a municipality and the bidder claims that a mistake, omission or error has been made in preparing the bid, the bidder shall, before the bids are opened, make known the fact that an error, omission or mistake has been made. If the bidder makes this fact known, the bid shall be returned to the bidder unopened and the bidder may not bid upon the public contract unless it is re-advertised and relet upon the re-advertisement. If a bidder makes an error, omission or mistake and discovers it after the bids are opened, the bidder shall immediately and without delay give written notice and make known the fact of the mistake, omission or error which has been committed and submit to the municipality clear and satisfactory evidence of the mistake, omission or error and that it was not caused by any careless act or omission on the bidder's part in the exercise of ordinary care in examining the plans or specifications and in conforming with the provisions of this section. If the discovery and notice of a mistake, omission or error causes a forfeiture, the bidder may not recover the moneys or certified check forfeited as liquidated damages unless it is proven before a court of competent jurisdiction in an action brought for the recovery of the amount forfeited, that in making the mistake, error or omission the bidder was free from carelessness, negligence or inexcusable neglect.

2.2 Non-Public Work Projects: After a Request for Bid/Proposal/Quote has been filed with the Portage County Purchasing

Department, the responder may submit an amended response BEFORE THE DUE DATE AND TIME set in the request. All the conditions and provisions of the original Bid/Proposal/Quote will be in effect. No submittals or amendments will be accepted after the due date and time of the request. This does not preclude the County from requesting additional information and/or clarification.

3.0 DEVIATIONS AND EXCEPTIONS: Deviations and exceptions from original text, terms, conditions, or specifications shall be

described fully, on the bidder's/proposer's letterhead, signed, and attached to the request. In the absence of such statement, the bid/proposal shall be accepted as in strict compliance with all terms, conditions, and specifications and the bidders/proposers shall be held liable.

4.0 QUALITY: Unless otherwise indicated in the request, all material shall be new, newest model year, and free from defects. Items

which are used, demonstrators, obsolete, seconds, or which have been discontinued are unacceptable without prior written approval by the County.

5.0 QUANTITIES: The quantities shown on this request are based on estimated needs. The County reserves the right to increase or

decrease quantities to meet actual needs. 6.0 DELIVERY: Deliveries shall be F.O.B. destination freight prepaid and included unless otherwise specified. 7.0 PRICING AND DISCOUNT: The County qualifies for governmental discounts. Unit prices shall reflect these discounts.

7.1 Unit prices shown on the bid/proposal or contract shall be the price per unit of sale (e.g., gal., cs., doz., ea.) as stated on the request or contract. For any given item, the quantity multiplied by the unit price shall establish the extended price; the unit price shall govern in the bid/proposal evaluation.

7.2 Prices established in continuing agreements and term contracts may be lowered due to general market conditions.

8.0 RESPONSES TO REMAIN OPEN: Responses must remain open and will be deemed to be open and subject to acceptance until awarding of the bid/proposal is finalized, or a minimum of sixty (60) days unless otherwise specified.


9.0 ACCEPTANCE-REJECTION: The County reserves the right to accept or reject any or all bids/proposals, to waive any technicality

in any bid/proposal submitted, request clarification of any bid/proposal, award a bid/proposal that is not the lowest price, and to accept any part of a bid/proposal as deemed to be in the best interests of the County.

10.0 GUARANTEED DELIVERY: Failure of the Contractor to adhere to delivery schedules as specified or to promptly replace rejected

materials shall render the Contractor liable for all costs in excess of the contract price when alternate procurement is necessary. Excess costs shall include the administrative costs and other costs attributable to the delay.

11.0 CONTRACT AND EXECUTION OF CONTRACT: Unless otherwise specified in the bid/proposal, the successful responder agrees to

enter into a contract, a copy of which will be on file in the office of the Portage County Purchasing Department. Contractor shall and will well and truly execute and perform this contract under the terms applicable to the satisfaction of the County and shall promptly make payment to each and every person or party entitled thereto of all the claims for work or labor performed and materials furnished in the performance of this contract.

12.0 ENTIRE AGREEMENT: These Standard Terms and Conditions shall apply to any contract or order awarded as a result of this

request except where special requirements are stated elsewhere in the request; in such cases, the special requirements shall apply. Further, the written contract and/or order with referenced parts and attachments shall constitute the entire agreement and no other terms and conditions in any document, acceptance, or acknowledgment shall be effective or binding unless expressly agreed to in writing by the County.

13.0 APPLICABLE LAW AND COMPLIANCE: This contract shall be governed under the laws of the State of Wisconsin. The Contractor

shall at all times comply with and observe all federal and state laws, local laws, ordinances, and regulations which are in effect during the period of this contract and which in any manner affect the work or its conduct. The County reserves the right to cancel this contract if the contractor fails to follow the requirements of s. 77.66, Wis. Stats., and related statutes regarding certification for collection of sales and use tax. The County also reserves the right to cancel this contract with any state or federally debarred contractor or a contractor that is presently identified on the list of parties excluded from federal procurement and non-procurement contracts.

14.0 LICENSES AND PERMITS: Contractor shall have and/or provide any and all licenses and permits required to perform the work

specified and furnish proof of such licensing authorization and permits with their bids if required. 15.0 ASSIGNMENT: No right or duty in whole or in part of the Contractor under this contract may be assigned or delegated without

the prior written consent of the County. 16.0 NONEXCLUSIVE CONTRACT: Unless otherwise stated, the County reserves the right to purchase work or materials outside of this

contract. 17.0 NONDISCRIMINATION & AFFIRMATIVE ACTION: In connection with the performance of work under this contract, the Contractor

agrees not to discriminate against any employee or applicant for employment because of age, race, religion, color, handicap, sex, physical condition, developmental disability as defined in s. 51.01(5), Wis. Stats., sexual orientation as defined in s. 111.32(13m), Wis. Stats., or national origin. This provision shall include, but not be limited to, the following: employment, upgrading, demotion or transfer; recruitment or recruitment advertising; layoff or termination; rates of pay or other forms of compensation; and selection for training, including apprenticeship. Except with respect to sexual orientation, the contractor further agrees to take affirmative action to ensure equal employment opportunities.

18.0 INDEPENDENT CAPACITY: The parties hereto agree that the contractor, its officers, agents, and employees, in the performance

of this agreement shall act in the capacity of an independent contractor and not as an officer, employee, or agent of the County. The contractor agrees to take such steps as may be necessary to ensure that each subcontractor of the contractor will be deemed to be an independent contractor and will not be considered or permitted to be an agent, servant, joint venture, or partner of the County.

19.0 SAFETY REQUIREMENTS: All materials, equipment, and supplies provided to the County must comply fully with all safety

requirements as set forth by the Wisconsin Administrative Code and all applicable OSHA Standards.


20.0 WARRANTY: Unless otherwise specifically stated, equipment purchased as a result of this request shall be warranted against

defects by the Contractor for one (1) year from date of receipt. The equipment manufacturer's standard warranty shall apply as a minimum and must be honored by the Contractor.

21.0 INSURANCE RESPONSIBILITY: If insurance is required, satisfactory proof of the existence and carriage of such insurance of the kinds and limits specified will be required.

22.0 CANCELLATION: The County reserves the right to cancel any contract in whole or in part without penalty due to non-appropriation of funds or for failure of the contractor to comply with terms, conditions, and specifications of this contract.

23.0 VENDOR TAX DELINQUENCY: Vendors who have a delinquent Portage County tax liability may have their payments offset by the County.

24.0 OPEN RECORDS: Both parties understand that the County is bound by the Wisconsin Public Records Law, and as such, responses and contracts are subject to and conditioned on the provisions of the law. Contractor acknowledges that it is obligated to assist the County in retaining and producing records that are subject to Wisconsin Public Records Law, and that the failure to do so shall constitute a material breach of the contract, and that the Contractor must defend and hold the County harmless from liability under that law. Except as otherwise authorized, those records shall be maintained for a period of seven (7) years after receipt of final payment under the contract.

25.0 MATERIAL SAFETY DATA SHEET: If any item(s) on an order(s) resulting from this award(s) is a hazardous chemical, as defined under 29CFR 1910.1200, the Contractor shall provide one (1) copy of a Material Safety Data Sheet for each item with the shipped container(s) and one (1) copy with the invoice(s).

26.0 ADVERTISING AND NEWS RELEASES: Reference to or use of the County, any of its departments, officials, or employees, for commercial promotion is prohibited. News releases pertaining to this procurement shall not be made without prior approval of the County. Release of broadcast e-mails pertaining to this procurement shall not be made without prior written authorization of the County.

27.0 HOLD HARMLESS: The Contractor will indemnify, pay the cost of defense including attorney’s fees, and save harmless the County and all of its officers, agents and employees from all suits, actions, or claims of any character brought for or on account of any injuries or damages received by any persons or property resulting from the operations of the contractor, or of any of its contractors, in prosecuting work under this agreement.

28.0 FOREIGN CORPORATION: A foreign corporation (any corporation other than a Wisconsin corporation) which becomes a party to this contract is required to conform to all the requirements of Chapter 180, Wis. Stats., relating to a foreign corporation and must possess a certificate of authority from the Wisconsin Department of Financial Institutions, unless the corporation is transacting business in interstate commerce or is otherwise exempt from the requirement of obtaining a certificate of authority. Any foreign corporation which desires to apply for a certificate of authority should contact the Department of Financial Institutions, Division of Corporation, P. O. Box 7846, Madison, WI 53707-7846; telephone (608) 261-7577.

29.0 FORCE MAJEURE: Neither party shall be in default by reason of any failure in performance of this contract in accordance with reasonable control and without fault or negligence on their part. Such causes may include, but are not restricted to, acts of nature or the public enemy, acts of the government in either its sovereign or contractual capacity, fires, floods, epidemics, quarantine restrictions, strikes, freight embargoes and unusually severe weather, but in every case the failure to perform such must be beyond the reasonable control and without the fault or negligence of the party.


ATTACHMENT G=COST PROPOSAL Company Name=

Submit original plus one copy (Submit in separate sealed envelope within proposal package) Each bidder should complete the cost worksheets included in this attachment. Bidders are required to utilize the cost worksheets provided for their response to be considered. However, if supplemental information is deemed necessary, include this information within the response. A finalization of software and services is expected as a part of the final contract negotiation or through a Best and Final Offer process specified in this RFP.

Portage County Sheriff's Office Final Cost Chart

Sec Description of Totals $$ Worksheet

G-1 Total Hardware Cost

G-2 Total System Software Cost

G-3 Total CAD Cost

G-4 Total RMS Cost

G-5 Total Mobile Software Cost

G-6 Total Field Reporting Software Cost

G-7 Total Jail Management Software Cost

G-8.1 Total Implementation Cost

G-8.2 Training & Travel

G-9 5 Year Maintenance & Warranty Cost

G-10 Interface Costs

Other Cost Not Indicated but must be included (please

detail on a sheet included with proposal)

Total Cost of Portage County Proposal=

Make sure the cost listed above equals the total of all cost listed in Final Cost Chart

City of Stevens Point Police/Fire, Village of Plover Police/Fire, and UW Stevens Point Police Final Cost Chart

Sec Description of Totals $$ Worksheet

G-1 Additional Hardware Cost

G-4 Additional RMS Cost

G-5 Additional Mobile Software Cost

G-6 Additional Field (FBR) Costs

G-8.1 Additional Implementation Cost

G-8.2 Additional Training & Travel Costs

G-9 Additional 5 Year Maintenance & Warranty Cost

G-10 Additional Interface Costs

Other Cost Not Indicated but must be included (please

detail on a sheet included with proposal)

Total Cost for Additional Agencies=

Make sure the cost listed above equals the total of all cost listed in Final Cost Chart


G-1. Specific Hardware Costs The Proposer will supply any propriety or specific hardware not contained within the Portage county network environment to ensure that the applications software provided by the Proposer will perform at its optimum capabilities for the County. Please note the County reserves the right to purchase from sources other than the Proposer. Use this form to list all hardware that the Proposer will include in the system. Make as many copies of this table or add rows as needed.

Portage County Sheriff's Office

Quantity Make/Model/Part Component Description Unit Price

(If Applicable) Total Price Hardware

Total Hardware Cost=

City of Stevens Point Police/Fire, Village of Plover Police, and UW Stevens Point Police

Quantity Make/Model/Part Component Description Unit Price

(If Applicable) Total Price Hardware

Additional Cost For Agencies Adding Hardware=


G-2. System Software Costs Use this form to list all system software being proposed for Portage County. If additional system software is needed to include City of Stevens Point, Village of Plover, and UW Stevens Point please indicate that on the second chart. All software included in this form must be detailed individually. Make as many copies or add rows as needed to this form.


Quantity Release Level/Description Component Description Unit Price

(If Applicable) Total Price Software

Total System Software Cost For County=


Quantity Release Level/Description Component Description Unit Price

(If Applicable) Total Price Software

Additional Cost for System Software for Agencies=


G-3. Computer Aided Dispatch (CAD) APPLICATION SOFTWARE PACKAGE (CAD) Use this form to identify costs associated with each module in the proposed solution. In addition, the total cost for each individual application must be listed.

CAD Application Component Package Name

Number of

Licenses Package Cost Modifications Costs Total Cost

Total CAD Cost for

County=


G-4. Record Management Software (RMS) APPLICATION SOFTWARE PACKAGE (RMS) Use this form to identify costs associated with each module in the proposed solution. Please indicate the cost for just Portage County to have the correct amount of software. Then also include the cost to add City of Stevens Point Police, Village of Plover Police, and UW Stevens Point Police Units


RMS Application Component Package Name Number of

Licenses

Package Cost

Modifications Costs Total Cost

Total RMS Cost for County=

City of Stevens Point Police, Village of Plover Police, and UW Stevens Point Police

RMS Application Component Package Name Number of

Licenses

Package Cost


Additional Cost for Agencies Adding RMS=


G-5. Mobile Date Computer System (MDC) Applications MOBILE APPLICATION SOFTWARE Use this form to identify costs associated with each module in the proposed solution. Please indicate the cost for just Portage County to have the correct amount of software. Then also include the cost to add City of Stevens Point/Fire, Village of Plover, and UW Stevens Point Police Units


Mobile Data Computer System (MDC) Application Component Package Name

Number of Licenses

Package Cost


Total Mobile Cost for County=


Mobile Data Computer System (MDC) Application Component Package Name

Number of Licenses

Package Cost


Additional Cost for Agencies Adding Mobile=


G-6. Field Based Reporting (FBR) Applications

FIELD (FBR) APPLICATION SOFTWARE Use this form to identify costs associated with each module in the proposed solution. Please indicate the cost for just Portage County to have the correct amount of software. Then also include the cost to add City of Stevens Point, Village of Plover, and UW Stevens Point Police Units


Field Based Reporting (FBR) Application Component Package Name

Number of Licenses

Package Cost


Total Field Cost for County=

City of Stevens Point Police, Village of Plover Police, and UW Stevens Point Police

Field Based Reporting (FBR) Application Component Package Name

Number of Licenses

Package Cost


Additional Cost for Agencies Adding Mobile=


G-7. Jail Management System (JMS) APPLICATION SOFTWARE PACKAGE (Jail JMS) Use this form to identify costs associated with each module in the proposed solution. Please indicate the cost for just Portage County to have the correct amount of software.


JMS Application Component Package Name

Number of

Licenses Package

Cost Modifications

Costs Total Cost

Total JMS Cost for County=


G-8.1 IMPLEMENTATION AND CONVERSION COSTS IMPLEMENTATION AND CONVERSION Use this chart to identify costs associated with implementing the new software and transferring any data from the County Legacy System to the Proposer’s system. Please indicate the cost for just Portage County to implement and transfer. Then in the separate chart indicate what it will be for the other agencies to do the same. (IMPORTANT) On separate page also indicate all the things included with the various areas of implementation and conversion (Code Setup, State Database Connect, Onsite services, etc.)


Item Cost Cost of Project Management for The Implementation and Conversion

Installation of Hardware

Installation of Software

Data Migration from Legacy Systems

System Integration (include with current software within the county)

Other Installation Cost (Third Party, Breakout cost for each, etc)

Travel and Per Diem for Implementation

Other:(describe)

Total Implementation Cost for County=


Item Cost Cost of Project Management for The Implementation and Conversion

Installation of Hardware

Installation of Software

Data Migration from Legacy Systems

System Integration (include with current software within their agencies)

Other Installation Cost (Third Party, Breakout cost for each, etc)

Travel and Per Diem for Implementation

Other:(describe)

Additional Implementation Cost for Agencies=


G-8.2 TRAINING ADMINSTRATIVE AND FRONTLINE STAFF COSTS TRAINING Use this chart to identify costs associated with training both Administrative (Train the Trainer) and frontline staff in the new systems. Please indicate the cost for just Portage County staff training. Then in the separate chart indicate what it will be for the other agencies to do the same. In addition, please provide a description of what is included in the various items or services. Estimate the amount of time spent by various County Staff on each type of training Product. Then include a total dollar amount for all of the products and services you plan to provide for Training as part of your proposal. The County realizes this amount may not be equal to all individual costs listed. Please explain any variance. This number will be expected to be included in the total cost chart at the beginning of this section of the proposal.


Item or Description of Service Est. HRs Cost Product or

Service Description of What is Included Project Manager for Training Staff

Complete Administrative Training (Train the Trainer) (Examples: Manuals, Webinar, Onsite, etc.)

End User Training at Implementation (Examples: Manuals, Webinar, Onsite, etc.)

Ongoing Administrative and End User Training (Examples: Manuals, Webinar, Onsite, etc.)

Post Go-Live Refresher Training (Examples: Manuals, Webinar, Onsite, etc.)

Travel and Per Diem Proposer Staff

Other: (Define)

Other: (Define)

Total Training Cost for County=


Item or Description of Service Est. HRs Cost Product or

Service Description of What is Included Project Manager for Training Staff

Complete Administrative Training (Train the Trainer) (Examples: Manuals, Webinar, Onsite, etc.)

End User Training at Implementation (Examples: Manuals, Webinar, Onsite, etc.)

Ongoing Administrative and End User Training (Examples: Manuals, Webinar, Onsite, etc.)

Post Go-Live Refresher Training (Examples: Manuals, Webinar, Onsite, etc.)

Travel and Per Diem Proposer Staff

Other: (Define)

Other: (Define)

Additional Cost for Training Agencies=


G-9. MAINTENANCE (CONTINUED LICENSING) AND WARRANTY COSTS Use this form to provide a summary of all recurring costs for the proposed System for the next 5 years of ownership after implementation acceptance. A one-year warranty included in the pricing following final solution acceptance is desirable and will have an impact on the final solution provider selection. If the first year of maintenance and/or warranty is included in previous pricing, please indicate that in Year 1 column provided (INCL). If a warranty or maintenance is not provided past a certain year just indicate an N/A in that box.


Item Recurring Yr 1 Recurring Yr 2 Recurring Yr 3 Recurring Yr 4 Recurring Yr 5

Hardware Maintenance

System Software Maintenance

CAD Software Maintenance

RMS Software Maintenance

Mobile Software Maintenance

Field Reporting Software Main

Jail-JMS Software Maintenance

Warranty on Hardware

Warranty on Software

Other Recurring Costs

Total Annual Recurring Costs

Total 5 Year Recurring Cost for The County

City of Stevens Point Police/Fire, Village of Plover Police/Fire, and UW Stevens Point Police

Item Recurring Yr 1 Recurring Yr 2 Recurring Yr 3 Recurring Yr 4 Recurring Yr 5

Hardware Maintenance

RMS Software Maintenance

Mobile Software Maintenance

Warranty on Hardware

Warranty on Software

Other Recurring Costs

Total Annual Recurring Costs

Additional 5 Year Recurring Cost for Agencies Added


G-10. INTERFACE COST

APPLICATION SOFTWARE PACKAGE (Interfaces and Other Potential Applications) Use this form to identify costs associated with interfacing your module with other programs used by Portage County noted in E-9.2 of this document. Please indicate the costs, if any, associated with interfacing with the various software. In the area of other potential applications, you may list any packages or software not previous indicated that the Proposer feels Portage County may benefit from.

Interface Costs

Name of Interface Description of Need/How Total Cost

Total Interface Costs=

G-11 OTHER APPLICATION COSTS DO NOT INCLUDE THESE COSTS IN ANY TOTALS QUOTED TO PORTAGE COUNTY FOR

APPLICATIONS REQUESTED THESE COST OUR FOR-INFORMATION PURPOSES ONLY

Other Potential Applications the Proposer may present to the County

Other Application Component Package Name

Number of Licenses

Package Cost


Request for Proposal On Replacement Public Safety Software ...

Documents

Transcript of Request for Proposal On Replacement Public Safety Software ...