A useful OEM component sourcing brief names the host product, the interfaces already chosen, the limits that cannot change and the decision the next discussion must resolve. Mark unknowns explicitly. A clear first brief is more useful than a long specification that mixes requirements with assumptions.
- Application
- Equipment, operating environment and the user task
- Hard limits
- Electrical window, mechanical envelope and host interface
- Decision needed
- Compare a candidate, request a drawing, or arrange a sample
Add a quantity range, target market and milestone when known. Share confidential design files only after agreeing how they will be handled.
Use this structure with the project enquiry form. It describes the information needed, not a fictional customer project.
Copy this into your first enquiry
Use short answers. “Not decided” is a useful answer when the alternative is an invented requirement.
Equipment and intended use:
Destination market and operating location:
Project stage and next decision:
Must-have mechanical limits:
Input/output voltages and existing interfaces:
Normal, standby and peak load, if relevant:
Environment, mounting and service constraints:
Sample quantity and estimated production range:
Documents or clarification needed:
Unknowns and who can resolve them:For the first message, send dimensions and a requirements summary rather than confidential drawings. Agree on a suitable channel before sharing restricted design files.
Separate a requirement from a preference
| Entry | Write it as | What the reviewer can do next |
|---|---|---|
| Fixed constraint | “The available mounting envelope cannot change.” | Reject candidates that do not fit |
| Preference | “A shorter cable would simplify assembly.” | Discuss a standard option or a scoped change |
| Unresolved input | “The battery architecture is not selected.” | Identify the electrical decision before proposing a pairing |
| Acceptance question | “What must the sample demonstrate?” | Define evidence to collect, rather than promise a result |
Do not turn an assumed interface into a fixed requirement. For example, seeing CAN on two product summaries does not establish that their message sets are compatible.
Two examples of an enquiry with a clear next step
Illustrative roof-power brief: “We are comparing a module for a vehicle roof. The usable area and support arrangement are fixed; the charging controller is not. Please review the 240 W module envelope, identify the electrical documents we need and confirm which mounting questions remain open.” This asks for a review, not a guaranteed energy contribution.
Illustrative cabinet-monitoring brief: “We need temperature data from specified measuring points. Minimum operating current at those points is not yet recorded. Before we request W-S01 samples, please identify the power-condition and receiver information required.” The missing current measurement becomes an explicit task.
Give each open question an owner
A brief moves forward when someone can supply the missing information. Your equipment team normally owns the host constraints and intended use; manufacturer documentation describes the selected component. Agree separately who reviews system design, site work and acceptance.
The next step might be a clarified interface, a request for a current drawing or a sample plan. Price and lead time become meaningful only for a sufficiently defined configuration and quantity.
Send your project brief, or use the solar and wireless-temperature application pages to add the relevant technical inputs.
Sources & method
This is an initial-enquiry planning template. The examples are hypothetical and do not describe customers, completed projects or a verified component pairing.