What This Field Means

The kind of independently recognizable military identity represented by the record, such as a unit, command, formation, or task organization.

This answers the first identity question: what kind of separately recognizable military organization is this record claiming to represent? It helps distinguish a unit, command, formation, task organization, or commissioned command from a name fragment, office, asset, or alias.

How to Read It Correctly

Identity class is not the service branch, echelon, mission, or broad organization class. It describes why the subject has an independent organizational identity, not where it sits in the force structure.

Example

Unit, Command, Formation, Task organization, or Commissioned command.

Technical Specification

The database column is [USMIL-Unit].[Unit].[UnitIdentityClass]. Evidence-derived identity classification used during canonicalization. It is currently semi-controlled and more specific than the formal organization-class vocabulary.

The field currently stores evidence-derived phrases rather than a database-enforced menu. Use the narrowest supported identity description, and preserve uncertainty explicitly instead of forcing a confident class from the unit’s name alone.

PropertyDefinition or current value
Database columnUnitIdentityClass
Column order5
SQL data typenvarchar(128)
Kind of informationEvidence-derived text
CardinalityOne stored value per Unit row.
RequiredYes
Database defaultNo database default
Key or relationshipNone
Database check constraint([CurrentStatus]=N'Planned' OR [CurrentStatus]=N'Status unknown' OR [CurrentStatus]=N'Historical' OR [CurrentStatus]=N'Inactive' OR [CurrentStatus]=N'Current')
Live population9341 of 9341 Unit records (100%)
Distinct nonblank values in the live table178
Live profile measuredSeptember 2, 2026, 20:43 UTC

Allowed Values and Definitions

No preset menu applies to this field. It stores an identifier, relationship, measurement, date, timestamp, or evidence-derived narrative. Valid content is governed by the SQL type, key relationship, nullability, retained evidence, and the field-specific recording rule above. A list of observed contents would be data, not a list of allowed options.

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.

Connections to Other Fields