Platform

Available now

Plan the decade.
Run the event.
Keep what you learn.

STO·PATH is the software your STO program runs on, from the ten-year plan down to the person who owns one deliverable this week. The work process is its spine. Around that spine it carries the plan’s economics, the governance forums and their decisions, the risk register, every open action, and the lessons that make the next event better.

Book a walkthrough See how it fits the reviews→

The standard, made live

STO·CORE is the standard. STO·PATH runs it.

The STO Management System (STO·CORE) is the documented best-practice work process, built on public frameworks. STO·PATH is where it comes alive: the standard is visible and editable inside the tool, deployed to each event as a dated countdown your team actually works. Own the standard, not a black box, made literal.

Run it on your process, whichever it is

The STO·CORE master. Copy the STO Intelligence work process into your library and tailor it to your units, nomenclature, and event sizes.
Your own existing process. Import the work process you already run as a workbook and keep your house standard, now live and enforced.
A custom process. Maintenance, capital projects, or anything gated: the same tool runs it, not only STOs.

Your governance standards, procedures, and deliverable templates ride along as reference documents, deployed with every event and one click away on the activity that needs them.

Plan the decade

Before any of this

The long-range plan, built as a model rather than a spreadsheet.

What the cycle really costs per year in real terms, what a longer interval would cost you once scope growth and reliability are priced in, and which constraint actually binds. Scenarios that end in a recorded decision, fiscal-year cashflow, fleet benchmarks, and a board report that falls out of the plan.

Explore long-range planning→

Levelized annual turnaround cost, in real terms
Interval economics against the inspection and catalyst wall
What-if scenarios promoted through a named decision
Fiscal-year cashflow and fleet benchmarks

What it does

One system, from the countdown to the closeout.

It governs what happens, when, who owns it, and what gets approved, then carries the decisions, risks, actions, and lessons that grow around it. The detailed scope-level scheduling stays with your planners.

Run the event

The work process, deployed to a real event with a real team on it, and held to.

Own the standard

Your work process is a versioned template your company controls, not a vendor's black box. Start from the STO Intelligence master, import your own existing process, or build one, then edit every activity, role, gate, and date. No change requests to alter your own standard.

Deploy to every event

A built-in complexity calculator recommends the tier, then the whole countdown calendarizes from your execution start date. A small event gets a compressed front end, a mega event the full runway, automatically. Each deployment is an editable copy the site team can adjust without touching the company standard.

Accountability, enforced

Every activity has a named owner. One with a key deliverable cannot be submitted without evidence, cannot close without the accountable person's approval, and a gate closes only through a recorded decision: continue, conditional, or hold. Nothing is ever silently changed. It all lands in an append-only audit trail.

Improve the standard

The Drift report shows exactly how a running event diverged from its template. When a change is worth keeping, promote it into a new version of the company standard in one step. One event's lessons become the starting point for the next.

Report and notify

Roll up compliance by role, person, and phase, with gate status and pending approvals, and export the whole board to Excel for the meeting. Event-driven emails keep owners and approvers moving without anyone chasing them.

Govern it

The three forums that actually steer an event, run as a system rather than a calendar invite.

Strategy, steering, and core team

Each forum is a recurring series with a question-form agenda and a context dashboard built from live data: what moved, what is escalated, what is owed. Every meeting opens on the same ritual: approve the last minutes, walk its still-open actions, and revisit the decisions past their revisit-by date.

Minutes people trust

Record the room if you want to, disclosed and started by the facilitator, and the transcript drafts the minutes. Decisions, actions, and risks are proposed, never assumed: the facilitator accepts, edits, or dismisses each one. Approval freezes the minutes, turns proposed decisions into agreed ones, and sends them out.

A decision register that cannot rot

Every decision carries who agreed it, when, in which forum, and when it should be looked at again. Superseding one requires naming its replacement, so the register can never quietly contradict itself. Decisions due a revisit come back onto the agenda by themselves.

Manage what threatens it

An evergreen register with the heartbeat enforced, and contingency that comes off it.

Your matrix, your language

Scoring runs on your own risk matrix, uploaded in whatever form it exists today and read into the tool, including matrices that do not score cells as a simple product. Risks are written as cause, uncertain event, and effect, and the coach helps shape a vague one rather than refusing to save it.

The heartbeat is the product

Every risk has one named owner and a review-by date keyed to its severity, tightened once the execution window opens. Mitigations are real actions in the same spine, not prose in a cell. A risk that reaches its date untreated forces an explicit, recorded acceptance rather than quietly aging out. Gates hold for a register pass.

Contingency off the register

Quantified risks size the event's contingency two ways, both stated: expected value per AACE 44R-08, and a simulated band using the risk-driver method of AACE 57R-09, the practice GAO-16-89G describes. Remove-one analysis ranks which risk is buying the most contingency, so the number is arguable rather than asserted.

Learn from it

The half of lessons learned that everybody skips: capture during, not after.

Thirty seconds, from anywhere

One box, on the activity you are standing on, typed or spoken. The event, phase, and category fill themselves in. Attributed by default, anonymous when it needs to be. A register opened at closeout is reconstruction; this one is a record.

It comes back where it was learned

A lesson resurfaces on the next event's copy of the same work-process activity, in front of the person about to do that job. When a lesson echoes one from a previous event that was never actioned, the platform says so, which is the finding that actually changes behavior.

Actions that land in the plan

One action spine for the whole organization: gate conditions, meeting commitments, lessons actions, preparation tasks. One named owner, never a committee. Re-dating after the first due date requires a recorded reason. Verified is its own state, and the owner cannot verify their own action. A next-event action lands as a real activity in that event's plan.

Ask the platform

The standard, answering questions.

A standard nobody reads is a binder with a login. Every person on the event can ask the platform what a deliverable has to contain, why a gate exists, or what their own role owns this month, and get an answer grounded in two things only: your governing standard and your deployed plan.

It cites the standard. Every substantive answer names the governing document it came from, so the person can go and read it.
It reads your plan, not the template. Dates, owners, and sequence come from your deployed event, drift included. The master describes practice; your plan answers what is due here.
It coaches, it never decides. It will not approve, score, gate, or judge readiness. Asked whether something is good enough, it explains what the standard expects and points at the accountable approver by name.
It says when it does not know. If the standard and the plan do not cover the question, it says so and points at who can answer, rather than inventing a requirement.

How it is built

One standard, an editable copy per event, a named owner per activity.

Work process

Corporate admin

The company standard, versioned and published. The single source of truth every event starts from.

Event process

Site admin

An editable copy running one event. Adjust it to the event without ever changing the company standard.

Activity

The assigned person

One row of the process on one event: start it, attach the deliverable, submit it for approval.

Why it is different

A tool you run, not a subscription you cannot see into.

You edit it, not the vendor

Copy the standard into your library and change any activity, role, or gate yourself. The process the tool runs is the process you can read and edit, not a subscription you cannot see into.

The long-range plan is a model

Not a timeline someone maintains by hand. Levelized cost, interval economics tested against the technical wall, scenarios promoted through a recorded decision, and a board report that falls out of the plan rather than being rebuilt every cycle.

One record, end to end

The decision made in a steering meeting, the risk it was about, the action it created, the activity that action landed on, and the lesson that came out the other side are one chain of records, not five tools that agree by convention.

The standard learns

The drift-to-standard loop turns each event's real experience into the next event's starting point, so the process gets better with use instead of drifting apart across sites.

Keeping it alive

One brief a week, not a notification habit.

A process only survives if people are reminded of it at the right frequency, and gets abandoned if they are reminded too often. Everyone gets one brief a week: what moved across the event, and what is theirs in the week ahead. Only the genuinely time-critical items, approvals waiting and anything overdue, interrupt the day.

How you start

Stood up with you, then run by your team.

We do not hand you a login and walk away. STO Intelligence sets the platform up alongside your team, and your people run it from there. Secure Microsoft sign-in, so we never hold a password.

Already set up? Sign in to STO·PATH→

01Stand up your company and sites, and load the standard, ours tailored to you or your own imported.
02Lay out the long-range plan, every event across every site on one timeline.
03Deploy the first event together: set the tier, anchor the countdown to your start date, staff the roles.
04Walk the team through their tasks, then hand them the wheel.

The bigger picture

One event record

STO·PATH is the operational front door of the STO Intelligence platform. The work process, the assurance reviews, and the analytics all meet on the same event record, so process compliance and an independent read on readiness, schedule, and performance sit together. It is the live foundation the forward-looking capabilities are being built on.

See where it is going→

Deploy the standard. Run the event.

See STO·PATH on your work process.

Tell us how you run turnarounds today. We will show you the platform on your own process, or on the STO Intelligence standard.

Book a walkthrough

Plan the decade.Run the event.Keep what you learn.