The Main Layout
ProDex has a collapsible sidebar on the left, a main content area in the center, and a right-side chat panel for Dexter. The sidebar is your primary navigation — it contains links to every section of the platform. If you haven’t yet, What Is ProDex? covers what each module does. This page focuses on finding things in the UI.Where to Start
Most users start in one of two places:- Modeler — build your first simulation model from scratch or via Dexter
- Pipelines — upload MES, ERP, or spreadsheet data and have Dexter derive simulation parameters from it
Sidebar
Click any item in the sidebar to navigate. The active section is highlighted. If you collapse the sidebar with the chevron at the top, icons remain visible so you can still navigate without labels. The Modeler is the default landing page when you open ProDex. The sidebar is divided into sections based on what you’re trying to do: Data- Pipelines — reusable data transformations that turn uploaded files (MES exports, ERP dumps, PDFs) into simulation parameters, planning inputs, or reports
- Insights — free-form dashboards for exploratory data analysis, factory-scoped
- Modeler — build and edit simulation models
- Results — simulation run results, KPIs, and charts
- Experiments — compare what-if scenarios across multiple Snapshots of a model
- Monte Carlo — replicate a single Snapshot many times for confidence intervals and percentile distributions
- Layout — 2D floor plan of your facility
- Planning — production planning and APS optimization
- Scheduling — job-level scheduling
- BOMs — bill of materials and product structures
- Configurator — define configurable product variants and option classes
- Team Management — manage users and permissions (tenant admins only)
- Settings — user preferences
Key Concepts
Factory
Your factory is the top-level workspace. Everything in ProDex lives inside your factory — one factory per workspace. If you need to work across multiple facilities or scenarios, each one is a separate workspace.Model
A model is a simulation model within your factory. It has a name, description, and a version history of frozen copies called Snapshots. You can have multiple models in a factory — for example, one for your current operations and one for a proposed future state.Schedule
A schedule layers operational timing onto a model — when materials enter the system, when actions fire, and how long the simulation runs. Schedules travel with a Snapshot when you capture one, so each comparison row in an Experiment carries its own schedule context.Snapshot
A Snapshot is an immutable, frozen copy of a model’s configuration — including its schedule, entities, constants, and lookup tables at the moment of capture. They’re what Experiments compare, and every Run is traceable back to one.Saving a model is not the same as capturing a Snapshot. Saves update the live model in place; Snapshots are separate, explicit captures you take when you want to preserve a version for comparison.

