SMEPro turns the regulatory catalog — production reports, completions, permits, transfers — into a living calendar with in-form validation, agency-grade EDI output, and hard gates on the mistakes that cost real money.
The catalog, the calendar, the validators, and the audit trail live in one place — so the answer to "are we current?" is a query, not a meeting.
Deadlines generate themselves from agency rules — monthly PRs, post-completion windows, renewal cycles — per asset, per jurisdiction, with the legal basis on every row.
Field schemas and cross-field rules mirror agency edits. Blocking errors stop a bad filing before it leaves the building; warnings ride along for review.
A spud event with no approved W-1 on file raises an overdue, blocking obligation the moment it's recorded. Validation before drilling is the design, not an afterthought.
Accepted payloads render to agency EDI formats line-for-line — RRC production report EDI today — ready for upload, with problems surfaced per line.
Every form carries a verification status against primary sources. You always know whether a rule is confirmed, pending, or changed — and when it changed.
Obligations and submissions are append-audited in the database itself. Who filed, what version, which validator findings — reconstructable for any examiner.
Your workspace is provisioned against your P-5 operator number (or state equivalent). Sign in, invite your filers.
Wells, leases, and facilities load from your existing exports. The deadline engine generates the obligations they carry — nothing to configure by hand.
Work the calendar: validate, submit, attach the agency confirmation number. Rows leave the calendar only when the agency says so.
Deep where our operators file today. Cataloged — and clearly labeled — everywhere else.
PR Monthly production — schema, validators, EDIW-1 Drilling permits + pre-spud gateW-2/G-1 Completions · P-4 transfers · W-3 pluggingMEFC, RAMP DA, SADMS-PROD, MS-PERMIT, MS-COMPLETION catalogedneeds_verification in the interface until our stewardship
process confirms them. You will never mistake a draft rule for a confirmed one.
Row-level security pins every query to your organization — app.current_org is set from a verified token, never from client input. Cross-tenant reads are impossible by construction.
bcrypt-hashed credentials verified in-database; short-lived signed JWTs carry your org claim. Secrets live in GCP Secret Manager, not in code.
Obligation and submission changes are written to an audit log by database triggers — the application can't forget to record them.
Stateless API on Cloud Run, managed PostgreSQL on Cloud SQL, scheduled deadline generation via Cloud Scheduler. Scale is horizontal and boring — the way you want it.
Use the admin account provisioned for your organization.