Build a Condition Monitoring Proof Plan for an Older Press

A reliability team calls you because their hydraulic press keeps failing and they want a number. They want a date. Condition monitoring cannot give them one, not from a first conversation and not from two seal replacements. Your job as a technical sales engineer is to turn that pressure into a plan that actually produces evidence, without promising a prediction you cannot make.

Why This Conversation Goes Wrong

People under pressure want certainty. A reliability engineer facing one shutdown day next month does not want to hear that it depends. He wants you to look at two seal failures and tell him when the press will go down for good. If you answer with confidence you do not have, you set up a plan that collapses the moment your estimate misses, and you lose credibility for every proposal you bring to that plant after. If you refuse without explaining why or offering something concrete in its place, you sound evasive, and the conversation stalls without moving the account forward either. The failure mode here has two shapes, a guess dressed up as engineering or a flat refusal with nothing behind it. Neither gets the plant closer to a decision it can actually trust.

How to Prepare Before the Call

Get clear on what you need to know and what you can promise before you dial in. Review whatever repair history exists, even if it is thin or handwritten. Two seal replacements in a year tell you something about failure frequency and wear patterns, but nothing about a failure date, so separate those two ideas in your own head before you try to separate them out loud for Malik.

Ask your internal engineering team what data a proof plan on a press like this typically needs. That usually means hydraulic pressure trends over time, cycle counts, temperature readings at known stress points, and vibration data where a sensor could realistically be added without a major teardown. Find out what a minimal sensor kit costs to install and how long it takes, because that number will matter when you talk about the shutdown day.

Think about that shutdown day as a shared resource, not a slot reserved for you. One planned day has to serve maintenance, inspection, and possibly other vendors, so figure out what a limited install or inspection could realistically accomplish inside it. Learn who else has to be in the room. A press supervisor and a controls technician hold information a reliability engineer alone will not have, and naming them before the call shows Malik you understand how his plant actually runs, not just how monitoring equipment works in general. If you want background on how manufacturing plants structure decisions around new equipment during a tight schedule, the piece on how to Set a Production Schedule Freeze Review Before Discussing New Equipment is useful reading before a call like this one.

What to Say on the Call

Malik opens with the number he wants. He tells you his team replaced seals twice this year and asks if you can tell him when the press will fail, since they only have one shutdown day next month to work with.

You do not answer the date question directly, and you should not. You tell him you cannot infer a failure date from two seal repairs, and that predicting a specific failure point would be a guess wearing an engineering label. Then you ask for what you actually need. You ask what maintenance history the plant keeps, what hydraulic system documentation exists, what downtime events have been logged, and where that information currently lives.

Malik answers that the plant has paper repair records and an old schematic, but no central vibration monitoring system. That answer is more useful than a failure date would have been. It tells you the plant is starting from close to zero on instrumentation, which changes what a first phase should look like.

You propose using the shutdown day for something narrower than a prediction. You suggest confirming installation constraints for any new sensors, and you propose defining a limited proof phase with the press supervisor, the controls technician, and the plant planner all in the room. You ask Malik to agree on what signal gets captured first, who reviews the readings once they come in, and what result would justify expanding the work beyond that first phase.

Malik pushes back and asks if this means you cannot tell him anything about his risk right now. You tell him you can describe what the two seal failures suggest about wear patterns worth watching closely, but that turning that into a shutdown forecast without real data would be irresponsible, and you would rather hand him something he can trust in six months than a guess he cannot act on today.

That second exchange is the one that matters most. Malik will push once, maybe twice, because his constraint is real and his boss is asking him for an answer. Your job is not to make that pressure disappear. It is to keep answering it the same grounded way until the conversation shifts from a date to a plan with named steps.

Mistakes to Avoid

Do not soften your answer into something that sounds like a prediction in disguise. Telling Malik the press is probably fine for another quarter is still a date, just with more words around it.

Do not let the shutdown day discussion drift into a broader sales pitch about your full monitoring platform. Malik has one day of downtime and one real question. Stay on the proof plan and leave the rest for a later conversation.

Do not skip naming who reviews the data once it is captured. A proof plan with no named reviewer produces a folder of readings that nobody looks at again. Name the press supervisor or the controls technician as the person who checks results against the measure you agreed on.

Do not treat this as a problem one call can solve. A single conversation cannot replace a monitoring program built over months. Set the expectation early that this call defines a small first step, and that the shutdown day serves that step rather than a full diagnosis of the press.

Do not leave without naming the next decision and who owns it. If you hang up without agreeing on who decides whether to expand the monitoring scope after the shutdown day, Malik is left holding a set of readings with no path forward, and the account stalls right where it started.

How to Practice and Score This Conversation

The hardest part of this conversation is staying calm when someone repeats a question you already answered. Practice by having a partner or a counterpart ask you for a failure date twice, worded a little differently each time. Your answer should stay steady both times and should return to the available evidence rather than turning defensive or vague under repetition.

A manager listening to a practice run should check for three things. Did you name a specific signal worth capturing, something concrete like hydraulic pressure trend or cycle count, rather than a vague reference to more data. Did you connect that signal to a real installation constraint tied to the actual shutdown day, not a hypothetical future window. Did you state an acceptance measure, meaning a concrete result that would justify moving past the proof phase into a wider rollout.

The close of the call is where this conversation is won or lost. Reserve the shutdown window for the agreed inspection or sensor work, not a general equipment audit, and name who owns the next decision before you hang up. If you want a structured way to rehearse this exact exchange, DealSpeak runs Manufacturing practice conversations where an AI counterpart plays the reliability engineer and scores your response against these measures. The same discipline about naming signals, owners, and decision points carries into later meetings too, which is why it helps to read how to Set a Production Ramp Meeting With Clear Decision Owners once a plant moves from a proof phase toward wider adoption.

Closing

A reliability engineer asking for a failure date is not being unreasonable, he has one shutdown day and real pressure from above him. Your value in that call comes from replacing an answer you cannot give with a plan that produces real evidence, and from naming exactly who reviews it and what happens next.