Michele Esri — Spatial Coverage Intelligence

For every venue, rank Verizon, AT&T and T-Mobile by measured coverage quality, identify the winning carrier and the sales or build opportunity. Sources flow through Informatica IDMC into a governed Bronze → Silver → Gold warehouse on BigQuery, where the spatial analysis runs, and out to Esri maps and reports.

Flow How the data moves — sources to decision
1 · Sources
Your systems
CRM, site DB, work orders, crowdsource + Esri / Census / spatial files
CDICAI
2 · Informatica IDMC
Ingest & govern
CDI moves data at rest (batch, CDC) · CAI calls live APIs · data quality · catalog and lineage
3 · Bronze
Raw, as-is
Every source landed exactly as it arrived, tagged by origin
4 · Silver
Governed + spatial
DQ rules cleanse & audit; BigQuery-GIS point-in-polygon join to venue & state
5 · Gold
The decision
85th-percentile score per carrier · winning carrier · opportunity flag · CRM context
6 · Serve
Consume anywhere
Esri query layers · Grafana BI · this app · PDF reports
Report Executive summary, how it works, and definitions

Executive summary

A telecom company sells connectivity to large venues: stadiums, arenas, campuses. Before it spends money it wants two answers for every venue: where can we win a sale today, and where should we build or fix coverage. This application answers both, on a map, from data it can trace back to the source.

How it works, in plain words

Picture three boxes. The first box (Bronze) is where every piece of information is dropped exactly as it arrived: map shapes from Esri, county lines from the US Census, thousands of phone-signal readings that people collected on their phones, the list of venues, the customer records, and the open repair tickets. Nothing is changed in this box, so we can always prove what came in and when.

The second box (Silver) is where the data is cleaned. Bad readings (no location, impossible signal values, unknown carrier) are removed, and every removal is written down with the reason. Each good reading is then placed inside the right venue, state and county using the map shapes. This is the step a specialist used to do by hand; here it is a rule that runs the same way every time.

The third box (Gold) holds the answer. For each venue and each carrier (Verizon, AT&T, T-Mobile) we compute one coverage score, decide who wins, and flag the opportunity: Greenfield (everyone is weak, so build here), Competitive (no clear winner, so sell hard), or Dominated (one carrier owns it). Next to the score sit the account owner, the sales stage, the monthly revenue and the open work orders, so the map answers the business question, not just the engineering one.

Why Informatica IDMC

The boxes are filled by Informatica Intelligent Data Management Cloud. It moves data in two ways: CDI (Cloud Data Integration) for data that sits still in databases, files and business applications, moved on a schedule or as it changes; and CAI (Cloud Application Integration) for data you must ask for right now through an API, such as the live Esri map service. The same platform keeps the catalog, the lineage and the quality rules, so every number on the map can be traced to its source and every removed row is explained.

Why BigQuery and Esri

The three boxes live in Google BigQuery, which can do the map mathematics (which point falls inside which shape) inside the warehouse at any scale, with no separate GIS server. Esri provides the authoritative shapes and basemaps, and reads the Gold table directly as a map layer, so the people who already work in ArcGIS keep their tools.

What you are looking at in this demo

Two sources are pulled live from the internet on every run: Esri state polygons and Census county polygons. One source streams continuously: National Weather Service watches and warnings from the Esri Living Atlas, polled every minute and landed in Bronze within seconds, then matched to venues on the Gold map. The full pipeline also runs on a nightly schedule and records every run. A spatial file is ingested from disk. The venue list, the crowdsourced readings, the CRM accounts and the work orders are realistic sample data that stand in for the client's private systems, using the same connector patterns a production deployment would use. The tab In this demo vs. not lists exactly which is which, so nothing here overstates what is real.


Live Pipeline results — Bronze → Silver → Gold
Every source lands in Bronze exactly as it arrived: nothing is cleaned, and each row is tagged by origin. The ledger below lists one row per source with its connector, its integration path (CDI moves data at rest, CAI calls a live API) and how it was ingested. LIVE means the data was pulled from the real service on this run; SAMPLE means realistic sample data standing in for a private enterprise system. Click any source to inspect its raw rows.

Raw rows


Sources Source catalog: what is live, what is sample, what is architecture
Source catalog the sources discussed, sorted by what this demo actually does with them
Rule of thumb: CDI moves data at rest (databases, warehouses, files, object stores, bulk SaaS; batch and CDC). CAI calls and orchestrates in real time (REST APIs such as Esri and Census, application actions, events). LIVE pulled from the real service each run   SAMPLE realistic sample data, real connector pattern   ARCHITECTURE supported, not built here. The full sorted list with explanations is in the Report tab In this demo vs. not.
A · Sources discussed, sorted
SourcePathWhat the app does with itStatus
Esri ArcGIS REST feature service (state polygons)CAIService Connector pulls US state polygons into Bronze; spatial join and state stamp.LIVE
US Census TIGERweb (county polygons)CAICounty polygons into Bronze; county stamped in Silver.LIVE
NWS watches and warnings (Esri Living Atlas)CAIReal-time stream: polled every minute, new events land in Bronze within seconds, matched to venues.STREAM
Spatial file: GeoJSON (converted shapefile / KML)CDIFlat-file ingest into Bronze spatial_files.LIVE (file)
Esri basemaps (streets, imagery, topographic)MapVisual context only; not ingested.LIVE (map)
Crowdsourced coverage readingsCAI / CDISignal-quality readings into Bronze; the data-quality rules run on this feed.SAMPLE
Venue master, SQL Server / Azure SQLCDI + CDCSixteen venues with coordinates into Bronze.SAMPLE
Microsoft Dynamics 365 CRMCDIAccount, opportunity stage, monthly revenue into Gold.SAMPLE
ServiceNow field work ordersCAI / CDIOpen work orders per venue into Gold and the Where to Build report.SAMPLE
Esri geodatabase (ArcSDE)CDIRead natively at the database layer (Oracle SDE or SQL Server).ARCHITECTURE
Large national datasets (buildings, rivers, fibre, ~500 GB)CDISelective ingest and warehouse pushdown.ARCHITECTURE
CSV with geocodingCDIFlat file plus IDMC geocoding to coordinates.ARCHITECTURE
ExcelCDISpreadsheet ingest.ARCHITECTURE
SalesforceCDI / CAIAccounts, opportunities, cases into the CRM context.ARCHITECTURE
Points and areas of interest as run parametersCAIOrchestration parameters to scale from one venue to many.ARCHITECTURE
Boomi (existing in-house integration)n/aOverlaps IDMC; a migration topic for the account team.ARCHITECTURE
B · Reference: connectors in a comparable production IDMC estate
Taken from an export of a production Informatica IDMC organisation at a fibre and utility enterprise: about 230 CDI endpoints and 120 CAI connections across four Secure Agents. It shows what "all sources, one governed pipeline" looks like at scale, including the Esri geodatabase read natively at its Oracle SDE layer.
Connector in the real estatePathWhat it is / typical use
Oracle Database + Oracle Database Ingestion (CDC)CDICore operational DBs (billing/CCB, ERP, Maximo) — bulk + change-data-capture
Oracle GIS — Esri SDE geodatabase (schema SDE_*)CDIEsri spatial data read natively at its Oracle SDE layer — the "backing geodatabase" path
Microsoft SQL Server (2012 / 2016 / 2019, Azure SQL)CDIWarehouses, app DBs, SCADA / Ignition historians
Snowflake Cloud Data Warehouse V2CDICloud EDW — raw / curated / marts (the Zayo CDW)
Microsoft Dynamics 365 · SalesforceCDI & CAICRM accounts, opportunities, cases
Amazon S3 · FileIO · Flat / CSV filesCDIObject storage, extracts, reference sets, geocode inputs
Advanced SFTP V2 · SharePoint OnlineCDIPartner file exchange; documents & survey exports
Web Services (SOAP / WSConsumer) · REST V2CDIApp / service calls inside mappings & taskflows
Service Connector (generic REST)CAIReal-time API orchestration — how Esri & Census are wired here (112 in the reference org)
Maximo · Oracle Field Service · ServiceNow · WorkDayCAIApp-integration Service Connectors — dispatch, work orders, HR
Email · File (process) eventsCAINotifications, event-driven file handling, middleware
Frequency and orchestration in production: operational systems load on a scheduled batch cadence, with CDC where the source supports it; Esri and Census polygons are pulled on demand through CAI Service Connectors; one run can cover one venue or many. The pipeline is idempotent, and the Secure Agent runs inside the customer network, which is where catalog, lineage and access control are enforced.