BMW PSA Partnership to End?

Over the past year we’ve reported on the new 3 cylinder powerplant that is being developed and built by BMW 100% in house. During that time we’ve also wondered out-loud what this meant for the future of the BMW PSA partnership that created the current four cylinder range of MINI powerplants. Now Reuters is reporting that BMW and PSA will be parting ways and not co-developing any new engine or drivetrain components. However what’s really interesting is that BMW themselves crafted a press release last February indicating that the partnership would continue culminating in a new four cylinder engine capable of meeting EU6 efficiency standards. Either things have changed rapidly or Rueters has simply gotten it wrong. We’d bet on the former.
Whether that is true (or if that engine is destined for the MINI) it’s worth noting that the current 1.6L four cylinder engines will continue to have a long life ahead of them in quite a few MINI models. The “Prince” range will be mostly phased out on the R56 with the introduction of the 3 cylinder 2014 MINI in late 2013. However the “Prince” family of engines will continue to power R56 variants such as the R55 Clubman (until 2014), R57 Convertible (until 2015) and the R58 Roadster (2017) and R59 Coupé (2017).
15 Comments
<p>If BMW and PSA are parting ways, I don’t think it’s a given that the “Prince” engine would survive until 2017. It is often possible to swap an engine and otherwise leave the rest of the car basically unchanged. Automakers do that frequently across a range of vehicles and engines. While it’s also possible that any engine swap would await the full (or full-ish) model update cycle, that’s not a certainty.</p>
<p>After developing new engines, BMW often (but not always) will move those into existing models. I can’t see them bringing a new model, like the Roadster, and tying it to an old engine for 7 years.</p>
<blockquote>
<p>I don’t think it’s a given that the “Prince†engine would survive until 2017.</p>
</blockquote>
<p>This report is based conversations with multiple sources – it’s not just a shot in the dark. Expect the Prince engines to stick around in the Coupé and Roadster for a few years after the new engines are debuted in the 2014 MINI.</p>
<p>like the frenchmen say: “Cest La vie”</p>
<p>These would be the same sources that just a year ago said the PSA partnership would yield another new MINI engine, right Gabe? :-)</p>
<p>R.I.P. Fussy Little French Prince.
I don’t think anyone is going to miss you.</p>
<p>I understand that the Tritec is still being built – somewhere</p>
<blockquote>
<p>These would be the same sources that just a year ago said the PSA partnership would yield another new MINI engine, right Gabe? :-)</p>
</blockquote>
<p>That wasn’t our source – that was an official press release. Remember our report on 3 cylinders last year (before the PSA release)? That’s using our sources :)</p>
<p>A JCW 3-cylinder?</p>
<p>I bid good riddance to the Prince (I would even prefer if it was not to be used in the Coupster, but what can you do? At least JCW tuning is there to help, along with the aftermarket). To my experience, a wholly disappointing and relatively character-less motor that never should have been placed in the R56 engine bay, in either NA or turbocharged form. The Prince to me is pudding proof that “on-paper specs” (impressive at launch time back in 2007) do not necessarily translate into on-road and long-term driving appeal.</p>
<p>Oh, goody, another “new” engine for MINI customers to endure all the early-adopter bugs and flaws. Haven’t had an engine yet that stayed around long enough to mature into a stable trouble-free power plant.</p>
<blockquote>R.I.P. Fussy Little French Prince. I don’t think anyone is going to miss you.
</blockquote>
<p>It amazes me that, to this day, people insist on calling this a French motor. Didn’t you read any of the articles posted here on the prince motors leading up to the R56 launch? It’s designed by BMW and assembled by BMW in the Hams Hall plant in England. AFAIK only the block comes from France.</p>
<blockquote>Haven’t had an engine yet that stayed around long enough to mature into a stable trouble-free power plant.
</blockquote>
<p>This is pretty much a given, since emissions and economy regulations are quickly moving targets.</p>
<blockquote>This is pretty much a given, since emissions and economy regulations are quickly moving targets</blockquote>
<p>.</p>
<p>Funny how the Asian manufacturers all seem to be able to keep the same (reliable) engines in the mix for year after year after year and still meet or beat emissions and economy regs..</p>
<p>The prince engine is a gem… For what it is. It’s optimized for street driving, with tons of torque down low. I really see only two problems with the engine that could have been delt with differently: The hydrolic lash adjusters that (I think) lead to the cold start rattle, and the excessive oil change intervals that defy all logic. Both of these could have been handled differently.</p>
<p>Anyway, it’s a bit amusing how the partnerships come and go. Really, it’s short lived and I’m sure that we’ll see articles in the future talking about partnerships again because it’s just too expensive to make engines for low production number vehicles. That’s what created the Tritec, that’s what created the Prince and after a while, we’ll probably see that happen again with BMW courting some yet to be named suiter for another small engine package.</p>
<p>FWIW, one of the larger sub system suppliers (Magna, I think) says that they get interest from some customers about buying complete drivetrains, but that not many are ready to do that because so many car companies have a lot of brand ID married to the power plants.</p>
<p>Matt</p>
<blockquote>I bid good riddance to the Prince …
… a wholly disappointing and relatively character-less motor that never should have been placed in the R56 engine bay</blockquote>
<p>Be careful what you wish for. Look at the general progression of BMW engines. The next generation will probably have even less of the “character” you’re looking for.</p>