Remote Readout Unit

1.0 - DESCRIPTION 1.1 - The United States Special Operations Command, Technology Applications Contracting Office (TAKO) is seeking information on potential sources concerning a Remote Readout Unit (RRU) which will satisfy the integration, interface, and processing requirements as detailed below. 2.0 - REQUIREMENTS: 2.1 - General information and coverage. The equipment will be of the manufacturer's current design, new and unused, and capable of performing its intended function in accordance with the operation and performance requirements specified herein. The equipment shall be completed so that when integrated, it can be used for any function for which it is designed and constructed. 2.2 - Production model. As an objective, components of the system shall be non-developmental items. 2.3 - Definition. The system shall consist of, but is not limited to, the following major components: 2.3.1 - One RRU meeting the display and mounting dimension characteristics below. 2.4 - Characteristics. Desired equipment capabilities and characteristics are below. Due to severe weight and space limitation, paramount/vital to this platform includes maintaining the weight of avionics equipment to a minimum and identifying equipment with dimensions that will fit within the limited space available. 2.4.1 - Power: 28VDC. Capability to meet MIL-STD Aircraft Electrical Power Characteristics (reference MIL-STD-704F) or currently qualified (desired)? 2.4.2 - Capability to meet MIL-STD Environmental and Electromagnetic Compatibility requirements (reference MIL-STD-810G and MIL-STD-461F) or currently qualified (desired). 2.4.3 - Military standard (MIL-DTL-38999 or similar) connectors. 2.4.4 - Display and bezel key assembly height and width when mounted no greater than 3.5" and 5.75", respectively. 2.4.5 - Weight no greater than 3 pounds. 2.4.6 - Capability to display at a minimum 10 alphanumeric characters. Display systems capable of displaying greater amounts of data will also be considered provided all other requirements have been met. Objective capability is the display of 5 lines of 20 characters or more. 2.4.7 - Display Night Vision Goggle (NVG) compatible. 2.4.8 - Day/Night mode controllable from external sources. Display luminance control will allow connection to a central master aircraft dimming source. It is desired that the RRU retain light level settings once power is lost. 2.4.9 - All bezel key controls (I.E. General purpose, mode, brightness control keys) are Night Vision Imaging System (NVIS) compatible lighted (controllable). 3.0 - RECOMMENDED RESPONSES: 3.1 - Respondent's responses to this announcement shall include the following information and address the following questions: 3.1.1 - Respondent's name, address, point of contact (POC), phone number, and e-mail address. 3.1.2 - Business size. 3.1.3 - No more than four pages providing clarification/explanation of the component(s) to include historical usage, if any. This portion of the response should clarify how the component meets all the above requirements. Note: Specific parameters and data of interest include: 3.1.3.1 - Dimensions including overall, display, mounting 3.1.3.2 - Weight 3.1.3.3 - Power, power consumption, and qualifications 3.1.3.4 - Environmental and EMI/EMC qualifications, specifying environmental conditions that the proposed product has been shown to be in compliance as well as conditions for which the product has either not been tested for compliance or is not compliant. If qualified, identify the cognizant engineering authority. 3.1.3.5 - Mean Time Between Failure (MTBF). 3.1.3.6 - Data and/or video input type (I.E. RS-422, RS-232, ARINC-429, Ethernet 10/100, RS-170, SMPTE) and quantity of each 3.1.3.7 - Viewing angle 3.1.3.8 - Viewable/Usable screen size (as applicable) 3.1.3.9 - Resolution (as applicable) 3.1.3.10 - NVIS compatibility - provide level and reference specification (I.E. MIL-STD-3009) 3.1.3.11 - Specular reflection (I.E. <1% per MIL-L-85762A) (as applicable) 3.1.3.12 - Chromaticity (as applicable) 3.1.3.13 - Luminance (as applicable) 3.1.3.14 - Luminance/Day/Night control ability 3.1.3.15 - Backlight technology, including region control capability (as applicable) 3.1.3.16 - Bezel key functions and NVIS compatibility (as applicable) 3.1.3.17 - Support of ARINC 661 (as applicable) 3.1.3.18 - Future Airborne Capability Environment (FACE) compatible (as applicable) 3.1.3.19 - Current availability 3.1.3.20 - Production rates 3.1.3.21 - Obsolescence planning 3.1.3.22 - Performance discriminators from other competitors 3.1.4 - Technical specification and supporting information for solutions meeting the performance requirements. 3.1.5 - Interface Control Documents (ICDs) available for review. 3.1.6 - Mechanical and Electrical drawings available for review. 3.1.7 - Any associated Technical Standard Order(s) (TSOs), Supplemental Type Certificate(s) (STCs) or other flight releases from cognizant aeronautical engineering design authority (e.g. Department of Defense (DoD), Federal Aviation Administration (FAA), European Aviation Safety Agency (EASA)). 3.1.8 - Test reports from executed flight test efforts. 3.1.9 - Artifacts providing evidence of DO-178B compliance, and environmental and electromagnetic compatibility MIL-STD qualification. 3.1.10 - Have you sold these products to any government agencies, or non-government, commercial sources? If so, please provide names of agencies, POCs and contract numbers. 3.1.11 - Recommended criteria towards technical capability assessment. 3.2 - Proprietary information, if any, should be minimized and MUST BE CLEARLY MARKED. To aid the Government, please segregate proprietary information. Please be advised that all submissions will not be returned. 3.3 -The Government intends to utilize personnel from Cruz Associates, Inc., Yorktown, Virginia, and Yahwehs Computers, Inc., Williamsburg, Virginia to provide technical advice and support in review of submitted information. By submitting a response to this RFI, the Contractor consents to the Government disclosing Contractor proprietary information to the aforementioned contractors to develop the acquisition approach. Each of these support contracts have the Defense Federal Acquisition Regulation Supplement (DFARS) clause 252.227-7025, Limitations on the Use or Disclosure of Government-Furnished Information Marked with Restrictive Legends, in the contracts with the Government and employees of these companies have individual non-disclosure statements on file with the company. 4.0 - INFORMATION EXCHANGE MEETINGS: 4.1 - The Government does not intend to host an information exchange meeting to discuss this RFI with interested potential respondents. 5.0 - CONTACT: 5.1 - This Request for Information (RFI) is issued solely for information and planning purposes only and does not constitute a solicitation. All information received in response to this RFI that is marked Proprietary will be handled accordingly. Responses to the RFI will not be returned. In accordance with FAR 15.201(e), responses to this notice are not offers and cannot be accepted by the Government to form a binding contract. Responders are solely responsible for all expenses associated with responding to this RFI. 5.2 - All interested, capable, and responsible sources that wish to respond to this RFI are asked to provide input to Mr. Anthony Ciccariello, Contract Specialist via email at anthony.ciccariello1.civ@mail.mil no later than 30 days from the date of this RFI, 22-Jan-2014. 12:00 pm EST. may be forwarded to the Contract Specialist by e-mail. Contracting Office Address: ATTN: AMSAM-TASO-K Lee Boulevard, Building 401 Fort Eustis, VA 23604-5577 Primary Point of Contact: Mr. Anthony Ciccariello anthony.ciccariello1.civ@mail.mil 757-878-0730 x247