Loading experience…
Loading experience…
Legacy Application Modernization for US Boiler Manufacturers
US boiler and pressure vessel manufacturers frequently run quoting, calculation, and production logic on VB6 software built 15-20 years ago - a language Microsoft stopped supporting in 2008. On top of the usual legacy risk, US shops carry ASME BPVC, NB-23, and OSHA-driven audit exposure that a modern insurance carrier or Authorized Inspector will eventually flag. This page covers what that risk looks like in a US regulatory context and how a phased migration works without stopping production.
Why This Matters Now
VB6 lost official Microsoft support in 2008. Any vulnerability discovered since then has no fix coming - a real exposure for plants that need to pass IT security review as part of insurance underwriting.
Windows 10 reached end of life in October 2025. VB6 applications on US plant floors that relied on compatibility shims to keep running often break as those shims get tightened under modern security hardening.
The people who understand both the VB6 codebase and how it maps to National Board Inspection Code requirements are a shrinking pool - when they leave, the logic tying quoting output to compliance documentation often leaves with them.
Discount rules, material substitutions, and tolerance calculations often exist only in the VB6 code, with no separate record of how they tie back to Manufacturer's Data Report requirements.
ASME BPVC
Section I & IV calculation logic
NB-23
National Board Inspection Code recordkeeping
OSHA 29 CFR 1910
Workplace pressure equipment provisions
State Boiler Law
Jurisdictional AI & state inspection alignment
Three Real Options
A full rewrite, an automated conversion, and a hybrid API wrap each solve a different problem. The right one depends on how much of your business logic is documented, how much downtime you can tolerate, and how much of the current system genuinely needs to change.
Rebuild from scratch on a modern stack
Redesigned and rebuilt on a modern web stack, with ASME Section I/IV logic re-implemented from a documented spec rather than reverse-engineered from old code. Cleanest long-term architecture, highest risk of missing undocumented compliance rules.
Best when: The current system is small, poorly suited to today's quoting volume, or the compliance logic is already well-documented outside the code.
Watch out for: Skipping a proper audit means ASME edge cases - like which section governs a borderline pressure/temperature combination - tend to surface late, in production or during an audit.
Tool-assisted code translation
Automated tools translate VB6 into C# or VB.NET, preserving the original calculation logic - including whatever ASME table lookups and thickness formulas are already embedded. Faster than a rewrite, but roughly a third to half of converted code on complex systems needs manual tuning.
Best when: The codebase is large, the compliance logic has been tested against real inspections for years, and preserving exact behavior matters more than a redesign.
Watch out for: Automated tools handle routine code well but struggle with proprietary calculation logic - human review against actual ASME requirements isn't optional.
Modernize the edges, keep the core running
Existing VB6 quoting and calculation logic stays in place, wrapped in a modern API so ERP integrations, mobile access, and audit-tracking dashboards can connect without touching the legacy code directly.
Best when: The plant can't tolerate downtime and the priority is giving the team (and auditors) modern access to a system that's still calculating correctly.
Watch out for: Buys time and reduces risk, but the underlying VB6 code still needs a real plan before the next Windows compatibility break.
US Boiler & Pressure Vessel Compliance
Section I applies to fired and unfired steam boilers above 15 psig; Section IV covers heating boilers at or below 15 psig steam, or 160 psi/250°F hot water. Calculation logic can be built to reflect the sections that actually apply to your equipment instead of manual table lookups.
National Board Inspection Code recordkeeping - repair and alteration history, R-stamp documentation - is a common gap in manual VB6 workflows. A modernized system can track this alongside the quoting and production data it's already generating.
Certificate expirations, inspection records, and Manufacturer's Data Report tracking (Form U-1/P-1) are frequent audit failure points - not because inspections were skipped, but because the paperwork trail wasn't kept current in software that predates modern reporting expectations.
A Note on ASME BPVC and NB-23
ASME BPVC and the National Board Inspection Code (NB-23) aren't the same document, and US shops get audited against both. BPVC governs how the equipment is designed and built; NB-23 governs inspection, repair, and alteration after it's in service.
Software that only encodes BPVC section logic but has no way to track NB-23 repair history leaves a gap that shows up during an insurance carrier's periodic review, not during design. Calculation logic and recordkeeping need to be built against both.
How the Migration Works
Timelines vary depending on codebase size and which modernization approach fits best - the audit is what determines that, not a fixed promise made before anyone's looked at the code.
Weeks 1-2
We review the existing VB6 code and current workflow, mapping business logic against ASME BPVC and NB-23 requirements to flag undocumented rules and audit exposure, not just technical risk.
Varies by scope
Based on the audit, we recommend rewrite, automated conversion, or hybrid API wrap, and build against a written scope covering both functional and compliance requirements.
Final phase
The new system runs alongside the existing one and is verified against real production and inspection data before cutover. Your team keeps working on the current system throughout.
FAQs
Next Step
A short review of the existing code and workflow is enough to tell whether a rewrite, an automated conversion, or a hybrid API wrap makes the most sense - before any commitment to a build.
Book a Legacy System ReviewNo obligation. NDA available on request.