Durgama Takeover

TO:
Tariqa Siti bte Yaacob

FROM:
Lt. Tan Ah Kow, 2nd Detachment, Ramah Task Force

SUBJECT: After Action Report – Raveneye Bow Tohaa Incursion
REFERENCE: #SG55-0908

General: This AAR aims to examine the strategic concerns that shaped the REF battle plans going into the “Weed Incident” on [DATE REDACTED], the tactical decisions that unfolded, and to present a final report on how the Tohaa managed a successful partial download of communications information from the Raveneye sensor network.

REF 2nd Detachment Order of Battle:
Core “Ghulam” Fireteam supporting 1x Zhayedan ML
Haris “Mukhtar” Fireteam with 1x Namurr Spitfire
1x Namurr (Free Agent)
1x Hakim (Secondary Infiltration)
Carmen & Batard

Prior Orders:
– A Zhayedan ML was brought in to provide heavy security, with the hopes of presenting a “must solve” problem for the opposing force to solve, before they can make physical contact with the Raveneye communication consoles.

– 2 Namurrs were requested due to the “take & hold” nature of the mission, combined with the need for Specialist work. The mobility and survivability of the Namurrs, especially their ability to climb and hide in hard to reach areas before being released to accomplish our objectives in the last moment, was anticipated to be crucial in this operation.

– 2 Mukhtars were also seconded from the main Ramah Task Force. A perfect pairing of MSV2 and Red Fury, to clear out opposing infiltrating specialists with strong visibility cloaking defenses, which were anticipated to be plentiful in the nature of the mission in this theatre. A mukhtar specialised in infowar was also brought in to help deal with anything more advanced which his Red Fury counterpart cannot reliably neutralise.

– Carmen & Batard. Great at helping to clear out infiltrators, and expendable to cripple more valuable opposing assets.

Estimated Tohaa Force:
Hatail Aelis Keesan,
2x Sukeuls
1x Draal
well screened with a force of Makauls and Chaksas

Notable Additionals: 1x Grief Operator, 3 “Pokemons”

Post Action Analysis of Opposing Force troop makeup:
2x Sukeuls with mimetism and pokemon backup, are indeed a good choice for “take and hold” objectives. With Makauls providing excellent 0 visibility coverage, completely shutting down our Zhayedan ML and field overwatch from our Fanous bots. A hidden Tuareg might perhaps been a better secondment request than a Hakim to provide more forward defense options.

Overall Strategic Plan:
Take initiative if possible, especially with Carmen & Batard to sniff out infiltrators who may have deployed upfield. Mukhtars to mop up what they can early, and deliver a Namurr to the midfield to sit in a safe spot before being released at the last moment to secure our assets in the theatre of operations. With good dodging ability and sheer immunity to a majority of weaponary out there, the Namurr is our best bet at holding or denying an opfor’s plans to physically acquire any information from the consoles. 2nd Namurr to fill in for the Zhayedan ML in the core fireteam for a reserve push if needed, or to hunt e/m vulnerable targets of opportunity. Hakim on call to revive any Namurrs on point, or to back up the Mukthar team if they receive wounds.

Post analysis of Strategic Plan above: Sound, but this OOB lacks Armor Piercing direct firepower if the opposing force consists of heavily armoured troops. Battlefield success would then rely on risky alternative methods of shutting down heavy strike forces with the unique equipment of the Namurrs, and/or mukhtar infowar capabilities. Thankfully, the Tohaa strike force in this operation consisted of a large number of lightly armoured but hardy troops.

Actions:
– Due to Pokemon interference, the Tohaa LT ( a Sakiel) took initiative. With Makauls providing complete 0 visibility cover on demand, and a lack of forward deployed Ramah Task Force defenses, a Tohaa Triad easily made contact with a console and set up an automated information crawler. This console was left unchecked, and by the time our infowar specialists purged the offensive software, we realised that the Tohaa had succeeded in partial retrieval of their objective. A Grief Operator was detected at the periphery of our deployment zone, but effective positioning by Carmen & Batard shut him out, and Batard was expended to reveal the Operator.

– As planned, our Mukthar Haris pushed hard and punished the Tohaan forces on our initial counteroffensive. Concurrently, an enraged Carmen neutralised the Grief Operator and set herself up further up the area of operations. While the Zhayedan ML did not directly harm the opfor in their initial push for the console, the need to constantly stop and lay out 0 vis zones meant they did not have time to safely reposition before our first counteroffensive action. With smoke cover provided by our very own NCO Ghulam, the Mukthar effectively crippled the forward Triad of a Makaul, Sukuel, and Sakiel. Pokemon nonsense saved the Sakiel.

At the same time, a Namurr was delivered to a safe high ground spot in the middle of the theatre of operations, despite nursing a wound in the process from an exchange with a particularly vigorous Chaksa. The Mukhtar, a Duo at that point, then made a temporary retreat for safer grounds near our core Ghulam team, as our Mukthar infowar specialist intercepted Tohaa radio chatter that indicated a secondary triad of a Draal supported by 2 Makauls were pushing up contest the parallel console on our other flank.

– The Tohaa’s lack of high burst weaponry to deal with our Zhayedan ML, meant that the Triad of Draal/Makauls had to expend a good amount of time laying our more 0 vis zones. Their objective was to set up another crawler bot in the console nearer to them. The Makauls are not known for their subtlety though, and Carmen effectively repositioned herself through the din near the console, forcing a close combat brawl if the opfor wanted to close in on their objective. While her efforts were ultimately futile, losing out to a Makaul in a fistfight, and the Draal finally accomplishing his tactical objective, Carmen crucially cemented the strategic battle in our favour as the opfor again were caught out of position again by our Mukthar Haris, who had by then linked up with our another free agent Namurr and made their way to the Draal’s side of the area of operations.

– With superior manoeuvrability and more support from the NCO, our Mukhtars outflanked and neutralised the Draal/Makaul Triad, while the 2nd Namurr manually purged the console of the Tohaa software. A tactical retreat was then called while the Hakim was directed to enter the AO, but with no Ramah troops unconscious, with only the 2 Namurrs wounded, his job was to come in and attempt to clear the first console of Tohaa cybertronic interference. However, a symbiobomb pokemon attached to the Sakiel was missed and the Hakim was left unable to accomplish his mission. the symbiobomb providing effective area of denial. Post operation analysis indicated that it would have been a better idea for the Hakim to push on regardless, with his high mental willpower fortitude providing a credible defense against the symbiobomb, and even if that fails, to trigger his regeneration ability to get back on the field, right on top of the console, if needed.

– The Tohaa formed a last ditch push with a prior overwatching Sukeul ML, with a Kaeltar securing the main tech coffin, and Hatail Alis Keesan making an admirable self sacrifice to restart the attack on the console which had been purged by the Namurr. However, this was a critical mistake and the blast from our Zhayedan ML also caught a Sukeul and Kumotail nearby, who could have provided more resistance to our final counteroffensive push to retake the consoles. Our final counteroffensive saw effective action by both Namurrs, clearing out the remnants of the Tohaa strike force, resecuring the central tech-coffin, and restarting the anti virus software of a console on a flank.

FINAL: While this OOB was effective in this case, a relook into the the role of the Hakim is needed. On the field, we may not have the operational bandwidth to support another troop who needs a decent amount of positioning and manoeuvring to be effective. A well prepared Tuareg, given sufficient time to prepare a carefully hidden mine, could provide a more immediate impact on similar operations in the future, especially in missions where the other attached units such as the Namurrs and Mukhtars require more operational bandwidth to be effective.