HomeProcurementThe DHS NCCS 2.0 Delay Leaves the Leidos NOSC Bridge Ending December...

The DHS NCCS 2.0 Delay Leaves the Leidos NOSC Bridge Ending December 8, 2026 With No Option Periods Left

The October 5 notice moves a single-award vehicle with a $626 million estimated ceiling, not funded money, to an undated later timeframe. The interim order behind it has no option periods left, so DHS faces a bridge decision first.

What the DHS NCCS 2.0 delay changes, and for whom

The DHS NCCS 2.0 delay moves the decision that matters from the award to the bridge. On October 5, 2026, DHS told industry that the acquisition schedule “will be revised to a later timeframe” and gave no new date. The interim order carrying the work, held by Leidos, has no option periods left after December 8, 2026. For Leidos, retention now runs through a contract action before December 8. For a cleared challenger, the opportunity is intact. The wait, though, keeps the incumbent’s references current while other bidders’ relevant work gets older.

Field Answer
Signal Notice 70RTAC26R00000007 amended October 5, 2026: schedule revised to a later timeframe, no new date, no final solicitation released
BD implication The planned single-award vehicle is delayed; the near-term contract action is a further bridge for the incumbent
Customer DHS Office of the Chief Information Officer, IT Operations, for the headquarters Network Operations and Security Center
Buyer DHS Office of Procurement Operations. Contacts: Nicole Belanger and Michael Lipperini
Funding $27,246,754 obligated on the current interim order. The planned vehicle obligates nothing at award beyond a $10,000 guaranteed minimum
Vehicle / path Planned: a new single-award department-wide IDIQ. Current: task order 70RTAC26FR0000001 on Leidos’s GSA Schedule contract
Incumbents / ecosystem Leidos on core operations through December 8, 2026; Peraton on hosting and security tools, current period through February 28, 2027, options recorded to September 2031
Access strategy Prime or subcontractor on the planned vehicle’s Phase 1 team, each requiring an active Top Secret facility clearance; for uncleared firms, task-order subcontracting after award
Timing Bridge ends December 8; continuing resolution expires December 11; notice archive date December 15
Confidence High
Pursuit posture PURSUE at reduced spend for cleared challengers; DEFEND for Leidos; WATCH for Peraton, DEFEND only if DHS maps its scope onto NCCS 2.0; TEAM for CACI NSS; WATCH for General Dynamics Information Technology
Upgrade triggers A revised schedule or the final solicitation with ceiling and single-award structure intact
Downgrade triggers A successor interim order with a base period running past mid-2027, the notice archiving without a successor, cancellation, or a move to multiple award

The October 5 notice leaves these unchanged.

  • The structure: a single-award, department-wide indefinite delivery/indefinite quantity (IDIQ) contract for network, cloud and cybersecurity operations.
  • The $625,996,046 cumulative task-order ceiling, an estimate the draft solicitation says may change, and not funded money.
  • The attachments: the draft request for proposals, statement of work, pricing template and labor categories, all dated September 2026.

The September analysis of the NCCS 2.0 contract covers the original solicitation design, including the facility-clearance gate and rates-only pricing.

The interim order has used up its option periods

The order that carries the headquarters operations work is 70RTAC26FR0000001, a time-and-materials order to Leidos, signed December 9, 2025. DHS described it at signing as “an interim order for 2-months.” Since then, DHS has stretched it to twelve months.

Date Action Obligated
December 9, 2025 Order signed as a two-month interim $5,000,000 obligation
January 30, 2026 Extended four months $3,788,434 obligation
March 19, 2026 Periods of performance aligned to June 8, 2026 $0 obligation
May 21, 2026 Base-year line items fully funded $5,991,525 obligation
June 4, 2026 Option Period 1 exercised $7,207,542 obligation
September 4, 2026 Option Period 2 exercised $5,259,253 obligation
$27,246,754 obligated on an order DHS labeled a two-month interim, now running twelve months to December 8, 2026, with no further option period recorded.

Task order 70RTAC26FR0000001 carries December 8, 2026 as both its current and its potential end date. No priced option remains to exercise. The order document is unpublished, so whether it carries an extension-of-services clause is not public. Such a clause shows up in the record only once DHS uses it.

So DHS needs a new contract action by December 8. Three paths remain:

  • An extension of 70RTAC26FR0000001, if the order’s terms allow one.
  • A new interim order. The last two interim orders each recorded one offer received under fair-opportunity procedures. The earlier one, 70RTAC25FR0000013, ran on a different Leidos GSA Schedule contract. It followed the original IDIQ’s expiry in September 2024 without a completed recompete.
  • An NCCS 2.0 award before December 8. The original plan put about eight weeks between final solicitation and award. A release this week would leave only days of margin. The October 5 notice moves the schedule later, which makes this path unlikely.

For a capture lead, that bridge action is the next dated signal DHS will send. Read its length as a floor, not a forecast. The current order was labeled two months and ran twelve. An extension-of-services clause, if the order has one, caps at six months whatever DHS expects. A short bridge says little about an early award. A long base period suggests DHS does not expect to award before it ends.

Every month of delay keeps the incumbent’s record current

The delay leaves the opportunity’s size intact and widens a recency gap between the incumbent and everyone else. The draft solicitation ranks demonstrated prior experience and reference checks above staffing approach. The two together rank well above price.

Leidos has performed this work since at least 2021, so a few more months add little to the length of its record. They keep it current. The draft sets no recency window for prior experience. Whether added months change a rating is unsettled. An evaluator is still likely to read current performance on the same requirement as stronger than work that ended months earlier.

A delay that buys a challenger time also keeps the incumbent’s past performance current on the factor the evaluation ranks above staffing.

The delay costs the two sides differently:

  • Leidos keeps billing on the current order through December 8, and on any further bridge DHS awards it.
  • A challenger that staffed a capture team for an October 6 Phase 1 carries that cost with no restart date.
  • A teammate whose last relevant order has ended risks losing ground if the final solicitation adds a recency test.

Challengers gain one thing from the wait. In the draft solicitation’s original timeline, the Phase 2 window ran October 9 to October 21. That gave offerors twelve days to price 194 labor-category lines. A challenger that finishes its rate card now removes that constraint before DHS restarts the clock.

December 8 and December 11 fall three days apart

The bridge’s last day is December 8, 2026. The continuing resolution funding DHS for fiscal year 2027 runs through December 11, 2026, unless full-year appropriations pass first. DHS has not tied the delay to the funding calendar, and I would not assume a connection. The calendar still constrains any December bridge action.

Under the continuing resolution, an ongoing activity is not a new start. So DHS can fund a bridge for existing operations work. Until full-year appropriations pass, DHS would likely fund a bridge signed in early December in increments, within the continuing resolution’s limits. That may give DHS a funding reason to sign a short bridge no matter when it expects to award. It is one more reason not to read a short bridge as an early award.

The next observable events, in order:

  1. A contract action on 70RTAC26FR0000001, or a successor interim order, before December 8, 2026.
  2. The continuing resolution’s expiry on December 11, 2026, and whether full-year funding for DHS follows.
  3. The notice’s archive date of December 15, 2026, which DHS can extend by amending it.
  4. A revised NCCS 2.0 schedule or final solicitation, which can come at any point and has no date.

Competitive Landscape: the same four firms, with a higher cost of waiting

The DHS NCCS 2.0 delay leaves the field as it was on September 17. Four firms have held DHS headquarters operations orders since 2021, and two are performing now.

  1. Leidos holds core operations on 70RTAC26FR0000001 through December 8, 2026, and held the predecessor IDIQ that expired in 2024.
  2. Peraton holds data center managed hosting and security tool support on 70RTAC26FR0000015, a $1,468,330 obligation, with a current period through February 28, 2027 and options recorded through September 29, 2031.
  3. CACI NSS held infrastructure continuing support until June 30, 2026, a $40,619,032 obligation.
  4. General Dynamics Information Technology held tier 1 and tier 2 services at the primary data center until August 2022.

No bidder is publicly named. The May 2026 industry day was closed to press, with no attendee list released. Beyond the four, the pool remains prime-scale and mid-market systems integrators and managed security services providers (MSSPs). The firms in it hold an active Top Secret facility clearance and federal security operations past performance.

Peraton is not exposed to the bridge problem. Its order carries options to 2031, so the delay creates no cliff for it. Its stake is the NCCS 2.0 competition itself. That stake exists only if DHS moves Peraton’s scope onto the new vehicle, and DHS has not said it will.

What to do with the time the delay creates

For a cleared systems integrator or MSSP, NCCS 2.0 is still worth pursuing. The structure, ceiling and evaluation design are unchanged. Spending is the variable. I would cut the capture team to a ready-to-restart state. A reduced core team keeps the rate card, teaming agreements and past-performance write-ups current. I would release proposal writers until DHS sets a date.

  • Cleared challengers: finish the rate card against the draft pricing template now, so a short Phase 2 window does not decide your price.
  • Cleared challengers: confirm each teaming agreement’s exclusivity and term run past a realistic 2027 award.
  • Subcontractors on the Leidos order: confirm your subcontract periods track any bridge DHS awards after December 8, and lock your teaming role for NCCS 2.0.
  • CACI NSS and other recently exited holders: decide on a teaming role while your recent, comparable order is still a current reference.
  • Firms without a Top Secret facility clearance: do not treat the delay as time to qualify; keep your focus on task-order subcontracting after award.
  • Component information and security staff: confirm how your operations that depend on the headquarters center will be covered after December 8.
Capture and BD leads: put December 8, 2026 on your pipeline calendar as the deadline for DHS to act on the bridge. Budget for that bridge’s length as the minimum wait. Restore full capture spend only when DHS posts a revised schedule or the final solicitation.

FAQ

Did DHS cancel NCCS 2.0?

No. DHS revised the schedule to a later timeframe and kept the notice, structure, ceiling and attachments in place. Cancellation would require a separate notice. Until one appears, treat the vehicle as delayed.

Why did DHS delay NCCS 2.0?

DHS has not said. The October 5 amendment gives no reason and no new date. The known facts are timing facts: no final solicitation released, a bridge ending December 8, and a continuing resolution ending December 11.

Is the $626 million ceiling changing?

Not yet. The figure stands at $625,996,046, an estimated ceiling for all task orders. The draft solicitation already says it may change before the final solicitation. It is not funded money. The only committed amount at award is the $10,000 guaranteed minimum.

Who decides how long the next bridge runs?

The DHS Office of Procurement Operations decides, acting for the Office of the Chief Information Officer, which owns the operations requirement. The bridge’s length is the first dated sign of DHS’s timing. Read it as a rough floor rather than a forecast. An extension-of-services clause caps at six months, and continuing-resolution funding favors short actions.

Does the delay help a firm without a Top Secret facility clearance?

Not on the prime competition. Phase 1 still requires an active Top Secret facility clearance for the prime and every subcontractor. The clearance needs a sponsor tied to a classified requirement. The realistic route remains task-order subcontracting after award.

What would make me rethink the pursuit posture?

A successor interim order with a base period running past mid-2027 would mean budgeting for a 2027 award at the earliest. A switch to multiple award would change the access strategy from one winner to a pool. The notice archiving on December 15 without a successor would suggest DHS is reworking the requirement. That would call for a fresh bid decision.

The Contract Opportunity Atlas

Two issues a week.. Free.

Two issues a week. Data-driven intelligence for small tech firms selling to the federal government. Free.

Subscribe to Contract Opportunity Atlas

Get federal technology, AI, procurement, and GovCon insights delivered to your inbox.

Shahid Shah
Shahid Shah
Shahid specializes in bringing world-class CTO, CISO, and EiR expertise to startups, business units and companies on a part-time (fractional) basis. With a rich background in regulated, safety-critical industries like Med Devices, Digital Health, and Gov 2.0, he possess a unique understanding of complex, high-demand products and services. He is a C-suite native that can easily blend in with technical and engineering teams that need to deliver revenue-generating solutions to the marketplace. He has served as an Entrepreneur in Residence when a market seems lucrative but it's unclear how to build and launch products and services for such opportunities. Shahid has years of leadership experience as a co-founding startup CTO for multiple venture-backed companies, business unit CTO and EiR, and public company CTO helping transform product teams from marginal to high performance. His software/hardware engineering and cybersecurity body of knowledge is up to date because he rolls up his sleeves to create code when appropriate & dive into system architecture and design when required. He also conduct technology due diligence exercises for corporate acquisition or product integration requirements.
RELATED ARTICLES

Most Popular

CATEGORIES