Every refinery with an alkylation unit manages the same tension. Acid costs eat into margin, octane targets keep pressing, and the FCC upstream sends whatever olefin composition it produced that shift. Cooling water temperature changes with the season, isobutane availability tightens, and feed contaminants drift in ways that inferential measurements do not always catch.
Each of those variables can be managed on its own. Margin is lost when they move together, because their effects on octane, throughput and acid consumption interact. Alkylation is a clear case of why coordinated setpoints matter in refinery operations.
Why alkylate carries a premium
Finished gasoline is a blend, and alkylate's value comes from what it does not contain. It combines low sulfur, low vapor pressure and high octane without the sulfur or aromatics trade-offs of other blendstocks.
EPA Tier 3 gasoline sulfur standards have raised the value of blendstocks that hold octane while keeping the pool compliant. Hydrotreating FCC naphtha to meet sulfur limits can cost octane, and reformate blending runs into aromatics limits. Alkylate avoids both trade-offs, so its premium rests on sulfur regulation rather than on cyclical crack spreads.
Where alkylation margin slips away
Interacting variables
Alkylate octane depends on the isobutane-to-olefin (I/O) ratio and reactor temperature, and feed contaminants shift the relationship between them. Each variable can move independently, and the interactions are nonlinear. The same change in I/O ratio can produce a different octane response at a different temperature profile.
Acid strength and its inferential
Acid strength sits near the center of those interactions. In HF units, acid behavior directly affects both operating cost and unit performance. Some plants measure it with online analyzers. Many still depend on inferential relationships, and those can drift as acid-soluble oil (ASO) concentration changes with feed quality and operating conditions. When the inferential drifts, every control layer above it is working from weaker information.
Shift-to-shift variability
One crew may run a more conservative acid strategy while another pushes throughput harder. The difference shows up as shifting I/O ratios, uneven acid draw-off rates and reactive responses to feed changes that a coordinated approach could anticipate. Shift-to-shift variability is one of the most persistent sources of recoverable margin in alkylation.
Reactor cooling
When reactor cooling falls short, throughput, octane-barrels and acid consumption can all move in the wrong direction at once. Cooling water temperature follows the season, so the constraint returns every summer.
Olefin feed from the FCC
Olefin feed arrives from the FCC, outside the alkylation unit's control boundary. A shift from C4 to C3 olefins changes alkylate yield, octane and isobutane demand at the same time. As in any crude oil refining process, upstream changes cascade into downstream units in ways that are hard to predict from the control room.
Protecting octane, throughput and acid use depends on seeing these variables together instead of tuning any one of them alone.
Why conventional control falls short
Advanced process control (APC) delivers value on alkylation units inside the envelope its models were identified on. Alkylation leaves that envelope regularly.
Models that go stale
Model accuracy is hard to sustain when acid strength drifts, FCC feed composition changes or cooling water temperature shifts with the season. The controller's assumptions can go stale before anyone formally retunes it. When the process response no longer matches the embedded model, model-based control can amplify disturbances instead of rejecting them, and linear model predictive control settles on local optima that leave margin behind.
The inferential acid strength is a stubborn weak point. If the base inferential drifts, every APC layer above it works from a flawed input. The problem can stay hidden, because the controller still appears to be working normally while it responds to conditions that no longer describe the unit.
The unit boundary
Conventional control also stops at the unit boundary. The FCC-to-alkylation olefin balance is a live economic variable: a change in C3/C4 ratio moves alkylation yield, octane and isobutane demand. The alkylation APC has no mechanism to anticipate those upstream changes or to weigh their effect on refinery margin before they arrive as disturbances.
Experienced board operators catch problems no controller sees. The number of interacting variables can still exceed what any operator or linear controller can optimize continuously across the full range of operating states.
What a learned model changes
A model learned from the unit's own operating history does not depend on a single linearized operating point. It learns how I/O ratio, acid behavior, temperature and feed composition move together across the range of conditions the unit has actually run. When ASO concentration shifts with a change in feed quality, the model reflects how the unit responded to similar conditions before, so its recommendations stay grounded in real process behavior. The same history lets the model learn acid behavior from the relationships observed across operating states, instead of relying on one fixed inferential.
Coordinating across the FCC boundary
With visibility across connected units, the model can bring FCC optimization and the alkylation interface into one view. A shift in the C3/C4 olefin balance becomes a known input instead of an after-the-fact disturbance. The model can estimate the margin effect of the upstream change and recommend setpoints that account for both units.
One model for operations, planning and engineering
A shared model also changes how teams work together. Planning may set LP targets on assumptions that differ from what the board sees, while operations compensates in ways the planning model does not capture. A common model built from historical process data makes that gap visible, so teams can align before mismatches compound.
How trust builds in practice
Plants do not start in closed loop. In advisory mode, the model recommends setpoint changes for variables such as I/O ratio, acid draw-off rate and reactor temperature targets, and operators decide whether to act. Experienced operators can test the model's judgment against their own before any automatic move, and the model has to prove itself under the unit's real operating conditions as well as in offline validation.
Advisory mode also gives every shift the same reference point, so changing conditions are not interpreted from scratch each time, and it makes the trade-offs visible so crews can make more consistent choices without being held to one operating philosophy. Newer operators see what the model recommends under conditions they have not yet met, which builds operator understanding of the unit faster than time at the board alone.
A model will not capture every instinct behind a veteran's call. It can preserve the observable relationships between process states and the moves that produced better results. As operators confirm, shift after shift, that the model finds margin under changing conditions, plants move from advisory recommendations to closed-loop control. Operators set the envelope the controller may use and can take over from the board.
How the Imubit Platform applies
Imubit applies Map, Model and Control to the alkylation unit as part of its work in refining. Map traces lost octane-barrels and acid cost to the recurring decisions behind them, such as I/O ratio, acid draw-off and reactor temperature targets. Model learns the unit's nonlinear behavior, and its coupling to the FCC, from its own history with Deep Learning Process Control® (DLPC®). Control takes those decisions to closed loop, writing setpoints to the existing APC and DCS, inside limits set by plant engineers.
