Odyssey ERP Automated Pattern Maintenance Reminders
Every Monday, WebRun opens Odyssey ERP, checks every active pattern's impression count against its maintenance interval, and emails the pattern shop lead in Outlook a list of which patterns are due for inspection or rework this week, ordered by how overdue they are.
How do I know which patterns are due for maintenance?
WebRun tracks pattern wear for you. Every Monday, it opens Odyssey ERP, checks each active pattern's impression count against its maintenance interval, and emails your pattern shop lead in Outlook a ranked list of what is due or overdue, so worn patterns get pulled for rework before they start producing bad castings.
- Worn patterns are flagged before they start producing defective castings
- The pattern shop gets a ranked due list every Monday instead of tracking impressions by hand
- Maintenance history stays tied to each pattern's real impression count
Built for sand casting foundries · pattern shop leads · foundry tooling managers · permanent mold casters
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 - check pattern impression counts
blinfo.com
WebRun opens Odyssey ERP to check pattern impression counts. - Open Odyssey ERP and pull every active pattern's impression count and maintenance interval
- Calculate how many impressions remain before each pattern's next scheduled maintenance
- Sort patterns by how close, or how far past, they are from their interval
Done when Every active pattern's impression count is checked against its maintenance interval.
-
2
Outlook - email the pattern shop the due list
microsoft.com
WebRun opens Outlook to email the pattern shop the due list. - Draft and send an email to the pattern shop lead listing patterns due or overdue for maintenance this week
- Put the most overdue patterns at the top with their impression count and job history
- Send the list to your internal pattern shop distribution only. No customer or vendor is contacted
Done when The pattern shop has this week's maintenance due list in their inbox.
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
Will it pull patterns out of service on its own?
No. It only sends the maintenance due list. Someone on the pattern shop still decides when a pattern actually comes off the floor for inspection or rework.
How does it know a pattern's maintenance interval?
It reads the interval already set on each pattern's record in Odyssey ERP, whether that's a fixed impression count or a time based schedule, and compares it to the pattern's current count.
What if a pattern is used across multiple jobs?
Its impression count in Odyssey ERP already totals every job it's run, so the reminder reflects real cumulative wear, not just the count from one job.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.