Automated SigmaNEST Laser Program Revision Log
Every few minutes, WebRun checks SigmaNEST for laser program revisions, logs the job number, program version, who made the change, and what changed to Google Sheets, and posts a Slack alert to programmers and operators so nobody runs an outdated version of a part program.
How do I track laser program revisions in SigmaNEST automatically?
WebRun checks SigmaNEST every few minutes for laser program revisions and logs the job number, version, who made the change, and why to Google Sheets. It posts a Slack alert naming the current version and tagging the assigned operator, building a full audit trail while making sure nobody on the floor keeps running a superseded program.
- Every program revision is logged automatically with who changed it and why
- Operators get alerted the moment a newer program version exists
- A full revision audit trail builds without a manual change log
Built for laser cutting programmers · fabrication shop engineers · quality managers · sheet metal shop supervisors
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.sigmanest.comin a real browser with your saved login - no setup, no API keys. -
1
SigmaNEST - detect laser program revisions
sigmanest.com
WebRun opens SigmaNEST to detect laser program revisions. - Check SigmaNEST for laser programs revised since the last check
- Capture the job number, program name, version number, and who made the revision
- Note the reason for the revision where one is recorded
Done when Every laser program revision since the last check is captured with its details.
-
2
Google Sheets - log the revision history
google.com
WebRun opens Google Sheets to log the revision history. - Open the Laser Program Revision Log spreadsheet
- Append a row per revision with date, job number, version, revised by, and reason
- Mark the previous version as superseded
Done when Every revision is logged and the current version is clearly marked.
-
3
Slack - alert the team to the current version
slack.com
WebRun opens Slack to alert the team to the current version. - Post an alert naming the job number and new version whenever a program is revised
- Tag the operator currently assigned to run that job
- Note that the prior version should no longer be used
Done when Anyone running that job has been alerted to the current program version in Slack.
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 approve or block a program revision?
No. WebRun only logs revisions already made in SigmaNEST and alerts the team to the current version. Approving and making the revision itself stays with your programmer.
How far back does the revision history go?
As far back as the Google Sheet has been running. Every check appends new revisions, so the log builds into a complete audit trail over time.
What if an operator is already running an outdated version?
The Slack alert tags the operator assigned to that job as soon as a newer version exists, so they can confirm which print packet and program to use before continuing.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.