Your refinery shuts down for 32 days every 4 years. In that 32-day window, 1,400 contractors mobilize, 8,400 work orders execute, 12,000 permits-to-work get issued, and every extra day past plan costs you somewhere between $480,000 and $1.2M in lost throughput. If you run on SAP PM, here is the conversation your turnaround lead has been avoiding: SAP PM is excellent at financial integration. It is not built for STO execution. To run a refinery turnaround on SAP, most majors bolt on Prometheus STO Manager, ePAS for permits, a separate contractor system, and Primavera P6 for the schedule. Combined: $400K-$1.2M in additional license + integration cost, and you still spend the first 3 days of every STO chasing data between four systems. The honest comparison most SAP partners won't put on paper: SAP PM was built for general industrial maintenance. STO is a different sport. OxMaint is built for the sport. Book a free demo of refinery turnaround CMMS software.
The On-Prem Server Stack — STO Command Center, Behind Your Firewall
Refinery STO data is critical IP — turnaround scope, contractor rates, inspection findings, safety incident records. Three pieces of NVIDIA hardware sit in your turnaround command center, never connect to the public internet, and run your full STO + PTW + LOTO + contractor coordination platform. Book a free demo of refinery turnaround CMMS software.
EDGE · FIELD GATE
NVIDIA Jetson AGX Orin The Field Gate
JobContractor badge scan, PTW kiosk, LOTO verification
SpeedSub-second badge check at entry gate
WhereMounts at site entry + each unit work zone
FormRuggedized box, fits in field cabinet
What it does: Scans contractor badges at site entry. Checks safety orientation completion, training validity, PPE certification, and active permits before allowing zone access. Logs every entry/exit with timestamp for incident traceability.
COMMAND CENTER · STO CORE
RTX PRO 6000 Blackwell The STO Command Center
JobRuns STO planning + PTW + LOTO + contractor workflows
SpeedReal-time critical path · live tool-time tracking
WhereSits in your turnaround command center
FormTower computer, fits under a desk
What it does: Runs the full STO platform — scope freeze, work packages, contractor onboarding, PTW issuance, LOTO chains, scope addition impact analysis, real-time critical path. AI surfaces predicted overrun risk per unit.
ENTERPRISE · FLEET STO BRAIN
NVIDIA DGX Station GB300 · Fleet STO Brain
JobCross-refinery STO benchmarking + learnings
SpeedHistorical STO analysis in hours
WhereSits at corporate HQ in a server rack
FormRack-mounted, 24/7 enterprise grade
What it does: Aggregates STO performance data across all refineries. Surfaces what worked, what overran, which contractors hit on tool time, which scope additions could've been caught earlier. Next STO scope built from condition data + fleet learnings.
100%
Stays inside your plant · never goes online
$0/mo
No subscription · buy once, own forever
Offline
Works fully air-gapped if your team requires it
Yours
Source code included · modify it freely
The STO Execution Timeline — SAP PM Pain vs OxMaint Native at Every Phase
Refinery turnarounds follow six distinct phases from scope definition 6 months out to punch-list close on return-to-service day. Each phase has unique requirements where SAP PM forces bolt-on tools or manual workarounds. Here is where OxMaint ships native — and what each gap costs in days. Sign up free for refinery turnaround CMMS software.
P1
SCOPE DEFINITION & FREEZE · 6 MONTHS OUT
SAP PM
Scope built in SAP Project Systems (PS) + work-order lists. No native condition-data linkage. Scope freeze enforced via change order workflow. Typical scope-lock slip: 30-45 days.
OXMAINT
Scope built from condition data + RBI findings. Locked 90 days out before overrun window opens. Addendum process for any post-freeze additions. Standard config — no PS customization.
P2
WORK PACKAGE PLANNING & CONTRACTOR PRE-QUAL · 12 WK OUT
SAP PM
Work packages in SAP PM. Contractor pre-qualification in separate system (Avetta / ISN). Manual reconciliation between systems. Bolt-on Prometheus STO Manager often required.
OXMAINT
Pre-built refinery work package library. Contractor onboarding native — qualifications, certs, safety orientation, badging — issued 30 days before mobilization. One platform.
P3
PTW + LOCKOUT/TAGOUT · DAY 1 ONWARD
SAP PM
No native PTW or LOTO. Hot work, confined space, electrical isolation permits live in ePAS or equivalent. LOTO chains tracked in eSOMS or paper tags. Manual link between permit, LOTO, and SAP work order. Multi-crew conflict detection is reactive.
OXMAINT
PTW and digital LOTO chains native to the work order. Hot work, confined space, hot tap, electrical isolation issued from same record. No permit → no WO open. Multi-crew lock conflict detection automatic. OSHA 1910.147 compliant.
P4
REAL-TIME EXECUTION + SCOPE ADDITION · DAY 1-30
SAP PM
Work order status updated end of shift. Critical path tracking lives in Primavera P6. Scope addition impact runs manually. Field-to-command-center latency: hours.
OXMAINT
Live tool-time dashboard. Critical path updated continuously. Scope addition auto-assessed against critical path before approval. Field-to-command-center latency: seconds.
P5
PUNCH LIST & RETURN-TO-SERVICE · FINAL 72 HR
SAP PM
Punch list tracked manually or in side-spreadsheet. Recommissioning sign-offs paper-based. No native cryptographic completion record. Audit prep adds days post-STO.
OXMAINT
Punch list live, assigned, signed off in-platform. No return-to-service without full closure. Cryptographic audit trail on every recommissioning step. Post-STO report auto-generated.
SAP PM + 4 BOLT-ONS · TYPICAL STO STACK COST
$400K-$1.2M + integration
OXMAINT · UNIFIED STO + PTW + LOTO + CONTRACTOR
One platform · 6-12 week pilot
Three Real Refinery Scenarios — Where the Choice Pays Off
Three real scenarios from refinery maintenance managers and turnaround leads who moved STO execution from SAP PM + bolt-ons to OxMaint. Each shows the exact moment the decision started paying for itself. Book a free demo of refinery turnaround CMMS software.
SCENARIO 01
"Our last STO overran by 6 days. $5.4M in lost throughput. Root cause: scope additions caught too late. How do we run the next one without the overrun?"
THE PROBLEM
Mid-Atlantic refinery. 28-day planned STO ran 34 days. Three scope additions on the crude unit weren't surfaced until day 18 — vessel internals more corroded than inspected last cycle. By day 22 the critical path had shifted 3 times. End of STO: 6-day overrun, $5.4M in lost throughput, contractor demob delays added another $480K. Root cause analysis pointed at SAP PM + Primavera + ePAS not talking to each other in real time. Maintenance manager doesn't want a repeat.
HOW OXMAINT SOLVES IT
The STO Command Center (RTX)
Scope frozen 90 days out from condition data + RBI findings. Pre-STO inspection reveals 80% of "surprises" before mobilization, not during execution.
Real-Time Critical Path
When a scope addition lands, OxMaint auto-calculates impact on critical path within minutes. Turnaround lead approves or defers with full data — no spreadsheet calc.
Day-Over-Day Variance
Tool-time tracked live. Variance reports nightly. Recovery actions surfaced before slippage compounds. STO finishes on plan or with 1-2 day buffer absorbed cleanly.
THE RESULT
Next STO finished 1 day early. $5.9M saved vs prior overrun. Scope addition process auditable end-to-end.
SCENARIO 02
"During our last STO, two crews almost worked on the same isolated line — different LOTO chains, different supervisors, near miss. How is this prevented?"
THE PROBLEM
Gulf Coast refinery STO. 1,400 contractors on-site. LOTO chains tracked in paper books at each unit gatehouse, with eSOMS as the backup. Two pipe crews from different vendors arrived at the same isolated line — one was clearing for re-energization, the other was just starting a hot tap. Site safety caught it 90 seconds before either crew acted. Process safety lead filed a near-miss report. HSE team rated it severity-1 because the energy release potential was significant. Plant manager will not run another STO without digital LOTO.
HOW OXMAINT SOLVES IT
Digital LOTO Chains (Standard)
Every energy isolation logged in OxMaint with asset ID, lock holder, date/time, isolation scope. Mobile QR scan at each lock confirms placement and verifies state in real-time.
Multi-Crew Conflict Detection
If a second crew tries to open a permit on a line that is in active LOTO under another crew's lock, system blocks the permit and alerts both supervisors + site safety. Hard stop, not advisory.
Shift Handover Continuity
Isolation state preserved across shift changes. New shift sees full LOTO history per line, lock holder transitions logged. OSHA 1910.147 compliance auditable.
THE RESULT
Zero LOTO conflict incidents next STO. OSHA-auditable digital trail. HSE elevated case study to corporate.
SCENARIO 03
"Our SAP partner quoted $720K for Prometheus STO + ePAS + contractor module + integration. Plus 14 months. Our next STO is in 9 months. What's the alternative?"
THE PROBLEM
Independent refiner with 2 sites. SAP partner proposed Prometheus STO Manager + ePAS for permits + a contractor management portal + Primavera P6 integration. Total: $720K license + $380K integration. Timeline: 14 months to all systems talking to each other. Next major STO is in 9 months. Turnaround lead asked the obvious question: is there a unified platform that ships with STO + PTW + LOTO + contractor in one box, faster?
HOW OXMAINT SOLVES IT
Refinery Edition · Pre-Configured
OxMaint ships with STO planning, PTW workflows, LOTO chains, contractor onboarding, work package library, refinery asset templates — all in one platform. No integration between systems because there are no separate systems.
Sits Alongside SAP PM
OxMaint handles STO execution. SAP PM keeps financial integration with S/4HANA, cost-center accounting, capex tracking. Work order costs flow back to SAP PM via standard API.
Live Before Next STO
Pilot site live in 8 weeks. Second site onboarded in additional 6 weeks. Total: 14 weeks vs 14 months. Both refineries ready for the upcoming STO.
THE RESULT
2 refineries STO-ready in 14 weeks. $880K saved vs SAP+bolt-on stack. No integration project.
$5-15M
Typical value per STO cycle at a mid-size refinery moving execution from SAP PM + 4 bolt-on systems to OxMaint — STO overruns eliminated, LOTO incidents prevented, scope additions caught earlier, contractor tool-time up, integration costs gone. Most refineries reach break-even within the first STO event.
Refinery Edition · STO + PTW + LOTO + Contractor · 6-12 Weeks
See the Refinery STO Module Live · Before Your Next Turnaround.
Book a 30-minute demo with our refinery turnaround team. We walk through your last STO postmortem, your next STO scope, your PTW + LOTO procedures. You leave with a side-by-side comparison against your current SAP PM stack, plus a pilot plan that lands hardware before your next turnaround. Buy it once, own it forever — no monthly fees, source code included.
Frequently Asked Questions
The most common questions refinery maintenance managers, turnaround leads, and operations directors ask when evaluating OxMaint as an SAP PM alternative for STO + PTW + LOTO + contractor coordination. Sign up free for refinery turnaround CMMS software.
Do we have to replace SAP PM entirely?
No. Most refineries run OxMaint alongside SAP PM. OxMaint handles STO execution — scope planning, PTW issuance, LOTO chains, contractor onboarding, real-time critical path, punch list, recommissioning sign-off. SAP PM keeps financial integration with S/4HANA, asset depreciation, capex tracking, procurement. Work order costs and final STO actuals flow back to SAP PM via standard API. Your CFO sees the same SAP PM reports. Your turnaround team uses a refinery-specific platform.
How does OxMaint compare to Prometheus STO Manager + ePAS + contractor portal?
The biggest difference is that STO, PTW, LOTO, and contractor management are one integrated platform — not four systems with integration overhead. Prometheus STO Manager handles planning well but PTW lives in ePAS, contractor management in a third tool, and you integrate them. OxMaint ships these as one. Result: faster deployment (6-12 weeks vs 12-18 months), lower TCO (no recurring per-tool subscriptions, no integration maintenance), and a single source of truth during execution. Your team learns one platform, not four.
How does the PTW workflow handle hot work, confined space, and electrical isolation?
All standard permit types are native: hot work, confined space entry, electrical isolation, hot tap, line break, working at height, excavation, radiation work. Each permit type has its own checklist, sign-off chain, gas-test interval, and rescue plan requirement. Permits link directly to the work order — no permit, no open WO. Permits also link to active LOTO chains so the system blocks a hot work permit on a line that hasn't been isolated. All compliance trails are auditable for OSHA 1910.119 PSM review.
Can OxMaint integrate with Primavera P6 for the master schedule?
Yes, bidirectionally. Many refineries keep Primavera P6 as the master critical-path scheduling tool. OxMaint sends work-order completion progress to P6 nightly (or real-time, configurable). P6 schedule updates flow back to OxMaint work orders. Scope additions in OxMaint flag impact on P6 critical path automatically. Same integration pattern works with MS Project, Asta Powerproject, and Oracle Primavera Cloud. Standard connectors are pre-built; custom connectors can be added since source code is included.
How fast can we get a pilot live before our next STO?
Typical timeline: Weeks 1-4 — refinery asset library loaded, STO scope template configured, contractor onboarding workflow live. Weeks 5-8 — PTW and LOTO procedures mapped, mobile devices deployed to supervisors, first work packages tested. Weeks 9-12 — full STO simulation run on a non-critical unit shutdown. From contract signature to a fully-tested STO execution platform: 12 weeks. Most refineries with 6+ months to their next major turnaround can land OxMaint and run a pilot STO on a small unit before the major event.
Refinery Edition · 6-12 Week Pilot · Buy Once, Own Forever
Stop Running STOs on 4 Disconnected Systems. Get the Unified Platform.
Book a 30-minute call with our refinery turnaround team. Walk through your STO history, your overrun analysis, your contractor coordination pain points. See the unified platform live. Pilot before your next STO. Buy it once, own it forever — no monthly fees, source code included.
