Piping Estimate Summary — Companion Article

What this tool does

The Piping Estimate Summary is the consolidated view of the piping engineering and design labour-hour estimate. The man-hour estimator is where you develop the hours. This page is where you read them as one picture: the planned labour basis for the work the scope includes.

Use that picture before you schedule, and keep it beside the schedule afterwards. Anyone who needs to see what the piping hours are, and what they are for, should be able to read it here without opening every worksheet behind it.

When to use it

Use it after the scope is agreed and the labour-hour estimate has been built, and before you treat the control-level schedule as ready. The schedule takes an approved labour-hour estimate as its starting point. This summary is that estimate, gathered in one place.

Use it in reviews with the project manager and the client when the question is “what hours are we planned to, and for which work?” Use it again when a change is approved, so the planned basis you are looking at includes that change and shows it separately from the original hours.

Inputs

Bring the estimate, and the scope it was built from:

• The activities that carry piping hours, in the same names used on the schedule.
• The hours against each of those activities, and the total.
• The scope items those hours rest on: facilities, services, deliverables, and the quantities behind them, such as a line count.
• The assumptions that bound the hours.
• Any approved change hours, kept visible as change rather than mixed into the original total with no trace.

Resource needs, such as how many designers the duration implies, are read from this labour basis together with the schedule. They are not a second estimate.

How it works

Read and check the summary in this order.

• Start from the approved scope. The summary cannot include work the scope does not include.
• Lay the labour-hour estimate out by activity. The lines of the summary are those activities and their hours.
• Confirm each line. If an activity has hours, the scope should define that work, and the control-level schedule should contain the same activity.
• Keep approved change hours visible next to the original hours. The planned basis people are working to is the original hours plus the approved change, with the change still identifiable.
• Leave unapproved trends out of the approved total. They belong on the design change notice until someone approves them.

The summary does not develop the hours. It gathers the estimate you have already built and makes the check above easy to do in a review.

Understanding the result

The result is the planned labour basis: hours by activity, a total, and a clear split between original hours and approved change. That is the estimate the schedule should place on the calendar, and the estimate progress will later call the approved hours.

A cost figure, if the project tracks one, is the project’s own rate applied to these hours. This page does not produce that rate. A staffing sketch, if you need one, comes from the duration and these hours on the schedule, not from a separate resource formula on this page.

Engineering considerations

Treat the summary as the document you are willing to defend in a review. If you cannot point from a line of hours to the scope and to a schedule activity, the line is not ready to sit in the approved view.

Calibrate the hours against your own finished projects before you lock the view. The summary is only as good as the estimate it gathers.

When the work changes, update the view on purpose. Do not let the original total quietly absorb new work. Reviewers should see the original basis, the approved change, and the total they now add up to.

The piping lead is responsible for the content. The project manager uses the view to staff, to report, and to talk to the client.

Example

Illustrative example. Figures are not benchmarks.

An agreed scope for one process unit has produced this labour-hour estimate: 100 hours plot and layout, 200 hours model, 150 hours isometrics, 50 hours material take-off. The summary shows those four lines and a total of 500 hours. Each line is named in the scope and will be an activity on the schedule.

A client then approves 80 hours for extra tie-in isometrics. The summary now shows 500 hours original and 80 hours approved change, 580 hours in total, with the 80 still labelled as change. A further 40 hours of model creep that nobody has approved stays off the 580 and on the change record until it is accepted or dropped.

Standards and references

Based on the project-controls methodology of James O. Pennock, Piping Engineering Leadership for Process Plant Projects. The estimate summary is the consolidated view of the labour-hour estimate in that method. It is a practical aid for a piping engineering lead. It is not an ASME or API code, and it is not a substitute for your contract or your company procedure.

Limitations and disclaimer

This tool presents the labour-hour estimate as one view. It does not set a universal hours-per-line rate, and it does not replace your company’s approved estimating procedure. It does not calculate a cost or a billing rate. Hours still need the judgement of the piping lead and the project manager, calibrated against your own finished work.

Use the tool

Calculate now: Piping Estimate Summary

How this calculation works: Piping Estimate Summary

Related tools

• Scope of Work is the base case the summarised hours have to match.
• Piping Man-Hour Estimator is where those hours are developed.
• Control Level Schedule places the approved view on the project calendar.
• Physical Progress Calculator reports physical completion against the approved hours.
• Design Change Notice is where a change is approved before it enters this view.
• Historical Data Log holds the actual hours you compare with this plan after the job.