MODIFICATION
15 -- Small Tactical Unmanned Aircraft System/Tier II Unmanned Aircraft System (STUAS/TIER II UAS)
- Notice Date
- 12/14/2006
- Notice Type
- Modification
- NAICS
- 336411
— Aircraft Manufacturing
- Contracting Office
- Department of the Navy, Naval Air Systems Command, Naval Air Warfare Center Aircraft Division Pax River, Building 441 21983 Bundy Road Unit 7, Patuxent River, MD, 20670, UNITED STATES
- ZIP Code
- 00000
- Solicitation Number
- Reference-Number-STUAS112206
- Response Due
- 1/5/2007
- Archive Date
- 1/20/2007
- Point of Contact
- Kelly Chism, Contract Specialist, Phone 301-757-9735, Fax null,
- E-Mail Address
-
Kelly.Chism@navy.mil
- Description
- THE PURPOSE OF THIS NOTICE MODIFICATION IS TO PROVIDE QUESTIONS AND ANSWERS TO ALL INTERESTED RESPONDENTS. THE PREVIOUSLY RELEASED STUAS/TIER II SOURCES SOUGHT NOTIFICATION AND MODIFICATION REMAIN IN EFFECT. ***THESE QUESTIONS AND ANSWERS ARE SUPPLEMENTAL INFORMATION ONLY.*** Small Tactical Unmanned Aircraft System/Tier II Unmanned Aircraft System (STUAS/Tier II) Request for Information (RFI) Questions and Answers 12 December 2006 NAVAIR Public Release 06-0520 Distribution Statement A ? ?Approved for public release; distribution is unlimited? 1. The NAVAIR Interoperability Profile (NIOP) referenced is Version 11. Q 1a: This version specifies BR 10.71B as the standard return link waveform, but we believe this is being changed to BR 10.71A. Is BR 10.71A acceptable? A 1a: A new Joint Interoperability Profile for TCDL Systems will be available soon and will replace the requirement for the NAVAIR Interoperability Profile Version II. BR-10.71A will be required. Q 1b: Version 11 also requires a CDL BR 0.2 forward link. Provision of a standard CDL forward link for vehicle command and control is a cost and weight driver, if availability of a secondary radio is assumed. Can a waiver of compliance with the CDL forward link for the air vehicle be obtained? A 1b: A secondary radio should not be assumed. A "standard" uplink data rate of 200Kbps will be required by the new Joint Interoperability Profile for TCDL Systems. Q 1c: The RFI contains no reference to air traffic control communications. Are ATC comms from the UAV required for this system? A 1c: An Air Traffic Control (ATC) communication requirement should not be assumed. ATC communications will not be required for Increment 0 but may be required for Increment 1. THIS IS NOT A REQUEST FOR PROPOSAL. RESPONSES TO THIS RFI ARE NOT OFFERS AND CANNOT BE ACCEPTED BY THE GOVERNMENT TO FORM A BINDING CONTRACT. THIS RFI IS NOT TO BE CONSTRUED AS A COMMITMENT BY THE GOVERNMENT, NOR WILL THE GOVERNMENT PAY FOR ANY INFORMATION SOLICITED OR PROVIDED. Contractual questions or comments may be addressed to Mr. Michael McLoughlin at 301-757-5898, email Michael.mcloughlin@navy.mil. Technical questions or comments may be addressed in writing to Mr. Brad Johnson (email Bradley.johnson@navy.mil.) Point of Contact Michael McLoughlin, Contracting Officer, Phone 301-757-5898, Fax 301-757-5955, Email Michael.mcloughlin@navy.mil Kelly Chism, Contracting Specialist, Phone 301-757-5896, Fax 301-757-5955, Email Kelly.chism@navy.mil
- Place of Performance
- Address: TBD
- Zip Code: 00000
- Country: UNITED STATES
- Zip Code: 00000
- Record
- SN01196819-W 20061216/061214221140 (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 |