The file's text, extracted by GovTribe without its formatting.
DARPA-SN-26-33 Unclassified
DARPA-SN-26-33
Drones -Attachment #1 Defense Advanced Research Projects Agency Tactical Technology Office Cover Page Data [Required]
| Topic Area |
| Variable |
| Response |
| Business Information |
| Response Title |
| Business Information |
| Company/Person Name |
| Business Information |
| Company Registered Address |
| Business Information |
| Company Point of Contact (POC) Name |
| Business Information |
| Company POC Email |
| Business Information |
| Company POC Phone |
| Business Information |
| Company Fax Number |
| Business Information |
| Response Classification Level |
| Business Information |
| Submission Date |
| Business Information |
| Company is a small business? |
| Yes or No |
| Business Information |
| Company meets the definition of a Nontraditional Defense Contractor per 10 US Code § 3014 |
| Yes or No |
Business Information Comment by Miller, Bethany (contr-tto): @Gingras, Michael (contr-sid) do you want to add the following as a possible question after this one on Facility Clearance?
“Company/Facility document safeguarding level (please provide)”
@Guptaa, Suneal (conr-tto) If Yes, this needs to bee added to Attachment #2 as well.
| Once completed please resolve | Comment by Gingras, Michael (contr-sid): @Miller, Bethany (contr-tto) @Guptaa, Suneal (conr-tto) Maybe, does "[list type if Yes]" asking for them to provide classification level? | Comment by Miller, Bethany (contr-tto): @Gingras, Michael (contr-sid) whatever you think is best. We can say, if Yes, list type | Comment by Gingras, Michael (contr-sid): @Miller, Bethany (contr-tto) OK, we're good then, that info is already in that block. |
| Company has a Facility Clearance? [list type if Yes] | | |
| Yes or No | | |
| Business Information |
| Company can design and build proposed platform? |
| Yes or No |
| Business Information |
| Commercial and Government entity (CAGE) Code |
| Business Information |
| Unique Entity Identifier (UEI) |
Required Data Table [Required]
| Topic Area |
| Variable |
| Example 1 |
| Example 2 |
| Units |
| Weight Statement |
| Gross takeoff weight |
lbs
| Weight Statement |
| Empty weight |
lbs
| Weight Statement |
| Fuel weight (i.e. power-source weight) |
lbs
| Weight Statement |
| Maximum payload weight (at full fuel/battery) |
lbs
| Performance |
| Endurance at full fuel/battery & maximum payload |
hours
| Performance |
| Operational ceiling at full fuel/payload |
ft MSL, std day
| Performance |
| Maximum flight speed at full fuel/payload |
ft/s
| Battery (if applicable) |
| Voltage & Power [cell/pack/system] |
Volts & Watts
| Battery (if applicable) |
| C Rating |
| Engine (if applicable) |
| Displacement |
cubic centimeters
| Engine (if applicable) |
| Sea level brake horsepower |
Watts
| Engine (if applicable) |
| Naturally aspirated? |
Yes or No
| SWaP-C |
| Maximum, continuous payload electrical power |
Watts
| SWaP-C |
| Length/width/height of flight-ready platform |
in x in x in
| SWaP-C |
| Unit cost (manufactured & assembled) |
$USD
| SWaP-C |
| Platform quantity cost basis (for unit cost above) |
| Constellation Management |
| Proposed constellation software (COTS or Custom, if Custom, describe below in Technical Description) |
Name
| Constellation Management |
| Maximum number of drones that can be managed by the constellation software |
| Constellation Management |
| Is path planning and deconfliction included? |
Yes or No
| Constellation Management |
| Is software fully functional or developmental? |
Estimated TRL
Graphic Overview [1 page, Optional]
Technical Description 1 [1 – 2 pages, Required]
Technical Description 2 [2nd Page, Optional]
References [1 page, Optional]