A BOF oxygen lance delivers supersonic oxygen at 450–500 m/s into a 300-tonne bath of molten steel at 1,650°C. The only thing standing between productive blowing and a catastrophic water-into-bath explosion is the integrity of the lance's water cooling circuit and the condition of the copper lance tip. Every heat erodes the tip nozzles slightly, deposits skull on the lance body, and cycles the cooling water circuit through thermal stresses that progressively degrade seals and connections. The sublance — which descends into the converter during the blow to measure bath temperature, carbon content, and oxygen activity — carries its own failure modes: probe contamination, tip freezing, cable damage, and withdrawal mechanism wear that together determine whether the heat ends on a measured data point or an estimated one. Managing BOF oxygen lance and sublance reliability is not a replacement task — it is a structured PM and condition monitoring program that tracks heat counts, cooling water differentials, skull build-up rates, and sublance tip quality to prevent the water leak, the tip burnout, and the lance hoist failure before they create the emergency. OxMaint's CMMS connects lance heat count tracking, water cooling condition logging, sublance probe records, and hoist mechanism PM into a single mobile-accessible platform that gives your melt shop maintenance team visibility across every lance in your fleet. Register your BOF lance assets in OxMaint and start your lance reliability program today.
Blog · BOF · Oxygen Lance and Sublance Reliability
BOF Oxygen Lance and Sublance Reliability Programs for Steel Producers
Lance Tip Heat Count Tracking · Water Cooling Differential Monitoring · Skull Build-Up Management · Sublance Probe Records · Lance Hoist PM · Emergency Retraction Testing · BOF Lance CMMS · Lance RUL · Lance Campaign Records
Lance Fleet Status — BOF Shop
L-01
Oxygen Lance — Converter 1
Active · Heat 312 · Water Flow Normal
L-02
Oxygen Lance — Converter 2
Heat 480 · Tip Change Due at 500
SL-01
Sublance — Converter 1
Cable Wear Detected — WO Open
L-03
Oxygen Lance — Standby
Ready · Skull-Free · Inspected
300–600
Typical oxygen lance tip service life in heats before nozzle erosion requires replacement — varies by oxygen flow rate, blowing pattern, and skull management practice
₹8–20L
Cost of a lance cooling water leak event during blowing including emergency retraction, heat abort, converter inspection, and unplanned maintenance delay
45 min
Average production delay per sublance failure event — unplanned probe tip freezing or cable damage that requires mid-heat withdrawal and replacement
2 per heat
Typical sublance measurement cycles — one mid-blow for in-process bath data, one end-blow for final temperature, carbon, and oxygen before tap decision
The Five Failure Modes That Interrupt BOF Blowing — and the Signals OxMaint Tracks
01
Lance Tip Burnout / Nozzle Erosion
Warning Signal
Oxygen flow pressure drop at constant demand; asymmetric flame pattern during blowing; bath turbulence change detectable by vibration; heat count approaching tip service limit
Root causes: operating beyond heat count limit, excessive lance height causing tip overheating, skull build-up redirecting oxygen jets, inadequate water flow cooling the tip face
OxMaint tracks cumulative heat count per lance tip — generates tip change work order at configurable threshold before erosion causes oxygen delivery inefficiency or tip burnout
02
Cooling Water Leak During Blowing
Warning Signal
Rising water temperature differential between inlet and outlet at constant flow; dropping outlet water flow rate; steam at lance exit visible from operator platform; water differential alarm approaching trip threshold
Root causes: water tube pinhole corrosion from scale build-up, thermal fatigue crack at tube-to-header joint, seal failure at lance connection, jacket wall erosion from oxygen jet impingement
OxMaint logs water ΔT and flow differential at each heat — trending rising ΔT over successive heats gives 12–24 hours of warning before the threshold trip that forces emergency retraction
03
Skull Build-Up and Lance Freeze
Warning Signal
Lance weight increase detectable on hoist current; skull visible at lance inspection; restricted oxygen flow through nozzles after skull deposition; uneven bath stirring pattern during blow
Root causes: low lance position during skull formation period, inadequate skulling control procedure, high-silicon heats with elevated skull volume, infrequent lance inspection between heats
OxMaint schedules visual skull inspection at configured heat intervals — records skull severity score per inspection, tracks heats between skull removal events, and generates cleaning work orders before skull immobilises the lance
04
Lance Hoist Mechanism Failure
Warning Signal
Hoist motor current rising at constant lance speed; travel speed deviating from baseline; wire rope inspection showing broken wires; gearbox oil analysis showing metal particles; brake test showing reduced holding force
Root causes: wire rope fatigue from thermal cycling, gearbox gear wear, motor overheating from overloaded skull mass, brake lining wear, guide roller wear from lateral lance forces
OxMaint tracks hoist motor current baseline, wire rope inspection cycle, and brake test results — a hoist failure with the lance in the bath is a safety emergency; OxMaint prevents it by managing the hoist maintenance schedule
05
Sublance Probe Tip Freezing / Cable Failure
Warning Signal
Probe withdrawal force increase on descent/retraction; signal quality degrading on temperature and carbon measurement; cable sheath damage visible at last inspection; tip probe batch quality variation from supplier
Root causes: slag skull adherence on sublance outer body, bath temperature too low at measurement point causing probe freezing, cable damage from heat radiation, worn withdrawal mechanism seal
OxMaint tracks sublance probe tip batch records, withdrawal force log per heat, and cable condition inspection records — sublance PM ensures measurement quality and mechanism reliability simultaneously
Lance Heat Count Lifecycle — OxMaint Tracks Every Stage from New to Condemned
BOF Lance Tip Heat Count Progress — Live Status Across Lance Fleet
Each bar represents one lance. Colour indicates proximity to tip replacement threshold (configured per plant — typically 300–600 heats).
Lance L-01 (Converter 1)
Normal
Lance L-02 (Converter 2)
Change Due
Lance L-03 (Standby)
Normal
Lance L-04 (Converter 3)
Normal
Lance L-05 (Converter 3 — Spare)
Replace Now
Sublance SL-01 (Converter 1)
Inspect Due
OxMaint auto-generates a tip change work order when heat count reaches the configured threshold — your melt shop team always knows which lance is due for service before the tip reaches its erosion limit.
BOF Lance and Sublance PM Schedule — Auto-Generated by Lance ID in OxMaint
| Component | PM Task | Interval | Predictive Indicator | Risk if Missed |
|---|---|---|---|---|
| Lance Tip (Nozzle) | Heat count check — tip change at configured threshold; nozzle condition inspection at mid-life | Per heat count threshold (300–600 heats) | Oxygen pressure drop at constant demand; bath turbulence change | HIGH — over-life tip → nozzle burnout, oxygen delivery failure, heat abort |
| Lance Cooling Water Circuit | ΔT (inlet vs outlet temperature) and flow differential log per heat; circuit pressure test | Per heat (ΔT log); monthly pressure test | Rising ΔT trend over successive heats indicates developing tube degradation | HIGH — water leak during blowing → explosive steam event, emergency shutdown |
| Lance Body (Visual) | Skull build-up inspection — severity rating, location, and cleaning decision recorded | Every 50 heats or after high-silicon heats | Skull severity score increasing trend over successive inspections | HIGH — excessive skull → lance freeze, hoist overload, oxygen flow restriction |
| Lance Hoist Wire Rope | Broken wire count, kinking, corrosion check — entire rope length; sheave condition | Monthly visual + quarterly detailed inspection | Hoist current increase at constant lance speed; broken wire count per metre | HIGH — rope failure with lance in bath → safety emergency, converter shutdown |
| Hoist Gearbox | Oil analysis (metal particles, viscosity, water content) + bearing vibration | Quarterly oil sample; monthly vibration | Fe/Cr content in oil sample above threshold; vibration rising at gear mesh frequency | HIGH — gearbox failure → lance stuck in bath, major safety incident |
| Emergency Retraction System | Full retraction test — timed from max depth to full park position; backup power supply check | Monthly functional test | Retraction time exceeding commissioning baseline; power supply voltage check | HIGH — failed emergency retraction → water-in-bath explosion risk if cooling fails |
| Sublance Withdrawal Mechanism | Withdrawal force measurement, seal condition, guide roller wear, drive chain/belt check | Weekly inspection + monthly force measurement | Withdrawal force increasing above baseline — probe freezing risk | MEDIUM — withdrawal failure → probe loss in bath, heat abort, refractory damage risk |
| Sublance Cable / Signal Conductor | Cable sheath inspection — abrasion, kinking, heat damage; signal quality verification | Weekly visual + monthly signal test | Signal noise increasing on bath measurement — cable insulation degrading | MEDIUM — cable failure → loss of in-process measurement, heat managed on estimate |
Every Heat Count. Every Water Differential. Every Sublance Probe Record — in One CMMS Your Melt Shop Team Uses on Mobile.
OxMaint registers each oxygen lance and sublance as a serialised asset. Heat counts accumulate automatically from work order logging. Water differential trends are visible on the lance asset page. Hoist wire rope inspection cycles and emergency retraction test results are stored in the PM history. Your melt shop team never needs to wonder how many heats are on Lance L-02's tip or when the last emergency retraction test was done — it is in OxMaint, accessible on any device. Start your BOF lance reliability program in OxMaint — free trial.
What OxMaint Tracks for Each BOF Lance — The Four Data Pillars
Water Cooling Condition — Per-Heat ΔT Trending
The only real-time indicator of lance cooling water circuit integrity during blowing is the temperature differential between inlet and outlet water. A lance with a developing crack in its water jacket shows a rising ΔT trend over successive heats — the crack admits hot gas, the water absorbs more heat, and the outlet temperature rises relative to inlet. OxMaint logs the ΔT at each heat and displays the trend on the lance's asset page. A rising ΔT trend over 10–15 heats gives the melt shop team the advance warning to plan a lance change before the ΔT reaches the automatic trip threshold. This converts what would be an emergency lance retraction mid-heat into a planned changeover at heat end. OxMaint also tracks monthly pressure test results against each lance's pressure history, identifying lances with declining seal integrity before operational pressure testing reveals a failure.
Alert: ΔT rising more than 8°C above rolling baseline over 10 heats — investigation work order generated
Heat Count and Tip Remaining Useful Life
Every heat in which a lance is used increments its heat count in OxMaint. The tip change threshold — configured per plant based on oxygen flow rate, blowing pattern, and historical tip performance — is stored against each lance asset. OxMaint displays the heat count progress bar on the lance dashboard and generates a tip change planning work order when the count reaches the pre-alert threshold, typically 80% of the tip service limit. This allows the tip change to be scheduled for the next planned converter idle period rather than reacting to nozzle erosion symptoms during a blow. The tip change work order also records the removed tip's condition — confirming whether the threshold is appropriately set or needs adjustment for the grade mix and blowing patterns being run. See how OxMaint tracks lance heat counts — book a demo.
Alert: Heat count reaches 80% of tip service limit — planning work order generated for next converter idle window
Hoist Mechanism and Emergency Retraction
The lance hoist is safety-critical. A hoist failure with the lance submerged in the bath of a BOF converter is a major emergency requiring immediate crane intervention, bath agitation risk, and potential refractory damage. OxMaint manages every aspect of hoist maintenance: wire rope inspection cycles with broken wire count per metre recorded, gearbox oil analysis results, motor bearing vibration trending, brake lining measurement, and — critically — monthly emergency retraction functional tests with the timed retraction distance and speed recorded against the asset. The emergency retraction test record is the documented evidence that the safety system was tested and functional. Without a CMMS logging these tests, the question "when was the retraction system last tested" cannot be answered from shift logs alone. Configure hoist maintenance PM in OxMaint — free trial.
Alert: Retraction test overdue by >7 days; hoist current >10% above baseline; broken wire count approaching rejection limit
Sublance Probe Batch and Mechanism Records
The sublance delivers two measurement cycles per heat — mid-blow and end-blow — each requiring a single-use probe tip to be loaded, lowered into the bath, and withdrawn with a valid temperature, carbon, and oxygen reading. OxMaint tracks the probe tip batch number and supplier against each heat's sublance record, enabling correlation between measurement failures and specific probe batches — critical data for supplier qualification and batch rejection. The sublance withdrawal mechanism, cable condition, and guide system are tracked in separate PM work orders with scheduled inspection intervals. When withdrawal force increases above baseline, OxMaint generates an investigation work order before the mechanism reaches the point of probe loss in the bath — the failure mode that requires crane removal of frozen probe material from the converter.
Alert: Sublance measurement failure rate >5% over 20 heats; withdrawal force >15% above baseline — mechanism inspection work order generated
Before vs After — What CMMS-Managed Lance Reliability Changes
Reactive Lance Management
Lance tip replaced only when nozzle erosion causes a heat quality issue or oxygen pressure drop forces investigation — typically 20–50 heats after the optimal change point
Water differential trend data exists in the control room historian but is never systematically reviewed — a developing ΔT rise is invisible until the thermal trip fires and triggers emergency retraction
Lance skull inspection depends on operator initiative — skull builds unchecked until withdrawal force on the hoist alarm or lance weight increase causes concern
Emergency retraction test performed when the shift manager requests it — no fixed schedule, no record of last test date in a system that can be audited
Sublance measurement failures investigated per-event — no correlation of failure patterns to probe batches, so a bad batch from a supplier is not identified until 10+ failures have occurred
Lance fleet management is by individual knowledge of the hoist operator — no way to tell which lance has the most heats or which is next for hoist inspection
OxMaint Lance Reliability Program
Tip change work order generated at 80% of heat count limit — tip is changed at the planned converter idle period, never after an erosion symptom appears during blowing
Per-heat ΔT logging in OxMaint shows rising trend on Lance L-02 over 12 heats — investigation work order raised, lance changed at heat end, no emergency retraction required
Skull inspection work order generated every 50 heats — skull severity score trending allows cleaning to be scheduled before skull weight affects hoist operation
Monthly emergency retraction test work order in OxMaint — every test result recorded with timestamp, timed retraction distance, and pass/fail status, fully auditable
Sublance probe batch numbers recorded per heat in OxMaint — measurement failure correlation identifies the bad batch after 3 failures, supplier notified with full evidence record
OxMaint lance fleet dashboard shows every lance's heat count, last skull inspection, and next PM due — shift supervisor has full fleet visibility in 30 seconds on any device
"We had a water leak event on Lance L-03 that triggered an emergency retraction during a heat and forced a two-shift investigation. When we reviewed what data was available, the cooling water differential had been rising for fourteen heats — the information existed in the DCS historian, but nobody was systematically reviewing it between heats. After implementing OxMaint and setting up per-heat ΔT logging with a rising-trend alert, we caught the next developing lance degradation on a different converter at heat eight of the trend rise. We changed the lance at the next heat end. That single early detection more than justified the entire year of OxMaint subscription. Safety, production continuity, and the knowledge that our emergency retraction tests are now formally scheduled and recorded — all three improved simultaneously."
Frequently Asked Questions — BOF Lance and Sublance Reliability with OxMaint
How does OxMaint track lance heat counts and generate tip change work orders automatically?
Each oxygen lance is registered as an asset in OxMaint with a configured tip service limit in heats — typically 300–600 heats depending on plant oxygen flow rate and blowing pattern. Heat count is incremented against the lance asset record at each heat either manually by the shift team via the mobile interface, or automatically if the plant's control system can provide a heat completion signal. OxMaint displays the current heat count and the remaining heats to the tip change threshold on the lance's dashboard. A planning work order is generated at 80% of the tip service limit — giving the melt shop team typically 60–120 heats of advance notice to schedule the tip change during a converter idle window. The completed tip change work order records the removed tip's condition assessment, providing feedback on whether the service limit threshold is correctly calibrated for current blowing conditions. Configure lance heat count tracking in OxMaint — free trial.
Can OxMaint trend cooling water differential temperature per heat to detect developing lance tube failure?
Yes. The cooling water temperature differential (outlet minus inlet) is logged against the lance's asset record at each heat via the OxMaint mobile interface or desktop entry. OxMaint calculates a rolling baseline ΔT from the last configured number of heats and displays the trend chart on the lance's condition page. An alert is generated when the ΔT rises more than a configured number of degrees above the rolling baseline over a defined number of consecutive heats — this pattern is the earliest detectable signal of developing tube wall degradation before the differential reaches the automatic trip threshold. The trend converts a single-point alarm system into a multi-heat early warning system, giving the melt shop team planned intervention time rather than emergency reaction time. Monthly pressure test results are also stored against the lance's record, providing a second condition monitoring channel. Book a demo to see lance ΔT trending in OxMaint.
How does OxMaint manage the emergency retraction system test schedule and records?
The emergency retraction system for each lance hoist is registered as a child asset in OxMaint, with a monthly functional test work order automatically generated. The test work order checklist requires the technician to record: retraction time from maximum blowing depth to full park position, backup power supply voltage and switch-over function, retraction speed uniformity, and any mechanical resistance observed during the test. Pass/fail determination is automatic based on the configured maximum retraction time and minimum power supply voltage. All test records are stored permanently against the emergency retraction system's asset record, providing an auditable history that answers "when was the retraction system last tested and what was the result" instantly — critical for both safety compliance and incident investigation. Overdue tests generate escalating alert notifications to the maintenance supervisor.
How does OxMaint track sublance probe batch records and correlate measurement failures with specific batches?
Each heat's sublance usage is recorded in OxMaint as a work event against the sublance asset, with the probe tip batch number and supplier recorded along with the measurement result quality (valid reading, partial reading, no reading, or measurement abort). OxMaint accumulates these records and can generate a failure analysis report filtered by probe batch — showing measurement failure rate per batch number across the selected date range. When a specific batch shows a statistically elevated failure rate compared to historical batches from the same supplier, OxMaint generates an alert and a hold work order that prevents the suspect batch from being used until a quality investigation is completed. This batch correlation capability, available only when probe batch data is systematically recorded in a CMMS, is what separates plants that identify bad batches after 3 failures from those that discover them after 30 heats of degraded process control.
Can OxMaint manage skull build-up inspection scheduling and skull severity trending for BOF lances?
Yes. Skull inspection work orders are auto-generated by OxMaint at configured heat intervals — typically every 50 heats, or after heats with high-silicon hot metal input that are known to produce more skull volume. The mobile inspection checklist captures skull severity on a defined scale (none, light, moderate, heavy, critical), skull location on the lance body, and the inspection decision (continue, clean, or change lance). OxMaint trends the skull severity score over successive inspections and generates a cleaning work order when the trend indicates progressive skull build-up before the skull mass begins to affect hoist current or oxygen flow distribution. The inspection history also correlates skull build-up rate with specific grade sequences and hot metal silicon levels — enabling the melt shop team to pre-schedule skull inspections more frequently on high-silicon charge sequences.
How does OxMaint manage the full lance hoist maintenance program including wire rope, gearbox, and brake?
The lance hoist is broken down into its major maintainable components in OxMaint — wire rope, gearbox, drive motor, brake assembly, sheaves, and guide rollers — each as a child asset with independent PM schedules. Wire rope inspections are scheduled monthly for visual inspection and quarterly for detailed broken wire count per metre and stretch measurement. Gearbox oil samples are generated quarterly with results recorded against the gearbox asset, trending metal content and viscosity over successive samples. Brake lining measurements are captured at quarterly inspections with wear recorded against the brake assembly record. Motor bearing vibration is measured monthly. All of these inspections are batched into a single hoist maintenance work order at the scheduled interval — the technician completes one work order covering the full hoist system, not five separate tasks, making the inspection manageable within a converter idle window. Set up your lance hoist PM in OxMaint — free trial.
Does OxMaint require sensor hardware or DCS integration to deliver BOF lance monitoring value?
No. OxMaint delivers full BOF lance and sublance reliability management through structured data entry by the shift team and maintenance technicians via the mobile interface — no sensor hardware, no DCS integration, and no IT project required. Heat count is logged manually per heat. Water differential is read from the existing instruments and entered on the mobile app. Skull inspections are completed with a mobile checklist. Hoist measurements are recorded from handheld instruments. Plants with DCS historian systems can connect them to OxMaint via API for automated data import, but this is an enhancement available after the program is running — not a prerequisite. OxMaint delivers structured lance reliability program value from the first heat logged, with zero hardware or integration lead time. The entire BOF lance asset register can be configured and live within a single working day on the free trial.
What makes OxMaint different from generic CMMS platforms for BOF lance and sublance management?
Generic CMMS platforms manage work orders and PM schedules for static assets. BOF lance reliability management requires additional capabilities: heat count accumulation per lance as the primary PM trigger (not calendar time), per-heat water differential trending with anomaly detection logic, probe batch tracking linked to measurement quality events, skull severity scoring with grade-correlated inspection intervals, and emergency retraction test records with timed performance data. OxMaint is pre-configured with these BOF-specific workflows, available on day one of your free trial without custom development. Competitor platforms that focus on IoT sensors and AI prediction require hardware investment and months of baseline data collection before delivering value. OxMaint delivers structured lance program management from the first heat registered, with zero hardware. Schedule a demo to see OxMaint configured for your BOF shop.
BOF Lance Reliability Starts with Heat Counts and Water Differentials. OxMaint Makes Both Routine.
OxMaint gives your melt shop maintenance team a single mobile-accessible platform for lance heat count tracking, cooling water ΔT trending, skull inspection scheduling, hoist mechanism PM, emergency retraction testing, and sublance probe batch records — all without sensor hardware, DCS integration, or IT project lead time.
