1. What is ProductMixer?
ProductMixer is a refinery product blending component in the Petroleum Refining Library that combines multiple process streams into finished products using either automatic LP-based optimization or user-defined blending strategies. It supports refinery simulation, production planning, and digital twin applications.
2. How does ProductMixer work?
ProductMixer collects the current state of all incoming streams, evaluates product specifications and operating constraints, calculates the blend composition, distributes material between accepted and rejected streams, and updates the simulation with the new flow distribution.
3. What operating modes does ProductMixer support?
ProductMixer supports Automatic and Manual blending modes. Automatic Mode generates the optimization model internally, while Manual Mode allows users to define their own objective function, variables, and constraints.
4. Does ProductMixer use linear programming?
Yes. In Automatic Mode, ProductMixer automatically formulates and solves a linear programming (LP) model to determine the optimal blend while satisfying all quality and operational constraints.
5. When is the blend recalculated?
The blend is recalculated automatically when inlet flow rates, product specifications, or other operating conditions change. Users can also trigger recalculation manually through the runtime API.
6. What quality properties can ProductMixer optimize?
ProductMixer supports any linear blending property, including octane number, sulfur content, density, Reid Vapor Pressure (RVP), cetane number, benzene concentration, aromatics, oxygen content, and refinery-specific quality indicators.
7. What happens if a blend cannot satisfy all quality constraints?
If no feasible solution exists, ProductMixer automatically prevents the production of an invalid blend. Depending on the operating mode and optimization strategy, incoming streams are redirected to residual outputs or the optimization minimizes quality violations using a penalty-based objective.
8. What are accepted and rejected streams?
Accepted streams are the portions of inlet flows used to produce the final product. Rejected streams are diverted to dedicated residual outlets because including them would violate quality constraints or reduce the optimization objective.
9. Can ProductMixer minimize additive consumption?
Yes. ProductMixer supports optimization objectives that minimize balancing additive consumption while continuing to produce products that satisfy the required quality specifications.
10. Can ProductMixer be integrated into a refinery digital twin?
Yes. ProductMixer is designed for refinery digital twins and integrates directly with simulation models, automatically adapting the blend to changing process conditions throughout the simulation.
11. What statistics does ProductMixer provide?
ProductMixer reports comprehensive performance metrics, including inlet flows, product flows, residual streams, product quality indicators, additive consumption, constraint evaluation, and optimization results through a unified runtime API.
12. What refinery applications is ProductMixer suitable for?
Typical applications include gasoline blending, diesel blending, intermediate product blending, refinery production planning, optimization studies, and refinery digital twin simulations.
13. Does ProductMixer support custom optimization models?
Yes. In Manual Mode, users can define their own optimization model, including decision variables, objective functions, and linear constraints, enabling ProductMixer to solve virtually any refinery blending optimization problem.
14. Does ProductMixer support runtime control?
Yes. The runtime API allows engineers to switch operating modes, update product specifications, modify additive settings, trigger recalculation, and integrate ProductMixer with other Petroleum Refining Library components during simulation.
15. Which optimization objectives are supported?
ProductMixer supports optimization objectives such as maximum product production and minimum additive consumption. The objective can also be changed dynamically during simulation to match current operational requirements.