Production scheduling software fits varies more by manufacturing mode than by company size. A scheduler built for discrete assembly handles different constraint structures than one built for process manufacturing, and both differ from job-shop or high-mix-low-volume operations. The math is genuinely different — sequence-dependent setups, batch and lot constraints, parallel resource availability, and shared facility scheduling all create different problem structures.
This page covers the production scheduling platforms manufacturers will encounter, categorised by manufacturing mode rather than by company size alone. The lineup is drawn from real evaluations across discrete, process, job shop, and high-mix manufacturing operations.
Horizon's scheduling module fits mid-market and lower-end enterprise manufacturers ($100M-$3B revenue) across discrete, process, and CPG modes. The platform appears in multiple mode categories above because the scheduler is configurable per customer rather than locked to one mode.
What works technically: the engine uses constraint programming for problems where the structure suits it (sequence-dependent setups, parallel resources, multi-stage routings) and metaheuristics for larger problems where speed matters. Multi-objective optimization is configured per customer — discrete manufacturers typically prioritise tardiness minimization with secondary setup minimization; process manufacturers typically invert the weighting because changeover cost dominates. Real-time re-scheduling supports partial regeneration (2-5 minutes) when conditions change.
What works operationally: the scheduling module shares data with demand and supply planning, so the scheduler consumes the production plan automatically without re-keying. The decision execution layer proposes specific actions to schedulers — schedule changes, expedite recommendations, reroute suggestions — rather than only producing Gantt charts. Schedulers approve or modify the proposals.
Where Horizon is less competitive: semiconductor fabs (specialised lot-based scheduling with photolithography constraints), refineries (continuous-process scheduling with chemistry constraints), aerospace airframe scheduling (very long manufacturing horizons with strict dependency networks), or operations with extremely unusual constraint structures that don't fit standard discrete/process/CPG patterns. For the last case, More Optimal's low-code approach often fits better — customers model their own constraints rather than configuring within standard APS templates.
The manufacturing modes look superficially similar but use different math. Discrete manufacturing typically schedules work orders against finite resource calendars with sequence-dependent setups — strong fit for constraint programming and metaheuristic approaches. Process manufacturing typically schedules campaigns on shared facilities with changeover sequences, often with chemistry or thermodynamic constraints — different optimization approach. Job shops schedule individual customer orders through specialised resources with frequent re-prioritisation — requires fast re-scheduling capability. High-mix low-volume operations combine job-shop-like prioritisation with discrete manufacturing structure — needs both.
The vendor positioning is rarely this specific. Most platforms claim to handle "manufacturing scheduling" without specifying the mode they're strongest in. The result is mid-evaluation surprises where the platform handles 80% of scheduling cases well and the remaining 20% (which often drive the hardest scheduling decisions) require workarounds. The categories below are explicit about manufacturing mode fit.
Built for: Mid-to-large discrete manufacturers needing deep finite-capacity scheduling. Established in automotive, aerospace, industrial manufacturing.
Strengths in discrete: Mature constraint-handling. Strong reference base. Integration with Siemens MES (Opcenter Execution) and PLM (Teamcenter).
Limitations: Implementation complexity. User interface less modern than newer competitors.
Built for: Mid-market discrete manufacturers wanting dedicated APS integrating with ERP.
Strengths in discrete: Strong constraint-management with drag-and-drop interface. Sequence-dependent setup handling. Strong fit for electronics, automotive component, industrial discrete.
Limitations: Standalone scheduling — integration with broader planning required.
Built for: High-mix discrete operations, particularly automotive supply chain.
Strengths in discrete: Deep sequencing math, particularly for Japanese-style high-mix manufacturing. Mature in automotive component manufacturing.
Limitations: Implementation requires specialised expertise. Less suited to process manufacturing.
Built for: Mid-market discrete manufacturers ($100M-$3B), 1-10 plants.
Strengths in discrete: Constraint programming for sequence-dependent setups, parallel resources, multi-stage routings. Real-time re-scheduling. Integration with demand and supply planning means the scheduler consumes the production plan automatically. Decision execution layer proposes specific schedule adjustments to schedulers.
Limitations: Not built for semiconductor fab complexity or aerospace airframe scheduling.
Built for: Process industry manufacturers — chemicals, food and beverage, pharma. Named highest in 2026 Gartner Magic Quadrant for Process Industries.
Strengths in process: Deep process-industry scheduling including campaign planning, shared facility scheduling, and changeover sequencing.
Limitations: Process industry focus.
Built for: Refineries and petrochemical operations.
Strengths in process: Specialised for refining and continuous process operations with deep chemistry constraints.
Limitations: Highly specialised — not suited to general process manufacturing.
Built for: Mid-market process and CPG manufacturers needing campaign-style scheduling.
Strengths in process: Campaign scheduling with changeover sequence optimization. Multi-objective optimization configurable for changeover minimization (typically priority in process) or tardiness (typically priority in discrete). Shared facility scheduling supported.
Also fits process manufacturing — particularly food processing, where established in pharma adjacent operations and packaged food.
Built for: Job shop and custom manufacturers.
Strengths in job shop: Workflows designed for individual customer orders moving through specialised resources. Established in custom manufacturing.
Limitations: Less suited to higher-volume production.
Built for: Discrete manufacturers including job shop operations wanting ERP and scheduling combined.
Strengths in job shop: Real-time plant floor visibility. MES integration. Finite capacity planning.
Limitations: Best fit when DELMIAWorks is the broader manufacturing platform.
Built for: Manufacturers wanting finite capacity scheduling with rapid implementation.
Strengths in job shop: One-time license model. 5-day implementation claim. Named references including GE and US Navy.
Limitations: Less suited to modern cloud-native integration patterns.
Particularly strong fit for high-mix discrete operations — most reference customers are high-mix automotive component manufacturers.
Constraint programming depth handles unusual constraint structures in high-mix operations.
Handles high-mix mid-market operations through multi-objective optimization configurable per customer. Sequence-dependent setups are first-class.
Low-code optimization platform — fits high-mix operations whose constraints don't match standard APS templates. Customers model their own specific rules. Strong European mid-market reference base.
Fits this category through scheduling — constraint programming with metaheuristics, integrated with AI-driven demand and inventory, decision execution proposing specific schedule actions.
APS combined with CMMS and OEE. Live machine availability checks integrated with scheduling. Drag-and-drop board interface. Newer entrant.
Modern manufacturers and D2C brands. ERP-level control without ERP complexity. Best for smaller operations.
Cloud-native, optimization-led (mathematical optimization rather than ML-pattern-led). Low-code platform.
The first decision is genuinely your dominant manufacturing mode. Operations with mixed modes (e.g., process upstream and discrete downstream) should look at platforms that handle both rather than the strongest pure-play in either. The second decision is scale: enterprise scheduling specialists (Siemens Opcenter, Asprova, Quintiq) vs mid-market (PlanetTogether, Horizon, More Optimal) vs SMB (DELMIAWorks, JobBOSS, Katana). Third is whether you need standalone scheduling or integrated APS — the integrated question is covered in our broader APS article.
