The chart below represents the general implementation and onboarding steps for FINDER. Your Account Executive assists you through the process and ensures your agency is able to successfully implement and launch FINDER.

NOTE: The “Server” referenced above is a Windows-based computer system that has the ability to read/access RMS/CAD/JMS/etc., as well as connect/upload to FINDERweb and meets the requirements listed below. The process above is representative; an individual agency’s process may vary based on their requirements and connections. Steps in the process may be completed congruently.

A Windows-based computer system that has the ability to read/access RMS/CAD/JMS/etc., as well as connect/upload to FINDERweb, is required. The FINDER connection is a .net console application scheduled to run using the Windows task scheduler. It requires 100MB of RAM, 2GB of disk space and consumes about 5% of CPU while its running. Due to the minimal resource requirements, a dedicated Windows machine is not required.

Minimal hardware specifications:

• Server class computer (at least 4 cores)
• 12 GB RAM
• 200 GB hard disk or higher- RAID  1 or 5 recommended (>300 GB for larger agencies)
• Network interface (2 interfaces may be needed at some locations)
• Current Microsoft Windows OS
• Microsoft  .Net 3.5 & 4.7.2 (Free download)
• Anti-Virus/system security software with a subscription
• All the latest security patches and server packs installed
• Any required third-party ODBC compliant drivers for RMS connectivity

NOTE: This is the recommended connection method; legacy on-prem solutions will no longer be supported after May 2024.

Designed as a web application, agency users can access FINDER Query Only on most current systems. FINDER recommends using a current and updated web browser on a current and updated computer system with a high-speed internet connection

Activation Requirements:

• As part of the set-up and activation, the agency will need to provide FINDER with the agency’s “outbound IP address” so it can be permissioned within the FINDER network. This also limits user access to devices within that IP.

FINDER provides an interface to allow other agencies to view your information while keeping your production data safely under your agency’s control.

FINDER is designated to meet the technological directives established by the federal government for sharing law enforcement data, including LEXS-SR, CJIS, and FIPS 140-2. FINDER also uses AWS GovCloud. This ensures a path to future expansion.

FINDER operates on the AWS GovCloud platform. Please visit the AWS GovCloud FAQs to find answers to commonly raised questions. .

FINDER Software Solutions also offers custom Extract, Transform, Load (ETL) work via FINDER Integrate. This process allows any agency to transfer their legacy data from one database to another. This process is perfect for those agencies that need to change RMS systems and want to transfer their legacy data.

We also specialize in developing Application Program Interfaces (APIs) to enhance agencies’ ability to utilize other custom software systems such as mapping, analytical programs, and external law enforcement data sources.

At FINDER, we are always working to improve our platform for our customers. If you have an idea or product request, you may submit it using the form HERE, and our engineering team will review it. If you happen to identify a bug, you can also use this form to submit it. Please note due to development cycles and the wide base of customers, not all requests will be implemented, however, our team does read all requests.

FINDER product release notes can be accessed on the Product Release Notes page.

FINDER moved to a cloud-based architecture to better support the growth and development of the product and services for our customers, which is not possible with a distributed on-prem solution.

The new architecture still meets the strict security requirements for the law enforcement user base.

Some benefits include:

1. Easier to implement for the agency
2. Lower entry and ongoing cost with no expensive server requirements
3. Faster updates from FINDER without the need for manual upgrades
4. Enhanced security
5. Lower system latency
6. Access to the latest updates and tools from FINDER
7. Lower on-going agency operational cost

NOTE: Please be aware that opting for an on-premises installation is not recommended and may lead to extra servicing expenses and fluctuations in system performance and security. On-prem and legacy FINDER installations will no longer be supported and updated after May 2024. Contact FINDER Support to schedule a conversion to the Cloud-based platform.

Minimal hardware specifications for a FINDER server are:

• Server class computer (at least 4 cores)
• 12 GB RAM
• 200 GB hard disk or higher- RAID  1 or 5 recommended (>300 GB for larger agencies)
• Network interface (2 interfaces may be needed at some locations)
• Microsoft Windows 2016 Standard or higher (Per processor licensing mode)
• Access to a Microsoft SQL 2014 SP3 or higher. We can also install SQL EXPRESS (Free download) on the FINDER server
• Microsoft  .Net 3.5 & 4.7.2 (Free download)
• IIS installed and running (Part of Windows server)
• Anti-Virus/system security software with a subscription
• All the latest security patches and server packs installed
• Any required third-party ODBC-compliant drivers for RMS connectivity

If your agency wishes to install FINDER on a Virtual Server:

• There is no additional setup or configuration if your virtual server meets the minimum server specifications described above and is CJIS compliant.
• A shared server is permitted as long as the system is secure and the FINDER application functions reliably.

NOTE: FINDER can run on most systems, but it will run only as well as the agency system on which it’s placed.

The Clearview AI API to FINDER requires the FINDER engineering team to add your unique Clearview API key to the system. Follow the steps below to obtain this key and then provide to your FINDER onboarding consultant.

Steps to obtain the Clearview API Key

• First, the API keys permission set must be enabled within the Clearview admin section.
• From the home screen, click the drop-down next to the user’s name, then select API Keys.
• From there, the user will select the highlighted Create API Key.
• In the pop-up box under Create a new API key, type in the name of the agency, for example, Anytown Police Dept FINDER.
• Once this is complete, the user will see a QR code along with their alphanumeric code. This code must be sent over to FINDER to allow for integration.

FINDER provides agencies with three different ways to load bulletins into the FINDER system.

FINDER Bulletin Upload Module

To perform this task, you must be assigned the Bulletins module.

• From the Dashboard, click the Bulletin Upload icon.
• To assign today’s date to this Bulletin (default), proceed to the next step. To assign a different date to this Bulletin, proceed to the Bulletin’s Date field at the top of the page. Next, enter a date in mmddyyyy format or click the calendar icon to select a date from the popup calendar.
• Click the dropdown arrow icon to the right of the Bulletin’s Category field. Next, select a category from the drop-down list.
• Click Choose File or Browse (button names may vary based on the web browser you’re using).
• Navigate to the directory on your PC or network where the Bulletin is located, then double-click on that file to select it. The file name displays to the right of the Choose File or Browse button.
• Click Upload. The new Bulletin displays in the left column.

Secure File Transfer Protocol (SFTP)

FINDER offers a SFTP folder to agencies to load bulletins and other files. Please contact the FINDER Support Team HERE to use the SFTP process and for access instructions. The Secure File Transfer Protocol (SFTP) server we use to upload the bulletins into FINDER, is FIPS 140-2 complaint and secured end to end. You can read more about FINDER security on our FAQ page.

Email Upload

Create an email forwarding rule within the department workflow to automatically send bulletins to bulletins@findersoftware.com.View instructions on how to create an Outlook forwarding rule HERE.

Please note, the email upload option should NOT be used for CJIS-protected information.

FINDER provides agencies with two different ways to load LPR Hotlist into the FINDER system.

Secure File Transfer Protocol (SFTP)

FINDER offers a SFTP folder to agencies to load hotlist and other files. Please contact the FINDER Support Team HERE to use the SFTP process and for access instructions. The Secure File Transfer Protocol (SFTP) server we use to upload the bulletins into FINDER, is FIPS 140-2 complaint and secured end to end. You can read more about FINDER security on our FAQ page.

Email Upload

Create an email forwarding rule within the department workflow to automatically send bulletins to lpr@findersoftware.com. View instructions on how to create an Outlook forwarding rule HERE.

Please note, the email upload option should NOT be used for CJIS-protected information.