TCCOM REPORT #55

REPORTING OFFICER: High Admiral Plif, TIE Corps Commander
DATE SUBMITTED: 3 Feb 24
ACTIVE DUTY ROSTER COUNT: 154 (+1)

202FOR THE EMPIRE

It's been a while since I've written one of these. I was thinking that I might not have anything interesting enough to say to publish for you all in a report, so I held back on writing something that I wasn't 100% sure about. Held back too much, I'm seeing now, so I'll be working on getting back on track in the new year. And it's even already February after January seemed to go by in the blink of an eye.

The year is 32 ABY and the First Recon Division of Emperor's Hammer is continuing its journey in the Unknown Regions. We've made contact with the Navigator's Guild and the Chiss Ascendancy, with the latter describing a threat to not just Chiss space but several other species in the region. We're taking an active interest because we're so far from home and we need safe harbors to maintain our ships and resupply. Also for bar and cantina access, since we don't have those on our capital ships... ostensibly.

Being that we've improved our ability to get news out to the fleet as it happens rather than waiting for reports or meetings to come around, I'm going to shift from recapping news in reports to going over more long-term, big picture topics. I think that'll be more interesting for me to write and for you to read, so it'll be easier for me to write more often. Also, it'll give me something to either copy/paste or summarize for the EH Wiki for later reference by pilots that have questions. The first iteration of this is below.

ROSTER ASSIGNMENT STRATEGY

One thing I do as TCCOM is place pilots in squadrons. A lot of the time they're brand new pilots fresh from training and we've also got pilots coming back from the Reserves and Inactives. They're not assigned randomly, there are some considerations I make and I want to go over what those are.

For pilots that choose a squadron for themselves, even coming from IWATS, they go to that squadron as long as that squadron isn't already full. Personal choice is paramount, I don't step in and try to divert pilots away from an assignment they've chosen. My thought is that the surest way to discourage someone from being part of the club is to overrule an assignment preference they've expressed, so we don't do that.

Next up is looking at whether they have a recruiter and assigning the new pilot as close to that recruiter as we can. If the recruiter's squadron isn't full, the new pilot goes to that squadron. If the recruiter's squadron is full, I'll talk to the BGCOM about assigning them to another squadron in the same battlegroup. The assumption I'm making is that most recruits have met their recruiter and will do the best near the person that brought them to us. I'm hopeful that the relationship between a recruiter and their recruit doesn't end in IWATS, so I assign them together to help maintain that relationship. Also, the opportunity to fill out one's part of the roster forms a natural benefit to being a recruiter.

If there's no recruiter and no squadron preference expressed by an incoming pilot, I'll talk to the BGCOM of the smallest battlegroup about assigning the pilot to one of their squadrons. The pilot might not always go to the smallest squadron because we're also considering which squadron has something in common with the incoming pilot be it games played or even something like a general mindset. We want to make sure that a new pilot has the best chance of becoming a part of the community so we try to "hook" them by matching them with pilots we think they'll get along with. Sometimes we're not working with a lot of information about the incoming pilot so the BGCOMs are invited to talk to them before deciding which squadron to send them to.

Inter-squadron transfers happen infrequently, but pilots are always free to request a transfer to another squadron. It could be that they've made friends in another squadron or don't get along with someone in their current squadron, and in those situations we come back to personal choice being paramount. I give the leaders involved a chance to talk to the transferring pilot before the transfer is processed in case there's been a misunderstanding that can be resolved; I feel like that's not a lot to ask the transferring pilot to wait for and I make sure to tell them that they're not under any obligation to change their mind. Transferring hurts sometimes, but it's better than telling a pilot they can't move and have them fade away on us. That's not good for us or them.

TITLE HOLDERS

The Raise the Flag event each year confers three titles to recognize the top ship, squadron, and individual pilot from the competition. These are the current holders of those titles.

TIE Corps Flagship: ISDII Warrior

TCCOM's Escort Squadron: Lambda

TCCOM's Wingman: LCM Vanguard88

TIE CORPS UNITS

Note: The database counts the three NPCs and counts the TCCOM, SOO, and WO towards Battlegroup II, so there’s some differences between what it shows and what I’ve listed here.

TIE Corps Command Staff (4) plus CA:TCCOM (1)

• ISDII Hammer, Wing I (63)
  • Alpha Squadron (8)
  • Beta Squadron (12)
  • Delta Squadron (10)
  • Epsilon Squadron (12)
  • Gamma Squadron (9)
  • Lambda Squadron (12)
• ISDII Grey Wolf, Wing XIII (0)
  • STANDING BY

• ISDII Warrior, Wing II (44)
  • Kappa Squadron (12)
  • Rho Squadron (12)
  • Sin Squadron (11)
  • Theta Squadron (9)
• ISDII Relentless, Wing IX (0)
  • STANDING BY

• ISDII Challenge, Wing X (17)
  • Tempest Squadron (9)
  • Typhoon Squadron (8)
• MC90 Renegade, Wing XXII (17)
  • Eagle Squadron (9)
  • Firebird Squadron (8)

• Spectre Squadron (5)
  Note: Via dual profiles, the TCCOM and SOO are also members of Spectre

SIGNOFF

If there's anything I can help you with Corps-wise, please let me know! Message me on Discord at Plif#2475 or over email at tccom at emperorshammer dot org.

TCCOM-EDR/HA Plif/TC-1/ISDII Warrior/Battlegroup II
MoH/IC/GOE/GSx9/SSx15/BSx38/PCx37/ISMx39/IAR/MoT-gh/MoI/MoC-7doc-6poc-7goc-9soc-57boc/MUA/IS-PW-43GW-88SW-103BW-4CW-PR-11GR-27SR-43BR-2CR/ORA-1C/LoC-3PS/LoS-6PS/DFC-SW/CoE/CoLx12/CoB/LoAx13/OV-25E [Centurion] [Ace 1st] [Ace Ranger 3rd] {TCCORE-COE-MP/1/2-SM/2/4-WIKI}