SOURCES SOUGHT
15 -- Request for Information (RFI) For United States Navy Small Tactical Unmanned Air Systems (STUAS), (PMA-263)
- Notice Date
- 12/28/2015
- Notice Type
- Sources Sought
- NAICS
- 336411
— Aircraft Manufacturing
- Contracting Office
- Department of the Navy, Naval Air Systems Command, NAVAIR HQ, Building 2272, 47123 Buse Road Unit IPT, Patuxent River, Maryland, 20670, United States
- ZIP Code
- 20670
- Solicitation Number
- N00019-16-NORFP-PMA-263-0069
- Archive Date
- 2/12/2016
- Point of Contact
- Denise R Lamb, Phone: 301-757-5902
- E-Mail Address
-
denise.lamb@navy.mil
(denise.lamb@navy.mil)
- Small Business Set-Aside
- N/A
- Description
- 1.0 Introduction This Request for Information (RFI) is in accordance with the Federal Acquisition Regulation (FAR) 15.2, and is published to obtain market research for use by the Naval Air Systems Command (NAVAIRSYSCOM), Program Executive Office, Unmanned Aviation and Strike Weapons (PEO(U&W), Navy and Marine Corps Small Tactical Unmanned Aircraft Systems Program Office (PMA-263), Patuxent River, Maryland. NAVAIRSYSCOM intends to issue Basic Ordering Agreements (BOA) to provide PMA-263 with Small Tactical Unmanned Aircraft System (STUAS) systems in accordance with the requirements contained herein. A BOA is a written instrument of understanding, negotiated between an agency, contracting activity, or contracting office and a contractor that contains: (1) terms and clauses applying to future contracts (orders) between the parties during its term, (2) a description, as specific as practicable, of supplies or services to be provided, and (3) methods for pricing, issuing, and delivering future orders under the BOA. A BOA is not a contract. Delivery/Task Orders issued under BOAs are the binding contractual actions, and each order issued shall be subject to the contract clauses, provisions, certifications, terms, and conditions of the BOA. Issuance of BOA's will be based on evaluation of qualifications in accordance with the criteria as set forth in this notice. Award of specific orders as requirements arise will be based on price/cost and other factors as deemed desirable and set forth for each specific requirement. The Government reserves the right to set-aside future BOA orders for small businesses contractors when practicable. In the event more than 1 BOA is issued, specific firm-fixed priced orders will be competed among the BOA holders. Individual orders will not be synopsized unless it is determined by the Contracting Officer that the requirements of FAR Part 5 have not been met by this notice for a specific order, or otherwise determines that synopsis of the requirement is in the best interest of the Government. The Government does not intend to pay for the information solicited. No entitlement to payment of direct or indirect costs or charges by the Government will arise as a result of preparing submissions in response to this RFI and the Government's use of such information. The Government will not reimburse respondents for any costs associated with the preparation or submission of the information requested. Submittals will not be returned to the sender. Respondents of this RFI may be requested to provide additional information/details based on their initial submittals. Contractors that demonstrate that they meet the qualifications in paragraph 3.0 will be considered for issuance of a BOA. The Government reserves the right not to issue a BOA. BOAs will be issued for a period of 3 years. There is no guaranteed minimum dollar amount or volume of work that will be ordered under the BOAs. Government funds are obligated only to the extent that a duly issued order creates such an obligation. The BOA can only be changed by modification of the agreement itself and not by individual orders issued under the BOA. Modification of the BOA shall not retroactively affect orders issued prior to the time of the modification. A BOA may be cancelled by either party by mailing or otherwise transmitting 30 days prior written notice to the other party. Any such cancellation shall have no effect on any orders issued prior to the effective date of the cancellation, which shall be 30 days from the date of mailing or otherwise transmitting the written notice of cancellation. Prior to the effective date of cancellation, NAVAIR may continue to place orders under the BOA. 2. OBJECTIVE PEO (U&W), PMA-263 is seeking industry inputs to identify Small Tactical Unmanned Aircraft System (STUAS) systems capable of providing Intelligence, Surveillance and Reconnaissance (ISR) in day and night operations, and in adverse environmental conditions. The systems are intended to build needed Foreign Partner capacity in accordance with Defense Security Cooperation Agency guidelines. These systems may build partner capacity in countries with differing levels of access to protected U. S. technologies. To this end, Section 4.0 asks respondents to identify the full range (minimum to maximum) of capability within configuration management control for technical attributes such as air vehicle performance, sensor performance, ground station performance, system architecture, communication link design, operating software, and any associated payload capability. 3.0 REQUIREMENTS ("STUAS" or "the system" refers to the air vehicles and the ground system, to include the control segment, support equipment, launch and recovery equipment, and any ancillary equipment required to accomplish the mission.) System capabilities must be complete and qualified through test and demonstration. A system must be proven to work in its final form and under the expected operational conditions. The desired STUAS should be of lightweight design (Group 2 or low-end Group 3) and shall have the capability of providing real time full motion video via electro-optical (EO) and infrared (IR) sensors for maritime and land based operations with minimal setup and quick (1 to 2 hour) disassembly capabilities. Systems should be capable of reaching high altitudes to avoid detection or enemy intervention for transit to and from the operating area, with a normal operating altitude in the operations area of 3,000 - 5000 feet AGL. The air vehicle should be capable of autonomous or manual launch and recovery with minimal to no required modifications in a small confined area and hot or cold terrain conditions. It must be runway independent. The system configuration should be designed for quick (24 Hour) deployment, long range missions (minimum 10-12 hours flight time), quick turn-around times between day & night operations. The minimal air vehicle performance attributes are listed in Table 1. The ground control station should be easily deployable and have the necessary equipment to monitor UAS sensor(s) position and status, control its movement and have the capacity to view video surveillance in real time. The system should be reusable and rugged enough to survive adverse weather conditions, unimproved areas, uneven terrain, urban areas, forested areas and salt water (maritime) conditions. Required minimum system capabilities are listed below. Table 1 Minimum Air Vehicle Performance Specifications Airspeed Minimum 50 KTAS [1] Service Ceiling [2] Minimum 15,000 Feet MSL [3] Takeoff / Recovery Wind Limits Maximum Headwind 30 Knots Crosswind 10 Knots Maximum Gust 15 Knots Takeoff, Operations, and Recovery Temperature Range -20 to +140F 95 % Relative Humidity Density Altitude 6000 Feet for Takeoff and Recovery Rainfall Maximum 0. 2 5 Inches/Hour Takeoff / Recovery Area 100 x 100 Meter Area Surrounded by Obstacles up to 15 Feet Tall, Sloping up to 4 Degrees, with Surface Obstacles/Depressions Throughout, up to 1 Foot Depth/Height E n d u r a n c e Threshold: 10 Hours of Continuous Sensor Data Objective: 18 Hours of Continuous Sensor Data [1] 50 KTAS - 50 Knots of True Airspeed - Minimum airspeed necessary to meet the requirement to fly to the 50 Nautical Mile maximum radius of GCS within one hour after launch. [2] Service-ceiling is the altitude at which the AV's vertical rate of climb performance is equal to 100 feet/minute. [3] MSL - Mean Sea Level Other minimum system requirements are: The system must be runway-independent. The system must provide near-real time EO/IR full motion video (FMV) to the ground site. Minimum range for FMV and command-and-control (C2) of the vehicle is 50 nm (LOS only) at an altitude of 3000 feet AGL. All transmitters must have approved DD1494s. The system must use at a minimum a Mode 3/C transponder, and have an AIMS certification traceable through Spectrum approval in addition to a DD1494. If the system uses GPS, the GPS must not be SAASM-enabled. If the system uses lithium batteries (larger than coin sized), it must have a current NOSSA Lithium Battery certification. The system must have existing operational and maintenance technical publications or manuals, and be capable of organic repair and overhaul. The system must have an established Field Service Representative Program (trained operations and maintenance field representatives), able to perform Outside the Continental United States (OCONUS). The STUAS must be a U.S. domestic end product, in accordance with DFARS 225.75. 4.0 REQUESTED INFORMATION / SYPNOSIS The respondent is requested to provide detailed information in response to the questions listed below. Company Profile/Status: 1. What is your experience and maturity with manufacturing and developing Small Unmanned Aircraft System products ? 2. Please provide your cage code, NAICS code and business category of your company? (i.e. Small Business, 8(a) Small Disadvantaged Business, etc.) ? 3. What is the Technology Readiness Level (TRL) of the STUAS as described in the DoD Technology Readiness Assessment handbook? 4. Are you currently on one or more GSA schedules? If so, which one(s)? 5. Did you receive funding to develop your STUAS from a governmental agency? STUAS Operating Parameters/Configuration: 1. Describe the configuration of the entire STUAS (air vehicles, ground control stations, support equipment, payloads, system architecture, communication link design and capabilities to include any encryption scheme, navigation capabilities, operating software, and repair capabilities). What are the dimensions of the air vehicle? What type engines are used? What types of fuels does the air vehicle use/operate on? What is the current weight of the air vehicle (empty and operating weight)? What is the maximum airspeed, operating altitude, range and endurance of the air vehicle? 2. Describe how the STUAS satisfies the minimum requirements stated in Section 3.0. 3. How many launches and recoveries, and total flight hours for this configuration? 4. Provide data supporting that the STUAS has been tested in a relevant operational environment, to include day and night video if available. 5. If the STUAS has conducted field user evaluations for the U. S. Government, provide applicable (unclassified) details as to what was demonstrated, any changes since the demonstration as relevant to this RFI, and a U. S. Government Point of Contact. 6. List all the hardware required to prepare the air vehicle for operation. 7. List all required equipment needed to operate the STUAS. 8. How is the Air Vehicle launched and recovered? 9. What are the current payloads of the air vehicle? What are the performance attributes of the sensors, for both day and night? What is the available EO/IR focal plane array size(s) in pixels along major axis? What is the stability for the available turret(s) in micro-radians? What is the maximum ground speed detected in knots, if your system provides Ground Moving Target Indicator capability? 10. What are the different types of flight modes and mission control characteristics used by the STUAS? (fly waypoints, loiter, hover and stare, etc.) 11. How does the ground control station communicate with the air vehicle? Describe the data link used including waveform, operational frequency band, analog or digital, and encryption capabilities. What is the data link range at different operating altitudes? 12. Describe the STUAS's repair/overhaul capability. 13. What type of warranty is provided for the STUAS? 14. What is the production lead-time, including any production/delivery constraints based on single order quantities ranging from one to 25 STUAS's? 15. How many cubic feet of space is required to store the STUAS when not in use and how is the system stored when not in use/operation? 16. How many people are required to operate the STUAS? 17. How many people are required to maintain the STUAS at the organization level? 18. Is the STUAS capable of simultaneous air vehicle operations? If so, please describe. 19. Describe the assembly required to ready the air vehicle for operation from its field packed state. A field packed system is defined as having all the required equipment to accomplish a mission and be in a state safe to be transported. How long does it take to go from a field packed system to air vehicle launch? 20. What software operating system does the STUAS use? Was the software developed and coded in the U. S.? Does the operating software interface with DoD software and DoD mapping imagery software or does it require company proprietary software to operate the system? 21. How does the STUAS download and store data through your ground control station and for how long? 22. Is the STUAS controlled under the International Traffic in Arms Regulations (ITAR)? 23. Do you have an export configuration? Describe the Export Configuration. 24. Has Critical Program Information (CPI) or Critical Technology (as defined in the DoD 5200.39) that requires anti-tamper protection and/or low observable requirements been identified for the STUAS? (Unclassified responses only) Training and Field Support: 1. Describe any other ancillary equipment that is not included as part of the system configuration, such as calibration equipment. 2. Describe the existing operational and maintenance publications or manuals. 3. Provide the STUAS's sparing requirements based on 3,600 flight-hours per year. 4. Describe the STUAS's facility and infrastructure requirements at a fielded site. 5. Describe CONUS and OCONUS field support on the STUAS while deployed to include harsh or hostile environments overseas. 6. Describe the existing training curriculum (course type classes, devices, duration, training location and any certification requirement timelines). 7. Provide any other system features that the STUAS has that are unique and stand out from other system platforms. 5.0 RESPONSES All responsible sources are encouraged to submit a capability statement in response to this announcement to be evaluated for issuance of a BOA. All interested sources that wish to respond to this RFI, please respond with a capability statement via email no later than 30 days after release date on FEDBIZOPS. It is the responder's responsibility to monitor this site for the release of any follow-on information. Responses should be submitted electronically via email to the POC in paragraph 6.0. Responses should reference FedBizOpps reference# N00019-16-NORFP-PMA-263-0069. The response shall contain the responder's name, street address, cage code, point of contact with phone number and email address and the responder's web page URL. It is suggested that responses be approximately 15 pages in length, 12 point font, not including preprinted information material. In order to maximize efficiency and minimize the effort involved in the evaluation process, all submissions must comply with the following instructions format and content. The electronic capability statement shall be prepared so that if an evaluator prints the capability statement it meets the following format requirements: 8.5 x 11 inch paper; single-spaced typed lines; newspaper column formatting is not permitted; 1 inch margins on all sides; not smaller than a 12 point font without condensing; photographs, pictures or hyperlinks are not permitted; files shall be Microsoft Office 2010 compatible; no ZIP files, no fold-out pages; PDF files are permitted; all file names shall include title of the evaluation criteria. All material provided in response to this RFI shall be unclassified, non-confidential, and non-proprietary to the maximum extent practicable. Responses to this RFI will not be returned. If the response includes proprietary information, (1) ensure proprietary information is marked appropriately, (2) identify disposition instructions, and (3) indicate whether you require Government support contractors providing advisory and assistance services to the Government to facilitate the execution of information/proprietary exchange agreements with you. The Government will NOT be responsible for the disclosure of any confidential/proprietary information not clearly marked. At any time after receipt of RFI responses, the Government may contact respondents independently for further clarification of the submittal.
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/spg/DON/NAVAIR/N00019/N00019-16-NORFP-PMA-263-0069/listing.html)
- Record
- SN03978615-W 20151230/151228233958-bd18f8167db2d938525f40bba19d2a47 (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 |