≈$3.23B Navy DEFINITIVE CONTRACT N0001908C0023

An accounting code still sits at the front of the description — a Navy contract of $3.23 billion

Department of the Navy 2008-04-22 〜 2023-03-31

A Navy contract signed in 2008 and closed on 31 March 2023, obligating about $3.23 billion. Its description begins with the machine-facing prefix TAS::17 1319:: before the programme name starts.

Contract key facts

  • RecipientNorthrop Grumman
  • Contract value$3,229,122,597 (≈$3.23B)
  • BranchNavy
  • Awarding agencyDepartment of Defense
  • Awarding sub-agencyDepartment of the Navy
  • Award typeDEFINITIVE CONTRACT
  • Period of performance2008-04-22 〜 2023-03-31
  • Contract ID (PIID)N0001908C0023

Contract scope (original)

TAS::17 1319::TAS SYSTEM DEVELOPMENT AND DEMONSTRATION

Key points

  • Signed by the Department of the Navy on 22 April 2008 and closed on 31 March 2023 for about $3.23 billion.
  • The description begins with the machine-facing prefix TAS::17 1319::.
  • Three of the Defense Department contracts kept here have descriptions starting with that prefix.
  • With the prefix removed, the text reads as the name of work at the development and demonstration stage.

1Symbols come before the sentence

In the previous article the description held a single meaningless word. Here the description does carry a real programme name — but something else is attached in front of it.

The string in the descriptionTAS::17 1319::TAS SYSTEM DEVELOPMENT AND DEMONSTRATIONa machine-facing prefix leads
Descriptions starting with that prefix3among the 208 Defense Department contracts this site holds as of 2026-09-05
Period of performance22 April 2008 to 31 March 2023about fifteen years

2Strip the prefix and it reads as a description

Remove TAS::17 1319:: and a programme name is what remains. The part to discard and the part to read share one field.

  1. 1Read it as it standsSymbols, digits and English run together and the sentence has no clear start
  2. 2Spot the prefixThe segment before the double colons is machine-facing identification
  3. 3Take the programme nameWhat is left names work at the development and demonstration stage
  4. 4Note the limitWhich system it refers to cannot be pinned down from this field alone

3Why the shape of the record survives

Federal spending data is assembled by passing through several systems. Identifiers added along the way are not always stripped before the end. The legacy lines seen in the two previous records are the same phenomenon in a different form.

The next article takes up a health-care contract sitting inside the defence spending data.

Why it matters

Descriptions can carry identifiers picked up during collection. In any system that searches or classifies on this field, results turn on whether the preprocessing removes those prefixes.

FAQ

What does TAS::17 1319:: refer to?
The record does not explain it. It has the shape of a federal accounting identifier, but that cannot be confirmed from the record, so this article treats it simply as a machine-facing prefix.
Are prefixes like this common?
Three of the 208 Defense Department contracts kept here begin this way. That is a small number, but enough to cause misses in a search.
Can the description be searched as-is?
Stripping prefixes and separators first will reach more records. Design the processing on the assumption that the field has no fixed format.

Sources (primary)

This article is an independent organization based on the U.S. official spending data below. Verify the exact, latest details with the official source.

#Defense contracts#Department of the Navy#Contract closeout#Data quality#Reading the data
Disclaimer: This site independently summarizes and classifies information based on official data sources. Always verify the latest and accurate information with the official sources. Content on finance, health, legal, and security is information, not advice. This site is not an official website of the U.S. government.