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.
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.
", "SubmitLabel": "Save Scheduling Inputs", "SuccessMessage": "Scheduling inputs saved. You can update, reuse, or export this data for your scheduling engine or MES/ERP integration.", "DataType": "FiniteSchedulingInputV1", "SchemaVersion": 1, "Fields": [ { "Key": "resource_id", "FieldType": "text", "Label": "Resource identifier (machine/line/cell)", "HelpText": "A stable short code used by your systems (e.g., M-101, LINE-A, CELL-3). Required.", "Required": true }, { "Key": "resource_type", "FieldType": "select", "Label": "Resource type", "HelpText": "Choose the best match for this resource.", "Required": true, "Options": [ { "Value": "machine", "Label": "Machine / Equipment" }, { "Value": "line", "Label": "Production line" }, { "Value": "cell", "Label": "Work cell / Station set" }, { "Value": "workcenter", "Label": "Workcenter" }, { "Value": "other", "Label": "Other" } ] }, { "Key": "resource_calendar", "FieldType": "textarea", "Label": "Resource calendar summary", "HelpText": "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.", "Required": true }, { "Key": "capacity_per_shift_hours", "FieldType": "number", "Label": "Effective capacity per shift (hours)", "HelpText": "Net productive hours per shift for this resource after planned breaks and expected micro-stops. Use decimals. Required.", "Required": true }, { "Key": "planned_maintenance_windows", "FieldType": "textarea", "Label": "Planned maintenance / downtime windows", "HelpText": "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.", "Required": false }, { "Key": "operation_times_csv", "FieldType": "textarea", "Label": "Operation times (CSV rows)", "HelpText": "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.", "Required": true }, { "Key": "changeover_matrix_csv", "FieldType": "textarea", "Label": "Changeover / setup time matrix (CSV)", "HelpText": "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.", "Required": false }, { "Key": "constraint_flags", "FieldType": "checkbox", "Label": "Constraint flags (select all that apply)", "HelpText": "Mark known resource constraints so the scheduler treats them appropriately.", "Options": [ { "Value": "bottleneck", "Label": "Known bottleneck / constrained capacity" }, { "Value": "material_supply_limit", "Label": "Material supply or feeder limit" }, { "Value": "operator_skill", "Label": "Requires certified/skilled operator" }, { "Value": "fixture_constraint", "Label": "Limited fixtures/tools" }, { "Value": "quality_hold", "Label": "Intermittent quality holds suspected" }, { "Value": "sequence_sensitive", "Label": "Sequence-dependent operations (must preserve order)" } ], "Required": false }, { "Key": "priority_rule", "FieldType": "select", "Label": "Default priority rule for this resource", "HelpText": "Choose the rule the scheduler should apply when sequencing work on this resource. Teams can override per run.", "Options": [ { "Value": "due_date", "Label": "Earliest due date (EDD)" }, { "Value": "customer_priority", "Label": "Customer / order priority" }, { "Value": "shortest_processing_time", "Label": "Shortest processing time (SPT)" }, { "Value": "critical_ratio", "Label": "Critical ratio (time remaining / work remaining)" }, { "Value": "custom", "Label": "Custom rule (describe below)" } ], "Required": true }, { "Key": "custom_priority_description", "FieldType": "textarea", "Label": "Custom priority rule details", "HelpText": "If you selected 'Custom' above, describe the rule here (conditions, fields used, escalation logic).", "Required": false }, { "Key": "expected_lead_time_days", "FieldType": "number", "Label": "Expected lead time for this family/resource (days)", "HelpText": "Typical end-to-end lead time expectation for work routed through this resource. Helpful for feasibility checks and demand windowing.", "Required": false }, { "Key": "demand_windows", "FieldType": "textarea", "Label": "Demand windows / delivery commitments", "HelpText": "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.", "Required": false }, { "Key": "max_wip_units", "FieldType": "number", "Label": "Maximum allowed WIP at this resource (units)", "HelpText": "If you limit WIP by station, enter the maximum allowed units or batch size. Leave blank if not enforced.", "Required": false }, { "Key": "notes", "FieldType": "textarea", "Label": "Additional notes or local rules", "HelpText": "Anything else the scheduler should know (safety holds, inspection steps, parallelism, preferred batching, etc.).", "Required": false } ] }Discussion
Comments and conversation will live here.