Building the Next Kiln Outage Scope from the Last Outage's Numbers
In a cement or lime plant almost nothing thin can be measured while the plant runs. Preheater cyclones, riser ducts, the kiln hood and the cooler are only reachable cold and cleaned, so the thickness history taken in the last stop is the entire evidence base for the next one. It has to survive plate replacements, mixed methods and missed grid squares without silently rewriting itself.
Cement thinning is abrasion and dew-point corrosion, not uniform code corrosion, so the reporting unit is a grid rather than a CML. A 4 m riser duct measured on a 500 mm pitch produces several hundred points per component and thousands per tower. The buyer's question is not what the minimum is but which plates reach their replacement thickness before the outage after next, because rolled plate, abrasion-resistant wear liner and ceramic tile carry procurement lead times of six to fourteen weeks and the purchase order is raised months before the scaffolding goes up. That arithmetic only works if the history is anchored to the plate, not to the wall. When a cone segment is replaced the old grid must retire with it and a new nominal start, or the next wear-rate calculation runs across a plate change and returns a negative rate, thickness that grew, or a false safe rate on thinner new material.
Source: Written against ASTM E797/E797M and ISO 16809 for contact ultrasonic thickness measurement; ASME Section V Article 23; ISO 20669 for pulsed eddy current examination of ferromagnetic components; API 579-1/ASME FFS-1 Parts 4 and 5 for general and local metal loss, applied voluntarily because no jurisdictional inspection code governs kiln shells, preheater cyclones or duct casings the way API 510 governs pressure vessels; ASME Section VIII Division 1 for the small population of coded vessels on site; ASNT SNT-TC-1A and ISO 9712 for personnel; and OSHA 29 CFR 1910.146 and 1910.147 for the confined space and isolation constraints that generate most outage exclusions.
| Component | When it can be measured | Dominant mechanism | Usual method | What the history must retain |
|---|---|---|---|---|
| Preheater cyclone cones and roofs | Cold stop only, after build-up removal | Abrasion by clinker dust, alkali-chloride build-up and spalling | UT grid from inside, scaffolded | Grid origin, pitch, per-square value, and the segment identity so a replaced cone retires its own history |
| Riser and tertiary air ducts | Cold stop; short runs reachable externally through cladding | Erosion at elbows and transitions, worst on the outer radius | UT grid externally where lagging is removed; PEC screening through insulation | Method per reading, because a PEC wall average and a UT point minimum are different quantities |
| Kiln shell | Cold, and only after the shell has come down in temperature | Thermal cycling, creep in hot zones, localised loss under failed refractory | UT along fixed axial and circumferential stations | Station coordinates referenced to a permanent datum, plus refractory campaign history at the same station |
| Kiln hood and cooler casing | Cold stop | Abrasion by falling clinker, thermal distortion | UT grid, often on patched and previously welded plate | Patch and doubler-plate geography, so a reading on a repair is never trended against the parent plate |
| Baghouse, ESP casing and cold-end ducting | Cold stop, occasionally on a mill trip | Acid dew-point corrosion when surfaces fall below dew point, worst on start-stop cycling | UT grid, plus visual on internal stiffeners | Operating history flags, because dew-point loss tracks cold-running hours rather than production tonnes |
| Chutes, hoppers and transfer points | Any short mechanical stop | High-angle abrasion, very local | UT spot readings on wear-liner and parent plate | Which layer was measured: liner, parent plate, or both, since the two have unrelated retirement criteria |
Nothing thin can be measured while the kiln runs
This is the single constraint that makes cement thickness management different from every process-industry version of the same problem. In a refinery, a piping circuit can be measured on stream almost any week of the year; the inspection interval is a code decision. In a cement plant, the preheater tower's internal surfaces are behind refractory, buried in build-up and at several hundred degrees. The cooler is full of clinker. The kiln shell is too hot for standard couplant and the internal surface is inaccessible until the brick comes out. Measurement is not scheduled by interval; it is scheduled by the plant's stop calendar, and that calendar is set by the market and the kiln's refractory campaign, not by an integrity engineer.
The practical result is that the data set behind the next outage decision is fixed and finite. Whatever was measured in the last stop is what you have. You cannot go back for a clarifying reading, you cannot resolve an ambiguity, and you cannot re-measure a square that returned a suspicious value. Every deficiency in that data set is a deficiency you carry all the way to the day the scaffolding goes up, at which point it becomes an emergent scope item, a change order and an overrun.
That is why the provenance fields matter here for a different reason than they do in a pressure-equipment plant. There, provenance defends an inspection interval. Here, provenance is what lets you decide, months in advance and without the ability to check, whether a number you are looking at is real.
Cement wear is not code corrosion
The mechanisms are mechanical and thermal far more than they are electrochemical. Clinker dust in a high-velocity gas stream abrades the outer radius of every elbow and the entry region of every cyclone. Alkali and sulphur circulate through the kiln and preheater, forming build-up that both protects and, when it spalls, tears at the steel underneath. Cold-end equipment, particularly when the raw mill is down and the gas is not being dried, drops below acid dew point and corrodes in a pattern that tracks cold-running hours rather than clinker tonnes. The kiln shell itself sees thermal cycling, ovality-driven flexing and local overheating wherever refractory has failed.
None of these produce the smooth, near-linear wall loss that a corrosion rate is designed to describe. A duct elbow can hold nominal for two campaigns and then lose four millimetres in one, because a build-up shelf collapsed and exposed bare steel to the stream. Trending such a component with a single linear rate is not conservative or unconservative; it is simply the wrong model. What the history has to support instead is per-square rates, visible acceleration, and a comparison of this campaign's map against the last one so a new scour pattern is obvious at a glance.
There is also no external authority setting the rules. Cement and lime plate equipment is largely outside the scope of pressure-equipment codes; there is no API 510 equivalent for a cyclone cone and no statutory inspection interval. Sites therefore adopt internal retirement criteria, often informed by API 579-1/ASME FFS-1 methods applied voluntarily, and those criteria live or die on the consistency of the underlying record. When the criterion is a site standard rather than a code, the record has to be more disciplined, not less, because there is no external body forcing the discipline.
The grid has to land on the same steel twice
A wear map is only a trend if the second campaign measured the same physical squares as the first. In practice, grid registration fails constantly. Paint markers are blasted off during the outage coating campaign. The scaffold is built differently and the crew starts numbering from a different corner. A cone is described as having twelve segments in one report and eight in the next because the reporting crew counted plate seams instead of design segments. The result is two beautiful data sets that cannot be subtracted from each other.
The fix is to define the grid origin against something permanent and physically findable: a manway centreline, a specific weld seam intersection, a nozzle, a permanently stamped datum punch. The record then holds the origin, the pitch, the axis convention and the numbering direction, and the job pack issued to the next crew carries the previous values pre-loaded square by square. A technician who can see that square C-7 read 8.2 mm last time and reads 4.1 mm now will stop and check rather than write it down and move on.
Pre-loading prior values has a second effect that surprises people. It changes the incentive structure of the field work. A crew collecting numbers into an empty template has no way to notice an error; a crew collecting against a prior map is effectively performing a continuous plausibility check, and the rate of transcription errors, misregistered grids and swapped axis conventions falls sharply. That improvement costs nothing except the ability to issue the history back out as a job pack, which is a capability worth testing in any demo.
The plate-replacement discontinuity
This is the failure mode that quietly destroys cement thickness histories, and it has no equivalent in a refinery piping circuit. Outage work replaces steel. A cone segment is cut out and a new one welded in. A worn duct panel is plated over with a doubler. A wear liner in abrasion-resistant plate is fitted where none existed. Each of these events changes the material, the nominal thickness and the retirement criterion at that location, and each of them breaks the arithmetic of any trend that runs through it.
Three specific errors follow. Replacing worn 6 mm steel with new 12 mm plate produces a negative wear rate at the next campaign; systems that clamp negatives to zero make the location look stable when it has actually been reset. Replacing carbon steel with a thinner abrasion-resistant grade produces an apparent step loss that triggers investigation into damage that never occurred. And a doubler plate welded over a thinned panel produces a UT reading through two plies with an air gap, which reads either as the outer ply alone or as an unstable echo, depending on fit-up.
The record therefore needs component-level events, not just readings: an installation event carrying date, material grade, nominal thickness, extent and the work order that produced it. The prior grid retires against the removed steel and remains available for historical analysis; a new baseline starts from the installation date. Retiring history rather than deleting it is the point. Ten years later, when you want to know how long the last cone lasted before replacement, the retired grid is the only place that answer lives.
Exclusions inside a fourteen-day window
A cement outage is a queueing problem in which inspection competes with refractory, mechanical and electrical work for the same access. Inspection is usually near the back of that queue because the areas it needs are the areas everyone else is working in. The consequence is that a meaningful fraction of the planned grid never gets measured, and the reasons are almost always about access and sequencing rather than about the steel.
Coded exclusions turn that into a manageable pattern. When the same eight squares on the same cyclone are skipped for build-up in three consecutive stops, the conclusion is not that the crew was lazy; it is that the cleaning sequence needs to put that cone ahead of the inspection window, or that a permanent access platform is justified. When the misses cluster around scaffold availability at a particular elevation, that is a planning input for the next outage's scaffold schedule, and it is worth real money because scaffold is one of the largest single cost lines in a stop.
Exclusions also protect the scoping decision itself. A component whose grid was eighty percent measured supports a confident replacement decision. One whose grid was thirty percent measured, with the missing squares concentrated in the region that historically wears fastest, supports no decision at all, and the honest output is a contingency plan and a pre-ordered plate rather than a false sense of coverage. That distinction is only visible if the misses were recorded.
Two methods, two quantities, one dangerous chart
Cement plants increasingly screen insulated ducting with pulsed eddy current, because it works through cladding and does not require lagging removal or full scaffolding. It is a genuinely valuable technique and it belongs in the programme. What it does not do is produce a number that can share an axis with a contact UT reading. Pulsed eddy current, applied per ISO 20669, reports an average wall thickness over the probe footprint, referenced to a calibration on nominal material. Contact UT per ASTM E797 reports the thickness under a probe a few millimetres across.
On uniformly corroded plate the two agree reasonably well. On the scoured, patchy loss that cement ducting actually suffers, the PEC average sits well above the UT minimum, and by a margin that depends on how localised the scour is, which is exactly what you do not know in advance. Plot a PEC value from 2023 and a UT value from 2026 on the same trend line and the chart shows a loss event that is entirely an artefact of the method change. The reverse ordering shows reassuring growth.
The discipline is simple to state and easy to enforce once the method is on the reading row: series are per method, screening results drive follow-up rather than trending, and a component's retirement decision is taken on the measurement type its criterion was written for. Any system that lets you build a single trend across mixed methods without a warning is a system that will eventually be used to make a wrong call about a cyclone.
From history to a scope list, a steel order and a crew plan
The output that justifies the whole exercise is not a thickness report. It is a ranked scope list that answers a question with a hard deadline: which components will reach their replacement criterion before the outage after next, given the wear rate measured on their own grid and the plant's confirmed stop calendar. That framing forces two things most inspection reporting omits. It forces a date for the next window and the one after it, and it forces the wear rate to be expressed per square with a confidence that reflects how much of the grid was actually measured.
From that list falls everything else. A materials take-off with grade, thickness, extent and lead time, driving purchase orders raised months ahead of the stop. A labour estimate in welder-days and scaffold square-metres. A decision on whether a component is plated, part-replaced or fully replaced, which is often the difference between four days and eleven days of critical path. And a residual list of components that were measured too thinly to decide, which is the honest input to the next campaign's inspection scope.
The loop closes when this outage's plan becomes next campaign's job packs, pre-loaded with prior values and issued to whichever crew is on site. Atlantis implements this as a working cycle rather than a reporting module, alongside ASNT Level III consulting and independent report validation. Affordable, accessible and fully customisable to your component hierarchy and site conventions; a demo or consultation can be requested at info@atlantisndt.com.
Why does cement thickness data live on a grid instead of CMLs?
Because the damage is areal, not point-based. Abrasion in a riser duct elbow scours a patch a metre across on the outer radius while the inner radius stays near nominal. A handful of condition monitoring locations chosen for a pressure vessel would miss it entirely or sit inside it and condemn the whole component. A grid on a 300 to 600 mm pitch produces a wear map, and the map is what tells you whether to plate a panel or replace a segment.
What happens to the history when a cyclone cone is replaced?
The old grid must retire with the steel it belonged to. If the history stays attached to the geometric location, the next campaign compares a new 12 mm plate against a worn 6 mm reading and computes a negative wear rate, or compares a thinner abrasion-resistant replacement against a thicker carbon-steel original and computes a rate that looks alarming. The record needs a plate installation event with date, material, nominal thickness and a fresh baseline from that date forward.
Can pulsed eddy current readings be trended against UT readings?
Not directly. Pulsed eddy current returns an average wall thickness over a footprint that may be 50 to 100 mm across and is calibrated against a reference; contact UT returns a point thickness under a probe a few millimetres wide. On plate with localised scour the PEC average is systematically higher than the UT minimum. Trending one against the other manufactures either a wear event or a false reassurance. Store the method, and trend each series against itself.
How far ahead of the outage does the scope actually get set?
Earlier than most people expect. If a preheater segment needs new plate, the sequence is scope freeze, engineering, material enquiry, purchase order, mill or stockist lead time of roughly six to fourteen weeks, fabrication and delivery to site before the scaffold is built. Working backwards, the decision is typically taken four to six months before the window opens, from data gathered at the previous stop, which may be twelve months old by then.
What counts as a valid reason to skip a grid square?
Build-up not removed, refractory still in place, surface temperature above the couplant rating, plate too rough or scaled to hold a backwall echo, scaffolding not built to that elevation, confined space permit not issued, and the square falling on a stiffener, weld or patch where the parent-plate reading is meaningless. Each needs a code rather than free text, because the coded pattern is what justifies fixing access before the next stop.
Which cement components deserve a full grid rather than spot checks?
Anything where failure means unplanned downtime measured in days and where the loss is areal: cyclone cones, riser duct elbows and transitions, the kiln hood, cooler casing above the grate, and cold-end ducting subject to dew-point attack. Spot readings are defensible on chutes and transfer points where a wear liner is a consumable with a short, well-understood life. The distinction is whether you are managing a replacement schedule or a wear-part inventory.
Built for any business that runs on operations
Most companies do not fail at their craft. They lose time, margin and goodwill in the gaps between the tools they use to run the place — a quoting spreadsheet that does not talk to the job sheet, a job sheet that does not reach accounts, and a compliance folder nobody can search when a client asks. Atlantis closes those gaps by putting the whole operation on one platform, so information is entered once and everything downstream stays in step.
What you can run on it
- Sales and CRM — leads, quotes, follow-ups and the pipeline that tells you what next month looks like.
- Projects and job costing — plan the work, track the hours and materials against it, and see the margin while the job is still live rather than at final account.
- Field and service teams — dispatch, schedules, mobile capture that works with no signal, and sign-off from site.
- Inventory and purchasing — stock, suppliers, reorder points and goods receipt, joined to the jobs that consume them.
- People — records, qualifications and licences with renewal reminders, timesheets, leave and payroll.
- Quality and documents — procedures and forms under revision control, with the audit trail an inspection or accreditation body actually asks for.
- Accounts — invoicing, expenses, multi-currency and the reporting your accountant stops chasing you for.
Affordable, accessible, fully customizable — and we mean each word
Affordable because the whole suite is included rather than sold to you a module at a time, and because implementation is done by people who have run operations rather than by a chain of subcontractors. Accessible because it runs in a browser and on a phone, works for a small team on day one, and does not need a specialist on staff to keep it alive. Fully customizable because your process is the thing that makes you competitive — the software should bend to it, not the other way round.
Industries we configure for
Service businesses and contractors, manufacturing and fabrication, trading and distribution, laboratories and testing houses, engineering consultancies, construction and facilities, and asset owners across energy, marine, aerospace and infrastructure. Inspection and testing is where we started, and it remains the sector we go deepest in — but the platform underneath is general-purpose, and most of what it does has nothing to do with inspection at all.
What happens when you get in touch
A short conversation, not a sales sequence. We ask how the business runs today and where it hurts, show you the platform doing that work, and send a written quote shaped to your region, your team size and the scope you actually need. No obligation, nothing to install first, and no pressure to decide on the call. Reach out and tell us what you are trying to fix.
Related: business management platform · inspection management software · choosing the right category of software · modules · by industry · asset integrity platform. Book a free consultation.