Open to work
DW

I build software
for plant problems.

✓ Built & used in a real plant See the work →

I work in inspection at a petrochemical plant. The tools I needed didn't exist, so I built them — and I write down how they're made, equation by equation. No guru talk. Just working software.

Open to: Asset Integrity · Inspection Planning · Industrial AI

~1,100 RBI tags assessed 10,936 ISO drawings tracked 67 damage mechanisms screened 1,300+ engine tests passing
Q32026
Q42026
Q12027
Q22027
Q32027
Q42027
R
RBI EngineAPI 581 calculator
Built & testingIN USE
D
DM Screener67 mechanisms
Screening liveLIVE
A
Agentic RBIAI copilot
ExploringSOON

Work

R

RBI Engine

IN USE

In-house API 581 risk-based inspection calculator — PoF, CoF, inspection planning. Every equation cited to the standard.

Outcome: replaced spreadsheet-based assessment for ~1,100 tags — inspection planning now risk-based, not gut-feel.

PYTHON · SQLITE · 1,300+ TESTS
D

DM Screener

LIVE

Screens 67 damage mechanisms per API 571, grouped by corrosion loop so assessments stay consistent.

Outcome: same mechanism, same verdict, every circuit — screening stops depending on who runs it.

API 571 · SCREENING
A

Agentic RBI

SOON

An assistant that answers "what should we inspect next?" straight from the RBI data. Early sketches.

Exploring: a copilot over live RBI data — inspection questions answered in seconds, with citations.

EXPLORING

Background

~10 years in oil, gas & petrochemical

Started in the field, now working in inspection planning at a petrochemical plant.

Metallurgy background

Engineering degree in metallurgy — comes in handy when a damage mechanism doesn't read the textbook.

Field → planning

Years of hands-on inspection before moving to planning: deciding what gets inspected, when, and why.

Say hello.

Ask about what I built — or just talk shop about inspection.

LinkedIn ↗

How I work

01

Verbatim to the standard

If a number can't be traced to API 581, it doesn't go in. Suspected errata get flagged, never silently "fixed".

02

Tested, not trusted

Every equation ships with a test. If the test doesn't pass, the feature doesn't ship.

03

Field-verified

What the model predicts, the field confirms. Software that never meets a plant is just a demo.