Category level examples show how engineering review, rebuild documentation and regional service routing reduce outage risk without inventing customer names. The cases below are written for maintenance and procurement teams that need a defensible path before committing to repair, rebuild or replacement. Each example starts with plant evidence: nameplate data, ratio, input kW, output rpm, oil condition, vibration trend, bearing temperature and the available shutdown window. Flender support uses that evidence to decide whether the next step is a repair center inspection, a distributor stock check, an archived drawing search or a replacement comparison. The value is not a dramatic claim; it is a clearer decision record before the gearbox is removed from service.
A Tier 1 mining operator needed a rebuild decision before a planned shutdown. The review compared bearing replacement, seal upgrade and gear tooth condition against service factor and conveyor duty. The plant sent oil analysis, vibration notes and photos of the output shaft seal. Flender support mapped those details to a repair route that protected the outage schedule and identified which wear parts had to arrive before the gearbox was opened.
A cement producer used nameplate data, oil analysis and temperature notes to decide whether the reducer could be rebuilt in place or should be exchanged during the outage. The engineering review focused on thermal capacity, bearing L10 h assumptions, lubrication interval and DIN 3990 load capacity evidence. Procurement received a comparison between rebuild scope, lead time and replacement risk, which made the internal approval discussion simpler.
A marine equipment maker required drawing support, coupling envelope checks and replacement documentation before moving a legacy deck machinery drive into service. The request included shaft dimensions, mounting limits and an alignment note from the shipyard. Flender support treated the case as an engineering fit question first, then routed catalog, manual and parts list requests to the correct archive path.
Share the application, duty cycle and outage window. Flender support can compare repair, rebuild and replacement routes before purchase orders are issued. The most useful first message includes the unit serial number, ratio, mounting position, motor kW, running rpm, site location, current symptom and any photos of seals, shafts, oil samples or gear tooth contact patterns. If the team is unsure which data matters, send the nameplate and a short description of the operating problem. A spec engineer can then ask for the missing values instead of forcing the plant to search every old document at once.