Meru AI

Empirical research brief

Entity resolution across FMCSA motor carriers, EPA chemical releases, and municipal property rolls

Logistics fleets, industrial facilities, drinking-water basins, wireless towers, and commercial parcels are tracked under separate federal, state, and local keys. Separating corporate operator lineage from spatial parcel identity prevents costly false merges.

For
Supply chain, underwriting, environmental & real estate ops
Primary feeds
FMCSA MCMIS/L&I, EPA TRI/RCRA/UCMR5, FCC Part 101, Assessor/DOB
Prepared by
Meru AI
Updated
November 17, 2026

One industrial facility, corridor, or fleet appears under six separate agency identities

Supply-chain risk teams, environmental engineers, commercial underwriters, and real estate diligence analysts inspect physical operations that exist at real street parcels and infrastructure corridors — yet every federal, state, and municipal regulator keys the exact same property or operator around its own statutory filing system:

  • Interstate motor carriers (Carrier Ledger): USDOT FMCSA tracks interstate fleets by `USDOT Number` in MCMIS census and crash tables and by `MC/MX Docket Number` in Licensing and Insurance (`L&I`) authority and policy-revocation histories.
  • Industrial chemical releases & hazardous waste (Plume Ledger): U.S. EPA links plant sites through `FRS Registry ID`, annual Toxics Release Inventory (`TRI Facility ID`) chemical disclosures, and ECHO Resource Conservation and Recovery Act (`RCRA Handler ID`) compliance and enforcement records.
  • Drinking-water systems & groundwater basins (Subsurface Ledger): EPA UCMR 5 PFAS analytical testing keys utilities to 9-character Public Water System IDs (`PWSID`), while California SAFER water-system risk assessments, DWR SGMA groundwater sustainability basins, and CNRA Well Completion Reports index hydrological boundaries and well depths.
  • Fixed wireless backhaul & towers (Backhaul Atlas): The FCC separates licensee `FRN` entities, Part 101 Fixed Microwave `Call Signs` (point-to-point path links), and physical Antenna Structure Registration (`ASR`) tower numbers.
  • Parcels, permits & municipal right-of-way (Parcel Ledger, Safer Places): County assessors and municipal building departments key land and safety filings to Assessor Parcel Numbers (`APN` or NYC `BBL`), deed/LLC chains, and permit numbers (`DOB NOW`, `HPD`, `OATH/ECB`), while local 311 systems log street and utility maintenance along right-of-way segments.

Merging these registries on raw street addresses or company trade names breaks immediately in industrial parks, port terminals, rural highway routes, and single-purpose real estate holding structures.

Linking fleets, plants, water basins, towers, and parcels without false merges

Across Meru AI's civic and infrastructure ecosystem, we separate corporate operator identity (who holds the license, permit, or operating authority) from spatial site identity (which tax parcel, tower structure, or hydrological basin hosts the physical activity).

Entity and spatial resolution rules across six infrastructure, supply-chain, and environmental registries.
Registry & Meru platformPrimary statutory keysCorporate & spatial bridge signalsHigh-risk false merge to block
Interstate motor carriers (Carrier Ledger)FMCSA `USDOT Number`, `MC/MX Docket`, and L&I insurance policy filings.Link MCMIS census snapshots to L&I active coverage and revocation timelines via USDOT-to-docket crosswalks; distinguish physical terminal addresses from registered process-agent mail drops.Never merge two distinct USDOT numbers solely because both list the same commercial compliance service or truck-stop P.O. box; flag shared physical terminal, officer, and insurer overlaps for review instead.
Industrial facilities (Plume Ledger)EPA `TRI Facility ID`, `FRS Registry ID`, `RCRA Handler ID`, and reported parent company.Anchor TRI chemical releases and RCRA enforcement histories through EPA FRS facility bridges; track annual parent-company restatements across M&A spin-offs.Multi-tenant industrial lots frequently host two separate RCRA generators in adjacent buildings (`Bldg A` vs `Bldg B`); parcel centroid overlap alone must not collapse distinct handler IDs.
Water systems & PFAS basins (Subsurface Ledger)EPA `PWSID`, CA Water Board `SAFER` system ID, DWR `SGMA` basin code, and CNRA well report ID.Crosswalk state water-system boundaries to EPA UCMR 5 analytical sample rows by `PWSID` (`CAxxxxxxx`); intersect well completion depths against official SGMA basin polygons.Wholesale water agencies and retail municipal utilities have distinct `PWSID`s serving overlapping cities; keep wholesale versus retail system roles explicit so PFAS sample denominators are not double-counted.
Microwave backhaul & towers (Backhaul Atlas)FCC `FRN`, ULS Part 101 `Call Sign` + path number, and `ASR` antenna structure ID.Separate licensee ownership (`FRN`) from physical tower registration (`ASR`), since utility, rail, and telecom licensees lease dish mounts on third-party tower structures.Do not equate tower owner with microwave path operator; link transmit/receive path endpoints to ASR structures by explicit registration ID first and coordinate tolerance second.
Property & building safety (Parcel Ledger)County `APN` / NYC `BBL`, recorder document ID, `DOB NOW` / `HPD` building ID, and `OATH/ECB` summons.Resolve municipal BIN/permit filings onto canonical parcel polygons (`MapPLUTO` / county assessor); group single-asset property LLCs only through verified deed, mortgage, or HPD head-officer registrations.Avoid fuzzy name grouping on generic LLC strings (`123 Main Holdings LLC` across different counties or unrelated managers); require shared registered principals or recorded instrument links.
Municipal 311 right-of-way (Safer Places)DataSF 311 service request ID and historical Los Angeles MyLA311 request ID (2020 through July 2025).Snap street, sidewalk, streetlight, and water-waste requests to jurisdiction street segments while keeping exact agency category and date-window boundaries visible.Never compare raw 311 request counts across cities as an objective defect rate without stating agency scope differences and reporting cutoffs (such as LA's historical archive window).

Handling carrier reincarnations, corporate parent rollups, and single-asset LLCs

Static company directories struggle whenever legal entities are inexpensive to form and dissolve. Three structural patterns recur across logistics, environmental, and property records:

  1. Operating authority revocations and fleet succession: In Carrier Ledger, a motor carrier's MCMIS census snapshot shows active power units and drivers today, whereas FMCSA Licensing & Insurance history shows involuntary revocations, insurance cancellations, and authority reinstatements over time. Evaluating carrier safety or freight-broker onboarding requires reading crash history alongside authority continuity rather than checking a single `ACTIVE` flag at dispatch time.
  2. Facility continuity across corporate divestitures: On Plume Ledger, a chemical plant or metal finisher keeps the same EPA `TRI Facility ID` and `RCRA Handler ID` across decades even as private equity sponsors or industrial conglomerates buy, rename, or spin off the division. Preserving a facility-level spine with dated parent-company intervals prevents historical releases or RCRA corrective actions from disappearing when a parent name changes.
  3. Single-purpose property LLCs: Commercial and multifamily properties on Parcel Ledger almost always sit inside property-specific LLCs (`410 Oak Street Owner LLC`). Portfolio-level building-safety and repeat-sale margin analysis relies on statutory disclosure filings (such as NYC HPD multiple-dwelling registrations, tax-bill mailing care-of entities, and recorded deed/loan signatories) with explicit evidence tiers rather than speculative name similarity.

Where supply-chain and environmental data pipelines quietly fail

Rural facilities, wells, or motor carriers disappear from regional risk summaries.

Records carrying highway-milepost descriptions, township-range coordinates, or P.O. box mailing addresses are dropped when street geocoding fails.

What to do: Keep every valid filing in state and county totals, and label spatial precision tiers openly (rooftop/parcel, street segment, basin/ZIP centroid, or unmapped) following our Reconciling Living Government Releases standard.

Vendor compliance screening clears a brokered carrier whose operating authority lapsed last week.

Onboarding checks a cached quarterly census table without reconciling daily FMCSA L&I insurance and revocation filings.

What to do: Separate census fleet size from live L&I authority and insurance effective dates, and route lapsed or newly re-keyed carriers to human exception review.

Environmental diligence sums EPA TRI pounds across years without separating on-site air/water releases from off-site recycling or treatment transfers.

Total waste-managed columns and fugitive/stack release columns are combined indiscriminately.

What to do: Preserve EPA TRI statutory disposal and release categories side by side so analysts distinguish direct local emissions from managed off-site transfers.

Embedding registry verification into onboarding, underwriting, and exception workflows

In distribution, logistics brokerage, specialty insurance underwriting, and real estate operations, analysts still burn hours copying USDOT numbers, parcel IDs, permit statuses, and EPA facility records across browser tabs into onboarding packets or credit memos.

Through Meru AI's workflow automation and AI consulting practice, we connect verified external registries directly to internal ERP, TMS, underwriting, and document-review pipelines:

  • Automated packet assembly with cited source rows: When a new carrier, supplier plant, or commercial property enters onboarding, deterministic lookups pull exact authority, crash, permit, or environmental compliance records and attach release dates directly to the review file.
  • Three-way reconciliation and exception routing: Just as our distribution document-processing example reconciles purchase orders, warehouse receipts, and vendor invoices before payment approval, operational compliance workflows pass clean matches automatically and route revoked authority, parcel mismatches, or open enforcement flags to a named reviewer.
  • Versioned custody over time: Using the principles in Reconciling Living Government Releases, Cross-Agency Entity Resolution, and Enterprise AI Implementation, teams keep an auditable trail of what the public record showed on the exact date an underwriting or procurement decision was approved.

Companion engineering and domain briefs

Implementation & system integration

Connecting carrier, vendor, environmental, or property checks into operations?

Share the onboarding, underwriting, or compliance workflow your team runs by hand today. Meru will review the source registries and design a governed workflow with clear exception review.

Do not include passwords, protected health information, or confidential client records in an initial note.

This brief summarizes cross-registry corporate and spatial entity resolution practices across Carrier Ledger, Plume Ledger, Subsurface Ledger, Backhaul Atlas, Parcel Ledger, Safer Places, and Meru AI workflow engagements.