SPECIAL NOTICE
99 -- Radio Frequency (RF) Distribution Over Fiber Request for Information (RFI)
- Notice Date
- 3/28/2007
- Notice Type
- Special Notice
- Contracting Office
- US Army C-E LCMC Acquisition Center - DAAB07, ATTN: AMSEL-AC, Building 1208, Fort Monmouth, NJ 07703-5008
- ZIP Code
- 07703-5008
- Solicitation Number
- USA-SNOTE-070328-009
- Archive Date
- 6/26/2007
- Description
- NOTE: This Request for information was also to the IBOP, March 27, 2007. The link for the IBOP is http://abop.monmouth.army.mil/. It is strongly recommended to view the RFI on the IBOP easier reading. Updates, if any, to this RFI will be posted to the IBOP only. Radio Frequency (RF) Distribution Over Fiber Request for Information (RFI) March 23, 2007 INTRODUCTION: The US Army is requesting information to support a study of an optical based Radio Frequency Distribution (RFD) system to be used in an Intelligence, Surveillance, and Reconnaissance (ISR) aircraft. The goal is to reduce SWaP (Size, Weight and Power) by p erforming RF functions in the optical domain. This can be accomplished by replacing standard coaxial or waveguide cabling with fiber optic cables, switching with photonic based switching technology, and processing through the use of phase shifting and ampl itude control, filtering, and wavelength division multiplexing for routing of signals. Because SWaP bounds the capabilities that can be carried on an airborne system, the Army and the other services are very interested in any efforts to reduce SWaP in ord er to increase ISR capability. The Army will be assessing photonic technology in order to quantify performance, SWaP, technological maturity, risk, and Total Ownership Cost (TOC). The intent is to determine when this technology could be integrated onto an ISR platform, the benefits fro m such an implementation, and risks. This RFI is for the purpose of obtaining information only. The information will be used to assess the depth and range of contract firms with the requisite skills and performance to meet the requirements. No contract award or funding of any kind will occur as a result of this market survey. The lack of the submission of data at this time will not eliminate any firms participation in the future competition. Any submission to this RFI should address these specific TOC aspects; logistical support (reliability, sustainability, and maintainability) and Pre-Planned Product Improvement (P3I). SCOPE: The study of the optical based RFD will be completed in two phases. Phase I: Market Survey- The first phase will survey photonics technologies and fielded implementations. This will include an evaluation of innovative photonic technologies that improve performance and reduce SWAP in the entire RF system. However, the foc us will be on RFD components and systems. Phase II: Technology Demonstration- The second phase, if executed, will involve a demonstration of a scaled RFD to validate performance that consists of at least three functional elements, e.g. conversion, distribution, and switching. The validation will be by both a lab demonstration and a flight test on a test bed aircraft. The flight test validation is to serve two purposes, validate technology readiness level (TRL) and provide a comparison between a conventional RFD and one in the optical domain. NOT E: The Definitions of Technology Readiness Levels in the Department of Defense (DOD) can be found at the end of this document. The RFD for the ISR platform connects a large number of antennas distributed over an aircraft to several processing nodes within the aircraft. The RFD covers a wide frequency range from HF to millimeter wave frequencies. The frequency bands may be divided into sub-bands to meet performance objectives for dynamic range. The sub-bands and apertures must be individually switched to the individual processing nodes. Each processing node must have non-blocking access to any allowable antenna/sub-band simultaneo usly. In addition, a single antenna/sub-band can be connected to multiple allowable processing nodes simultaneously. Requirements: The following subset of system capabilities and requirements will be used to demonstrate the proposers ability to meet the overall system requirements. 1. RFD: Referring to the table, a hypothetical spectrum of interes t is divided into four frequency bands that are further broken down to accommodate requirements changes in-band. Within each band, the proposed RFD solution is required to switch and distribute 5 RF feeds (5 inputs and 5 output ports) simultaneously, incl uding a single feed serving multiple subsystems. Where the RFD system requires subdivision of the bands into sub-bands to meet performance requirements, the performance effects of filters should be included, and switching capabilities should be scaled to ensure that all sub-bands have connection to all processing sub-systems. The minimum input power is assumed to be -95 dBm and each of the output should experience no losses (gain of 10-20 dB is desirable). Submissions should include any gain and noise fi gures where applicable. Band Frequency Band (MHz) Processing Nodes 1 MHz Bandwidth (Switching) Dynamic Range (dB) SFDR (dB) HF 3-30 5 108 81 VHF /UHF 30-500 5 110 81 500-3000 110 80 UHF/ SHF 500-3000 5 110 80 3000-10000 104 76 SHF / EHF 500-3000 5 110 80 3000-10000 104 76 10000-20000 101 74 20000-30000 94 70 It is expected that the architecture will generally follow these guidelines: " System should be designed to facilitate maintenance and allow for upgrading. As such, equipment located in a centralized location is favored over distributed equipment. Any necessary equipment located at the antennas should be designed to maximize the ease of maintenance and upgrading. " Responders may show a partial solution/sub unit of the RFD system such as a single frequency band RFD, a RF-photonic link, an optical switching net-work, etc., however, the information should indicate what other parts (preferably COTS components) are nee ded in order to complete the whole RFD. " Innovative solutions to improve performance/SWAP should include: o For the RF-photonic link, include enough detail such as methods of RF-to-optical conversion and detection (intensity modulation or phase modulation/coherent detection; external modulation or direct modulation); laser, modulator and detector performances to indicate what SFDR and link gain can be achieved. o For the switching network, include enough detail such as method of switching (i.e. WDM or electro-optic); method of splitting; and RF-Photonic link requirement for the net-work. Indicating loss, cross-talk, switching speed, etc. o Packaging schemes to reduce size (footprint) and complexity such as multi-level modules that integrate: optical, microwave, electro-optic and antennas at millimeter wave frequencies; integration of multiple optical functions on the same chip or circuit t o reduce cost and improve reliability o Optical cable type and connectors type o Overall SWaP estimates. 2. Other innovative photonic technologies: The following photonic technologies that improve performance and significantly reduce SWaP in the entire RF system of an airborne ISR platform if the TRL is above 3. " Optical control of phased array antenna o Beam-forming/steering o Optical true-time-delay generator " RF-Optical signal processing o Filtering o Channelizing " RF-Photonic radar receiver Environmental: Environmental requirements are as called out in RTCA DO-160. Aircraft is expected to fly at up to 40,000 ft. RFI Format Paper should not exceed 10 pages, with Font Size 11, in PDF format; Excel format for SWaP (Size Weight and Power) analysis should have locked cells for protection of proprietary simulations. For SWaP data, government should be allowed to change or update parameters on all spreadsheet data. The papers will be categorized into system, sub-system and components. System papers should present an overall solution of the entire RFD. Sub-systems papers should show a significant system function. Components papers should show innovative components that can address fiber optic links, processing or switching. Government contractors should be allowe d to evaluate white paper and / or technology (NRO contract). Government and their consultants may request site visits to observe technology demonstrations. 0. Executive summary (one page) 1. Introduction: 1.1. Paper category: system, sub-system component 1.2. Company background 1.3. Technology Capability 1.4. Listing of companys recently awarded government contracts: Title, date awarded, government entity 2. Technical Description of Approach 3. Performance & SWaP Data (paper must stress Size Weight and Power savings with documentation, i.e., spreadsheets) 4. Environmental, shock and vibration data. 5. Maturity Assessment " Current " 5 Year projection 6. Risk mitigation plan to have technology ready by 2011. 7. Include plan for funding maturity/development (internal, commercial, government contract, etc.) Questions should be directed to the point of contact regarding this RFI: Mr. Marc Busala at email address: Marc.Busala@us.army.mil. Subject line must state RF Over Fiber. Submissions are due by May 14, 2007. Unclassified RFI responses must be submitted via compact disc (CD). The CD must be labeled with RF Over Fiber. Unclassified CD must be submitted to Mr. Marc Busala at the following address: US Army RDECOM, CERDEC, I2WD Building 600 Attn: AMSRD-CER-IW-SA Fort Monmouth NJ 07703-5211 Classified information will be accepted, but please mark it accordingly. RFI responses at the Secret/Collateral level must be submitted to Mr. Marc Busala (annotated on inner wrapper) at the following address: US Army RDECOM, CERDEC, I2WD Building 600 Attn: AMSRD-CER-IW-OPO (Security) Fort Monmouth NJ 07703-5211 For responses at a higher level of classification, please contact Mr. Busala for submittal instructions. Your participation in this RFI is appreciated. Reference: Technology Readiness Levels in the Department of Defense (DOD) (Source: DOD (2004), DODI 5000.2 Acquisition System Guidebook) Technology Readiness Level Description 1. Basic principles observed and reported Lowest level of technology readiness. Scientific research begins to be translated into applied research and development. Example might include paper studies of a technology's basic properties. 2. Technology concept and/or application formulated Invention begins. Once basic principles are observed, practical applications can be invented. The application is speculative and there is no proof or detailed analysis to support the assumption. Examples are still limited to paper studies. 3. Analytical and experimental critical function and/or characteristic proof of concept Active research and development is initiated. This includes analytical studies and laboratory studies to physically validate analytical predictions of separate elements of the technology. Examples include components that are not yet integrated or represent ative. 4. Component and/or breadboard validation in laboratory environment Basic technological components are integrated to establish that the pieces will work together. This is relatively Alow fidelity compared to the eventual system. Examples include integration of 'ad hoc' hardware in a laboratory. 5. Component and/or breadboard validation in relevant environment Fidelity of breadboard technology increases significantly. The basic technological components are integrated with reasonably realistic supporting elements so that the technology can be tested in a simulated environment. Examples include 'high fidelity' lab oratory integration of components. 6. System/subsystem model or prototype demonstration in a relevant environment Representative model or prototype system, which is well beyond the breadboard tested for TRL 5, is tested in a relevant environment. Represents a major step up in a technology's demonstrated readiness. Examples include testing a prototype in a high fidelit y laboratory environment or in simulated operational environment. 7. System prototype demonstration in an oper ational environment Prototype near or at planned operational system. Represents a major step up from TRL 6, requiring the demonstration of an actual system prototype in an operational environment, such as in an aircraft, vehicle or space. Examples include testing the prototyp e in a test bed aircraft. 8. Actual system completed and 'flight qualified' through test and demonstration Technology has been proven to work in its final form and under expected conditions. In almost all cases, this TRL represents the end of true system development. Examples include developmental test and evaluation of the system in its intended weapon system to determine if it meets design specifications. 9. Actual system 'flight proven' through successful mission operations Actual application of the technology in its final form and under mission conditions, such as those encountered in operational test and evaluation. In almost all cases, this is the end of the last 'bug fixing' aspects of true system development. Examples in clude using the system under operational mission conditions. Technology Readiness Levels in the Department of Defense (DOD) (Source: DOD (2004), DODI 5000.2 Acquisition System Guidebook) Technology Readiness Level Description 1. Basic principles observed and reported Lowest level of technology readiness. Scientific research begins to be translated into applied research and development. Example might include paper studies of a technology's basic properties. 2. Technology concept and/or application formulated Invention begins. Once basic principles are observed, practical applications can be invented. The application is speculative and there is no proof or detailed analysis to support the assumption. Examples are still limited to paper studies. 3. Analytical and experimental critical function and/or characteristic proof of concept Active research and development is initiated. This includes analytical studies and laboratory studies to physically validate analytical predictions of separate elements of the technology. Examples include components that are not yet integrated or representative. 4. Component and/or breadboard validation in laboratory environment Basic technological components are integrated to establish that the pieces will work together. This is relatively 'low fidelity' compared to the eventual system. Examples include integrati on of 'ad hoc' hardware in a laboratory. 5. Component and/or breadboard validation in relevant environment Fidelity of breadboard technology increases significantly. The basic technological components are integrated with reasonably realistic supporting elements so that the technology can be teste d in a simulated environment. Examples include 'high fidelity' laboratory integration of components. 6. System/subsystem model or prototype demonstration in a relevant environment Representative model or prototype system, which is well beyond the breadboard tested for TRL 5, is tested in a relevant environment. Represents a major step up in a technology's demonstrated readiness. Examples include testing a prototype in a high fidelity laboratory environment or in simulated operational environment. 7. System prototype demonstration in an operational environment Prototype near or at planned operational system. Represents a major step up from TRL 6, requiring the demonstration of an actual system prototype in an operational environment, such as in an a ircraft, vehicle or space. Examples include testing the prototype in a test bed aircraft. 8. Actual system completed and 'flight qualified' through test and demonstration Technology has been proven to work in its final form and under expected conditions. In almost all cases, this TRL represents the end of true system development. Examples inclu de developmental test and evaluation of the system in its intended weapon system to determine if it meets design specifications. 9. Actual system 'flight proven' through successful mission operations Actual a pplication of the technology in its final form and under mission conditions, such as those encountered in operational test and evaluation. In almost all cases, this is the end of the last 'bug fixing' aspects of true system development. Examples include us ing the system under operational mission conditions.
- Web Link
-
RF Over Fiber
(http://www1.fbo.gov/spg/USA/USAMC/DAAB07/USA%2DSNOTE%2D070328%2D009/Marc.Busala@us.army.mil)
- Record
- SN01261224-W 20070330/070328221246 (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 |