FactoryLogix Automatic Kitting Status Updates
Every morning before the shift starts, WebRun opens FactoryLogix, checks the kitting status of every work order scheduled today, logs each one as complete, short, or not yet pulled in a Google Sheet, and posts the shift's kitting status to your production Telegram group.
How do I give the production floor a kitting status update every shift?
WebRun checks FactoryLogix each morning for the kitting status of every work order scheduled that day, logs each one as complete, short, or not yet pulled in a Google Sheet, and posts a shift start summary to your production Telegram group naming any short kit and its missing component before the first work order is due to start.
- The floor knows which kits are short before the shift starts, not mid run
- Short kits are named with the exact missing component for a faster chase
- A running Google Sheet log tracks kitting reliability over time
Built for contract electronics manufacturers · kitting and warehouse teams · SMT production supervisors · EMS shift leads
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.aiscorp.com/solutions/lean-materials-managementin a real browser with your saved login - no setup, no API keys. -
1
FactoryLogix - check kitting status for today's work orders
aiscorp.com
WebRun opens FactoryLogix to check kitting status for today's work orders. - Open FactoryLogix Lean Materials Management and list every work order scheduled to run today
- Check each work order's kit status: complete, short one or more components, or not yet pulled
- For any short kit, note which component and how much is missing
Done when Every work order scheduled today has a recorded kit status.
-
2
Google Sheets - log each kit as complete, short, or not pulled
google.com
WebRun opens Google Sheets to log each kit as complete, short, or not pulled. - Open the kitting status log and add or update one row per work order for today's date
- Record the status, the missing component if short, and the scheduled start time
- Sort short kits to the top so they stand out first
Done when Today's kitting status log has one current row per scheduled work order.
-
3
Telegram - post the shift's kitting status to the floor
telegram.org
WebRun opens Telegram to post the shift's kitting status to the floor. - Post the production group a shift start summary: how many kits are complete, how many are short, and how many are not yet pulled
- List each short kit by work order and the missing component
- Keep the message short enough to read on the floor in under a minute
Done when The floor has this shift's kitting status in the Telegram group before the first work order starts.
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 replace the kitting team's own checklist?
No. WebRun reads the kit status your team already records in FactoryLogix and reports it. It does not pull, count, or stage a single component itself.
What counts as a short kit?
Any work order where FactoryLogix shows at least one component not fully allocated to the kit. The Telegram summary names the work order and the missing part so the shortage team can chase it.
Can it post to Slack instead of Telegram?
Yes. Telegram is the default here because it is common on the shop floor, but the channel is configurable to Slack or another tool your team already uses.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.