Infanteer said:
What is the MGS being designed for?
The MGS is meant to be a company-level support gun for the Strykers. This is an infantry gun; essentially like a StuG of WWII fame [BUT WITHOUT THE ARMOUR PROTECTION]
However, one has to wonder what sort of roles this thing will fill based upon its specs. The LAV units were kept as cordon forces at Fallujah for a reason - you won't see an MGS replacing an M1A1 in an dismounted, urban assault. So accompanying the Infantry in complex terrain (where our fights will most likely be) seems to be out. So, what use does it have then? It could advance behind the Infantry in a complex battle scenario; but this puts your infantry in the "trolling" role, and human tissue isn't as good as Chobham armour in taking fire - so I'm willing to say that this is bad on both the tactical and the moral level (see the Aussie Army Chief's statement). Perhaps it can be used to backstop dismounted Infantry on other tasks - cordons and searches, VCPs, patrols, etc, etc. But one has to wonder if a 105mm MGS will offer us anything substantial over the current LAVIII capability?
If heavier firepower is required, we have other means at our disposal like the new 155mm Excalibur round from our Gunner brethren or we have to consider that perhaps it is out of the league of a Light, wheeled force - giving Cavalry a longer, heavier lance does nothing to change the fact that you can shoot the horse out from underneath the guy.
So my question (and challenge) to the MGS crowd - the MGS is being adopted due to the fact that we've simply ripped some pages out of US Army transformation planning. It seems that it was never considered if this planning even applied to our current organization and layout.
To me, it seems that a DFS requirement of heavier, sustained fire from a stabilized turret with good sensory/targeting capability has already been largely filled out and that the we will not gain anything substantive from a 105mm MGS - there will be no "bang for the buck" on this one. If we want maneuverable armoured capability that provides tactical mobility and heavy firepower, then we are foolish not to buy a modern MBT like the M1A1 Abrams, as this requirement is heavily dependent on protection that a LAV chassis can simply not provide.
If we wanted to add a real addition of capability to a LAV organization, I'd argue for the LAV-based 120mm gun that I discussed before - new 120mm rounds can be used as pretty potent low-velocity DFS while a 120mm indirect-fire capability for a sub-unit seems to be a pretty nice additional capability.
Couldn't agree with you more Infanteer (& 2B)!
See my two recent posts in Artillery Thread:
http://Forums.Army.ca/forums/threads/36703/post-309616.html#msg309616
http://Forums.Army.ca/forums/threads/36703/post-309825.html#msg309825
Some illuminating info re: MGS and AMOS capabilities.
Additionally, a May 05 briefing by Maj Parsons, OC HQ Sqn LdSH-RC,
'PROVISION OF INTEGRAL SUPPORT CSS TO THE MEDIUM DIRECT FIRE REGIMENT [MDFR]' as they are calling it now has some illluminating info on planned methodology of employment.
"Once MDFR transformation is complete in 2007, the LdSH-RC will have the following structure from which to generate F echelon capabilities: 1x Surv Sqn [16x Coyotes - 2x Tps], 3x MGS Sqn [4x MGS Tp (4 MGS)], 1x TUA Coy [3x Plts], and 1x MMEV-ADATS Bty [3x Tps]. This is an increase of 3 sub-units from the traditional structure of the Regt.
A Direct Fire Team [DFT] currently consists of: 4x MGS, 2x TUA, and 2x ADATS and is the current construct the Army foresees being generated to deploy as part of a TF.
* A fourth TUA Plt could be stood up in APS 2007, however, this issue is still being debated at higher levels.
Once the MDFR reaches IOC, expected to be sometime in 2007, it is expected that LdSH-RC will be prepared to generate 1x DFT for each TF that deploys, in line with the current Army plan that sees 2x TFs deployed and sustained indefinitely in 2 different locations."
Additionally, the current CO E Coy Maj Gentles confirms in a 28 July 2005 update that
"we are structured for Force Generation of DFTs consisting of: a HQ, 4x MGS, 4x TUA and an Echelon. We are organized into two Platoons of two Troops, each Troop having 4x LAV ITAS TUA. We see 4x TUA in a DFT [vice 2x TUA and 2x MMEV] until the MMEV is on-line."
While, in a 11 July 2005
'E Coy SITEP' he notes:
"each Platoon is organized into two Troops of four TUA to facilitate Force-Generation for operations under the Direct Fire concept being developed by DGLCD and LdSH-RC. We will need to grow to 3 Platoons in APS 06 in order to sustain a Troop sized commitment to one BG indefinitely."
Yet, , in February 2004, Comd LFDTS BGen G.W. Nordick observed
"our Direct Fire [DF] Squadrons . . . must be organized as sub-units that will support a BG (or TSSU).
The two components that determine if a DF Capability will be sustainable are vehicles / equipment and the crews to man them [4 + 1 = 5].
There is little doubt in my mind that with Whole Fleet Management the equipment will be available to support two DF Sqns outside the country indefinitely.
** However, from a crew perspective, a BG DFT of: 4x MGS; 2x TUA; and 2x ADATS [times two x five] would require: 10x Sqn HQs/Sp echs; 40x MGS crews; 30x TUA crews; and 30x ADATS crews to sustain." **
Unfortunately, current plans for LdSH-RC DF Regt provides only an eventual:
5x Sqn/Coy/DF Bty HQs/echs; 48x MGS crews; 24x TUA crews; and 18x ADATS crews.
***** A crew shortfall of: 5x HQs; 6x TUA crews; and 12x ADATS crews. *****
This gets even worse for an Unsustainable Sqn Level DFT deployment:
" from a crew perspective, a BG DF Sqn of: (16x) MGS; (6x) TUA; and (6x) ADATS [times two x five] would require: 10x Sqn HQs/Sp echs; (160x) MGS crews; (60x) TUA crews; and (60x) ADATS crews to sustain."
***** An Astounding UNSUSTAINABLE MGS-based DFS crew shortfall of: 5x HQs; 112x MGS crews; 36x TUA crews; and 42x ADATS crews. *****
The 27 April 2004
'ADATS/MMEV - A TRANSITION CONCEPT' Paper by former Co 4AD Regt LCol M. Lavoie confirms,
"ATOF. This three-year cycle . . . is based on a rule of [1 + 4 = 5]; . . .
Based on the ATOF cycle formula, and the fact that MMEV-ADATS forces of sub-sub-unit [Troop] size are required for two separate operations, a requirement for ten sub-sub-units (10x Tps) emerges. Because it is unlikely that this would be acceptable in terms of available PYs, risk must be assumed by ensuring that we are at least capable of maintaining support to one Tactical Self Sufficient Unit [TSSU] on a sustained basis and supporting a second TSSU on a surge basis. Based on this concept, there would be a requirement for six sub-sub-units (6x ADATS Tps) in order to meet Army tasks [four plus one equals five for one TSSU sustained and one for the second TSSU].
(AND)
Our experience with ADATS has clearly demonstrated that when employing ADATS it must be used as a minimum in a Tp of four (OR IDEALLY 6 TO UTILIZE ADATS NETWORKING CAPABILITY) due to high maintenance and support requirements, mainly fuel. "
Meanwhile, the 11 Jan 2005
'CHAIR-MMEV TTP WG' document 11000-1(Adjt),
'NOTES REGARDING THE EMPLOYMENT OF ADATS AS A DF SUPPORT ASSET AND INTERIM MMEV', by 4 AD Regt Adjt Capt Jeff Schamehorn reaffirm that:
" 'Penny Packeting', long recognized as a critical dilution of combat systems effectiveness, is a serious issue with the MMEV-ADATS due to the multifaceted nature of its capabilities.
It should also be noted that effective GBAD deployments are not possible with less than four (4) MMEV-ADATS. In order to maintain the flexibility of concurrent DFS [Missile] and GBAD tasks, a minimum or two (2) MMEV-ADATS Troops, should be provided to a deployed TSSU where the possibility of hostile UAV / Cruise Missile / Assymetric air threat exists.
'Fire Team' - Level 2A. Two (2) MMEV-ADATS, when grouped with a recce element, can be detached for a period of less than six (6) hours.
Troop - Level 3. Two to Three 'Fire Teams' combined with the Command and Control necessary to identify, plan, and reconnoitre for MMEV task in support of TSSU ISTAR and ICP. Also includes the non-specialist CSS assets necessary to extend MMEV function to the 24 hour period.
(And Strongly Recommends)
Grouping of MMEV-ADATS and TUA in a single DFS [Missile] sub-unit. The commonality of DF command and control procedures for MMEV-ADATS and TUA are extensive.
Summary. The proposed MMEV-ADATS v1 TTPs are enclosed as TAM804 [Annex B] to this document. The overall intent is to employ the system as a weapons capable sensor, predominantly providing information to the Commander and staff and engaging targets at extended range to shape the enemy for the insertion of Close forces when necessary. In this way the MMEV-ADATS is designed to meet the first two activities of the FEC: Develop the enemy with Sensors, and Engage with Precision from Stand-off range. These precepts are most efficiently accomplished when the MMEV-ADATS, grouped with TUA as a DFS [Missile] Sub-unit, is deployed as 'Brigade Troops' similar to the specialized Sense and Act capabilities.
Direct Fire concept being developed by DGLCD and LdSH-RC [MORE ON THIS LATER, TIME PERMITTING, HOPEFULLY BY CHRISTMAS - the History/Thrust is an eye-opener!]
This is an increase of 3 sub-units from the traditional structure of the Regt. [HOPEFULLY MORE ON THIS LATER - TIME PERMITTING.]