Response to RFI Questions.docx

DOCX document 14 KB Posted

Attached to
SMC-32 Broad Agency Announcement (BAA): MILSATCOM Commercial Architecture Options
Solicitation number
SMC-32
Issued by

About this file

Responses to questions submitted regarding the RFI.

View the file

Other files

Show all 19

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

Questions and Answers

Below are questions that have been submitted regarding RFI SMC-32. The answers are in bold.

1) You mention other Governmental agencies, FFRDCs, and “SETA” contractors having access to the RFI responses; will they be required to sign Non-Disclosure Agreements? If any company wants a separate NDA executed it must be submitted to the POC listed on this site by 9:00 a.m. PST on 25 November 2009. If no separate NDAs are submitted, there will be no separate agreements and the existing agreement (if any) will apply.

2) Does this RFI intend to collect data on hosted payloads for mission areas outside MILSATCOM? No

3) Does DoD intend to allow COMSATCOM industry to act as System Integrator for each of the four response areas? These Options can be considered. This RFI is to inform a decision process to select a go forward Wideband strategy, not to select information for a pending RFP.

4) What operational scenarios and force structure would DoD like the COMSAT industry to use in determining threat and force loading? The purpose of this RFI is to outline the general context of threat/force loading contexts to facilite 1st order go forward capability decision considerations. Detailed consideration of the specific implementation could be the focus of a follow on study or Gov’t assessment.

5) In Response Area1:

a. “Acquisition of Modified Commercial Payload for Separate Hosting,” under the MILSATCOM features for consideration, Space Situational Awareness (SSA) and Space Protection (SP) are listed. SSA and SP are not inherent MILSATCOM features. Please provide additional clarity and context. Is this “feature” meant to be broader than MILSATCOM? Is the RFI collecting data at the payload level, system level, constellation level, or architecture level? What assumptions may respondents make about access to and performance of government capabilities, sensors, and architectures? No, this is not meant to be broader than MILSATCOM. The purpose of the RFI is to collect information about generalized available commercial SA/P capabilities. Military appliqués could be the focus of future consideration.

b. Is the term “commercial payload” meant to describe any payload purchased via FAR Part 12 or a payload the commercial industry routinely purchases to satisfy its normal business requirements (such as a Ku band transponder for a typical commercial communications satellite). Yes, both. We are attempting to understand the spectrum of what’s available for inform go forward decision. If the latter, we point out that many of the payloads that are candidates for hosting are not commercial payloads.

c. We do not understand the term “separate” hosting. Is this meant to imply the absence of coordination between payload and host at the time the payload is purchased, designed, and/or modified? It’s intended to indicate payloads purchased in ground at a time when the host platform is unknown and separately integrated based on need.

6) Is it the intent of the RFI to focus/limit responses to communications applications only and to exclude information regarding sensors and/or other types of payload Yes.

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