Global Search Overview
This Request for Proposal (RFP) is being issued for the acquisition and implementation of a Global Search Solution.
The need to search information on people, places and things has always been a vital part of the functions of TPS police officers. Searching such information currently involves several search functions and is restricted to data repositories. The TPS has the need to get the required information from a single common interface with the end goal of searching and retrieving all relevant content from data repositories, both internal and external, semi-structured and unstructured, document and content management systems and social media through the Global Search Solution.
Phased Approach
The TPS Global Search Solution Proof of Concept Project will be conducted in several phases:
- Phase One – Acquisition and Implementation of the Global Search Solution Tools
Phase One must be completed by March 31, 2018.
- Phase Two – Conduct a Proof of Concept on the Global Search Solution with a few selected TPS databases.
After evaluation of the Proof of Concept, if deemed successful, the Global Search solution will be implemented throughout the Toronto Police Service Divisions and Operational Units. As funds become available to the TPS, additional repositories, both internal and external, and functionality will be added to the project. Therefore the Global Search Solution must be expandable and allow content to be added as it becomes available, and it must have the capability of being leveraged for other purposes such as intranet search, internet search and full replacement of the search based legacy systems.
It is the intent of the TPS to select a partner who is committed to assisting the TPS with the design and implementation of a Global Search Solution that will serve the needs of its users for the next 5 years.
The successful proponent will have a major presence in the Global Search Solution market place, with an existing and preferably proven law enforcement client base, and an ongoing commitment to supporting and enhancing its technologies in line with industry directions.
Term of the Contract
The term of this contract is as follows:
- Initial Period: Phase One – start on or about February 21, 2018 and end March 31, 2018
- Option to Extend: Phase Two – one additional year at the sole discretion of the TPS.
Mandatory Requirements
Search Requirements
- The Global Search solution must allow for both analytical and transactional searching of current and legacy TPS repositories of different formats (specifically DB2, Oracle and Informix for Phase 1 & 2 of the project), directories, files, and document/ content management systems as well as external data sources (e.g. CPIC, MTO) through a single user interface.
- The Global Search user interface must be presented in a browser-based format and be compliant with the TPS standards as defined in section 3.1.
- The search user interface must provide suggestions for alternative spelling or wording, based on a dictionary, configurable within the solution, as well as query suggestions.
- The user must be able to execute basic searches with a single text box. For example, searching for “red car” across multiple data repositories.
- The Global Search solution must provide the capability to perform advanced searches. For example, searching for “Jane Smith” with “Blue” eyes and “Brown” hair with a “Spider” tattoo in a specific repository.
- The Global Search solution must provide the capability to search large text fields by text or keyword. For example, searching for “John Doe” in an incident synopsis or a note.
- The user must be able to perform partial searches with the use of wildcards on fields that accommodate for partial searches (i.e. on names, dates, vehicle license plate numbers, locations and addresses, telephone numbers, document identification numbers, descriptions, etc.). For example, searching for vehicle with license plate number “AB??123”.
- The Global Search solution must allow for searching multiple entities such as person, business name, street address, intersection, common place, vehicle, telephone, property, document, offence, accident, tickets, etc. For example searching for “John Smith” who lives at “123 Main Street” and committed the offence of “Break and Enter” during the period of “June 1, 2017 to August 15, 2017”.
- The user must be able to provide a reason for performing a search. This is specifically required for high sensitive data and external systems. This must be configurable/customized within the solution to make the reason either optional or mandatory for each data set as per TPS security procedures.
- The search results must be listed in order of relevance (i.e. weight, score, rank).
- The search results returned must be listed with the source of the information and summarized information (e.g. when returning persons, the surname, given names and date of birth are provided).
- The user must have the ability to export the search results to other file medium such as MS Excel.
- The Global Search solution must respect and adhere to the security constraints of the source systems. For instance, data that has been marked as restricted or private must only be returned if the user is authorized to view the data, and deleted data must not be returned.
- When a record is deleted or restricted, or when some of its details have been deleted or changed, the global search must update the indices in a timely manner.
- The user must have the capability to select a search result and view its full details. For example, if a vehicle collision report is selected, the full report is presented to the user.
- When searches are done on systems that contain pictures, images, maps, audio or video, the search must return these items.
Security Requirements
- The Global Search solution must provide multiple levels of security based on roles or positions and accordingly permit user access to the corresponding functionality.
- The Global Search solution must allow for restricting access to the search to a specific user or group of users, and be managed by Active Directory.
- The Global Search solution must maintain a transaction log of users, requests, search results and data viewed and paged for auditing purposes.
- The Global Search solution must be capable of reporting on the following transaction details:
- Date/time stamp of queries
- Device from where the query is initiated
- User details (i.e. user name, badge number)
- Search criteria, including if system suggestions were made to user
- Results including the navigation done through the result set, printing of results, dismissing, saving, exporting of results, etc.
- The audit log reports must be exportable to other file medium such as MS Excel.
- The Global Search solution must provide the capability to integrate the audit logs with Bunyan (which is a solution that processes and allows for the viewing of various application logs, and is the central repository of logging messages from TPS applications).
Administrative Tools Requirements
- The Global Search solution must allow for the configuration and management of user and group roles and permissions.
- The Global Search solution must allow for maintaining a dictionary of alternative spellings or wordings.
Technical Requirements
- The Global Search solution must integrate with TPS Active Directory to achieve single sign-on.
- The Global Search solution must be hosted completely on TPS infrastructure.
- The Global Search solution must have the ability to integrate with Hortonworks (TPS Big Data Platform).
- The Global Search solution must have the ability to integrate with Identity Insight (TPS Master Naming Platform).
- The Global Search solution must have the ability to integrate with Infosphere Stream (TPS Data In Motion Platform).
- The Global Search solution must have the ability to integrate with Cognos (TPS Reporting Platform).
- The Global Search solution must be available for use on mobile workstations, standard workstations and smart devices, and provide similar functionality for all devices.
- The Global Search solution must be able to support a minimum of 1,000 concurrent users.
- Simple searches should return the results asynchronously and between 5 to 10 seconds.
- The Global Search solution must be scalable to accommodate TPS growing data requirements, which is estimated to 25 to 50 percent per year.
- The Global Search solution must provide the ability to leverage Search API to incorporate search/results into other solutions.
- The Global Search solution must provide thorough logging with error and warning messages that include correlating identification numbers to enable troubleshooting from the technical staff where needed.
- The retention period of the audit logs must be configurable, and set as up to five (5) years.
- The Global Search solution must provide an out of the box indexing feature.
- The Global Search solution must provide technical support tools for troubleshooting, system configuration, and search optimization.
- The Global Search solution must integrate with the standard TPS backup tool, TSM, for online backups.
- The Global Search solution must support a high availability load balanced multi-data center deployment.
- The Global Search solution must provide the ability to automatic fail over to another center in the event of a disaster recovery event.
- The Global Search solution must conform to the Accessibility for Ontarians with Disabilities Act (AODA) requirements.
- The Global Search solution must be able to integrate with an enterprise standard document management system, so that documents and contents are loaded into the search solution and made searchable.
General Requirements
- The proponent must provide all required hardware and software required for the Global Search Solution Proof of Concept (i.e. Phase 1 & 2 of the solution as described in section 2.2).
- The proponent must provide the professional services necessary to support the POC such as training, project management, development/ integration, installation, etc.
- The proponent must have practical experience with search technologies for a minimum of five (5) years.
- The proponent must have delivered a similar search solution within the last year to an organization of the same size, complexity and environment as TPS.
- The proponent must be able to provide a Global Search solution that meets the use cases outlined in Appendix L.
- Phase 1 of the solution as described in section 2.2 must be delivered and implemented by March 31st, 2018.
All in accordance with the requirements stated in the RFP document to be downloaded.
