pAud AI Lite · free
Build your warehouse failure pattern library.
Your systems already recorded every late dispatch, missed cut-off and overtime shift. Send us the exports. In 3 days, you see which failures repeat, how often, and where each one starts.
Start your library Explore a live sample
Not ready to upload? Open pAud on public, simulated benchmark data. No sign-up.
Where it hurts is rarely where it started.
A missed cut-off shows up at dispatch. It often started hours earlier, in inbound or replenishment. Your WMS, TMS and ERP each see one piece of it.
pAud joins your exports into one timeline per order, end to end from supplier to customer. So you see where each failure started, not just where it landed.
- ERP / OMSPurchase orders, sales orders, promise dates
- Supplier / ASNExpected deliveries, arrival times
- YMSTrailer arrivals, dock door times
- WMSReceipts, putaway, replenishment, picks, packs
- WCS / MHEConveyor, sorter and robot events
- Labour / LMSShifts, headcount, overtime
- TMSLoads, carrier cut-offs, departures
Send what you have. Two systems is enough to start. Every system you add makes the library more complete.
One entry from a library
Example · sample data
Pattern
Replenishment released after pick start
- Seen
- 11 times in 6 months
- Median disruption
- 180 orders per occurrence
- Started in
- Inbound, supplier ASN late
- Moved with it
- Receiving backlog, then replenishment released after pick start
Explore a live sample.
pAud running on public benchmark logs. Open one and click through the same dashboards your library gets. No sign-up, nothing to upload.
-
Public benchmark · simulated data
Container Logistics
Port container flow: bookings, trucks, forklifts and vessels.
What you'll see Where containers wait before they depart, which steps break the expected order, and the cost of delay on assumptions you can read.
- Events
- 35,413
- Objects
- 13,910
- Object types
- 7
Open live dashboard: Container Logistics, opens in a new tab
Source: Knopp & Graves, Zenodo 10.5281/zenodo.8428084 · CC BY 4.0
-
Public benchmark · simulated data
Order Management
Order to delivery: orders, items, packages and customers. Employees pseudonymised.
What you'll see Out-of-stock items and the slower orders associated with them, failed deliveries, and where packing waits.
- Events
- 21,008
- Orders
- 2,000
- Object types
- 6
Open live dashboard: Order Management, opens in a new tab
Source: RWTH PADS, Zenodo 18373906 · CC BY 4.0
The samples are read-only: the pack is fixed and nothing re-runs. On your own trial you edit the pack (your rules, cut-offs and KPIs) and re-run the analysis.
Your library in 3 days. Your data gone in 14.
-
Upload
Exports only, to encrypted storage in the EU. Nothing to install or connect.
-
Within 3 days
Your library is ready. Or we tell you exactly what to fix in the files.
-
10 days of access
Explore it. Add your rules, shift patterns, cut-offs and KPIs.
-
Within 14 days
Your data and everything built from it are deleted. No backups.
Free. No billing. Delete your data any time from your confirmation email.
What to send
Send 3 to 12 months of history. More history, more patterns.
- Raw tables or logs from the systems above.
- CSV, Excel (.xlsx), XES or OCEL 2.0. Zip several files into one upload.
- All files from the same period, so each order can be followed across systems.
- Up to 95 MB.
- Pseudonymise personal data first. No special-category data (health, religion, union membership).
We check the files and email you what we found, what we fixed and what is missing.
What's in your library
- For each failure pattern: how often it hit, how many orders it touched, where it started, and what moved with it.
- Where orders wait, and for how long, from supplier to DC to carrier.
Start your library
Your details, an email code, your files. Done.
Already sent us a file? See it on your status page, or upload corrected files.
- Your details
- Email code
- Your file
- Done
Your details
Confirm your email
We'll send a code to . Quick human check first.
Enter the code
We sent a code to .
You already have a submission
- Submission id
- State
We take one submission per email address. Its dates, any report and the link to delete your data are on your status page.
Upload a corrected export
Submission is waiting for corrected files.
- The new file replaces the old one, which we delete when the upload starts.
- The 14-day clock restarts, and we reply within 3 days.
- We keep only your table and column names, to check the new file.
Your file
We found your earlier submission
, which has no file yet. This upload completes it.
File received
- Submission id
- Received
- —
- Your library by
- —
- Deleted by
- —
We reply by the date in your confirmation email with our report. If your data is ready, the link to your failure pattern library follows once it is built.
Your data is deleted no later than 14 days after your latest upload.
Your confirmation email has these dates and a link to delete your data. You can also follow progress on your status page.