Attachment 0011 - Questions and Answers (QA) RFP W519TC-23-R-0031.pdf

Enterprise Digital Intermediate Frequency Multi-Carrier (EDIM) Modem Questions and Answers

Item # Subject PWS/USG Reference Questions/Comments USG Response

Government Furnished Equipment List Attachment 0008 GFE List GFE excel file was provided with no other instructions. Which submittal volume should include this file? The GFE list identifies equipment the Government will provide to the Contractor to assist with First Article Testing (FAT) at the Contractor's facility, where the Contractor shall be expected to demonstrate the capabilities of their EDIM Modem and how it interoperates with the EBEM.

2 Performance Based Payments General Will performance based payments be considered as part of this contract? No. Performance based payments will not be considered.

Price Matrix (Maint. Repair and Replacement Costs)

Attachment 0001 PWS, Paragraph

5.1 (page 17-19)

Where in the Price Matrix does the Gov intend for bidders to include pricing associated with PWS paragraph 5.1 (Maintenance Repair and Replacement Service) of the PWS?

Bidders should include costs in the most appropriate CLIN listed in the Base Year and Option Years 1, to include the Extended Warranty CLIN within Option Year 2-4. Government has identified a number of CLINS associated with the requirements of deliverables. The Government did not prescribe or breakout how those costs will be distributed as it could be used to derive a preferred technical solution, which was never the intent. Bidders are encouraged to identify costs associated with the delivery of any and all deliverables as required to support their technical solution.

Technical Study Attachment 0001 PWS, Paragraph 8

(page 43) Does the Gov want any scope related to PWS paragraph 8 included in any of the proposal volumes, or is this considered outside the scope of this RFP? No. The Government does not require Offerors to address PWS, paragraph 8 (Technical Study) at this time. If the

Government requires an optional technical study after award, the Government will provide a technical description of the study and request the Contractor to submit a FFP proposal to complete the study.

Price Matrix (CDRL Costs) Attachment 0001 PWS, Paragraph

14 (Page 49-50) Where would pricing associated with the generation of all CDRL's referenced in the PWS be captured in Attachment 0003 Price Matrix? Technical Data Package (A002) and Interface Control Document (A003) are two examples.

Please refer to the Government's response to Item #3.

6 PWS (Redlines) Attachment 0001 PWS Can bidder submit redlines to the PWS for clarity and compliance issues? No. Any questions regarding a PWS issue need to be submitted.

Price Matrix (Schedule) Attachment 0003 Price Matrix Can the schedule for completing CLIN's 001, 002, and 003 exceed a 12 month period and still be considered a compliant offer? Yes, the schedule for completing CLINs 0001, 0002, and 0003 may exceed a 12-month period and still be considered compliant; however, the Government will consider an Offeror's failure to comply with any timelines specified in the PWS in evaluating the Offeror's proposal.

Price Matrix (Quantity) Attachment 0003 Price Matrix Higher quantity order sizes greater than 300 Units may provide a cost benefit to the government. Can higher quantity prices be included in the proposal?

And if yes where should they be included?

No. Higher quantity prices may not be included in the proposal. Please adhere to the quantity limits included in the price matrix.

Volume 3 - Price (Narrative) Attachment 0005 Section L, Paragraph 5.3 Can the bidders submit a separate Narrative document for the cost volume in additional to the RFP Pricing Matrix Excel Workbook? No. Please refer to Section L Volume 3 / Factor 3 – PRICE.

Offeror Assuptions Attachment 0005 Section L, Paragraph 5.4 Where should Offeror bid assumptions be included? ACC-RI cannot advise Offerors where to include their assumption. Offerors must make that determination themselves.

Page Count Attachment 0005 Section L, Paragraph 5.2.3 Are the ISRs or SSRs part of the page count for V-2 Management? No. The ISRs or SSRs are not part of the page count.

Requirements Compliance Matrix Attachment 0005 Section L, Paragraph 3.2.2 Is a Requirements Compliance Matrix required and can this be submitted as an attachment? No. A Requirements Compliance Matrix is not required.

Offeror POC Attachment 0005 Section L, Paragraph 5.4.3.4 Can POC's be identified at the three contractors that will be performing proposal evaluation? No. POCs will not be identified.

Program Management ( Evaluation Criteria) Attachment 0006 Section M, Paragraph 5.2.4 Will customer provide Evaluation Criteria for Subfactor 2D – Program Management? The Evaluation Criteria was inadvertently removed. An updated Attachment 0006 Section M will be included in

Amendment 0002.

Small Business Participation Attachment 0006 Section M, Paragraph 7.2.3

In bullet d, are the goals for procurement listed under this sub- bullet (Small Disadvantaged Business, Women Owned Small Business, etc.) in addition to the general Small Business Participation requirement? For example, would an offer need to include 15% small business participation and 2% small disadvantaged business participation to be considered compliant with this requirement?

Yes, the individual socio-economic goals are in addition too the general Small Business Participation goal. Simply meeting the 15% Small Business subcontracting goal will not make the offeror compliant with the specific socio-economic goals established in the RFP. Each special type (socio-economic) of small business is first of all a small business. This means an offeror can take credit in every category that is applicable to the recipient of the subcontract. However, any credit that applies to multiple socio-economic categories will not be double or triple counted towards the general Small Business Participation goal. See section (b) of Attachment 0007, Small Business Participation, for an example of receiving credit for multiple categories and how the overall SB percentage is impacted. Attachment 0007 will be provided in Amendment 0002.

L-Band Input Attachment 0002 Specification, Paragraph 3.2.5.5.3 Page 36

Does the requirement for L-Band input of:

The LM demodulator shall operate to a minimum carrier level Pmin, such that Pmin = -130 dBm/Hz + ESym/N0 + 10 log RSym [dBm]

Supersede the requirement of:

1.4 Digital IF Migration

Digital IF Enterprise terminal infrastructure is key to supporting DOD SATCOM growth and resilience. The EDIM Modem supports the transition from L- Band to Digital IF infrastructures by offering dual IF interface sets. Operation over the L-Band IF is compliant with MIL-STD-188-165B.

EDIM and MIL-STD-188-165B have different Min Rx input power.

The EDIM has 17dBm/Hz lower noise floor.

Therefore, the EDIM receiver requires a lower Rx Noise Figure (NF).

Yes.

DVB-S2X Attachment 0002 Specification, Paragraph 4.3.2.5.2.2.2, Page 94

The requirements of Section 3.2.5.2.2.2 and its subsections shall be verified, to the maximum extent possible, through interoperability with legacy DVB- S2X modems presently in DOD SATCOM service.

As mentioned in the RFP many vendors have slightly modified GSE or perform ACM in ways that are not published. Can DOD provide a list or golden unit to which interoperability will be tested? Can the vendor use one of its own modems provided that it can be verified it is in use by the DOD?

The intent of allowing the DVB-S2X waveform is to allow vendors flexibility in their approach to extending EDIM Modem rates beyond present EBEM rate limits. The intent of verification through legacy interoperability is to simplify the verification of DVB-S2X waveform compliance with cited standards. The Government is not prepared, at this time, to suggest one or more legacy DVB-S2X "gold standard" modems for this purpose. Yes, a vendor can use one of its own modems, but Sections 3.2.5.2.2.2.2 thru 3.2.5.2.2.2.4 include requiremens for documentation of waveform constructs, which exceeds simple interoperability testing against individual legacy modems.

EMMS Software Installation Attachment 0002 Specification, Paragraph 4.3.3.2.1.1, Page 111 Referencing “m. Test that EMMS software installation can be completed in less than 60 minutes”, can we assume that all machine OS and all virtualization tools as well as any other needed supporting software is installed an up to the proper revision and that this time is purely for the installation of the EMMS core software?

Yes. Please refer to Attachment 0002 Specification for the EDIM Modem System.

OI Software Installation Attachment 0002 Specification, Paragraph 4.3.3.2.1.2, Page 112 Referencing “m. Test that the OI software installation can be completed in less than 10 minutes”, could we assume that all machine OS and all virtualization tools as well as any other needed supporting software is installed an up to the proper revision and that this time is purely for the installation of the EMMS core software?

Yes; however, Section 4.3.3.2.1.2 concerns the Operator Interface--not the EMMS core software, which is addressed in Section 4.3.3.2.1.1. Please refer to Attachment 0002 Specification for the EDIM Modem System.

Configuration Integrity Attachment 0002 Specification, Paragraph 4.3.3.4.5, Page 114

Referencing “(d)emonstrate that before committing a configuration change on a dataset, the EDIM Modem System

a. detects issues within the EDIM Modem System that will result from impending changes and affect other configuration datasets,

b. alerts the controlling operator of the issues, and”

Is the intent for the M&C system prevent an out of bounds (improper configuration of a carrier due to frequency, SR, capability being out of bounds) or to know and prevent any configuration change what would negatively impact an existing link on any other carrier within a 1RU EDIM modem? Within the entire known network?

Yes, the intent is for the M&C system to prevent "an out of bounds" configuration. Please refer to Attachment 0002 Specification for the EDIM Modem System.

Yes, the intent is for the M&C system to prevent any configuration change that would negatively impact an existing link on any other carrier with a 1RU EDIM modem--especially on the L-Band output interface. Please refer to Attachment 0002 Specification for the EDIM Modem System.

No, this is not required within the entire known network at this time (i.e., it is probably not required at the EMMS level).

Network Interface Isolation Attachment 0002 Specification, Paragraph 4.3.4.7, Page 120

EDIM Modem network interface isolation shall be verified by demonstration. Corresponding internal resource isolation shall be verified by analysis of the EDIM Modem design.

Would the Government clarify what is meant by network interface isolation?

Network Isolation means the practical separation of independent LANs for data traffic, Digital IF, and management. In other words, separation of data, management, and Digital IF planes.

Third Party COTS General Are third party COTS open source SW utilities/applications not integrated directly into the EMMS SW offering acceptable to implement various aspects of the system requirements?

Open source software must be evaluated and approved prior to its use. US Army Regulation 25-2 provides guidance on Open Source Software.

NMS Attachment 0002 Specification, Paragraph 3.3, Page 47 Not including the Future Site-Level NMS, are the EMMS requirements limited to individual sites, or an entire network composed of many sites, each with its own EMMS? Are the EMMS instances from individual sites required to be interconnected and integrated together in any way, once again excluding the Future Site-Level NMS?

EMMS is intended to function over a LAN (single-site), not a WAN (between sites).

NMS Attachment 0002 Specification, Paragraph 3.3.2.1.1, Page 48

Referencing “(t)he EMMS shall be the central point of secure machine control for up to 256 locally networked EDIM Modems. The EMMS shall consist of software operable on both SHB platforms IAW Section 3.4.8 and virtual machines. The EDIM Modem System shall support 1 to 4 EMMS instances. The EMMS shall support minimal operation that consists of a single EMMS and a single OI collocated on the same hardware platform. EMMS instances shall securely support at least 16 concurrent OI connections and 256 concurrent EDIM Modem connections. EMMS instances shall concurrently support at least 16 active secure sessions between OIs and EDIM Modems.”

Please provide a use case example for the support of 1-4 EMMS instances? Do the concurrent EMMS sessions provide resiliency or another capability?

Multiple simultaneous EMMS instances are intended to support

* continuous M&C operation in the event of the failure of any EMMS platform

* make-before-break upgrades/updates of EMMS instances or of EMMS host platforms

* load balancing, as needed, to support 16 operators simultaneously controlling 256 EDIM Modems EMMS instances should be capable of working alone (one instance) or together (two or more instances backing each other up and/or load sharing).

Failover vs Self-Heal Attachment 0002 Specification, Paragraph 3.3.2.1.1, Page 48

Referencing “EMMS instances shall be simultaneously operable on separate hardware platforms for the sake of redundancy and availability. It will be acceptable to employ load-sharing across multiple EMMS instances. Failure of any EMMS instance shall be automatically detected, upon which surviving EMMS instances shall continue supporting EDIM Modem System functions with minimal, if any, interruption.”

Is the expectation that a spare EMMS can take over for a failed EMMS, or is the expectation that the failed EMMS system self-heal?

The expectation is that surviving EMMS instances take on the management load of failed EMMS instances, and that surviving EMMS instances alert operators of the failures, so they may be addressed (e.g. failed host hardware repair or replacement). EMMS instances should be capable of working alone (one instance) or together (two or more instances backing each other up and/or load sharing).

Auto detection Attachment 0002 Specification, Paragraph 3.3.2.1.1, Page 48

Referencing “Each EMMS instance shall automatically detect the presence of each new EDIM Modem on the M&C network and enable subsequent operation. Each EMMS instance shall detect the presence of each new EMMS instance on the M&C network and allow the operator to enable subsequent operation. Each EMMS instance shall detect the presence of each new OI on the M&C network and enable their subsequent operation.”

Please clarify the use case for this paragraph.

The use case is for auto-registration of EDIM Modems (up to 256), EMMS instances (up to 4), and OI instances (up to 16) introduced into the (local) EDIM Modem System.

Integrity Risk Conditions Attachment 0002 Specification, Paragraph 3.3.4.5, Page 55

Will all "Integrity" risk conditions be outline and defined by the customer in future requirements documentation?

Is the intent for the M&C system prevent an out of bounds (improper configuration of a carrier due to frequency, SR, capability being out of bounds) or to know and prevent any configuration change what would negatively impact an existing link on any other carrier within a 1RU EDIM modem? Within the entire known network?

No, the Government will not outline and define all "Integrity" risk conditions in future requirements documentation.

Yes, the intent is for the M&C system to prevent "an out of bounds" configuration.

Yes, the intent is for the M&C system to prevent any configuration change that would negatively impact an existing link on any other carrier with a 1RU EDIM modem--especially on the L-Band output interface.

No, this is not required within the entire known network at this time (i.e., it is probably not required at the EMMS level).

Integrity Risk Conditions Attachment 0002 Specification, Paragraph 3.3.5.4, Page 57 Clarification on use case requested. Does this outline capability to send out commands, or groups of commands similar to a type of macro functionality to multiple modems at same time via a single user action?

This is a comprehensive modem suite management requirement. The intent is to offload repetitive tasks and cognitive load from the operator.

Linux Based SW Components Attachment 0002 Specification, Paragraph 3.4.8, Page 64

Referencing “a. The EMMS shall be capable of being executed on, or otherwise accessed in its entirety, from an SHB Microsoft Windows based server or computer. The OI shall be capable of being executed on, or otherwise accessed in its entirety, from an SHB Microsoft Windows based computer. For guidance on the implementation of Microsoft Windows SHB, please refer to DSD Memorandum, dated Feb 26, 2016, and entitled “Implementation of Microsoft Windows 10 Secure Host Baseline.” Supporting software and storage necessary for each component shall be capable of residing on the same component’s hardened platform.”

What is the acceptable method to handle required SW components that are Linux based?

Offerors proposing SW components that are Linux based should explain how SW components that are Linux based can be accessed from an SHB [or otherwise equivalently hardened] Microsoft Windows [or appropriately approved OS] based server or compute, as necessary.

Font Attachment 0005, Paragraph L.3.1.2, Would the Government accept the use of 10-pt font in the headers and footers? No. Please refer to Section L.3.1.2 for font size.

Use of CUI Attachment 0004 DD254, Paragraph

14, Page 3 The DD254 states “All information furnished to the Contractor is to be used as Controlled Unclassified Information (CUI).” Yet the PWS, Specification and other documents provided are not marked CUI. Please clarify classification guidance or markings.

An updated DD254 is provided in Amendment 0002.

Day/Time Reference Attachment 0002 Specification, Paragraphs 3.2.1.1 and 3.2.1.2, Pages 19 and 20

If both systems are in use, will the time of day reference and the frequency reference be synchronized such that they do not drift independently?

For example, if a 10 MHz reference is supplied, and PTP is employed, will the PTP time advance in lock step with the 10 MHz clock period of the frequency reference? If an external frequency reference is supplied, will it be supplied to all elements of the system (e.g. modem, combiner, digitizer)? If an external time of day reference is supplied, will it be supplied to all elements of the system?

"Lock-step" synchronization is not guaranteed between TOD references IAW 3.2.1.1 and frequency references IAW 3.2.1.2.

The intent at this time is for common necessary external TOD and frequency sources to be supplied to all locally networked Digital IF subsystems.

SHB Server Attachment 0002 Specification, Paragraph 3.2.5.1.5, Page 23 Figure 14 references an “SHB Server”. DSD Memorandum “Implementation of Microsoft Windows 10 Secure Host Baseline” directive 6 states “This Windows 10 implementation does not include Microsoft Server Operating Systems”. Is “SHB Server” intended to be a Windows 10 workstation?

The intent is that the EMMS will lend itself to being hosted flexibly on servers or workstations.

To the extent that "SHB," or any specific Windows OS, may be out of context WRT servers because it applies to workstations, approved server OS and appropriate hardening will be necessary.

M&C Interface Attachment 0002 Specification, Paragraph 3.2 , Page 19 Is the M&C interface on the modems IPv4, IPv6 or dual-stack for the intent of discovery? The M&C interface is dual-stack.

Virtual Machine Environments Attachment 0002 Specification, Paragraph 3.3 , Page 48 What “Virtual Machine” environments are expected to be supported as referenced in 3.3.2.1.1, 3.3.2.1.2, 4.3.3.2.1.1, 4.3.3.2.1.2? These are not specifically called out.

Virtual machine environments will be identified during EDIM Modem System development after consultation with the Contractor. M&C software components are expected to be flexible with respect to host environments.

Hypervisor Attachment 0002 Spedification, Paragraph 3.3 , Page 48 What hypervisor will be available on the government systems to run the virtual machines? Hypervisor system details will be provided during EDIM Modem System development after consultation with the

Contractor. Software solutions are expected to be flexible in this respect.

Third-Party Integration Flexibility Attachment 0002 Specification, Paragraph 3.3 , Page 48

6. Regarding 3.3.1, “Third-Party Integration Flexibility”, what specific areas would you want to see third-party integrations? The Government desires third-party integration flexibility WRT host platforms. The Government also desires third-party integration flexibility WRT comprehensive site level management of the Northbound EMMS interface IAW section 3.7.2.1.

FIPS Attachment 0002 Specification, Paragraph 4.3.4 , Page 117

Please clarify whether FIPS is relevant to EMMS and OI or just modem? If it is relevant to EMMS or OI, is FIPS Level 1 sufficient? FIPS is relevant to any system component that has internal crypto modules or data encryption standards, which generally includes modems and components that do data encryption. These systems must contain NIST approved key management algorithms. The modem's crypto module must be validated under the NIST Cryptographic Module Validation Program and meet a minimum of FIPS 140-3 Level 2. Army Regulation 25-2 identifies general FIPS requirements.

RFP RFP, Section A, Page 2 The Period of Performance is insufficient to implement the PWS and Specification; the Government funding may not cover the development cost associated with CLINs 0001, 0002, 0003, and 1001; with full Government purpose rights to the solution and no assured production, the program appears imbalanced. How does the Government intend to restructure the RFP to be more balanced?

ACC-RI has no plan to restructure the RFP.

EDIM Modem Quantity RFP, Section I, Page 14 The Government specifies a minimum of 38 EDIM Modem first articles for FAT. How many additional EDIM modems does the Government intend to buy during this IDIQ Contract?

The Government intends to order a minimum of 1 to a maximum of 300 modems per option year.

Digital IF Pricing Attachment 0002 Specification, Paragraph 3.2.4.3, Page 21

Based on the availability of Digital IF products capable of supporting the DIFI IAW IEEE-ISTO Std 4900-2021 standard, and currently available on the market today, did the IGCE consider the current market prices of these devices when considering this to be supported on the EDIM modem? Currently, devices capable of supporting the DIFI IAW IEEE-ISTO Std 4900-2021 standard range from $48,500 to $100,000. Specifically, these capabilities include converting an L-Band spectrum (950 MHz to 2150 MHz) to and from the DIFI IAW IEEE-ISTO Std 4900-2021 standard over a 40/100 GBE Ethernet connection, similar to the EDIM specification.

Yes. Digital IF current market prices were considered.

Digital IF Pricing Attachment 0002 Specification, Paragraph 3.2.4.3, Page 21 When considering Digital IF (DIFI) support to be provided by the EDIM modem for the DIFI IAW IEEE-ISTO Std 4900-2021 standard, did the IGCE consider single channel where one RF interface (spectrum) is supported per 40/100 GBE interface or multi-channel multiple RF interfaces (spectra) to be supported per 40/100 GBE interface?

The intent is for Digital IF interfaces to each support multiple carrier channels.

43 CP's and/or ECPs Attachment 0003 Price Matrix Is it the governments intent to award CPs and/or ECPs under this IDIQ Contract in the base year and/or the option years? Please refer to PWS, Paragraph 2, Configuration Management.

Government Budget RFP, Section A, Page 2 Does the Government have projected, in the FY 24-27 budget requests, funding for option years 1-4, to include production lot buys? The requested information is pre-decisional. The Government will exercise option periods and optional CLINs, as needed.

RFP Extension RFP, Section A, Page 3 The current closing time for the RFP response is set to 25 January, 2023. Due to holidays, and impact on small business coordination, we respectfully request a 3 week extension to the proposal due date The Government concurs with an extension. Please refer to Amendment 0001 for the revised submission date.

EBEM and/or DVB-S2X Waveforms Attachment 0002 Specification, Section 3.2.5.2.2, Page 27

Paragraph 3.2.5.2.2 states that added value to the Government can be achieved by EDIM supporting both EBEM and DVB-S2X waveforms at higher symbol rates ("at least one of the following methods") although it is commonly understood that DVB-S2X has superior bandwidth efficiency to EBEM. It is also known that there are no widely deployed EBEM modems operating above 60 Msysm/s, while there are widely deployed DVB-S2/S2X modems operating above 60 Msym/s. Thus it seems that the better overall benefit to the Government (balancing performance, cost, and risk) would be to deliver either EBEM or DVB-S2X but not both. Should "at least" be stricken from the 3.2.5.2.2 phrase "by employing at least one of the following methods:"

The Government agrees and removed this language.

Government Budget RFP, Section A, Page 2 According to the publicly available budget documents there looks to be about $3M dollars of RDTE available for this program per year, which in our estimation is inadequate to complete the scope of work within the base and option year 1. The scope of work for development, integration, and test on this program in the base year and option year 1 is likely in excess of Can the Government clarify this? This discrepancy creates a poor business case for industry participation and may limit full and open competition.

This is a fixed-price requirement. Offerors are required to propose their prices. The Government is then required to determine whether the proposed prices are fair and reasonable and how best to fund the requirement.

Manpower Reporting Attachment 0001 PWS, Paragraph

13, Page 47 Manpower Reporting is not consistent with FFP full and open competition, does the Government intend to make this program Cost Reimbursable? No, the Government does not intend to make this program cost reimbursable.

Period of Performance RFP, Section A, Page 2 Will the Government modify the Period of Performance for CLINS 0001, 0002, 0003, and 1001, to be consistent with the work scope requested in the PWS and Specification? Period of Performance for these CLINS should be a minimum of 36 months.

No, the Government does not intend to modify the period of performance (POP) for CLINs 0001, 0002, 0003, and 1001 because the Government believes the existing POP for these CLINs is sufficient to perform the required work. The Contractor is required to conduct a PDR (CLIN 0001) within 90 calendar days after the Systems Requirements Review, which the Contractor is required to conduct in conjunction with the Post-Award Conference. The Contractor is required to conduct the CDR (CLIN 0002) within 60 business days of the PDR. Therefore, the Contractor should be able to complete CLINs 0001 and 0002 during the base year of the contract. FAT Hardware (CLIN 0003) will begin in the Base Year, but delivery of the Hardware is not required until FAT in accordance with PWS paragraph 4.1.b. FAT (CLIN 1001) is requied to be conducted in Option Year 1. If the Contractor is unable to complete the FAT within Option Year 1, the Government will consider extending the POP for CLIN 1001 at the appropriate time.

Unlimited Rights Attachment 0001 PWS, Section

3.5.2.2, Page 7 The Governments request for unlimited rights is not consistent with FFP full and open competition, does the Government intend to make this program Cost Reimbursable?

No, the Government does not intend to make this program cost reimbursable.

Unlimited Rights Attachment 0001 PWS, Section 5.4.2, Page 23

The PWS specifies that the technical data documentation to be delivered shall be delivered with the license rights provided by DFARS 252.227-7013 and 252.227-7014, as applicable to technical data related to noncommercial items or noncommercial software. However, it also states that “all source data for commercial items shall be delivered with unrestricted rights to use, modify, reproduce, release, perform, display or disclose the data per DFARS 225.227-7015, Technical Data – Commercial Items.” Per DFARS 225.227-7015, the only commercial item technical data subject to unrestricted rights are the data listed in paragraph (b)(1) of the clause, and any requirement to deliver all commercial item technical data with unrestricted rights would violate 10 USC 3771 and DoD policy. We request clarification that only the data listed in that paragraph are to be delivered with unrestricted rights, and confirm that any technical data covered by paragraph (b)(2) of the clause will be subject to the restrictions specified by paragraphs (b)(2) and (b)(3).

The requirement to deliver source data for commercial items with unrestricted rights to use, modify, reproduce, release, perform, display, or disclose the data per DFARS 225.227-7015, Technical Data - Commercial Items, is limited to the circumstances specified in DFARS 225.227-7015(b)(1). The Government intends to apply and enforce the other provisions of DFARS 252.227-7015 in accordance with their terms. Please note, however, that the EDIM Modem is not a commercial product, as that term is define in FAR 2.101. Therefore, while the EDIM Modem may incorporate some COTS products/elements, the Government anticipates that most of the items, components, processes, computer software and/or computer software documentation required for the development of the EDIM Modem will be developed exclusively with Government funds or mixed funding.

Source Material Definition Attachment 0001 PWS, Section

5.4.2, Page 23 Preparation and Delivery of Technical Data states that the “contractor shall package and delivery all source material for all deliverables under this contract.” “source material” is not defined. Please clarify that this term refers only to any technical data or computer software required by the contract to be delivered under as a CDRL item.

Source material is all data under the CDRL, whether it is technical or computer software.

Data Rights Attachment 0001 PWS, Section 5.4.2, Page 23

The PWS states that all codes, intellectual property rights, and technical data rights used to generate technical publications in support of this PWS shall revert to the Government in the event that the Contractor no longer supports the program.” “Used to generate” is not clear and is overly broad because it could implicate third-party information that embodies third-party intellectual property rights (e.g., Microsoft Word may be “used to generate” a technical publication), and the requirement to transfer all rights to the Government violates the statutes and regulations discussed in earlier questions.

Please clarify the scope of the specific data and the license rights the Government would obtain in the event the Contractor no longer “supports the program.” For example, is the Army seeking to convert any Limited Rights, Restricted Rights, and/or Commercial Rights in technical data and computer software delivered under the contract to Government Purpose Rights in the event the contractor no longer “supports the program”?

The Government's data rights are set forth in DFARS 252.227-7013, DFARS 252.227-7014, and DFARS 252.227-7015, and the Government intends to apply and enforce those clauses in accordance with their terms.

Missing Clause RFP, Section I, Page 14 DFARS 252.227-7015 Clause, Technical Data-Commercial Items, is not included in the list of clauses in RFP Section I. Request that the agency add this clause to Section I, which governs the government’s license rights in any contractor or subcontractor technical data pertaining to commercial items, or any portion of a commercial item that was developed exclusively at private expense in accordance with DFARS 227.7102-4(b).

The Government will add DFARS 252.227-7015 to the RFP.

Warranty Requirements Attachment 0001 PWS, Section 2.4, The PWS requires a 12 month warranty from acceptance at destination. Please clarify what the requirements for the coverage are. At a minimum, the warranty must cover the requirements in PWS, paragraph 2.4, Warranty, as well as the requirements in

PWS, paragraph 5.1.2, Maintenance Repair, and its subparagraphs.

Data Rights Attachment 0001 PWS, Sections

3.5.2.2 and 5.4.2, Pages 7 and 23

The RFP also incorporates by reference the data rights clauses at DFARS 252.227-7013 and 252.227-7014, which govern the government’s rights in technical data for noncommercial items and noncommercial computer software.

It is DoD Policy to acquire commercial computer software or commercial computer software documentation “under the licenses customarily provided to the public unless such licenses are inconsistent with Federal procurement law or do not otherwise satisfy user needs,” and that “[o]fferors and contractors shall not be required to (1) Furnish technical information related to commercial computer software or commercial computer software documentation that is not customarily provided to the public except for information documenting the specific modifications made at Government expense to such software or documentation to meet the requirements of a Government solicitation; or (2) Relinquish to, or otherwise provide, the Government rights to use, modify, reproduce, release, perform, display, or disclose commercial computer software or commercial computer software documentation except for a transfer of rights mutually agreed upon.” DFARS 227.7202-1.

Additionally, DFARS 227.7203-1 prohibits agencies from requiring offerors to relinquish their rights in any computer software developed exclusively at private expense either as a condition of being responsive to a solicitation or as a condition of award, and from prohibiting or discouraging offerors from furnishing or offering to furnish computer software developed exclusively at private expense solely because the Government’s rights to use the software may be restricted:

(c) Offerors shall not be required, either as a condition of being responsive to a solicitation or as a condition for award, to sell or otherwise relinquish to the Government any rights in computer software developed exclusively at private expense except for the software identified at 227.7203-5(a)(3) through (6);

(d) Offerors and contractors shall not be prohibited or discouraged from furnishing or offering to furnish computer software developed exclusively at private expense solely because the Government's rights to use, modify, release, reproduce, perform, display, or disclose the software may be restricted.

What is the Governments plan to amend the RFP to comply with the data rights clauses of DFARS?

As noted above, the EDIM Modem is not a commercial product, as that term is define in FAR 2.101. Therefore, while the EDIM Modem may incorporate some COTS products/elements, the Government anticipates that most of the items, components, processes, computer software and/or computer software documentation required for the development of the EDIM Modem will be developed exclusively with Government funds or mixed funding. IAW DFARS 252.227-7014(b)(1), the Government is entitled to unlimited rights in computer software developed exclusively with Government funds and computer software documentation required to be delivered under the contract. IAW DFARS 252.227-7014(b)(2), the Government is entitled to Government purpose rights in computer software developed with mixed funding. To the extent the Contractor can demonstrate that computer software required for the development of the EDIM Modem was developed exclusively at private expense, DFARS 252.227-7014(b)(3) will apply. To the extent the Contractor can demonstrate that computer software required for the development of the EDIM Modem is "commercial computer software," as that term is defined in DFARS 252.227-7014(a)(1), the Government acknowledges that it shall only have the rights specified in the commercial license under which the software was obtained. Please note, however, that PWS, paragraph 3.5.2.2, requires the Contractor to provide a justification for the assertion of restricted or limited rights in software items, as well as an Analysis of Alternatives (AoA) documenting alternatives considered, the criteria for the selection of the software item, and the strategy and estimated cost for the life cycle support of that item. The Government does not intend to require the Contractor to sell or otherwise relinquish any rights in computer software developed exclusively at private expense , nor does the Government intend to prohibit or discourage Contractors from providing an EDIM Modem that includes computer software developed exclusively at private expense .

Data Rights Attachment 0001 PWS, Sections

3.5.2.2 and 5.4.2, Pages 7 and 23

PWS Section 3.5.2.2 appears to violate DoD’s policy and these prohibitions (including the same prohibitions regarding technical data, per DFARS 227.7103- 1(c), (d); 10 USC 3771(b)(8)), and is inconsistent with the government’s license rights under DFARS 252.227-7013, 252.227-7014, and 252.227-7015 (including as the clauses are also incorporated into PWS 5.4.2). Specifically, Section 3.5.2.2 states that the “Government will have “unlimited rights to all software, documents, and material, except the Commercial-Off-The-Shelf (COTS)/modified COTS elements, produced under this contract.”

First, it is unclear what is meant is by “documents” and “material”—please clarify what “documents” and “material” this statement is referring to and confirm that this statement is referring only to such software, documentation, or other “material” required to be delivered as a Contract Data Requirements List (CDRL) item. Second, the term “produced” is not clear and to the extent that it means “delivered to the Government under the contract,” the requirement to deliver “all software, documents, and material” with unlimited rights is inconsistent with DoD policy and violates the prohibitions in DFARS 227.7203 and 227.7103, and 10 USC 3771(b)(8). Similarly, the specification that “[a]ny customization done to a COTS solution shall become the sole property of the Government” likewise violates DoD policy, DFARS 227.7203 and 227.7103, and 10 USC 3771(b)(8) by requiring offerors to relinquish not only license rights (and discourages offerors from proposing a solution that may restrict the government’s license

For these reasons, and because the government’s license rights are defined by and adequately described by the terms of DFARS 252.227-7013, 252.227- 7014, and 252.227-7015, and any commercial software licenses (see, e.g., PWS 3.5.2.3 requiring contractor to obtain all COTS software and software licenses from Army CHESS program), request that PWS 3.5.2.2 be revised to delete these specifications.

See prior response. PWS, paragraph 3.5.2.2, specifically addresses computer software data rights. Therefore, the term “materials” includes computer databases and computer programs, as those terms are defined in DFARS 252.227-7014(a)(2)- (3); the term “software” means “computer software” as that term is defined in DFARS 252.227-(a)(4); the term “document” means “computer software documentation,” as that term is defined in DFARS 252.227-7014(a)(5); and the term “produced” means “developed,” as that term is defined in DFARS 252.227-7014(A)(7). As noted above, the Government does not intend to require the Contractor to sell or otherwise relinquish any rights in computer software developed exclusively at private expense , nor does the Government intend to prohibit or discourage Contractors from providing an EDIM Modem that includes computer software developed exclusively at private expense . If, however, the customization of a COTS solution results in the solution no longer falling within the definition of “commercial computer software,” as that term is defined in DFARS 252.227-2014(a)(1), the Government’s rights will be determined IAW DFARS 252.227-2014(b)(1) or (2), as appropriate.

Over-the-Air Upgrade Attachment 0002 Specification, Section 1.8, Page 79

Paragraph 1.8 states the EDIM Modem is software (SW) / firmware (FW) upgradable and open to additional capabilities. The SW/FW upgrade process will be simple, local and remote capable, and over-the-air capable, but it does not appear that there is a detailed specification for OTA software upgrades.

Sections 3.7.1 and 4.3.7 describe local and remote upgrades but do not describe over-the-air upgrades. What is the over-the-air upgrade requirement?

Refer to 3.7.1 item "f." referring to "secure in-band file download available through the LM and DM interfaces ..."

FAT Delivery Attachment 0003 Price Matrix, Base Year

The way we interpret the schedule and deliveries is that FAT hardware is delivered within the base year, and then tested for compliance in Option Year 1.

Does this mean delivery in place of FAT hardware at the end of the base year that should pass FAT without modification in option year 1? What is the acceptance criteria for the FAT Hardware during the Base period since testing will not take place until Option Year 1?

The Government anticipates that the Contractor will deliver the FAT Hardware (CLIN 0003) for FAT in accordance with PWS paragraph 4.1.b.

Classified Documents Attachment 0002 Specification, Section 3.2.5.1.6, Pages 23-24 Section 3.2.5.1.6 of the specification requires interference mitigation, and many test results for interference mitigation tend to be classified. If one would like to provide classified results substantiating performance, would the government consider allowing classified addendum submissions, or is the Governments intent to handle this post award?

No classified submissions are allowed in proposals.

Hyper-V Compatible VM Attahcment 0002 Specification, Section 3.3.2.1.1, Page 48 This section specifies that the EMMS software shall be operable on SHB platforms and virtual machines. Is it allowable to provide a Hyper-V compatible VM to meet this requirement?

Virtual machine platforms will be identified, and hypervisor system details will be provided during EDIM Modem System development after consultation with the Contractor.

ACI Validation Attachment 0002 Specification, Sections 4.3.2.2.5.8 - 4.3.2.5.5.9.2, Pages 102-103

ACI validation requirements do not define an upper bound to the number of test configurations. In contrast, interoperabilty / BER testing defines 150 test configurations. What is the number of ACI test conditions to be used for FAT schedule and cost planning? Can we assume that the maximum adjacent channel symbol rate is the EDIM maximum symbol rate (e.g. 200 Msym/s) so that the maximum COI symbol rate is 1/2 that (e.g. 100 Msym/s) for asymmetric cases?

A better precedent would be to consider ACI testing (Section 4.3.2.5.5.8) as an extension of BER testing (Section 4.3.2.5.5.7 and its subsections, as applicable). As to COI symbol rates exceeding 100 Msym/s, modems other than EDIM Modem can be used to generate carriers at twice the symbol rate. The alternative would be to apply a 200 Msym/s ceiling to interfering carriers for the sake of testing ACI WRT COI from 100 to 200 Msym/s.

Software Code Review Tools Attachment 0001 PWS, Section 7.2, In the PWS Section 7.2 it states "The Contractor shall incorporate the regular use of Software Code Review (SCR) tools, designated in PEO EIS Policy Memorandum #12-65 and its accompanying Standard Operating Procedures, into the EDIM Modem lifecycle." Can you provide the policy memorandum and accompanying tools list?

Yes, the document will be provided.

Software Code Review Tools Attachment 0001 PWS, Section 7.2, In the PWS Section 7.2 it states "The Contractor shall incorporate the regular use of Software Code Review (SCR) tools, designated in PEO EIS Policy Memorandum #12-65 and its accompanying Standard Operating Procedures, into the EDIM Modem lifecycle." Can the contractor utilize equivalent tools subject to approval by the Government?

Yes, but the Contractor would be required to provide the proper reports and/or source code to meet the requirements for code evaluation.

SHB Windows Server/Computers Attachment 0002 Specification, Section 3.4.8, Page 64 Section 3.4.8 of the System Specification requires EMMS installation and execution on SHB windows based server or computers. Will GFE SHB windows server and computers be provided upon contract award?

The need to provide SHB workstations as GFE will be evaluated during EDIM Modem System development after consultation with the Contractor.

UMGD/AGM Attachment 0001 PWS, Section 7.1, PWS Section 7.1 states the following "The Contractor shall implement the DoD Unified Master Gold Disk (UMGD), also referred to as the Army Golden Master (AGM), for all Microsoft Windows-based operating systems." Is the UMGD/AGM analogous or equivalent to the SHB referenced in Section 3.4.8 of the Specification?

Yes it is equivalent.

L-Band Modem Acquisition and Reacquisition

Time Requirements Attachment 0002 Specification, Section 3.2.5.5.4, Page 37 L-band modem (LM) acquisition and reacquisition time requirements are given by Table I in Section 3.2.5.5.4 on p.37. Do these requirements apply when bulk encryption (see 3.2.5.2.1.3 & 3.2.5.2.2.2.3) is enabled or disabled? Furthermore, do the requirements of Table I apply equally to EBEM and DVB-S2X waveforms?

Acquisition and reacquisition time requirements apply with bulk encryption enabled, in IF back-to-back configurations, and equally to EBEM and DVB-S2X waveforms.

Minimum Symbol Rate Attachment 0002 Specification, Section 3.2.5.6.1, Page 41 Section 3.2.5.6.1 and 3.2.5.6.2 specify 128ksym/s as the minimum symbol rate, should this be updated to 512 ksym/s IAW Section 3.2.5.1.4? Yes. An updated Attachment 0002 will be provided in Amendment 0002.

Test Features Attachment 0002 Specification, Section 3.2.5.9, Page 46

Section 3.2.5.9 of the specification says ' this subsection specifies test features common to all EBEM emulations supported by the EDIM modem.' We interpret this to mean 'all waveforms supported by the EDIM modem' to include DVB-S2X if offered. Is that correct?

Yes.

70 Security Classification Guide Attachment 0004 DD254 Does the Govt. plan to provide a Security Classification Guide for the program during the RFP solictation period? No.

EMMS Software Attachment 0001 PWS, Section I, Can the Government confirm that the EMMS Software is not considered part of CLIN 0003? EMMS Software is part of CLIN 0003.

GFE DVB-S2X Modems Attachment 0002 Specification, Section 3.2.5.2.2, Pages 27-28 Does the Govt. intend to provide GFE DVB-S2x modems for the purpose of interoperability and FAT testing? If so, what models and quantities may be provided?

No, the Government will not supply DVB-S2x modems.

"I am a little confused as to the process of this. is submitting a proposal for the EDIM proposal. In the requirements, it states we need to execute an NDA with MagAero as they may be “non-government advisors in the source selection process.”. Please advise as to what the process is from your end..."

The intent of the Government is for Offerors to send the required agreements to the addresses provided in Section L.5.4.3.4 of the RFP, and provide the executed agreements in Volume 4 of their Proposals. [NOTE: The agreement that Offerors are required to submit in Volume 4 is the agreement required by FAR 9.505-4(b)(i.e., an agreement stating that the Contractor providing non-government advisors for the EDIM source selection will protect the Offeror's proprietary informatio from unauthoirzed use or disclosure for as long as it remains proprietary and refrain from using the information for any other purpose other than that for which it was furnished). The agreements do not need to be more detailed that required to comply with FAR 9.505-4(b) or address issues not required by FAR 9.505-4(b). The NDAs referenced in Section L.5.4.3.4 are separate agreements between the Government and the non-government advisors who will be participating in the source selection. These NDAs do not satisfy the requirements of FAR 9.505-4(b), but are intended to further ensure that Offerors' proposals are not used or disclosed improperly.]

74 When do you plan to make a decision regarding the Proposal Extension and can we expect notification if the request is denied? Proposal Extension was issued in Amendment 0001.

Does Rock Island intend to post responses to industry questions about the RFP and if not, will RI make notification of the decision to decline to post responses?

Rock Island intends to post responses to questions in an amendment to the RFP.

In the event that Rock Island does not post responses, can you please share POCs for the contractors listed below assisting in evaluation, so we can request NDAs from them?

Rock Island intends to post response to questions. Addresses were provided in Section L.5.4.3.4. of the RFP. No other POC information will be provided.