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 can read from agency data sources such as RMS/CAD/JMS/etc., as well as connect and upload reports to the FINDERcloud hosted solution, is required. The FINDER uploader is a .NET console application that will be scheduled to run using the Windows task scheduler. The utility requires about 100MB of RAM, 2GB of disk space, and typically consumes about 5% of the CPU while its running. Due to the minimal resource requirements, a dedicated Windows machine is not required.

Minimal computer specifications:

• Windows based computer (at least 2 cores)
• 2 GB RAM
• 100 GB available hard disk space or more
• Current Microsoft Windows OS
• Regular OS/file backups
• 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 April 2024. All current on-prem customers will be required to move to the cloud environment by August 30, 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 operates on the AWS GovCloud platform. Please visit the AWS GovCloud FAQs to find answers to commonly raised questions. .

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 moved to a cloud-based web 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

There are three primary milestones for the FINDERweb transition:

1. Agency IP address added to FINDERweb access list,
2. FINDERweb parser setup on-prem with bulk reimport of data to FINDERweb,
3. Agency user accounts transitioned to FINDERweb.

After providing the agency’s IP addresses, we’ll add them to the FINDERweb access list. Then the first stage is for us to setup a FINDERweb data parser on one of your computer systems that can read from the RMS and connect to FINDERweb – this could be the FINDER server, another server, or any Windows based computer for the most part- whichever you prefer. This updated data parser will parse agency reports up to FINDERweb by SFTP so outbound port 22 should be permitted, at least to FINDERweb. The timeline for transitioning to FINDERweb varies with each agency due to the amount of agency data being imported to FINDERweb.

The second stage will be to complete the transition process and deactivate the old on-prem FINDER components.

For continuity of data access, switching users to begin using FINDERweb would take place at the end of the transition process—after the primary data load has been completed.

What work, if any, would be involved on our end to move to the cloud?

>Mainly to connect our engineers to the agency server(s) so they can setup the new FINDERweb parser and deactivate the old FINDER components. If network access to FINDERweb is by default blocked, then the firewall/security team will need to configure an exception for it.

What changes, if any, would the users see?

>The main noticeable element would be the URL change. Select local features such as FINDER Gun Crimes reports, FINDER Link Charts, or FINDER Agency Tree groups may need to be recreated on FINDERweb. New features and updates to FINDER would be available faster.

Do we need any special systems or network changes to move to the cloud?

>Unlikely—agency users would need to be able to reach FINDER Cloud. The utility computer with the new FINDERweb parser would need to be able to see FINDER Cloud and SFTP to it, as well as read reports from the agency RMS.

Would data be stored in the cloud, or as you mention below would this application be 100% cloud resident and we would continue to store our own data as we do today?

>The FINDER user interface would be in the cloud and agency data would be moved to the cloud with regular nightly updates with the new FINDERweb on-prem data parser.

Are there any financial upcharges or contractual changes needed to move to FINDERweb?

>No additional charges to transition to FINDERweb, no contract changes needed.

How long does the migration process take to complete?

>The timeline for transitioning to FINDERweb varies with each agency due to the amount of agency data being imported to FINDERweb, which can be from a day to a couple of weeks. For continuity of data access, switching users to begin using FINDERweb would take place at the end of the transition process- after the primary data load has been completed.

FINDER does not require the agency to have an API for their RMS or CAD systems to make the data available within the FINDER platform. As part of the implementation process, FINDER will install a data parser on a local agency PC, which will read the reports and then make the copy available within the FINDER system. During implementation, you will need to provide a data fragment so FINDER can configure the parser, and you will then need to complete a data validation to ensure the data is returning properly. Your FINDER Account Executive will assist you with this during the implementation process.

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.

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.

The CLEAR from Thomson Reuters connection to FINDER is standard within FINDER Investigate. However, a user must have an active account with FINDER and CLEAR. Additionally, the agency must have the CLEAR sharing API activated in order to search CLEAR from Thomson Reuters records from within FINDER Investigate.

Set-up will occur during your implementation process, or you may contact FINDER Support or CLEAR from Thomson Reuters Support to learn more and begin using this connection.

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.

The Evidence IQ connection to FINDER is configured per agency and will require the agency credentials.

Set-up will occur during your implementation process or you may contact FINDER Support to request adding Evidence IQ to your FINDER account.

The IRIS connection to FINDER is standard in FINDER, however a user must have a FINDER and IRIS account and be activated by IRIS in order for the data sharing to function.

Set-up will occur during your implementation process or you may contact FINDER Support or IRIS Support to beginning using this connection.

The Lucidus Tech search is is standard in FINDER for users with version 7.0 or greater. By having a FINDER account and accessing a Lucidus Tech search, the user agrees to the posted terms and use conditions avaliable at https://findersoftware.com/terms-privacy/.

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.

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

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.