Who Owns a Steam System Efficiency Project at an Industrial Plant?
A steam issue can begin as a maintenance task and become a plant level energy project. Before selling a system wide solution, separate the local repair, the system assessment, the business case, the project funding decision, and the purchasing path.
A leaking steam trap is a maintenance issue. A plant wide steam project is not.
The sales mistake is treating those two things as the same pursuit.
A technician may identify a failed component. That does not mean the plant has approved a system assessment, accepted an energy savings estimate, or decided to fund a larger project. Each step needs its own evidence and its own owner.
Let the scope earn its way upward
The U.S. Department of Energy treats steam as a system, not a collection of isolated components. Its steam resources cover generation, distribution, end use, and condensate recovery, and its MEASUR tools are designed to evaluate operating conditions and potential opportunities across the system.
That systems view is useful commercially because it forces a clean distinction. A local defect can justify a repair. A broader project needs broader evidence.
Start with the problem the plant actually recognizes
If maintenance has a list of failed traps, sell to that scope first. If the utilities team wants to understand the broader steam balance, that may justify a system assessment. If management wants a quantified energy project, the conversation has moved again.
Do not take a generic percentage savings claim into the plant and work backward to justify it. DOE's MEASUR tool is built around current operating conditions and scenario analysis. That is the right mindset: establish the baseline, define the boundary, and let the customer decide what opportunity is worth pursuing.
The buying center expands with the scope
A local maintenance repair may involve a planner, supervisor, technician, and buyer. A system assessment can pull in utilities, energy management, operations, and engineering. A larger implementation may require facility management support, capital planning, and procurement.
DOE's steam system sourcebook specifically notes that facility management support is important to a successful assessment. That does not tell you who signs a purchase order at a refinery or chemical plant. It tells you something more useful: a system wide project cannot live only with the person who first noticed the problem.
| Decision to resolve | Function to investigate |
|---|---|
| What problem are we solving? | Maintenance, utilities, operations, or energy management |
| What system boundary should be assessed? | Utilities and engineering |
| What evidence supports the business case? | Energy management, engineering, operations, finance as applicable |
| What implementation path is acceptable? | Engineering, maintenance, project organization, site management |
| How will the work be purchased? | Procurement or the authorized purchasing function |
Those are functions to investigate, not a universal organization chart.
Steam projects are vulnerable to attractive numbers that nobody inside the plant recognizes later.
Before putting a savings number in front of management, agree on the current condition, energy cost basis, production assumptions, measurement period, and what the proposed change actually affects. If the customer cannot reproduce the logic, the number is not helping the pursuit.
DOE provides assessment tools precisely because a systems approach needs data. Use that discipline even when the project starts with a simple field observation.
A small repair can still be strategically valuable
Not every steam conversation should become a capital project. Fixing a defined problem well can create a better relationship than forcing a plant wide proposal before the customer is ready.
A maintenance job gives the Account Executive a chance to learn the system, document service performance, and identify who owns utilities, energy performance, and future project decisions. If the plant later wants a broader assessment, the seller starts from credibility rather than a cold presentation.
Know which pursuit you are actually running
Keep the local repair, the assessment, and the implementation opportunity separate in the pipeline. They may be related, but they are different customer decisions.
That distinction also makes the account map better. Instead of one vague “steam opportunity,” the team can see which people are relevant to the maintenance problem, which people matter for the system assessment, and which responsibilities appear only if the plant chooses to fund a larger project.
ExecGraph is most useful when the scope is clear enough to map the right decision chain. Start with the work the plant recognizes today. Expand the buying center only when the opportunity actually expands.
Sources
Questions Answered
Is a steam trap repair the same pursuit as a steam efficiency project?
No. A local maintenance task and a system wide assessment can involve different scopes, evidence, budgets, and decision makers. Keep them separate until the plant defines the broader need.
Who should a vendor contact first?
Start with the legitimate point of access connected to the observed need, then map the additional functions required by the scope. Do not assume one utilities or maintenance contact owns every stage of a plant wide project.
When does engineering become involved?
That depends on the project. If the work changes system design, equipment, controls, or operating conditions, the plant may require engineering review. Verify the facility's process rather than assigning the review from the outside.
What should the sales team prove before discussing savings?
Establish the current condition, measurement basis, assessment method, assumptions, and customer accepted baseline. Avoid quoting plant savings from generic benchmarks.
Explore the decision chain at the facilities mentioned above
ExecGraph organizes 47,000 industrial business records across 1,300 organizations in 12 markets. Record-level source, date, and confidence can vary by pursuit.
Request accessAccess requests are reviewed before an account is activated.