FINDER® Parsers

Twenty years of writing code for systems other people built.

A FINDER parser is a small application that runs inside your network, reads your source system on a schedule you control, and moves records into FINDER. We have built them for the RMS, CAD, JMS, pawn, and scrap systems agencies actually run, and the library grows every time a member agency brings a new one.

What it actually is

A console application, not a connector into your database.

Each parser is written for a specific source system. It installs on any Windows machine that stays powered on, including a laptop, positioned on your network where it can reach both your source database and FINDER. Typically that is behind your firewall.

It needs two off the shelf components: the driver for your source system database and the free Microsoft SQL Server driver. Most database drivers are free or close to it.

> type lightweight Windows console app
> location your network, behind your firewall
> schedule Windows Task Scheduler, your interval
> components source driver + free MSSQL driver
What we read

If a driver or an API exists, the data can come out.

These are the database platforms member agencies run today. The list is not a limit.

DatabaseMicrosoft SQL Server
DatabaseOracle
DatabaseIBM DB2
DatabaseProgress
SourceStructured databases
SourceUnstructured text files
SourceThird party APIs
SystemsRMS, CAD, JMS, pawn, scrap

60 plus parsers in the library, growing as member agencies adopt new systems

Transformation

Why a report from your RMS lines up against one from a different vendor.

Extracting the data is the easy part. Making it comparable is the work.

Code mapping

Hair color, eye color, race, sex and similar coded fields are mapped to a standard code such as FCIC or NCIC, so two agencies describing the same thing use the same value.

Standardization

Fields are formatted consistently. Directions abbreviate, names take a common last, first, middle form, and addresses are geocoded.

Cleansing

Mandatory fields must be present, values must match their data type, dates must fall in a valid range, and formatted fields must match their expected pattern.

Confidential and expunged

Data flagged confidential in the source is never read. If a record is flagged after it has already loaded, it is deleted from the destination.

What ETL cannot fix

Cleansing is not the same as accuracy.

A parser can enforce structure. It cannot correct a misspelled name or fill in a field the report writer left blank, because that information does not exist to recover. Fixing it means going back to the report.

When your agency corrects a report in your own system, the parser picks up the change on its next run and syncs it into FINDER. The source of truth stays with you.

> enforced structure, types, ranges, formats
> not fixed spelling, missing information
> corrections made in your system, synced to FINDER
> truth stays in your records
Keeping it running

Monitored on our side, updated before your vendor breaks it.

Status and error monitoring

Parsers report status and errors back to our monitoring system. When an error comes in, we contact your agency to resolve it rather than waiting for someone to notice.

Alerts to your IT contact

Parsers can be configured to send notifications directly to your own IT staff as well, so nobody is waiting on a phone call.

Vendor upgrade coordination

Parsers need updating when your RMS vendor ships a new version. We coordinate with your IT staff ahead of the upgrade so we know it is coming.

On site testing after

Once your system is updated, we update the parser and test on site to confirm every record type is still flowing correctly.

Get started

Tell us what you are running.

Send us your source systems and we will tell you what is already built and what is not. If you already have an account and need technical help, use the support form instead.

Supporting law enforcement for over 20 years.

© 2026 FINDER® Software Solutions LLC