LexisNexis Technical Setup Requirements — Accurint Crime Analysis / AVCC / Lumen (Client, 08-2022)

LexisNexis Risk Solutions Technical Setup Requirements for Accurint Crime Analysis, the Accurint Virtual Crime Center, and Lumen (Client version, dated 08-2022). The document is the engineering playbook behind PSDEX contribution. It instructs the agency to stand up a computing environment inside its own network where LexisNexis builds a custom interface named the PSDex Data Client. That client runs an automated ETL process that extracts read-only data from the agency Records Management System and Computer-Aided Dispatch, reformats it, and uploads it to LexisNexis servers over SFTP. The setup runs on a daily schedule, with a service account whose password is set never to expire so the job does not break, and LexisNexis is given VPN access into the agency network to build and maintain it.

Two details stand out. First, the document states a data preference: limited copies and filtered views are not preferred, and raw access to the unfiltered RMS is preferred. The default configuration pulls the whole records system rather than a curated subset. Second, the document publishes the exact network destinations an agency firewall must allow, including PSTRANSFER, PSIMPORTER, and API.PSDEX at lexisnexisrisk.com, plus communitycrimemap.com and the Lumen environment in AWS GovCloud. Those endpoints are a fingerprint: a network that talks to them is running the contribution pipeline.

This is a generic vendor document rather than an agency-specific contract, so it does not by itself establish that any particular department contributes. What it establishes is the mechanism. It is the technical counterpart to the AVCC XML Addendum: the addendum is the legal permission to contribute, and this is the plumbing that carries the data out. It also confirms that Community Crime Map is fed by the same Data Client, which supports treating CCM presence as a contribution indicator.