Attachment 1 Request for Information Worksheet.pdf
PDF 1018 KB Posted
- Attached to
- Space Test Experiment Platform (STEP) 2. 0 Industry Day Announcement - Amended Federal contract opportunity
- Solicitation number
- FA8818-22-R-0003
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| Industry Day Announcement Amendment 1.pdf | ||
| STEP 2.0 Industry Day Special Announcement (25-26 Oct 2022).pdf |
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 Experiment Platform 2.0 (STEP 2.0)
Attachment 1 – Request for Information Worksheet
Version 1.0 Space Systems Command
Acquisition Delta, Innovation and Prototyping DoD Space Test Program
(SSC/SZIS)
Kirtland Air Force Base Albuquerque, NM 87117
STP is seeking a flight system to include the Spacecraft (SC), Payload (PL) integration, SC testing, launch vehicle integration and 1 year of on-orbit operations and payload data distribution. The Government will use this RFI Worksheet for market research purposes for the STEP 2.0 acquisition to obtain a better understanding of the industrial base. A response to this RFI Worksheet will allow for schedule prioritization of one-on-one Government interactions with industry.
Respondents should complete this questionnaire based on a SC that would meet the STEP 2.0 requirements and submit this completed worksheet to the POC listed on the industry day announcement.
Respondent: Date:
Unique Entity Identifier:
SC Name /Model#:
1a
Do you have a SC with a form factor at or between the sizes of a 12U CubeSat and an ESPA Class SC?
Please identify the SC size(s).
Yes No
1b
Do you have a commercial item determination for the SC listed above.
If yes, please list identifier: Yes No
2a Has your SC successfully flown within the last five years?
Yes No
2b
How many different configurations of your SC have flown in the past five years?
Please identify the applicable mission(s).
1 2 3 4 5 or greater
3a Has your company previously independently performed Payload (PL) integration and testing? Yes No
3b Has your company previously integrated multiple PLs together onto your SC? Yes No
3c How many payloads has your company integrated on the SC?
4a Has the SC operated in LEO?
1 2 3 4 5 or greater
Yes No
Consider LEO as an orbit with an altitude ranging between 350-650 km and inclinations ranging between 0° and 180°.
Please identify the applicable mission(s) and orbit.
4b
Has the SC operated in a GEO environment?
Consider GEO is an Earth-centered orbit with an orbital period that matches Earth's rotation with a constant altitude of around 35,000 km
Please identify the applicable mission(s) and orbit. Yes No
5a
Has your SC flown successfully and transmitted payload data consecutively for at least 1 year without any major issues?
If No, are any currently on orbit working towards 1 year on orbit milestone? Yes No
5b
Please identify the applicable mission(s) and orbits.
6a
Did your company perform on-orbit operations with the SC used to answer the previous questions, to include operating this Space Vehicle (SV) and distributing Payload (PL) data for a minimum of 365 consecutive days with a 95 percent ground segment availability?
Yes No
6b
How was the PL data distributed to the end users?
Please specify.
6c Does your company have the capability to operate the SC and distribute payload data from your ground operations center? Yes No
Does your company own or have a contracted ground solution?
A proven ground segment solution consists of the ground station/system, operations facility, and communication network infrastructure providing command and control of a SC and distributing payload data to the customer(s) and PL(s).
If so, please specify.
Own: Contracted:
Ground Station name, location, spectrum used or contracted solution.
8a Do you have experience with the DoD Risk Management Framework (RMF) and cybersecurity requirements? Yes No
8b Is your SC (i.e., software) DoD RMF compliant? Yes No 8c Is your ground solution (i.e., hardware/software) DoD RMF compliant? Yes No
9a
Does your combined Ground and Space solutions currently operate on approved or recently expired FCC Licenses and/or NTIA Certifications?
If so, please provide Ground and Space “FCC Call Sign(s)" and/or "NTIA SPS #(s)" below for what is to be proposed on STEP 2.0:
and
Yes No
9b
Could STP use your existing frequency authorization as part of your potentially proposed ground solution?
If so, do you foresee any issues or risks related to STP usage? Yes No
10a Does your company have a cleared facility to support classified SC payload integration? Yes No
10b If yes, what is your company’s current facility clearance level?
Secret Top Secret Top Secret / SCI
10c Does your company have a current facility clearance to support classified ground operations? Yes No
10d If yes, what is your company’s current facility clearance level?
10e Does your company currently have a facility with classified networks? Yes No
10f If yes, what is your company’s current facility clearance level?
11a Does your company have a Communications Security (COMSEC) account? Yes No
11b If yes, what level?
CUI Secret Top Secret Top Secret / SCI
For STEP 2.0, STP is looking for a flight system to include the bus, PL integration, SC testing, launch vehicle integration and 1 years of SC Yes No
Secret Top Secret Top Secret / SCI
Secret Top Secret Top Secret / SCI operations and payload distribution. Would your company be able to provide such a solution for STEP 2.0?
Has your SC been successfully launched on a launch vehicle?
If so, please specify
Launch vehicle type and launch loads Yes No
Is there any additional information or comments you would like to provide?
If so, please do so here:
| Company Name: |
| UEI Number: |
| SC Name/Model: |
| SC Size: |
| Identifier: |
| 1a Yes: Off |
| 1a No: Off |
| 1b Yes: Off |
| 1b No: Off |
| Missions: |
| 2a Yes: Off |
| 2a No: Off |
| 3a Yes: Off |
| 3a No: Off |
| 4a Yes: Off |
| 2b 2: Off |
| 2b 3: Off |
| 2b 5: Off |
| 3c 0: Off |
| 3c 1: Off |
| 3c 2: Off |
| 3c 3: Off |
| 3c 4: Off |
| 3c 5: Off |
| 4b Mission and Orbit: |
| 4a Mission and Orbit: |
| 3b Yes: Off |
| 3b No: Off |
| 4b yes: Off |
| 4b no: Off |
| 5a yes: Off |
| 5a no: Off |
| 6a yes: Off |
| 6a no: Off |
| 6c yes: Off |
| 6c no: Off |
| 5a progress: |
| 5b Missions and Orbit: |
| 6b details: |
| 7 owned: Off |
| 7 contracted: Off |
| 7 name, location, spectrum, contracted: |
| 7 yes: Off |
| 7 no: Off |
| 8a yes: Off |
| 8a no: Off |
| 8b yes: Off |
| 8b no: Off |
| 8c yes: Off |
| 8c no: Off |
| 9a yes: Off |
| 9a no: Off |
| 9a NTIA SPS#: |
| 9a Call sign: |
| 9b Risk: |
| 9b yes: Off |
| 9b no: Off |
| 2b 0: Off |
| 2b 1: Off |
| 2b 4: Off |
| 10a yes: Off |
| 10a no: Off |
| 10b secret: Off |
| 10b top secret: Off |
| 10b TSSCI: Off |
| 10e yes: Off |
| 10e no: Off |
| 10d secret: Off |
| 10d top secret: Off |
| 10d TSSCI: Off |
| 10c yes: Off |
| 10c no: Off |
| 10f secret: Off |
| 10f top secret: Off |
| 10f TSSCI: Off |
| 11b cui: Off |
| 11b secret: Off |
| 11b TS: Off |
| 11b tssci: Off |
| 12 yes: Off |
| 12 no: Off |
| 11a yes: Off |
| 11a no: Off |
| 13 Type and load: |
| 13 yes: Off |
| 13 no: Off |
| 14 yes: Off |
| 14 no: Off |
| 14 fill in blank: |
| Date5_af_date: |
| 4a no: Off |
File details come from the government source that posted it. Updated .