Custom ERV development can begin with the HVAC equipment you already manufacture. A cabinet drawing, a ventilation target and an explanation of how the product will be used are enough to start a discussion with EXINDA.
You do not need to arrive with a fully designed ventilator. You may know the available space but still be deciding on the air connections. Your control platform may already be established, while the ventilation sequence remains open.
EXINDA offers ERV customization covering airflow, casing and controls. For fan coil and other HVAC manufacturers, the purpose is to develop a ventilation solution around the host equipment and establish what needs to be demonstrated before production.
What should you send to start a custom ERV project?
Start with your equipment drawing and the problem you want the ERV to solve.
For an existing product, share the space available for ventilation, the intended air connection positions and the areas that must remain accessible. Explain which parts of the host design are fixed and where changes are possible.
For a new platform, an outline drawing and target specification can provide the starting point. Useful information includes:
- Required ventilation airflow and operating pressure.
- Available dimensions and service access.
- Electrical supply and control interface.
- Intended market and application.
- Expected annual quantity and target sample date.
If an input is still undecided, identify it as an open design question. That allows the initial review to focus on the decisions that matter most.
For the physical integration questions, see Custom ERV Integration for Fan Coil Manufacturers.
Can development start from a standard ERV?
Yes. Reviewing an existing ERV platform is a practical first step when its airflow, dimensions and control functions are close to the requirement.
The review should establish which parts can be retained and which need development. A project may involve changes to the enclosure and connection positions, or require a different arrangement of the ventilation assembly and controls.
This distinction matters commercially. Adapting an established design and developing a substantially different module involve different engineering work, samples and validation.
For the buyer, the useful result is a defined scope: what EXINDA will develop and supply, what the host equipment manufacturer will provide, and how the two assemblies will be evaluated together.
Agree on what a successful sample must demonstrate
A sample is more useful when both teams know what they are approving.
A dimensional sample can help establish mounting, connection positions and assembly access. A functional sample can demonstrate controls and airflow. A production-intent sample should represent the agreed components and configuration closely enough to support the next release decision.
These purposes can sometimes be combined, but they should be stated clearly. Approving the cabinet fit does not automatically approve ventilation performance.
For a custom ERV integrated into HVAC equipment, the sample review should answer a few concrete questions:
| Buyer question | Evidence to obtain |
|---|---|
| Does it fit our equipment? | Assembly review using the agreed cabinet and mounting arrangement |
| Can it deliver the ventilation duty? | Measured supply and exhaust airflow at defined pressure conditions |
| Does it meet the recovery target? | Performance results with the test conditions and configuration identified |
| Does it respond correctly to our controller? | Recorded operation through the agreed commands and transitions |
| Can it be maintained? | Demonstration of filter removal and access to serviceable components |
This gives engineering and purchasing a common basis for accepting the design.
Why test the ERV in the intended configuration?
The enclosure, filters, fans and air passages work together.
A change that improves cabinet fit may also change airflow resistance. A different filter can affect the operating point. The host blower can influence an ERV connected to shared ductwork.
The development plan should therefore distinguish tests on the ventilation assembly from checks that require the host equipment. Each result should identify the relevant configuration, settings and operating conditions.
For the OEM buyer, this makes the evidence usable. It allows the team to understand which results support the finished product and which still need confirmation after integration.
What happens if the sample needs a change?
Connect the requested change to the problem it needs to solve.
For example, moving an air connection may improve installation access. Changing a filter removal direction may make servicing possible through the host cabinet door. Adjusting a control sequence may prevent ventilation from stopping unexpectedly when a temporary request ends.
Each change should be reviewed for its effect on the rest of the design. A revised air path may require another airflow check. A firmware change may require the operating transitions to be repeated. A purely cosmetic change may have a narrower verification scope.
Keeping a clear drawing and configuration revision helps both teams evaluate the same product. It also prevents an earlier sample from becoming the accidental reference for production.
When should certification and market requirements be discussed?
Include the intended markets in the first development brief.
A manufacturer serving North America, Europe, Australia or New Zealand should identify the electrical configuration, required approvals and performance documentation for its product program. Those requirements help shape component selection and the testing plan.
For a customized assembly, establish which existing evidence applies and which assessments are needed for the final configuration. The project should also identify who will hold the relevant product approvals and who will coordinate testing.
This turns certification planning into part of the product development schedule, with clear responsibilities.
What determines the development schedule and quotation?
The main factors are the extent of customization, component availability, sample requirements and the agreed validation work.
An enclosure adaptation with an established control interface is a different project from a new ventilation layout with new firmware. The quotation should make that distinction visible.
For a useful commercial discussion, separate the development scope, sample supply and expected production arrangement. Identify any tooling, external testing or other project costs that need to be included.
A schedule should show the next deliverable and the inputs required to complete it. This lets the buyer coordinate the ERV program with its own cabinet, controller and product launch work.
What should be agreed before production release?
Production release should refer to an identified design revision and an agreed acceptance basis.
The release package should bring together the approved drawings, component configuration, control version, electrical information and applicable test records. Installation and service instructions should reflect the same configuration.
It should also identify the routine production checks and how future changes will be reviewed. A representative pilot build can help confirm assembly consistency and reveal issues that were less visible during individual sample construction.
For an OEM manufacturer, this is what connects an approved sample to a repeatable supply arrangement.
Start your custom ERV development discussion with EXINDA
Send EXINDA your equipment drawing, target ventilation duty and intended market. Tell us whether you are adding ventilation to an existing range or developing a new platform, along with your expected quantity and sample timing.
We can use those inputs to discuss the customization scope, interfaces and sample evaluation priorities.
For operating logic, see ERV Interlock and Fan Coil Controls. For broader customization capabilities, visit EXINDA ERV Manufacturing.
Contact info@exindagroup.com to discuss your custom ERV development requirements.
Frequently asked questions
Do we need a complete specification before contacting EXINDA?
No. An equipment drawing, available space and ventilation objective can start the discussion. Identify any requirements that are still open.
Can an existing ERV be the basis of a custom design?
Yes. An existing platform can be reviewed against the required dimensions, airflow and controls to determine what can be retained and what needs development.
Does sample approval mean the product is ready for production?
It depends on what the sample was intended to demonstrate. Cabinet fit, functional performance and production readiness should each have a clear acceptance basis.
Can EXINDA quote before every detail is finalized?
An initial commercial discussion can begin with the available requirements. The quotation needs an identified scope and assumptions so both teams understand what is included.
