Engineering office for noise and vibration

About

The same vibration looks entirely different from three sides: the manufacturer judges a vehicle, the supplier owns a component, the test house measures a curve. I have worked at all three levels — and the most expensive loops happen exactly in between.

Hussein Abi Nassif, engineer for noise and vibration
Hussein Abi NassifEngineering office for noise and vibration

Three levels

One cause, three points of view

My work has taken place at all three levels of vehicle development. At the vehicle manufacturer, where a noise is always judged on the complete vehicle and someone has to sign a release at the end. At the tier-one supplier, where the same symptom concerns a component whose targets were agreed long ago. And at the engineering service provider, where test rigs are built and measurements run for both sides — neutral, and nonetheless in the middle of the conflict.

These three roles do not speak the same language. The manufacturer describes an impression, the supplier a specification, the test house a level at a given speed. The most laborious loops in an acoustics project rarely arise because the physics is difficult — they arise because somebody has to translate between those three descriptions, and that is rarely done by someone who knows all three from their own work.

Technically the field has shifted considerably in these years. Electrification removed the combustion noise that masked everything else for decades; what remains are tonal components from gearbox and inverter, which people accept far less readily. At the same time sound is turning from nuisance into measurand: automated vehicles are meant to hear, machines to report their own condition. Neither has established procedures yet — and that is where the work is most interesting at the moment.

This office brings that experience to wherever it is needed right now. Project by project, with a clearly defined scope, without a headcount and without months of lead time.

How I work

What you can hold me to

Not statements of intent, but the rules I run a project by. They are here so that you can insist on them.

  • Evidence before assertion

    I name a cause when the measurement carries it. Until then I separate finding, hypothesis and suspicion cleanly — in every interim status, not only in the final report.

  • Every statement with its limits

    Scatter, boundary conditions, range of validity: that belongs in the report, not in a footnote. A result without its limits fails at exactly the moment it is needed.

  • Responsibility all the way through

    No change of team, no handover, no second onboarding. Whoever starts a project carries it through to acceptance — that is the practical difference from a service provider with a staff pool.

  • The inconvenient answer too

    If an accredited laboratory is required, or somebody else would solve your task better, I will say so in the first conversation. It costs me an assignment and saves you several weeks.

Formal

Degrees and certificates

Education

  • M.Sc. Mechanical Engineering — Karlsruhe Institute of Technology
  • B.Sc. Mechanical Engineering — Karlsruhe Institute of Technology

Certificates

  • Project Management Professional (PMP), PMI
  • Professional Scrum Master
  • Professional Scrum Product Owner
  • PMI-CPMAI — Artificial intelligence in project management

Languages

  • German, English, Arabic — full professional proficiency
  • French — good working knowledge

Twenty minutes settle more than a web page

What is on your plate, whether I am the right person for it, and what a quotation would look like — that is answered faster in one call than in any exchange of documents.