When the mill's thickness workbook outgrows the people editing it
A remaining life and interval engine recomputes each vessel, tank and piping circuit's next inspection date from its own thickness history under API 510, 570 or 653, instead of storing a date somebody typed. In a pulp mill that matters because digesters, recovery boilers, liquor tanks and bleach plant lines run under four different inspection codes at once, and a single workbook column applies one rule to all four.
The distinguishing constraint in a pulp mill is that the equipment file spans four inspection regimes at once. Continuous digesters and impregnation vessels are Section VIII Div. 1 vessels under API 510. Liquor storage sits under API 653 where the tank was built to API 650. Bleach plant, brownstock and liquor piping is API 570. The recovery boiler is a Section I pressure part whose interval is set by the jurisdiction and the National Board Inspection Code, with BLRBAC practice layered over it. A single next-due column in a workbook applies one rule to all four. Beyond the code split, two mechanisms defeat corrosion-rate arithmetic outright: caustic stress corrosion cracking in digester weld heat-affected zones, which consumes no measurable wall until it opens; and the FRP, rubber-lined and titanium equipment that fills a chlorine dioxide bleach plant, for which no minimum thickness exists to divide into. An interval engine for this industry must carry calculated, cracking-driven and condition-based intervals in the same register.
Source: Sources: API 510 for vessel inspection intervals and remaining-life rules; API 570 for piping circuit classification and intervals; API 653 for tank external and internal intervals; API 571 for caustic stress corrosion cracking; API 579-1/ASME FFS-1 for fitness-for-service justification; ASME BPVC Section VIII Div. 1 and Section I for construction basis; NBIC NB-23 for in-service power boiler inspection; BLRBAC Recommended Rules for recovery boiler practice; TAPPI's 0402-series Technical Information Papers on digester inspection; ASTM D2563 for FRP visual acceptance; OSHA 29 CFR 1910.119(j) for mechanical integrity recordkeeping.
| Asset class | Governing in-service practice | Dominant damage | What actually sets the interval |
|---|---|---|---|
| Continuous digester and impregnation vessel | API 510, on ASME VIII Div. 1 construction | Caustic SCC in weld heat-affected zones; overlay disbondment; thinning at the outlet device | Crack-detection coverage and indication sizing, not a corrosion rate |
| Black, white and green liquor storage tanks | API 653 where built to API 650 | Bottom-side corrosion, shell thinning at the liquid line, settlement | Bottom corrosion rate plus release prevention barrier and leak detection status |
| Bleach plant and filtrate piping | API 570 | Chlorine dioxide and chloride attack; erosion-corrosion at elbows and valve outlets | Short-term corrosion rate following any chemistry change |
| Recovery boiler pressure parts | Jurisdiction and NBIC NB-23, with BLRBAC practice | Lower furnace composite tube thinning and cracking near air ports; floor tube attack | The operating certificate cycle and defined UT grids |
| FRP towers, chests and ducting | No code interval; owner-user written practice | Resin attack, blistering, delamination, glass exposure | Condition assessment result and the assessor's judgement |
| Rubber-lined tanks, chests and acid vessels | Owner-user practice, then API 653 once the liner fails | Liner holiday followed by rapid steel attack — a step function | Holiday and spark test results, not a thickness trend |
Four inspection codes, one equipment file
A pulp mill's fixed-equipment register looks homogeneous in a spreadsheet and is nothing of the kind. The continuous digester and the impregnation vessel are ASME Section VIII Div. 1 pressure vessels inspected under API 510. The black, white and green liquor storage tanks are welded storage tanks and, where they were built to API 650, they fall under API 653. The bleach plant, brownstock and liquor piping is API 570 territory. The recovery boiler and the power boilers are none of these: they are Section I pressure parts, and their in-service inspection is governed by the jurisdiction and the National Board Inspection Code, with BLRBAC's recommended rules layered on top for anything that could put water into smelt.
Those four regimes do not share an interval rule. API 510 caps the internal or on-stream inspection at the lesser of half the remaining life or ten years. API 570 puts a Class 1 piping circuit at five years or half the remaining life, whichever is shorter, and lets a Class 3 circuit run longer. API 653 sets the external visual at five years or a quarter of the computed bottom life, whichever is less, and holds the internal interval to a twenty-year ceiling that only a risk-based assessment can extend. A boiler's interval is usually annual because the jurisdiction says so, and no arithmetic will change that.
So the honest version of next due is four different functions of the same asset record. A workbook has one formula per column. The moment the mill's equipment list grows past a couple of hundred lines and more than one person maintains it, the four regimes flatten into whichever rule the last editor understood best. That flattening is invisible, because every row still shows a plausible date.
What actually breaks in a shared workbook
The failure is rarely a wrong number. It is that nobody can say where a number came from. Excel stores the value; it does not store the provenance. When a reliability engineer opens the register and finds a digester circuit carrying a corrosion rate of 0.004 inch per year, there is no way to tell whether that cell still contains the formula that divides loss by elapsed years, or whether somebody pasted a value over it three outages ago because the formula was returning a negative and the sheet looked broken.
Multi-editor sheets fail in a recognisable sequence. First the previous-thickness column gets overwritten at each outage instead of appended, so the long-term rate becomes uncomputable after two cycles. Then CML identity drifts: Elbow 3, east in one submission and E-3E in the next become two rows describing the same point, each carrying half a history and neither producing a rate. Then somebody sorts a range without extending the selection, and the readings detach from their tags — the most destructive spreadsheet error there is, because it produces plausible numbers everywhere and an error message nowhere.
The regulatory version of the same problem is sharper. OSHA's mechanical integrity rule at 29 CFR 1910.119(j)(4)(iv) requires that each inspection and test record identify the date, the name of the person who performed it, the identification of the equipment, a description of the test and the results. A shared workbook has no per-cell authorship. At a mill where the chlorine dioxide generator and its storage put the process over the thousand-pound threshold in Appendix A, that is not a housekeeping observation.
The short-term rate trap in a bleach plant
API 510 and API 570 both require the owner-user to compute a long-term and a short-term corrosion rate, and to use whichever predicts the shorter remaining life. Almost every spreadsheet computes only the long term, because that is the formula you write on day one: original thickness minus current thickness, divided by years in service. It is not wrong; it is incomplete in exactly the way that matters here.
Take a bleach plant washer filtrate line, nominal 0.375 inch, computed minimum thickness 0.180 inch, twelve years in service. The 2026 reading at the governing CML is 0.290 inch. The long-term rate is (0.375 − 0.290) ÷ 12 = 0.0071 inch per year, giving a remaining life of (0.290 − 0.180) ÷ 0.0071 = 15.5 years, and the interval falls out at the code ceiling. Now bring in the 2024 reading of 0.330 inch. The short-term rate is (0.330 − 0.290) ÷ 2 = 0.020 inch per year, the remaining life is 5.5 years and the interval is 2.75. Same asset, same file, a factor of five between the two answers.
In pulp bleaching that divergence is the normal case, not the pathological one. Chemistry moves — a shift in chlorine dioxide charge, a rise in recycled filtrate chloride, a washer run hotter to close the water loop — and corrosion rates move with it by a factor of several inside one campaign. The long-term average deliberately smooths out precisely the event you needed to see. An interval engine earns its keep by computing both rates on every circuit, every time, and by showing which one governed alongside the readings that produced it.
Digesters: cracking is not thinning
A continuous digester running white liquor at 160 to 175 degrees Celsius sits squarely in the caustic cracking region for carbon steel. API 571 describes the mechanism: cracking concentrates in weld heat-affected zones, at the liquor line, through the impregnation zone and around nozzle reinforcements. A crack does not consume wall at a rate. It initiates, then it propagates, and a thickness history taken through the same period looks flat and reassuring the entire time.
This is why digester inspection practice in the industry — the TAPPI 0402-series Technical Information Papers, and most mills' own written procedures — is built around surface crack detection on a properly prepared surface: wet fluorescent magnetic particle over the full weld network, supplemented by ACFM or EMAT where grinding is impractical, plus ultrasonic examination of the stainless weld overlay or clad layer for disbondment. The interval that comes out of that programme is not a function of remaining wall, and no amount of thickness data will produce it.
The engine has to model that honestly. A digester needs two intervals against one asset: a thinning-driven interval from wall loss where thinning genuinely occurs, in the overlay-free zones, the cone and around the outlet device; and a cracking-driven interval set by the date and extent of the last full magnetic particle coverage, the percentage of the weld network actually examined, and the indications carried forward with their last sizing. Whichever is sooner governs. Any product that hides a digester behind a single corrosion-rate field is describing a different vessel than the one you own.
The recovery boiler lives outside API 510 entirely
The recovery boiler is the single asset most likely to be mishandled in a mill spreadsheet, because it is the one everybody agrees is critical and the one API 510 does not govern. Its pressure parts are ASME Section I. In-service inspection authority sits with the jurisdiction and the National Board Inspection Code, and practice is shaped by BLRBAC's recommended rules, which exist because a smelt-water reaction is an explosion rather than a leak.
That produces obligations a corrosion-rate engine will never generate on its own: pressure-part inspection tied to the certificate cycle, defined ultrasonic grids on the lower furnace where composite tubing thins and cracks near the primary air ports and smelt spout openings, floor tube inspection on a documented pattern, and specific attention to anything that could put water into the char bed. None of that is derived from remaining life. All of it has a date, a defined extent and a named owner.
What the mill needs from software here is not a calculation but a container: the boiler's inspection items modelled as scheduled requirements, each with its own basis, its own evidence and a link to the certificate that lapses if the item is not completed — sitting in the same register as the vessels, tanks and piping, so that show me everything due in the March outage returns a complete answer rather than the API-governed subset of it.
Assets with no thickness model at all
A modern bleach plant is substantially FRP, rubber-lined steel and titanium. Chlorine dioxide stages consume carbon steel and most stainless grades fast enough that mills abandoned them decades ago. For that equipment there is no required minimum thickness, no corrosion rate and no remaining-life arithmetic to perform. API 570 and API 653 have nothing at all to say about a filament-wound FRP tower or a rubber-lined chest, and any system that forces one into a corrosion-rate field is producing a number with no meaning behind it.
The damage is a step function rather than a trend. A rubber-lined acid or filtrate tank corrodes at essentially zero until the liner holidays, and then at a rate set by the exposed steel and the liquor, which can be an order of magnitude faster than anything in the trend history. FRP degrades by resin attack, blistering, delamination and glass exposure, assessed visually and by Barcol hardness, acoustic emission where appropriate, and mechanical thickness measurement where the laminate allows, against acceptance criteria of the ASTM D2563 type.
The evaluation question for a buyer is simply whether the product can hold a condition-based interval alongside a calculated one — with the condition scale, the last assessment, the assessor, the findings and the next date — and whether past due means the same thing on both. If the FRP and rubber-lined equipment ends up living in a comment field, the mill has rebuilt the spreadsheet inside a database and paid for the privilege.
Snapping computed intervals to the outage calendar
Mills run one annual cold outage, sometimes a second shorter one, and a handful of departmental shuts. Nothing pressure-retaining opens outside them without a production decision that is made well above the inspection group. So the useful output of an interval engine in this industry is not a date. It is an outage.
The arithmetic is unforgiving in one direction only. If a vessel's computed interval is 6.4 years and the outage cadence is annual in March, the answer is the sixth March, not the seventh — rounding up spends 0.6 years of margin you just calculated. If the interval comes out at 1.2 years and there is only one outage a year, no window satisfies it, and the honest output is a flag: this asset needs an off-cycle opening, a mitigation such as monitoring or a rate reduction, or a fitness-for-service assessment under API 579-1/ASME FFS-1 that justifies running to the next window.
This is where spreadsheets fail in the most comfortable way possible. The planner slides the date to the next convenient outage because the alternative is a difficult conversation with operations, and no record is kept that the slide happened or that it consumed margin. The engine should compute the code date, snap it, display the gap, and require a named approval for any snap that pushes past the calculated date. Nothing is prevented; everything is visible.
Evaluating an interval engine before you commit
Ask for a reproduction, not a demonstration. Give the vendor three of your own assets — a digester circuit with a real overlay history, a bleach line with a chemistry change buried in it, and a liquor tank with a patched bottom — and ask the product to produce the next date together with the full chain that got there. If the chain cannot be read and verified by your Level III without a support call, the mill has not solved its reproducibility problem; it has relocated it into someone else's software.
Then push on the awkward cases, because they are the ones that occur weekly. A negative corrosion rate. A replaced spool nobody logged. A CML retired because the fitting was cut out. A reading taken by a technician whose certification expired the week before. A due date that has already passed with a written deferral behind it. Every one of these exists in your workbook right now, and every one is a place where a product either has a defined, recorded behaviour or quietly guesses on your behalf.
Atlantis builds the interval engine on Odoo, so the equipment register, the outage plan, the contractor purchase orders and the technician certification records live in one database rather than three. Affordable, accessible, fully customizable — the calculation rules for a digester circuit or a recovery boiler inspection item are configured against your written procedure rather than fixed by ours. For a working session on your own equipment list, contact info@atlantisndt.com.
Does API 510 set the inspection interval for a kraft recovery boiler?
No. A recovery boiler's pressure parts are built to ASME Section I, and in-service inspection authority sits with the jurisdiction and the National Board Inspection Code rather than API 510, with BLRBAC's recommended rules shaping practice around smelt-water risk. The interval is normally tied to the operating certificate and an annual pressure-part inspection, not to a computed remaining life. A mill's register has to hold both kinds of basis side by side without pretending they are the same calculation.
Why does a long-term corrosion rate under-report a bleach plant line?
Because the long-term rate averages the whole service life, and bleach plant corrosion moves in steps. A change in chlorine dioxide charge, a rise in recycled filtrate chloride, or a washer run hotter to close the water loop can multiply the rate inside a single campaign. API 510 and API 570 both require a long-term and a short-term rate, with whichever gives the shorter remaining life governing. Spreadsheets almost always compute only the long term, because that is the formula you write first.
How should a digester with caustic cracking be intervalled?
By detection coverage, not by wall loss. Caustic stress corrosion cracking concentrates in weld heat-affected zones and consumes no measurable thickness, so a corrosion rate stays silent right up to the point a crack goes through-wall. The defensible basis is the extent and effectiveness of the last surface crack examination — typically wet fluorescent magnetic particle over ground welds, with ACFM or EMAT where grinding is impractical — together with the sizing of any indications carried forward from the previous outage.
What interval basis applies to FRP and rubber-lined bleach plant equipment?
None of the thickness codes apply, because there is no required minimum thickness to divide into. FRP is assessed on visual condition, Barcol hardness, delamination and glass exposure against acceptance criteria of the ASTM D2563 type. Rubber-lined vessels are assessed by holiday and spark testing, because the steel behind an intact liner corrodes at effectively nothing and then extremely fast. The engine needs condition-based intervals sitting in the same register as calculated ones, with past-due meaning the same thing on both.
Is API 510, 570 or 653 inspector certification training part of this offer?
No. Atlantis supplies inspection management and reporting software, digital twin platforms, 3D laser scanning, ASNT Level III consulting and independent report validation, together with NDT method training to ASNT SNT-TC-1A and ISO 9712 at Levels I, II and III across UT, RT, MT, PT, ET, VT, PAUT and TOFD. API's individual inspector certifications are issued through API's own certification programme; the software stores those credentials and monitors their expiry, but does not confer them.
What happens when a computed interval falls between mill outages?
The engine should compute the code date, snap it to the nearest preceding outage, and display the margin surrendered by that snap. If no outage satisfies the interval, that is a flag rather than a rounding decision: the asset needs an off-cycle opening, a mitigation, or a fitness-for-service assessment under API 579-1/ASME FFS-1 justifying operation to the next window. Any snap that pushes past the calculated date should require a named approval rather than a quiet edit.
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.