Work-center load, order queue and material requirements in one place. The planner sees which orders will shift and what will run short before confirming the change.
A spreadsheet with colours and macros nobody but the planner touches. When the planner is on holiday, the week's plan stands still.
The customer moves collection by a week. The planner reshuffles orders in three files, calls purchasing and reprints the floor's schedule. Something slips along the way.
Supplier orders placed from memory and with a "just in case" buffer. One day the profile for tomorrow is missing, the next the warehouse is full of material from six months ago.
Built around your work centers, routings and the way your planner works. We start with one department.
Three years ago features like these needed a data science team. Today language models read emails, documents and photos, and we build them into the system we make for you. Below is what makes sense in this solution. A person approves, AI prepares.
From due dates, load, material and time history the model lays out a proposed plan. The planner reviews, reshuffles and approves.
Example 40 orders across three work centers with two critical dates → a proposed queue with the orders that will not fit without overtime marked
The model learns from history how far actual times differ from standard ones at each work center, and warns about a date at risk while there is still room to reshuffle.
Example a welding order planned for 6 hours, history of this part says 8 → an alert about Friday's collection being at risk
A customer's email about a moved collection or a changed quantity arrives as a proposed plan change, with its consequences to review.
Example email "can you add 200 more pieces to the same delivery?" → a proposal to increase the order, with whether material and the work center can take it
The salesperson, owner or foreman asks in plain language. The answer comes from the current plan.
Example "will we make it for Nowak by the 20th if the urgent one from Kowalski comes in?" → a list of orders that will shift, and by how much
Orders and BOMs come from the ERP, completion from the floor or the MES, stock from the warehouse. The plan goes back to the ERP.
The first version does what the spreadsheet does today, only faster and for everyone. The planner works in both until they stop opening the spreadsheet.
You have the diagnosis, we build the solution. Web applications, B2B portals and automations for companies without a large IT department. Today a system can read emails and documents, suggest decisions and answer customers on its own, so we build that in from the first version, not as an add-on a year later.
We agree scope, price and dates upfront, show progress every week, and the code and data stay yours.
You tell us how the week's plan is made today and what happens when a customer changes a date, we tell you which department to start with.
Write to us