Odyssey ERP Automated Non-Conformance Logs
Every night, WebRun opens Odyssey ERP, pulls every non-conformance recorded that day, logs each one in Google Sheets with the job, defect type, root cause, and disposition, and rolls up a running count by cause so recurring problems stand out.
How do I keep one running log of casting non-conformances by cause?
WebRun keeps a running non-conformance log so you don't have to. Every night, it opens Odyssey ERP, pulls every non-conformance recorded that day with its job, defect type, root cause, and disposition, adds a row to a Google Sheets log, and updates a rolling 30-day count by cause so recurring problems stand out early.
- Every non-conformance is logged the same night it's recorded instead of batched at month end
- A rolling 30-day rollup by cause surfaces recurring defects early
- Job, defect type, and disposition stay in one running log instead of scattered paperwork
Built for foundries · die casters · foundry quality managers · casting quality engineers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
www.blinfo.comin a real browser with your saved login - no setup, no API keys. -
1
Odyssey ERP - pull today's non-conformance records
blinfo.com
WebRun opens Odyssey ERP to pull today's non-conformance records. - Open Odyssey ERP and pull every non-conformance record logged today
- Capture the job, part, defect type, root cause, and disposition for each
- Note whether each one was scrapped, reworked, or dispositioned use as is
Done when Every non-conformance recorded today is pulled with its job, cause, and disposition.
-
2
Google Sheets - log each one and roll up by cause
google.com
WebRun opens Google Sheets to log each one and roll up by cause. - Add a row per non-conformance to the running log with job, defect type, cause, and disposition
- Update the rolling count of non-conformances by cause for the trailing 30-day window
- Highlight any cause that has jumped compared to last week
Done when Today's non-conformances are logged and the 30-day rollup by cause is updated.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does it decide how a non-conformance is dispositioned?
No. It logs the disposition your quality team already recorded in Odyssey ERP, whether that's scrap, rework, or use as is. It doesn't make that call itself.
How far back does the rollup by cause go?
It keeps a rolling 30-day count by cause, updated every night, so you can see whether a defect type is trending up or down over the past month.
Can it flag a cause that's suddenly spiking?
Yes. It compares this week's count for each cause against last week's and highlights any cause that has jumped, so a new problem doesn't sit unnoticed in the log.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.