OEM Engineering Resource
Turn an early pump enquiry into a controlled engineering handoff.
Complete pump information gives the OEM team and supplier one traceable basis for feasibility review, sample configuration and validation. It cannot eliminate development risk, but it can reduce avoidable clarification, unsuitable samples and changes caused by unrecorded assumptions.
What Does “Complete Pump Information” Mean?
Complete does not mean that every design detail is already final. It means that known facts, target values, assumptions and open questions are separated clearly enough for both teams to make the next decision without treating an estimate as an approved requirement.
OEM application input
Describe what the equipment must do and the conditions under which it must work.
Supplier response
Identify the exact pump configuration and the conditions behind every relevant data point.
Controlled project record
Connect drawings, sample identity, approved changes and acceptance criteria to the same revision.
What Should an OEM Send Before Requesting a Pump Sample?
A useful enquiry describes the complete equipment task, not one attractive catalogue value. The first table covers the information needed to screen an air, vacuum or liquid pump platform. The second captures the interfaces that often cause redesign after a sample has already been ordered.
| Performance input | What to provide | Why it affects the decision |
|---|---|---|
| Equipment function | Pressure generation, vacuum evacuation, gas transfer, liquid transfer, circulation, dosing or another defined task. | Establishes the pump type and the result the equipment must achieve. |
| Medium | Air, gas or liquid; include composition, concentration, temperature, humidity, particles, vapour or condensation where relevant. | Affects pump structure, wetted materials, sealing and the validation method. |
| Required working point | Required flow at the actual discharge pressure or vacuum, with an acceptable tolerance or minimum result. | Connects the requirement to useful output under load rather than an endpoint rating. |
| Dynamic task | Chamber or reservoir volume, target evacuation or pressurisation time, recovery need or dosing cycle where applicable. | Relates steady-state pump data to the equipment’s actual function. |
| Circuit load | Tube inner diameter and length, filters, valves, fittings, nozzles, orifices, chamber volume, leakage and routing. | These items influence pressure loss and the installed working point. |
| Liquid conditions | Viscosity, suction lift, discharge head, priming state, dry-running limits and solids where applicable. | Liquid behaviour can change suction, flow and material requirements. |
| Integration input | What to provide | Why it affects the decision |
|---|---|---|
| Power supply | Nominal voltage, minimum and maximum voltage at the pump terminals, available starting current and current limit. | Confirms whether the motor and controller can start and operate under the real load. |
| Control interface | On/off, PWM, analogue command, feedback, braking, polarity or communication needs where applicable. | Prevents electrical changes after the mechanical layout is frozen. |
| Operating pattern | Longest run, shortest rest, starts per hour, daily use and restart against residual pressure or vacuum. | Describes the demand more accurately than a duty-cycle percentage alone. |
| Environment | Ambient temperature, humidity, enclosure ventilation, dust, vibration, orientation and storage conditions. | Affects thermal behaviour, sealing, materials and test scope. |
| Mechanical interfaces | Maximum envelope, mounting points, port direction, tube size, connector and cable routing. | Confirms fit and prevents interface conflicts in the prototype. |
| Acceptance and compliance | Measurable noise, vibration or performance limits plus applicable project standards, restricted substances and cleanliness needs. | Defines how the sample will be judged and which documentation may be relevant. |
| Project context | Concept, prototype, verification or production stage; sample quantity, expected annual range and target schedule. | Distinguishes an early screening sample from a production-intent configuration. |
Do not delay the first review merely because some values are open. Send the available information, label each gap and state who will confirm it. A visible unknown is safer than an unstated assumption.
Why Is the Real Working Point More Useful Than Maximum Values?
Free flow, maximum discharge pressure and maximum vacuum describe different endpoints of a pump curve. They are useful for initial screening, but they do not state how much flow the pump will deliver after it is connected to the equipment.
A request for “5 L/min” remains incomplete until the pressure or vacuum and circuit condition are known. Tubing, filters, valves, leakage, fittings and nozzles can move the installed operating point.
- If pressure loss has been measured, include the flow and test setup.
- If it is unknown, send a circuit sketch, tube dimensions and component list.
- Keep the unmeasured load marked open until it is tested in a representative system.
Need the detailed method? Read How to Match a DC Micro Pump to a Real Load Curve. This page intentionally keeps curve theory brief and focuses on the information handoff.
What Should the Pump Supplier Return?
A useful response is traceable to the exact proposed sample. A product name, headline rating or catalogue image alone is not an engineering release package.
| Supplier deliverable | Minimum content | How the OEM uses it |
|---|---|---|
| Configuration identity | Exact model, voltage, motor, materials, ports, wiring, connector and control option. | Prevents test results from different variants being combined. |
| Drawing and revision | Dimensions, mounting, port direction and electrical interface, with the applicable revision. | Supports mechanical and electrical integration. |
| Performance data | Flow-pressure or flow-vacuum information with voltage, medium, temperature and test condition identified. | Supports comparison at the required working point. |
| Electrical limits | Starting and running conditions, polarity, wiring and control-signal limits where applicable. | Supports power-supply and controller design. |
| Operating envelope | Permitted duty, load, ambient and restart conditions for the proposed configuration. | Defines the conditions to reproduce during equipment testing. |
| Materials and documents | Relevant material identification plus available specification, inspection and compliance documents. | Supports compatibility and compliance review without confusing pump scope with complete-device approval. |
| Evidence and traceability | Test scope and conditions, sample revision, serial or lot reference, deviations and change route. | Connects the evidence to the hardware actually evaluated. |
If data is unavailable for the exact proposed model, record the gap and the next test. Do not transfer a value from another configuration without establishing that it is relevant.
How Does the Information Package Support Each Development Gate?
The requirements package should mature with the project instead of remaining as an informal email chain. Each gate answers a different question and produces a controlled output.
Can a pump platform plausibly meet the function, medium and target working point? Output: shortlist or clarification list.
Which exact voltage, motor, ports, materials, wiring and controls will be evaluated? Output: sample specification.
Does the candidate work with the actual circuit, supply, enclosure, mounting and control? Output: integration record.
Does the configuration meet agreed limits under representative conditions? Output: approval, change or further test.
Can the tested version be reproduced from controlled drawings and criteria? Output: production-intent configuration.
Passing one gate does not automatically approve the next. A functional bench sample may establish feasibility without proving service life, regulatory compliance or complete-equipment performance.
How Should Requirements Mature from Concept to Production?
Concept
Ranges and open items are acceptable. Define function, medium, approximate working point, power source, space and major constraints.
Prototype
Freeze sample identity and interfaces. Build a representative circuit so configurations can be compared fairly.
Verification
Convert preferences into measurable limits for performance, restart, environment, noise, materials and duty.
Production
Release approved drawings, inspection criteria and deviations. Assess whether later changes require revalidation.
Common Incomplete Requests—and Better Engineering Inputs
The goal is not to make an enquiry longer. It is to replace ambiguous phrases with information that can support a traceable decision.
How Should Duty and Service-Life Requirements Be Described?
Motor type alone does not establish the duty rating or service life of a complete pump. Bearings, diaphragms, valves, seals, drive parts, electronics, load, temperature and the start-stop pattern may also affect the result.
An endurance result is useful only when the exact sample, working point, operating cycle, environment, inspection interval and acceptance criteria are recorded together.
Define the use profile
State the exact configuration, working point, medium, longest run, rest time, start frequency, environment and restart load.
Define failure
Set measurable limits for output drift, leakage, noise change, temperature, current or failure to restart as applicable.
Check evidence scope
Read any duration or cycle result together with its model, load, voltage, environment, inspection interval and acceptance criteria.
For operating-pattern decisions, see Intermittent vs. Continuous Mini Pumps. After a candidate is selected, use the Micro Pump Sample Validation Checklist to define the equipment test.
A Ready-to-Send OEM Pump Requirements Checklist
A final CAD model is not required for the first review. A block diagram, a sketch of the flow path, the available installation envelope and clearly marked open items can be enough to start platform screening.
- Equipment function and project stage
- Air, gas or liquid medium and temperature
- Required flow at pressure or vacuum
- Chamber, reservoir or dynamic task
- Tubing, filters, valves, nozzles and leakage
- Voltage range, available current and control
- Longest run, rest time and start frequency
- Ambient and enclosure conditions
- Envelope, mounting, ports and connector
- Noise and vibration measurement method
- Materials, cleanliness and compliance needs
- Sample and expected annual quantity
- Mandatory limits, targets and open questions
- Drawing, circuit sketch or test data if available
Keep customer identities, restricted drawings and confidential project data within the agreed disclosure scope. Non-identifying functional requirements are often enough for early screening; detailed geometry can be exchanged later under the project’s confidentiality process.
What Happens After JSG Reviews the Requirement?
JSG DC PUMP develops and manufactures miniature air, vacuum, diaphragm, piston and liquid pumps for OEM equipment. The review begins by separating confirmed requirements from targets and open questions.
Clarify and shortlist
Identify missing or conflicting inputs, then compare relevant pump platforms against the working point and interfaces.
Define the configuration
Record the proposed voltage, motor, ports, materials, wiring, mounting and control options that will be sampled.
Define the next evidence
Provide available model-specific information and state which conditions still require testing in the customer’s equipment.
Platform choice comes next. Use Existing Pump Platform Customization vs. New Pump Development to decide whether a proven platform can be adapted or a new pump needs a separate development path. For the wider service scope, see JSG DC PUMP OEM & ODM Services and custom micro pump development support.
Frequently Asked Questions
Do I need a finished equipment drawing before asking for a pump recommendation?
No. An initial review can begin with the function, medium, target working point, approximate circuit, power source, operating cycle and available space. Clearly mark dimensions or conditions that are still open.
Is free-flow data enough to select a micro pump?
No. Free flow is an endpoint measured with little pressure difference. Selection should consider the required flow at the actual discharge pressure or vacuum and the resistance of the installed circuit.
What if the system pressure loss is not yet known?
Provide the tube dimensions, filters, valves, fittings, nozzles, chambers and expected leakage. The supplier can identify the uncertainty and propose a measurement or representative test. Final approval still requires validation in the intended system.
How should I specify a service-life target?
State the working point, medium, operating cycle, starts, environment and failure criteria together with the required duration or cycle target. A generic “long-life” request or motor-life value is not sufficient for approving the complete pump.
Does complete information guarantee that no redesign will be needed?
No. It reduces avoidable ambiguity and makes decisions more traceable. Prototype and validation testing are still required because the complete equipment can introduce electrical, thermal, acoustic, mechanical and fluid-circuit effects.
Can confidential project information be withheld during the first review?
Yes. Begin with non-identifying functional requirements and disclose detailed drawings or restricted data only within the agreed confidentiality scope. The supplier should state which missing details prevent a firm recommendation.
Start with a traceable requirement
Send Your OEM Pump Requirement for Engineering Review
Send the application, medium, required flow at pressure or vacuum, circuit information, voltage and control limits, operating cycle, environment, installation constraints and expected quantity. Attach a drawing, block diagram or test result if available.
JSG DC PUMP will review the information, identify open technical questions and propose an appropriate next engineering step. A model or sample should not be considered approved until its working-point and integration requirements have been validated.
