Blending · Trader workflow
Blending what-if scenarios: how Traders pressure-test a blend plan.
This note refers to MaeWest Blending. Before an instruction is sent to an FSO, Traders can run structured what-if checks to see how margin, quality, and component limits move under different assumptions.
The practical question
When a blend looks acceptable on a single pass, the next question is whether it still holds if prices move, component availability changes, or a quality constraint tightens. Without that check, the instruction can be technically valid but commercially weak.
MaeWest Blending supports this decision step by letting Traders compare candidate blends before issuing a signed instruction to vessel operations.
Projected tank quality
Add candidate parcels — component, destination tank, quantity — and the planning surface computes the post-restock quality of each affected tank using the same mass-weighted math the deriver uses after execution. Use a real supplier CoQ if you already hold one, or the component master’s nominal values while you are still shopping.
Change-of-use pivots
Tick Replace tank on any line to model a tank being drained and repurposed to a new component — HSFO → MGO, distillate → residual. The projection uses the incoming parcel(s) only and flags the drain/clean the vessel side will need to arrange.
Fleet capacity & compare
A per-component roll-up shows tanks, capacity and inventory before and after the scenario. Save up to three variants and open Compare to see arrow deltas per component against a common baseline — two purchase strategies, one glance.
Not signed, not audited — until you decide
Scenarios are stored as local JSON under Documents\MaeWest BlendManager\Trader\Scenarios\. Nothing is transmitted to the FSO, nothing is anchored to the hash chain, nothing commits you to a purchase. Trial-and-error is meant to be cheap and reversible.
When one scenario wins, Promote to Issue opens the Issue Restock dialog pre-populated with every line and the Replace-tank flag intact. From that moment the plan is a signed restock instruction like any other — identical downstream.
Why the distinction matters
Cargo Operations and Blending answer different questions. Product Control looks backward across operations to identify recurring deficiencies; Blending what-if analysis looks forward before execution to reduce avoidable commercial and operational risk.
When both perspectives are clear, teams can separate planning decisions from post-operation diagnostics and avoid mixing workflows across product lines.
How MaeWest fits
In MaeWest Blending, scenario comparison is part of instruction readiness: evaluate alternatives, select the most defensible plan, then issue a signed instruction that the FSO can execute and return in a verifiable loop.