SPCC · SWPPP · RCRA · Title V · UST · FRP
Every requirement VRM extracts, traced to the document it came from.
VRM reads your permits and plans, extracts the obligations inside them for your team to review, and schedules the accepted ones as dated tasks, which customers see with their status. Keeping the evidence that each one was met is shown in the demo and not yet connected.
The demo runs on sample data, and access to it is by request.
One requirement, end to end
40 CFR 112.8(c)(6)
Monthly SPCC Visual Inspection
- DocumentsSPCC_Plan_Baytown_2025.pdf87 pages
- AI Extraction“Visually inspect all aboveground containers and associated piping for leaks, corrosion, or other deterioration monthly.”extracted as 40 CFR 112.8(c)(6)
- Requirements RegisterMonthly SPCC Visual Inspectionfederal · high criticality · active
- Task SchedulingMonthly SPCC Visual Inspection — July 2026monthly, 3-day grace · due Jul 15, 2026
- Field ChecklistsSPCC Monthly Visual Inspection Checklist8 items, each with its own acceptance criteria
- Non-Compliance AnalysisIncomplete June SPCC Inspection Documentationmedium severity · in corrective action
- ReportsNon-Compliance Analysis Report — Baytown Refinery Complex — June 2026cites 40 CFR 112.8(c)(6) as the regulatory basis
Sample data — Gulf Coast Industrial Services is a demonstration company in the shipped demo dataset, not a customer.
How it works
Seven stages, in order
Each stage hands the next one something it can act on. Today a customer's document becomes requirements for review, and an accepted requirement becomes dated tasks, which customers see; in the demo, a task then becomes a checklist somebody completed, and every one of those still points back at the citation it started from.
Documents
Upload the regulatory documents you already hold — permits, plans and SOPs.
AI Extraction
AI agents parse each document and extract its inspection, testing and training obligations, each kept with the document it came from and the citation and source text the extraction found.
Requirements Register
Extracted requirements land in the review queue for a compliance specialist or an admin to review, versioned with append-only history.
Task Scheduling
The scheduling engine resolves calendar, rolling and multi-year frequencies into concrete dated tasks, every day; event-triggered ones are read but not scheduled. Customers see the tasks and their status.
Field Checklists
In the demo, field staff complete the checklist on a phone and attach evidence to the item it belongs to; the field app is not yet connected for customers.
Non-Compliance Analysis
A non-compliance is recorded automatically, with a severity, when an inspection for an active requirement is marked overdue without having been marked complete, or by a specialist or an admin from the requirements register. Customers see their non-compliances in the app, where each can be given an owner, a corrective action and a target date, and only a specialist or an admin can close one as verified. One recorded for an inspection is resolved when that inspection is recorded as verified or closed; nothing in the app records that yet.
Reports
Reports come in four templates — the requirements register, a non-compliance analysis, a compliance roadmap and a site assessment — but the app cannot request one yet.
The walkthrough
See it running, in the demo
The walkthrough drives the live demo — the application’s own screens on sample data, in a browser, not a video of one. Two of its seven screens are not yet connected for customers. It cannot go stale, because there is nothing to re-record when the product changes.
Chapters
- DocumentsIt starts with the documents you already hold — permits, plans and SOPs, uploaded as files.
- AI ExtractionAI agents read each document and extract its obligations, each kept with the document it came from and the citation the extraction found.
- Requirements RegisterNothing goes live unreviewed. Extracted requirements land in the review queue for a compliance specialist or an admin to accept, amend or reject first.
- Task SchedulingThe scheduling engine resolves calendar, rolling and multi-year frequencies into concrete dated tasks every day; event-triggered ones are not scheduled. Customers see the tasks and their status.
- Field ChecklistsIn the demo, the inspector records pass, fail or not-applicable against each item’s own acceptance criteria; the field app is not yet connected for customers.
- Non-Compliance AnalysisA non-compliance is recorded automatically when an inspection for an active requirement is marked overdue without having been marked complete, or by a specialist from the register, and can be given an owner, a corrective action and a target date — not a red cell on a spreadsheet.
- ReportsReports come in four templates — the requirements register, a non-compliance analysis, a compliance roadmap and a site assessment — but the app cannot request one yet.
Chapters are read from the tour script the player runs, so this list is what the walkthrough actually does — not a description of it.
Who uses it
Four views of the same register, in the demo
One dataset, four jobs, as the demo shows them. A specialist reviewing what was extracted, a manager watching posture facility by facility and executive leadership watching it across every facility are what customers can do today; a field operator working a checklist on a phone is not yet connected for customers.
Compliance Specialist
The dashboard, document management, the review queue, the requirements register and non-compliance tracking; reports are not yet connected for customers.
/app/admin
Manager
The compliance posture dashboard, inspection status, documents, and non-compliances with their corrective actions; reports are not yet connected for customers.
/app/client
Executive Leadership
Every facility on the account, for portfolio-level posture.
/app/admin
Field Staff-Operator
Task list and inspection checklists with evidence capture — not yet connected for customers.
/app/field
Programs
Six example programs, each parsed on its own terms
A SWPPP and a Title V permit do not hide their obligations in the same places, so they are not read the same way. Each of these six document types is extracted with a prompt written for that type.
- SPCCSpill Prevention, Control, and Countermeasure
Extracted for
- Plan Updated Within 5 Years Of Initial Issue or Last Update
- Facility Information
- Management Approval (Signature / Date)
- SWPPPStormwater Pollution Prevention Plan
Extracted for
- Identification of the Stormwater Pollution Prevention Team by name/title, with individual responsibilities
- Signed certification statement
- Site description: Narrative description of industrial activities at the facility
- RCRAContingency plan and hazardous waste management
Extracted for
- Hazardous Waste Written determination of Generator Status (VSQG, SQG, LQG)
- Waste Generator Requirements
- Hazardous Waste Identification
- Title VAir permit
Extracted for
- General Permit Applicability
- Permit Term Valid
- Renewal Requirement Date
- USTUnderground Storage Tank
Extracted for
- Tank Registration - Permit
- Release Detection
- Spill And Overfill Protection
- FRPFacility Response Plan
Extracted for
- Emergency response action plan (112.20(h)(1))
- Facility information (112.20(h)(2))
- Information about emergency response (112.20(h)(3))
Which programs apply to a given site is determined by that site’s permits and its own counsel. VRM tracks the requirements you register; it does not decide which regulations you are subject to.
The practice
Our HSSE practice is led by Ron Gemeinhardt
Forty-five years in the petroleum industry and research, from the field to executive boards.
Ron Gemeinhardt, MSES, has been a Shell Oil Company staff manager and support to field operations, FEMA NEPA response staff, and project manager for the ESG work that took a large recycler through International Sustainability & Carbon Certification.
His operating background runs through refinery operations, terminal operations, exploration and production, pipeline facilities and retail systems, with in-depth experience under the Incident Command System, RCRA, environmental remediation and safety compliance.
He has published numerous books on HSSE issues, including two focused on used oil management: the Texas Used Oil Management Guide and the Used Oil / Federal Management Guide.
His requirement checklists are written into the extraction rule sets the product runs, program by program.
Our permit read, offered on the contact page, means a permit provided is analyzed for all regulatory obligations that include a citation identified by him.
Next step
Tell us what you are carrying
Which programs, how many facilities, and where the current process hurts. We will read it and come back to you.
Documents · AI Extraction · Requirements Register · Task Scheduling · Field Checklists · Non-Compliance Analysis · Reports