NBG Part IV

[Tacom]

I will take CO Mech coy and Emi will take a CV90 platoon. Please, choose a different platoon to go with the tanks, to minimize language problems.

[Tacom]

So, UNOFFICIAL staffing list:

HQ:

- CO: Duke

- FO: Hedgegog

- A platoon (2x EagleIV, 4x Motocycle):

- A (Tank)/II-Reserve: ¿Tango 29?

MECH (CV9030, from FI and NO coys):

- CO: Tacom

- A (Tank)/I: Tango 29

- B platoon (4): TJay/Marko

- C platoon (4): Emilio

TANK (all tanks combined):

- CO (Strv122):

- A (Mech):

- B (3 Leo2A4): Abaddon

- C (3 Strv122): Tacbat

RECCE:

- A (4 CV9040C):

CSS: Gibsonm

- A (2 Leo1A5plow, 2 M113eng):

- B (Wisent, 2 M113 med, 2 MAN supply, M113 repair):

[Duke(911)]

Servus,

HQ:

- CO: Duke

- FO: Hedgegog

- A platoon (2x EagleIV, 4x Motocycle):

- A (Tank)/II-Reserve:

MECH (CV9030, from FI and NO coys):

- CO: Tacom

- A (Tank)/I: Tango 29

- B platoon (4): TJay/Marko

- C platoon (4): Emilio

TANK (all tanks combined):

- CO (Strv122): Falli

- A (Mech):

- B (3 Leo2A4): Eisenschwein, Ricopico

- C (3 Strv122): Tacbat, Abaddon

RECCE:

- A (4 CV9040C):

CSS: Gibsonm

- A (2 Leo1A5plow, 2 M113eng):

- B (Wisent, 2 M113 med, 2 MAN supply, M113 repair):

Here the first idea:

Intention:

RECCE first along HIGHWAY to HELL to RA1

NBG follow in column formation till PL2

Attack with TANK eastern part of bridge

MECH attack over bridge establish bridgehead

NBG cross the river and attack with MECH left, TANK right to Obj TV

RECCE to bp Block 1

establish OP1 and 2 with HQ units and combat outpost in bp viking (TANK)

company orders follow tomorrow,

CO`s can think about her formation for march and attack

I try to be in TS a little bit earlier tomorrow, but can`t promise.

best regards

your battlefield coordinator

Duke

[Gibsonm]

your battlefield coordinator

Duke

Is that some sort of Euro PC term?

I thought you were the CO, not just a "coordinator"?!

Will be at Orders at H-30.

PACKHORSE OUT

Edited May 4, 2013 by Gibsonm

[Eisenschwein]

Is that some sort of Euro PC term?

I thought you were the CO, not just a "coordinator"?!

Will be at Orders at H-30.

PACKHORSE OUT

No, that´s some sort of German battle field sarcasm....

[Gibsonm]

So its H-30 and I'm switching between SB and PzBtl 911 TS locations ...

[Tjay]

Me too. And nobody there....

[Falli]

Wasn´t it 1800 GMT?

[Tjay]

Yes, and it's now 18:00 GMT - 20min. (19:00BST - 20min).

[Zipuli]

Thanks guys! It was fun to recon, and we did way better than I thought! AAR to follow.

[Gibsonm]

Yes sorry I had to cut and run but I used up my time allocation "pre H Hr" waiting.

Some issues with pathing (unsure if it was lag or turning circles of vehicle type, etc.).

Anyway the Engrs who had to get out and walk because their ride drowned at the first crossing (before we got to the start point) were able to help secure OBJ YODA so they had a nice stroll.

[Marko]

A good mission

Very well coordinated.

[Tacom]

Nothing as a hasty attack to improve coordination!!!

[Hedgehog]

Well I spent an hour sitting around waiting, then dropped about 30mins in.

Eh shit happens, but the waiting around while stuff was planned to nth degree was a bit much.

Can we stick to a 30 mins briefing time, and any further briefing is done Oscar Mike?

[Gibsonm]

Well yes.

I appreciate it doesn't affect everyone but getting up at 0300 so I'm in the chair and ready for orders at 0330 for a 0400 "start" (i.e. the scenario starts) does become an issue when we actually "started" at about 0500 and then the first 30 mins was just driving to the "start point".

PACKHORSE crossed the LD at about 0600 and I was meant to be on the road at 0730 for RL.

Now in RL I have a radio and I can issue radio orders while moving.

If this becomes the "norm" because everybody assumes that everybody else has nothing else to do, then I'll have to abandon participation in these because I at least DO have something to do after Steel Beasts because its the morning.

The other option is to continue to play but then just drop when I reach my personal "no later than" time and the CO gets stuck with another unit to look after.

[Tango29]

Well yes.

I appreciate it doesn't affect everyone but getting up at 0300 so I'm in the chair and ready for orders at 0330 for a 0400 "start" (i.e. the scenario starts) does become an issue when we actually "started" at about 0500 and then the first 30 mins was just driving to the "start point".

I think that there are two elements that, if addressed effectively, can reduce or remove the high level of coordination currently required to get an exercise of this magnitude underway on time, "on the Day:"

a. An early identification of the key players; and

b. Passage of orders from CO to key players as soon as possible

First, to use this exercise as an example, we needed seven key players: CO, FO, HQ platoon, Recce, Tank CO, Mech Inf CO, CSS CO. Subordinate players can be identified later, although as soon as possible.

Second, there were three weeks from the first announcement of the mission to Startex. It is in this time frame that the CO gets his BG orders, writes and issues his orders to his key players, and finalizes his plan. This can be done via personal messages, emails, or by TeamSpeak meetings. The intent is that, at a minimum, the key players know the plan prior to joining TS about 30-45 minutes before Startex. That time is used to set up whisper lists and to brief the individual platoon and vehicle players if this briefing has not been done earlier. If these players have been identified earlier, then the key players can brief them in much the same way as the CO briefed them: PM, email, TS. You can imagine how quickly the mission could start if players arrived fully briefed as to their role and the role of their subunit.

I fully realize that none of us has a fully operational crystal ball. I note that a few stalwarts could not play, or got called away just prior to the mission. Others will join “on the day,” because the unforeseen opportunity arose or for other reasons. But I think that we’d get the “80% solution” at least if we can get most of our key players identified and briefed early on.

One final thought. For a few good and valid reasons I’ve been comfortable playing at the platoon/sub-sub-unit level. For example, I think that I’ve CO’d one, maybe two, TGIFs, and I might have run a company or two now and then in a few scenarios. But if I’m going to post thoughts like this, I’d better start stepping up a bit.

Another final thought: I’m not downchecking anyone in the SB family. These are only my thoughts, put forward for consideration. If I’m off-track or light years away from reality, feel free to let me know and get me aimed in the right direction. Who knows? There may be features in the soon to arrive SB update that might make some of the required coordination easier. We’ll see. TIA for any constructive criticism!

[Tjay]

All sounds eminently sensible to me Tango.

[Gibsonm]

Second, there were three weeks from the first announcement of the mission to Startex.

Yes but I think a quick check of the posts above would confirm that Zipuli was busy for a large slice of time between announcing the event and getting orders to Duke a couple of days prior.

Certainly Red Tide 85 showed that orders can be issued earlier and then confirmatory ones given on the day (assuming subordinates actually read what is sent to them ).

Guess we'll find out on the count down to LNoT in June.

As for features in 3.0 that might help - well that would be telling.

[Tjay]

Certainly Red Tide 85 showed that orders can be issued earlier and then confirmatory ones given on the day (assuming subordinates actually read what is sent to them ).

And that subordinates are actually sent the orders. Oh, and that the orders do not contain a mass of jargon impenetrable to all except professional soldiers.

[Gibsonm]

And that subordinates are actually sent the orders. Oh, and that the orders do not contain a mass of jargon impenetrable to all except professional soldiers.

Sorry not sure if that's a dig or not?

Pretty sure all my subordinates [those that commanded the various nationalities] received orders in good time (indeed they may have complained of being swamped with too much communication).

If they didn't pass stuff on to you - well I can't speak to that.

[Hedgehog]

And that subordinates are actually sent the orders. Oh, and that the orders do not contain a mass of jargon impenetrable to all except professional soldiers. :smile:

Sorry not sure if that's a dig or not?

Pretty sure all my subordinates [those that commanded the various nationalities] received orders in good time (indeed they may have complained of being swamped with too much communication).

If they didn't pass stuff on to you - well I can't speak to that.

All this sniping.... :Marine:

Can I say something?

Its in the past.

Move on.

And:

If you have queries, ask.

Learn from the mistakes.

[Tjay]

All this sniping.... :Marine:

Can I say something?

Its in the past.

Move on.

And:

If you have queries, ask.

Learn from the mistakes.

Pointing out things that were a factor in past exercises and which MIGHT POSSIBLY stand improvement for LNoT 08/06 is not sniping.

In Red Tide, I know Mark sent out orders in good time to HIS subordinates, but they sometimes didn't pass them down the chain. That might be worth looking at. And it is very easy for those for whom jargon is part of their daily lives to not realise that simpler language (or a note saying what a particular acronym means) is very helpful to non professionals.

[Tjay]

Sorry not sure if that's a dig or not?

Pretty sure all my subordinates [those that commanded the various nationalities] received orders in good time (indeed they may have complained of being swamped with too much communication).

If they didn't pass stuff on to you - well I can't speak to that.

Not intended as a dig - but I accept that my choice of words makes it look like that. Apologies. I hope my reply to Hedge makes things clearer.

[Hedgehog]

Pointing out things that were a factor in past exercises and which MIGHT POSSIBLY stand improvement for LNoT 08/06 is not sniping.

In Red Tide, I know Mark sent out orders in good time to HIS subordinates, but they sometimes didn't pass them down the chain. That might be worth looking at. And it is very easy for those for whom jargon is part of their daily lives to not realise that simpler language (or a note saying what a particular acronym means) is very helpful to non professionals.

Not intended as a dig - but I accept that my choice of words makes it look like that. Apologies. I hope my reply to Hedge makes things clearer.