What This Field Means
The operation, campaign, exercise, contingency, or standing plan in which a command relationship or unit activity applies.
This tells readers the operation, campaign, exercise, contingency, or standing plan within which a unit fact or command relationship applies. It prevents a temporary wartime or exercise arrangement from being mistaken for permanent organization.
How to Read It Correctly
Operational context is not mission function, area of responsibility, operating location, or current status. A named operation can span several places and missions while the same unit also has enduring peacetime relationships.
Example
A named deployment, campaign, joint exercise, or contingency response.
Technical Specification
The database column is [USMIL-Unit].[Unit].[OperationalContext]. Required context summary related to the Operational context ontology. The current field often contains the specific named context rather than only a category.
Use the controlled context category and retain the specific official name in the associated evidence or relationship. Include dates when known so the context does not leak into periods where it did not apply.
| Property | Definition or current value |
|---|---|
| Database column | OperationalContext |
| Column order | 37 |
| SQL data type | nvarchar(256) |
| Kind of information | Ontology-controlled classification with a scalar Unit-table summary |
| Cardinality | Unit table: one scalar summary per row. Ontology dimension: multiple; time-varying: true. |
| Required | Yes |
| Database default | No database default |
| Key or relationship | None |
| Database check constraint | ([CurrentStatus]=N'Planned' OR [CurrentStatus]=N'Status unknown' OR [CurrentStatus]=N'Historical' OR [CurrentStatus]=N'Inactive' OR [CurrentStatus]=N'Current') |
| Live population | 9341 of 9341 Unit records (100%) |
| Distinct nonblank values in the live table | 2059 |
| Live profile measured | September 2, 2026, 20:43 UTC |
Allowed Values and Definitions
The complete active controlled vocabulary is listed below. The ontology is authoritative for normalized options. Narrative or legacy phrases found in the scalar Unit-table column are current data expressions, not additional approved options.
| Ontology property | Definition |
|---|---|
| Ontology dimension | Operational context |
| Dimension number | 20 |
| Ontology definition | Operation, contingency, exercise, campaign, plan, or other relationship context. |
| Ontology cardinality | multiple |
| Changes over time | Yes |
| Active controlled options | 11 |
| Canonical option | Code | Plain-language definition | Technical definition |
|---|---|---|---|
| Unknown | unknown | The evidence reviewed so far does not establish a value. | No supported value is asserted; this is an evidentiary state, not a positive classification. |
| Not applicable | not-applicable | This question does not apply to this kind of unit or relationship. | The dimension is intentionally inapplicable to the subject type; it is not missing data. |
| Unresolved | unresolved | The unit is known, but the available evidence does not yet settle this particular point. | Confirms that resolution remains open after review without asserting a competing value. |
| Needs review | needs-review | The retained evidence needs additional review before a reliable value can be shown. | Places the assertion in a review-required disposition rather than accepting a substantive value. |
| Source conflict | source-conflict | Reliable sources disagree, so the guide preserves the disagreement instead of choosing one silently. | Records an unresolved conflict among retained sources and prevents false canonical certainty. |
| Operation | operation | Operation means an organized military action or set of actions conducted to accomplish a defined objective. | Controlled operational-context code 'operation' in ontology Dimension 20. The specific named context, participating relationship, evidence, and effective dates must remain separately traceable. |
| Contingency | contingency | Contingency means a situation requiring military operations in response to natural or human-caused events, emerging threats, or other uncertain conditions. | Controlled operational-context code 'contingency' in ontology Dimension 20. The specific named context, participating relationship, evidence, and effective dates must remain separately traceable. |
| Exercise | exercise | Exercise means a planned training or rehearsal event used to practice, evaluate, or demonstrate military capabilities and command relationships. | Controlled operational-context code 'exercise' in ontology Dimension 20. The specific named context, participating relationship, evidence, and effective dates must remain separately traceable. |
| Campaign | campaign | Campaign means a series of related military operations designed to achieve strategic or operational objectives within a given time and space. | Controlled operational-context code 'campaign' in ontology Dimension 20. The specific named context, participating relationship, evidence, and effective dates must remain separately traceable. |
| Standing plan | standing-plan | Standing plan means an approved continuing plan under which forces, responsibilities, or relationships are arranged before execution. | Controlled operational-context code 'standing-plan' in ontology Dimension 20. The specific named context, participating relationship, evidence, and effective dates must remain separately traceable. |
| Another operational context | another-operational-context | Another operational context is used when authoritative evidence establishes a specific context that does not fit operation, contingency, exercise, campaign, or standing plan. | Controlled catch-all code 'another-operational-context' in ontology Dimension 20. Use requires explicit source support; recurring concepts should receive a separately defined extension rather than accumulating as unexplained catch-all data. |
How the Live Unit Table Uses This Field
The scalar Unit-table column currently contains 2059 distinct nonblank expressions. The 20 most frequently used expressions are shown below; these are evidence-derived or legacy contents, not extra controlled options.
| Observed live expression | Live Unit records |
|---|---|
| Institutional context | 5320 |
| Official retained-body source-period identity | 359 |
| Army lineage register effective through 1 October 1997 | 319 |
| Current official organizational context | 173 |
| Historical official organizational context | 54 |
| Official retained-body source-period identity; source date signal 1990 | 33 |
| Official retained-body source-period identity; source date signal 1944 | 23 |
| Current commissioned-command context | 23 |
| Official Department of the Air Force security forces squadron operations | 23 |
| Historical Navy aviation squadron | 22 |
| Official historical Marine aviation operations | 20 |
| Official Department of the Air Force operations group operations | 20 |
| Official NHHC source-period identity | 19 |
| Official Department of the Air Force logistics readiness squadron operations | 19 |
| Historical numbered Marine regiment | 19 |
| Official retained-body source-period identity; source date signal 1943 | 18 |
| Fall 1972 Sub Unit One, 1st ANGLICO deployment chart | 18 |
| Historical commissioned-command context | 17 |
| Official retained-body source-period identity; source date signal 1918 | 17 |
| Official Department of the Air Force mission support group operations | 17 |
Missing, Unknown, and Conflicting Information
This column cannot be NULL in the Unit table. When the underlying fact is incomplete, the record must use an allowed explicit disposition or a supported evidence-derived statement. Required storage does not mean that every historical fact is known, and it never authorizes a guessed value.
The controlled uncertainty values are deliberately different: Unknown means evidence has not established a value; Unresolved means the question remains open after review; Needs review identifies work still requiring evaluation; Source conflict preserves disagreement among retained sources; and Not applicable means the dimension does not apply to the subject.
Connections to Other Fields
- Operational Command — The command directing or employing the unit for an operation, deployment, exercise, or assigned mission.
- Assignment Status — How the unit is connected to another command—assigned, allocated, attached, supporting, or supported.
- Command Authority — The kind of authority one commander or command has over the unit for a particular purpose.
- Operating Location — A place where the unit is operating, deployed, detached, or rotating, which may be different from its home station.
- Effective From — The date from which the facts represented by this unit record are known to apply.