58 -- RADIO FREQUENCY IDENTIFICATION-BASED AMMUNITION IDENTIFICATION AND MONITORING SYSTEM

Notice Date

April 13, 2001

Contracting Office

Supply Department NAVSEA Indian Head, 101 Strauss Ave, Indian Head, MD 20640-5035

ZIP Code

20640-5035

Response Due

May 11, 2001

Point of Contact

Jessica Maddox, Contract Specialist, 301-744-6614, maddoxjd@ih.navy.mil

Description

Radio Frequency Identification (RFID)-based Ammunition Identification and Monitoring System This is not a request for proposals. This synopsis is for information and planning purposes only, and is not to be construed as a commitment by the Government. This is not a solicitation announcement for proposals and no contract will be awarded from this announcement. Reimbursement will not be made for any costs associated with providing information in response to this announcement and any follow-up information requests. The Indian Head Division, Naval Sea Systems Command, Indian Head, Maryland, is searching for sources who can respond in writing within 30 days of this announcement. The Advanced Technology Ordnance Surveillance (ATOS) system will be an automatic, RFID-based system that will provide ammunition storage location and environmental data to an external database. The following is a summary of the ATOS components and features that will be developed by private industry. We wish to receive vendor comments with respect to development time and cost, development risk, and overall feasibility. Many of the features listed below are currently under discussion, and we wish to assess the impact of these features on both prototype and final version feasibility before developing specifications. We wish to receive vendor comments for the following questions: 1. What is the impact of these features on the feasibility (cost, time, risk, etc.) of developing prototypes? Specific feature-by-feature assessment would be useful. 2. What is the impact of these on development of the final version? The final version will be based on a successful prototype, and will be manufactured as an application-specific integrated circuit (ASIC), for low unit cost. We are targeting $5-15 per tag in quantity of 100,000 in the final version. Ultimate quantity may range upwards to 1M or more. We wish to have prototype features as adjustable as possible to allow assessment of various alternatives during testing. It would also be acceptable to build several prototype versions, each with different capability, rather than a single prototype with adjustable capabilities. Where possible, "best guess" information on the final version has been provided below. Quantities are approximate. Components: 1. RFID tag: prototype quantity several hundred; ultimate quantity in final version, at least several hundred thousand. a. Application Programming Interface per ANSI NCITS 256-1999 part II. b. Package size about 2.5" x 3.5" x 0.5". Exact dimensions TBD. c. Prototype package may be sealed unless access is required to make adjustments or switch selections during testing. Final version package completely sealed with no access after manufacture, except for any sensor requiring access to outside environment. d. Attached to ammunition container or pallet. Impact of adhesive vs. temporary holder. e. Final version operating frequency TBD. Prototype to be capable of selectable operation within the range 2400-2483.5 MHz and either of the following ranges: 225-400 MHz or 433-434 MHz. Additional selectable capability within the frequency range 5725 -- 5875 MHz is optional. Note that the prototype need only operate within one frequency range at a time. We expect to determine exact frequencies within 225-400 MHz and 433-434 MHz based on worldwide regulatory considerations within 6 months. The 2400-2483.5 band is most likely on this basis. 433.92 MHz is also a popular frequency for low power unlicensed devices. It is desirable that the exact frequency below 2400 MHz could be selected after prototype development begins. f. Impact of capability in final version to change frequency within a band (frequency agility, not spread spectrum). g. Impact of capability in final version to switch operation between two widely separated bands (for example, 400 and 2450 MHz) based on receiving a signal in the selected band. This may be required by regulatory considerations. h. RF power level: limited by FCC part 15/NTIA annex K, non-spread-spectrum. Note that according to these regulations, peak ERP above 1000 MHz may be up to about 18.8 dBm (omni radiator), but we anticipate about 0 dBm based on battery and ammunition safety constraints. Capability to field-select ERP levels in prototype from -10 dBm to the permitted maximum is desired. Final version ERP will be fixed. i. Impact of encrypted transmission. j. Read range: 100 ft/30 m in free field desired to fixed, handheld or portable reader. Measured path loss in specific environments to be provided when available. k. Emission type: non-spread spectrum. Modulation method TBD. Impact of FSK modulation. l. Temperature and humidity sensors. Detailed specifications (accuracy, calibration stability, etc.) TBD. We expect to provide sensor information. m. Interface circuitry for two additional sensors, TBD. n. 8-bit sensor resolution. o. Sensor data to be sampled periodically and immediately transmitted in digital form with time and date. Fixed sample period 30 minutes +- 10 minutes for prototype. Final version period will probably be one hour or more. p. Impact of capability to sample sensor data more frequently than RF beacon period. q. Internal memory for 90 days of sensor data. r. Impact on cost and battery life of a tag receiver that must be powered frequently enough for convenient use with a manual handheld reader. Cycle period and duty cycle TBD. s. Tradeoff between read-only tag (no receiver) with asset info in external database only, vs. read-write tag (requiring a receiver) with asset info stored in tag memory. t. Tradeoff between automatic download of stored sensor data at fixed intervals vs. download upon command (latter option requires receiver in the tag). u. Impact of additional read-write memory from 512 bytes to 8 KB (requires receiver in the tag). v. Battery life 5 years minimum at 70F, based on one-hour beacon period. w. Operating temperature range TBD. -65F/-54C to 160F/71C desired for tag and all other components. x. Storage temperature range TBD. -65F/-54C to 160F/71C desired for tag and all other components. y. Final version to withstand standard transportation shock and vibration tests per MIL-STD-810D. z. Cost and feasibility of tag variant with 1-minute beacon period, but no sensors or receiver. Tag transmits fixed ID only, which is associated with an asset in an external database. This variant would be used for brief periods as part of a real-time locating system. It would not be used for long-term location or monitoring. 2. Data relay device that allows tags placed on assets within metal shipping containers to communicate with readers outside the containers. Containers have rubber gaskets around doors, which may provide sufficient access via wire or RF. Prototype quantity 10; ultimate quantity in final version, several thousand. a. Application Programming Interface per ANSI NCITS 256-1999 part II. b. If battery-powered, same battery life requirements as the tag. c. If data relay includes a transmitter, RF power level same as tag. d. No data storage; immediate data transfer to external reader. 3. Fixed reader, to be installed in structures such as magazines and shops. It communicates with tags and sends ID and sensor data on to a database via a LAN. Database server may be located up to 10 miles away. Prototype quantity 20, ultimate quantity in final version, several thousand. a. Application Programming Interface per ANSI NCITS 256-1999 part II. b. No data storage; immediate data transfer to external database. c. For ammunition magazines, installed outside with only antenna(s) placed in magazine; therefore weatherproof. Access through vent. d. Power requirement in prototype: 120 VAC, 60 Hz and 240 VAC, 50 Hz capability required, with alternate power 12 or 24 VDC desired. Final version TBD. e. Omnidirectional antenna(s) desired, to simplify installation. f. If fixed reader transmits to tag (assumes a receiver in the tag), maximum RF power levels same as permitted for tag. g. Impact of various methods of connection to LAN (coax, RF, etc.) Standard RF LAN may be acceptable based on standoff distance between fixed reader and ammunition. 4. Hand-held reader: barcode scanner modified to read RFID tags manually. Prototype quantity 10; ultimate quantity in final version, several hundred to about one thousand. a. Impact of various methods of transferring data to and from external database (docking, IR, Bluetooth, etc.). Standard RF LAN interface in hand-held reader not acceptable because of relatively high (40-54 dBm) ERP. b. Compatible with legacy and recent barcode formats. c. Barcode data syntax per ANSI MH 10.8.2. d. Virtual buttons and GUI desired. e. Final version mechanically rugged and suitable for operation in bright sunlight. f. Rechargeable battery capable of 8 hours of operation per charge. g. Primary battery backup. h. Possible functions (data transfer to and from external database): 1. Read asset data barcode and transfer information to database. 2. Change asset data. 3. De-associate tag from asset. 4. Re-associate tag with asset. 5. Add tag and asset to location. 6. Remove tag and asset from location. i. Possible functions if the tag has a receiver (data transfer to and from tag memory): 1. RFID Application Programming Interface per ANSI NCITS 256-1999 part II 2. Maximum RF power level same as permitted for tag. 3. Rapid "roll-call" of all tags within range. 4. Read asset data. 5. Change (write) asset data 6. De-associate tag from asset. 7. Re-associate tag with asset. 8. Add tag and asset to location. 9. Remove tag and asset from location. 5. Portable reader: allows communication with tagged assets located away from a fixed reader for significant time, but requiring immediate inventory. Prototype quantity 10; ultimate quantity in final version, several hundred. a. Application Programming Interface per ANSI NCITS 256-1999 part II. b. If portable reader transmits to tag (assumes receiver in the tag), maximum RF power level same as permitted for tag. c. Automatic operation in situations where ammunition is located away from a structure for a significant time. d. Rapid setup and takedown. e. Capability for internal and external battery and portable AC generator operation. f. 60 days unattended outdoor operation and data storage. g. Non-volatile memory. h. Impact of rechargeable battery vs. primary battery. j. Impact of various methods of transferring data to and from external database, including upon command from handheld reader. Standard RF LAN in portable reader not acceptable because of relatively high ERP. It is likely that the portable reader will be located at a remote site, and not connected to a LAN. Interested parties are to respond 11 May 2001. Interested parties may send responses to: Commanding Officer, Indian Head Division, Naval Sea Systems Command, 101 Strauss Avenue, Indian Head, MD 20640 Attn: Code 1143I, email: maddoxjd@ih.navy.mil

Record

Loren Data Corp. 20010416/58SOL006.HTM (W-102 SN50J0H9)