Use cases guide

The Task Scheduling model powers automated, optimized scheduling of jobs across machines and employees, from factory floors and project teams to maintenance crews and laboratories.

This guide outlines common use cases and shares tips on how to use Timefold’s Task Scheduling model for each.

Use cases of the Task Scheduling model include:

  • Discrete manufacturing: sequence production jobs across machines and operators while minimizing setup and changeover time.

  • Project scheduling: sequence project tasks, respect dependencies, and assign the right people to each task.

  • Single-site maintenance: plan and assign preventive and corrective maintenance work on assets at one site.

  • Laboratory and testing: schedule sample analyses across instruments and analysts while respecting deadlines and calibration needs.

The Task Scheduling model assigns each job to a machine that processes jobs one at a time, and optionally to an employee whose skills and availability also constrain the job. "Machine" is the primary sequential resource a job occupies, so in different industries it can represent a production machine, a project resource, an asset undergoing maintenance, or a lab instrument. The tables below show how to interpret these terms for each use case.

Discrete manufacturing

Typical use case

Manufacturers use the Task Scheduling model to sequence production jobs across machines and operators. It orders work to reduce changeovers, respects setup times and capacity, and reoptimizes when a line goes down or a rush order lands, to boost throughput and protect delivery commitments.

Key challenges

  • Minimizing setup and changeover time by sequencing similar jobs together.

  • Assigning jobs to the right machine and a qualified operator.

  • Avoiding conflicts over shared tooling and limited capacity.

  • Meeting due dates and delivery commitments.

  • Reacting to machine breakdowns and high-priority rush orders without rebuilding the whole plan.

How to interpret model terms

Model term How it applies to this use case

Machine

A production machine, workstation, or line that processes one job at a time.

Employee

A machine operator whose skills and availability determine which jobs they can run.

Job

A production operation or work-order step with a duration.

Job type

The product or part category of a job, used to determine changeover time between consecutive jobs.

How to address common scheduling problems

Problem Solve it with

You want to reduce setup and changeover time between jobs.

Define job transitions driven by job types and machine types.

You need to run jobs in the correct production order.

Model job dependencies between operations.

You need only capable machines or qualified operators to run a job.

Use required tags and employee resources.

A job takes longer on some machines or with some operators than others.

Set resource-specific durations.

You want to finish production as early as possible.

Optimize makespan.

You need to account for planned machine downtime or maintenance windows.

Add machine unavailability.

You want to insert an urgent rush order first when capacity is tight.

Assign job priorities.

You want to reschedule around a breakdown while protecting jobs already running.

Combine freeze jobs until with real-time planning.

Project scheduling

Typical use case

Project teams use the Task Scheduling model to turn tasks, durations, dependencies, and skills into an executable plan. It respects precedence rules, assigns resources by skill and availability, and reoptimizes as scope or staffing changes, so projects stay on time and on budget.

Key challenges

  • Respecting task dependencies and precedence rules so no work starts before its prerequisites finish.

  • Matching skills and roles to each task without overbooking resources.

  • Coordinating shared resources across parallel tasks or projects.

  • Honoring task priorities and deadlines.

  • Reforecasting instantly when scope, duration, or staffing shifts.

How to interpret model terms

Model term How it applies to this use case

Machine

A resource that handles one task at a time, such as a team, a workspace, or a piece of equipment.

Employee

A team member or specialist whose skills and availability constrain which tasks they can take on.

Job

A project task with a duration.

Job dependency

A precedence relationship between tasks, optionally with a minimum or maximum delay.

How to address common scheduling problems

Problem Solve it with

You need tasks to run in the correct order.

Model preceding-job dependencies.

You need a minimum or maximum gap between dependent tasks (for example, curing or review time).

Set a delay between dependent jobs.

You need related tasks handled by the same resource.

Require dependent jobs to use the same resource.

You must assign tasks to people with the right skills.

Use required tags and employee resources.

You want to prioritize critical-path or high-value work when resources are scarce.

Assign job priorities.

You need certain tasks to hit a target completion time.

Use time windows or an ideal end time.

You want to spread work evenly across teams or resources.

Apply balance jobs across machines.

You want to replan when scope or staffing changes mid-project.

Use real-time planning and freeze jobs until to protect committed work.

Single-site maintenance

Typical use case

Maintenance teams use the Task Scheduling model to plan and assign preventive and corrective work on assets at a single site. It sequences tasks by priority and dependencies, assigns qualified and certified technicians, and coordinates access to shared equipment and restricted zones, to increase asset uptime while staying compliant.

Key challenges

  • Sequencing tasks to minimize asset downtime while respecting dependencies.

  • Ensuring only qualified and certified technicians handle specialized or high-risk work.

  • Coordinating access to shared tools, restricted zones, and critical machinery.

  • Balancing preventive and corrective maintenance.

  • Responding to urgent work orders and breakdowns quickly.

How to interpret model terms

Model term How it applies to this use case

Machine

The asset, equipment, or work area undergoing maintenance, which can only have one task performed on it at a time.

Employee

The technician performing the task, with skills, certifications, and availability.

Job

A maintenance task or work order with a duration.

Priority

How urgent a task is, used to schedule critical or corrective work ahead of routine preventive work.

How to address common scheduling problems

Problem Solve it with

You need tasks performed in a safe, required sequence.

Model job dependencies, and prevent other work in between with no intermediate jobs.

You must assign only certified or qualified technicians to high-risk work.

Use employee resources with required tags for certifications.

You need a specific asset, bay, or tool for a task.

Restrict the job with required resources.

You must respect asset access windows and planned shutdowns.

Add machine unavailability.

You must handle urgent corrective work ahead of routine preventive tasks.

Assign job priorities.

Some tasks take longer for less-experienced technicians.

Set resource-specific durations.

You must respond to breakdowns while protecting work already under way.

Use real-time planning with freeze jobs until.

Laboratory and testing

Typical use case

Laboratories use the Task Scheduling model to schedule sample analyses across instruments and analysts. It sequences tests to reduce calibration and setup between assay types, assigns qualified analysts, and honors sample-stability deadlines and rush requests, to raise instrument use and turnaround.

Key challenges

  • Sequencing tests to minimize calibration and setup between assay types.

  • Assigning analyses to capable instruments and qualified analysts.

  • Meeting sample-stability deadlines and turnaround targets.

  • Prioritizing rush or clinical-critical samples.

  • Working around instrument downtime, calibration, and maintenance.

How to interpret model terms

Model term How it applies to this use case

Machine

An analytical instrument that processes one test at a time.

Employee

An analyst or technician whose qualifications determine which tests they can run.

Job

A test or analysis performed on a sample, with a duration.

Job type

The assay or test category, used to determine calibration or setup time between consecutive tests.

How to address common scheduling problems

Problem Solve it with

You want to reduce calibration or setup between different assay types.

Define job transitions driven by job types and machine types.

You must run tests only on capable instruments and qualified analysts.

Use required tags and employee resources.

A sample must be analyzed before it degrades.

Add a required latest end time, or target an ideal end time.

Multi-step protocols must run in order.

Model job dependencies, with a delay between steps where needed.

You must fast-track rush or clinical-critical samples.

Assign job priorities.

An instrument is down for calibration or maintenance.

Add machine unavailability.

You want to clear the backlog as fast as possible.

Optimize makespan.

New samples arrive throughout the day.

Use real-time planning with freeze jobs until.