I don't really know why it was always marked as a draft and never published, but I think it's still relevant even though it's from November last year (2017):
A new article from "Ynet News" adds new info on the Barak and other programs.
Just a reminder, Barak is an upgraded Merkava 4M.
It's in Hebrew, but I have taken upon myself to translate the important bits here (some new, some old, I will mark it):
1)The Barak weighs 70 tons. (new)
Ex: In Israel, exact figures are almost never given. It's not because it's OPSEC, but because that's the sort of mentality here. Only the engineers will handle that, and the plebs get rounded numbers. So it could mean about 69, or it could be 73.
However up until now it's always been 60-65 tons, so we could see some solid amount of equipment added to the tank, which will be interesting. On the downside, it means weight reduction measures probably weren't taken and I shouldn't explain why excessive weight is bad.
2)Utilizes an AI-managed "mission computer". (new/old)
Ex: Okay so we've heard plenty of times that many actions will be automated, and that means AI. It was said however mostly in the context of the firing loop. Now they say the mission computer, otherwise known as BMS, will automatically manage certain comms with other assets that will also include the Namers and Eitans among others. Info that was previously manually input by the TC (commander).
The AI will be able to make various decisions based on the targets it identifies, whether based on the optics or the APS, and advise the crew on certain actions, and make terrain-mapping related decisions such as pointing optimal firing positions or dangerous areas.
3)Female voice selected to alert crews via BMS. (new)
Ex: Easy to distinguish from a male voice, so it won't blend in with the crew's voices, and the crew will not ignore it (they tend to ignore messages from crewmen). Among the alerts it will give are "Missiles", "Short range ATGM", and "Turning over" which means it will not only alert the crew of the type of threat and thus approximate time to impact, but also of terrain related issues to minimize accidents.
4)It was tested as a fully autonomous vehicle. (new)
Ex: But there is no operational requirement, for obvious reasons, so it's merely a test.
5)Hybrid powerplant. (new)
Ex: To cope with the higher weight and to save on fuel, hybrid is the way to go. This could also give it an amazing torque and make it a "little" speed demon. And as an environmentalist it really gives me some relief.
6)IronVision helmet system tested last month (October). (old)
Ex: I thought it was scheduled to be tested in April, but nonetheless it's good news it happened. The date for operational fielding has remained unchanged, and even rounded down to 2020, so there's no delay but a re-scheduling.
7)IronVision to be tested soon on Company-sized force. (new)
Ex: Means less time required for full operational testing, if they segment the operational testing phases to do in parallel with the program.
8)Starting next year, 3 times as many Trophy-equipped vehicles will be manufactured as this year. (new)
Ex: While the production rate is still minimal, to keep the work stable and allow to double the output when needed urgently, the front-line units will benefit greatly and at a quick rate from this decision. It also comes in light of the recent contract for 1,000 Trophy systems, and the decision to not only equip the Namers and Eitans with it, but also the Merkava 3.
No comments:
Post a Comment