SOURCES SOUGHT
58 -- Defense Courier Service (DCS) Surface Conveyance Tracking
- Notice Date
- 6/25/2007
- Notice Type
- Sources Sought
- NAICS
- 334220
— Radio and Television Broadcasting and Wireless Communications Equipment Manufacturing
- Contracting Office
- Other Defense Agencies, United States Transportation Command, USTRANSCOM Command Acquisition, 508 Scott Drive Bldg 1900, Scott AFB, IL, 62225, UNITED STATES
- ZIP Code
- 00000
- Solicitation Number
- HTC711-07-Q-0123
- Response Due
- 7/16/2007
- Archive Date
- 7/31/2007
- Description
- REQUEST FOR INFORMATION HTC711-07-Q-0123 is issued for informational and planning purposes only. The information requested by this synopsis will be used within United States Transportation Command (USTRANSCOM) to facilitate decision making and will not be disclosed outside the agency. Please note that USTRANSCOM will not be responsible for any costs incurred by interested parties in responding to this Request For Information (RFI). USTRANSCOM requires listings of products and services that will be required to support / execute / perform / and provide the Defense Courier Service Surface Conveyance Tracking System for 52 Government owned vehicles worldwide. 1. PURPOSE. The purpose of this RFI is to obtain technical information regarding tracking capabilities for surface conveyances such as vans and trucks. 2. BACKGROUND: The Defense Courier Surface (DCS) is responsible for delivery of sensitive materials in several parts of the world. In many cases, DCS-owned surface assets such as vans and trucks are used to deliver these items. To help ensure the security and safe delivery of these materials, DCS is investigating options for the tracking and monitoring of its surface deliveries. This RFI solicits from commercial vendors descriptions of capabilities and technologies that DCS might leverage to that end. 3. HIGH-LEVEL DESIRED CAPABILITIES DESCRIPTION. Vendor responses to this RFI should describe proposed technologies and capabilities that could be used to support the DCS conveyance tracking desired capabilities listed below. a) The capability should enable monitoring of DCS vans and trucks. A ?conveyance manager? should be able to sit at an office workstation, display a geographic area of interest, and ? using that geographical display - show the last reported location of any DCS conveyances making deliveries in that region. b) The conveyance should automatically report its location at flexible time periods. For example, highly sensitive deliveries might require position reports every 5 minutes; while less sensitive deliveries might require position reports every 30 minutes. c) The conveyance manager should automatically be alerted if the conveyance deviates significantly from an assigned route or if the conveyance falls significantly behind schedule. The conveyance manager should be able to define business rules for route and schedule deviation, and other business rules that might be appropriate. d) The driver of the conveyance should have a capability to contact the conveyance manager in case of emergency. e) The conveyance should have the ability to connect other sensors to the system e.g. door opening, security cage breech and tip over/roll over sensors and relay information from these sensors to alert the conveyance manager when activated. f) The conveyance should include the ability to activate remote devices installed on the vehicle e.g. remote vehicle disabling, remote door lock/unlock. g) The driver of the conveyance should have a ?panic button? available in case of emergency. h) The conveyance should alert the conveyance manager automatically if the conveyance tips over i) Information from the conveyance tracking solution should be generically exportable to other software applications or systems as needed by DCS. j) Coverage. The capability should be able to track DCS deliveries in the continental US, Alaska, Hawaii, Korea, Japan, Italy, and Western Europe. 4. INFORMATION SOUGHT FROM VENDORS. A description of technical solutions from vendors ? as they apply to the above desired capabilities ? should include the following as a minimum: a) Description of equipment. Equipment required for the conveyance, equipment required for the conveyance manager, network/comms equipment, etc. b) Description of equipment installation requirements. For example, can an untrained user install the equipment? Or does equipment installation require vendor technicians? What is the level of effort to install each piece of equipment recommended to meet requirements? c) Description of technologies involved in the solution d) An architecture description. For example, how is conveyance location data transmitted from the conveyance to the conveyance manager? e) Technology limitations. For example, are there ?dead zones? in the geographic areas listed above where the conveyance would be unable to transmit a position? f) Interoperability description. For example, is the equipment capable of running additional third-party software, such as navigation software or status reporting software? g) Description of information provided to the conveyance manager. For example, position and date-time. Would the conveyance provide any additional information such as vehicle speed, weather conditions, etc? h) Description of the solution?s ability to handle the following situations: a. Driver Panic alert b. Equipment failure to communicate c. Telemetry alerts (i.e., door or other intrusion sensors) i) Description of your service?s abiliaty to interface with a government GIS system rather than providing visual access directly to the user. j) Estimated costs for: a. Equipment b. Equipment Installation c. Equipment transmission These estimates are to be based on the following parameters: - 300 tracking events (road delivery missions) per month - Each tracking event requires tracking for approximately eight (8) hours - Geographically dispersed in the following areas: - Continental United States (80%) 264 missions per month - Japan (8%) 24 Missions per month - Western Europe (12% ) 12 missions monthly in UK, 23 within Continental Europe 5. FORMAT FOR RFI: The format for submittal of your RFI is outlined below. a) Pages 8.5 x 11 inches in size, single or double spaced, margins not less than one inch all around, one-sided printing, pages numbered, in at least 10 point type; b) The title page shall be limited to one page and clearly labeled ?RESPONSE TO REQUEST FOR INFORMATION HTC711-07-Q-0123.? It shall also include the date of submission, the RFI response title, area(s) addressed by the response, plus respondent?s administrative and technical points of contact along with telephone and facsimile numbers, electronic mail address (if any), and signed by an authorized officer; 6. Submission Information: Please submit two hard copies with one electronic copy to Paula Teague at Paula.Teague@USTRANSCOM no later than 3 August 2007. Hard copies shall be mailed to USTRANSCOM, TCAQ, ATTN: Paula Teague, 508 Scott Drive, Scott AFB, IL 62225-5237. Responses received after that date may be evaluated at the Government?s discretion as time permits. Questions may be directed to Paula Teague by e-mail at Paula.Teague@USTRANSCOM.mil. 7. RESPONSE REVIEW: Any information submitted with your responses that you do not consent to limited release must be clearly marked and submitted segregated from other response material. Response to this RFI or lack thereof does not constitute any obligation on the Government to pursue a follow-on effort, in part or whole, with specific vendors or otherwise.
- Place of Performance
- Address: Scott AFB, IL
- Zip Code: 62225
- Country: UNITED STATES
- Zip Code: 62225
- Record
- SN01327445-W 20070627/070625221358 (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 |