| Area | Definition | Determined by |
|---|---|---|
| Area of Operations (AO) | The area in which the unit is authorized and responsible to operate | Assigned by higher headquarters |
| Area of Interest (AI) | The area from which information is needed because developments there could affect the mission | Established by commander/S2 |
| Area of influence | The area in which the unit can achieve effects with its own assets (sensor and weapon range) | Follows from own capabilities |
The AI is always larger than the AO: enemy reserves, artillery, air support and logistics that could affect the AO are usually located outside it. Rule of thumb: include everything from which the enemy could bring effect within the operation's timeline — in both distance and time.
A battalion is assigned a 15 × 20 km AO for an attack on a river crossing. The S2 sets the AI at 60 km depth: within it lie the enemy divisional reserve (2 hours' drive), the artillery grouping (in range from 35 km) and the airfield from which attack helicopters could reach the AO within 30 minutes.
The dimensions of the battlespace
The battlespace is more than a flat plane on the map. Define every relevant dimension:
- Ground — the classic AO/AI plane, including subsurface infrastructure in urban terrain;
- Air — altitude bands, air corridors, air defense range on both sides;
- Electromagnetic spectrum and cyber — jamming, communications, enemy EW coverage;
- Information environment — media, social networks, population sentiment;
- Time — the planning horizon: how far ahead must the analysis predict?
The most frequently forgotten dimension is time. A reserve 200 km away is irrelevant to a four-hour raid, but critical to a week-long defense. An AI without a time horizon is meaningless.
Limits, boundaries and coordination
When defining the battlespace, explicitly record:
- Imposed boundaries — higher headquarters' boundaries, phase and coordination lines;
- Adjacent units — who is left, right, ahead and behind; where are the seams the enemy could exploit;
- Restrictions — no-strike lists, restricted areas, cross-border limitations (ROE);
- Responsibilities — who covers the parts of the AI outside the own AO? Usually higher headquarters; record what information you need from there.
Air force example: battlespace geometry for air operations
For an air force analyst the AO is not a ground plane but a set of airspace volumes: altitude bands (strata), sectors and corridors. Step 1's scoping translates into very different overlays than for ground operations:
- ADIZ (Air Defense Identification Zone) and FIR boundaries — where identification requirements and jurisdiction begin and end;
- No-fly zones and restricted airspace — the air force equivalent of no-strike lists;
- Altitude bands — low (below the radar horizon, vulnerable to short-range SAMs and small arms), medium and high (within range of long-range SAMs);
- Corridors and tanker tracks — fixed ingress/egress routes and air refueling areas, comparable to mobility corridors on the ground;
- AI over time — the AI extends as far as enemy fighters, long-range SAMs or AWACS coverage can reach within the mission duration — often hundreds of kilometers beyond the ground-based AO.
A strike package is assigned an AO spanning the airspace between FL200 and FL350 over the target area. The AI is set at a 400 km radius: within it lie enemy fighter base Zvezda (10 minutes' flight time), a long-range SAM site (300 km range), and a GCI radar station covering the entire corridor.
The analytical process (setting boundaries, selecting significant characteristics, identifying gaps) stays identical — only the geometry changes from a plane into a volume.