-Celibrae- wrote:Is it cheaper to have divisional slice in brigades (like a BCT) or in the division?
Neither, because that's not what the "division slice" is.
The "division slice" is the total amount of manpower needed to support a division including personnel that would never be part of the division anyway. The division slice for a US division is 40,000-50,000 men, meaning that for a 20,000-man division, there's an additional 20,000-30,000 men in various roles needed to support it. That includes everything down to the extra clerks in the personnel records department needed to keep those extra records straight, who would never be part of the division in the first place.
Direct CSS personnel are generally included in the division's TO&E in the first place, so they're not part of the "slice."
I have no data to back this up but I suppose in theory it might be cheaper to place the CSS at the division if you wanted to be really skimpy, because then you could use smaller CSS formations and parcel them out by priority only to the units that need it. It is possible that not every subordinate brigade will need all of its expected CSS at any given point so with a division-based CSS element you could try to get away with not having a full complement for every brigade, but this might cause problems in the event that every brigade
does need its CSS, such as if every subordinate brigade finds itself in combat or conducting an advance. Both of which are times when you really don't want to find yourself short on logistics.
If you're keeping the same CSS element size though then it doesn't matter where it's placed in regards to cost. The major costs are personnel salaries followed by the cost of maintaining that formation in the field (supplying fuel, food, water, etc.), and these costs don't change based on whether they report to the brigade commander or the division commander. In practice, they will be deployed to the same places anyway and division-based units will be attached to line units so that they can be supported.