CyFrame Automatic Co-Extrusion Recipe Logs
Every hour, WebRun opens CyFrame, finds co-extrusion jobs newly started on any line, and logs the capstock and substrate ratio, layer thickness, resin lots, and screw speeds for each extruder to a Google Sheet, so every recipe run is traceable back to the job that used it.
How do I keep a record of every co-extrusion recipe I run?
WebRun keeps a searchable history of every co-extrusion recipe you run. Each hour it opens CyFrame, finds jobs newly started on any line, and logs the capstock to substrate ratio, layer thickness, resin lots, and screw speeds to a Google Sheet, so any job's exact setup can be pulled up later for QC or a customer question.
- Every co-extrusion job's exact recipe is searchable after the fact
- QC and customer questions get answered from the log, not a memory
- Layer ratios and resin lots stay traceable to the job that used them
Built for plastics profile extruders · co-extrusion line operators · quality control teams · process 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
cyframe.comin a real browser with your saved login - no setup, no API keys. -
1
CyFrame - find newly started co-extrusion jobs
cyframe.com
WebRun opens CyFrame to find newly started co-extrusion jobs. - Open CyFrame and find co-extrusion jobs started on any line since the last check
- Read the capstock to substrate ratio, layer thickness target, and resin lot assigned to each extruder
- Capture the screw speed and barrel temperature profile set for the job
Done when Every newly started co-extrusion job has its recipe details captured.
-
2
Google Sheets - log the recipe details
google.com
WebRun opens Google Sheets to log the recipe details. - Open the recipe log and add a row per co-extrusion job
- Record the job, line, layer ratio, resin lots, screw speeds, and barrel temperatures
- Link each row to the job number so it can be pulled up if a customer or QC question comes up later
Done when The recipe log holds every co-extrusion job started this hour with its full setup.
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 change any settings on the line?
No. WebRun only reads the recipe CyFrame already has recorded for each job and copies it to the log. It never adjusts a screw speed, temperature, or ratio on the line itself.
Why log recipes that are already in CyFrame?
The Google Sheet gives you a single searchable history across jobs, separate from CyFrame's job records, so you or QC can pull up exactly what ran on a given order without digging through individual job screens.
What if a job's recipe changes mid run?
The next hourly check picks up whatever CyFrame shows at that point, so a recipe change made partway through a run is captured on its next pass.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.