Rocket Vetting

How It Works | Rocket Vetting

How Rocket Vetting Works

Rocket Vetting uses one secure tokenized pipeline to support both private and collaborative program integrity workflows. RVP provides pull-based LADMF deceased reconciliation. RVC uses the same secure process to support customer-triggered and network-triggered alerts for deceased, duplicate, and anomalous records. RVC-CM can be added when customers want structured review, research, and resolution workflow.

RVP — Private
Pull-based LADMF deceased reconciliation using tokenized data.
RVC — Collaborative
Pull + push alerts across participating programs and jurisdictions.
RVC-CM — Case Management
Optional workflow for alert review, research, and resolution.

1. Tokenize Inside Your Environment

Rocket Vetting tokenizes sensitive roster data inside your controlled environment, within your firewall, before any data is securely transmitted. Only the fields required for matching are used.

2. Secure Transmission

Tokenized data is securely transmitted using key-based SFTP with host verification and encrypted transport. Each customer operates within isolated inbound and outbound paths.

3. Processing Through One Secure Pipeline

RVP and RVC use the same secure processing pipeline. This allows customers to begin with private vetting and expand into collaborative detection without changing their integration model.

4. RVP — Private Pull-Based Alerts

RVP generates pull-based alerts using SSA LADMF data. Alerts are created when customer roster data is submitted, scheduled, or processed through the pipeline.

  • Deceased match alerts
  • Recurring reconciliation alerts
  • Customer-triggered processing only

5. RVC — Pull and Push Collaborative Alerts

RVC extends the same pipeline to support collaborative detection. Alerts are generated both from customer activity and from changes made by other participating organizations.

  • Deceased match alerts
  • Duplicate participation alerts
  • Cross-program and cross-jurisdiction alerts
  • Address anomaly alerts

RVC supports both customer-triggered (pull) and network-triggered (push) alerts, allowing new potential matches to be identified even when a customer has not recently submitted new data.

6. Optional Case Management (RVC-CM)

RVC alerts can be routed into Rocket Vetting Case Management when customers want structured workflows for review, research tracking, and resolution.

  • Alert-to-case conversion
  • Research notes and tracking
  • Case status and resolution workflow

7. Customer-Controlled Outcomes

Rocket Vetting is a detection platform. It identifies potential matches but does not determine eligibility, remove participants, suspend benefits, or direct program action.

Customers control all review, validation, investigation, and resolution decisions.

System Requirements

Rocket Vetting integrates with existing environments. No database migration is required. Your launch pad runs inside your environment and streams only the fields needed for vetting.

Supported Databases
  • MySQL
  • Oracle
  • Microsoft SQL Server
  • PostgreSQL
Launch Pad Requirements
  • Windows or Linux host
  • Outbound SFTP access
  • SSH key authentication
  • Rocket Vetting launch/reentry tooling
No inbound firewall changes required.

Output / Alert Data

Each alert or match record may include:

  • Roster identifier
  • Supplied data (echo)
  • Deceased match indicators (when applicable)
    • LADMF-derived data
    • Cemetery (when available)
    • Obituary (when available)
  • Alert type (deceased, duplicate, anomaly)
  • Verification method
  • Match quality indicator
  • Supporting indicators (when available)