Step 2 determines how the operational environment affects both friendly and enemy operations. Where Step 1 establishes where the operation takes place, Step 2 explains how the environment influences the conduct of operations: mobility, observation, fields of fire, cover and concealment, obstacles, infrastructure, weather and civil factors. The result forms the foundation for threat evaluation (Step 3) and COA prediction (Step 4).
Terrain touches nearly everything: movement, observation, fire support, logistics, communications, survivability, tempo and decision making. A good terrain analysis identifies opportunities and constraints — for both sides.
| Framework | Primary use |
|---|---|
| OAKOC | NATO / US Army — the standard |
| OCOKA | US Marine Corps — different sequence |
| RABVI | Several European armed forces — maneuver-oriented |
| MCOO | Integrated terrain product |
The methods address the same factors from different analytical perspectives; pick one and apply it consistently.
OAKOC — the five terrain factors
Observation & Fields of Fire. Where can you observe and engage? Determines detection, target acquisition, surveillance, fire control and collection. Question: which positions dominate the battlefield, where is dead ground? Good observation: hilltops, tall buildings, ridgelines. Poor observation: dense forest, urban canyons, valleys, fog.
Avenues of Approach. Routes that let a force reach its objective: roads, valleys, river crossings, forest tracks, mountain passes, streets. Assess width, capacity, trafficability, speed, protection and accessibility.
Key Terrain. Any location whose control provides a marked advantage: bridges, passes, high ground, airfields, communication hubs. Test question: "if this terrain is controlled, who gains the operational advantage?"
Obstacles. Obstacles delay, disrupt or canalize movement. Natural: rivers, lakes, marshes, mountains, dense forest. Man-made: minefields, demolitions, barricades, anti-tank ditches, rubble. Obstacles are existing, reinforced, or created during operations.
Cover & Concealment. Two different concepts: cover protects against fire (concrete walls, bunkers, reverse slopes); concealment only protects against observation (vegetation, smoke, darkness, camouflage). Good concealment does not automatically provide cover.
| Element | Key question |
|---|---|
| Observation | What can be seen (and hit)? |
| Avenues | Where can forces move? |
| Key Terrain | What terrain is decisive? |
| Obstacles | What restricts movement? |
| Cover | Where can forces survive? |
RABVI and OCOKA
RABVI is used in several European armed forces and starts with movement rather than observation: Routes (specific roads: load classification, width, choke points, alternatives) · Axes (broader maneuver corridors containing multiple routes) · Barriers/obstacles (from a maneuver perspective: does it stop, delay or canalize?) · Visibility and fire (which routes are exposed, where can overwatch positions be established?) · Influential terrain (equivalent of key terrain).
OCOKA is content-identical to OAKOC in a different sequence (Observation, Cover & concealment, Obstacles, Key terrain, Avenues) and is used primarily by the US Marine Corps.
All three frameworks lead to the same conclusions. The framework is a completeness checklist — not an end in itself. Pick what the staff knows and apply it consistently.
Route Alpha (★★★★☆): suitable for tanks, IFVs and logistics. Threat: enemy observation from Hill 201 dominates the middle stretch — requires overwatch or smoke.
Air force example: integrated air defense as 'terrain'
For air operations, the Integrated Air Defense System (IADS) plays the role terrain plays on the ground: it determines where you can fly safely, where you'll be observed, and where you'll be hit. Translating OAKOC into the air domain:
| OAKOC element | Air force equivalent |
|---|---|
| Observation & Fields of Fire | Radar coverage and Weapon/Missile Engagement Zones (WEZ/MEZ) |
| Avenues of Approach | Low-level ingress corridors below the radar horizon, gaps between SAM envelopes |
| Key Terrain | GCI radar stations, AWACS orbits, critical airfields |
| Obstacles | SAM belts and no-escape zones that rule out a straight-line course |
| Cover & Concealment | Terrain masking (flying low behind hills), ECM/chaff/flares |
The result is a combined threat overlay: a map of overlapping threat rings (SAM range, fighter CAP areas, AAA coverage) — the air force equivalent of the MCOO. Gaps between the rings form the "avenues of approach" for a strike package.
An SA-10 site with a 150 km range partially overlaps a short-range SA-8 system. The overlay reveals a 20 km-wide corridor where the two threat rings just fail to touch — the designated ingress route, provided the aircraft flies low enough to stay below the SA-10's radar horizon.
Engagement zones: from separated zones to the JEZ
The threat rings from the previous section are not arbitrary circles: they belong to formal engagement zones — airspace volumes in which responsibility for engaging air threats is assigned to one type of weapon system. Assigning those zones is the core of airspace control: it prevents friendly fighters and friendly SAMs from getting in each other's way — or worse, shooting each other down.
| Zone | Full name | Engaged by |
|---|---|---|
| WEZ | Weapon Engagement Zone | Generic term — the volume within which one weapon system can engage |
| FEZ | Fighter Engagement Zone | Fighter aircraft — usually above and beyond the range of surface-based AD |
| HIMEZ | High-Altitude MEZ | Long-range SAMs at high altitude (e.g. Patriot, S-400) |
| LOMEZ | Low-Altitude MEZ | Medium-range SAMs at low altitude |
| SHORADEZ | Short-Range AD Engagement Zone | Short-range systems around a specific object or unit |
| JEZ | Joint Engagement Zone | Fighters and SAMs simultaneously in the same volume |
Classically these zones are separated in space: fighters above a line, SAMs below it — deconfliction by procedure rather than real-time coordination. That costs effectiveness (part of the airspace is "locked" for one party) but is safe. A FEZ combined with a MEZ also poses a double dilemma for the attacker: evading the SAMs pushes him up toward the fighters, and vice versa.
The Joint Engagement Zone (JEZ)
The JEZ drops the spatial separation: fighters and SAMs operate in the same airspace at the same time. In theory the maximum density of firepower — but historically largely avoided, for three reasons:
- Combat identification — without reliable identification (IFF dropout, limited non-cooperative target recognition), a SAM battery cannot reliably distinguish a friendly fighter from an enemy;
- Fratricide risk — in shared airspace the chance of friendly fire on friendly aircraft is real;
- C2 blindness — the battle managers lacked real-time awareness of the position, identity and intent of all platforms at once.
Modern networks do make the JEZ feasible (the JAPCC calls it "JEZ+"): Link 16 / MIDS datalinks share tracks and task changes in near-real-time, sensor federation merges separate radar pictures, and electro-optical identification pods complement IFF. The hard requirements remain: robust combat ID, near-real-time C2 and tight airspace discipline — without all three, the JEZ collapses into fratricide.
The adversary's zone structure reveals his C2 maturity. An adversary who can only run separated FEZ/MEZ zones leaves exploitable seams and time windows between them. An adversary who can run a true JEZ has no "gaps" between fighter and SAM coverage — and is substantially more dangerous. So assess not just the systems but the integration.
These zones are moreover no longer bounded by the weapon system's own radar horizon: see the deep dive on third-party targeting in Chapter 7, where the network extends the engagement zone beyond what a single sensor can see.