Template

Finite Scheduling Input Template — Capacity, Changeover & Constraints (Interactive)

An interactive template that captures the minimal, well-structured inputs a finite scheduler needs: resource calendars and shift capacity, operation cycle times, changeover/setup matrices, constraint flags, demand windows, priority rules, and expected lead times. Saves inputs as structured JSON for reuse, validation, and integration with scheduling tools.

Interactive Tool

Finite Scheduling Input Template (Capacity, Changeover, Constraints)

This interactive template helps capture the realistic, minimal inputs a finite scheduler needs to build short-term, executable schedules. Fill each field with the most accurate operational data available. Where helpful, paste CSV-style rows for bulk tables using the column headers shown in the help text.

Saved submissions are stored as structured JSON so your plant team or scheduling tools can reuse them, compare versions, and reduce rework.

A stable short code used by your systems (e.g., M-101, LINE-A, CELL-3). Required.
Choose the best match for this resource.
Describe the working pattern (shifts, start/end times, breaks) or paste a weekly calendar. Example: 'Mon–Fri: 06:00–14:00, 14:30–22:30; Sat: 06:00–14:00; Sun: off'. If you have a calendar ID in your MES/ERP, paste it here.
Net productive hours per shift for this resource after planned breaks and expected micro-stops. Use decimals. Required.
List known planned outages (dates/times or recurring windows). Example: 'Monthly PM: 1st Tue 08:00–12:00; Quarterly: 1st Sat 06:00–18:00'. These windows should be treated as unavailable capacity.
Paste rows with headers: operation_code, operation_name, standard_cycle_time_min, processing_station, setup_group. Example row: OP100,DrillHole,2.5,M-101,SG-A. Use minutes for cycle time. This table defines processing times for operations routed to this resource.
Optional: paste a changeover matrix with headers: from_setup_group,to_setup_group,changeover_minutes. When blank, schedulers may use a default setup time per group. Example: SG-A,SG-B,18 If your changeover depends on part families, map parts to setup groups in operation_times_csv.
Mark known resource constraints so the scheduler treats them appropriately.
Choose the rule the scheduler should apply when sequencing work on this resource. Teams can override per run.
If you selected 'Custom' above, describe the rule here (conditions, fields used, escalation logic).
Typical end-to-end lead time expectation for work routed through this resource. Helpful for feasibility checks and demand windowing.
List order IDs, required delivery dates, or committed windows that must be respected by schedules. Use one item per line with date or date window.
If you limit WIP by station, enter the maximum allowed units or batch size. Leave blank if not enforced.
Anything else the scheduler should know (safety holds, inspection steps, parallelism, preferred batching, etc.).
You can explore this tool now. Sign in or create an account to save your responses and return to them later.
Sign In to Save Create an Account
Make this tool part of your work

Save a personal copy, bring it to your team, or tailor the questions and workflow to fit what you are hungry to improve.

Member customization and team collaboration are coming soon.
Discuss Ask the Librarian

Discussion

Comments and conversation will live here.