A request for product R&D acceleration usually arrives with a rough idea: a cleaning machine, an automation cell, a station for a new process. What turns that idea into a quotation, a build plan and a machine that can be repeated is not the idea itself but the process information behind it. Before an engineering team can size a prototype, it needs to know what the equipment has to handle, where it has to work and how the result will be judged.
Start with the workpiece, not the machine
Describe what enters the process and in what condition. For cleaning and degreasing duties this means the material being cleaned, the residue involved, how thick or baked-on it is, and how often the cleaning has to happen. A machine that removes fresh cutting fluid from a machined part and a machine that breaks down carbonised grease in a kitchen extraction system are not the same problem, even when both are described as "degreasing". Note the surfaces that can be touched, the surfaces that cannot, and anything nearby that must stay dry.
Then state what "done" looks like. Visible cleanliness, a residue limit, a disinfection requirement, or simply a task that a crew can finish inside a shift change — each answer leads to a different process and a different machine.
Pin down the site and utility constraints
Most specification arguments are settled by the installation, not by the concept. Record these items before the first design meeting:
- Available supply: single-phase 220 V or three phase, available power, water source and pressure, drainage, compressed air, extraction.
- Floor space and access: footprint limits, door widths, whether the unit is fixed, hand-pushed or driven, and whether it must move between bays.
- Working environment: wet floor, dust, temperature, indoor garage, outdoor parking area, or a hygiene-controlled room.
- Operator profile: how many people use the equipment, their training, shift length, and what maintenance they can perform themselves.
An equipment maker working on both cleaning equipment and automation lines will design very differently once it knows whether the unit runs on a fixed 220 V supply or has to move through a narrow parking area without a fixed connection.
Define throughput and the duty cycle
Give a realistic daily workload: units per hour or per shift, minutes allowed per unit, and how many hours the machine runs without a break. This is where a concept is usually reworked. A process that works once in a workshop can fail when repeated for eight hours, because tank capacity, heating recovery and consumable refill fall behind the cycle. State peak days as well as average days, and say whether the line is allowed to stop for cleaning or refilling during the shift.
Say what may be standard and what must be custom
Be explicit about which parts of the request are fixed requirements and which are open to a standard solution. Voltage, footprint and safety features are usually fixed; the tank layout, the tool set and the control interface often are not. Where the process is genuinely new, ask for a product R&D accelerator engagement with a trial step, so the process is proven on your own samples before a production build is committed.
Plan the evidence you will need at handover
Decide early what has to be demonstrated before you accept the equipment: the cleaning or process result on defined samples, the cycle time, the documentation, and the tests the machine has to pass. A buyer who asks for hardware testing as part of the development scope, rather than after delivery, avoids arguing about performance with no agreed baseline.
It also helps to say which standards, site rules or customer requirements apply, and to name the documents your own team must receive: drawings, spare-parts list, operating instructions, and the records needed for inspection.
What to send in the first enquiry
A short, complete brief moves faster than a long, vague one. Include photographs of the workpiece and the installation position, a sketch of the space with dimensions, the utility list, the daily workload, the acceptance criteria, and your target date for a first sample. Where an existing machine already performs part of the job, describe what it does well and where it stops — that single sentence often removes a whole design iteration.
With those inputs, an engineering partner can tell you which parts of the request are routine, which need a trial, and where an integrated engineering team is more cost-effective than a single custom machine. The specification you supply is what makes that judgement possible.
