Military Julian Date

The DoD ordinal date

Every U.S. Department of Defense supply requisition, every MILSTRIP document, every logistics transaction that moves an item of material through the joint-services supply system is stamped with an ordinal date — three digits, 001 through 366, identifying the day of the calendar year the document was cut. The format traces to the Military Standard Requisitioning and Issue Procedures (MILSTRIP), historically DoD 4000.25-1-M, which placed a four-character date in card columns 36–39: one digit for the last digit of the year, three digits for the Julian day.

A requisition cut on Thursday, June 18, 2026 carries the date code 6169. Combined with the service code, the unit DODAAC, and a sequence number, that four-character string forms the document number that uniquely identifies the transaction in every downstream joint-services database for the life of the record. The same three-digit day of year is one of the seven Julian date formats used across industry and science.

Why ordinal, not calendar?

Punched cards had 80 columns, and the original MILSTRIP definition allocated exactly four of them to the date. A full month-day-year in MM/DD/YY form needs six columns; a Julian ordinal date fits in four. In 1960 every column on a card was real estate that had to be fought for, so the savings were decisive — this was a hard constraint, not a stylistic choice.

Decades after the last card reader left active service, the four-character format persists for three reasons. First, it is unambiguous: no leading-zero month-versus-day confusion, no U.S.-versus-European ordering. Second, it sorts correctly as a plain integer, which makes inventory rotation and database queries trivial. Third, every supply clerk in every service is trained to read it, and retraining the entire logistics workforce across the Army, Navy, Air Force, Marine Corps, and Coast Guard is not a small undertaking.

MILSTRIP and the requisition document number

A MILSTRIP requisition (document identifier code A0_) is the standard “document of request” a unit uses to order material from the Defense Logistics Agency. The document number is a 14-character string with this structure:

A supply sergeant ordering materiel today would generate a document number along the lines of W06BAA6169001, where 6169 is the Julian date. That single string becomes the primary key for the requisition in every DLA database, every Global Combat Support System (GCSS) record, and every audit trail for the life of the supply record.

YJJJ vs. YYYYDDD in service practice

The legacy MILSTRIP format is YJJJ — one year digit, three day-of-year digits. The modern Defense Logistics Management Standards (DLMS) transactions that replace it are built on ASC X12 EDI, and their date elements carry the full four-digit year. A seven-digit YYYYDDD — today, 2026169 — eliminates the decadal rollover that left a single-year-digit code ambiguous between, say, 1995, 2005, 2015, and 2025.

The transition is not finished. Some older logistics systems still reject anything longer than four characters in the legacy date field, so the four-digit and seven-digit forms continue to coexist in the joint-services supply chains. An analyst working across both legacy MILSTRIP and modern DLMS needs to read both, which is why this site’s converter handles both, and the batch decoder covers the related codes on rations and packaged goods.

The document number as a unique key

The document-number system was designed so that every requisition generated by any unit in any service has a globally unique identifier. The Julian date is essential to that guarantee: it ensures a unit cannot produce two document numbers with the same serial number on different days. Combined with the DODAAC (unique to the requesting unit) and the serial number (which resets daily), the Julian-date component creates a namespace large enough that collisions are effectively impossible within the retention period of supply records.