RFI_Affordable_Aerial_Relay_(2).pdf
PDF 333 KB Posted
- Attached to
- Affordable Aerial Relay RFI Federal contract opportunity
- Solicitation number
- 336413
View the file
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
Request for Information (RFI): Affordable Aerial Relay 1
Key Dates: 2
Release Date: 4 March 2014 3
Response Date: 10 March 2014 4
NAICS: 336413 5
Issued by: AFLCMC/HNAA, Mr. Andrew Geisel 6
Purpose 7
Solicit information from industry and academia regarding affordable and innovative means of providing 8 aerial communications relay to support Air Force missions. The Air Force would like to use this 9 information for market research purposes at this time. The Air Force’s intention is to gather additional 10 insight into communication payloads, potential platforms and integrated platform/communications 11 payload concepts. 12
This RFI should not be construed as a commitment by the Air Force to issue a solicitation or to ultimately 13 award a contract. Neither unsolicited proposals nor any other kinds of offers will be considered in 14 response to the RFI. This RFI is in no way binding to the government. The government will not pay for 15 any information submitted in response to this request. The information will be used to facilitate 16 acquisition planning; any proprietary information will be handled accordingly. The determination of an 17 acquisition strategy, based upon the comments submitted by interested parties in response to this RFI, 18 is solely within the discretion of the government. The NAICS Code 336413 (Airframe assemblies), is 19 subject to change based on market research and input from industry to the program office. 20
Background 21
The Air Force uses satellite communications for many of its missions. These beyond line of sight 22 networks support a variety of applications including voice, file transfer, text chat, and range extension of 23 tactical data links. Satellite communication systems are a limited resource and do not have the capacity 24 to support all of the warfighter’s information exchange needs. To exacerbate the issue, during times of 25 conflict, these communications could be degraded or denied. An alternate communications path 26 through the aerial layer would add resilience to these networks. 27
The Joint community has captured the requirements and been developing a complex system of systems 28 that will provide a robust and expansive communications infrastructure to support the warfighter across 29 the Range of Military Operations (ROMO). This infrastructure is known as the Joint Aerial Layer Network 30
(JALN). The JALN is based on dedicated aircraft providing the gateway between both surface and aerial 31 assets in lieu of satellite systems. The intent of this RFI is to examine the feasibility of augmenting the 32 dedicated communications gateway aircraft that carry communications payloads with a subset of the 33 required capabilities. 34
Mission Support 35
The Air Force is looking for the most effective means of accomplishing some or all of the following 36 mission tasks: 37
1. Ku SATCOM Surrogate: This capability supports ISR (U-2, RQ-4, MQ-9, MQ-1) sensor and control 38 data relay to a ground entry point. The typical operation will have an aircraft at 350 nautical 39 miles (nm) from the ground entry point. The aerial communications relay would provide 40 connectivity between the aircraft and the ground entry point. 41
2. Tactical Data Link Connectivity via Link 16 and SADL: This capability supports Command and 42
Control (C2) tactical information exchanges between two aircraft operating at 35kft and 200nm 43 apart. The gateway platform would provide Link 16 and SADL connectivity for the two aircraft 44 and support data translation between J-series messages and K-series. 45
3. Link 16 Range Extension. This capability supports the C2 mission by providing situational 46 awareness information to operational C2 nodes such as the Air Operations Center. The gateway 47 platform would receive Link 16 traffic from an aircraft at 35Kft and convert it to JREAP C. The 48 gateway platform would then relay the information via the Ku SATCOM surrogate capability to a 49 ground entry point up to 350 nm away. 50
4. UHF Voice and Data: C2 voice and data relay for dismounted airmen such as TACPs or SOF 51 tactical teams 100nm apart. The aerial communications relay would provide connectivity 52 between the two units of dismounted airmen 53
Communications Payload 54
The threshold communications payload would support one of the four mission support requirements 55 indicated above. The objective communications payload would support all of the mission support 56 requirements. The communication capabilities are provided in the following prioritized order: 57
1. KU SATCOM Surrogate 58
2. Link 16 59
3. SADL 60
4. Link 16/SADL Gateway 61
5. Link 16 JREAP C Gateway 62
6. UHF Voice and data 63
Objectives: 64
(T=O) The payload must be controlled remotely. 65
An example requirement would support relay of sensor data (45 Mbps, <5s delay, <1s jitter) 66 from ISR aircraft to GEP and control data (100 Kbps, <1s delay, <100ms jitter) bi-directionally 67 between ISR aircraft and GEP. 68
(T=O) No changes to existing deployed forces using Link 16, SADL, and UHF Voice or data. (This 69 does not apply to aerial layer relay platform and the GEP) 70
(O) Payload will be able to operate in accordance with MIL-STD- 810, Environmental Engineering 71
Platform 72
Objective requirements for the platform (or system of multiple platforms) would be to host all or 73 portions of the communication payload described above. The platform’s desired characteristics are: 74
1. (O) Remain at a known location (orbit) with a relatively high altitude (> 40,000 ft) for at least 24 75 hours 76
2. (O) Provide continuous multi-day coverage 77
Information Requested 78
The Program Office is interested in responses to some or all of the following questions: 79
Communications Payload Questions 80
1. Given the desired communication payload capabilities listed above, which elements can be 81 provided by your capabilities? 82
2. What are the size, weight, and power requirements of your communication payload? 83
3. What are the components that comprise your communication payload (processor, amplifier, 84 antennas etc.? 85
4. What are your payload’s non-operating and operating tolerances for temperature and pressure? 86
5. Has this communications payload been integrated onto any type of platform? 87
a. Provide platform name and date of start & completion 88
b. Provide test accomplishments (include associated government org) 89
c. Provide historical cost of integration/installation effort 90
i. Include breakout software, hardware B-kit, and A-kit efforts (A-Kit and B-kit 91 definitions provided in section 6) 92
6. Is your payload Non Developmental Item (NDI) or commercially available today? 93
a. How may it be procured? 94
i. If government product, please provide contract information 95
b. Provide price of payload as an end item 96
7. Is your payload currently in development? 97
a. At what stage of development is the hardware, software, and integrated payload? 98
b. Has it been independently reviewed for TRL (Technology Readiness Level) or MRL 99
(Manufacturing Readiness Level)? Provide TRL /MRL and organization name. 100
c. What environmental testing has the payload successfully completed? (i.e. temperature, 101 vibration, explosive atmosphere, decompression, altitude, acceleration, shock , crash 102 loading, humidity, fungus, salt fog, sand and dust, lightning, EMI/EMC). 103
d. What additional environments has the payload been analyzed for, which have not been 104 tested? 105
e. Has a durability and damage tolerance assessment been conducted? 106
f. What other testing has been accomplished? Has it been government witnessed? Provide 107 organization name 108
g. For all analysis/testing which has been conducted, identify whether it has been done at 109 the system level, or at the component level. 110
h. Can the government obtain copies of any test or analytical reports / documentation? 111
(All proprietary or distributions limits will be followed) 112
i. What standards were used in the design and selection of materials for the payload (such 113 as aerospace wiring standards and composite material characterization)? 114
j. Under what quality system was the payload designed and built? 115
k. What experience do you have with communications payload integration on airborne 116 platforms and airworthiness certification? 117
l. When is it expected to be production ready, what is the current schedule? 118
m. Provide a ROM cost of the payload as a first unit production end item 119
i. Include breakout of A (if applicable) & B kit, B-kit will include software) 120
n. Provide a ROM cost of the integration and installation of the first unit production 121 payload (please breakout B-kit and A-kit efforts) 122
8. Do you have any existing communication performance profile data (i.e. range vs capacity, 123 number of users, etc.) and can you provide copies to the government? 124
Platform Questions 125
1. What is the overall size, weight and power (SWaP) available for your platform for the integration 126 of a payload? 127
a. What is the remaining (or available) SWaP for your platform 128
b. How much power can your platform provide for various payload(s)? 129
c. What are the limitations to integration and installation of a payload? (Are there any 130 special requirements, like added test or certification for instance?) 131
d. Is there currently installed (or planned to be installed) equipment that can be jettisoned 132 to make additional SWaP available? Please identify roughly what SWaP would be 133 added. 134
2. Are there geographic limitations? Are there weather limitations? Provide platform test 135 accomplishments (include associated government organization or institution) 136
3. Do the systems exist today and what do you assess its maturity level to be? (Manufacturing 137 Readiness Level (MRL), Technology Readiness Level (TRL) or Commercial utilization)? 138
4. What are the bed-down or basing & ground equipment requirements? 139
a. Please include operations and maintenance needs 140
5. What experience do you have with obtaining Military and/or FAA airworthiness certification? 141
6. Does your platform or integrated platform/communications payload concept have airworthiness 142 approval? If so, identify the type of approval and approval authority (i.e., Military or FAA) and 143 identify any restrictions associated with the airworthiness certification. 144
7. What is the launch and recovery concept? Can it be launched from an aircraft or ship? 145
8. What is the performance profile/operational envelope? 146
a. Provide the maximum and minimum speed 147
b. Provide the maximum and minimum altitude 148
c. Provide the operating range (time and distance) at recommended operating altitude 149
9. What is the fuel source? Please explain. Does it currently have an in-air capability? 150
10. Has this platform carried any communications payloads in the past? 151
a. Provide payload name and date of start & completion 152
b. What type of mission did it support? 153
c. Provide test accomplishments and any reports (include associated government org) 154
d. Provide historical cost of integration/installation effort 155
i. Breakout software, payload hardware (B-kit), and platform efforts (A-kit)) 156
11. Is your platform NDI or commercially available today? 157
a. How may it be procured? 158
b. If government product, please provide contract information 159
c. Provide price of platform as an end item (breakout required ground equipment) 160
12. 161
13. Is your platform currently in development? 162
a. At what stage of development is the hardware, software, and integrated payload (if 163 applicable)? 164
b. Has it been independently reviewed for TRL or MRL? Provide TRL / MRL and 165 organization name. 166
c. What level of testing has been accomplished? Has it been government witnessed? 167 Provide organization name 168
d. Can the government obtain copies of any test reports / documentation? (All proprietary 169 or distributions limits will be followed) 170
e. When is it expected to be production ready, what is the current schedule? 171
f. Provide a ROM cost of the platform as a first unit production end item 172
g. Please include a breakout of ground equipment 173
h. Provide a ROM of the expected steady state operations and maintenance cost 174
i. Please include the expected manpower requirements for the platform 175
j. Provide the expected fixed and per flight hour costs? 176
Definitions 177
A-Kit: Consists of combinations of the item necessary to integrate a Payload Set(s) on to a platform. 178
Typically includes mounting trays/racks/brackets, antennas, platform specific co-site mitigation 179 devices/filters, interface devices, cables/wiring harnesses, and platform specific software external to the 180
Payload. 181
B-Kit: Consists of the payload and all interconnects. Typically interconnecting cables, cabinet support 182 brackets and peripherals that do not require platform modifications. 183
Capability Statement Requested 184
In addition to the request for responses on the above questions, we also request interested parties to 185 provide a Capability Statement. The Capability Statement should include the following elements: 186
1. Prospective Offeror Identification 187
a. Company Name and Commercial and Government Entity (CAGE) Code 188
b. Address 189
c. Phone Number 190
d. Fax Number 191
e. E-mail address 192
f. Point of Contact Information 193
g. A website address that provides additional information about the prospective business 194
h. The highest security clearance that your company currently holds. 195
i. Identify your company type as a large or small, small disadvantaged, 8a, veteran owned 196 small business, service disabled veteran owned small business, woman-owned small 197 business and/or HUB zone business. Include your company’s North American Industry 198
Classification System (NAICS) code. NOTE: This RFI is open to large and small 199 businesses. Small businesses are encouraged to respond. 200
2. In the event that the Government issues an RFP for this effort, identify your intent to submit a 202 proposal or describe your likely level of participation. 203
3. Provide a brief history of your business, and experience. 205
How to Submit a Response 206
1. Response to above questions (inclusive of Capability Statement) should not exceed 7 pages. 207
2. Please provide your response by 10 March 2014, to the following email address: 208 andrew.geisel@hanscom.af.mil 209
Inquiry 210
Technical inquiries about this Notice should be submitted to: 211 andrew.geisel@hanscom.af.mil 212
Other inquiries concerning this RFI may be directed to: 214 Andrew Geisel 216 Contracting Officer 217 Space, Aerial & Nuclear Networks Division 218 Hanscom AFB, MA 219 Phone: 781.225.2917 220
Email address: andrew.geisel@hanscom.af.mil 222
No basis for claims against the Program Office shall arise as a result of a response to this RFI, or from the 223
Program Office’s use of such information in refining its acquisition strategy or in developing any 224 subsequent policy or announcement. 225
This RFI is for planning purposes only and should not be construed as a solicitation for applications or an 226 obligation on the part of the government. The government will not pay for the preparation of any 227 information submitted or for the government’s use of that information. All information received in 228 response to this RFI marked “Proprietary” will be handled accordingly. In accordance with FAR 15.201, 229 mailto:andrew.geisel@hanscom.af.mil mailto:andrew.geisel@hanscom.af.mil responses to this notice are not offers and cannot be accepted by the Government to form a binding 230 contract. Responders are solely responsible for all expenses associated with responding to this RFI. 231
Responses to the RFI will not be returned. 232
File details come from the government source that posted it. Updated .