Skip to main content

​
Overview

Wherever your data lives, ProDex can ingest it. Direct integrations cover ERPs, MES, WMS, databases, warehouses, cloud platforms, shop floor systems, BI tools, and more — but the platform isn’t limited to systems with built-in connectors. If data only exists in a spreadsheet, a PDF report, or even a screenshot of a dashboard, Dexter can still read it, profile it, and incorporate it into your factory model. Your data stays in the systems your organization already owns and governs. ProDex reads from those systems under credentials your team controls; nothing is copied into ProDex unless you explicitly build a pipeline that materializes it.

​
Supported Connections

The systems below have direct integrations. Setup is handled by your ProDex team today — see How Connections Are Set Up below. If a system you need isn’t on this list, see Alternative Ingestion Paths at the bottom of the page. ERP
MES
WMS
BI
Cloud Platforms
Data Warehouses and Lakehouses
Databases
IoT and Shop Floor
CRM
Salesforce (for demand signals)
Messaging
Files
Don’t see your system? Contact us — we can add it.

​
Alternative Ingestion Paths

Not every useful data source has a direct integration — but that doesn’t mean it’s out of reach. If a system isn’t on the supported list above, or if the data you need only exists as a report or dashboard view rather than a queryable table, you have options:
  • Spreadsheet or CSV export — download from the source system and attach it to a conversation. Dexter profiles the columns and asks clarifying questions before using the data.
  • PDF reports and documents — upload them directly. Dexter extracts values, tables, and context from the document.
  • Screenshots of dashboards — if the data lives in a BI tool view that’s cumbersome to export, a screenshot works. Dexter reads the chart, extracts the values, and can use them in analysis or model configuration.
  • Any document format — PowerPoint decks, Word documents, images. See File Attachments for the full list of supported types and how Dexter handles each.
This means onboarding doesn’t have to wait on a direct integration being built. You can start working with data from a new system the same day — Dexter will tell you what it needs to make sense of what you uploaded.

​
How Connections Are Set Up

ProDex operates a managed-integration model today: your ProDex team provisions connections during onboarding and adds new ones on request. This covers credential setup, network configuration, schema mapping for your key tables, and any transformation logic required to normalize source data into the shapes Dexter expects. To request a new connection, contact your ProDex representative with:
  • The system you want to connect (name and version if relevant)
  • The kind of data you want ProDex to access (tables, schemas, or specific data domains)
  • Any security or compliance constraints your IT team requires (read-only, VPN, IP allowlist, etc.)

​
How Dexter Uses Connected Data

Once a connection exists, Dexter can:
  • Query live — ask questions against source data directly (“What’s our average cycle time for Product X across the last 30 days?”) without waiting for an export
  • Profile and document — inspect schemas, value distributions, and data quality, then document what it finds before you build on top
  • Build pipelines on top — use connected sources as nodes in a pipeline, deriving simulation parameters from live data with full traceability
  • Re-run on schedule — scheduled jobs can re-run pipelines against fresh warehouse data automatically
Every query Dexter runs is visible in the conversation, so you can audit exactly what data was read and what was done with it.

​
Security and Access

Connections use credentials provided by your team. ProDex accesses data at the permission level you grant — typically read-only on specific schemas or tables. All data transfer is encrypted in transit. Connection credentials are stored in ProDex’s managed secrets store and are scoped to your factory. If your organization requires specific network controls — IP allowlisting, private links, VPN, or proxy routing — your ProDex team configures those during setup.