Loren Data's SAM Daily™

fbodaily.com
Home Today's SAM Search Archives Numbered Notes CBD Archives Subscribe
FBO DAILY ISSUE OF SEPTEMBER 14, 2003 FBO #0656
SOURCES SOUGHT

12 -- REPLACEMENT FOR AVENGER/CLAWS RTU

Notice Date
9/12/2003
 
Notice Type
Sources Sought
 
Contracting Office
N00164 300 Highway 361, Building 64 Crane, IN
 
ZIP Code
00000
 
Solicitation Number
N0016403Q6628
 
Response Due
10/15/2003
 
Point of Contact
DOUG MCDANIEL 812-854-5395
 
E-Mail Address
Email your questions to To email point of contact
(mcdaniel_d@crane.navy.mil)
 
Description
The Navy is seeking information on a replacement unit for the Marine Corps? Avenger/Claws Remote Terminal Unit (RTU). In this replacement RTU effort, it is the Marine Corps? desire to find a potential solution and gather technical and cost information to plan and budget for future requirements. Potential technologies to be considered include the utilization and integration of a ruggedized laptop computer (preferably Commercial-off-the-Shelf (COTS)) with interfaces that allow for simple, cost effective upgrades in the future, or others that could meet the requirements of this Request For Information (RFI). The following are the tentative requirements of the replacement RTU: (a) The unit must have a CPU with a minimum of 500 MHz processing speed and is X86 compatible; (b) The unit must have a minimum of 256 MB RAM; (c) The unit will use VxWorks as the operating system (for compa tible with application software); (d) The unit must have a hard disk drive with a minimum of 10 Gigabytes capacity; (e) The unit must have at least 2 removable solid state memory devices, that allow for storage of data and to provide the capability and capacity to operate the unit in configurations in which the hard drive has been removed; (f) The unit should be man portable; (g) The unit must be capable of being securely mounted and easily dismounted by the operator in both the turret and the cab of an Avenger Anti-Aircraft Missile vehicle; (h) The weight of the unit should not exceed 20 lbs; (i) The maximum height for the unit in it?s operating configuration is 12 inches; (j) the maximum width to prevent interference is 15 inches (connectors in an appropriate location may extend 1 additional inch beyond the maximum); (k) The maximum depth to prevent interference is 10 inche s (there is room for additional depth away from the edges) (a diagram showing the relative position of the RTU in relation to the steering yoke can be provided upon request); (l) The unit?s color display screen should be at least 6.4 inches diagonal, and should be easily legible in all light conditions including direct sunlight and total darkness; (m) The unit?s keyboard should have raised buttons (membrane keyboards are unacceptable); (n) The unit must have Military connectors providing the following interfaces: 2 each RS232, 4 each RS422/423, 1 each TCIM and 1 each 24VDC power (Connector part numbers and pin assignments are available upon request.); (o) The unit must communicate with SINCGARS Radio to receive GBDL data and to send and receive tactical email; (p) The unit must communicate with the Avenger weapon system via the existing connections and interfaces in the Avenge r; (q) The unit will not have a functional wireless network capability. If the hardware to support this capability is provided, it shall be disabled; (r) The unit must pass the following MIL-STD-810F requirements; (1) Low Pressure (Altitude) (500.4), Procedure I Storage, and II Operation, and should continue to operate normally during the test while all communication cables are connected up to an altitude of 15,000 ft; (2) High Temperature (501.4), 140? F Operational, 160? F Non-operational, and should continue to operate normally during the test while all communication cables are connected; (3) Low Temperature (502.4), ?20? F Operational, ?60? F Non operational, and the unit should continue to operate normally during the test while all communication cables are connected; (4) Temperature Shock (503.4), to 80? F to ?60? F and back, non-operational; (5) Drop Tested (Method 516. 5), Procedure IV (Transit Drop Test); (6) Vibration (Figure 514.5C-1), the unit should continue to operate normally during the test with all communication cables connected; (7) Water Resistance (506.4), Method I, in rain and blowing rain, the unit should continue to operate normally during the test with all communication cables connected; (8) Humidity (506.7), the unit should continue to operate normally during the test with all communication cables connected; (9) Salt Fog (509.4), the unit should continue to operate normally during the test with all communication cables connected; (10) Sand and Dust (510.4), for both Procedure I - Blowing Dust and Procedure II ? Blowing Sand, the unit should continue to operate normally during the test with all communication cables connected; (s) The unit will be required to operate in close proximity to radar antennae, radios and explosive or dinance. The unit must meet MIL-STD-461E standards during operation with all communication cables connected; (t) All cable connections should survive a sudden pull of 30 ft/lbs to simulate a person tripping on the cable; (u) The device should not require any special tools or equipment for operator tasks. Built-in test equipment or self-test circuitry may be incorporated. Respondents should include in submittal the following: proposed approach (including pictures, if available), advantages, disadvantages, training requirements for users, ability by the Government to maintain item, timeline for development and delivery, and Rough Order of Magnitude of cost. The information above should be based on a quantity of 633 units. Interested companies should provide information along with technical questions regarding this announcement to Mr. Doug McDaniel, e-mail mcdaniel_d@crane.nav y.mil, NSWC Crane, 300 Highway 361, Code 1164, Building 64, Crane, IN 47522-5011. Responses should be submitted no later than 15 October 2003. Please include the RFI number on all correspondence. This notice does not constitute an Invitation for Bids or a Request for Proposal (RFP), and it is not a commitment by the Navy to procure products or services. The Navy is only seeking information for future needs. No RFP solicitation document exists at this time. The Navy does not intend to award a contract on the basis of this Request For Information, and will not reimburse any costs incurred by interested companies responding to this announcement. However, respondents to this Request for Information will not be excluded from consideration for contract participation in any potential follow-on hardware development activity. All information marked as proprietary information wil l be safeguarded to prevent disclosure to non-Government personnel and entities.
 
Web Link
NSWC CRANE WEB PAGE
(http://www.crane.navy.mil/supply/homepage.htm)
 
Record
SN00433430-W 20030914/030912213418 (fbodaily.com)
 
Source
FedBizOpps.gov 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.