One engine core holds the plant data, and every module works from it: damage-mechanism screening and assessment today, with IOW, RBI and the corrosion control document in development. A result in one module is available to all the others.
Corrosion studies usually live in separate spreadsheets: one for damage mechanisms, another for IOWs, another for RBI. In CorroNexus every module works from the same engine core, so what one module finds is used by the others. The engine is rule-based: the same input gives the same answer, and each result shows its reason.
The main dashboard. It holds the plant registers, process data and every module's results in one place, so each module reads what the others have found and writes its own result back.
Damage-mechanism screening for complete plant registers.
The back office of the engine.
Integrity operating windows.
Risk-based inspection.
The corrosion control document.
We ran the Stage-1 screener on the registers of five completed corrosion studies and compared its output, component by component, with the mechanisms the engineers had written. Only the counts are reported here. The client data stays on our own machines.
These figures measure agreement with the delivered studies, not absolute accuracy. Most of the remaining differences are client-specific choices, or inputs the registers never recorded, which the engine reports as missing data. The engine makes a proposal. The final decision stays with a qualified corrosion engineer.
What the engine contains is engineering logic: how materials, process conditions and components combine into damage mechanisms and the actions that follow. It does not copy the text, tables or numbering of published standards, and it does not hold material-property data. That makes it a good fit alongside materials databases, inspection systems and asset-performance platforms, which hold that data under their own licences.
The rules sit in editable files, with a Python reference version and a browser version that give identical results.
Damage-mechanism reviews, corrosion loops and circuits, IOW registers, corrosion control documents and RBI corrosion studies. The engine does the screening, and a senior corrosion engineer reviews and signs the work.
Every corrosion decision, from the wellhead to the refinery and petrochemical plant, should be based on data, easy to check, and repeatable.
To turn senior corrosion-engineering judgement into a tested engine, so that integrity decisions can be traced and defended, and do not depend on one person's spreadsheets or memory.
CorroNexus is a corrosion and asset-integrity engineering practice. Its method comes from more than 17 years of damage-mechanism reviews, RBI corrosion studies, IOWs and corrosion control documents, across the whole hydrocarbon chain. That method now sits in the engine, so every project gets the same senior approach, whoever runs it, and every result can be checked.
The methodology follows the recognised industry frameworks (API, AMPP, ASME). They are cited as the basis of the method, not as a claim of compliance or endorsement. No text, table, figure or numbering from a published standard is reproduced on this site or in the engine's output; users work from their own licensed copies.
Ask for a walkthrough of the engine, or get in touch about an integration or a corrosion study for your plant.