The Fourth Shift add-ons do the real work on the floor: the scan that moves inventory, the watcher that catches the late PO, the count that has to tie. We've written and rebuilt hundreds of these scripts and configurations — and we've built an AI expert on the documentation, the script library and our own conventions, so the answer to "why did it do that?" takes minutes instead of a support ticket.
Every one of these is a place where a wrong scan, a missed event or a mistyped count becomes wrong inventory in a plant that runs around the clock. The job is to make the correct path the path of least resistance.
Receipts, moves, issues, picks, labor and completions — scripted between the scanner and the ERP so the standard transaction fits the real flow.
Late POs, negative on-hand, stuck work orders, orders shipped without an invoice, a price that changed overnight. Watched continuously, alerted to the right person, escalated when ignored.
Planning, tag or sheet setup, count-day support, variance review and posting. Reconciled to root cause so the same variances don't come back next year.
Fourth Shift knowledge is leaving plants faster than it's being replaced. The people who wrote your VisiBar scripts are retiring; the vendor's documentation was last updated when they still shipped it on CD. So we built the expert we wished we'd had in 1998.
What it knows. The VisiBar, VisiWatch and IAMS product documentation. A library of working scripts and configurations from real plants. Our own conventions: how prompts are guarded, how recordsets are handled, which transaction contracts are safe to call from a scanner and which aren't.
What it does. Explains what an existing script actually does. Reviews a change before it goes to sandbox. Drafts a new script to a spec. Diagnoses an error message with the reference cited — so you can check it, not just trust it.
What it never does. Touch production. It has no write path to Fourth Shift. Every change still goes through the sandbox-to-production protocol, because that discipline is the whole point.
Want the same thing for the whole environment, not just the toolset? The Fourth Shift AI Expert assessment → Or ongoing help that leaves your team more capable: Fourth Shift support →
This is the protocol a South African wheel plant now follows for every VisiBar change, three shifts a day. It's boring on purpose.
The transaction, the prompts, the guards, the failure cases — written down before a line is changed.
Built and run against a copy of production data with the real items, lots and locations that break things.
Test transactions traced through to inventory and GL. If the numbers don't tie, it doesn't ship.
Controlled release, VisiWatch on the new path for the first shifts, and the change documented for whoever comes next.
A VisiBar script that errors on lot-tracked items, a VisiWatch alert that fires at 3 a.m. for nothing, a physical inventory that took a week and still didn't tie. Tell us which one and what it's doing.
You'll get a straight answer and a tight scope. If we can't help, we'll tell you that too — and usually who can.
