ATTACHMENT 12 Gateway Questionnaire_Response Form v2.pdf
PDF 515 KB Posted
- Attached to
- RFP - Space Test Experiments Platform (STEP) 2. 0 Federal contract opportunity
- Solicitation number
- FA880924RB001
- Issued by
- Department of the Air Force
About this file
This document is the STEP 2.0 IDIQ Attachment 12 Gateway Questionnaire Response Form associated with the STEP 2.0 RFP solicitation FA880924RB001. It outlines requirements for offerors to provide details on their proposed spacecraft solutions, including form factor, flight heritage, on-orbit operations, and licensing. Offerors must complete this questionnaire for each spacecraft solution they intend to propose. The government will evaluate the responses against the Gateway Questionnaire Evaluation Criteria to assess the offeror's spacecraft capabilities. The STEP 2.0 program establishes a multiple-award IDIQ contract to procure proven spacecraft and space access for science and technology experiments. The anticipated period of performance is a 5-year base period with one 5-year option period. The government anticipates awarding firm-fixed price contracts for each spacecraft solution.
View the file
Other files for this federal contract opportunity
Show all 27
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Acquisition Delta, Innovation and Prototyping Space Test Program (STP)
Space Test Experiments Platform 2.0 (STEP 2.0)
Attachment 12 Gateway Questionnaire
FA8809-24-R-B001
Version 1 Space Systems Command
Acquisition Delta, Innovation and Prototyping DoD Space Test Program
(SSC/SZIS)
Kirtland Air Force Base
Albuquerque, NM 87117
STEP 2.0 IDIQ
Attachment 12 Gateway Question Response Form FA8809-24-R-B001
Acquisition Delta, Innovation and Prototyping Space Test Program (STP)
Space Test Experiment Platform 2.0 (STEP 2.0)
SUBMITTED BY:
Date Signed
DAVID J. LORE, Maj, USSF Program Manager, STEP 2.0
APPROVED BY:
Date Signed
BRIAN A. SHIMEK, Lt Colonel, USSF Director, DoD Space Test Program
Change History
Version Effective Date Prepared by Changes 06 MAY 2024 Maj LORE, DoD STP Document Creation 1. 1.0
Offerors shall complete the following questionnaire for each Spacecraft (SC) solution they intend to propose in response to the STEP 2.0 Request for Proposal (RFP). If an Offeror has flown a spacecraft at both Low Earth Orbit (LEO) and geosynchronous orbit (GEO), the Offeror shall submit a Gateway Questionnaire for each altitude. All questions must be answered based on the SC solution to be proposed, unless otherwise specified. The Government will use the Prior Customer Questionnaire to substantiate claims on the Gateway Questionnaire. The Government will evaluate the Gateway Questionnaire in accordance with Gateway Questionnaire Evaluation Criteria, Section M.2.1.1.2. An applicable mission is defined as a prior work effort by the Offeror to provide a SC that operated within its destined orbit to include the distribution of Payload (PL) data.
Terminology:
SC refers to the SC bus with no PLs. A PL is the space-borne hardware and software components of an experiment (e.g., instruments, booms, and antennas) supplied as Government Furnished Property (GFP) from STP or reimbursable customers. The PL suite is the combination of all PLs on the mission. The SV is the SC integrated with the PL suite. Prime Contractor refers to the company in charge of overseeing the completion from start to finish. Subcontractor refers to a company who performs part or all of the obligations of another company’s contract. When submitting classified information, please refer to L.41.a for further instructions.
Offeror: Date:
Unique Entity Identifier or Cage Code:
SC Name:
(A) (B) (C)
Does the SC have a form factor at or between the sizes of a 6U CubeSat and the maximum Multi-Manifest Design Specification (MMDS) Rev 1.0a1 Class 2 SC mass and volume?
Please identify the form factor of your company’s proposed spacecraft. Select one box and provide a brief description of the SC, mass, in kg, and dimensions, in cm.
CubeSat ☐ MMDS Class 1 SC ☐ Other ☐ MMDS Class 2 SC☐
X dimensions
(cm)
Y dimensions
(cm)
Z dimensions
(cm)
Mass (kg)
Description (50 words maximum):
Yes
No
Has the SC identified in response to Question 1 had any significant system modifications or changes since last the last flight that established the flight heritage?
Significant changes are any Class 1 configuration changes to include form, fit, function and software changes that affect an item’s specifications, weight, interchangeability, interfacing, reliability, safety, schedule, cost, etc.
If yes, please identify any Class 1 changes made to the SC design since the last flight and succinctly describe the verification or the plan for verification of those changes.
Narrative (100 words maximum):
Yes
No
1 The Multi-Manifest Design Specification Rev 1.0a is available from the Small Payload Ride Share Association at https://www.sprsa.org/mmds-project/mmds-ver-10a https://www.sprsa.org/mmds-project/mmds-ver-10a
Did the SC identified in response to Question 1 perform on-orbit PL operations including PL commanding and distribution of PL data to the PL operation centers consecutively for 1 year or more?
Please identify applicable missions.
Narrative (100 words maximum):
If not, please describe the duration the SC successfully operated and transmitted payload data and the cause that resulted in a duration of less than 365 days. Narrative (100 words maximum):
Yes
No
Does your SC that you are referencing for your flight proven heritage requirement have a current or recently expired (within the last five years) Federal Communications Commission (FCC) License for your company’s to be proposed SC?
If yes, please provide the SC’s “FCC License” or equivalent document. (15 words maximum):
Mission name:
FCC License:
OR
Identify your procedure or process used for Spectrum Licensing. (100 words maximum)
Yes
No
Is your company a United States (US) entity, a US subsidiary of a foreign entity, or a foreign entity? If teaming, please identify the roles and responsibilities for each entity on the team and include whether each entity is a US Subsidiary or Foreign Entity in the narrative below.
Narrative (50 words maximum):
US Entity
US
Subsidiary
Foreign Entity
5-1
If an entity on your team or your company is a US subsidiary of a foreign entity, does your company have integration and testing facilities within the US including all engineering and technical support personnel necessary being US citizens?
Please provide your company’s Department of State / Directorate of Defense Trade Controls registration number, if applicable.
Yes
No
N/A
5-2
If an entity on your team or your company is a US subsidiary of a foreign entity, will interactions with the US Government furnished hosted payload(s) on your spacecraft require one or more export authorizations, such as a Technical Assistant Agreement (TAA), with your company to support Interface Control Document (ICD) development, integration, and testing?
Yes
No
N/A
5-3
If an entity on your team or your company is a US subsidiary of a foreign entity, will interactions with a US launch organization require one or more export authorizations, such as a TAA, between the launch organization and your company to support ICD development, integration, and testing?
Yes
No
N/A
Has the SC been produced, integrated with PL(s), and operated on-orbit for a minimum of 365 days, with a launch date within the last five years?
Date range of Period of Performance (MM/DD/YY) From:__________ To:____________
Yes
No
Q6-1. Table 1
If Question 6 was answered “Yes,” please complete the tables on the following pages provided for each applicable mission (minimum of 1 mission and maximum of 3 missions). The first mission listed must be for the proposed SC. If the SV was developed as the result of teaming, please identify the roles and responsibilities of each entity on the team in the narrative for each mission.
Mission Name:
Date of Contract: Period of Performance (including options) (MM/DD/YY):
From: To:
Total Days on Orbit: LEO/MEO/GEO/Other:
Launch Date: Post Launch Acceptance Review / Nominal Operations Readiness Review (NORR) Date:
Orbit Parameters: Inclination:
Perigee: Apogee:
The Offeror demonstrated the following contractor responsibilities for spacecraft development*, which included the following:
During the contract performance being verified, the Offeror was the:
Prime Contractor
Subcontractor
Spacecraft manufacturer Conducted SV Integration and Test (I&T) Conducted space vehicle to launch vehicle I&T support Conducted pre-launch operations support and launch support Conducted on-orbit space vehicle checkout Mission Operator
*Development implies design, fabrication, assembly and testing
Narrative (100 words maximum):
Question 6-1, Continued. Table 2.
The contractor demonstrated the following contractor responsibilities for spacecraft development*, which included the following:
During the contract performance being verified, this firm was the:
Prime Contractor
Subcontractor
Spacecraft manufacturer Conducted SV Integration and Test (I&T) Conducted space vehicle to launch vehicle I&T support Conducted pre-launch operations support and launch Support Conducted on-orbit space vehicle checkout Mission Operator
*Development implies design, fabrication, assembly and testing
Narrative (100 words maximum):
Mission Name:
Date of Contract: Period of Performance (including options) (MM/DD/YY):
From: To:
Total Days on Orbit: LEO/MEO/GEO/Other:
Launch Date: Post Launch Acceptance Review / Nominal Operations Readiness Review (NORR) Date:
Orbit Parameters: Inclination:
Perigee: Apogee:
Question 6-1, Continued. Table 3.
The contractor demonstrated the following contractor responsibilities for spacecraft development*, which included the following:
During the contract performance being verified, this firm was the:
Prime Contractor
Subcontractor
Spacecraft manufacturer Conducted SV Integration and Test (I&T) Conducted space vehicle to launch vehicle I&T support Conducted pre-launch operations support and launch support Conducted on-orbit space vehicle checkout Mission Operator
*Development implies design, fabrication, assembly and testing
Narrative (100 words maximum):
Mission Name:
Date of Contract: Period of Performance (including options) (MM/DD/YY):
From: To:
Total Days on Orbit: LEO/MEO/GEO/Other:
Launch Date: Post Launch Acceptance Review / Nominal Operations Readiness Review (NORR) Date:
Orbit Parameters: Inclination:
Perigee: Apogee:
| Offeror Click or tap here to enter text: | |
| Unique Entity Identifier or Cage Code Click or tap here to enter text: | |
| SC Name Click or tap here to enter text: | |
| Enter date here: | |
| Check Box 3: Off | |
| Check Box2: Off | |
| Check Box 4: Off | |
| Check Box 5: Off | |
| X dimensions cm: | |
| Y dimensions cm: | |
| Z dimensions cmRow1: | |
| Mass kg: | |
| Click here to insert description: | |
| Yes: Off | |
| Click here to enter a narrative: | |
| Mission name: | |
| FCC License: | |
| US Entity: Off | |
| US Sub: Off | |
| Foreign: Off | |
| Click here to add narrative: | |
| Orbit Parameters click or tap here to enter text: | |
| Yes1: Off | |
| No2: Off | |
| Yes3: Off | |
| No4: Off | |
| Yes5: Off | |
| Yes6: Off | |
| No8: Off | |
| Click here to enter narrative1: | |
| Click here to enter narrative2: | |
| Click here to add narrative6: | |
| Yes7: Off | |
| No9: Off | |
| N/A4: Off | |
| Click here to add text1: | |
| Click to add text here100: | |
| Click to add text here94: | |
| From12: | |
| To13: | |
| Yes14: Off | |
| No17: Off | |
| N/A18: Off | |
| Yes19: Off | |
| No20: Off | |
| N/A23: Off | |
| Yes25: Off | |
| No26: Off | |
| Mission Name Click or tap here to enter text30: | |
| Date of Contract Click or tap here to enter text32: | |
| LEOMEOGEOOther Click or tap here to enter text34: | |
| Launch Date Click or tap here to enter text35: | |
| Inclination Click or tap here to enter text36: | |
| Perigee Click or tap here to enter text37: | |
| Apogee Click or tap here to enter text38: | |
| From41: | |
| To42: | |
| Check Box1743: Off | |
| Check Box1744: Off | |
| Check Box1745: Off | |
| Check Box1746: Off | |
| Check Box1747: Off | |
| Check Box1748: Off | |
| Check Box1749: Off | |
| Check Box1750: Off | |
| Check Box1751: Off | |
| Check Box1752: Off | |
| Check Box1753: Off | |
| Check Box1754: Off | |
| Days on Orbit click to add text55: | |
| click to add text59: | |
| Click here to add text60: | |
| Mission Name Click or tap here to enter text 61: | |
| Date of Contract Click or tap here to enter text 62: | |
| LEOMEOGEOOther Click or tap here to enter text 64: | |
| Click or tap here to enter text66: | |
| Inclination Click or tap here to enter text68: | |
| Apogee Click or tap here to enter text69: | |
| Perigee Click or tap here to enter text70: | |
| Orbit Parameters click or tap here to enter text72: | |
| From75: | |
| To76: | |
| Check Box1777: Off | |
| Check Box1778: Off | |
| Check Box1779: Off | |
| Check Box1780: Off | |
| Check Box1781: Off | |
| Check Box1782: Off | |
| Check Box1783: Off | |
| Check Box1784: Off | |
| Check Box1785: Off | |
| Check Box1786: Off | |
| Check Box1787: Off | |
| Check Box1788: Off | |
| click to add text89: | |
| Click here to add text91: | |
| Orbit Parameters click or tap here to enter text94: | |
| Mission Name Click or tap here to enter text130: | |
| Date of Contract Click or tap here to enter text131: | |
| LEOMEOGEOOther Click or tap here to enter text132: | |
| Inclination Click or tap here to enter text133: | |
| Perigee Click or tap here to enter text134: | |
| Apogee Click or tap here to enter text135: | |
| Click or tap here to enter text136: | |
| Orbit Parameters click or tap here to enter text137: | |
| From138: | |
| To139: | |
| click to add text141: | |
| Click here to add text142: | |
| Check Box17143: Off | |
| Check Box17144: Off | |
| Check Box17145: Off | |
| Check Box17146: Off | |
| Check Box17147: Off | |
| Check Box17148: Off | |
| Check Box17149: Off | |
| Check Box17150: Off | |
| Check Box17151: Off | |
| Check Box17152: Off | |
| Check Box17153: Off | |
| Check Box17154: Off | |
| Date1_af_date: 6/10/24 | |
| Date2_af_date: 6/11/24 | |
| 2024-06-10T11:40:48-0600 | |
| LORE.DAVID.JAMES.1395819158 |
| 2024-06-11T10:55:13-0600 | |
| SHIMEK.BRIAN.ANDREW.1252700109 |
File details come from the government source that posted it. Updated .