Scout

RFI_MBMTRS_FA2330_Phase3

Request for Information Multi-Band Multifunction Tactical Radar System (MB-MTRS)

DEPT OF DEFENSE > DEPT OF THE AIR FORCE > AIR FORCE MATERIEL COMMAND > AIR FORCE LIFE CYCLE MANAGEMENT CENTER > ELECTRONIC SYSTEMS > FA2330 ARSPC MGNT SYSTMS AFLCMC/HBA

New
Actions
Open SAM.gov
Notice Type Sources Sought
Due 2026-04-29
Posted 2026-04-13
NAICS 334511
PSC 5895
Set-aside No Set aside used
Scout Score 45

Quick analysis

AFLCMC/ESA issued an RFI (not a solicitation) seeking industry input on a Multi-Band/Multifunction Tactical Radar System (MB-MTRS) supporting ATC, BMC2, UAS, and weather missions, with stringent transport, environmental, and R&M requirements.

Trace’s core strengths (ABMS/JADC2 integration, SE&I, edge compute/M-DRIVE, SATCOM transport, OCC operations, OCONUS deployment) align with integration and enabling-technology aspects, but Trace is not a radar OEM and lacks evident radar hardware/manufacturing past performance.

Given the RFI’s openness to partial/enabling solutions and its explicit ABMS alignment, this is strategically useful for shaping interfaces and teaming with radar OEMs. Monitor to engage, provide an enabling-technology response, and pursue teaming. The technical fit to the primary radar hardware is weak, so we should not posture as a prime radar provider.

Scope summary

  • Provide complete or partial/enabling solutions for a deployable multifunction tactical radar supporting ATC, BMC2, UAS (Groups 1–3), and weather sensing (NEXRAD Level II products).
  • Solutions actionable within FY2027 and ability to deliver initial pre-production units within 29 months after award.
  • COTS preferred; provide TRL/MRL substantiation, development needs, risks, and mitigations.
  • Transportability: two C-130J-30 aircraft (≤10 463L pallets, total transport weight ≤34,000 lbs incl. 1,400 lbs personnel/gear), LMSR RO/RO, CH-47 sling load, rail, ship; withstand rapid decompression, SAE AS8090 Type IV mobility, rail impact, vibration/shock; single apex lift.
  • Setup ≤4 hours with four technicians; power at 50/60 Hz, 100–130 VAC and 200–260 VAC.
  • Environmental ops: -54°C to +71°C; 5–100% RH; salt, fungus, blowing sand/dust; rain/snow/ice; up to 13,100 ft altitude; 50 mph winds with 71 mph gusts.
  • R&M targets: MTTR ≤30 minutes, MaxTTR ≤1.5 hours, MTBCF ≥3,000 hours.
  • Open architecture and data/interface compliance; provide data products, formats, ICDs; support integration to C2/ABMS.
  • Provide ROM cost/schedule using attachment table (not available in extract).

Dimension scores

Total - 45/100
Technical Fit - 6/20

The RFI centers on delivering a deployable multifunction tactical radar (AESA, radar signal processing, weather products). Trace’s core capabilities are SATCOM/multi-orbit transport, JADC2/ABMS integration, CDS, edge compute (M-DRIVE), SE&I, OCC, and OCONUS FSRs (company_profile). These align with integration and C2/ABMS interface aspects the RFI requests, but Trace lacks stated radar hardware design/manufacturing capability. Partial/enabling-role fit, not a primary radar provider.

Past Performance - 11/20

Relevant USAF/ABMS ecosystem past performance (ABMS IDIQ active; USAF/USAFCENT comms and IT; company_profile) and JADC2/C2 integration experience align with the RFI’s ABMS and BMC2 context. However, there is no explicit radar hardware past performance; thus, strength is agency/mission-adjacent rather than sensor build.

Vehicles / Contract Access - 6/10

This is an open RFI (market research), not competed on a restricted vehicle. No specific vehicle access required. While Trace holds ABMS IDIQ and other vehicles (company_profile), they are not cited as the access path for this RFI.

Competitive Position - 3/15

OTA Phases I–II underway per RFI, suggesting existing performers. Trace is not identified as an OTA performer and lacks radar OEM credentials, making us an underdog for primary sensor provision. We may compete for enabling/integration roles but face strong radar OEM competition.

Risk - 6/15

If postured as a radar provider, risk is high (hardware development, extreme environmental/transport specs, PPU in 29 months). As an enabling/integration respondent, risk moderates but still includes dependency on teaming and evolving OTA pathway. RFI stage reduces immediate contractual risk but indicates a demanding program.

Strategic Value - 6/10

Directly tied to ABMS theater sensing grid and AFLCMC/ESA. Engagement could shape open-architecture interfaces and position Trace for ABMS/JADC2 integration, CDS, and edge compute roles with OEM partners. Potential to expand USAF relationship and pipeline, though not a prime hardware lane.

Compliance - 7/10

Set-aside: None; NAICS 334511 is among Trace’s primary codes (company_profile). No disqualifying certifications cited. However, to meet manufacturing/delivery expectations we would require teaming for radar hardware—manageable at RFI stage but a future compliance/capability gap without partners.

Concerns

  • Program is in an OTA construct with Phases I–II underway; current performers may have an incumbency advantage moving into later phases.
  • Significant hardware development/manufacturing complexity and environmental/transport constraints may exceed Trace’s in-house capabilities without strong OEM teaming.
  • Aggressive schedule for delivering PPUs (29 months) with stringent performance could drive cost/schedule risk.
  • Partial document review: detailed performance tables and ROM template not available, increasing uncertainty about exact thresholds/objectives.

Teaming opportunities

  • Radar OEM partner with AESA panels/T-R modules, radar signal processing, and weather processing expertise.
  • Manufacturing partner able to meet C-130J-30 pallet/weight constraints and environmental/transport qualifications; TRL/MRL maturity with test evidence.
  • Open-architecture radar middleware/interfaces and ICD ownership for integration to C2/ABMS.
  • FAA/ICAO/EUROCONTROL ATC surveillance performance understanding and verification experience.
  • Test and evaluation partners/facilities for environmental, vibration/shock, and transport qualification.

Competitive position

  • Position Trace as the ABMS/JADC2 integration and data-interface lead leveraging ABMS IDIQ experience and C2ISR integration track record (company_profile).
  • Offer M-DRIVE/edge compute as the on-platform processing environment supporting multi-mission radar workloads and data distribution to ABMS/command nodes.
  • Leverage NSA TI/CDS expertise to enable multi-domain data sharing from radar outputs into classified/coalition environments (MPE/BICES-X pedigree).
  • Provide global deployment, field support, and sustainment via OCONUS FSR footprint and OCC 24/7 operations for reliability and managed services.
  • Integrate multi-orbit SATCOM transport to extend sensor data reach and resilience in contested environments.

Bid/No bid factors

  • RFI only; no guaranteed procurement and unclear down-select path from OTA to production.
  • Ongoing OTA phases may bias toward existing performers not identified in available materials.
  • Trace lacks organic radar hardware capability; without an OEM partner, we cannot meet core system requirements.
  • Detailed key performance requirement tables and ROM template were not included in the reviewed sections, limiting precise alignment.

Documents

Download all
MTRS RFI 3.pdf Download

Partially reviewed: Too large

Summary

Partially reviewed RFI (selected sections only) from AFLCMC/ESA (dated 8 Apr 2026) requesting industry input for a Multifunction Tactical Radar System (MTRS). Selected sections describe program background, four mission areas (ATC, BMC2, UAS, Weather), program timeline context (OTA Phase I complete Feb 2025; Phase II through FY Q4 2026), COTS preference but possible development, manufacturing/delivery expectations, and detailed transport, environmental, setup, power, and reliability requirements. Review was limited to provided sections 1 and 3 of 5 due to file size; other technical sections were not included in the extract.

  • Issuing office: AFLCMC Electronic Systems Directorate, Aerospace Management Systems Division (ESA), Air Traffic Systems Branch (ESAA) — Hanscom AFB
  • Document type: Request for Information (RFI) — explicitly not a solicitation; market research
  • Date: 8 April 2026; references OTA Phase I award 23 Feb 2024 (completed Feb 2025) and Phase II planned through FY Q4 2026
  • MTRS missions: ATC surveillance, Battle Management Command & Control (BMC2), UAS surveillance (Group 1–3), Weather sensing (NEXRAD Level II products)
  • Delivery/manufacturing expectations: solutions actionable within next year (FY2027) and ability to manufacture/deliver initial pre-production units (PPUs) in 29 months after award
  • Government preference for COTS solutions but accepts some development may be required; requests TRL and MRL substantiation
  • Transport constraints: must be transportable by C-130J-30 (≤10 463L pallet positions across at most two aircraft — 7 in first, 3 in second), LMSR RO/RO, helicopter sling load (CH-47), rail, ship; total transport weight ≤34,000 lbs including 4 personnel/1,400 lbs
  • Transport survivability: rapid decompression (8,000 ft to 45,900 ft in <15s), Type IV road mobility per SAE AS8090, rail impact, single apex lift, helicopter sling load, vibration/shock tolerance
  • Setup and sustainment: emplace/setup time ≤4 hours with four technicians; power compatibility 50/60 Hz, 100–130 VAC and 200–260 VAC; environmental operability -54°C to +71°C, 5–100% humidity, sea level to 13,100 ft, salt/fungus/blowing sand, 50 mph winds w/71 mph gusts
  • Reliability/maintainability targets: MTTR ≤30 minutes; MaxTTR ≤1.5 hours; MTBCF ≥3,000 hours
  • RFI requests technical details from vendors: existing systems/subcomponents (AESA panels, T/R modules, resource manager), modifications needed, TRL/MRL, development risks/mitigations, throughput/target capacity, min/max detectable velocities, clutter processing, pictures/illustrations
  • Government asked vendors to identify representative components within five working days to arrange follow-up discussions
Technical details

Entry: sync

Review status: Up to date

Logical upstream opportunity: 30528

Notice lineage:

  • bd5ef9d0d00647ef9cd6d66a33344480 (posted 2026-04-13) - current

Last synced: 2026-04-21T15:20:34.674773+00:00

Last analyzed: 2026-04-21T15:25:02.135333+00:00

Latest package fingerprint: 1c246b6dcdefd32e4c5e8a8a0eee7c16d33799b77d3263533a74d1ec09dce8de

Latest package notice: bd5ef9d0d00647ef9cd6d66a33344480

Latest package documents: 1

Evidence limitations
  • MTRS RFI 3.pdf: partially reviewed (too large)
Recent package history
  • 2026-04-21T15:20:34.677098+00:00: bd5ef9d0d00647ef9cd6d66a33344480 with 1 docs

Labels

Human notes

Qualification Settings

Included notice types

Scope Filters

Use one code or phrase per line, or comma-separate.

System Settings

Runtime

Custom Search

Search time

These filters apply only to this run. Qualification settings stay unchanged.

Custom Search queries Fetchmesh and stores the results in Scout without mutating the default sync configuration.

Workspace visibility

All custom searches are public for now.

Included notice types

Scope Filters

Use one code or phrase per line, or comma-separate.

Browse Searches