STOINTELLIGENCE
Data-driven. Field-proven.

STO·PLN · Planning, Estimating & Materials  ·  A module of STO·PATH, the STO Management Platform

Every job planned. Every hour priced. Every part on its date.

STO·PLN turns the frozen scope into work packages your planners build step by step, reads those steps as the estimate, and derives each material’s order-by date from the step it feeds. It is one build-up, so the plan, the number, and the parts cannot drift apart. Your scheduling tool stays your scheduling tool: the platform hands it clean files and checks against it.

One build-up: the plan, the estimate, and the materials.

The planning register: every package with its planner, its due date, and what it still lacks.
The planning register: every package with its planner, its due date, and what it still lacks.Illustrative demo data

The problem

The plan lives in three places, and they stop agreeing in week two.

The packages are in folders, the estimate is a workbook priced once, and the materials are a list somebody chases by phone. Each is defensible alone. Together they describe three different turnarounds, and nobody finds out until the first one is wrong in the field.

Packages in folders
Nobody can say how many are planned, reviewed, or late

Planning progress is a percentage reported upward on trust. The steering team learns the true count at the readiness review, when it is too late to add planners.

An estimate beside the plan
Priced once, never re-read when the steps change

The control budget and the job plans were built by different people from different lists. Every scope change is then argued twice, once in hours and once in money.

Paid hours nobody stated
Tool time, schedule hours, and paid hours blurred into one number

One site plans tool time, another plans paid time, and the estimate quietly assumes they are the same. The gap is a third of the labor budget.

Long lead found late
The order-by date passed before the package was planned

Material dates are worked back from memory. The line that needed eight months is identified at six, and the event is planned around a part.


What it does

From the work list to a released package, a class of estimate, and a part on order.

It carries the planning the way your planners already think about it: package the scope, plan the steps, price the build-up, order what the steps need, and review the pack before it is released.

01

Package the scope

The planning lead turns the scope into numbered work packages and hands them out.

A register, not a folder

Scope items become numbered work packages, each with a planner and a planning due date. The register shows who plans what, what is late, and a curve of packages due against planned and approved. A scope item sits in one package unless you split it on purpose, and the work process reads its planning progress from the register instead of from somebody’s estimate of it.

Start from the last turnaround

The previous event’s schedule becomes the planning basis. Each job shows how many times it was planned before, the hours it actually took, and whether it carried a deferral, a change, or a quality issue last time. Clean jobs start as drafts marked to verify; a flagged job waits for its planner. Nothing is ever marked planned by the basis.

Plan here, or link to your schedule

Choose once. Packages link to the activities in your schedule, or are planned here as steps with crew, duration, logic, crafts, equipment, permits, and hold points, then exported to your scheduling tool as one project. Dates are never typed; they come from the schedule. The platform checks. The schedule decides.

A package is a document

The first tab says what the pack must contain for its equipment class: a marked-up P&ID, photos, the job steps, the permits, a hazard analysis, and the class’s own sheets. A review round of named seats, planning, operations, the contractor, the engineer, the inspector, sets it reviewed, never a button. The platform then builds the pack as a revisioned PDF: an owner’s edition and a contractor’s with no money in it.

02

Price it from the build-up

The estimate is the plan read as money, class by class. It is not a second tool.

A ladder, each class a snapshot

Budget, Class C, Class B, Control. Each is the packages’ steps priced through the rate table in force at its date, with a coverage line stating where the hours came from and what still carries no rate. Issuing writes the figure to the long-range plan. Freezing the control estimate turns every later approved change into a delta.

Paid hours, said out loud

Each calendar states its paid hours, its productive hours, and the hours the schedule carries, so scheduled hours become paid hours by arithmetic you can read. Nothing above a budget estimate issues until the labor basis is set. Unknown paid hours are unknown, never assumed.

A resource plan by the day

People and machines by day, by contractor and shift: taken from the schedule, planned between two dates tied to the start, or inferred by ratio, a foreman per ten crafts, a fire watch per two hot-work jobs. Each craft reads needed against paid: red where paid falls below need, amber where the same people are counted twice.

Each contractor’s plan, accepted

Every craft line has a company. Each contractor builds its resource plan from its direct hours and hands it in; you accept or return it against the house inference shown beside it. The estimate prices accepted versions only. A contractor’s seat never sees money, rates, or another company’s crews.

03

Get the materials on their dates

Order-by dates that come from the plan, and a long-lead list that is released first.

A bill of materials from the piping spec

Lines come from the piping spec the line number names, an equipment set, or your catalogue. An exception takes a reason and an engineering signature, and release is refused while one is unsigned.

Dates derived, not guessed

Need-by is the step’s start less your staging lead. Order-by is need-by less the lead time, with a buffer on a long-lead line. Move the plan and the dates move. A promise that lands after the step it feeds lights the lamp.

Long lead goes first

A threshold by event size marks the long-lead lines, and they release ahead under their own number with the order-by frozen at release, so trigger dates met is a measured figure. An early buy on undecided scope asks who authorized it. Scope deferred later says cancel or hold the order.

Quotes by item, orders by you

A quote request carries one row per item, and a recorded quote prices every line that uses it. The release list goes out in your layout and carries the order into your purchasing system. Nothing is ordered here.

04

Plan what holds the work

The inspection plan, the scaffold, the money, and the change paperwork, planned with the package.

The inspection and test plan

A named inspector owns the plan and issues it by revision. Quality is not planned until it is issued, every hold point sits on a step, and the hours for the examination land on that step so the planner carries them.

Scaffold by quantity

Each build is sized and crew-rated with your own rates, with a need-by and a dismantle date, and the build curve to the start is tracked against the foreman’s daily report. The rate achieved goes into the site history.

Who pays, and the change paperwork

Every accepted scope item says whose money it is, turnaround, capital, or maintenance expense, and whether it needs a management of change. The estimate splits by it. A package is not released while its change is not approved, unless an administrator records why.

Files for your scheduler and your CMMS

Packages export to your scheduling tool with stable codes, and progress goes back as a file. Job plans, notifications, orders, and confirmations go out in your maintenance system’s import layout, and a documented API with company keys carries the same records to anything you build.


Estimate · the ladder

The estimate is the plan, read as money.

Open a class and the platform prices the packages’ steps through the rate table in force, adds the resource plan’s people and machines, and states its own coverage: the share of hours from planned steps, what carries no rate, and which contractor has no accepted plan. The gaps are printed on the estimate rather than discovered after it is approved.

The ladder: an issued Class C, a working Class B, and the labor basis each calendar is priced on.
The ladder: an issued Class C, a working Class B, and the labor basis each calendar is priced on.Illustrative demo data
The Class B build-up by category, split by who pays.
The Class B build-up by category, split by who pays.Illustrative demo data
The resource plan: each craft needed against paid, by day.
The resource plan: each craft needed against paid, by day.Illustrative demo data

Materials · long lead

The parts that set the date are released first.

The long-lead view lists every line past the threshold for this event’s size, its order-by date worked back from the step it feeds, and the scope items flagged long lead that still have no line. Compliance against the frozen trigger dates is a number on the page.

Long lead: order-by dates derived from the plan, released ahead, measured against their trigger.
Long lead: order-by dates derived from the plan, released ahead, measured against their trigger.Illustrative demo data

Where the line sits

It plans with you. It does not plan for you.

A planning tool earns trust by being exact about what it will not do. STO·PLN holds the packages, prices what your planners wrote, and derives dates from your schedule. The judgment stays with the planner, the scheduler, and the buyer.

  • Your schedule decides. Levelling, master logic, and the cross-package critical path stay in your scheduling tool. The platform checks against it and runs no second critical path.
  • It never invents hours. The job library carries steps with no house hours, and a missing rate is shown as missing, never assumed.
  • It records, it does not order. The release list carries the order. There is no inventory, no warehouse, and no bidding here.
  • No model writes the plan. Every figure is arithmetic on your own records. The coach can explain a screen; it never plans, prices, or approves.

What changes

The difference between three lists and one build-up.

Planned the usual way

  • ×Planning progress reported as a percentage, on trust
  • ×An estimate priced once, beside the plan
  • ×Paid hours assumed equal to scheduled hours
  • ×Long-lead items identified after their order-by date

Planned in STO·PLN

  • ✓A register that counts planned, reviewed, approved, released
  • ✓Every class of estimate read from the steps, with its gaps printed
  • ✓The labor basis stated per calendar before anything issues
  • ✓Order-by dates derived from the plan, long lead released first

How it fits

Scope in, a released package out, on the same event record.

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·SCP challenges the scope before it is planned, and the items that survive arrive here already screened. STO·EXE takes the released packages into the unit: the shift look-ahead, the isolation list, and progress claimed against the same steps. The cost control one-pager covers what happens to the estimate once the baseline is frozen.

Bring last turnaround’s schedule and your work list.

We load the schedule as your planning basis, package the scope with your planning lead, and show the first estimate read from your own steps.