Top 10 Best Refinery Planning Software of 2026

GITNUXSOFTWARE ADVICE

Supply Chain In Industry

Top 10 Best Refinery Planning Software of 2026

Top 10 refinery planning software ranked for scheduling and supply-chain planning, with technical comparisons of Aspen PIMS, AVEVA, and Honeywell.

31 min readUpdated AI-verified · Expert reviewed
How we ranked these tools
01Feature Verification

Core product claims cross-referenced against official documentation, changelogs, and independent technical reviews.

02Multimedia Review Aggregation

Analyzed video reviews and hundreds of written evaluations to capture real-world user experiences with each tool.

03Synthetic User Modeling

AI persona simulations modeled how different user types would experience each tool across common use cases and workflows.

04Human Editorial Review

Final rankings reviewed and approved by our editorial team with authority to override AI-generated scores based on domain expertise.

Read our full methodology →

Score: Features 40% · Ease 30% · Value 30%

Gitnux may earn a commission through links on this page — this does not influence rankings. Editorial policy

Refinery planning software turns crude selection, unit yields, and product slates into solvable optimization models and operational schedules, then links results to supply coordination. This ranking targets analysts and plant technical teams who need defensible comparisons across LP and mixed-integer approaches, with integration depth and configuration control as the key decision tradeoff.

Aspen PIMS is the safest pick when refinery planning teams need repeatable, LP-ready cases with tight stream routing control, whereas Mosek Refinery Planner fits engineering groups that want constraint-driven refinery models via explicit optimization and if you need a cheaper entry, KBC PRISM is a strong specialist alt when governed routing and dispatch-ready outputs matter.

Editor’s top 3 picks

Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.

Editor pick
1

Aspen PIMS

Aspen PIMS integrates Aspen HYSYS stream property context into planning models to reduce property mismatch.

Built for fits when refinery planning teams need repeatable LP-ready cases with tight stream routing control..

2

AVEVA Spiral Suite

Editor pick

Its equation-driven planning workflow connects refinery constraints into scenario runs that feed scheduling and dispatch coordination outputs.

Built for fits when refinery planning teams need configurable planning logic and automated scenario runs into execution systems..

3

Mosek Refinery Planner

Editor pick

Refinery LP modeling centered on MOSEK engine integration for constraint-driven plan generation.

Built for fits when engineering teams need repeatable refinery LP planning driven by explicit constraints..

Comparison Table

1
Aspen PIMSBest overall
enterprise
9.1/10
Overall
2
8.8/10
Overall
3
8.5/10
Overall
4
vertical specialist
8.2/10
Overall
5
vertical specialist
7.9/10
Overall
6
enterprise
7.6/10
Overall
7
7.4/10
Overall
8
vertical specialist
7.0/10
Overall
9
vertical specialist
6.7/10
Overall
10
vertical specialist
6.4/10
Overall
#1

Aspen PIMS

enterprise

Linear programming-based refinery planning and optimization system used across the petroleum industry for feedstock selection, product slate optimization, and margin maximization.

9.1/10
Overall
Features9.1/10
Ease of Use9.3/10
Value8.9/10
Standout feature

Aspen PIMS integrates Aspen HYSYS stream property context into planning models to reduce property mismatch.

Aspen PIMS is built for refinery planners who need equation-based production planning across multiple process units, with explicit handling of constraints and scenario variants. The workflow typically starts from a refinery data model, then adds economics and routing rules to build an optimization-ready representation and produces dispatch-ready outputs. Integration depth is a key differentiator because Aspen PIMS connects to Aspen HYSYS for thermodynamic and stream property context instead of requiring manual property replication.

A tradeoff is that credible results depend on disciplined model configuration because routing, constraints, and yield behavior must match plant practice. Aspen PIMS fits best when planning teams run repeated day-ahead and week-ahead cases with frequent crude changes, unit limits, and turnaround schedules that must stay consistent across reports.

Pros
  • +Strong refinery-wide material balance planning with routing and constraint handling
  • +Direct Aspen HYSYS integration reduces stream property rework
  • +Scenario analysis supports repeated planning cycles with varied assumptions
  • +Automated reporting outputs align plan decisions to operations workflows
Cons
  • Model configuration and constraint setup require engineering-level governance discipline
  • Complex solver configurations can slow case iteration for ad hoc questions
  • Some turnaround and dispatch details need external integration to be fully closed-loop
  • Spreadsheet-style adjustments are limited for deeper equation-level constraints
Use scenarios
  • Refinery planning teams

    Day-ahead crude and unit planning

    Faster, consistent daily cases

  • Optimization analysts

    Blend and cutpoint optimization studies

    More comparable scenario decisions

Show 2 more scenarios
  • Process engineers

    Turnaround-aware unit constraint updates

    Fewer plan-to-shutdown conflicts

    Maintain unit availability and routing constraints so planning remains aligned with planned maintenance windows.

  • Refinery operations coordinators

    Plan-to-dispatch handoff workflows

    Clearer operating directives

    Use structured planning outputs and reporting to coordinate dispatch and operational follow-up actions.

Best for: Fits when refinery planning teams need repeatable LP-ready cases with tight stream routing control.

#2

AVEVA Spiral Suite

enterprise

Integrated planning and scheduling platform for refineries and petrochemical complexes combining crude oil evaluation, production planning, and blend optimization.

8.8/10
Overall
Features8.8/10
Ease of Use9.0/10
Value8.6/10
Standout feature

Its equation-driven planning workflow connects refinery constraints into scenario runs that feed scheduling and dispatch coordination outputs.

AVEVA Spiral Suite is used for refinery planning where planners need controlled model configuration across streams, units, and constraints rather than spreadsheet-driven trial-and-error. The workflow supports iterative scenario analysis for scheduling and supply planning, then produces planning outputs that operations can track through dispatch coordination. The software’s strongest fit appears when teams manage consistent process definitions and repeatable case runs across multiple planning cycles.

A key tradeoff is that model configuration depth and integration scope require governance discipline to keep scenarios repeatable when personnel or assumptions change. Spiral Suite fits best when a refinery already has upstream lab data pipelines and downstream production reporting dependencies, because the planning outputs must remain consistent across planning, scheduling, and execution.

Pros
  • +Equation-based planning supports structured refinery constraints and repeatable scenarios
  • +Extensibility and API enable automation from model setup through reporting outputs
  • +Turnaround-aware planning inputs support unit-level schedule cases
  • +Dispatch-oriented planning outputs align with operations coordination needs
Cons
  • Model configuration depth increases onboarding time for new planners
  • Advanced workflows depend on disciplined scenario management practices
  • Integration efforts can require refinery-specific mapping for downstream systems
  • Large model runs can raise runtime and testing overhead during frequent edits
Use scenarios
  • Planning engineers

    Run constrained planning scenarios

    Repeatable planning cases

  • Refinery scheduling teams

    Incorporate turnaround schedules

    Fewer schedule conflicts

Show 2 more scenarios
  • Process engineer teams

    Optimize blend and routing logic

    Consistent spec compliance

    Engineers maintain blend and routing parameters and rerun cases when assays and specs change.

  • Operations coordinators

    Coordinate dispatch and reporting

    Tighter plan execution

    Coordinators use planning outputs to drive dispatch coordination and align production reporting with plans.

Best for: Fits when refinery planning teams need configurable planning logic and automated scenario runs into execution systems.

#3

Mosek Refinery Planner

API-first

Optimization platform used for large-scale linear and mixed-integer refinery planning models.

8.5/10
Overall
Features8.7/10
Ease of Use8.4/10
Value8.3/10
Standout feature

Refinery LP modeling centered on MOSEK engine integration for constraint-driven plan generation.

Mosek Refinery Planner is designed around an optimization workflow where refinerywide constraints and economics become a solvable LP formulation. It targets blend and cutpoint decisions by using refinery-specific relationships from process inputs, then uses the LP solution to produce schedules and recommended stream assignments. Integration depth depends on how refinery teams structure their refinery information system interfaces, since configuration and data mapping work still sit outside the core optimizer. Teams typically use it when they need consistent equation-driven planning outputs rather than a spreadsheet-driven what-if loop.

A practical tradeoff is that governance over model configuration and constraint completeness becomes a core responsibility for engineering teams. Failure modes show up as infeasible or degenerate solutions when unit logic, stream constraints, or economics drivers are incomplete. A common usage situation is running recurring planning cycles for unit availability and feed slate decisions where dispatch coordination and subsequent reporting rely on stable output structure.

Pros
  • +Solver-first LP formulation produces consistent refinerywide optimization outputs
  • +Supports refinery stream routing and cutpoint decisions within one workflow
  • +Scenario runs support comparative planning for operating horizon options
  • +Deterministic plan generation fits recurring planning cycles
Cons
  • Model configuration effort shifts to process and planning engineers
  • Spreadsheet-centric workflows require careful data mapping around imports and exports
  • Complex refinery constraint sets can increase cycle time to converge
Use scenarios
  • Refinery planning engineers

    Crude slate and blend recommendation runs

    Consistent blend recommendations

  • Process engineers

    Unit yield logic and stream constraints updates

    Reduced manual rework

Show 1 more scenario
  • Planning system integrators

    Refinery information system data handoffs

    Fewer interface mismatches

    Maps planning inputs into exportable outputs for downstream reporting and coordination workflows.

Best for: Fits when engineering teams need repeatable refinery LP planning driven by explicit constraints.

#4

Haverly H/PLAN

vertical specialist

Refinery planning system using linear and mixed-integer programming for crude selection, production planning, and distribution optimization.

8.2/10
Overall
Features8.2/10
Ease of Use8.0/10
Value8.4/10
Standout feature

Worklist generation ties equation-based planning results to dispatch coordination artifacts without separate spreadsheet rebuilding.

Haverly H/PLAN is refinery planning software focused on refinery-wide scheduling and material flow coordination across process constraints. It supports equation-driven planning workflows for crude and product balancing, then moves into dispatch-ready worklists tied to operational parameters.

H/PLAN also emphasizes scenario handling so planners can compare deterministic production outcomes and constraint impacts. The solution is designed to fit refinery ecosystems that already have assay, routing, and reporting pipelines rather than replacing them end-to-end.

Pros
  • +Scenario comparison supports planner tradeoffs with constraint-aware outputs
  • +Planning-to-dispatch worklists reduce manual handoffs to operations teams
  • +Refinery-wide material balance emphasis fits planning around actual stream flows
  • +Spreadsheet import and export workflows fit existing refinery data handovers
Cons
  • Model setup requires governance discipline for assays, units, and constraint definitions
  • Nonlinear blend property correlation depth may lag advanced solver ecosystems

Best for: Fits when refinery planners need constraint-aware schedules and material balance outputs aligned to operations workflows.

#5

KBC PRISM

vertical specialist

Refinery planning and optimization software combining LP modeling with KBC's process simulation and consulting expertise for margin improvement.

7.9/10
Overall
Features7.7/10
Ease of Use8.0/10
Value8.1/10
Standout feature

Unit yield modeling tied directly to stream routing inside coordinated refinery planning runs.

KBC PRISM produces refinery planning outputs by combining unit yield modeling, stream routing, and scheduling constraints into coordinated planning scenarios. It supports equation-based planning workflows where planners can generate deterministic schedules and material balance results for dispatch and process coordination use.

The solution is geared toward scenario analysis with configurable economics drivers and measurable planning outputs for refinery-wide studies. Integration work focuses on connecting refinery data sources and operational systems so planning runs can be tied to operational dispatch and reporting.

Pros
  • +Refinery-wide scheduling and routing constraints in one coordinated run
  • +Scenario analysis supports repeatable studies across planning assumptions
  • +Configurable economics drivers for cost and margin sensitive decisions
  • +Planning outputs connect to refinery reporting and operational coordination workflows
Cons
  • Setup requires careful model governance across units, streams, and constraints
  • Automation and API depth are less visible than major scheduling suites

Best for: Fits when refinery planning teams need coordinated scheduling, routing, and dispatch-ready scenario outputs with governed configuration.

#6

PIMS-AO

enterprise

Refinery planning and scheduling software for LP-based optimization, supply coordination, and margin analysis.

7.6/10
Overall
Features8.0/10
Ease of Use7.3/10
Value7.3/10
Standout feature

Planning case execution that ties refinery constraint sets to economics drivers for schedule-ready optimization outputs.

PIMS-AO is a Hexagon refinery planning application that focuses on refinery-wide optimization using refinery-specific data such as assays, yields, and economics drivers. It supports planning workflows that connect crude selection, blending and cutpoint decisions, and process unit constraints to produce schedule-ready outputs for downstream coordination.

The solution is designed to fit into refinery information system landscapes through integration patterns commonly used around Hexagon process and operations data flows. Scenario runs can be used to compare deterministic outcomes across planning cases without converting work into custom spreadsheets.

Pros
  • +Refinery-centric optimization inputs and constraint handling
  • +Scenario comparison for planning cases without custom modeling each run
  • +Integration-ready workflow outputs for dispatch and coordination
  • +Use of refinery economics drivers to steer LP-based results
Cons
  • Works best when upstream data like assays and yields are well maintained
  • Automation depends on integration approach rather than a native app-per-task UI
  • Requires governance to keep economics and constraints consistent across cases
  • Limited evidence of direct extension for custom solver logic in standard deployments

Best for: Fits when refinery planning teams need repeatable crude and scheduling optimization with scenario-based comparisons.

#7

Refinery Planning and Scheduling

vertical specialist

Digital refinery planning and scheduling solution for production planning, yield optimization, and inventory visibility.

7.4/10
Overall
Features7.2/10
Ease of Use7.5/10
Value7.4/10
Standout feature

Scheduling workflow design that emphasizes dispatch coordination and operational handoff from planning runs.

Refinery Planning and Scheduling from Infosys focuses on refinery planning workflows tied to scheduling and dispatch coordination rather than generic production tracking. Core capabilities include scenario planning with constraints, planning data preparation for refinery-wide studies, and integration hooks for refinery information system handoffs.

Automation is centered on repeatable planning runs and configurable work patterns that support planner and operations coordinator handoff. Governance is supported through enterprise integration controls that fit refinery IT change management and controlled access.

Pros
  • +Scheduling and dispatch-oriented workflow supports refinery operations handoff
  • +Scenario reruns support what-if analysis across planning constraints
  • +Integration orientation supports refinery information system data exchange
  • +Refinery planning workflow favors controlled, repeatable execution
Cons
  • Higher modeling effort is needed to align constraints with unit and routing logic
  • External integration dependencies can slow first end-to-end deployments

Best for: Fits when refinery teams need controlled scenario runs and scheduling-focused planning workflows with IT governance.

#8

GAMS

vertical specialist

General Algebraic Modeling System for large-scale linear, nonlinear, and mixed-integer optimization problems used in refinery planning.

7.0/10
Overall
Features7.0/10
Ease of Use6.8/10
Value7.3/10
Standout feature

Model-driven refinery planning where constraint logic and objectives are coded as equations and then compiled into solver-ready matrices.

GAMS provides refinery planning capabilities built on equation-based optimization with a solver workflow driven by model logic rather than fixed heuristics. It supports refinery-wide material balance modeling, blend optimization, and refinery scheduling use cases through configurable sets of constraints and objective functions.

Its distinct strength is extensibility through model formulation, data mapping, and automation hooks that can generate linear programming matrix forms for downstream solvers. In practice, the fit is strongest when planning logic must be expressed precisely and reused across scenarios and what-if studies.

Pros
  • +Equation-based optimization modeling supports refinery-specific constraint systems
  • +Blend optimization can use nonlinear property correlation formulas in the model
  • +Automation can regenerate planning cases from model and data inputs
  • +Refinery scheduling logic can be encoded as constraint sets and objective terms
Cons
  • Operational deployment requires stronger engineering involvement than UI-led tools
  • Scenario management and planner collaboration need external workflow tooling
  • Prebuilt refinery scheduling interfaces are limited compared with dedicated suites
  • Integration depth depends on custom data mapping for refinery information system exports

Best for: Fits when refinery planning requires equation-based control and repeatable scenario generation with custom constraints.

#9

LINDO Systems

vertical specialist

Optimization software suite for linear, nonlinear, stochastic, and integer programming applied to refinery planning problems.

6.7/10
Overall
Features6.7/10
Ease of Use6.8/10
Value6.7/10
Standout feature

LINGO’s model-authoring approach that ties solver settings directly to mathematical structure for refinery constraint tuning.

LINDO Systems helps refineries build and solve equation-based optimization models for planning and scheduling using LINGO and related solvers. The product focus centers on LP and mixed-integer optimization with model-driven workflows that map refinery constraints into a math model.

It supports refinery planning tasks like unit turnaround timing, stream routing logic, and blend or product assignment through scenario-based runs and constraint formulation. LINDO’s distinct strength is giving model authors control over the optimization structure, including custom nonlinear representations and solver settings that affect throughput and convergence.

Pros
  • +Model-first workflow for encoding refinery constraints and objective tradeoffs
  • +Mixed-integer optimization support for unit status and operational decision logic
  • +Scenario runs support repeatable comparisons for planning variants
  • +Solver configuration control for convergence behavior and performance tuning
Cons
  • Refinery-specific UX is limited compared with dedicated refinery planning suites
  • Complex models demand careful formulation to avoid infeasibility and slow solves
  • Integration depth with refinery information systems often requires custom scripting
  • Governance features like audit logs and role permissions can be minimal by default

Best for: Fits when refinery teams need equation-based optimization control with custom constraints over packaged scheduling.

#10

Quorum Planning & Scheduling

vertical specialist

Quorum Planning & Scheduling manages production plans, operational schedules, and energy supply chain decisions.

6.4/10
Overall
Features6.3/10
Ease of Use6.7/10
Value6.4/10
Standout feature

Dispatch coordination outputs are generated from the same planning scenarios used for scheduling and reporting.

Quorum Planning & Scheduling is used for refinery planning work where scheduling, material planning, and reporting must align to the same operational context. It supports equation-driven planning workflows with configuration for refinery economics drivers and constraint sets.

Quorum also supports scenario analysis and dispatch coordination outputs tied to operational roles. Its governance model is built for multi-role planning teams that need controlled scenario changes and traceable results.

Pros
  • +Scenario runs support deterministic planning with repeatable constraint sets
  • +Dispatch coordination outputs align planners and operations coordinators
  • +Refinery economics driver configuration helps tune objective behavior
  • +Audit-focused change trails support planner role handoffs
Cons
  • Extensibility depends on provided integration points rather than open scripting
  • Refinery-wide model configuration requires substantial upfront governance
  • Nonlinear blend property correlation setup can be time-consuming for teams
  • Spreadsheet exchange is available but adds manual QA steps

Best for: Fits when refinery scheduling and material planning must share scenarios across planner and operations roles.

Conclusion

After evaluating 10 supply chain in industry, Aspen PIMS stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.

Our Top Pick
Aspen PIMS

Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.

How to Choose the Right refinery planning software

Refinery planning software coordinates constrained LP or equation-based models that turn refinery-wide inputs into scenario runs for scheduling, stream routing, and dispatch coordination across planner and operations teams.

This guide covers Aspen PIMS, AVEVA Spiral Suite, and the wider set of refinery planning tools including AspenTech, Honeywell-aligned planning workflows where those fit refinery planning needs, plus tools such as Mosek Refinery Planner, Haverly H/PLAN, KBC PRISM, PIMS-AO, Refinery Planning and Scheduling, GAMS, LINDO Systems, and Quorum Planning & Scheduling.

Refinery planning software for scenario-based LP optimization, material balance, and scheduling handoff

Refinery planning software builds refinery constraint systems that model unit throughput limits, stream routing, yield and cutpoint decisions, and refinery-wide material balance so teams can generate repeatable scenarios.

In practice, Aspen PIMS focuses on integrating Aspen HYSYS stream property context into planning models so planning cases reduce stream property mismatch, while AVEVA Spiral Suite uses an equation-driven workflow that connects refinery constraints into scenario runs feeding scheduling and dispatch coordination outputs.

These tools also differ in where automation and control sit, such as scenario-to-worklist generation in Haverly H/PLAN versus solver-first formulation in Mosek Refinery Planner versus model-compilation into solver-ready matrices in GAMS.

Refinery planning features that change solver control and execution handoff

Refinery planning software matters most where constraint logic becomes scenario outputs that operations teams can act on. The feature set should cover stream routing and unit throughput constraints together, or teams lose traceability between the plan and dispatch behavior.

  • Integration between stream properties and planning constraints

    Aspen PIMS integrates Aspen HYSYS stream property context into planning models to reduce stream property mismatch during routing and plan runs. This makes it easier to keep stream assumptions aligned between process simulation and LP-ready planning cases versus tools that treat stream properties as external inputs.

  • Equation-driven scenario execution that feeds scheduling and dispatch

    AVEVA Spiral Suite uses an equation-driven planning workflow that connects refinery constraints into scenario runs feeding scheduling and dispatch coordination outputs. Haverly H/PLAN instead ties equation-based planning results to dispatch worklist generation without requiring separate spreadsheet rebuilding.

  • Solver-first refinery LP formulation for repeatable constraint outcomes

    Mosek Refinery Planner centers refinery LP modeling on MOSEK engine integration for constraint-driven plan generation. GAMS takes a model-driven approach where equation logic is compiled into solver-ready matrices, so the workflow favors engineering control over UI-led planning iterations.

  • Routing, yield modeling, and scheduling-ready outputs in a single run

    KBC PRISM ties unit yield modeling directly to stream routing inside coordinated refinery planning runs to produce dispatch-ready scenario outputs. KBC PRISM is built for governed configuration across units, streams, and constraints, while PIMS-AO focuses on refinery constraint sets tied to economics drivers for schedule-ready optimization outputs.

  • Worklist and dispatch artifacts generated from planning scenarios

    Haverly H/PLAN generates planning-to-dispatch worklists from planning results so planners and operations avoid manual handoffs. Quorum Planning & Scheduling also generates dispatch coordination outputs from the same planning scenarios used for scheduling and reporting, which aligns planner and operations coordinators on identical scenario runs.

How to choose refinery planning software based on workflow philosophy

Teams should choose based on how the tool turns refinery constraints into scenario outputs and how it drives outputs into dispatch and scheduling artifacts. The key split is between equation-driven workflows that execute scenarios directly versus solver-first or model-compile workflows that center engineering formulation and matrix generation.

  • Decide whether planning control lives in equations, formulation, or scenario execution

    If planning control should run through an equation-driven scenario workflow, AVEVA Spiral Suite connects refinery constraints into scenario runs that feed scheduling and dispatch coordination outputs. If control should start from solver-first LP formulation, Mosek Refinery Planner focuses on MOSEK engine integration for constraint-driven plan generation.

  • Select an integration path that reduces rework between simulation inputs and planning cases

    If the refinery uses Aspen HYSYS stream properties as the source of truth, Aspen PIMS integrates Aspen HYSYS stream property context into planning models to reduce stream property rework. If stream properties are maintained elsewhere, tools like PIMS-AO still support refinery constraint handling but work best when upstream assays and yields are kept current.

  • Confirm whether dispatch-ready artifacts are generated in-tool or produced externally

    If operations handoff requires direct dispatch worklist generation from planning runs, Haverly H/PLAN ties worklist generation to equation-based planning results. If dispatch coordination must align with the exact scenario set used for scheduling and reporting, Quorum Planning & Scheduling generates dispatch outputs from the same planning scenarios.

  • Match unit yield and stream routing coupling to the refinery modeling responsibility split

    If unit yield modeling must be coupled directly to stream routing within coordinated runs, KBC PRISM supports refinery-wide scheduling and routing constraints in one coordinated run. If the model needs to be tied to economics driver configuration for schedule-ready optimization outputs, PIMS-AO ties planning case execution to economics drivers and scenario comparisons.

  • Choose an engineering governance posture for model configuration and scenario management

    If deeper model configuration and constraint setup is acceptable for repeatable scenarios, Aspen PIMS and AVEVA Spiral Suite both require engineering-level governance discipline for constraint and model configuration. If model setup governance will be light, GAMS and LINDO Systems require stronger engineering involvement for operational deployment and careful formulation to avoid infeasibility and slow solves.

  • Pick a workflow that fits ad hoc planning iteration speed needs

    If teams need rapid ad hoc iteration, avoid tools whose complex solver configurations can slow case iteration, which is a tradeoff called out for Aspen PIMS. If teams can standardize scenario runs through equation-driven scenario execution, AVEVA Spiral Suite emphasizes configurable planning logic and automated scenario runs into execution systems.

Who refinery scheduling and supply chain planning teams should assign to each workflow

Refinery planning software fits roles that own constraint logic, stream routing assumptions, and the path from scenario outputs to operations handoff. The strongest match depends on whether the organization runs planning cases from simulation context, from encoded equations, or from solver-first LP formulations.

  • Refinery planning leads coordinating constrained planning cases and routing decisions

    Aspen PIMS fits teams that need repeatable LP-ready cases with tight stream routing control and reduced property mismatch through Aspen HYSYS stream property context integration.

  • Planning engineers building equation-driven constraint logic that must feed execution systems

    AVEVA Spiral Suite fits teams that want configurable planning logic where equation-driven scenario runs feed scheduling and dispatch coordination outputs, with extensibility and API automation from model setup through reporting outputs.

  • Operations and dispatch coordinators who need dispatch worklists generated from the same planning scenarios

    Haverly H/PLAN and Quorum Planning & Scheduling both focus on aligning planning outcomes with operations handoff by generating worklists or dispatch outputs from planning scenarios rather than requiring separate spreadsheet rebuilding.

  • Process and planning engineering teams responsible for model governance and solver feasibility

    Mosek Refinery Planner and GAMS fit engineering-led workflows where constraint-driven plan generation and solver-ready matrix compilation depend on disciplined model configuration and careful scenario management.

Common procurement and implementation pitfalls for refinery planning software

Many implementation failures come from mismatched expectations about where model configuration and governance discipline must live. Teams also underestimate the effort required to keep scenario management consistent across planner reruns and operational dispatch artifacts.

  • Assuming refinery-wide routing and balance constraints can be adopted without engineering governance for assays, units, and constraint definitions

    Haverly H/PLAN explicitly calls out that model setup requires governance discipline for assays, units, and constraint definitions, so the rollout plan must include ownership for those inputs.

  • Selecting a tool for equation-driven planning without a scenario management process that prevents planners from generating inconsistent dispatch outputs

    AVEVA Spiral Suite notes that advanced workflows depend on disciplined scenario management practices, so governance must cover scenario lifecycle, rerun rules, and output mapping.

  • Building workflows around spreadsheets and then underestimating the data mapping effort required for LP-ready refinery models

    Mosek Refinery Planner warns that spreadsheet-centric workflows require careful data mapping around imports and exports, so migration scope must include mapping validation and repeatability checks.

  • Expecting automation depth and integration points to match major scheduling suites without validating the available integration surface

    Quorum Planning & Scheduling states that extensibility depends on provided integration points rather than open scripting, so procurement should verify that the required integrations exist for planner and operations systems.

How We Selected and Ranked These Tools

We evaluated Aspen PIMS, AVEVA Spiral Suite, and the other tools by scoring refinery planning capability across constraint handling, planning-to-output workflow fit, and dispatch coordination alignment. Features accounted for 40% of the score, ease/value each accounted for 30% of the score.

Aspen PIMS separated itself by integrating Aspen HYSYS stream property context directly into planning models, which reduces stream property rework during repeatable LP-ready case generation. AVEVA Spiral Suite ranked highly for equation-driven planning workflows that produce scenario runs feeding scheduling and dispatch coordination outputs, with extensibility and API support spanning model setup through reporting outputs.

Frequently Asked Questions About refinery planning software

How does Aspen PIMS generate LP-ready inputs for refinery-wide scheduling and material balance?
Aspen PIMS converts refinery models and operating constraints into LP-ready scheduling and material balance inputs. It coordinates crude and unit planning logic through stream routing, utility balance, and economics driver configuration, then runs deterministic scenario analysis.
What is the practical difference between equation-based planning workflows in AVEVA Spiral Suite and solver-first workflows in Mosek Refinery Planner?
AVEVA Spiral Suite connects refinery constraints through an equation-driven planning workflow that outputs scheduling and dispatch coordination artifacts. Mosek Refinery Planner centers on a solver-first workflow around the MOSEK optimization engine, which changes how constraint logic is represented and tuned during plan generation.
Which tools support importing planning data from existing refinery pipelines without forcing a full re-platform?
Haverly H/PLAN is designed to fit refinery ecosystems that already have assay, routing, and reporting pipelines, with equation-driven planning feeding dispatch-ready worklists. Mosek Refinery Planner also supports fitting into existing toolchains through import and export of planning data.
How do integrations and APIs affect workflow automation from planning to dispatch and reporting?
AVEVA Spiral Suite exposes an API surface and extensibility options that map planning results into downstream refinery systems. Quorum Planning & Scheduling aligns scheduling, material planning, and reporting to the same operational context so scenario changes propagate consistently across planner and operations workflows.
When does refinery scheduling require turnaround planning and dispatch timing controls rather than only material balance?
LINDO Systems supports unit turnaround timing as part of its equation-based optimization model inputs. AVEVA Spiral Suite also includes turnaround planning inputs and production reporting outputs tied to operations execution in the same planning workflow.
What breaks if a refinery planning process needs tight control over stream property context across planning and operations?
Aspen PIMS reduces property mismatch by integrating Aspen HYSYS stream property context into planning models. Without that kind of context alignment, planners often need manual recalibration of stream attributes before running scenario analysis for refinery scheduling and supply chain planning.
How should security and access controls be evaluated for multi-role planning teams using refinery scenarios?
Quorum Planning & Scheduling provides a governance model built for multi-role planning teams that need controlled scenario changes and traceable results. Refinery Planning and Scheduling from Infosys adds enterprise integration controls designed to match refinery IT change management and controlled access for scenario runs and scheduling handoffs.
Which tools generate worklists or dispatch artifacts directly from the same planning equations used for scheduling?
Haverly H/PLAN generates dispatch-ready worklists from equation-based planning results without separate spreadsheet rebuilding. Quorum Planning & Scheduling also produces dispatch coordination outputs from the same planning scenarios used for scheduling and reporting.
How does data migration typically show up during onboarding for refinery planners using constraint-rich models?
Aspen PIMS expects LP-ready scheduling and material balance inputs that reflect stream routing, utility balance, and economics driver configuration, so migrating existing models often means mapping those elements into its planning inputs. AVEVA Spiral Suite relies on configurable planning logic and scenario comparison workflows, so onboarding usually focuses on recreating constraint sets and integration mappings for automated results handoff.
What tradeoff exists between using GAMS model extensibility and using packaged refinery modeling workflows in KBC PRISM?
GAMS supports extensibility through model formulation and data mapping that can compile into solver-ready linear programming matrix forms for downstream solvers. KBC PRISM provides coordinated refinery planning where unit yield modeling is tied directly to stream routing inside coordinated planning runs, so teams get governed workflows but less freedom in how the math model is expressed.

Tools reviewed

Primary sources checked during evaluation.

Referenced in the comparison table and product reviews above.

Logos provided by Logo.dev

Keep exploring

FOR SOFTWARE VENDORS

Not on this list? Let’s fix that.

Our best-of pages are how many teams discover and compare tools in this space. If you think your product belongs in this lineup, we’d like to hear from you—we’ll walk you through fit and what an editorial entry looks like.

Apply for a Listing

WHAT THIS INCLUDES

  • Where buyers compare

    Readers come to these pages to shortlist software—your product shows up in that moment, not in a random sidebar.

  • Editorial write-up

    We describe your product in our own words and check the facts before anything goes live.

  • On-page brand presence

    You appear in the roundup the same way as other tools we cover: name, positioning, and a clear next step for readers who want to learn more.

  • Kept up to date

    We refresh lists on a regular rhythm so the category page stays useful as products and pricing change.