U.S. Department of Justice, Immigration and Naturalization Service Contracting and Procurement Branch, 425 I Street, NW, Room 2102 Washington, DC 20536

70 -- GENERAL PURPOSE ADPE (INCLUDING FIRMWARE), SOFTWARE, SUPPLIES AND SUPPORT EQUIPMENT POC Lesa Scott, Fax 202 514-3353. The INS is investigating technologies to expedite vehicle travel through a port-of-entry (POE). The INS is requesting information on software and hardware products to support a Dedicated Commuter Lane (DCL) to be installed at the Otay Mesa, CA, POE. These products will be reviewed for integration into the pilot DCL. This DCL will provide a pre-approved group of low-risk frequent border crossers the ability to enter the United States in a dedicated lane, monitored by the automated DCL system, without having to stop. At enrollment, each individual (driver and passengers) must provide a biometric which serves as a unique identifier and one the DCL system can validate while traveling in the DCL. Each vehicle using the DCL must be approved for enrollment and equipped with an identification device that, like the individual, can be uniquely identified and validated by the DCL system while traveling in the DCL. This validation ensures that all individuals and vehicles crossing the border are actually enrolled. The DCL system will request and collect all vehicle identification and individual biometric data in order to validate enrollment in the program before allowing entry into the United States. The vehicle shall not be required to stop, unless the DCL system is unable to approve the vehicle, driver, or any passenger. The preferred biometric is voice verification, however other biometric types will be considered, provided the collection of the biometric data does not interfere with the actions of the driver nor pose a safety hazard. The major requirements are as follows: (1) at enrollment, biometric data for each enrollee shall be captured, digitized, and stored in the DCL system database, (2) the DCL system shall make the initial request for biometric data from the individual and no biometric data shall be processed by the system unless requested by the system, (3) biometric data captured by the system shall be compared to the data for that individual stored in the DCL system database, (4) all biometric data shall be requested, captured, and validated (or rejected, if invalid) while the vehicle is in the DCL prior to crossing the border and without causing the vehicle to fall below the minimum DCL speed, (5) while traveling in the DCL, the DCL system shall be able to uniquely identify the vehicle, driver, and all passengers while the vehicle maintains a speed of not less than 5 miles per hour (mph) nor more than 10 mph, (6) while traveling in the DCL and after the DCL system captures and processes all individual and vehicle data, the driver shall be instructed to either proceed through the DCL without stopping or proceed to an alternate lane for inspection, (7) the border crossing event shall be recorded and stored in the DCL system database, and shall include the vehicle identification number (VIN), license plate number and state number and identity of all individuals in the vehicle time and date of the border crossing event and location of the crossing event (POE, lane number), (8) the border crossing event data shall be accessible by querying the DCL system database, either locally or remotely via a network, (9) all data transferred between the DCL system and remote identification devices located in the vehicle or DCL shall be secure, (10) there shall be a process for detecting and handling violators in the DCL (for example, a non-enrolled vehicle or individual or a vehicle not proceeding as directed), (11) all software shall exhibit the quality factors for maintainability, reliability, performance, security, human factors, portability, compatibility, and adaptability, (12) the DCL system must be able to track and process up to 100 vehicles using the DCL at any given time and initiate and complete all processing within 45 seconds, (13) the software and hardware products must be able to work with any reasonable traffic volume and number of enrollees expected for a POE in California, (14) hardware products installed in the vehicle must be physically secure. Responses may be for products or technical information that provide automatic vehicle identification (AVI), biometric verification (voice preferred, but not required), or both. Responses should not be restrictive and all proprietary items must be identified. Pricing information for commercial-off-the-shelf (COTS) products should be provided as both feasibility and cost/benefit will be evaluated, especially those products installed in the vehicle. COTS products must be provided with an assurance that they will be available for integration into this pilot system and, if applicable, in sufficient quantity for installation in enrolled vehicles. Security must address both computer and data security as well as the physical security of products mounted in the vehicle and in the DCL. All software and hardware products must be compatible with commercially available open systems platforms and, where applicable, have standard high- level programming language or database interfaces. A product demonstration or proof-of-concept might be required. Interested parties shall submit a technology capability package with complete descriptive literature within 10 days to: Neil Adams, EDS/ITP, 800 K Street, NW, Suite 830, Washington, DC, 20001. Questions should be faxed to (202) 414-4855. This is a request for information only. The INS will issue a formal synopsis for any procurements resulting from this technology investigation. INS SYNOPSIS 14- 95. (0073)

Loren Data Corp. http://www.ld.com (SYN# 0401 19950315\70-0001.SOL)