Overview
The Data page, in the left sidebar, is where operational data enters ProDex and where the things Dexter builds from it live. It opens on an overview of everything the factory holds. From there, the Files, Pipelines and Datasets tabs hold the detail. Most of the work happens in conversation with Dexter: you upload or connect data, Dexter analyzes it with you, and the results land back on this page.The Overview
The overview is the Data page’s landing view. It has three parts:- Collection cards. Files, Pipelines, Datasets and Integrations, each with a count. Click a card to open that tab. The Integrations card instead opens the list of data integrations connected for your organization.
- Recent activity. A timeline of uploads, reports and pipelines, filterable by All, Files or Pipelines.
- Actions. Upload files opens a file picker, and you can also drop files anywhere on the page. Create with Dexter is described below.
The Tabs at a Glance
Integrations (ERP, MES, databases and similar systems) don’t have a tab. The ProDex team sets them up for your whole organization, not per factory, and they appear on the Integrations card. To get one connected, ask your ProDex representative. See Data Sources.
Uploads belong to the factory they were uploaded to. When someone shares a factory, the recipient gets their own copy, and uploaded files don’t travel with a share or an export.
Create with Dexter
Create with Dexter opens a dialog for asking Dexter to build something from your data. Under What should Dexter do?, describe the result you want. Then pick the inputs: existing uploads under Files (or Upload a new file) and any connected Integrations. Create sends the request, with the selected files attached, to Dexter in chat.Analyze Your New Data?
When an upload you started on the Data page finishes, an Analyze your new data? prompt appears in the corner of the screen. Analyze it asks Dexter for a full exploratory analysis of the new files. Not now dismisses the prompt. If Dexter is busy, the request is added to the chat, ready to send. The prompt appears in every response mode, but how deep Dexter goes depends on the mode. Turbo doesn’t run an exploratory analysis. See Response modes.Exploratory Analysis
Exploratory Analysis is the workflow Dexter follows to understand a source before building on it. Dexter profiles the data, raises quality problems and codes it can’t interpret, and confirms its reading with you. What it produces depends on what you asked for: an answer, parameters for a model, a report, or a pipeline for data that arrives on a recurring schedule.A Typical Journey
1
Upload
Drop a quarterly MES cycle-time export on the Data page. It lands in Files, in the Uploaded files folder.
2
Analyze
Click Analyze it on the Analyze your new data? prompt, or ask Dexter in chat. Dexter profiles the file and asks about codes, gaps and units before it extracts anything.
3
Get the result you asked for
Depending on your request, that might be an answer in chat, a report in the Reports folder, fitted service times for a simulation model, or a module to explore the data in.
4
Make it repeatable
If a new export arrives every quarter, ask Dexter to turn the preparation into a pipeline, so the next file gets the same treatment without redoing the analysis.
Terms That Live Elsewhere
Where to Go Next
- Data Sources: uploads, integrations, and how sources are documented
- Exploratory Analysis: how Dexter turns a raw file into trusted numbers
- Pipelines: repeatable data preparation
- Datasets: versioned data tables you can browse, correct and compare
- Custom modules: interactive pages for exploring your data, such as the Data insights template
- Reports: downloadable deliverables built from your data