NECC: the command system meant to modernize GCCS that w...

Around 2006 the Defense Information Systems Agency set out to modernize the software backbone that senior U.S. commanders use to run wars. The Global Command and Control System, or GCCS, had been in service since roughly the late 1980s and 1990s. It was aging and, by the standards of the mid-2000s web, stovepiped. The replacement effort was called the Net-Enabled Command Capability, or NECC. Its director pitched it as a kind of Travelocity or YouTube for command and control: one clean, web-based interface pulling together the information a commander needs. Roughly four years later, Congress directed the program's termination. Little operational capability had been fielded, and the money was redirected to keep the very system NECC was supposed to modernize running.

This post walks the documented record of NECC: what it was, what happened, what the primary sources actually establish, and where the popular retelling outruns the evidence. It is part of a series that tries to trace public money to primary sources and to keep the honest failure critique and the honest mission defense sitting side by side.

A caution up front, because this program is genuinely obscure and its acronym collides with several unrelated things. "NECC" also stands for Navy Expeditionary Combat Command, for Northern Essex Community College, and for the New England Compounding Center of the 2012 meningitis case. Every figure below is verified as belonging to the Net-Enabled Command Capability specifically. Where a number could not be confirmed from a primary source, this post says so plainly rather than repeating it.

What NECC was

NECC was a Department of Defense program managed by DISA to modernize joint command and control using net-centric, service-oriented, web-based capabilities. That framing is corroborated across the Director, Operational Test and Evaluation (DOT&E) annual reports for fiscal years 2007 and 2008, DISA budget documents, and contemporaneous trade press, so it can be stated plainly.

The program grew out of an earlier DoD Joint Command and Control effort. According to Washington Technology, that program was renamed NECC and advanced into technology development at Milestone A in March 2006. The exact "Milestone A, March 2006" phrasing rests on that single trade-press item, which is hard to fetch directly, but the roughly 2006 start is corroborated by DISA research-and-development budget timelines that reference NECC activity planned across fiscal years 2006 through 2013.

The architecture is where NECC's ambition shows. DOT&E's reporting describes a plan to build command and control as reusable, service-oriented "capability modules" delivered over three increments. Increment 1 focused on Joint Force Commander situational awareness and joint operations planning. To develop and certify those modules, NECC established what it called a Federated Development and Certification Environment, or FDCE. The idea was that instead of a single monolithic application, commanders would draw on modular web services that could be updated and recombined. DISA director Lt. Gen. Charles Croom, who championed the program, described the target as a single interface for command and control, comparing the vision to Travelocity and YouTube.

One nuance matters and is easy to get wrong. NECC is often described as a clean-slate replacement for GCCS. DISA's own budget documents frame it more precisely: NECC was to be incorporated into the GCCS "family of systems" through an incremental, spiral approach. So the accurate phrasing is modernization of GCCS rather than a single-swap replacement, and NECC should never be conflated with GCCS-J, the legacy Global Command and Control System-Joint that it was meant to modernize and that continued in service.

What happened

NECC did not deliver a fielded modern command-and-control platform. After years of development and systems-engineering work, DoD components could not agree on common requirements for a centrally-managed joint system. The Services, each with its own command-and-control equities, were unwilling to cede design authority to a single central program. That is the recurring theme across the sources: the failure was organizational and about governance, not a demonstration that the underlying goal was wrong.

The program was still active in mid-2009. A July 2009 Nextgov article described NECC as an ongoing effort and covered its contracting. By the time DISA submitted its fiscal year 2011 budget, in early 2010, NECC was shown terminated. That brackets the cancellation decision to roughly late 2009 or 2010. No single document reviewed here pins the termination to a precise day, so the honest label is "around 2010," or the FY2010 to FY2011 budget cycle.

The strongest primary evidence of both the termination and its aftermath is the DISA budget justification itself. DISA's FY2011 (and FY2012) budget documents state that GCCS-J funding increased because of the "realignment of NECC program funding to the GCCS-J program." In other words, the money that had been going toward modernizing the command-and-control backbone was rolled back into sustaining the legacy backbone it was supposed to modernize. The old system survived; the modernization program did not.

There is also a widely-repeated account that a congressional committee directed the termination, with language to the effect that, because of the unwillingness of the Services and others to agree to centrally-managed joint command-and-control modernization, the committee directed the termination of the NECC system. That quotation is load-bearing and consistent with the budget outcome, but it is sourced here only through a secondary blog (GovLoop), and the specific committee, report, and year could not be independently confirmed. Treat it as reported rather than as a pinned citation. The underlying cause it describes, failure to agree on centrally-managed requirements, is consistent across the sources.

Timeline

1980s to 1990s: GCCS enters and grows in service as the joint command-and-control system.
March 2006: The DoD Joint Command and Control program is renamed NECC and enters technology development at Milestone A, per Washington Technology (roughly 2006 start corroborated by DISA budget timelines).
FY2007 and FY2008: DOT&E covers NECC in its annual reports, describing three planned increments, service-oriented capability modules, and the Federated Development and Certification Environment.
July 2009: NECC is still an active program, covered by Nextgov, with systems-engineering contracts in place.
Around 2010 (FY2010 to FY2011 cycle): The program is terminated. The DISA FY2011 budget, submitted in early 2010, reflects termination and the realignment of funds to GCCS-J.

The money, kept honest

This is where NECC most needs careful handling, because the tidy version of the story ("hundreds of millions wasted, nothing to show") is exactly the version the primary sources do not cleanly support.

The firmly-sourced dollar figures are contract values, not expenditures:

Up to $172.4 million in potential value. SPAWAR Systems Center Pacific awarded three indefinite-delivery, indefinite-quantity (IDIQ) cost-plus-fixed-fee contracts, reported by Defense Industry Daily with a combined potential value of $172.4 million, for NECC systems-engineering support to DISA. The reported awardees were FGM Inc., Booz Allen Hamilton, and SAIC. This is a ceiling: the maximum potential value of the contract vehicles, not money obligated or spent.
About $60 million competed over five years. The July 2009 Nextgov article described the same three companies competing for NECC task orders valued at roughly $60 million over a five-year period.

Those two figures describe the same systems-engineering support acquisition from different angles and dates. They should not be added together, and neither one is a measure of total program cost.

What about the total? A figure often repeated online is that NECC "spent on the order of $300 million or more" before cancellation. That number could not be confirmed from any primary source in this research: not GAO, not the DoD Inspector General, not DOT&E, not the budget documents. Given the severe acronym collisions noted above, a stray dollar figure attached to the wrong "NECC" is an easy way to manufacture a false fact. So this post does not assert a total-spend figure. It is plausible that a multi-year DISA program with systems-engineering contracts valued in the low hundreds of millions consumed a substantial sum in the aggregate, but that aggregate is unverified here, and it should be treated as an estimate rather than a documented number.

The defensible, cited version of the money story is therefore: a multi-year program, with systems-engineering contracts valued up to about $172 million in potential ceiling, that was cancelled with little fielded and whose funding was rolled back into sustaining the legacy GCCS-J system.

NECC versus GCCS-J, in one box

Because the two are so easily confused, it helps to state them side by side:

NECC (Net-Enabled Command Capability): the DISA modernization program, roughly 2006 to 2010, intended to deliver net-centric, service-oriented command and control. Terminated with little fielded.
GCCS-J (Global Command and Control System-Joint): the legacy system, in service since the 1980s and 1990s, that NECC was meant to modernize. It continued in service and was sustained with the funds realigned from NECC.

The program meant to replace the old system died; the old system it was meant to replace lived on.

The honest critique and the honest defense

The critique. NECC fits a recurring pattern in Defense Department command-and-control and IT modernization: an ambitious, centrally-managed rewrite of a legacy backbone, funded across multiple years with systems-engineering contracts worth up to nine figures in potential value, that was terminated having fielded little. Congress directed the termination after the Services and DoD components could not agree on requirements or accept centrally-managed joint modernization. The money then had to be redirected simply to keep the aging system NECC was supposed to modernize running. The blunt version: a multi-year program consumed time and money while the warfighter kept using the old software.

The defense. The mission behind NECC was legitimate, and it still is. GCCS dated to the 1980s and 1990s, and modernizing joint command and control off aging, stovepiped systems toward shared, service-oriented, web-based capabilities is a real warfighting need, not vanity. NECC's failure was substantially organizational. The Services and components could not agree on common requirements for a centrally-managed system, and that is a governance and acquisition failure rather than proof the goal was misguided. GCCS-J continued in service, sustained with the redirected funds, and the broader move toward web-based, service-oriented command and control that DISA and the Services eventually pursued drew on the lessons NECC surfaced about incremental delivery, governance, and the limits of a single monolithic joint program.

Both verdicts are true at once. The clean way to hold them is this: the need was real, the execution model (one centrally-managed joint rewrite everyone had to agree on) was the thing that broke, and the honest lesson is about governance and acquisition, not about whether command-and-control modernization should be attempted.

Fact-check notes and sources

NECC was a DISA-managed DoD program to modernize joint command and control using net-centric, service-oriented, web-based capabilities, championed by DISA director Lt. Gen. Charles Croom as a "Travelocity/YouTube-like" single interface. Source: Nextgov/FCW, July 2009, corroborated by DOT&E FY2008 annual report (NECC), GlobalSecurity mirror.
NECC's goal was to modernize the aging Global Command and Control System (GCCS), incorporated into the GCCS "family of systems" via an incremental approach rather than a clean-slate swap; GCCS-J continued in service. Source: DISA FY2011 budget estimates, DoD Comptroller (this host now also resolves under comptroller.war.gov following a 2025 domain rebrand).
The DoD Joint Command and Control program was renamed NECC and entered technology development at Milestone A in March 2006. Source: Washington Technology, March 2006 (single trade-press source; roughly 2006 start corroborated by DISA RDT&E budget timelines).
NECC was planned across three increments delivering service-oriented "capability modules," with Increment 1 focused on Joint Force Commander situational awareness and joint operations planning, developed through a Federated Development and Certification Environment (FDCE). Source: DOT&E FY2008 annual report (NECC), GlobalSecurity mirror and DTIC NECC overview, AD1015692.
SPAWAR Systems Center Pacific awarded three IDIQ cost-plus-fixed-fee contracts with a combined potential value of $172.4 million for NECC systems-engineering support (FGM Inc., Booz Allen Hamilton, SAIC). This is a contract ceiling, not money spent. Source: Defense Industry Daily.
The same acquisition was described as roughly $60 million in competed task orders over five years; this is a contract value from a different angle, not a total-spend figure, and should not be added to the $172.4 million ceiling. Source: Nextgov/FCW, July 2009.
NECC was terminated and its funding realigned to sustain the legacy GCCS-J program; DISA budget language attributes a GCCS-J increase to the "realignment of NECC program funding to the GCCS-J program." Source: DISA FY2011 budget estimates, DoD Comptroller.
The cancellation occurred in roughly the FY2010 to FY2011 budget cycle (decision around 2009 to 2010): NECC was still active in July 2009 and shown terminated in the FY2011 DISA budget submitted in early 2010. Source: Nextgov/FCW, July 2009 and the DISA FY2011 budget.
A congressional committee reportedly directed the termination, citing the Services' unwillingness to accept centrally-managed joint command-and-control modernization. The exact quoted language is sourced only through a secondary blog; the specific committee, report, and year could not be independently confirmed, so it is presented as reported. Source: GovLoop.
Unconfirmed claim, flagged: the often-repeated figure that NECC "spent about $300 million or more" before cancellation could not be verified from any GAO, DoD IG, DOT&E, or budget primary source in this research. Only contract ceilings are documented. This post does not assert a total-spend figure. Sourcing note per GovLoop (secondary, unverified for the total).

NECC: the command system meant to modernize GCCS that was cancelled with little fielded