Lubricant blending plant (LOBP) batch controls: Refutas viscosity-index trim math, piggable manifold matrices, and flush-slop reabsorption

Topics: lubricant manufacturing software, lube blending software, petroleum blending software.

Unlike refinery fuel inline blenders (O023) that produce three or four gasoline and diesel grades, a Lube Oil Blending Plant (LOBP) manufactures 150 to 400 distinct SKUs across automotive engine oils (SAE 0W-20, 15W-40), industrial hydraulic fluids (ISO VG 32/46/68), gear oils, marine cylinder oils, and transmission fluids from Group I, II, III, and PAO base stocks plus concentrated performance additive packages (DI) and Viscosity Index Improvers (VII). A $20\text{ MT}$ batch kettle that misses its SAE J300 kinematic viscosity window at $100^\circ\text{C}$ ($\text{KV}_{100}$) by $0.4\text{ cSt}$—or an ashless turbine oil contaminated with $25\text{ ppm}$ of calcium detergent left in an unpigged filling header, creates tens of thousands of dollars in off-spec rework. This guide (O124) defines the Refutas viscosity-trim calculation, co-additive dilution protection, piggable manifold family matrix, and segregated flush-slop reabsorption workflow.

Scope and governance boundary

This article specifies the batch-manufacturing, LIMS laboratory, and PLC manifold control architecture for lubricant blending and filling plants:

• What this workflow governs: Load-cell / mass-meter kettle charging (Base Oil 150N/500N/150BS + DI Package + VII + PPD), laboratory first-sample release (ASTM D445 $\text{KV}{100}/\text{KV}{40}$, Cold Cranking Simulator $\text{CCS}$, and ICP-AES elemental metals), Refutas/Walther non-linear trim-addition recipes, piggable line clearance interlocks, and family-segregated flush-slop inventory reabsorption (ERPNext Stock Entry).
• What this workflow does not replace: It does not replace API/ACEA/OEM engine sequence dynamometer testing, ATIEL Base Oil Interchange (BOI) licensing rules, or hazardous hot-oil drumming safety procedures.

1. Step 1 — Record intake & baseline identification: Never use linear weighted-average arithmetic to calculate base-oil or polymer trim corrections on an out-of-spec lubricant batch: kinematic viscosity blends logarithmically, requiring **Refutas / Walther Viscosity Blending Index ($\text{VBI}$) math ([ASTM D341](https://www.astm.org/d0445-23.html))** coupled with proportional **Detergent-Inhibitor (DI) additive package top-ups** so elemental $\text{Zn/P/Ca}$ specs are not diluted below [API 1509 / ATIEL](https://atiel.eu/code-of-practice/) limits.
2. Step 2 — Cross-system reference & custody linkage: Enforce a deterministic **Product Family Compatibility & Pigging Matrix** across Automatic Batch Blenders (ABB), Dedicated Piggable Manifolds (DPM), and small-pack filling lines: never allow a high-ash engine oil ($\text{Ca/Zn}$) to contaminate an ashless turbine, compressor, or zinc-free hydraulic oil without a verified line flush and laboratory $<5\text{ ppm}$ carryover clearance.
3. Step 3 — Exception quarantine & authority check: Segregate flush oil into **family-specific ERP slop tanks** (`Ashless Hydraulic`, `PCMO/HDDO Engine Oil`, `Gear/EP Sulfur-Phosphorus`, `Metalworking Emulsifiable`) rather than dumping all flushes into a single downgraded mixed-slop tank.
4. Step 4 — Verified disposition & audit trail closure: Cap flush-slop reabsorption into fresh commercial batches at a strict formulation ceiling (typically $\le 1.0\%\text{–}2.0\text{ wt\%}$ of same-family flush) and block release until ICP-AES elemental metals and [ASTM D445](https://www.astm.org/d0445-23.html) kinematic viscosity at $40^\circ\text{C}$ and $100^\circ\text{C}$ pass.

Why linear trim math and single-tank slop systems ruin LOBP margins?

Lubricant plants that manage kettle corrections and line flushes by operator rule-of-thumb experience three recurring operational losses:

1. Over-Correction from Linear Viscosity Assumptions: When a heavy base stock ($500\text{N}$ or Bright Stock) and a light base stock ($150\text{N}$) are mixed, the resulting blend viscosity is always lower than the linear mass-weighted average ("viscosity depression"). If an operator uses a linear spreadsheet to thin a high-viscosity batch from $15.85\text{ cSt}$ down to $14.50\text{ cSt}$, the batch overshoots the target and drops too thin, requiring a second reverse trim with heavy oil and polymer.
2. Diluting the Performance Additive Package During Base-Oil Trims: Adding $1,450\text{ kg}$ of neat $150\text{N}$ base oil to correct viscosity reduces the mass percentage of the Detergent-Inhibitor (DI) package in the kettle by nearly $7%$. If the trim calculator does not automatically mandate a co-addition of DI package at the licensed treaty rate (e.g., $13.05\text{ wt%}$), the batch passes viscosity but fails its ICP-AES Zinc, Phosphorus, and Calcium minimums (ATIEL Code of Practice).
3. Cross-Family Additive Poisoning on Shared Filling Headers: Trace silicon defoamer, sulfur-phosphorus EP gear additives, or calcium sulfonate detergents left in unpigged manifold dead-legs ruin the air-release, demulsibility, or filterability of subsequent turbine, compressor, or ashless hydraulic oil batches.

• Primary control scope: lubricant manufacturing software across operations and connected ERP/EAM records.
• Segregation boundary: Operational status updates never auto-close engineering, safety, or finance sign-off gates.
• Verification cadence: Reconcile open exceptions, overrides, and late adjustments at each shift or period close.

LOBP kettle blending, trim calculation, and line-clearance control matrix

Illustrative worked example: Refutas SAE 15W-40 viscosity trim with DI co-dosing and flush-oil reabsorption

Illustrative blending scenario with synthetic figures to demonstrate Refutas viscosity blending index math, additive dilution protection, and flush-oil accounting; not a client case study.

Consider an LOBP blending a $20,000.0\text{ kg}$ ($20.0\text{ MT}$) batch of SAE 15W-40 API CI-4 heavy-duty diesel engine oil in Kettle BK-04 (licensed DI additive package treat rate $= \mathbf{13.05\text{ wt%}}$).

Step 1: Evaluate first-sample KV100 and compute Refutas VBI trim

While SAE J300 defines the legal SAE 40 kinematic viscosity band at $100^\circ\text{C}$ as $12.50\text{ to } <16.30\text{ cSt}$ ($\text{mm}^2/\text{s}$), the plant's internal quality release window is $14.20\text{ to }14.80\text{ cSt}$ (target center $14.50\text{ cSt}$) to guarantee stay-in-grade shear stability.

• First-sample lab result on BK-04 ($20,000.0\text{ kg}$): $\text{KV}_{100} = \mathbf{15.85\text{ cSt}}$ (too viscous; sits outside the $14.80\text{ cSt}$ upper plant release gate).
• Available light trim base stock (Group II 150N): $\text{KV}_{100} = \mathbf{5.20\text{ cSt}}$.
• Compute Refutas Viscosity Blending Index ($\text{VBI}$) for each stream: $$\text{VBI} = 14.534 \times \ln\bigl(\ln(\text{KV}_{100} + 0.80)\bigr) + 10.975$$
  1. Current kettle batch ($\text{KV}_{100} = 15.85\text{ cSt}$): $$\text{VBI}_{\text{batch}} = 14.534 \times \ln\bigl(\ln(16.65)\bigr) + 10.975 = 14.534 \times 1.03407 + 10.975 = \mathbf{26.004}$$
  2. Light 150N trim base oil ($\text{KV}_{100} = 5.20\text{ cSt}$): $$\text{VBI}_{\text{150N}} = 14.534 \times \ln\bigl(\ln(6.00)\bigr) + 10.975 = 14.534 \times 0.58320 + 10.975 = \mathbf{19.451}$$
  3. Target corrected batch ($\text{KV}_{100,\text{target}} = 14.50\text{ cSt}$): $$\text{VBI}_{\text{target}} = 14.534 \times \ln\bigl(\ln(15.30)\bigr) + 10.975 = 14.534 \times 1.00359 + 10.975 = \mathbf{25.561}$$

Step 2: Solve required 150N base-oil trim mass and proportional DI package top-up

Because Refutas $\text{VBI}$ blends linearly by mass fraction ($w_{\text{trim}}$): $$w_{\text{trim}} = \frac{\text{VBI}{\text{batch}} - \text{VBI}{\text{target}}}{\text{VBI}{\text{batch}} - \text{VBI}{\text{150N}}} = \frac{26.004 - 25.561}{26.004 - 19.451} = \frac{0.443}{6.553} = \mathbf{0.06760}\quad (6.760%\text{ of base/polymer phase})$$

• Required 150N base-oil addition to the $20,000.0\text{ kg}$ kettle: $$M_{\text{150N_trim}} = 20,000.0\text{ kg} \times \frac{0.06760}{1 - 0.06760} = 20,000.0 \times \frac{0.06760}{0.93240} = \mathbf{1,450.0\text{ kg}}$$
• Proportional DI additive package co-addition (so the $1,450.0\text{ kg}$ of added neat base oil also carries the mandatory $13.05\text{ wt%}$ DI package treat rate: $1,450.0 \times [0.1305 / (1 - 0.1305)] = \mathbf{218.0\text{ kg}}$):

Step 3: Track piggable line clearance and segregated flush-slop reabsorption

On the adjacent industrial filling line switching from Ashless Hydraulic Oil (ISO VG 46, $0\text{ ppm}$ Zn) to a second ISO VG 46 run after a manifold maintenance flush:

• Dual-seal pipeline pigging recovers $98.2%$ of the header hold-up directly into the destination pack.
• The remaining $140.0\text{ kg}$ line-rinse flush is routed into dedicated ERP bin WH-SLOP-ASHLESS-HYD (tested at $45.8\text{ cSt}$ @ $40^\circ\text{C}$, $0\text{ ppm}$ Ca/Zn) and automatically scheduled for reabsorption into the next $20,000.0\text{ kg}$ ISO VG 46 kettle batch at $0.70\text{ wt%}$ ($\le 1.00\text{ wt%}$ maximum flush-rework cap)—recovering $100%$ of the base-oil value with zero downgrade waste.

Acceptance tests and operational readiness criteria

1. ACT-O124-01 (Refutas VBI & Co-Additive Protection on Kettle Trims): Whenever a kettle batch requires a base-oil trim Stock Entry, the LIMS/ERP calculator must compute the viscosity shift via Refutas/Walther logarithmic blending indices and automatically append the proportional DI additive top-up required to keep elemental ICP-AES percentages constant.
2. ACT-O124-02 (Dynamic Base-Oil CoA Ratio Adjustment Pre-Charge): Before releasing a batch manufacturing order to the ABB/kettle PLC, the system must adjust the 150N : 500N base-oil mass split using the active supply tanks' current measured $\text{KV}_{100}$ rather than static nominal textbook values.
3. ACT-O124-03 (Ash-to-Ashless Manifold Pigging & Flush Interlock): If a filling line or non-dedicated manifold transitions from a detergent/ash-containing family (Engine Oil) to an ashless/low-ash family (Turbine / Ashless Hydraulic / Transformer Oil), the PLC/ERP must block filling until both a completed pig-return signal and a passing flush-sample ICP check ($<5\text{ ppm}$ Ca/Zn) are logged.
4. ACT-O124-04 (Family-Specific Slop Segregation & 1%–2% Reabsorption Cap): The ERP BOM/rework module must block issuing flush-slop batches across incompatible product families and enforce the maximum allowable percentage ($\le 1.0%\text{–}2.0\text{ wt%}$) of same-family slop per fresh batch.

Next steps

1. Embed actual base-oil tank $\text{KV}_{100}$ feed-forward math into pre-blend recipe generation: Prevent initial kettle viscosity misses caused by refinery base-oil lot-to-lot drift ($5.05\text{ cSt}$ vs $5.35\text{ cSt}$ on 150N).
2. Replace linear trim spreadsheets with a locked Refutas VBI + DI co-dosing calculator in LIMS/ERP: Ensure viscosity corrections never dilute licensed performance additive treat rates.
3. Establish 5 to 6 segregated flush-oil holding totes in the warehouse and ERP: Separate PCMO/HDDO, Ashless Hydraulic, Industrial Gear EP, Transmission ATF, and White/Process Oil flushes so >90% of flush oil is re-blended at full product value.
4. Sequence weekly filling schedules from light/ashless grades to heavy/high-additized grades: Minimize mandatory line flushes across shared headers.

Frequently Asked Questions

How do lube-oil blending plants (LOBP) optimize Automatic Batch Blender (ABB) piggable manifolds, kinematic viscosity at 40°C/100°C trim additions, and flush-oil slop re-absorption?

Teams should govern lubricant manufacturing software by linking every transaction to its source evidence, timestamp, and assigned owner before permitting downstream posting. Distinct from O023 (refinery fuel inline octane/cetane blending); O124 governs Group I/II/III base-oil + VI improver/additive package batch kettles, line-pigging compatibility matrices, and small-pack filling line clearance. Rather than relying on informal spreadsheet overrides, the workflow enforces a documented verification gate and preserves the original observation whenever a correction is recorded.

How does lube blending software handle exceptions and mismatches?

When a discrepancy occurs during lube blending software, the system routes the blocked record into an owned exception queue rather than silently dropping or auto-adjusting the balance. Assigned operational, quality, and finance owners must review and approve exceptions before posting. Each exception retains the original quantity, date, and counterparty reference until the designated reviewer resolves the variance with supporting evidence.

What should teams test before automating petroleum blending software?

Before scaling petroleum blending software, run a bounded pilot using historical records that include partial receipts, late updates, duplicate messages, and rejected lines. Verify that the integration preserves idempotency, maintains a clear segregation of duties between operational entry and financial approval, and produces an auditable trail for every state transition.

Summary and next actions

1. Map the current lubricant manufacturing software record boundaries, system of record, and named approval owners before changing workflow rules.
2. Separate operational status updates from engineering, safety, or financial disposition sign-off.
3. Validate exception queues, duplicate handling, and cutoff reconciliation in a bounded pilot before production rollout.