← dataprostudio.ca · Version française
DataProStudio · Technical white paperThis paper describes the method behind every DataProStudio engagement, and the platform (DPS8020) that grew out of it. Figures cited are indicative ranges from comparable engagements — not guaranteed results, and validated case by case for your operation.
Every SMB manufacturer or distributor runs on a planned process: the routing in the ERP, the pick path in the WMS, the SOP binder. And every operations lead knows the real process deviates from it — a returns loop that never shows up on the org chart, an approval that sits in an inbox for two days, an inspection step duplicated because two systems don’t talk to each other.
The gap between the planned process and the real one is where lead time, margin, and customer complaints hide. Large enterprises close this gap with consulting engagements that run for months. SMBs can’t justify that math — the analysis costs more than the problem, and by the time the report is bound, the plant has already changed.
Your systems already record what actually happens. Every ERP transaction, WMS scan, and shipping confirmation is a time-stamped fact: this order, this activity, this moment. Process mining reconstructs the real process from those records — not from interviews, not from a whiteboard session, from data you already have.
The minimum viable input is an event log with three fields:
| Field | Example |
|---|---|
| Case ID | Order #A-2214 |
| Activity | QC inspection completed |
| Timestamp | 2026-07-18 09:14:02 |
Most SMB ERPs and WMS platforms can export this with no new instrumentation — this is usually a data-pull, not a project.
Most software vendors start at step 4. This method starts by finding out where automation is actually worth it.
For an SMB supplying larger customers, the pressure comes from two directions at once: operational (on-time delivery, scrap, returns) and evidentiary (customer audits, IATF 16949 traceability for automotive suppliers, ISO 9001 quality records). These are usually tracked in different tools by different people.
The event log that reveals your bottleneck is the same record that proves what happened, when, and on whose watch. A process-mining exercise that maps your real flow can generate that evidence at close to zero marginal cost — it’s a by-product of the analysis, not a separate project.
Operational data — cycle times, customer volumes, margins — is competitively sensitive. Engagements are scoped so your data stays under your control: analysis is typically performed on extracts you provide, and the DPS8020 platform that grew out of this method is hosted exclusively with Canadian and European infrastructure providers, or run entirely on-premise / air-gapped for organizations that need production data to never leave the building. See the Platform section of dataprostudio.ca for deployment options.
The real process is already written down in your event data. This method reads it, prioritizes it, and turns it into two things an SMB manufacturer or distributor actually needs: shorter, more predictable lead times, and evidence that’s ready before the customer or the auditor asks for it.
Contact: +1 604 673 9292 · dataprostudio.ca · DataProStudio Inc., Vancouver, BC, Canada · See also: Engagement methodology (MET-001)