Fill load and available hours to see the utilization read.
Economic batch size (needs costs)
Fill all three to see the economic batch size.
Nothing to paste? — a machine shop's next 48 hours: nine work orders across three families and two lines, a frozen first shift, a 4-hour maintenance outage on the constraint, a job that is already lost, and a rush order sales wants squeezed in. Or , rendered from a saved reply with no run and no charge.
Paste the work orders
Job lines plus the scenario: lines, available hours, changeover matrices, freezes, disruptions. The job scanner sizes the board up free in your browser — total load, EDD and SPT lateness reads. No sign-in needed for that.
Say what you need
Full schedule, bottleneck check, changeover sequencing, rush order insertion, or disruption response — plus any notes. A job the numbers say will miss its date is reported whatever the task; the task sets where the depth goes.
Post the sequence
The drum named with its load arithmetic, a sequence with the timing and the reason for every slot, changeovers taken from your matrix with an SMED note where one helps — and the risks, actions and open questions. Download the sequence as a CSV a spreadsheet or a dispatch list will take, or as markdown.
What do I paste in?
Job lines like WO-4411: 6h, due 24 — the first number is processing hours, the number after “due” is hours from now — plus prose about your lines and work centers, available hours, the changeover matrix, any frozen window, a breakdown or a rush order. Messy is fine. Anything you leave out comes back as an open question rather than as an invented number.
Are the timings clock times?
No. Every timing is hours from now, consistent with the processing times you pasted — h0 is the moment you ran the schedule. The CSV export carries the start and finish hours in their own columns so you can offset them to your shift clock.
What runs free, without signing in?
The job scanner and the bottleneck calculator. The scanner detects the job lines in your paste and computes total load plus the single-machine EDD and SPT lateness reads; the calculator turns load and available hours into a utilization verdict, and an economic batch size when you supply the costs. Both run entirely in your browser — nothing is sent anywhere and there is no charge. Building the schedule itself uses the model and costs credits.
What happens when I run the same board twice?
The second schedule is compared against the first and the difference is shown above the summary: which job slips or pulls in and by how many hours, whether the drum moved, and whether the feasibility call changed. That is the question a rush order or a breakdown is really asking, so it is answered in the browser rather than by another run.
Can the schedule quietly drop one of my work orders?
It is checked. After every run the browser compares the returned sequence against the job lines the free scanner read out of your paste, and any detected work order that never got a slot is flagged in red under the schedule — before you post it, not after.