[SG] ITTT ETRU (was: Questions)

Thanks for the clarification.

I think it works out about the same either way, I just wanted to know if I was
missing something official.

But as I said I like the Fire Team concept as it better fits the ITTT forces.
It give the smallest unit more flexibility (but also has drawbacks).

Basic Economic Threat Response Unit (Platoon): Mission Leader
                 |   \
                 |  Support Staff (rest of HQ unit)
                 |
      -----------------------------------------
      |            | | | | |        |         |
Enforcement Unit  EU |EU |EU  Specialist Unit SU
      |             EU  EU    (Mission specific
   ----------------            attachment from
   |      |   |   |            company level.
Security  S   S*  S*	       [Engineer, EW, etc.])
*May have support weapon
 (GMS/P, PPG)

In some ways this arrangement is more flexible than a regular command. But it
can also be less flexible when transfering activation from command.

Temporary groupings of EUs may be made by the use of a communication action by
the mission leader and a reorganize action by each EU. This allows for
multiple EUs to be activated at once, but they must remain within unit
integrety distance (or use detachment rules). Reverting to the standard
organization only takes a communication action from the mission leader. All
EUs are treated as an individual unit except that they are activated together.
Each EU maintain thier own leadership and confidence markers. No leadership
transfer is possible between the temporary grouping leaders (no true command
for the group, all are just waiting for the 'go' command from the Mission
Leader). No more than 2 EUs may be grouped together in this manner. Basic ETRU
with temporary grouped EU: Mission Leader
                 |   \
                 |  Support Staff (rest of HQ unit)
                 |
      ----------------------------------
      |            |   |   |   |   |   |
Temp Action Group EU EU EU EU SU SU
      |
    -----
    |   |
   EU  EU

-----
Brian Bell bkb@beol.net