STOINTELLIGENCE
Data-driven. Field-proven.

STO·EXE · Execution & Field Quality  ·  A module of STO·PATH, the STO Management Platform

Issue the shift. Hold the sequence. Know where you stand by morning.

STO·EXE carries the plan into the unit: a shift look-ahead cut from your current schedule and issued by crew, the isolation and blind list with its sequence held, the step-out and the return planned by system, and progress claimed on a phone or a printed sheet and verified by the owner. What the crew found is on the record the same hour, and the same claims feed earned value overnight.

The plan goes into the unit, and the unit answers back.

The shift look-ahead in force: every line with its crew, its coordinator, and the holds the platform knows.
The shift look-ahead in force: every line with its crew, its coordinator, and the holds the platform knows.Illustrative demo data

The problem

Execution runs on paper the plan never sees.

The schedule is updated at night from what people remember. The blind list is a clipboard. The look-ahead is a spreadsheet emailed at six. Each works until the day two of them disagree, and that is the day the event is decided.

A look-ahead by email
Issued as a spreadsheet, progressed by rumor

Nobody can say which work was actually issued to which crew, so nobody can say whether the crew that is behind was ever sent.

The blind list on a clipboard
One list, forty packages, counted by hand before startup

A blind serves many jobs. Pulled when the first one finishes, it is a near miss. Left in after the last, it is a startup delay.

Progress by opinion
Percent complete nobody verified

The contractor claims it, the schedule takes it, and the gap between claimed and true surfaces in the last three days.

Findings at shift end
Radioed in, written up from memory, decided a day late

A quality issue or a discovery waits for the paperwork, and the decision it needed arrives after the crew has moved on.


What it does

From the issued shift to the signed turnover, on one record.

Five things happen in a turnaround’s execution window, and each is usually a different spreadsheet. Here they read each other: the look-ahead knows the isolation is not in, the system knows a package is still open, and the turnover knows a blind is still counted.

01

Issue the work

The planner cuts the next shifts from the schedule and issues them by contractor and crew.

The shift look-ahead

Cut the next two to six shifts from the schedule you keep here. Every line carries its crew, a named owner coordinator, and the holds the platform knows: an isolation not in, a permit not reviewed, a hold point, materials not arrived, an open change, an inspection plan not issued, a system not released. Issuing freezes it and renders the sheets.

Only issued work is progressed

Once an issue stands, a claim on work that was not issued is refused, with the way to ask. The request goes to the coordinator for that work, who hears at once; approving it adds the line. The gap between what was sent and what was worked closes at the source.

Paper is first-class

Each crew gets a printed sheet with a box per shift for percent, hours left, crew, delay, and a note, a line for the foreman’s signature, and a code. A foreman with no account scans the code and reports from a phone, or the sheet is keyed in. The coordinator’s initials are recorded as validated on paper.

Your current schedule lives here

An administrator or the planning lead uploads the current schedule export, or the scheduler’s script pushes it. The team confirms its coding once and later copies carry it forward. The copy’s age reads on every page that uses it, amber past a day in execution. It is kept current, never scored: a score takes a review.

02

Make it safe, in sequence

One isolation list for the event, with the order of locks and blinds held by the record.

One list, shared by every package

The isolation and blind list comes from your site library, an import, or the last turnaround, and serves every package that depends on it. A blind stays in while any dependent package is open. A confined space entry needs a positive isolation at the equipment, or a recorded deviation.

Locks before blinds, and back again

A blind goes in only once the valves are locked and the make-safe steps are reported done. Those locks release only once every blind is verified. A blind comes out only under the valves locked again. Each refusal names what blocks it, and operations can pass one with a reason that is kept.

Lockboxes and the two counts

Each isolation has a lockbox per stage, with crews signed on and clear by package. A box is not released while a crew is on it. Before startup the blind count and the lockbox clearance are signed, and the as-built list is written back to the site library for next time.

Permits proposed, reviewed by operations

Each step proposes the permit kinds it needs, and operations reviews them by package. The review is stamped against the steps as they stood, so any later change to a step reads proposed again.

03

Step out and return by system

The shutdown and the startup planned by process system, with the packages tied to the systems they open.

A unit is many systems

Process systems and the unit’s own utilities, steam, cooling water, instrument air, nitrogen, each with its steps and targets in hours from the start so they move when the start moves. Utilities release last and return first. Operations’ own spreadsheet or project file imports, and nothing is written until you apply it.

Released to maintenance

A package cannot start its turnaround work until the systems it opens are released to maintenance, and its page says which release it is waiting on. The gates view lists every package planned to start before its release.

Turned over, system by system

A system cannot be turned over while a package on it is open, a blind is still in, a lockbox is not released, an A punch item is open, or a closure form is unsigned. The board says which, and the last signature turns it over.

04

Capture it where it happens

A phone, a tag, or a poster at the gate: the finding is on the record before the crew leaves it.

Raise it where you stand

A quality issue, a field observation, an RFI, a punch item, or a scope change, raised on a phone with a photo and a line, from the job or from the tag on the equipment. With no signal it waits on the phone and sends itself.

A poster, and no account

A contractor’s worker scans the poster at the gate and reports a safety observation, a near miss, a quality issue, or a lesson with no sign-in. Sending without a name is the default for safety. Every entry is held until your site team accepts it into the register, and a severe near miss reaches them at once.

Hold points with a clock

The crew calls the hold point when it is ready and the notice clock starts: yellow past notice, red past the hours you set. Who may release it is a rule, never the caller.

05

Know where you stand

Progress claimed at the work, verified by the owner, and read as earned value by morning.

Report this shift

Two minutes at shift end: the steps by quarter, hours by craft, and one delay code. It works offline and sends when the signal is back.

Claimed, then verified

The named coordinator validates the crew’s claim. A contractor never verifies its own, and you can choose to count verified claims only. Validated progress goes back to your scheduling tool as a file.

The shift handover

Issued, claimed, validated, done, slipped, and disputed, with hours remaining and delays by code, read from the same lines the crews worked. The daily meeting walks it rather than rebuilding it.


The field · on a phone

The same record, in the unit, with gloves on.

The Field page runs in any phone’s browser. It shows the crew’s lines from the look-ahead in force, takes progress in four taps, finds a blind by its number or its tag, and holds what was entered until the signal returns.

01
My look-ahead

The lines issued to this crew: 25, 50, 75, done, or a typed percent, and the hours left.

02
Blinds and locks

Find a point by number or tag, report it in or out, add a photo. Operations alone moves a lock.

03
Raise what you found

Quality, an observation, an RFI, punch, a scope change, from the job or the equipment tag.

04
Report this shift

Steps, hours by craft, one delay code. It waits on the phone when there is no signal.

The Field home on a phone.
The Field home on a phone.Illustrative demo data

Isolations · systems

The sequence is held by the record, not by memory.

The isolation list shows each point’s stage, its lock, its lockbox, and the packages that depend on it. The systems view shows the step-out and the return by system, with the packages that would start before their release.

The event’s isolation list: stage, lock, lockbox, and the packages each point serves.
The event’s isolation list: stage, lock, lockbox, and the packages each point serves.Illustrative demo data
Shutdown and startup by system, in hours from the start.
Shutdown and startup by system, in hours from the start.Illustrative demo data

Statuses here are reported by a named person · your permit-to-work system stays the authority


Where the line sits

We hold the plan and the count. Never the lock.

This is safety-adjacent work, so the line is drawn where it belongs. The platform plans, sequences, and tracks what named people report. It authorizes nothing. A status here reads ‘reported by’, never ‘proven safe’.

  • Your permit to work stays the authority. The platform proposes permit kinds and records operations’ review. It issues no permit and no certificate.
  • No personal locks, no names on a box. It tracks the site’s numbered isolation locks and crews by package. Gas test values stay in the permit-to-work system.
  • Not your timekeeping. Hours from a shift report are estimates until your timesheet or gate record lands.
  • No model in the loop. Nothing in the look-ahead, the isolation sequence, or the systems plan is decided or drafted by AI.

What changes

The difference between six spreadsheets and one record.

Executed the usual way

  • ×A look-ahead emailed at six, progressed by rumor
  • ×A blind list counted by hand the night before startup
  • ×Percent complete claimed by the party being paid for it
  • ×Turnover argued system by system in a meeting

Executed in STO·EXE

  • ✓Issued work by crew, and only issued work progressed
  • ✓A sequence that refuses, two signed counts before startup
  • ✓Claims validated by a named owner coordinator
  • ✓Turnover held by the record until the last signature

How it fits

The packages come from planning. The progress goes to cost control.

How it is packaged

One add-on, three modules.

STO·SCP (Scope Management), STO·PLN (Planning, Estimating & Materials) and STO·EXE (Execution & Field Quality) are one add-on to the STO·PATH subscription, per site, and one add-on covers both the turnaround and the capital door a site holds. The work process, governance, risk, lessons, the readiness indicator, and the role guides are in the base platform.

STO·PLN releases the packages this module issues, and the cost control one-pager covers how the claims made here become earned value. Closure forms and the punch list, already part of the platform, close the work by system.

Bring your current schedule and your blind list.

We load the schedule, bring your isolation list in, and cut the first look-ahead with your planner and your operations lead.