Loren Data's SAM Daily™

fbodaily.com
Home Today's SAM Search Archives Numbered Notes CBD Archives Subscribe
FBO DAILY ISSUE OF JUNE 29, 2011 FBO #3504
SPECIAL NOTICE

15 -- Request for Information - Vertical Takeoff and Landing (VTOL) UAS

Notice Date
6/27/2011
 
Notice Type
Special Notice
 
NAICS
336411 — Aircraft Manufacturing
 
Contracting Office
ACC-RSA - (Aviation), ATTN: AMSAM-AC, Building 5303, Martin Road, Redstone Arsenal, AL 35898-5280
 
ZIP Code
35898-5280
 
Solicitation Number
W58RGZ-RFI-VTOL
 
Archive Date
9/25/2011
 
Point of Contact
Steven Keiser, 256-842-1424
 
E-Mail Address
ACC-RSA - (Aviation)
(Steven.Keiser@us.army.mil)
 
Small Business Set-Aside
N/A
 
Description
Request for Information - Unmanned Aircraft Systems (UAS) Project Office (PO) Medium Range Multi-Purpose (MRMP) Vertical Takeoff and Landing (VTOL) UAS. Summary Important: This notice is not a Request for Proposals. The Government will not award a contract on the basis of this notice, or otherwise pay for information solicited by it. The functional capabilities contained within this RFI are intended to provide an overview of the Army MRMP VTOL UAS goals and objectives. Proprietary information should be clearly marked on the page containing the proprietary data and the Title page should be marked stating that the package contains proprietary data. The requested information is for planning and market research purposes only and will not be publicly released. This RFI is to support the Army development of the MRMP acquisition strategy and to inform the collaborative Army and Navy Medium Range Maritime UAS (MRMUAS) Analysis of Alternatives (AoA). The MRMUAS AoA will be a joint collaboration between the Navy and Army to specifically evaluate alternatives and determine what components, sub-components, or technologies could be cooperatively and jointly developed to reduce total ownership cost in the Department of Defense (DoD). Respondents to this RFI shall provide information for an Army VTOL solution only. The Navy in parallel to the Army will release an RFI for Navy VTOL solutions and the two Services will exchange information. The Army intends to move forward with the MRMP VTOL Technology Development phase in FY12 and deploy competitive systems in FY13. Deployments of the competitive systems will support down-select to a single vendor in FY14. Key Attributes PM UAS is seeking an MRMP VTOL UAS to leverage existing, proven technology solutions from industry that address the following areas: 1.Primary Intelligence, Surveillance and Reconnaissance (ISR) role and additional capabilities (i.e. resupply, weapons, high-levels of autonomy, teaming, safety, redundancy, maintainability, reliability, survivability, airworthy, security, deployability, etc.) 2.Operations in adverse weather conditions (rain, icing, high winds, temperature extremes) for all mission profiles 3.Interoperability and Net-Centric Operations 4.Compatibility with U.S Army Universal Ground Control Station (UGCS) 5.Training program for UAS Universal Operator and UAS Universal Maintainers 6.Modular, plug-and-play payload functionality capable of supporting a minimum of 3 payloads, excluding Electro-optical/Infrared (EO/IR), simultaneously with simplified integration. 7.System integrity consistent with safe operations over populated areas and in controlled airspace. 8.Affordability Response Requirements I.Responses must comprise an existing system, preferably that has been deployed by a U.S. Government organization within the Department of Defense. Customizations to your system are expected in order to meet unique PM UAS requirements. Include an assessment of your Technology Readiness Level (TRL) and production capability/status with respect to the system, sub-systems and capabilities you can provide. The draft MRMP VTOL OV-1 and descriptions of current UAS systems is provided for reference in Appendix B (see attachment). II.It is preferred that responses include two (2) customer references for similar system implementations, and each reference should reflect systems that have been implemented within the last three (3) years. U.S. Government customer references should include Point of Contact (POC) information for both the requiring element and the contracting officer. III.Responses on any or all efforts within the RFI will be considered. IV.Your response should be no more than forty five (45) typed pages, to include the cover. V.Your response may include an attached corporate capabilities brief. It is requested that you provide your response to the Contracting Office Address no later than 27 July 2011. IAW FAR 15.207(b), all information received in response to this RFI shall be safeguarded adequately from unauthorized disclosure. Note that your response may be reviewed by a support contractor employed by the Government under a signed non-disclosure agreement (NDA) with each support contractor. Respondents should establish NDAs with companies identified in Appendix C (see attachment) as soon as possible to support Government review of RFI responses. A copy of the established NDAs must be submitted with the RFI response. Responses may include data that the offeror does not want disclosed to the public for any purpose or used by the Government except for information purposes. If your company wishes to restrict the data, the title page must be marked with the following legend: Use and Disclosure of Data This response includes data that shall not be disclosed outside the Government and shall not be duplicated, used, or disclosed -- in whole or in part -- for any purpose other than to evaluate this response. This restriction does not limit the Government's right to use information contained in these data if it has been obtained from another source without restriction. The data subject to this restriction are contained in Sheets [insert numbers or other identification of sheets]. Your company may also mark each sheet of data it wishes to restrict with the following legend: "Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this response." Electronic Submission of Documents Your response may be submitted electronically to the Contracting Officer through a secure website. Please use the AMRDEC Safe Access File Exchange (SAFE) site at https://safe.amrdec.army.mil/SAFE2/ and submit your documents to steven.keiser@us.army.mil. These addresses are also contained in Appendix C. Functional Capability Requirements I.Standard Equipment Package (SEP) The Standard Equipment Package (SEP) establishes a baseline for airframe weight, space, and power. This requirement is considered basic UA weight, not mission payload weight. 1.Basic Equipment - The VTOL Unmanned Aircraft (UA) includes (1.) an EO/IR payload (150 lbs), (2.) four AN/ARC-231 Airborne Communications Systems, (3.) an AN/APX-118 -or- 123 Common Transponder, (4.) interchangeable SATCOM vs. Air Data Relay (ADR) system, (5.) taxi/situational awareness camera 2.Lighting - The VTOL UA includes Federal Aviation Administration (FAA) compliant navigation lighting (navigation, anti-collision, IR) 3.Hard-points - The VTOL UA will include at a minimum (1.) four non-centerline hard-points capable of supporting 500 lbs each (2.) a centerline hard-point capable of supporting 5000 lbs 4.Situational Awareness (SA) Field of Regard - SA Field of Regard of the cargo and cargo hook may be accomplished by (1.a) a combination of sensors -or- (1.b) through sensor fusion. The SA Field of Regard will have a visual field of regard from 0 degrees to -90 degrees from the horizontal, for the full 360 degrees around the horizontal, regardless of orientation of sensors or aircraft 5.Flight Data Recorder -The aircraft must incorporate a (1.) crash-survivable data recorder and (2.) continuously record the last 30 minutes of flight data. 6.Emergency Locator Transmitter (ELT) - The VTOL UA has an ELT that is (1.) manually configurable (on, off, impact) prior to UA launch and (2.) in-flight reconfigurable 7.Meteorological sensor - The VTOL UA will include a meteorological sensor capable of (1.) Wind Speed 2 knots, (2.) Wind Direction 20 mils, (3.) Temperature 1 degree Celsius, (4.) Barometric Pressure 1 Millibars, (5.) Relative Humidity 5 %, (6.) minimum update rate of 1 minute (7.) data formatted for other systems (METS, DCGS-A) 8.Automatic Dependent Surveillance - Broadcast (ADS-B) - The VTOL UA must include (1.a) ADS-B - Broadcast Out -or- (1.b) an Universal Access Transceiver (UAT), (2.) ADS-B - Broadcast In, (3.) compliance with Minimum Aviation System Performance Standard (MASPS) 9.Airworthiness Certification - The VTOL UA must be certified as airworthy when operated under Visual Flight Rules (VFR) and Instrument Flight Rules (IFR) in National, host country, and full range of military operations (ROMO) airspace in the conduct of operational and training missions II.Aircraft Performance The VTOL UAS will operate in austere environments. The aircraft will have ground mobility over rough terrain, transportability, and hard-points for munitions or cargo. The payload bay will have adjustable power and racks to accommodate multiple payloads with sufficient external fuselage common mounting points for reconfigurable antennas. The VTOL UA will use sustaining cruising speeds and endurance to perform reconnaissance and surveillance, multi-mission, staring and resupply missions while having standard equipment on board. 1.Mission Profiles - For each mission profile state the time-on-station (in hours) or travel distance (in kilometers) of the VTOL UA. Reconnaissance and Surveillance Profile (Primary Profile) - (1.) State the maximum time-on-station for a 300 pound internal payload (not including standard equipment), travel distance to target area of 300 kilometers (km) at 16,000 feet MSL and travel 300 km at 16,000 feet MSL back from target. Air vehicle is not required to hover (other than for takeoff and landing). Multi-Mission Profile - (2.) State maximum time-on-station for a 600 pound external payload (not including standard equipment), travel distance to target area of 300 km at 16,000 feet MSL and travel 300 km at 16,000 feet MSL back from target. Air vehicle is not required to hover (other than for takeoff and landing). Staring Mission Profile - (3.) State time-on-station for a 1000 pound external payload (not including standard equipment), travel distance to target area of 300 km at 16,000 feet MSL, and operate in a Hover Out of Ground Effect (HOGE) profile at target area at 10,000 feet MSL, and then travel 300 km at 16,000 feet MSL back from target area. Resupply Mission Profile - (4.) State maximum travel distance to target area with 1,500 pound resupply payload (sling load), release sling load and return from target area. State maximum travel distance to target area with 3,000 pound resupply payload (sling load), release sling load and return from target area. The UA must sustain a HOGE takeoff and landing flight profile. NOTE 1: At a minimum provide two data points for (1.) takeoff/landing at sea level on standard day and (2.) takeoff /landing at 95 F, 6000 feet pressure altitude (PA). Performance charts inclusive of these data points are preferred. See example provided in Appendix A. NOTE 2: All mission profile ranges require Line of Site (LOS) and Beyond Line of Site (BLOS) data links between the UA and the UGCS. NOTE 3: The basic aircraft (baseline) weight includes the SEP and no SEP components are included as part of the payload weight. 2.Confined, Unimproved Area Performance - Describe the capability of the VTOL UAS to operate from austere environments where prepared airstrips are impractical or non-existent. The description should include the takeoff/landing (1.) pad size, (2.) terrain, (3.) slope, (4.) obstacle clearance, (5.) unassisted start/restart, (6.) time (in minutes) to start-up and shut-down (7.) autonomy for start-up and shut-down 3.Vehicle Performance - Describe performance capabilities of the VTOL UAS for each of the four mission profiles. The description should include (1.) service and absolute ceiling, (2.) cruise speed, (3.) loiter speed, (4.) rate of climb and descent, (5.) HOGE, (6.) maximum and gross takeoff weight, (7.) V-n Diagram, (8.) minimum takeoff climb angle NOTE: At a minimum provide two data points for (1.) takeoff/landing at sea level on standard day and (2.) takeoff and landing at 95 F, 6000 Feet pressure altitude (PA). Performance charts inclusive of these data points are preferred. III.Autonomous Operations Autonomous takeoff /landing support for resupply, remote delivery, and recovery operations. Autonomous operation provides an opportunity to use limited skilled operators. 1.Autonomous Takeoff/Landing - Describe the autonomous capability of the VTOL UAS during takeoff, landing and recovery. The description should include autonomous ability to perform (1.) normal operations, (2.) termination in and out of ground effects, (3.) emergency recovery, (4.) autorotation, (5.) BLOS operations, (6.) precision landings, (7.) terrain and obstacle mapping, (8.) low level/terrain flight, (9.) manned and unmanned flight coupled landings. (10.) Describe the manual/pilot assisted capability of the same functions list above. 2.Autonomous Control - Describe the autonomous capability of the VTOL UAS while conducting various mission profiles. The description should include autonomous ability to perform (1.) mission planning (2.) manned-unmanned teaming, (3.) unmanned-unmanned teaming, (4.) formation flight, (5.) swarming, (6.) resupply, (7.) re-routing, (8.) keep-in-airspace (KIA) safe-air-volume (SAV) navigation, (9.) health monitoring, (10.) airspace de-confliction (cooperative), (11.) airspace de-confliction (non-cooperative). (12.) Describe the manual/pilot assisted capability of the same functions list above. 3.Lost Link Performance - In the event of loss of data link, the aircraft must execute a preplanned, user-programmable mission profile to facilitate restoration of the data link and minimize collateral damage if the link cannot be reestablished. Describe the lost link profile capability of the VTOL UA for (1.) automatic landing, (2.) zeroization of cryptographic variables, (3.) cooperative traffic avoidance, (4.) uncooperative traffic avoidance, (5.) obstacle avoidance, (6.) reporting on traffic and obstacles if link is reestablished 4.On-Board Control Element (OCE) - The VTOL UA must be capable of both teaming and autonomous combat operations. Describe OCE of the VTOL UA, include the ability to perform missions, tasks, or sub-tasks performed independently or with varying degrees of human control for (1.) levels of independent action, (2.) collaborative planning, (3.) information sharing, (4.) collaboration with manned aircraft, (5.) collaboration with unmanned aircraft, (6.) single operator control of unmanned teams, (7.) contingency re-planning of unmanned teams, (8.) dynamic task re-planning of unmanned teams, (9.) dynamic reallocation of resources for unmanned teams, (10.) dynamic mission re-planning of unmanned teams, (11.) collaborative teaming tasking and re-planning 5.On-Board Payload Automation - With advanced payloads and higher levels of automation the VTOL UA must utilize on-board processing of EO/IR and SAR/GMTI data for near real-time targeting. Describe the capabilities of the UA for (1.) detection, (2.) recognition (3.) identification of target, (4.) automated operator cueing, (5.) independent action. The description should include (a.) target size (i.e. tank, truck, car, human, etc.), (b.) detection probability, (c.) discrimination between live and decoy targets, (d.) virtual, spatial and temporal trip wires, (e.) open-ended or bounded trip wires, (f.) converging/diverging criteria, (g.) minimum and maximum detected speeds, (h.) automatic target cueing prioritization, (i.) automatic target retasking, (j.) false alarm rate adjustability NOTE: Autonomous operations imply that the aircraft is following programmed instructions without active input from the aircraft operator, but that the aircraft operator still has live visual and instrument feedback from the aircraft. This differs from "lost link" operations, where the aircraft still follows programmed instructions without active input from the aircraft operator, but the aircraft operator does not have live visual and instrument feedback from the aircraft. IV.Environmental The VTOL UA must have the capability to track/monitor targets in adverse weather conditions. It is envisioned that the VTOL UA must not require facilities (hangar, hard stand, etc) during field operations for 100% of LRU replacements and 95% of all field maintenance tasks. 1.Weatherization - State the capability of the VTOL UA to operate in near all-weather conditions for (1.) rain, (2.) icing, (3.) sand, (4.) dust, (5.) volcanic ash, (6.) lightning, (7.) temperature (high, low, solar loading, altitude, storage), (8.) visual and instrumented meteorological conditions 2.Wind - For the VTOL UA configured with a 1000 lb payload in high/hot (950F/6000' PA) takeoff/landing conditions state the maximum wind limits (in KIAS) of (1.) sustained winds in the forward quadrant, (2.) gusting winds in the forward quadrant, (3.) sustained tailwind, (4.) gusting tailwind, (5.) winds aloft for station keeping in the forward quadrant at 50 KIAS forward airspeed, (6.) winds aloft for station keeping in any direction at 50 KIAS forward airspeed V.Survivability The VTOL UA must be survivable to support battlefield operations in a medium threat environment. 1.Aircraft Design - State the minimum detection altitude (in feet AGL) for all flight profiles (hovering, turning, cruising) for (1.) unaided visual detection by a ground observer, (2.) IR detection by a ground observer, (3.) audibility by normal human hearing at a distance of one mile in (a.) urban terrain and (b.) open and rolling terrain 2.Electromagnetic Environmental Effects - (1.) Describe the capability of the VTOL UAS to be mutually compatible with other electric and electronic equipment within the electromagnetic environment in which the VTOL UAS is expected to operate 3.Directed Energy Weapons - (1.) Describe the ability of the VTOL UA to survive the effects of directed energy weapons 4.Chemical Weapons and Decontamination - Describe the (1.) hardening of the VTOL UA against chemical agent absorption, (2.) hardening of the VTOL UA against damage during decontamination, (3.) replacement or maintenance strategy for decontamination 5.Weapons Carriage - The VTOL UA incorporates DoD and NATO open standard electrical, logical, and mechanical interfaces as governed by PM UAS Weapons Interoperability Profile. State the Target Location Error (TLE) which supports the employment of (1.) coordinate seeking weapons and (2.) small diameter bombs 6.Cargo - (1.) Describe the ability of the VTOL UA to autonomously jettison cargo 7.Aircraft Survivability - (1.) Describe the ability of the VTOL UAS to utilize route planning, flight profiles, dynamic maneuver and threat avoidance if threat data is provided to the system VI.Fuel/Lubricants The VTOL UA will (1.) use fuel common to Army manned aviation (Jet-A, JP-8 and JP-5) (2.) be fueled from a single port and (3.) utilize standard MIL spec lubricants that can be acquired through the Army's supply system and are common to Army manned aviation systems, (4.) support anti-ice additives compatible with common fuels. 1.Fuel System - State the (1.) minimum and (2.) maximum fuel operating temperatures. Describe the (3.) hot refuel capability, (4.) refuel time (in minutes), (5.) defuel time (in minutes), (6.) fuel/defuel calibration requirements 2.Fuel Monitoring - For the VTOL UAS state the accuracy of (1.) the fuel burn rate (in percentage of actual burn rate), (2.) fuel quantity remaining (in minutes) 3.Ballistic Tolerance - (1.) State the ballistic tolerance of the VTOL UA fuel system VII.Operational Characteristics Operations on the Future Force battlefield will require the combatant commander to employ his forces across the full battlespace and may require dislocation to a new launch and recovery site. A robust takeoff and landing system will ensure operations into and out of remote locations. 1.Launch and Recovery - State the amount of time (in hours) to (1.) begin sustained flight operations after relocation or transit, (2.) cease flight operations and prepare for location or transit 2.Takeoff and Landing Systems - The VTOL UAS will have a redundant SAASM GPS system for non-precision landing and a precision landing capability. (1.) Describe the precision approach capability. State the offset in (feet) for the (2.) non-precision SAASM GPS approach and (3.) precision landing approach. State set-up time (in minutes) for the (4.) non-precision system and (5.) precision system. State the capability of the VTOL UAS to (6.) interoperate with Joint Precision Approach Landing System (JPALS), (7.) compatibility with civil Local Area Augmentation Systems (LAAS), (8.) Ground Based Augmentation Systems (GBAS) VIII.Datalinks VTOL UAS operations will require the ability to transmit telemetry and sensor data, provide control, re-transmit information through both Line of Sight (LOS) and Beyond Line of Sight (BLOS) data links. 1.Data Dissemination - Describe the capability of the VTOL UA to downlink all sensor data to STANAG and Interoperability compliant receiving systems through (1.) LOS datalinks, (2.) BLOS datalinks (3.) Simultaneous LOS / BLOS include the data rates and bit error rate of transmission 2.LOS Air Data Relay (ADR) - Describe the (1.) ability to transmit from one VTOL UA to another VTOL UA (2.) transmission range (in kilometers) UA to UA, (3.) transmission range (in kilometers) UA to GDT (4.) signal degradation 3.LOS/BLOS Data Links - The VTOL UAS will be configured for simultaneous LOS and BLOS datalink for UAS control. Describe the (1.) data rates, (2.) signal degradation, (3.) re-configurability, (4.) encryption methods, (5.) transmission of Full Motion Video (FMV), (6.) full control of the aircraft and all sensors, (7.) resupply/retransmit to other users 4.Priority Messages - (1.) Describe the method the VTOL UAS will use to support priority designated message traffic 5.Crypto Rekeying - (1.) Describe the method the VTOL UAS will use to support in-flight rekeying of all cryptographic variables for secure communications systems 6.Signal Security - (1.) Describe the capability of the VTOL UA to operate without RF signals in radio silent autonomous mode IX.Navigation VTOL UAS operations will require the capability to support navigation, flight and payload commands through a pre set and in-flight modified mission plan. 1.Instrumented Flight - Describe VTOL UA compliance with (1.) Technical Standard Order (TSO) C-129A, (2.) Advisory Circular AC90-96 for instrumented flight, (3.) International Civil Aviation Organization's Required Navigation Performance (RNP) standards, (4.) Eurocontrol Basic Area Navigation (BRNAV), (5.) FAA approved navigation database that meets the ARINC 424 Navigation System Data Base Standard X.Computer Resources VTOL UAS operations will necessitate software intensive system to provide enhanced system performance, maintainability, interoperability, portability, reliability, and user friendly operation. 1.Computer Software - Describe the computer software for the VTOL UAS (1.) open-system approach and structured programming language, (2.) modular development to promote rapid and low-risk system upgrades, (3.) reusability in training devices, (4.) maintenance and maintenance data collection methods, (5.) compliance with the Office of the Secretary of Defense (OSD) Memorandum "Policy Guidance for use of Mobile Code Technologies in DoD Information Systems" 2.Fault Tolerant Flight Software - (1.) Describe the capability of the flight control software onboard to VTOL UA to provide compensation in the event of component failure 3.Onboard Computing - Describe computer capability to process sensor data to perform Processing, Exploitation and Dissemination (PED) not associated with aircraft functions. 4.Interfaces - (1.) Describe the capability of the external/internal system interfaces to facilitate evolutionary growth through modular replacement of hardware and/or software 5.Flight Program/Software - (1.) Describe the method by which software updates and software loads will be loaded/verified by organic organizational maintenance 6.Health/Usage Monitoring Systems (HUMS) - Describe the method with which the VTOL UAS will utilize HUMS 7.Built-in Test - (1.) Describe the VTOL UAA BIT capability for isolating failures, to include aircraft communications systems, to the LRU level XI.Information Security All VTOL UAS equipment and interfaces must be certified for DoD secure operations and data transmissions. 1.Information Assurance - Describe the capability of the VTOL UAS certification for (1.) DoD Information Technology Security Certification & Accreditation Process Application Manual DoD 851031-M, (2.) DoDI 5200.40, (3.) DoD Information Technology Security Certification and Accreditation Process (DITSCAP) and the ability to transmit data through C2 and data links that are (4.) NSA Compliance, (5.) Defense Information Systems Agency (DISA) - certified, (6.) Cryptographic Modernization CRD Manual 009-04. 2.COMSEC - Describe the ability of the VTOL UAS to render un-useable or un-exploitable (1.) automatically, (2.) manually "special equipment" and electronically stored classified/sensitive material and to clear crypto keys onboard the VTOL UA during any phase operations 3.Zeroizing Mission Data - Describe the ability of the VTOL UAS to zeroize Controlled Cryptographic Items (CCI) (1.) IAW DoD Trusted Computer System Evaluation Criteria (DoD 5200.25-STD), (2.) IAW National Computer Security Center (NCSG)-TG-025, Version 2, (3.) if the UAS loses contact with the UGCS and is in immediate danger of crashing XII.Interoperability and Communication Standards All VTOL equipment and interfaces must be to the greatest degree possible interoperable with current and planned Service, USSOCOM, Joint and Allied reconnaissance systems and their existing C4I elements, both fixed and deployable to maximize battlefield effectiveness. 1.Interoperability and Net-centric Operations - (1.) Describe the ability of the VTOL UAS to satisfy the technical requirements for transition to Net-Centric military operations. 2.Common Operating Environment (COE) - (1.) Describe the ability of the VTOL UAS to be compliant with all layers of the Defense Information Infrastructure (DII) COE 3.Protocols - Describe the VTOL UAS compliance with (1) the Department of Defense Information Technology Standards and Profile Registry (DISR), (2) Army Interoperability Standards, (3) Joint Interoperability Standards, (4) Army Portfolio Management System (APMS) 4.Data Tagging - (1.) Describe the method the VTOL UAS will use to support semantic tagging of data 5.Link-16 - (1.) Describe interoperability of the VTOL UAS with Link-16 XIII.Logistics The logistics and supply support chain of the VTOL UAS must be compliant with Standard Army practices and resources to ensure maximum Operational Availability 1.Forward Deployable - (1.) Describe the manner in which the VTOL UAS will be operable and supportable from forward deployed locations 2.Footprint - (1.) Describe any Army non-standard tooling required and/or unique equipment that will affect the operational footprint of the VTOL UAS. 3.Deployability - State the time (in hours) in VTOL UAS can be deployed for (1.) inter-theater, and (2.) intra-theater movements. 4.Transportability - Describe the transportability of the VTOL UAS system by: self-deployment, sea, ground, rail, air, and sling-load for (1.) inter-theater and (2.) intra-theater movements. 5.Responsiveness - (1.) State the time (in hours) to achieve minimum operational capability after arrival of the VTOL UAS at a preplanned launch site XIV.Payload Space, Weight and Power (SWaP) 1.Weight - (1.) Describe the maximum payload capacity (in pounds) of the VTOL UA 2.Space - Describe the VTOL UA payload space available (in cubic inches) for (1.) internal payloads, (2.) external payloads 3.Power - Describe VTOL UA power (in Watts) available for payloads for (1.) continuous output, (2.) maximum output
 
Web Link
FBO.gov Permalink
(https://www.fbo.gov/notices/96e5641604e1c97afc38795deecf682f)
 
Record
SN02483486-W 20110629/110627235057-96e5641604e1c97afc38795deecf682f (fbodaily.com)
 
Source
FedBizOpps Link to This Notice
(may not be valid after Archive Date)

FSG Index  |  This Issue's Index  |  Today's FBO Daily Index Page |
ECGrid: EDI VAN Interconnect ECGridOS: EDI Web Services Interconnect API Government Data Publications CBDDisk Subscribers
 Privacy Policy  Jenny in Wanderland!  © 1994-2024, Loren Data Corp.