SCMDSO Intelligence Brief — Solicitation 36C10B26Q0376

SCMDSO Intelligence Brief. Solicitation 36C10B26Q0376. Capture Corner is the premium BD intelligence companion to Mission Meets Tech. Public-record sourced. Independent analysis. Not a recommendation, not vendor advocacy, not capture material. Built for federal health BD, capture, and proposal leaders who need analytical depth, not headlines. This issue covers VA's Supply Chain Management DevSecOps and Integration (SCMDSO) opportunity. RFI closed May 11, 2026. Formal RFP expected late Q3 to early Q4 2026.

---

1. Procurement at a glance

Portfolio counts, user estimates, and optional-task scaling figures below are drawn from the draft PWS and associated VA program documentation current as of April-May 2026 and may change in the final solicitation. Contracting officials and the solicitation number are public via SAM.gov.

Field	Detail
Solicitation	36C10B26Q0376
Title	Supply Chain Management DevSecOps and Integration (SCMDSO)
Buying office	VA Technology Acquisition Center (TAC), Eatontown NJ
Contracting Officer	Jason King
Contract Specialist	Michelle Prinston
NAICS	541512 ($34M size standard)
PSC	DA01
Set-aside	Blank on RFI notice. VA explicitly states responses inform set-aside decisions
RFI response	Closed May 11, 2026 (amended from May 8)
Contract structure	Hybrid FFP base + T&M optional tasks + cost-reimbursable travel. 12-month base, four 12-month options. 60 months max
Citing authority	RFAR 15.101(c) (Revolutionary Federal Acquisition Regulation Overhaul)
Scope footprint	63 legacy systems across 174 sites. 34 products in HELM portfolio (12 OIT-funded, 22 VHA-funded). 3-10 additional products expected during PoP
Major discrete implementation inside scope	EAM CMMS rollout, up to 400,000 users, replaces Maximo and AEMS/MERS

---

2. Expected timeline

Based on typical VA TAC cadence for IDIQ-class follow-on awards and the apparent maturity of the draft PWS:

Milestone	Realistic window	Confidence
Industry day or one-on-one announcement	June to August 2026	Moderate
Draft RFP release	August to October 2026	Moderate
Final RFP release	October to December 2026	Moderate
Proposals due	December 2026 to February 2027	Lower
Initial award	Q2 to Q3 2027	Lower
Protest window resolution	Q3 to Q4 2027 if challenged	Conditional
Transition and IOC under new contractor	Q4 2027 to Q1 2028	Conditional

Anchor points. Two facts compress this timeline. First, the incumbent task order is descoping in real time, which limits how long VA can run an open-ended re-baseline. Second, RISE hits FOC in late September 2026, which gives VA a natural cadence reason to have the next contract on contract by mid-2027. If TAC delays beyond this window, expect bridge-contract activity on the incumbent path.

Disruption risks. A protest on the prior award scope, a continuing resolution that delays appropriations, or a RISE implementation event that forces VA to repaper the requirement could each push the timeline right by one to two quarters.

---

3. Vehicle scenario analysis

VA explicitly asked RFI respondents to identify "Existing Contractual Vehicles (GWAC, FSS, or MAC)." That question is a vehicle-strategy probe. Four plausible paths, with different implications.

Scenario A: T4NG2

Probability: Moderate to high. TAC is the natural home for T4NG2 task orders.

Implications. Incumbent base shapes the field. AFS has the strongest position. Other T4NG2 holders with VA OIT presence compete on integration depth, not on vehicle access. Set-aside flexibility is constrained by the T4NG2 base. Award speed is moderate (3-5 months from RFP to award typical).

Watch signal. If VA announces the eventual RFP as a T4NG2 task order, the small-business set-aside is unlikely.

Scenario B: GSA MAS (specifically the 54151S IT Professional Services SIN)

Probability: Moderate. VA OIT has shown increased GSA MAS use in 2025-2026.

Implications. Faster path to award, broader small business access, and the ability to set aside at the SIN level. Concentration risk gets more manageable because the prime field expands. Less VA-specific tailoring of LCATs.

Watch signal. If TAC posts an RFI or sources-sought specifically referencing GSA MAS as the proposed vehicle, this is a deliberate signal to broaden competition.

Scenario C: SEWP VI

Probability: Lower. NASA SEWP is product-led, and this requirement is services-heavy.

Implications. Unlikely to be the prime vehicle, but T&M optional tasks could plausibly land on SEWP if VA segments the buy. More common for hardware-adjacent components (the EAM CMMS implementation could involve some SEWP-eligible scope).

Watch signal. Any segmented buy that splits services from infrastructure components.

Scenario D: Stand-alone IDIQ or task order

Probability: Lower. Time pressure argues against a new IDIQ.

Implications. Maximum VA tailoring of evaluation factors, LCATs, and reporting. Slowest path to award. Highest protest exposure.

Watch signal. Industry day language emphasizing "VA-unique requirements" or PWS authority statements citing VAAR rather than FAR is a tell for stand-alone treatment.

Practitioner reading. T4NG2 is the path of least resistance. GSA MAS is the path of maximum competition. The difference matters for any small business contemplating prime posture. If GSA MAS, prime is realistic. If T4NG2, prime requires major incumbent-class teaming.

---

4. Realistic prime field

Public-record analysis only. No private capture intelligence. Primes likely to compete are those with simultaneous depth in three places: a vehicle that fits the eventual award path, VA OIT past performance at the product-line level, and named integration experience with Oracle Health, CGI Momentum iFAMS, or VistA legacy.

Tier 1 (incumbent and near-incumbent)

Accenture Federal Services. Holds the prior task order via the Cognosante MVH acquisition. Strongest position on transition, deepest knowledge of HELM portfolio, current VALIP relationships. Public USAspending data shows re-baseline pressure that creates evaluation exposure. AFS is also concentrated across EHRM-adjacent work, which is a strength and a concentration risk depending on how VA reads it.

Tier 2 (large primes with VA OIT depth)

Leidos. Strong VA OIT past performance, deep VistA modernization experience, significant EHRM-adjacent capability. Plausible prime under T4NG2 or GSA MAS.

General Dynamics IT (GDIT). Federal health IT scale, VA presence, mature integration practice. T4NG2 path holder.

Booz Allen Hamilton. Federal health analytics depth, less specific to VA logistics but credible on the data and architecture themes.

Peraton. VA OIT presence, supply chain past performance from legacy Perspecta acquisitions.

ManTech. Federal health and integration breadth, T4NG2 path holder.

SAIC. VA presence, integration depth.

Tier 3 (specialized VA health IT primes with realistic prime ambition)

Liberty IT Solutions. Heavy VistA expertise, plausible prime under partial set-aside scenarios.

VetsEZ. Public reporting indicates significant VA health middleware and data management presence. Realistic prime ambition under GSA MAS or T4NG2 second-tier scenarios.

Oracle Health. Already prime on EHRM. Could plausibly capture integration scope, though concentration risk would be the highest of any candidate.

Tier 4 (large SDVOSB/WOSB candidates capable of prime under partial set-aside)

This tier is populated by SDVOSB and WOSB primes with VA OIT past performance and Oracle Health or VistA integration experience. Specific names vary by sub-product line. Capture Corner does not name individual candidates at this tier, but practitioners should expect this tier to be the most active in shaping any partial set-aside lane.

Mentor-protégé and JV signals to watch

When the formal RFP drops, watch SAM.gov and SBA Mentor-Protégé Program records for:

• New AFS-led mentor-protégé filings naming an SDVOSB or 8(a) candidate
• New JVs registered in the 90 days before final RFP, specifically those listing 541512 capability and VA past performance
• Existing JVs that pivot capability statements to lead with Oracle Health, iFAMS, or VistA rather than supply chain

Any of those moves is a vehicle-strategy signal worth tracking.

---

5. People on the evaluation side

Contracting officials are public. Technical evaluation panel composition is not, but PWS authorship and recent leadership transitions usually telegraph who shows up.

Role	Person	Source
Contracting Officer	Jason King	RFI
Contract Specialist	Michelle Prinston	RFI
Under Secretary for Health	John Bartrum	VA leadership directory; cited in RISE update broadcast
Office of Information and Technology leadership	Currently in transition through 2026	Public VA leadership pages should be checked at time of RFP release
HELM Product Line technical leadership	Not publicly named in the RFI	Watch for PWS authorship signals in the final RFP

Practitioner reading. Jason King is the procurement decision authority for the contract action. Michelle Prinston controls the RFI/RFP communication channel. Bartrum is the strategic owner of the operational case for the contract. Building relationships in advance of the final RFP is appropriate only to the extent permitted under FAR 3.104 procurement integrity rules. Outside the RFP window, attendance at public RISE updates and VA OIT industry events is the standard professional engagement.

---

6. Win themes that will actually score

The ten RFI questions tell you what VA wants to test. Three win themes will discriminate.

Win theme 1: Integration architecture as the asset

VA's question structure rewards offerors who frame the contract as integration work first, not staffing work first. The strongest proposals will lead with architecture artifacts (interface specifications, RMF crosswalk, VALIP integration design) and treat Agile capacity as the execution layer that delivers them.

Discriminators. Demonstrated production interfaces with Oracle Health, CGI Momentum iFAMS, VistA, and CDW. Demonstrated DevSecOps pipeline maturity that includes integration testing for cross-platform data flows. Demonstrated ability to manage interface dependencies under active modernization (EHRM and iFAMS in flight simultaneously).

Win theme 2: RISE operating-model alignment

RFI Question 4 (enterprise-wide technical integrations) and Question 5 (incremental legacy replacement roadmap) both reward offerors who can describe a delivery model that maps to headquarters policy, middle-layer standardization, and VISN/facility execution. The 18-to-170 problem is the structural failure this theme has to solve.

Discriminators. Documented past performance supporting policy-to-execution chains in federated agency environments. Demonstrated experience reducing facility-level variation in policy implementation. Documented change management at the VISN scale or equivalent.

Win theme 3: Field adoption and operational outcomes

RFI Question 1 (hiring and onboarding at scale) and Question 6 (tiered training for enterprise rollout) together reward offerors who treat adoption as a measurable outcome, not a contractor activity. The 2024 OIG audit's 18.5 percent noncompliance rate is the anchor.

Discriminators. Past performance with measurable adoption metrics at large user bases. Tiered training programs that scale to 100,000+ users. Self-inspection or audit-readiness support at facility scale.

Themes that look strong but will under-perform

Generic SAFe certification depth. Necessary, not sufficient.

Cloud migration experience without VA-specific platform context. VAEC, VAPO, and the VA security overlay are specific. Generic AWS or Azure migration will be commodity-priced.

Cybersecurity narrative without RMF artifacts at scale. RFI Question 3 will be evaluated on documented compliance with VA security standards, not on the appearance of capability.

---

7. Past performance map

Three lanes will actually score. A fourth lane will be necessary but not differentiating.

Lane 1: Oracle Health (Federal EHR) integration

RFI Question 8 names Oracle Health directly. This is the rarest qualifying lane in the SDVOSB community and one of the most common in Tier 1 primes. Offerors with documented Cerner-to-VistA or Cerner-to-financial-system interface work will score highest.

Acceptable substitutes. DHA MHS GENESIS integration work, Cerner Millennium integration in any large federal context, FHIR API work at the EHR-to-logistics seam.

Lane 2: CGI Momentum iFAMS integration

RFI Question 8 names iFAMS directly. This is the rarest qualifying lane overall. CGI Momentum experience exists primarily in the small set of federal agencies that have deployed it. iFAMS-specific experience is rarer still.

Acceptable substitutes. Other CGI Momentum federal financial system implementations. Federal financial system integration at the order-to-pay layer. Acquisition system integration that touches federal procurement data.

Lane 3: VistA legacy module work

RFI Question 8 names VistA. The IFCAP family, AEMS/MERS, and the EQUIP module are all in scope. EAM CMMS replaces AEMS/MERS, so VistA legacy experience is both a past performance asset and a transition risk indicator.

Acceptable substitutes. Other VistA module modernization. MUMPS to modern architecture migration. Cache and IRIS for Health work at federal scale.

Lane 4 (necessary but not differentiating)

Supply chain or logistics past performance generally. Almost every credible offeror will claim this lane. It earns scoring but does not discriminate.

Past performance combinations that win

The strongest proposals will combine Lane 1 + Lane 3 (Oracle Health and VistA legacy) or Lane 1 + Lane 2 (Oracle Health and iFAMS). The rarest combination, Lane 1 + Lane 2 + Lane 3, is essentially the AFS profile. Building that combination at the prime + sub level is the highest-payoff teaming exercise available on this procurement.

---

8. Gating filter

RFI Question 2. "Software Development Lifecycle Activities... supporting, at a minimum, 15 products concurrently. Include your SAFe Agile Planning Interval (PI) cadence, pre-PI readiness, delivery of PI objectives, and post-PI artifacts required in Section 5.2.3."

This question is calibrated to the actual HELM portfolio (34 products, 12-22 active at any given time). It rewards incumbents and large primes with comparable concurrent-portfolio experience. It will quietly disqualify any small business prime that answers it honestly.

The honest answer for most SDVOSBs in this space is five to seven concurrent products with full SAFe PI artifacts. The threshold is fifteen. That gap is the gating filter, whether VA names it as such or not.

Mitigation paths for SDVOSBs. Three. First, prime under a partial set-aside on a single sub-product line, which lowers the concurrent-product threshold to a manageable number. Second, sub to a Tier 1 or Tier 2 prime that can credibly answer the fifteen-product threshold, contributing depth on Oracle Health, iFAMS, or VistA. Third, decline to bid prime and protect capacity for the next adjacent procurement.

The strategically wrong move. Stretching a five-product portfolio to claim fifteen. Evaluation panels will see through it, and the credibility loss carries into adjacent procurements.

---

9. Price-to-win framing

Public-record-derived only. Not authoritative. Use as a starting point, not a substitute for your own pricing analysis. Confidence is Moderate on the structural inputs and Low on the absolute dollar ranges.

Anchor data points

• Prior task order ceiling (Cognosante MVH, T4NG): approximately $545M over the prior period
• Current PWS structure: 60-month maximum PoP, hybrid FFP base + T&M optional tasks
• Scrum team scaling: Optional Task 1 alone provides for up to 5,100 team-months across Micro/Small/Medium/Large scrum teams. At average four FTE per team-month, that is approximately 1,700 sustained FTE-equivalent at full exercise across the full PoP
• Optional Task 2 (Highly Technical Scrum Team): comparable scaling at higher loaded rate
• Typical loaded rate for VA OIT Senior Engineer, Solution Architect, and DevSecOps labor categories: approximately $165 to $210 per hour, depending on labor mix. Rate bands are inferred from 2024-2025 federal IT services pricing for comparable labor categories, not a published VA rate schedule.

Estimated contract value ranges

Conservative case (40 percent option exercise across optional tasks).

• FFP base year approximately $40M to $60M
• Optional task spend at moderate exercise approximately $180M to $250M per year
• Travel approximately $1.5M to $2.5M per year
• Total approximately $900M to $1.3B over 60 months

Moderate case (60 percent option exercise).

• FFP base year approximately $40M to $60M
• Optional task spend at moderate-high exercise approximately $280M to $380M per year
• Total approximately $1.4B to $2.0B over 60 months

High case (full option exercise plus EAM CMMS major implementation).

• Approaching $2.5B to $3.2B over 60 months

Practitioner reading

The procurement is meaningfully larger than the prior task order. The conservative case is roughly 1.6x to 2.4x the prior ceiling. The moderate case is 2.6x to 3.7x. The high case is 4.6x or more.

Three implications.

1. Pricing strategy must account for the FFP base separately from the T&M optional tasks. Most evaluation panels will scrutinize FFP base year pricing and T&M loaded rates as separate cost realism factors.
2. Concentration risk language in VA's RFI suggests VA is alert to single-prime cost exposure. Expect option-exercise discipline tied to performance metrics.
3. The EAM CMMS implementation is large enough that separating it from the rest of the contract could be defensible as a discrete major implementation. If VA does not separate it, expect the winning prime to subcontract it.

---

10. Protest landscape

Public-record analysis. No nonpublic information.

Prior task order activity

Public GAO docket review shows no published bid protest decisions specifically tied to the prior SCM Product Line task order under Cognosante MVH. That does not mean there were none. It means none reached published decision. Sole-source bridges and re-baseline modifications can attract protest activity that resolves before docket publication.

VA TAC protest pattern

VA TAC awards in the T4NG and T4NG2 family have attracted moderate protest activity over the past five years, typically on past performance evaluation disputes and on technical evaluation factor weighting. Large VA OIT and TAC awards in technically complex lanes routinely attract post-award protest attention, especially where past performance, technical weighting, or incumbent advantage are in play. Most resolved through corrective action or denial.

Protest risk factors specific to SCMDSO

Higher risk if. VA awards on a sole-source bridge with substantial new scope. VA narrows competition to incumbent-favorable evaluation factors. The EAM CMMS implementation is bundled with the sustainment scope without separate cost realism analysis.

Lower risk if. VA structures the award with clear past performance evaluation criteria. VA includes a partial set-aside or carve-out that broadens the competitive field. VA exercises options based on documented adoption metrics.

Protest math for offerors

A protest filed within 10 calendar days of award stays performance for 100 calendar days under FAR 33.104. That is one full quarter of program delay risk. Offerors with weaker positions should map their protest grounds before final proposal submission. Offerors with stronger positions should evaluate protest exposure as a Volume IV pricing input, not as an afterthought.

---

11. RFP signals to watch

When the formal RFP drops, these are the specific signals that will tell you whether VA is treating this as a recompete or as an operating-architecture decision.

• Evaluation factor weights. If integration architecture, RISE alignment, and adoption outcomes carry meaningful weight against technical capacity and price, VA is buying capability. If price and staffing dominate, VA is buying capacity.
• Required proposal artifacts. If offerors must submit integration architecture diagrams, interface specifications, or RMF crosswalk evidence as part of the technical volume, VA is testing for the right thing. If proposal requirements stop at staffing plans and SAFe certifications, VA is not.
• Option-year exercise criteria. If option-year exercise is tied to measurable adoption metrics at named facilities, VA is committing to outcomes. If options auto-exercise on contractor performance reviews alone, VA is not.
• EAM CMMS treatment. If the EAM CMMS implementation is carved out as a separate CLIN or task with its own performance baseline, VA is managing it as the major implementation it is. If it sits buried in the broader sustainment scope, VA is repeating the DMLSS mistake.
• Set-aside posture. If the RFP includes any partial small business set-aside on Prosthetics or another sub-product line, VA has heard the concentration argument. If not, VA has not.

Each of these is a binary signal that will be visible the day the RFP drops. The faster you can read them, the faster you can position your team.

---

12. Risk read

Cognosante MVH was the prior task order recipient. Accenture Federal Services completed acquisition of Cognosante in May 2024. Public USAspending data shows continued execution alongside descopes and deobligations, including a late-2025 modification referencing a federal transparency directive that reduced total value by approximately $19.6M. Public transaction data shows re-baseline pressure. Public data does not prove performance quality. CPARS is not public.

---

13. Concentration watch

AFS now carries portions of EHRM-adjacent work in addition to this product line. Whether VA structures the next award to spread risk across primes or to consolidate further is the acquisition-strategy decision that defines this procurement. The one to track in the trade press for the next 90 days.

If VA awards SCMDSO to a prime already concentrated across EHRM execution, the concentration question becomes the dominant risk factor for the contract. If VA splits, awards to a different prime, or carves out a partial set-aside, the concentration question recedes.

---

14. What to do this week

1. Track Jason King's TAC for industry day or one-on-one announcements. That is where set-aside decisions get shaped on the record.
2. If you are a small business considering a teaming pitch, build it around Oracle Health, iFAMS, or VistA past performance, not generic supply-chain branding. Position the pitch to a Tier 1 or Tier 2 prime, with documented past performance, not capability statements.
3. Read RFI Question 2 honestly and decide your answer now, before the RFP drops. If your honest answer is five to seven concurrent products with full SAFe PI artifacts, your strategy is sub, not prime.
4. Map your teaming options before the final RFP drops. Mentor-protégé and JV moves that happen after the RFP looks suspicious. Moves that are already in place look like strategy.
5. Calendar a check-in for November 2027. The Friday article's prediction is structural and falsifiable. If the RFP rewards integration architecture, expect different downstream consequences than if it rewards capacity. Either way, the evidence will be visible in 18 months. Practitioners who can document which way it went will have a credibility asset for the next adjacent VA procurement.
6. If you are pricing now, treat the FFP base and the T&M optional tasks as separate pricing exercises. Cost realism evaluation will look at them separately.
7. If you are pursuing prime, map your protest exposure on the back of the envelope before final proposal. Protest math is a Volume IV input, not an afterthought.

---

Editorial discipline note

Capture Corner is built to be useful, not provocative. It does not name preferred vendors. It does not recommend awards. It does not characterize incumbent performance beyond what public records support. It does not reveal nonpublic information. It does not advocate for any specific offeror's win.

What it does is read the public record carefully, project realistic competitive scenarios from public data, and surface the practitioner-level decisions that BD and capture leaders actually have to make. Use it accordingly.

---

Next Capture Corner: scheduled for the next major federal health IT opportunity in active capture. Subscribers will receive an alert when the next issue publishes.

Capture Corner is an independent intelligence product. It is not affiliated with VA, with any contractor on this procurement, or with any offeror's bid strategy. Premium subscription includes access to the standing intelligence sidebar plus the searchable archive.