As Tata Motors begins working on the next-generation Harrier and Safari EVs, new details about the two SUVs have heightened the anticipation among auto enthusiasts. According to a recent AutoCar Professional report, the new under-development SUVs have been codenamed ‘Taurus’ and ‘LEO’. The second-generation Harrier and the new-gen Safari will be underpinned by a new platform capable of supporting multiple powertrain options.
The upcoming Harrier and Safari will be based on Tata’s Omega architecture, a heavily reworked iteration of Land Rover’s D8 platform. With a strong understanding of market needs, Tata has consistently equipped its vehicles with the best. Since the D8 platform was not capable of supporting an all-wheel-drive system with a conventional powertrain, the company reengineered the architecture to accommodate a QWD EV system.
Since the Safari moniker has always been synonymous with AWD prowess, Tata’s new platform will definitely help the moniker regain its previous recognition. This is what has prompted Tata Motors to develop a new platform.
New Powertrain For The Upcoming Tata Harrier and Safari
Tata has been developing an all-new 1.5-litre Direct Injection Turbo petrol engine that is yet to make its debut. The engine will likely be fitted into the next-gen Harrier as well as the Safari. The flagship variants might be equipped with an upgraded diesel version of the current 2.0-litre diesel engine that has been sourced from Stellantis, as reported by AutoCar Professional. An evolution of the current Harrier EV’s electric powertrain is also expected in the all-electric version of the next-gen SUVs.
With the new upgrades, the SUVs may grow in size. Tata has also collaborated with Chinese automotive electronics giant Desay to develop an all-new next-generation architecture, which could enable autonomous features in the upcoming models.
Meanwhile, Tata has planned several launches in the coming months, with the Sierra and Sierra EV set to break cover soon.
Also Read: Two-Wheeler Manufacturers Seek Relaxation In ABS Mandate, Citing Homologation Challenges As Reason!
