Finite capacity scheduling: how to build a realistic plan

Home » Resources » Finite capacity scheduling: how to build a realistic plan

Estimated reading time: 10 minutes

Finite capacity scheduling (FCS) assigns production operations to available resources at specific times. It fits work around machine capacity, shifts, qualified labor and tools, while respecting material readiness and the sequence of operations. The result is a timetable that shows when each job can actually start and finish.

For a production planner, the useful question is simple: can this order fit alongside the work already committed? A finite schedule exposes the conflict and its effect on completion dates. You can then choose which commitment to change or where extra capacity will help.

Finite vs. infinite scheduling: what changes on the shop floor?

An infinite schedule places work according to requested dates or lead-time assumptions, allowing the calculated load to exceed resource availability. A finite schedule allocates work within the capacity modeled for each resource. When that capacity is occupied, another operation needs a later slot or a suitable alternative resource.

Planning question	Infinite scheduling	Finite scheduling
Can two jobs use the same machine at once?	Calculated dates can overlap, exposing an overload for the planner to resolve.	Operations occupy separate available slots.
What happens when the shift fills up?	The load can exceed the shift’s available hours.	Remaining work moves to another available slot.
Where does a queue appear?	The shop floor may absorb work released against optimistic dates.	Waiting time appears between scheduled operations.
How is a delivery date assessed?	A lead-time calculation gives a target date.	The operation timetable provides a capacity-based completion date.
What changes after a breakdown?	The planner reconciles the existing dates with lost capacity.	Updating the resource calendar exposes the work that must move.

MRP calculates material requirements from demand, bills of materials and inventory information. Operation scheduling determines when resources can perform the work. These functions can work together within an ERP or through connected scheduling software; ERP systems can also include finite scheduling capabilities.

The practical benefit is earlier visibility of a conflict. If a machine loses its afternoon shift, the planner can see which operations and delivery commitments are affected before releasing the next jobs.

A worked example: two machines and one shared operator

A machine-load report can look comfortable while the schedule is impossible. The shared-operator feasibility worksheet below makes that hidden constraint visible.

This illustrative example uses two days, each with eight net working hours from 08:00 to 16:00. Materials are ready at the beginning of day 1, and the jobs have no dependencies. Durations include the relevant setup allowance. Each job needs operator O throughout its run. Job B can pause overnight and resume without an extra setup. The chosen priority order is A, C, then B.

Job	Machine	Duration	Shared resource	Target completion
A	M1	3 hours	Operator O	Day 1, 12:00
B	M1	3 hours	Operator O	Day 1, 16:00
C	M2	4 hours	Operator O	Day 1, 16:00

M1 has six hours of work in an eight-hour shift. M2 has four. Both machines have spare time. Operator O, however, has ten hours of work and eight available hours: 125% load, with a two-hour capacity shortfall.

A machine-only plan might run A on M1 from 08:00 to 11:00 and C on M2 from 08:00 to 12:00. That requires O in two places for three hours. Adding the operator constraint produces this feasible timetable:

Job	Scheduled time	Resources occupied	Completion result
A	Day 1, 08:00–11:00	M1 and O	Meets its target.
C	Day 1, 11:00–15:00	M2 and O	Meets its target.
B	Day 1, 15:00–16:00; day 2, 08:00–10:00	M1 and O	Finishes in the next shift.

B carries two working hours into day 2. Its completion moves from the day-1 target of 16:00 to day 2 at 10:00. The overnight gap matters when communicating the revised date to a customer.

Apply the worksheet to your own jobs

Create one row per operation with its required resources, processing time, setup time, material-ready time, predecessor and target completion. A starting workload calculation is:

Workload = setup time + quantity × cycle time

Use consistent time units. For 30 parts at four minutes each with a 20-minute setup, the machine workload is 140 minutes. Record operator occupancy separately: an unattended machine cycle may need labor only during setup and unloading.

Sum the workload for each resource, compare it with available calendar time, then place operations on a timeline. Each operation needs all its required resources together, after its material-ready time and predecessors. Finally, compare scheduled completion with the target. Total hours reveal a shortage; the timeline reveals simultaneous-resource conflicts and waiting.

The data a finite schedule needs

Start with one production flow and its main constraint. If a shared machining center determines delivery performance, model that center’s calendar, the operations feeding it and the resources those operations need. Expand the model as you validate it against actual work.

Input	What to capture	Effect of an inaccurate value
Orders and priorities	Quantity, target date and relative urgency	Available slots go to the wrong commitments.
Operation sequence	Predecessors, transfer requirements and eligible machines	A downstream step starts too early or uses an unsuitable machine.
Processing and setup times	Run time, setup allowance and relevant changeovers	Booked work occupies too little or too much capacity.
Resource calendars	Shifts, breaks, maintenance and absences	Work lands in unavailable time.
Skills and tools	Qualified labor and shared tooling needed for each operation	A machine slot appears usable while another required resource is occupied.
Material readiness	Availability time for required components	An operation receives a slot before its materials arrive.
Execution feedback	Completed quantity, actual progress and remaining work	Finished work stays booked or unfinished work loses its capacity allocation.

Model machine and labor time according to the process. In an attended assembly operation they may be identical. In automated machining they may differ substantially. This distinction can determine whether the apparent bottleneck is equipment or staffing.

How to build and update a finite capacity schedule

1. Define the planning scope. Select the orders, operations and horizon you need to schedule. Include existing commitments that already occupy those resources.

2. Set available calendars. Enter working time and planned downtime for machines and shared resources. Use net available time consistently with operation durations.

3. Connect operations and materials. Confirm the sequence, resource eligibility and earliest material-ready times. Check the inputs for the constraint first.

4. Choose priorities. Decide which commitments take precedence when they compete for capacity. Preserve work already released or fixed where your operating process requires it.

5. Place and inspect operations. Review overloaded resources, waiting time and completion dates. Trace a late order through its operations to identify the constraint that moved it.

6. Update from execution. Record progress, revised durations and changed availability. Recalculate affected work and communicate revised commitments.

Forward scheduling starts from an earliest available start and finds a completion date. It helps answer when a new order can finish. Backward scheduling starts from a required completion and works toward earlier operations. It helps identify the latest workable start. Both approaches need resource availability checks; a backward calculation can reveal that a target requires work to begin before materials are ready.

When capacity falls short, test a specific decision

Return to the shared-operator example. A second qualified operator is available on day 1 only from 13:00 to 15:00. Keep A at 08:00–11:00 and C at 11:00–15:00. Run B on M1 from 13:00 to 16:00: the additional operator covers 13:00–15:00, then O takes over for the final hour. All three jobs now meet their targets.

The decision is two additional qualified labor hours in a specific window. Extra machine time would leave the original staffing conflict unresolved.

Other choices include an eligible alternative machine, a revised sequence, a split batch or a changed delivery commitment. Test each choice against the resources it actually changes. Splitting a batch may add setup work; moving an operation may require different tooling. Record the new completion date and any added workload before approving the change.

What to test in finite capacity scheduling software

Bring a small, representative set of orders, a routing and resource calendars to a software evaluation. Ask to see the operation timetable and the reason a job moved.

Test	What a useful result shows
Schedule two jobs needing one shared resource	Separate resource reservations and the resulting completion times.
Delay a required material	The affected operation moves behind the new availability time, with downstream effects visible.
Remove a shift or record an absence	Lost capacity changes the affected work and delivery outlook.
Add an urgent order	The planner’s chosen priorities govern the revised sequence.
Preserve a fixed operation	The revised schedule respects the commitment while moving eligible work around it.
Compare additional capacity	The targeted extra resource changes the relevant completion dates.

Repeat the tests with the labor pattern your factory uses. A model that handles fully attended work should also represent your setup-only staffing or shared-tool requirements where those apply. Inspect an order across its complete route, including waiting between workstations.

Put the method to work with SkyPlanner

SkyPlanner APS is advanced planning and scheduling software for discrete manufacturers. Its Arcturus AI schedules jobs to workstations with material availability, shifts, priorities and delivery dates taken into account. The interactive Gantt timeline shows the schedule, and automatic rescheduling helps accommodate changes in production.

Explore SkyPlanner’s AI production scheduling software to see how those inputs become a production timetable. SkyPlanner integrates with any ERP or MES system through its open REST API, connecting the scheduling workflow to your existing systems.

Start your 30-day free trial with demo data or the AI-assisted Getting Started path in SkyPlanner Assistant. Use the evaluation questions above to focus your next conversation on the constraints that determine your factory’s delivery dates.

Frequently asked questions

Is finite capacity scheduling the same as capacity planning?

Capacity planning assesses whether available resources can cover expected demand over a period. Scheduling assigns individual operations to times and resources. A weekly capacity balance can look acceptable while one tool is needed by two operations on Tuesday morning; use the worksheet to examine that overlap.

Does finite scheduling always produce the optimal schedule?

A feasible timetable is the starting point for optimization. Several feasible sequences can give different delivery performance and setup totals. Select the objective you want to improve, then compare those outcomes while keeping the same resource constraints.

Can I use finite capacity scheduling in Excel?

Excel can model a small queue with simple resource calendars. It is useful for trying the worksheet with your own durations. Consider scheduling software when maintaining operation dependencies, shared resources and repeated changes takes substantial manual work.

What happens when an order cannot fit before its due date?

Identify the resource causing the delay and test a concrete change. For example, additional staffing helps only when the person is qualified and available during the conflicting operation. Confirm the revised finish time before making a new delivery commitment.

How does finite scheduling work with an ERP or MES?

An ERP can supply orders and production master data, while an MES can supply execution feedback. Scheduling uses these inputs to update the operation timetable. For an integration project, agree which system supplies each input and how completed or changed work returns to the planning workflow.