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.
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.
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.
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.
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.
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.
| Source | Path | What the app does with it | Status |
|---|---|---|---|
| Esri ArcGIS REST feature service (state polygons) | CAI | Service Connector pulls US state polygons into Bronze; spatial join and state stamp. | LIVE |
| US Census TIGERweb (county polygons) | CAI | County polygons into Bronze; county stamped in Silver. | LIVE |
| NWS watches and warnings (Esri Living Atlas) | CAI | Real-time stream: polled every minute, new events land in Bronze within seconds, matched to venues. | STREAM |
| Spatial file: GeoJSON (converted shapefile / KML) | CDI | Flat-file ingest into Bronze spatial_files. | LIVE (file) |
| Esri basemaps (streets, imagery, topographic) | Map | Visual context only; not ingested. | LIVE (map) |
| Crowdsourced coverage readings | CAI / CDI | Signal-quality readings into Bronze; the data-quality rules run on this feed. | SAMPLE |
| Venue master, SQL Server / Azure SQL | CDI + CDC | Sixteen venues with coordinates into Bronze. | SAMPLE |
| Microsoft Dynamics 365 CRM | CDI | Account, opportunity stage, monthly revenue into Gold. | SAMPLE |
| ServiceNow field work orders | CAI / CDI | Open work orders per venue into Gold and the Where to Build report. | SAMPLE |
| Esri geodatabase (ArcSDE) | CDI | Read natively at the database layer (Oracle SDE or SQL Server). | ARCHITECTURE |
| Large national datasets (buildings, rivers, fibre, ~500 GB) | CDI | Selective ingest and warehouse pushdown. | ARCHITECTURE |
| CSV with geocoding | CDI | Flat file plus IDMC geocoding to coordinates. | ARCHITECTURE |
| Excel | CDI | Spreadsheet ingest. | ARCHITECTURE |
| Salesforce | CDI / CAI | Accounts, opportunities, cases into the CRM context. | ARCHITECTURE |
| Points and areas of interest as run parameters | CAI | Orchestration parameters to scale from one venue to many. | ARCHITECTURE |
| Boomi (existing in-house integration) | n/a | Overlaps IDMC; a migration topic for the account team. | ARCHITECTURE |
| Connector in the real estate | Path | What it is / typical use |
|---|---|---|
| Oracle Database + Oracle Database Ingestion (CDC) | CDI | Core operational DBs (billing/CCB, ERP, Maximo) — bulk + change-data-capture |
| Oracle GIS — Esri SDE geodatabase (schema SDE_*) | CDI | Esri spatial data read natively at its Oracle SDE layer — the "backing geodatabase" path |
| Microsoft SQL Server (2012 / 2016 / 2019, Azure SQL) | CDI | Warehouses, app DBs, SCADA / Ignition historians |
| Snowflake Cloud Data Warehouse V2 | CDI | Cloud EDW — raw / curated / marts (the Zayo CDW) |
| Microsoft Dynamics 365 · Salesforce | CDI & CAI | CRM accounts, opportunities, cases |
| Amazon S3 · FileIO · Flat / CSV files | CDI | Object storage, extracts, reference sets, geocode inputs |
| Advanced SFTP V2 · SharePoint Online | CDI | Partner file exchange; documents & survey exports |
| Web Services (SOAP / WSConsumer) · REST V2 | CDI | App / service calls inside mappings & taskflows |
| Service Connector (generic REST) | CAI | Real-time API orchestration — how Esri & Census are wired here (112 in the reference org) |
| Maximo · Oracle Field Service · ServiceNow · WorkDay | CAI | App-integration Service Connectors — dispatch, work orders, HR |
| Email · File (process) events | CAI | Notifications, event-driven file handling, middleware |