Intel Officer's Mech?

[Black_Knyght]

Our mercenary unit has a bit of a conundrum, and thought I'd tap into the group-mind here for a possible solution.  8)

So the situation in this question is this:

We have a 3075-era multi-nationality mercenary battalion, and the battalion commander's immediate XO is also the battalion's acting Intelligence chief for the unit. And he's in need of a suitable mech for his position.

So the question in this situation is this:

What mech, from ANY nation/clan in the 3075-era, would be the most beneficial as both a war machine AND an Intel officer's machine?

And thanx all, ahead of time  ;)

[monbvol]

I'm not sure a Mech is appropriate for the Intel officer's actual intelligence duties but if he has to have one in the freak event his two duties overlap I'd suggest something with the Improved Communications and Improved Sensors design quirks.  So maybe a Cyclops.

[Hythos]

Could you consider something like an OTT-9-something (whatever works best) and have the best friend(s) in a Demolisher II? :)

[RoundTop]

Raven or an Owens. Both have tons of electronics gear. Owens can get you out faster and is an omni, so you could mount more.

[Syzyx]

Gotta back the Ostscout on this one. Ideally the IIC, but fluffwise that was a one off machine.

[Tai Dai Cultist]

Does he coordinate intel ops or does he participate in the intel ops?  That clarification would lead to very different mech suggestions.  Basically, the Cyclopses/BattleMasters for the former and Ostscouts/Owenses for the latter.

Edit:  If we're talking about a force that's only battalion sized, I'd probably be looking at your intel chief being the CO of the Battle Armor sub-force rather than being a mechwarrior.

[SteelRaven]

Unless you get into AToW, most mechs will only have a marginal advantages for info gather vs other combat vehicles.

A good scout Mech has more durability than a vtol and conventional aircraft (no Aerospace aircraft spring to mind) Something that remain hidden (stealth armor or void) and decent sensors and communication gear (sometimes only reflected in fluff text) I would imagine C3 would play a roll if working with a lance.

The Somerset Strikers may give us a vague idea of what type of unit a Intel Officer may work with consider their mission was supposedly to gather intel and recon during the Clan invasion. Though their Intel officer remained in a mobile combat vehicle (Packrat) and prior to a mission going bad to poor satellite relay, remained on the Jumpship via Mech Commander. I guess Adam Steiner could also be considered a model for Intel Officer who is also a Mechwarrior, his custom Awesome AWS-9Ma came equipped with a Command Console (this was older Command Console of course)     

[Saint]

I like the Firestarter Omnimech, good speed, armor, decent firepower, and configs with BAP, ECM, or C3 Slave.

[Black_Knyght]

Does he coordinate intel ops or does he participate in the intel ops?  That clarification would lead to very different mech suggestions.  Basically, the Cyclopses/BattleMasters for the former and Ostscouts/Owenses for the latter.

Edit:  If we're talking about a force that's only battalion sized, I'd probably be looking at your intel chief being the CO of the Battle Armor sub-force rather than being a mechwarrior.

For the most part he just coordinates Intel Ops as acting chief on a unit-wide command level for the unit, though he's was a former LOKI operative once himself.

Additionally we used both CBT and AToW in our ongoing campaigns.

[Tai Dai Cultist]

Then I'd save the Ravens, Owens, Ostscouts, and similar mechs for the recon lance(s) of the force.  I'd put your intel officer in a big, capable command mech as he's the overall 2nd in command of the entire force. 

[guardiandashi]

An important question is does it have to be stock or can it be customized?
As that changes things as well.

For example a stock cyclops sounds pretty good.
On the other hand a custom c3 master Battlemaster, with satellite uplink, command console ecm, and active probe would be a command vehicle from hell for an opponent to face.

[Black_Knyght]

I don't imagine customized would be an issue, provided it's not an optimizer's wet dream or a heavily clan-ified mech (though an actual Clan mech does work, following the former and ignoring the latter).

[Tai Dai Cultist]

I don't know how heavyweight the mercs are.  Ideally you'd want a big assault like a Cyclops BattleMaster or even an Atlas as a command mech, but if the force is generally light and fast that's actually a hindrance if the Bog Bosses can't keep up.

A good cavalry mech might be suitable as well in a case like this.  If ComStar or WoB materiel is plausible, an Exterminator might be a great idea.

[JPArbiter]

since the SLDF Royals were coming back into vogue, I would recommend a BLR-1Gbc Battlemaster.  Battlemasters are already command vehicles, and the tactical command console permits the intel officer to focus on battlefield intelligence coordination in real time while on the field while a subordinate pilots the mech, while still giving said XO to operate the mech either partially or fully if needed.

if you feel your intell officer needs to be a front line reconnisance officer, then a Mongoose II, Phoenix Hawk, or Wolverine, again because of scout and command capabilities.

[Stormforge]

Sunder, Avatar, and Black Hawk KU could make good mechs allowing your Intel Officer to mount his choice of electronics gear and weapons. Depends on your unit mobility. Could go the Clan route too, and use a Hellbringer, Timber Wolf, Executioner, etc.

[Black_Knyght]

In terms of size the battalion is actually now something of a reinforced battalion of sorts, composed of four companies and overall averaging out as mid- to upper-heavy in weight class. Currently lots of missing specialized sections/departments, hence some officers are acting heads of this section or that one.

[SteelRaven]

Considering we are talking about both assaults and omnis, the Hauptmann may be in the cards if your unit is friendly with the Lyrans.

At the same time, other mechs would be easier to come by. Might be able to make a stronger argument for a Clan mech if you unit has history with Operation Bulldog or Serpent.

[Black_Knyght]

Definitely participated in Operation Bulldog against the Smoked Jaguars (  >:D ), as well as worked for both the Draconis Combine along the Ghost Bear border and the Lyran Alliance along the Jade Falcon border.

[Tai Dai Cultist]

If you're going to play with C3, a Tai-sho may be an idea.  Put the 2C3M unit in a nice and high place where the CO's bodyguards can also help protect it.  And if you're using Battlefield Intelligence rules from Alpha Strike campaign system (or something like them) then the Intel officer is a natural to capitalize upon the HQ power that comes with 2 C3Ms.

[glitterboy2098]

Raven or an Owens. Both have tons of electronics gear. Owens can get you out faster and is an omni, so you could mount more.

wow, you must hate the guy if you want to stick him in an Owens.  #P

[Kojak]

If speed isn't a factor, the Atlas from XTRO Periphery is pretty swank for this kind of role.

[Black_Knyght]

Sadly, I'd have to say C3 of any kind is out too, because for this unit that would require refitting several mechs and not just assigning one new mech.

[Nightlord01]

For the most part he coordinates Intel Ops on a unit-wide command level for the unit, though he's also a former LOKI operative. Additionally we used both CBT and AToW in our ongoing campaigns.

Then he is not your INTELO (S2), he's your OPSO (S3). An INTELO receives, analyses, parses and reports intel to the commanding officer, they don't run ops! Good thing too, because they tend to suck at planning.

Now, repeat after me: The INTELO does not belong on the front line! Speaking of which, neither does your CO! Your CO and your S2 should be in a nice, safe location, where your S2 can look at reported hostile activity and assess it for the CO, allowing the CO to make faster, better decisions than the opposing CO. Having either in a mech, sexy as it is, is unnecessarily choking their information flow and slowing their decision cycle.

I know the BTU tends to play very fast and loose with combat doctrine, but there isn't a single military force on the planet that allows a BN CO to head to the front line, their role is to win the on the operational level. The company and lance OCs are really the only command officers who should be on the front line, with their associated G2s.

[Getz]

How about a Maelstrom 6E or 6K?  That gives you a fast, heavily armoured platform with all the electronic doodads.

[Col Toda]

I have a unit variant / model  of the Naganata . I removed the 3 tons of Artimes IV FC and use the tonnage for a Command Console .  So not only does it provide the XO with a +2 initiative and between the console and C3 Master can monitor 8 remote sensors by itself . It gets more comprehensive if one slave is in something with an active probe . By 3075 ECM is so common that Artemis IV is not worth the tonnage and should be replaced by something else .

[Archangel]

It needs to be noted that as Nightlord1 stated an intel officer's job isn't necessarily to gather the intel himself (if the unit is small there may be no choice) but to interpret/analyze it and provide only the requested/important information to his superior.  Not to mention that the officer's duties as XO will frequently take priority especially on the battlefield and IMO should be more important in his ride than his secondary position.  These duties include leading a portion of the unit, if not the entire unit, in the CO's absence/incapacitation/death into battle.  Therefore, IMO, depending upon your unit's composition the XO's ride should either be a heavier medium 'Mech or a faster heavy 'Mech to give him both firepower and maneuverability and an acceptable amount of armor.

[The Eagle]

To add on to what Nightlord said, the Intel officer should not be a MechWarrior.  They should be Intel branch, trained and schooled in analysis.  I was an Intel analyst in the US Army and every time we had a combat arms officer assigned as our S2, they repeatedly drew the wrong conclusions to the data at hand.  In one case, an Aviation branch captain questioned the intelligence assessment of myself (an NCO at the time), my supervising NCO, and my soldier, all of us trained analysts who reached our assessment individually to avoid groupthink.

When you're a hammer, everything looks like a nail.  As an analyst, you have to be a Gerber multitool instead.  It's hard to maintain that kind of objectivity when your training is "crush your enemies, see them driven before you, and hear the lamentation of the women."

[phoenixalpha]

An intel officers Battlemech should be a Dropship. In orbit. Far far away from any possible firefights with excellent communications links to all battlefield assets and every bit of data available at a moments notice. They should not be in combat if at all possible. Much like the CO (unless its a very small unit) - they are too valuable to be in combat in any shape or form.

[Robroy]

Well if he has to be in a mech I would go with a Crab, either the Royal or Star League variant ( CRB-27b or CRB-27sl ). It is fluffed as having a excellent coms gear, which is what he is going to need for coordinating everything.

[Weirdo]

A proper Intel officer belongs way the hell away from ALL combat units, found either in a command van or bunker, but you did specify mechs, so...

You want something with C3 gear, Beagle Probes, a Command Console, and/or extra Communications Equipment. The more of any of that stuff you have, the more Remote Sensors your spook can monitor, the better a view of the battlefield s/he has. If you have enough Comm Equipment, they can hack into orbiting satellites, with all sorts of combat benefits. This kind of stuff would be right up an Intel officer's alley.