About · Built by one chemical engineer
§01who
Spent four years at Materia Inc on DCPD-based ROMP thermoset (acquired by ExxonMobil), then transitioned into mechanical integrity and process safety consulting through ARPE Engineering. Field exposure to API 510 / 570 / 579 / 580 / 653 inspection programs across chemical, petrochemical, and specialty industrial facilities. PSM, RMP, HAZOP, LOPA, MOC are native vocabulary, not borrowed buzzwords.
ComplianceOS exists because the market jumps from "Excel + tribal memory" straight to "five-figure annual SaaS." For a 100-person specialty chemical plant under 1910.119, both options are wrong. This is the in-between.
§02why
Three patterns I kept seeing inside operating PSM programs:
/ 01
A new EHS or operations lead walks into a PSM program built by the last three people. They have no idea where the 1910.119(d) PSI is incomplete or which MOCs are mid-flight. Audits get scheduled before they know what they own.
/ 02
The compliance matrix lives in a single Excel file edited by five people over eight years. Half the cross-references are broken. Nobody trusts it before an audit, so the week before the inspector arrives, somebody rebuilds it from memory.
/ 03
The enterprise alternatives (Cority, Sphera, Intelex) require security review, vendor onboarding, multi-user configuration, and a six-month implementation. None of which fits the window between "we just realized our HAZOP is five years stale" and "the auditor lands Tuesday."
§03trust
There is no support tier, no ticket queue, no "your message is important to us." Every report PDF is signed by me. Every email comes from a real inbox. If a finding looks wrong, reply and I will read it within the hour during business hours.