About this file

This file is a Questions and Answers (Q&A) document addressing 51 vendor inquiries regarding a Commercial Solution Opening (CSO) Call for Solutions for a Commercial Digital Intermediate Frequency Subsystem (DIFS). The government clarifies technical requirements, pricing structures, evaluation criteria, and contracting approach for this Army initiative under solicitation W15P7T-27-R-DIGIF, issued by Army Contracting Command - Aberdeen Proving Ground (ACC-APG) for Product Manager Wideband Enterprise Satellite Systems (PdM WESS). Key responses address that the DIFS baseline must support up to 3 antennas and 64 FDMA modems per site with pricing granular enough to allow cost estimation for varying configurations; the First Article Testing (FAT) completion target is 2QFY28 (not within FY2027); partial software-only solutions may be awarded as Other Transaction Authority (OTA) agreements; the Automated Management and Control Function must be vendor-neutral to prevent vendor lock-in; deterministic port-based multicast routing is required in the switch fabric; operator entry is acceptable for satellite access parameter authorization in Increment 1; and a standardized 3-terminal reference configuration should be used for notional site pricing. Additional clarifications specify that DIFS will integrate with existing Government Management and Control systems with interface specifications provided, the system must comply with MIL-STD-461H for electromagnetic interference, RMF artifacts must follow NIST SP 800-53 Moderate-Moderate-Moderate controls, an established installation partner is mandatory for global deployments across up to 20 worldwide teleport sites, and the complete schedule timeline covering First Article milestones through production option fielding is required. The government indicates that Phase 2 demonstration details (timing, location, advance notice, test plans, success criteria, government-furnished equipment, and public internet connectivity) will be provided if vendors advance to Phase 2, and similarly for Phase 3 information regarding contract type (CPFF versus FFP), small business set-aside considerations, and commercial documentation acceptance.

View the file

Other files

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Q & As

Question #Page # or Section ReferenceQuestionGovernment Answer
1CSO Section 3.1, pg 6Sec. 3.1 states: "Times New Roman - not smaller than 12-point font type, although smaller font types may be used for figures, tables, and charts." Please specify the minimum font size for tables and please specify if any font size is acceptable for figures and charts.10-point for tables, figures, and charts.
2CSO Section 2.4, pg 5Sentence fragment "The Government's objective is to verify a c, followed...". What was intended language for "to verify a c, …"?Please see revised Call for Solutions.
3CSO Section 1.1 pg 2

CSO Section 2.3 pg 4 CSO Section 3.1.4 pg 6/7 Increment 1 appears to only focus on the baseline First Article, but Section 2.3 discusses optional production units and Section 3.1.4 Pricing Structure (an other text) indicate pricing is potentially desired for optional production units up to 20 worldwide teleport sites. Please clarify the bounds of the ROM pricing / articles to be priced. ROM should account for HW and SW supporting up to 3 antennas, 64 FDMA modems, site integration, and sustainment support. ROM should be granular enough to allow the government to establish the estimated costs for sites with fewer antennas and modems.

41.1, pg 2CSO states "Increment 1 will establish a fully operational baseline designed to support subsequent capability upgrades and integrations in future fiscal years." Assuming a Q2 FY2027 award, does this imply that the baseline must be fully operational in FY2027 (i.e. by October 1, 2027)?No. The Government does not require the Increment 1 baseline to be fully operational within Fiscal Year 2027 (i.e., by October 1, 2027). While the contract award is targeted for the first quarter of 2027 (Section 4.2), the milestone schedule spans into the following fiscal year. Specifically, the Government has established a target date for the completion of First Article Testing (FAT) & Verification in the second quarter of Fiscal Year 2028 (2QFY28).
5Section 3.1, Step 1 (partial solutions)Section 3.1 states that partial solutions may be awarded an Other Transaction or retained in the library. Will the Government evaluate a Solution Brief that addresses Objective 4 (Automated Management and Control) and the management and monitoring portions of Objectives 5, 6 and 7 from a software vendor whose suite integrates with the conversion, signal-processing and switch-fabric elements of a separately selected or teamed hardware vendor?Yes. The Government will evaluate Solution Briefs that propose high-value partial solutions (such as a software-only suite addressing Objective 4 and the management/monitoring portions of Objectives 5, 6, and 7).

Refer to Section 4.1 (Contract Vehicles): As outlined in Section 4.1 (Anticipated Type of Awards), while the Government intends to award one FAR Part 12 commercial contract for a complete, fully integrated solution, the Government may also award Other Transaction Authority (OTA) agreements as a result of vendor submissions.

Awards for Partial Solutions: As specified in Section 3.1, at the Government's discretion, a partial or software-only solution may be selected and awarded an Other Transaction (OT) to mature, or it may be retained in the library for future teaming opportunities.

Encouraging Integration and Teaming: The Government strongly encourages software vendors proposing partial solutions to describe how their software suite can integrate via open-standard interfaces and APIs with standard DIFI-compliant hardware (such as third-party converters and switches) as part of their Step 1 Solution Brief (Section 3.1). The government prefers software vendors with partial solutions to consider teaming arrangements for a comprehensive solution.

6Section 2.2, Objectives 1, 4 and 7Does the Government intend the Automated Management and Control Function to be a vendor-neutral software layer able to manage DIFS elements from more than one manufacturer, consistent with the Objective 1 goal of preventing vendor lock-in and the Objective 7 question on selecting a different contractor for future support, or does it expect each hardware vendor's native management suite?The Government intends the Automated Management and Control Function to be a vendor-neutral software layer able to manage DIFS elements from more than one manufacturer. In alignment with Open Systems (Objective 1) focusing on preventing vendor lock-in, the software-based management suite (Objective 4) must not be restricted to a single hardware manufacturer's proprietary ecosystem while providing flexibility in Future Lifecycle Support (Objective 7).
7Section 3.1, Step 1May a company participate in more than one Solution Brief, as the prime for one and as a team member on others?Yes, but each team can only submit one solution brief.
8Section 2.2, Objective 4Regarding "satellite access parameters": does the Government expect the management suite to ingest satellite access authorizations in machine-readable form, and if so from which system or format (for example SAA, SAR or GAA documents from the WSOC or RSSC, or an existing planning tool), or is operator entry from the authorization acceptable for Increment 1?Operator entry is acceptable for the Increment 1 baseline.
9Section 2.2, Objective 4Regarding "automated rerouting of critical traffic to alternate facilities": does this mean rerouting Digital IF streams between teleports over the WAN or GAIT, rerouting to alternate equipment within a teleport, or both? What inter-site transport and bandwidth should offerors assume for Digital IF between facilities in Increment 1?Both. Under Objective 4, the Automated Management and Control Function is expected to manage: 1) Intra-site rerouting: Rerouting to alternate, redundant equipment within a single teleport (Automatic Protection Switching); 2) Inter-site rerouting: Rerouting Digital IF streams between different teleport facilities over the Wide Area Network (WAN) or GAIT links.
10Section 2.2, Objective 4Is the DIFS management suite expected to integrate with existing Government management systems at the teleports or at PdM WESS, such as the Hosted Management and Control (HM&C) software fielded at Fort Belvoir in 2026, the EDIM Modem Management System, or a site network management system, and if so will their interface specifications be provided?1) Yes with Government Management & Control System. 2) Yes, interface control documents will be provided for integration. Additionally, the DIFS management suite should be implemented in a virtual environment.
11Section 2.2, Objective 4The December 2025 Sources Sought for a Digital IF System (W15P7T26RDIGIF) described a documented northbound API for mission download, acceptance or rejection, status and updates, and mission failure detection with reassignment to alternate SATCOM facilities over the WAN. Do those requirements carry into Objective 4 of this Call, and will the Government specify the northbound interface or accept the offeror's documented API?No, the Objective 4 are only required for this Call for Solutions. The Government will accept the offeror's documented API.
12Section 2.2, Objective 7Will the DIFS be authorized as a standalone system or inherit controls within the host teleport's authorization boundary? Is a container-based management suite on hardened Linux (DISA STIGs, signed images) acceptable, and does the Government expect Iron Bank or Platform One provenance for software components?DIFS will need to provide its own cybersecurity hardening and will inherit some controls from HM&C. Yes, STIGs and secure images are acceptable and should be provided in a way that enables transition to government sustainment. Solution should not be proprietary.
13Section 3.1, Pricing StructureFor a software element licensed per site or by annual subscription rather than per unit, how should the single-unit price and the range-based quantity discounts (1-10, 11-50, 51+) be presented?Vendor discretion but the government desires minimal recurring licensing.
14Spec A3425425 §§3.1.2.2, 3.1.3, 3.2.2.1, 3.7.2 and 3.7.3; Figures 3-1 and 3-4.May one commercial chassis implement multiple CD and IFC functions, provided the contractor demonstrates the specified interfaces, capacity, redundancy and maintainability? For the antenna-side configuration in §3.2.2.1(b), must CD processing remain in the equipment building, or may an integrated CD/IFC chassis reside in the antenna enclosure?Yes. However, all equipment must reside inside the equipment building (shelter).
15Spec A3425425 §3.1.2.3.6 and its subparagraphs; §§3.2.2.1 and 3.2.2.2.For a DIFS distributed across multiple racks, may each rack have its own redundant pair of 120 VAC mission-power inputs, with no individual input exceeding 15 A and either feed able to support that rack's full mission load? Or does the Government intend one redundant input pair for the complete site DIFS? Please identify any site-wide power limit offerors should use for sizing.Each individual rack should support two (2) separate power feeds connected to a single automated transfer switch (ATS) residing within that rack.
16Spec A3425425 §§2.2 and 3.1.2.1.1.In addition to the specified Information Class 0 and the revision current at RFP release, must DIFS interoperate with modems using earlier DIFI revisions, such as v1.1 or v1.2.1?Support Information Class 0 at the current DIFI revision. If accepted into Phase 2, additional information will be provided at that time, e.g. appropriate packet-field-level DIFI overlay requirements.
17CfS §2.2, Objective 3; Spec A3425425 §§3.1.2.1.3, 3.7.1 and 3.7.6.3.Is IGMP-based multicast sufficient to meet Technical Objective 3, or must the fabric also support deterministic forwarding based on the ingress port, configured by DMASS independently of multicast-group membership? Please clarify the required behavior where the CfS and draft specification differ.For the DIFI backbone, Incoming/Ingress Port-Based Multicast is Required: No, standard IGMP-based multicast alone is not sufficient to meet Objective 3.

Deterministic Behavior is Mandatory: In accordance with Objective 3, the switch fabric must support deterministic multicast routing based on the incoming (ingress) port without requiring strict, traditional multicast tables. This forwarding capability must be capable of rapid reconfiguration by the Automated Management and Control Function (Objective 4) without utilizing Layer 3 routing protocols.

Demonstrating Capability in Solution Brief: In their Step 1 Solution Brief (Section 3.1, Item 1), offerors must describe how their proposed switch fabric architecture implements this deterministic, port-based packet forwarding behavior, and how it interfaces with the management software suite.

The exact protocol definitions, API structures, and software integration interfaces for configuring this forwarding behavior will be collaboratively reviewed and finalized during Step 3 discussions (Section 3.4).

18 CfS Section 1; Spec A3425425 Figure 3-3 note; §§3.7.2 and 3.7.3. Without identifying site locations, can the Government provide the expected mix of MET and RHN sites, terminal and L-band aggregate counts, legacy-LBSS interfaces, and all-rack versus antenna-side configurations for the planned fielding? If those quantities are not available, which reference configuration should offerors use for the notional site price? No. The Government will not provide the specific mix of MET/RHN sites, terminal-specific counts, or spatial rack/antenna-side configurations at this stage.

Use 3-Terminal Site as Reference Baseline: To establish an "apples-to-apples" comparison for Rough Order of Magnitude (ROM) cost evaluations, offerors must use a standardized 3-terminal (antenna/pedestal) site as their reference configuration for notional site pricing.

19 CfS §2.2, Objective 8; Spec A3425425 §§2.1 and 3.3.2.2.3; Figure 3-5. Which MIL-STD-461 revision governs DIFS qualification and FAT: the CfS's revision G or the draft specification's revision H? Please also confirm whether the “Terminal RE Limit” curve in Figure 3-5 defines the tailored RE102 limit for the integrated DIFS rack. Under Objective 8 (Military Compliance and Certification Readiness) of the Call for Solutions (CfS), MIL-STD-461H is the governing revision for electromagnetic interference compliance and First Article Testing (FAT).

Tailoring and RE102 Limits: The specific "Terminal RE Limit" curve and tailored RE102 emission limits referenced from the separate draft Technical Specification are currently undergoing government review.

The finalized EMI/EMC testing requirements, tailored emission limit curves (such as RE102), and specific test methods will be collaboratively reviewed, refined, and finalized with the selected vendor during Step 3 discussions (Section 3.4).

20 Spec A3425425 §3.2.1.4; CfS §2.2, Objective 7, and §2.3, Deliverables. Will the Government authorize DIFS within an existing site or EWSTS RMF boundary, or as a separate boundary? Please identify the expected contractor scope for the initial RMF package, integration with inherited controls, and authorization maintenance after fielding. RMF Boundary & Authorization: The Commercial Digital Intermediate Frequency Subsystem (DIFS) will likely be authorized as a part of a larger, overarching Wideband Enterprise Satellite Systems (WESS) authorization boundary, rather than as a standalone or separate site boundary.

Contractor RMF Package Scope: Fulfillment of this contract will require the contractor to develop and deliver RMF artifacts utilizing the latest revision of the NIST SP 800-53 security controls for a Moderate-Moderate-Moderate (M/M/M) system (as required under Objective 7).

Applicability and Exclusions: 1) Approximately one-third (1/3) of the standard controls will be classified as Not Applicable (N/A) due to the system containing no Personally Identifiable Information (PII); 2) The contractor can plan for control inheritance from Host Management & Control (HM&C); 3) The contractor's scope excludes RMF controls that can only be completed by the operational command (e.g., operational physical security, site-specific guard forces, and operational personnel vetting).

Deliverables Supporting Local Integration: The contractor remains responsible for delivering the modular RMF artifacts (as required under Section 2.3 Deliverables) to support the integration of these inherited controls and to allow the local commands to seamlessly maintain the authorization after fielding.

21Spec A3425425 Appendix B and §4.2.1.Appendix B refers to a separate Verification Cross Reference Matrix spreadsheet. Can the Government provide that matrix for offerors to establish qualification scope, schedule and cost?Yes, the Government will provide an updated specification and a Verification Cross Reference Matrix (VCRM) after the Government completion of the Solutions Brief review.
22CfS §2.5, Program Schedule and Milestones; Section 3, Other Relevant Information.Does the Government have a target or maximum duration from award to First Article delivery or completion of FAT that offerors should use in their proposed Period of Performance?The Government has established a target timeframe for the completion of First Article Testing (FAT) & Verification in 2QFY28.
23Spec §3.2.1.1 Transmit PerformanceKindly clarify the maximum Tx output power and total control range?Analog input level range is specified in paragraph 3.1.2.3.2.1: +10 to -50 dBm. Analog output 1 dB compression point is specified in paragraph 3.1.2.3.2.2: 0 dBm.

IFC analog gain adjustment is specified in paragraph 3.7.3: "Each IFC analog input and analog output shall provide an analog gain stage adjustable over a range of no less than -15 dB to +15 dB for alignment with external equipment. The analog gains shall be adjustable via the DMASS in no less than 0.5 dB steps.

24Spec §3.2.1.1.2.9 Transmit Spurious OutputsThe spurious relaxation region of 2-4GHz corresponds to an IF range of 1-2GHz for Ka-Band in MIL-STD-188-164C. If we extend the IF range to 950MHz-2.05GHz, the 2nd harmonics falling in the 1.9-2GHz region will not have the necessary spurious relaxation. Can the -45dBc exception be extended over the 1.9-2GHz range to cover this?The MIL-STD-188-164 requirement is actually applied to the 31 to 33 GHz. When the 1 GHz wide L-Band IF is tuned to the range 0.950 GHz - 1.950 MHz (which will ultimately be upconverted to 30 - 31 GHz), the L-Band exclusion region will be 1.950 GHz to 3.950 GHz. Specification paragraph 3.2.1.1.2.9 will be updated to accommodate the tunable L-Band IF input frequency range.
253.1.2.3.2.1 Aggregate Analog Modem L-Band Inputs
3.1.2.3.2.2 Aggregate Analog Modem L-Band OutputsWhy has the IF VSWR requirement been tightened from 2.0:1 to 1.5:1? Achieving 1.5:1 across the operating bandwidth will require additional design tradeoffs and may reduce overall RF performanceThe DIFS VSWR requirement will be revised to 2.0:1 to be consistent with MIL-STD-188-164C CN2.
263.2.1.1.2.10 Transmit EVMWhat operating conditions are intended for the EVM test cases (e.g., input/output power levels, bandwidths, carrier counts)?EVM test requirements will be added to specification paragraph 4.3.2.1.1.2.10. Intended operating conditions include:

- multiple carriers varying in power spectral density (PSD) by up to 30 dB

- largest carriers positioned to risk intermod generation onto smallest carriers

- generally 16-APSK modulation, with potentially lower modulation orders on the lowest PSD carriers subject o risk of intermod generation by the higher PSD carriers

- max total power up to 0 dBm

- EVM requirements applicable to all such carriers

27Section 3.3 – Step 2: Pitch Session / Vendor Technical Demonstration (PS/VTD); Section 2 – Program Schedule and MilestonesDemo Schedule: When and where is the demonstration expected to take place?If accepted into Phase 2, additional information will be provided at that time.
28Section 3.3 – Step 2: PS/VTDAdvance Notice: How much advance notice will vendors receive to prepare, configure, test, and ship their equipment to the demonstration location?If accepted into Phase 2, additional information will be provided at that time.
29Section 3.3 – Step 2: PS/VTDTest Plan: When will the Army provide a detailed test plan outlining the technical requirements and functionality to be demonstrated?If accepted into Phase 2, additional information will be provided at that time.
30Section 3.2 – Submission/Evaluation Criteria; Section 3.3 – Step 2: PS/VTDSuccess Criteria: What specific evaluation and acceptance criteria will be used to determine whether a demonstration is successful?If accepted into Phase 2, additional information will be provided at that time.
31Section 2.2 – Objective 9: Global Integration and Installation Support; Section 3.1 – Global Integration and Installation ApproachInstallation Partner: How important is it to have an established installation partner to support deployments across all 20 worldwide locations? Is this a mandatory requirement or a preferred qualification?Both yes, it is a mandatory requirement to have an established installation partner.
32Section 2.2 - Objective 4: Automated Management and Control (Empowered):Please clarify your intended meaning with the term "satellite access parameters"Satellite access parameters define the establishment and termination of satellite communications paths.
33GeneralPlease state if any eligibility issues are foreseen with offered solution products that originate in non-US countries, i.e. Great Britain and CroatiaIn traditional federal contracting, the Buy American Act restricts the procurement of foreign-end products unless an exception applies. OTAs are entirely exempt from the Buy American Act. While foreign product origins are not a disqualifier, the awardee must still satisfy standard prototype OTA statutory requirements. The vendors shall ensure the proposed products satisfy the RMF & Supply Chain Risk Management (SCRM) requirements. Please note that under Objective 7 (Secure and Compliant Architecture), all hardware and software (regardless of origin) must satisfy the RMF baseline controls. This includes compliance with Supply Chain Risk Management (SCRM) standards (such as NIST SP 800-161), and the prohibition of covered telecommunications/video surveillance equipment (FAR 52.204-25) or software/hardware from prohibited entities. Offerors must clearly declare the country-of-origin for all proposed hardware components and software licenses in their Step 1 Solution Brief (Section 3.1, Item 3: Supply Chain Risk Management). Contractors must establish written procedures to vet suppliers and subcontractors for financial risks, Foreign Ownership, Control, or Influence (FOCI), and manufacturing vulnerabilities, and IT systems must adhere to DoD CIO ICT Supply Chain Risk Management (SCRM) 12-category guidelines, NIST SP 800-53r5/800-161 controls, NIAP/CCTL security profiles, and must be configured in accordance with official DoD Security Technical Implementation Guides (STIGs)
34Page 7,#5. Global Integration and Installation ApproachIt is stated up to 20 globally dispersed sites may be required for integration, install, and checkout. Since there may be a varying number of multiple ground terminal antenna per site, would it be acceptable to provide digital IF subsystem ROM pricing structure on a per ground terminal antenna/pedestal basis . This allows the Army to extrapolate pricing on a per site basis using the number of ground terminals per site. Please confirm this meets the Army's needs for ROM pricing evaluation.Yes. To support the Government's Rough Order of Magnitude (ROM) evaluation and allow for accurate scaling, vendors may use a representative 3-terminal (antenna/pedestal) site configuration as the standard baseline reference for their pricing structure.
35Page 7, Under Other Relevant Information - ScheduleIs the schedule required to cover only the First Article milestones and PoP, or does it also need to include a complete timeline for the production option covering integration/fielding for up to 20 global sites?The complete schedule timeline is mandatory.
362.5 Page 5Is a proposed PoP or schedule required as part of the solution brief, and is there a target date for First Article delivery?Yes, the proposed Schedule/PoP is required. Yes, the target date for First Article delivery is 2QFY28.
373.2. Page 11What is the anticipated timeframe between Step 1 notifications and the Step 2 pitch and demo sessions? Is there a notice period before sessions are scheduled?If accepted into Phase 2, additional information will be provided at that time.
383.2. Page 11Are slides or a leave-behind material permitted as part of the pitch?If accepted into Phase 2, additional information will be provided at that time.
393.2. Page 11For the demonstration, what equipment will be Government Furnished?If accepted into Phase 2, additional information will be provided at that time.
403.2. Page 11In addition to requirements, will Demo evaluation criteria be released before the demo, and how far in advance?If accepted into Phase 2, additional information will be provided at that time.
413.2 Page 11For the demonstration, will public internet connectivity be provided? Or is the demo expected to be conducted completely stand alone?If accepted into Phase 2, additional information will be provided at that time.
42ACC-APG_Digital+IF_Draft+Technical+Specfication+doc_W15P7T-27-R-DIGIF.docx
Page 2Will the Government provide the referenced WB C-SSE Terminal Performance Certification Test Procedures (Version 3.40 or later), or the applicable Section 4.3 excerpts as this document is non-publicIf accepted into Phase 2, additional information will be provided at that time.
43ACC-APG_Digital+IF_Draft+Technical+Specfication+doc_W15P7T-27-R-DIGIF.docx
Page 12; Section 3.2.1Please clarify whether Section 3.2.1 requirements apply at all supported bit depths (4–16 bits), only at maximum bit depth with lower depths meeting Appendix C's degradation criterion (≤ 0.1 dB C/N ), or under other conditions. If other conditions apply, please specify the bit depths and sample rates used for verification under Section 4.3.2.1Apply Appendix C requirements on sample rate and bit depth to Digital IF modem streams at the external modem-terminal interface. For internal composite Digital IF streams, sample rates and bit depths shall be adequate to sample the full IF band (500 or 1000 MHz) with less than 0.1 dB C/N degradation on the smallest carrier due to digital conversion.
44CfS Section 4.1, CfS Section 2.3CfS Section 4.1 states that "The Government intends to award one FAR Part 12 commercial contract as a result of this Call for Solutions." CfS Section 2.3 lists deliverables such as the TDP, ETM, NET, Test Reports, etc. On other PdM WESS efforts that we have worked on these documents require significant contractor effort to develop, format, validate and review as opposed to leveraging existing commercially available product documentation and training material. Such requirements may introduce substantial non-recurring costs not typically associated with the commercial product or its standard commercial support practices. Will the Government consider accepting existing commercial documentation and training materials?If accepted into Phase 2, additional information will be provided at that time.
45CfS Section 4.1, Draft Spec 4.1.4.1CfS Section 4.1 states that "The Government intends to award one FAR Part 12 commercial contract as a result of this Call for Solutions." Draft Spec Section 4.1.4.1 addresses First Article Testing. On other PdM WESS efforts FAT has required an exhaustive test verifying each requirement. This introduces substantial non-recurring costs not typically associated with the commercial product or its standard commercial support practices. Does the Government expect to retest all requirements that can be validated by test or does it expect to leverage commercial testing that has been done already?If accepted into Phase 2, additional information will be provided at that time.
46CfS Section 4.1CfS Section 4.1 states that "The Government intends to award one FAR Part 12 commercial contract as a result of this Call for Solutions." Is this effort intended to be solicited as CPFF and/or FFP? We believe it is reasonable for the commercial hardware to be proposed FFP, but the required services to generate final approved deliverables, First Article Testing, implementation of RMF controls and installation at the first teleport site requires significant interaction with the Government and are likely not suited for FFP. We believe future production units after these deliverables have been approved is feasible to be FFP.If accepted into Phase 3, additional information will be provided at that time
47CfS Section 4.1The purpose of a CSO is to identify, evaluate and acquire innovative commercial solutions more quickly and flexibly than traditional government procurement methods. The CSO allows for a variety of contract types to be awarded including FAR Part 12 and OTAs. We believe that a Prototype OTA that culminates in a fielded prototype to a single site with initial deliverables for TDP, ETM, and NET that verifies key requirements is a good approach since this is the first time Digital IF is integrated into a teleport. This can be done with a FFP contract. And once this is proven a future contract can be awarded to move forward to generate final deliverables and production units for other sites. Will the Government consider this approach?If accepted into Phase 3, additional information will be provided at that time
48CfS Section 4.1We believe that this effort is largely a COTS integration effort with associated services and is suitable to be a Small Business Set-Aside (SBSA). We believe that the Government is still expected to use the "rule of 2" within this process that says if there are two viable small business that are expected to submit proposals that the effort can be solicited as a SBSA. We believe that if the Government determines there are two viable small business after Step 2 "Pitch Session/Technical Demonstration" that Step 3 should be a SBSA. Will the Government adopt this approach? This helps small business determine the level of proposal resources that are allocated in Step 1 and Step 2 of this effort.OTAs are exempt from the FAR: Other Transaction Authority (OTA) instruments (authorized under 10 U.S.C. 4021/4022 for the Department of Defense) are not procurement contracts, grants, or cooperative agreements. Traditional Federal Acquisition Regulation (FAR) parts—including FAR Part 19 and the mandatory Rule of Two (FAR 19.502-2)—do not apply to OTAs.
49Section 1.1 BackgroundThe Government stated that PdM WESS "is seeking solutions for a COTS DIF system to satisfy the requirements for Increment 1 of this modernization effort." The PdM WESS DIFS System Specification document (A3225425, 5 June 2026) outlines an Increment 1 system for DIFS. Does the Vendor Technical Demonstration for this effort have to match exactly the Increment 1 DIFS System Spec doc (i.e. 64 carriers), or can vendors scale the design of their solution to meet Increment 1 design criteria after the evaluation of Step 2?The system design is up to the vendor's discretion.
50Section 1.1 Background and Section 2.1 Problem StatementThe Government stated, "Under this Call for Solutions, the selected vendor will deliver, integrate, install, and acceptance-test a flexible, open-standard, modular Digital IF solution..." DIFI defines open Digital IF transport interfaces but does not currently standardize M&C for devices such as modems, IFCs, and channelizers. Does the Government have additional expectations for open-standard M&C interfaces or protocols? More broadly, how should vendors demonstrate support for avoiding vendor lock-in when replacement components from other vendors may require unique M&C interfaces?Vendors are discouraged from proposing devices that employ undocumented or non-standards-based M&C interfaces (i.e. not listed on the DOD Information Technology Standards Registry).
51Section 2.2 Scope and Technical Objectives; Objective 6: Resilient and Maintainable Design:The Government stated "…and rapid maintainability (MTTR </= 30 minutes)…" There are a variety of components that could be repaired/swapped in this architecture. Does the MTTR apply to hardware only or to the Digital IF network routes? How are availability and MTTR calculated and demonstrated?The DIFS MTTR requirement applies to hardware only and includes all eight corrective maintenance elements listed in specification paragraph 4.3.2.4.1. MIL-HDBK-338 provides guidance for calculating MTTR. MIL-HDBK-472 provides guidance for calculating inherent availability.
52Section 3.1 Step 1 - Request for Solution Briefs; Other Relevant InformationThe Government stated, "Time directly dictates cost. A 45-day PoP implies a highly concentrated burst of work. Including the PoP explains your pricing; a $100,000 solution, for example, delivered over 1.5 months implies a very different team structure and urgency than the same cost spread over a year.". Is it the Government's intention to fund the demonstratable solution for the Step 2 Pitch Session/Vendor Technical Demonstration?No, the Government will not fund or provide financial compensation for the development of the Solution Briefs, the preparation of the demonstrable solutions, or travel/participation in the Step 2 Pitch Session and Vendor Technical Demonstration (PS/VTD). All activities under Step 1 (Solution Briefs) and Step 2 (Pitch Session/VTD) are considered part of the pre-award competitive evaluation phase, and participating offerors must bear their own associated costs.
53Section 2.2 Scope and Technical Objectives; Objective 3: High-Performance Digital Transport (Scalable)The Government stated, "The subsystem shall utilize a non-blocking, high-speed digital switch fabric to route Digital IF streams between all subsystem components and external interfaces (e.g., Digital Modems, Global Agile Integrated Transport (GAIT) connections, Wide Area Network (WAN) transport etc." For the final solution and pricing, can the Government provide additional information around the quantity of modems, connections, etc. that the DIFS system will integrate with so that we can assure the design can accommodate?If accepted into Phase 3, additional information will be provided at that time.
542.3 - Deliverables; Electronic Technical Manual (ETM)The Government stated that the primary deliverables will include an Electronic Technical Manual and New Equipment Training. Due to the fact that the Increment 1 system will likely develop organically based on engagement between the vendor and the Government over the course of the contract, can we (the vendor) reasonably expect that these may require some degree of scheduling to accommodate any changes derived from Increment 1?Yes
55Page 10; Rough Order of Magnitude (Unit Pricing)The Government stated, "Is the ROM price provided realistic for the work to be performed and reflect a clear understanding of the requirements? There also was a mention of "unit pricing". Is the Government looking for a line by line ROM of each piece of equipment in the BOM, including lower level components like cables, connectors, etc.? Does the Government want additional line items for elements such as installation, maintenance, and training?Both Yes
56Section 2.4 Programmatic Objectives & Commercial Acquisition StrategyThe Government stated: "The Government's objective is to verify a c, followed by the immediate execution of priced contract options...'"It appears that text is missing after 'verify a'. Could the Government please clarify what specific capability, baseline, or commercial solution the Government intends to verify prior to exercising the priced contract option?Please see revised Call for Solutions.
57Page 9; Achieve Military Compliance and Certification RequirementsWould the Government consider adding a requirement that all Digital IF equipment be WGS certified prior to award in order to reduce risk to the Government and speed up operation over WGS satellites upon delivery of Increment 1?No. WGS terminal certification is end-to-end for DIFS plus the antenna/RF equipment. Space Force Delta 8 does not certify individual terminal components.
58Section 4.1 Anticipated Type of AwardsThe Government stated, "The Government intends to award one FAR Part 12 commercial contract as a result of this Call for Solutions. The Government may also award an Other Transaction Authority (OTA(s)) as a result of a Vendor(s) submission(s)." FAR Part 12 contracts imply a simple acquisition path for the Government vs Other Transaction Authority (OTA) implies specific requirements (e.g.-nontraditional defense contractor, works share requirements, etc.). Would the Government clarify what may be awarded via FAR Part 12 vs OTA or pick one evaluation/award method as there may be significant partnering requirements imposed on the submitting contractor?If vendor advances to next phase, the information will be provided.
59Section. 2.1 Applicable DocumentsUnder section 2.1 Applicable Documents || Government Documents and within the spec itself in Section 4.3, the document titled “WB C-SSE Terminal Performance Certification Test Procedures” [latest revision at time of RFP release (Version 3.40, 2 April 2024 or later)] is referenced. This document is not publicly available. Will the Government provide the current revision of this document, or the excerpts cited in Section 4.3, to prospective offerors?If vendor advances to next phase, the information will be provided.
60DIFS Technical Specification Section 3.2.1Quantization noise at the low end of the 4–16 bit range will physically limit noise floor, spurious and EVM performance. Please clarify which of the following applies:

(a) The requirements of 3.2.1 must be met at every supported sample depth, 4 through 16 bits.

(b) The requirements of 3.2.1 must be met at full (maximum) bit depth with signal levels at 90% of full scale per 3.1.2.1.3. Lower bit depths need only meet the Appendix C criterion of ≤ 0.1 dB C/N degradation.

(c) Some other condition, in which case please specify the bit depth(s) and sample rate(s) the Government will use when verifying 3.2.1 under 4.3.2.1 for both modem streams and combined streams.Apply Appendix C requirements on sample rate and bit depth to Digital IF modem streams at the external modem-terminal interface. For internal composite Digital IF streams, sample rates and bit depths shall be adequate to sample the full IF band (500 or 1000 MHz) with less than 0.1 dB C/N degradation on the smallest carrier due to digital conversion.
61DIFS Technical SpecificationThe Government posted the draft DIFS Technical Specification document, although makes no reference to this document within the CFS. Is it expected for vendors to meet this technical specification in the solution, or should it be used as a general guide as the document is still a draft?The draft DIFS Technical Specification document is provided as a general guide and is not a strict compliance mandate. For the Step 1 Solution Brief (Section 3.1), the primary contractual evaluation criteria are the nine high-level Objectives outlined in Section 2.2 of the CfS. Vendors must focus on demonstrating how their commercial solution satisfies these core objectives and outline the long-term technical direction and desired specifications for the system.
622.1 – Technical Objective & Scope; 1.1 – BackgroundFor Increment 1, how many modems and RF apertures are expected to be supported at each of the up to 20 teleport sites? Please provide site-specific quantities or representative site configurations so offerors can develop a realistic rough-order-of-magnitude (ROM) cost estimate.ROM should account for HW and SW supporting up to 3 antennas, 64 FDMA modems, site integration, and sustainment support. ROM should be granular enough to allow the government to establish the estimated costs for sites with fewer antennas and modems.
632.1 – Mission Impact; 2.2 – Objective 4Is automated rerouting of Digital IF traffic from one SATCOM gateway or teleport to an alternate gateway expected as part of the Increment 1 solution? If so, please clarify the required use cases and extent of this capability.Yes, supporting the automated rerouting of critical traffic to alternate facilities (which includes alternate SATCOM gateways or teleports) is an explicit requirement of the Increment 1 software-based management suite under Objective 4. Under Increment 1, the management suite must feature the native logic and routing engine necessary to detect connection or component failures, and automatically re-establish or switch those critical communication paths to alternative destination IPs or pre-configured alternate teleport facilities. The Government declines to provide the specific operational use cases.
642.2 – Objective 3: High-Performance Digital TransportDoes the Government intend to use commercial wide area networks (WANs) to transport DIFI streams between globally dispersed teleports? If so, is support for commercial WAN transport required in Increment 1?The DIFS switch fabric must be network-medium agnostic capable of encapsulating and forwarding standard-compliant Digital IF packet streams (DIFI) across IP-routable networks (such as GAIT or standard WAN links) regardless of the underlying network provider.
652.2 – Objective 8: Military Compliance and Certification ReadinessWhich DIFS components are required to satisfy the applicable MIL-STD-810H environmental requirements: IF converters, digital combiners/dividers, IP switching fabric, or all delivered equipment? Please clarify the applicability of this standard to each equipment category.DIFS as a system must meet the MIL-STD-810 requirement. The MIL-STD-810H environmental requirements apply to all delivered hardware components (including the IF converters, digital combiners/dividers, and IP switching fabric). The vendors should detail the compliance posture of their hardware categories (e.g., existing commercial test data, previous military deployments, or design tolerances for temperature, humidity, and shock/vibration). If individual equipment cannot meet the requirement, it must be provided with protective measures.
662.3 DeliverablesIs there an example of the "FAT" First Article Testing that can be provided for reviewThe government will not provide a sample test report. See DoD First Article Test Report (MIL-STD-3018). First-article test verifies each requirement in Section 3 of the specification using test, demonstration, inspection, analysis or CoC as directed by the Verification Cross Reference Matrix (VCRM).
672.2 Objective 7; 2.3 RMF DeliverablesWill DIFS require a standalone Authorization to Operate (ATO), or will the subsystem be incorporated into existing GAIT/RHN/teleport/site ATO boundaries through an authorization update or assessment-only process?The Government’s intent is to establish a standardized core RMF package. The final authorization boundary whether a standalone ATO or a site‑specific inherited boundary will be determined by the Government in coordination with the Authorizing Official (AO).
682.2 Objective 7; 3.1 Secure and Compliant ArchitectureDoes the government require the NIST SP 800-53 Revision 5 Moderate baseline, and what Army, DoD, CNSSI, mission-specific, or system-specific overlays and control enhancements apply?The Government requires the system design to meet the standard RMF requirements outlined in Objective 7 in accordance with the latest NIST SP 800-53 Revision. Currently there is no specific DoD, CNSSI, Army-specific, or system-level overlays (such as the DoD Space System/SATCOM overlay) and specific control enhancements.
692.2 Objective 7; 2.3Is the contractor responsible for developing RMF documentation and supporting assessment activities only, or for delivering an authorization-ready package and supporting the government through an actual ATO decision?The contractor shall deliver an authorization-ready package (a robust set of RMF artifacts, security configurations, and design documentation) that proves the subsystem is fully capable of meeting the security controls in Objective 7. The contractor shall provide the technical and engineering support per Section 2.3 Integration Support throughout the government assessment to resolve all security inquiries or remediation actions issued by the Security Control Assessor (SCA).
701.1; 2.2 Objective 9; 2.3Will the government accept one standardized DIFS security authorization and assessment package across all teleport sites, or will site-specific RMF assessments, ATO updates, and authorization decisions be required?The Government intends to establish a single, standardized operational baseline across all teleports as stated in Sections 1.1 and 2.1. The RMF artifacts delivered by the vendor under Section 2.3 will represent this core baseline.
712.2 Objectives 7–8; 2.3; 2.5What cybersecurity assessment and testing activities must be completed before First Article acceptance, production authorization, and operational deployment, and which organization will conduct and fund them?More information will be provided if vendor advances to next phase.
722.3; 2.5 Program ScheduleIs receipt of an ATO a contractual prerequisite for First Article acceptance, site acceptance testing, operational fielding, or final payment, and how will delays in government-controlled authorization activities be handled?More information will be provided if vendor advances to next phase.
732.2 Technical Objectives; Objective 7Will DIFS be categorized as an Information System, Platform Information Technology (PIT), PIT subsystem, or another system type for Army RMF purposes?The baseline security requirement remains unchanged regardless of whether the system is categorized as a PIT, PIT Subsystem, or Information System.
742.2 Objectives 3–4; Objective 7What security architecture is required for the Automated Management and Control Function, including authentication, privileged access, management network segmentation, and remote administration?As required by the latest NIST SP 800-53 revision.
752.2 Objectives 3 and 7Will Digital IF traffic traversing GAIT, WAN, or inter-teleport connections require encryption, approved cryptographic protection, or an NSA-approved CSfC solution? Or does TRANSEC on the modems meet this requirement.There is no explicit Cryptographic/CSfC Mandate at this Stage. If accepted into next phase, additional information will be provided at that time.
762.2 Objective 7; 2.3; 3.1What requirements apply to centralized logging, audit retention, security event forwarding, endpoint monitoring, and integration with existing government SOC/SIEM infrastructure?The vendor's solution must support the latest NIST SP 800-53 revision. Standard for security controls required to achieve and maintain RMF compliance for a Moderate-Moderate-Moderate categorization.
772.2 Objectives 6–7; 2.3; 3.1Who will own vulnerability management, security patching, STIG maintenance, POA&M updates, and continuous monitoring during the 15-year operational service life?During the 15-year operational service life, the vendor is expected to deliver the baseline security architecture, provide RMF verification artifacts (under Section 2.3), and propose a long-term sustainment plan, field service support, and yearly sustainment/service agreements (under Section 3.1, Items 3 & 4) to support maintenance; and the Government will ultimately hold the RMF Authorization to Operate (ATO) and maintain the daily cybersecurity tasks (such as running continuous monitoring tools, applying patches, and updating POA&Ms) which will be finalized through the sustainment/service agreements proposed by the vendor and collaborative discussions per Section 3.4.
782.2 Objectives 7 and 9; 2.3What events will trigger a reassessment or authorization update when new teleport sites, software releases, hardware revisions, or future DIFS increments are introduced?If accepted into the next phase, additional information will be provided at that time.
792.3 DeliverableWill the ETM go through a full CECOM V & V for this process; will fielding be allowed with a Draft if soA full CECOM‑approved reproducible copy of the ETM is not required.
802.2 Scope and Technical Objectives - Objective 3Is there a larger ecosystem the government is looking to feed into for monitoring, control, planning and execution of missions?Objective 3 does not mandate feeding into a broader operational ecosystem, but the architecture should remain flexible enough to support external management interfaces if required in future increments.
812.2 Deliverables Technical Data Packagecan the government specify the DID's and CDRLs that will be used for the level of documentation for the technical package?If accepted into next phase, additional information will be provided at that time.
823.2 Step 2 Pitch SessionDoes the government have a planned window they can share for the pitch sessions?To be announced

File details come from the government source that posted it. Updated .