Managed cloud
We run it for you on AWS in the US. Nothing to install, and updates arrive on their own.
UpgradeAI Scheduling
Your schedule, rebuilt by talking to it.
Scroll to watch one shop get through one bad week.
UpgradeAIScheduler
Good morning. 18 jobs on 6 machines this week, and all 9 orders are on time.
Shopfloor 1Week of Oct 26
Mon 7:02 AM
Mon 7:02 AM
Change shows up in whatever form it comes.
A customer email. Paste it in as it is. UpgradeAI pulls out the one fact that matters: PO 4471 is now due Thursday, and the current plan finishes it Friday.
Dana Ruiz · Meridian Robotics
PO 4471: can we pull it in?
Our line move got moved up a week. Any chance PO 4471 ships this Thursday instead of next Monday?
Pulled out WO-4471 due date: next Mon → Thu 6:00 PM The current plan finishes it Fri 1:00 PM.
A supervisor's shift note. M-Mill-2 is down all of Thursday for a spindle repair, and two planned jobs sit on it.
shift-notes-thu.md
Thursday: M-Mill-2 down all day. Spindle bearing replacement, vendor on site at 6 AM.
Pulled out M-Mill-2 unavailable Thu 6:00 AM – 10:00 PM 2 planned jobs overlap it.
The ERP export. A new rush order for Helix Robotics is in the file and not on the schedule yet.
Works today Pasted text Markdown Excel CSV
Coming PDF purchase orders Voice notes
open-orders-oct26.xlsx
Pulled out New order WO-4490, Helix Robotics, 25 pcs, due Wed 10:00 PM Not on the schedule yet.
Mon 7:15 AM
It replans while you watch.
Ask in plain words. The dashed outlines keep the plan you started with on screen, so every change is easy to see.
Work all of that in. Nothing else should ship late.
M-Mill-1 has room on Wednesday. I'll move the Thursday jobs off M-Mill-2 and fit 4490 in.
Each change arrives as a card you can read. 4471 moves to M-Mill-1 and now ships Thursday morning.
Moved WO-4471 Machin to M-Mill-1 Starts Wed 8:00 AM. Ships Thu 8:00 AM, due Thu 6:00 PM.
4483 starts earlier on M-Mill-2, so it's done before the repair crew arrives.
Pulled WO-4483 Machin in to Wed 10:00 AM Done Wed 10:00 PM, before the repair starts.
The rush order goes where it fits. All ten orders are on time, and you can see exactly which jobs moved.
Scheduled WO-4490 on S-Mill-1 Machin Wed 6:00 AM, Deburr Wed 1:00 PM. Due Wed 10:00 PM.
All 10 orders are on time, and M-Mill-2 is clear for Thursday.
Mon 7:30 AM
You stay in control.
Every bar on the board is yours to move. Try it: drag a job to a new time, or to the other mill of the same size. UpgradeAI tells you what your change does to the rest of the week.
The board is yours. Drag any job and I'll tell you what it does to the rest of the week.
Wed 11:40 AM
Problems show up before the floor finds them.
Real run times come back from the floor and the plan moves with them. 4475 on S-Mill-1 is running long, so the jobs behind it slide.
Wed 11:40 AM
Anything at risk this week?
One check turns that into a short list: a rush order that will now ship late, and a job planned before its material arrives.
Checked the schedule 2 issues found.
WO-4490 will ship late 4475 is running long on S-Mill-1, so 4490 now finishes Thu 2:00 PM. Due Wed 10:00 PM.
WO-4466 has no material yet The supplier moved the bar stock to Thu 10:00 AM. Machining is planned Wed 2:00 PM.
UpgradeAI builds an alternative and puts both plans side by side, so you see the difference before you commit to it.
Alternative: run 4490 on S-Mill-2 from noon, then start 4466 once the bar stock is in. Both orders ship on time.
Apply it. Four jobs move, and both issues are gone.
Applied the alternative 4 jobs moved. No open issues.
Fri 9:40 PM
10 orders shipped. 0 late.
A pulled-in order, a machine down for a day, a rush job, a long run and a late delivery. Five changes in one week, handled in a few minutes each.
Fri 9:40 PM
All 10 orders shipped this week. None late.
Deployment
Runs where your data has to live.
The same product on every path. You choose where it runs.
Government cloud
Deployable in FedRAMP-authorized government clouds such as AWS GovCloud (US), for work that has to stay there.
On your own servers
Runs inside your network on standard Kubernetes, next to the systems it reads from.
Your data stays yours.
- Each company's data lives in its own organization, separate from every other customer.
- AI chats and uploaded files are private to the person who made them.
- Our support team sees your data only when an owner grants access, for a set number of days.
- You decide who on your team gets access.
Try it on your own shop.
We're onboarding a small group of high-mix shops for the beta. Tell us a little about your shop and we'll set it up with your machines and routers.