Skip to main content
English
Buyer's guide for OEMs and converters

How to brief a bespoke vehicle electronics supplier

A good brief saves weeks of back and forth. Here is what an engineering team needs from you, what to ask them in return and how the stages usually run.

⁨Ian D.⁩, Head of R&D at Scorpion Automotive. Reviewed by ⁨James M.⁩, Technical Director at Scorpion Automotive.

What should a bespoke electronics brief contain?

Say what the product must do, which vehicles it fits, how many you expect to buy and which quality and approval documents you need. Add the environment, the interfaces and the target dates. The supplier can then price and plan without guessing, and you can compare bids like for like.

Start an OEM or bespoke project

Key facts

  • Scorpion designs and builds vehicle electronics in Chorley, with R&D and firmware in-house
  • The quality framework is IATF 16949 certification, with design following APQP
  • Current OE programmes cover alarms, tracking, CAN bus products and lighting
  • Lead times, minimum quantities and tooling terms are not published, so ask us

Ten items that make a brief usable

Not every item needs a final answer on day one. A marked gap is far better than a missing line.

Items to include in a bespoke vehicle electronics brief and why the engineer needs each
ItemWhat to tell the supplierWhy it matters
Function What the product does, in one paragraph, and what it must never doSets the architecture and the safety boundaries
Vehicle platforms Makes, models, years and whether line-fit or retrofitDecides the connectors, networks and fitment method
Interfaces CAN or other buses, signals needed, power supply range and outputsDecides the hardware and the firmware workload
Environment Temperature, vibration, water and dust exposure, fitting locationDrives the enclosure, coating and test plan
Volumes Expected annual quantity, ramp-up and any variantsDrives the build method and the unit cost
Quality and documents Certificates, process documents and sample approval you requireSets the paperwork to plan from the start
Approvals Any vehicle or component approval the product must carryApprovals take time and test access
Software Update method, data you need out, security and ownership of codeAvoids rework late in the programme
Commercial Target cost, tooling expectations and the contract lengthAllows a reliable feasibility answer
Timeline Prototype date, validation window and start of productionShows whether the plan is realistic

Questions to put to the supplier

  1. Is design done in-house or subcontracted?

  2. Where is it built, and what is tested?

  3. Which quality system covers the work?

  4. Who owns the design and the code?

  5. How is change handled?

  6. What happens at end of life?

  7. Will an NDA be signed before the brief is shared?

How a bespoke programme usually runs

The names vary, but the sequence is common to most suppliers.

Stages of a bespoke vehicle electronics programme and what each produces
StageWhat happensWhat you receive
Feasibility The supplier reads the brief and tests the idea against the platformA view on what is possible, and the open questions
Design Hardware and firmware are specified and builtA specification both sides sign off
Prototype Early units are built and fitted to the target vehicleSamples to test on the real platform
Validation Environmental, electrical and vehicle tests, then approvalsTest evidence and corrections
Production Volume build under the agreed processUnits to the agreed standard, with documents

Durations depend on the product and the approvals involved, so ask for a plan with dates instead of relying on a general rule.

Scorpion's engineering and manufacturing

  • In-house engineering: PCB-level hardware design and Embedded C firmware, with satellite positioning, GSM, RF and Bluetooth skills.
  • In-house manufacture: prototype and volume builds in Chorley, using SMT and THT assembly, automated conformal coating and automatic optical inspection.
  • Quality: IATF 16949 certification, with hardware and software developed under an APQP framework.
  • Programmes: alarms and immobilisers, tracking and telematics, CAN bus motor controllers and sensors, LED light clusters, and connected vehicle development.
  • A sensor example: a programmable microwave intrusion detector, approved by Aston Martin Lagonda and DAF Trucks.
130,000+ active customers
50+ years, since 1973
24/7 support
UK designed, built & fitted
FAQs

Frequently asked questions

How detailed does the first brief need to be?

Detailed enough for a feasibility answer. Function, vehicle platform, interfaces and rough volumes are the essentials. Mark everything else as unknown rather than leaving it out.

Should I send a specification or a problem statement?

Send the problem and any hard constraints. A supplier with its own engineers can often reach a better design than one copied from a fixed specification.

Can a supplier work to my quality documents?

Ask directly. Share the documents you require, and ask the supplier to confirm in writing which it already works to and which would be new for the project.

What does an OEM need to know before approaching a UK manufacturer?

The volume range, the vehicle platforms, the approvals you need and the dates. Those four allow a supplier to say yes, no or not yet.

How is intellectual property handled?

It should be written into the agreement before design starts, covering the hardware design, the firmware and any tools built for the project.

Ready to brief an engineering team?

Tell us the function, the platform and the volumes, and we will say what is feasible and what we need next.