Decision pattern
Job Shop Scheduling
Job-shop scheduling sequences ordered operations from multiple jobs across shared machines so precedence and capacity constraints are satisfied.
Use this when
Job-shop scheduling gets difficult when each job has ordered operations, each operation needs a specific machine, and machines can process only one operation at a time.
Inputs
jobs and operations, machine eligibility, processing times, precedence and due dates.
Constraints
Machine no-overlap, Operation precedence, Release times, Due dates, Optional tardiness penalty.
Decision output
machine sequence, operation timing, makespan or tardiness measure, bottleneck visibility.
A small example
Schedulers try to sequence operations manually and often miss that a later job blocks a high-priority operation. The decision process makes the rules explicit, then compares feasible options against the stated objective: Minimize makespan, with optional weighted tardiness for due-date-sensitive jobs.
| Job | Operation | Machine | Duration | Predecessor | Due date |
|---|---|---|---|---|---|
| J1 | 1 | M1 | 3 | - | 18 |
| J1 | 2 | M2 | 2 | 1 | 18 |
| J2 | 1 | M1 | 2 | - | 20 |
Relevant industries
Related decisions
Choose how to use Optivise
Use the same decision intelligence through an AI agent, a familiar work tool, or a shared enterprise workflow.
Agent Optimization Engine
Use Optivise through the AI agent you already work with.
Explore Agent EngineSmart Planner
Start from a familiar spreadsheet and the operational data you already maintain.
Explore Smart PlannerOptivise Platform
Build persistent, shared, and governed decision workflows for your team.
Explore Optivise Platform