Catch breakage and remakes as they happen
Every few minutes, WebRun opens Ocuco Innovations, finds jobs newly marked as breakage or remake, captures the cause and stage for each, appends them to a Google Sheet, and posts a Slack alert so production reworks the job quickly and recurring breakage patterns become visible.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I automatically track breakage and remakes in my optical lab?
WebRun watches Ocuco Innovations for jobs marked breakage, scrap, or remake and captures the stage and cause for each. It appends them to a Google Sheet, tallies remakes by cause and machine, and posts a Slack alert, so production reworks the job fast and a recurring quality problem surfaces before it ruins a whole run.
- Remakes get reworked within minutes of being flagged, not at end of shift
- Recurring breakage causes surface before they waste a full production run
- A live remake rate is visible in Slack all day without a manual tally
Built for optical lab managers · lab production supervisors · quality control teams · wholesale lens labs
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.ocuco.comin a real browser with your saved login - no setup, no API keys. -
1
Ocuco Innovations - find breakage and remake jobs
ocuco.com How to Automate Ocuco Innovations
WebRun opens Ocuco Innovations to find breakage and remake jobs. - Open Ocuco Innovations and review jobs flagged as breakage, scrap, or remake since the last run
- Capture the job number, ordering account, the stage where it broke such as surfacing, coating, or edging, and the recorded reason
- Note the lens type, material, and coating involved so material-specific patterns are visible
- Skip breakage events already logged
Done when Every new breakage or remake job is captured with its stage, cause, and materials.
-
2
Google Sheets - log each remake and its cause
google.com How to Automate Google Sheets
WebRun opens Google Sheets to log each remake and its cause. - Open the Breakage and Remake Log sheet
- Append each new event as a row with job number, account, stage, cause, material, and timestamp, avoiding duplicates
- Tally remakes by cause and by stage so the biggest sources of loss stand out
- Keep a running remake rate for the day
Done when The breakage log is current and totals by cause and stage are up to date.
-
3
Slack - alert production to rework it
slack.com How to Automate Slack
WebRun opens Slack to alert production to rework it. - Post an alert to the production channel for each new remake with the job number, stage, and cause
- Call out when the same cause or the same machine appears repeatedly in a short window
- Summarize the day's remake count and top cause so far
Done when Production has a Slack alert per remake plus a running count and top cause.
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 this message anyone outside the lab?
No. WebRun only writes to your internal Google Sheet and posts to your internal production Slack channel. No account or outside party is contacted, so it is safe to run unattended.
How does it help reduce remakes, not just count them?
It tallies every remake by cause, stage, and material and flags when the same cause or machine repeats, so a bad coating batch or a drifting edger surfaces before it wastes a shift of work.
What counts as a remake in the log?
Any job Ocuco Innovations marks as breakage, scrap, or remake. WebRun reads the reason recorded on the job, so the cause in the log matches what your operators entered.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.