$165,514. That’s the 2026 OSHA maximum fine for a single willful PSM violation. And the fastest way to get one? Outdated engineering standards in your process hazard analysis. RAGAGEP — “Recognized and Generally Accepted Good Engineering Practice” — is not a suggestion. It’s a regulatory requirement under 29 CFR 1910.119. Here’s how to check your facility’s RAGAGEP currency in under a day.
Step 1: Inventory Every Engineering Standard Referenced in Your PHA
Pull your PHA documentation and list every engineering standard referenced. API 510, API 570, API 653, ASME VIII, ASME B31.3, NFPA 30 — whatever your facility cites. Make a simple two-column table: standard name and edition year. This should take 30 minutes for a typical process unit. If it takes longer, that’s your first red flag — it means nobody has a clean index.
Step 2: Check Each Standard Against the Current Published Edition
API 510 is on the 10th Edition. API 570 is on the 4th Edition. ASME VIII Div. 1 is the 2023 edition. ASME B31.3 is 2022. If your PHA references API 510 9th Edition or ASME VIII Div. 1 2019, you have a gap. RAGAGEP requires “latest edition” unless your facility has a documented technical justification for not adopting the update. Most facilities don’t have that documentation.
Step 3: Identify Which Revisions Actually Changed the Math
For each gap, check the revision summary in the new edition. Not every revision changes the calculations. Some are editorial. Some add new appendices. Some change allowable stress values or inspection interval formulas. The ones that change calculation results or inspection requirements are the ones your auditor will flag. Prioritize those. API 510 10th Edition, for example, restructured the entire inspection planning approach — that’s not editorial.
Step 4: Cross-Reference Your Mechanical Integrity Program
If you’re using thickness data from UT inspections and calculating remaining life per API 510 formulas, make sure the formula edition matches your PHA edition. I’ve seen facilities where the PHA cites API 510 9th Edition, but the MI program uses 10th Edition formulas. That inconsistency is exactly what a compliance auditor looks for — it suggests nobody is managing the document chain.
Step 5: Document Everything in a RAGAGEP Currency Register
Create a RAGAGEP currency register — one table showing every standard, current edition, your facility’s edition, gap status, and action plan. Update it annually, minimum. This register becomes your audit defense document. It shows the auditor that you’re managing RAGAGEP proactively, not reactively.
NORMEX Standards AI automates this entire process — upload your standards, get a gap analysis with specific section-level findings in hours instead of weeks. But even without AI, the manual process above takes one engineer one day per process unit. That day of work could prevent a six-figure citation.
What’s the oldest engineering standard edition still referenced in your PHA documentation?