I will post here the preliminaries that I would as Controller provide the active player. These will be:

1. Declare which optional rules are used, not used 2. Declare house rules to be used 3. Define operational boundaries 4. Describe overall strategic situation 5. Issue US orders 6. Issue NPF Orders 7. List Corps & Army assets devoted to both sides. 8. Issue SITREP to the US player

Scenario 31.0 won't likely be a good controller scenario. The US player is initially attacking making it hard to set a Soviet response in stone. But the counters are clipped and I'm committed, so here we go.

The following will be used:

[15.0] Ammo supply [16.0] Chemical Warfare, including [16.7] “Preparation Detection.”

Per [16.7] both sides have declared preparation for Nukes and Chem Warfare before game start. Turn 3 will be first opportunity to use these.

[17.0] Electronic Warfare Option 3. The US has an EW strength of 3, the USSR 6. Both sides may operate in the same turn instead of only the strongest side. [17.4] ECCM is also used.

[18.0] Tactical Nukes, including [18.3] Neutron Warheads and [18.33] where only the US has Neutron Warheads, and [18.4] “Preparation Detection”

[19.0] All Division Commander rules will be used. [20.0] All Subordinate and Battalion Leadership rules will be used. [21.4] Non-divisional support will be used and detailed. [22.5] Division Commander use of Perception in the Controller Game will be used.

The following Optional Rules will not be used:

[16.6] Catastrophic use of Gas (doubles combat shifts and doubles MA penalty)

[18.17] Alternate Weapons Usage Rate (US could have used 3-5 Nukes/turn; USSR 5 to 8 ). Could render the game moot.

1. Each day has three 8-hour turns; two daylight and one night. Allow the present Operational Intel acquisition rate on the 2 daylight turns (turns 1 & 2). At the beginning of the night turn (turn 3) knock the accumulated Intel level down to 50% of the prior turn (turn 2 in this example). At the start of the 4th turn (morning of second day) reduce Operational Intel again to 50% of the prior night (turn 3). Repeat each 3 day cycle. While this house rule reduces the accumulated Operational Intel, it does not reduce Intel on individual units.

2. At the beginning of each Fog/Rain/Snow turn; diminish the Intel level of each non-HQ, COMBAT unit of the phasing player that is not adjacent to an enemy unit by 2 levels.

3. At the beginning of each Fog/Rain/Snow turn that is at Night; diminish the Intel level of each non-HQ, COMBAT unit of the phasing player that is not adjacent to an enemy unit by 3 levels.

4. At the beginning of each Fog/Rain/Snow turn; diminish the Intel level of each HQ that is not adjacent to an enemy unit by 1 level. Night will have no effect on HQ Intel diminishment.

5. [The following isn’t a house rule, but a repudiation of a prior house rule on this topic. What follows is simply my latest understanding of what the rules say]. In the Operational Intelligence CSP Allocation Segment both players allocate CSPs to OPInt. These are spent for the Operational Intelligence Level ONLY and are considered used for the entire game turn. In the following Active Player Intelligence Phase, the active player only allocates CSPs for Sector Coverage Ability in his Intelligence Phase. Although this level of sector coverage remains for the entire turn, the CSPs used for Sector Coverage are returned to the unused box once the active player’s Intelligence phase is complete. Both players then conduct OpInt, with the non-active player doing so with the sector coverage he paid for the prior turn.

6. Units coming out of reserve mode do not halve their MA for that turn. Additionally, units released from reserve mode make no fatigue roll if they possess no fatigue (f0 or below). If when released they possess a fatigue level of f1 or higher, they must roll for fatigue normally.

7. The Soviet may not deploy in 4-column March Order.

8. Below is a clarification of the NDC Controller Game graduated Intel states:

Intel 1: The presence of a unit will be indicated by blank counter anywhere within its actual sector.

Intel 2: The general type of unit (Mech, Armor, Inf, HQ) and location anywhere within its actual sector. A dummy counter with unit type indicated is used.

Intel 3: Exact unit type, designation and hex are revealed

Intel 4: Exact unit type, designation, hex and actual TO/E level are revealed

John, I set myself to deal with Reserve Mode part of the way. Haven't devised a Reinforcement set of rules for Reserve Mode, but here is the straggler part:

1. Roll for straggler recovery (1d6) at the beginning of each night turn when the below casualty levels are met. Always round down when rounding is required

2. Rgts/Bdes with losses at 30-40% of scenario start levels recover 1 step by rolling 1-3

3. Rgts/Bdes with losses at 41-60% of scenario start levels recover 2 steps by rolling 1-3

4. Rgts/Bdes with losses at 61-99% of scenario start levels recover 3 steps by rolling 1-3

5. Recovered steps are placed under the relevant Rgt/Bde HQ and kept there until they may be distributed

6. Recovered steps may be distributed to organic Bns as needed only when the subject Rgt/Bde is in RS mode and an eZOC-free pathway exists between recipient Bn and donating HQ

7. If the relevant HQ was destroyed by conventional CBF (non-Nuke/Chem), 66% of the recovered steps are immediately transferred to DIVTAC/ALT only if an eZOC-free path to those HQs exist

a. If neither DIVTAC/ALT are available, they are then transferred to DIVMAIN.

b. If no eZOC-free pathway to DIVTAC/ALT or DIVMAIN exists the recovered steps are lost

c. Recovered steps stored at Divisional HQs may be reintegrated directly into any Bn of any Rgt/Bde provided eZOC-free paths exist, and the recipient is in RS mode.

d. Recovered steps stored at Rgt/Bde HQ may only be reintegrated within that Rgt/Bde

8. If the relevant HQ is destroyed by overrun, barrage associated with overrun, Nuke or Chem warfare, all recovered steps are lost

9. Destroyed Rgt/Bde HQs may be reconstituted per the existing rules, but one may not use stored recovered steps to reconstitute lost HQs.

The northern map boundaries are setup as per the Scenario 31.0 special rules. All hex rows north of XX27 inclusive (use of half hexes is not permitted).

[Nov 6, 1979]: On Nov 1, 1979, after the autumn harvests in the USSR, the Soviet 8th Gds Army crossed the East German border southward, penetrating into the US VII Corps area of operations. The action took the 8th Gds Army South of Bad Kissingen, Schweinfurt and eventually to Wurzburg. Casualties are reported to be heavy on both sides. It is uncertain if the 8th Gd Army has sufficient strength to continue westward, South of Frankfurt. US VII Corps is rapidly depleting its reserves. At the same time, the 2nd Gd Tk Army, 20th Gds Army and 3rd Shock Army charged westward into the North German Plain, well North of Frankfurt. US Theater Command was greatly suspicious of the quiescent 1 Gds Tk Army in Dresden (7th Tk in Rosslau, 11th Tk in Dresden and 27th Gd MRD in Grimma). While Soviet axes of attack had been aimed North and South of Frankfurt, no offensive toward Frankfurt and REFORGER stations beyond had materialized. US Command reasoned that Allied reserves were intended to be drawn away from the V Corps operational area leaving Frankfurt vulnerable.

On Nov 4, 1979, a Soviet Motorized Rifle Division originating in Dresden attacked into the Fulda Gap’s southern route. Delaying actions by forward US Armored Cavalry Regiments, heavy US air attacks and likely fatigue brought the Russian Division to a standstill at the Marburg-Frankenburg Line where it has set up a triple line defense.

3AD, commanded by Maj-Gen York is to proceed in 2-column March Order along the Grossfelden-Zeigenhain axis attacking, and bypassing if necessary, defending Soviet units. Intel reports a Motorized Rifle Division has deployed into a 3-line defense near Marburg-Frankenburg. 3AD’s division goal is to penetrate these Soviet positions and provide rear area disruption via spoiling attacks, buying time for REGORGER deployments. All unallocated V Corps combat support assets will be diverted to support 3AD, 1Bde in particular. 1Bde shall create a breakthrough while 2nd & 3Bdes shall exploit. The 3/12 Armored Cavalry Squadron of the 11th Cav Rgt has been attached to 3AD Division command. 3AD is advised to expect Soviet armor beyond the MRD’s operational area.

3AD Command Maj-Gen York

ADC Bgdr Jackson

COS Bgdr Irwin

DAC Col. Falco

DSC Col. Peters

Until a viable ammunition LOC is reestablished, 27MRD is to deploy in 3-line defense. Forward phase line boundary shall be along the Wohra River-Frannenbrau line. Second phase line boundary shall lie along the Speckswinkel-Falken Holz line. The third line shall be deployed to counterattack only if the second line is penetrated. If attacked 27MRD is to hold its operational area of control at all costs. If not attacked, the 27MRD is to await resupply, at which time it shall continue van operations to Frankfurt. 11th Tk is to hold position ½ day’s march behind, positioned to exploit breakthroughs created by 27MRD.

Contingent Orders: In the event that 27MRD second line of defense is penetrated the 11th tank is to counterattack and destroy all Allied elements.

27MRD Commanded by Lt. Gen Perech; FDC Col. Zhelezo; COS Col. Lopatov; DAO Col. Sobaka

11 TD Command: Lt. Gen Derevo; FDC Col. Yarost; COS Col. Indkov; DAO Col. Radchik

US V Corps adds to the 3AD: 7 FA, 5 Sig, 6 Eng, 9 Air CSPs and 6 SPAs.

USSR 1Gd Tk Army adds to the 27MRD: 2 FA, 2 Sig, 4 Eng, 3 Air CSPS, and 2 SPAs.

USSR 1Gd Tk Army adds to the 11TD: 12 FA, 6 Sig, 8 Eng, 9 Air CSPS, and 4 SPAs.

Intel from surviving elements of the 11th US Armored Cav Rgt identified 2 light infantry, Motorized Rifle Regiments in the Soviet van. These formations were identified as the 92nd and 93rd BTR Rgts of the 27MRD, 1Gds Tk Army. 3 Tk Divisions are likely a day’s march or more behind the MRD. The US has 1 Armored Division, 1 Mechanized Division and 1 Mechanized Brigade to oppose. V Corps secured massive ground support with fighter escort to strike primarily at 27MRD ammo transport. Air reconnaissance presently shows the MRD to be situated in a 3-line defense. Approximately 70 kilometers to the northeast satellite Intel indicates a mobilized formation of Division size entering the Gap approximately 2 days out.

Weather forecasts show 30 to 40% chance of rain mixed with fog in the next several days. Expect combat tempo to be significantly hampered in the event of precipitation.

Although Soviet NBC preparations have been detected, permission to deploy tactical nukes will only be granted in the event of Soviet first use of Chem/Nuke assets. Corps HQ advises that all units should initiate NBC warfare preliminaries prior to engagement.

I've got a few generic Intel markers I need to make, and must repair the table after the cat swept my CSP display...Then I'll post some setup pictures and I'll start with turn 1 of 9.

I often tell my girls that the cat is what we'll eat when the power goes out.

The 27th MRD has the 92nd BTR Rgt as its forward defense deployed in TZ Mode,. The entire division's best leader, Col Zhavel is commanding with a +3 Rgt leadership drm.

According to Rezyn (aka Suvorov) in "Inside the Soviet Army" the 1 Gd Tk Army Commander may appoint Zhavel as the new 27MRD commander if anything were to happen to the current Division Commander, Lt. Gen Perech. He may be promoted over the First Deputy, the Chief of Staff, etc. As Suvorov says, p278, "Seniority depends not on rank, but appointment. Only when two officers have no professional connection with one another, is seniority determined by rank."

I'll keep this in mind when the 92nd gets overrun...save Zhavel for some greater destiny.

The 2nd line of defense sees the 93rd BTR and 91st BMP Rgts deployed with 2 Bns up front in DZ mode, and 1 behind in reserve (MD mode).

Further back lies the 94th Tk Rgt in MD mode. In 1978-1980 these tanks were likely T-72s. According to Isby, p.39-40 in his "Weapons and Tactics of the Soviet Army" the Groups of Forces in Germany got the lions share of T-72s, and only about 300 T-80s had been built by 1980. I suspect those would have been apportioned to Tk Divisions, and Independent Tk Bns first...Motorized rifle Divisions second.

Methinks SPI played with words when naming some of these Russian commanders. Durok commands the 93rd BTR, "Durok" means fool in Russian.

Here the Forward and Main HQs are deployed nearly side by side. Lt. Gen Perech is stationed in the Foward (DIVALT) HQ. At the DIVMAIN reside The First Deputy Commander (FDC) Col Zhelezo, the Chief of Staff (COS) Col Lopatov and the Division Artillery Officer (DAO) Col Sobaka. Sobaka is good with his +3 subordinate leadership rating.

Hmmm...Subaka means "dog" in Russian.. Subaka, Sobaka...

1 Bde is the assault Bde with 840 ammo pts. 2 & 3 Bdes, with 300 pts must be the exploitation forces. But the US March Order diagram doesn't show an echeloned, staggering of force entry. It looks like the 2 columns enter simultaneously...unless I am wrong. I intend to stagger them.

Anyone got any thoughts?

I’m not satisfied with how terrain is ignored when computing OpInt. So I’m creating a house rule regarding Operational Intel Level accumulation. It has 3 components:

1. Assigning Defensive Intelligence Values to terrain that is unit type specific

2. Applying a simple formula that makes OpInt accumulate as a rising sinusoid

3. Create automatic OpInt knock down rules to account for weather. These won’t apply to Tactical Intel.

1. Terrain Defensive Intel Values based on Unit Type:

2. OpInt Accumulation Formula: -Turn 1 (AM) & Turn 2 (PM) OpInt accumulates normally

-Turn 3 (Nite) OpInt is reduced at beginning of turn 3 to 60% of end of turn 2 level. Accum OpInt normally (but with no Air CSP use)

-Turn 4 (AM) Accum OpInt normally -Repeat this every 4 turn cycle

3. Auto knock-down of Intel Levels due to weather/night

-For each COMBAT unit not adjacent to the enemy, reduce its Intel level by 2 at the beginning of each Fog/Rain/Snow turn.

-For each COMBAT unit not adjacent to the enemy, reduce its Intel level by 3 at the beginning of each Fog/Rain/Snow turn at NIGHT.

-For each HQ unit not adjacent to the enemy, reduce its Intel level by 1 at the beginning of each Fog/Rain/Snow turn. Night will have no effect on HQ Intel diminishment.

So I worked a spreadsheet to see how my OpInt method would work over 9 turns. I chose, using my terrain defense values, the worst, best and medium case scenarios. Worst case was an HQ, in the open, in MO mode. Best case was an Airborne Infantry Bn in the City (def 2) in Prepared Defense Mode (def 4). The medium case was a Mech Bn in the woods (def 2) in RS mode (def 3).

The first cluster of data comes from knocking down the OpInt each night to 75% of the prior PM turn. Repeat the cycle every third (night) turn.

The second cluster is the dame thing, only making the knock down to 60% of the PM turn's OpInt levels.

The first graph shows the 75% knock down on OpInt each night turn and how that cycle accumulates Intel for easy to find, hard to find and moderately easy to find units.

The second graph is the same thing with a 60% knock down each night.

The knock downs create a kind of rising sinusoid of Operational Intel. As the game goes on, Tactical Intel will begin to dominate as troops become committed, but also CSPs will be more and more needed for combat rather than OpInt and Sector Coverage.

So the Y axes of the above graphs is the total Intel value illuminating the unit on a turn by turn basis (either HQ in open, Mech in woods or Abn Inf in a City. Other unit/terrain/mode combinations should appear anywhere between the Abn and HQ values).

The number on the y-axis is the opponents Opint Level, minus the terrain defensive value and mode defensive value.

The resulting number is then found across the top of the Intel table (below) and cross-indexed with the die roll. The resulting number in the Intel growth upon your unit.