Clarify Pump Skid Interfaces Before a Technical Workshop

A plant engineer calls about a pump skid and gives you one number, gallons per minute. That number sounds like the whole problem, but a pump skid lives inside piping, controls, utilities, and site access that nobody mentioned on the phone. If you walk into the technical workshop treating the flow rate as the spec, you will spend the session defending a configuration that was never properly scoped instead of using the room to gather the facts a real design needs.

Why the flow number takes over the room

Flow rate is the easiest thing for a plant engineer to state and the easiest thing for you to write down, so it becomes the anchor for the whole conversation. Everyone in the room can nod at a number. Nobody wants to be the person who asks about drain routing or electrical disconnect location when the meeting was booked to talk capacity.

The problem is that a pump skid is not a pump. It is a pump plus piping connections, instrumentation, a control scheme, power and utility hookups, and a physical footprint that has to fit an actual pad with actual clearances. If you let the flow number stand in for all of that, you will walk out of the workshop having agreed to a design that nobody has actually checked against the site. Your engineering team ends up discovering the gaps during detailed design, which is the most expensive place to find them. The customer ends up with a schedule slip they will remember at renewal time.

The fix is not complicated. You just have to ask about the interfaces before you let anyone treat the configuration as settled, and you have to do it without sounding like you are blocking the sale.

Gather the interface facts before you schedule the workshop

Before you book the technical workshop, get a short list of facts on the table, even in rough form. You need the fluid range across every recipe or product the skid will handle, not just the nameplate condition. You need inlet condition and discharge pressure, since those drive pump selection as much as flow does. You need a copy of the piping drawing or at least a sketch of where the skid ties into the existing line. You need the controls list, meaning what signals the plant expects the skid to send and receive, and what system it talks to. You need to know where the electrical disconnect and the drain can physically sit, because those two items get skipped constantly and they stall installation later.

You will not get all of this before the workshop, and that is fine. The point of asking early is to find out which pieces are missing and who owns getting them, not to arrive with a complete packet. If the plant engineer cannot answer a question, write it down as an open item and assign it to a name, not to a vague future date. A workshop that produces a list of owned open items is a success. A workshop that produces a rubber stamp on a flow number is not.

This is the same discipline that applies anywhere a customer request skips past the operational detail that determines whether a quote or a design actually holds up. If you have dealt with a quote that stalled because nobody asked the right question early, the approach in Find Quote Cycle Delays Without Blaming Engineering covers the same instinct, asking before you commit instead of after.

What to say when the request outruns the facts

Here is how the conversation can go. Plant engineer Marcus opens with the number. He says, we need a skid that can move 120 gallons a minute before the blending expansion goes live.

You do not argue with the number. You use it as a starting point. You say, that gives us a target to design around. What fluid range are we talking about, and what inlet condition and discharge pressure does the process actually need.

Marcus says the fluid changes depending on which recipe is running that week.

That is exactly the kind of detail that changes pump selection, so you go after it directly. You say, can we get your process engineer into the workshop with the piping drawing and the controls list. I also need to know where the electrical disconnect and the drain are going to sit on the pad.

Marcus admits the electrical contractor has not been picked yet.

You do not let that stall the whole discussion, and you do not pretend it is settled either. You say, let us record that as an open item and use the workshop to assign someone to close it. Our engineering team can put together a final design once we have those answers, but not before.

Notice what you did not do. You did not promise a configuration based on the flow number alone. You did not let the missing electrical contractor turn into an awkward silence that gets glossed over. You named it, assigned it, and moved on. That is the whole skill in one exchange, hold the number as a starting point, pull the interface facts out one at a time, and turn every gap into an owned action instead of an assumption.

Mistakes that turn the workshop into a rubber stamp

The most common mistake is accepting the flow number as the brief and letting the workshop become a presentation instead of a discovery session. If you show up with a proposed configuration before you have the piping, controls, and utility facts, the customer will anchor on your proposal and stop giving you the details that would have changed it.

A second mistake is asking for information in a way that sounds like you doubt the customer's competence. Asking about the electrical disconnect location is not an accusation. Frame every question around what the workshop needs to produce, not around what the customer failed to bring.

A third mistake is letting an open item stay open without an owner. Recording that the electrical contractor is not selected yet is useless if nobody is responsible for closing that gap before the next meeting. Vague notes turn into forgotten notes.

A fourth mistake is treating design approval as something you can grant in the room. You gather facts in the workshop. Your engineering team reviews the final design afterward. If you blur that line to keep the meeting moving, you are the one who owns the consequences when the design does not hold up. The same discipline matters after something has already gone wrong, not just before a design is approved. Set Corrective Action Terms After a Supplier Quality Escape covers how to hold that same line when a customer wants a fix agreed to before anyone has confirmed the root cause.

Practice the pushback with DealSpeak

This conversation is hard to get right the first time because the pull toward the flow number is strong and constant. Practice it with a colleague who plays a plant engineer determined to keep circling back to capacity. Have them resist every attempt to talk about fluid range, pressure, controls, or site access, and practice steering the conversation back each time without sounding like you are stalling the deal.

A good run ends with a clear list, which documents each participant will bring to the next meeting and what decision the workshop is actually meant to support. If you want a structured way to run this drill and get scored on how well you held the line, DealSpeak builds this exact scenario, along with other Manufacturing practice conversationsso you can rehearse the pushback before you are doing it live with a customer.

Get this right and the workshop becomes a real information gathering session instead of a formality. The customer walks away with a clear list of what their side owes you, and your engineering team gets a design brief that actually reflects the site.