Symbology & ORBAT Guide · Updated November 20, 2026 · By YELME MAP Team
MIL-STD-2525E symbology & ORBAT guide
Direct Summary
Modern MIL-STD-2525E and STANAG APP-6E symbology encodes every map entity inside a 30-digit Symbol Identification Code (SIDC) specifying version, context, standard identity/affiliation (Friendly, Hostile, Neutral, Unknown), symbol set (10 Land Unit, 15 Equipment, 25 Control Measure, etc.), headquarters/task-force/feint modifiers, and a 6-digit entity icon code. Pairing unit symbols with standardized Phase Lines (PL), Boundaries, and Engagement Areas creates briefings any staff reader parses immediately.
1. How 30-digit MIL-STD-2525E SIDCs organize the battlefield
Legacy 15-character alphanumeric SIDCs ran out of room for modern domains such as Cyberspace operations, UAV swarms, and granular civil infrastructure. MIL-STD-2525D/E expanded the code into a clean numeric structure divided across fixed blocks: Version (digits 1–2), Context/Standard Identity (digits 3–4, distinguishing Real vs. Exercise vs. Simulation and Friendly/Hostile/Neutral/Unknown), Symbol Set (digits 5–6), Status & HQ Modifier (digits 7–8), Echelon Amplifier (digits 9–10), Entity/Type/Subtype (digits 11–16), and sector modifiers.
Because the identity and symbol set live in predictable numeric slots, compatible tools such as YELME MAP and ATAK export cleanly via KML ExtendedData or CoT XML without flattening icons into mute pixel stickers.
2. The 16 core domains (1,370 entities)
| Set | Domain | Count | Usage in Exercise Planning |
|---|---|---|---|
| 25 | Control Measure | 269 | Check point, TRP, action point, release point |
| 15 | Land Equipment | 223 | Armor, artillery, radar, armored personnel carrier |
| 10 | Land Unit | 213 | Infantry, combined arms, armour, recon, mortar, engineer |
| 40 | Activity / Incident | 148 | Arrest, fire, demonstration, patrol incident |
| 20 | Installation | 129 | Airfield, power station, depot, bridge, hospital |
| 30 | Sea Surface | 93 | Frigate, corvette, carrier, amphibious assault ship |
| 60 | Cyberspace | 65 | Combat mission team, cyber protection, threat sensor |
| 36 | Mine Warfare | 59 | Bottom mine, moored mine, minefield sweep area |
| 01 | Air | 52 | Fighter, fixed wing, rotary wing, UAS, medevac |
| 27 | Land Dismounted Individual | 45 | Dismounted infantry, scout, medic, engineer |
3. Standard tactical graphic abbreviations
A unit icon tells readers who is on the ground; tactical graphics tell readers intent and boundaries. Keep control-measure labels concise so printouts stay legible at brigade scale:
| Prefix | Graphic Name | Geometry | Doctrinal Role |
|---|---|---|---|
| PL | Phase Line | Labeled line (both ends) | Movement coordination & timing checkpoints |
| LD / LC | Line of Departure / Line of Contact | Control line | Boundary marking assault initiation timing |
| BNDY | Unit Boundary (with Echelon Tick) | Solid segmented line + II / X / XX | Separates adjacent maneuver sectors cleanly |
| OBJ | Objective | Closed polygon | Terrain or facility assigned for seizure/control |
| EA | Engagement Area | Closed solid area | Killsite / fires focus box covered by direct weapons |
| AA / NAI / TAI | Assembly / Named / Target Area of Interest | Dashed polygon | Staging pockets, recon collection & strike triggers |
4. Pairing Order of Battle (ORBAT) with timed operational phases
Cramming an entire multi-day exercise onto a single static screenshot turns symbols into unreadable overlap. Organize your ORBAT around discrete operational phases (for instance, Phase 1 Covering Force, Phase 2 Main Defense, Phase 3 Counter-Attack) so unit positions, sector boundaries, and task-organization tables stay crisp on every exported briefing page.