BLDC Pump Controller Prototype to Production: Customer Readiness Checklist
Prepared and technically reviewed by the Sankey Engineering Team. Updated August 26, 2026.
Questions to close with the pump-system owner
Protection cannot be reviewed independently from the pump and fluid system. Confirm the expected head, flow, fluid, temperature, inlet condition, installation, duty cycle, and service response. Agree which abnormal conditions are safe to reproduce and which require a controlled emulator. A useful customer brief explains what the pump should do after dry-run, blockage, sensor loss, input interruption, or repeated restart, and how the user or service technician will know that protection has acted.
Before pilot approval, link the protection matrix to the motor, controller revision, feedback method, firmware, harness, enclosure, fixture, and records. If the pump, impeller, fluid, sensor, or pipework changes, review whether the previous evidence remains valid. This prevents a protection threshold or recovery rule from being copied into a system where the load response is different.
- Hydraulic and electrical load conditions are defined
- Fault trigger and response are observable
- Restart and reset ownership is agreed
- Engineering tests are separated from production checks
- Fluid, sensor, and pump changes trigger review
A pump-controller prototype proves a design assumption; a production release proves that the approved system can be built, tested, serviced, and changed under control. This readiness checklist is written for pump OEM customers preparing a pilot build with a controller supplier.
Freeze the system configuration
Identify the pump, motor, fluid, enclosure, harness, controller PCB, firmware or parameters, sensor method, and target operating states. Record what is still provisional.
A controller sample without a frozen pump and fluid configuration cannot provide complete production evidence. Use a configuration sheet that purchasing, engineering, quality, and the supplier can all review.
Convert risks into evidence
Close startup, low-speed, dry-run, blocked-load, over-current, thermal, input variation, and restart questions with an agreed validation matrix. State sample count, setup, criteria, and owner.
Do not hide open risks behind a passing demonstration. A clear residual-risk list lets the customer decide what must be retested before pilot and what is accepted for the next phase.
Prepare the production station
Define fixture connections, safe power-up, pump or load emulator, programmed parameters, station checks, result records, failed-unit quarantine, and rework limits.
Engineering tests may be too slow or unsafe for every unit. Select repeatable production checks that protect the product while preserving enough traceability to investigate failures.
Release service and change control
Publish connector and sensor pinouts, fault indications, reset behaviour, approved replacement procedure, board and firmware identity, and revision history.
A pump, fluid, sensor, harness, or enclosure change can alter controller behaviour. Require an impact review and documented retest decision before using the next configuration.
Frequently asked questions
What is the most important pilot document?
A controlled configuration and validation matrix linking pump, motor, fluid, controller, firmware, fixtures, criteria, and owners.
Can a supplier define all pump acceptance criteria?
The supplier can propose engineering and production checks, but the OEM product owner must approve system-level requirements and market responsibilities.
For a project-specific review, send Sankey your motor, load, interface, target market, and volume requirements. Review the relevant Sankey solution area before preparing a quotation request.