07.06.2014 Views

Considering a Cadre Augmented Army - RAND Corporation

Considering a Cadre Augmented Army - RAND Corporation

Considering a Cadre Augmented Army - RAND Corporation

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

-184- An Operational Analysis of <strong>Cadre</strong><br />

Figure 3.2—Tillson et al Ready-Standby Organization 71<br />

Tillson et al argued that the Ready-Standby Organization could both reduce costs<br />

and increase unit cohesion compared with the force structure that existed at the time. It is<br />

not important to go into further detail about the RSO except to say that the general principle<br />

of rotating units through cadre status over time may be another way to structure the cadre<br />

augmented forces proposed in this dissertation.<br />

3.3.2—An ARFORGEN Rotational <strong>Cadre</strong> Force<br />

We might think about applying the Ready-Standby Organization with to build a<br />

cadre augmented force. This would require significant changes to army personnel policies.<br />

However, these changes would be no more significant than some of the other options<br />

discussed in this chapter. Because the <strong>Army</strong> has recently adopted ARFORGEN, we consider<br />

reconciling RSO with ARFORGEN so that when a RSO unit is in active status it moves<br />

through the three ARFORGEN force pools. The rest of this subsection shows how we<br />

might apply the Ready-Standby Organization together with ARFORGEN.<br />

We might consider a rotating cadre force where some AC units spend three years in<br />

active (ready) status building capability over this time according to ARFOGEN and three<br />

years in cadre (standby) status. To maintain the same capability, there would have to be two<br />

____________<br />

71 Tillson et al (1990), p. I-9 [replicated]

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!