RFID Technology
DoD RFID Policy
Standards and Tag Data Requirements
Contractual Requirements
Advance Shipment Notice (ASN) Requirement
Additional Information for Suppliers
RFID and UID
IT System Impact
Direct Vendor Shipments
Foreign Military Sales (FMS)
Electromagnetic Effects and the Safety of RFID Devices
Blanket Purchase Agreement
If your question is not answered by these FAQs, please send your question to info@dodrfid.org.
RFID Technology
Q: What is RFID?
A: Radio Frequency Identification (RFID) is an automatic identification method that relies on storing and remotely retrieving data using devices called RFID tags or transponders. An RFID tag is an object that can be attached to or incorporated into a product, animal, or person for the purpose of identification using radio waves. Microchip-based RFID tags contain silicon chips and antennae. Passive tags require no internal power source, whereas active tags require a power source.
Q: Can you explain RFID Technology?
A: RFID systems carry data in suitable transponders, generally known as tags, and retrieve data, via readers (fixed or handheld), at a suitable time and place to satisfy particular application needs. Each tag has a discrete memory capacity that varies from a small license plate with only a few characters to a memory capacity with thousands of records. Data within a tag may provide any level of identification for an item during manufacture, in-transit, in-storage, in-use, or in-maintenance. With additional data, the tag may support applications that require item-specific information. For example, shipment consignee or destination ports can be readily accessed upon reading the tag. In addition to tags, an RFID system requires a means for reading or “interrogating” the tags to obtain the stored data and then some means of communicating the tag data to a DoD logistics information system. RFID in the context of DoD usage falls into two broad categories based primarily on the technology currently in existence — active RFID and passive RFID.
Q: What is the difference between active and passive RFID?
A: Active RFID uses an internal power source (a battery) within the tag to continuously power the tag and its RF communication circuitry that generate the outgoing signal. Active RFID allows extremely low-level RF signals to be received by the tag (since the reader/interrogator does not power the tag), and the tag can generate high-level signals back to the reader/interrogator. Active RFID tags are continuously powered, whether in the reader/interrogator field or not, and are normally used when a longer tag read distance is desired.
Passive RFID relies on RF energy transferred from the reader/interrogator to the tag to power the tag. Passive RFID tags reflect energy from the reader/interrogator or receive and temporarily store a small amount of energy from the reader/interrogator signal in order to generate the tag response. Passive RFID requires strong RF signals from the reader/interrogator, and the RF signal strength returned from the tag is constrained to very low levels by the limited energy. Passive RFID tags are best used when the tag and interrogator will be in close proximity to each other.
Q: Will RFID tracking systems replace barcode systems?
A: RFID will supplement, not supplant barcodes for tracking items. The difference between RFID and barcodes is that RFID does not require line-of-sight. The barcode must be seen by the scanner in order to be read, while an entire shipment of goods labeled with passive RFID tags can be moved through an RFID reader, and all items in the shipment can potentially be identified at once.
Q: Why implement RFID now?
A: The DoD and numerous leading supply chain managers in the private sector have recognized RFID as a key technology enabler for the supply chain. The Department continues to help drive the direction, cost, and application of this technology, to drive the standards to work for us and to take early advantage of the benefits of this leading-edge technology. RFID is a key component in making knowledge-enabled logistics a reality.
Back to top
DoD RFID Policy
Q: What is DoD's vision and goal with regard to the use of RFID?
A: RFID is a truly transformational technology and will play a vital role in realizing the DoD vision for implementing knowledge-enabled logistic support to the warfighter through fully automated visibility and management of assets. Our goal is to employ mature and emerging supply chain technologies to optimize the supply chain. The use of RFID as an integral part of a comprehensive suite of Automatic Identification Technology (AIT) will facilitate accurate, hands-free data capture in support of DoD business processes in an integrated end-to-end supply chain enterprise.
Q: Why is RFID technology being implemented in the DoD Supply Chain?
A: The implementation of RFID enables the improvement of data quality, item management, asset visibility, and maintenance of materiel. RFID addresses a key challenge that has been observed at every node within the DoD supply chain — lack of visibility of logistics data. The use of RFID in the DoD supply chain has the potential to provide real benefits in inventory management, asset visibility and interoperability in an end-to-end integrated environment. RFID encapsulates the data accuracy advantages inherent in all types of Automatic Identification Technology (AIT). Additionally, RFID is a non-intrusive methodology for data capture (requires no human intervention), and, unlike barcodes, does not require line-of-sight to be read. RFID is a key technology enabler for the DoD logistics business transformation and supports long-term integration of Item Unique Identification (IUID) into the DoD end-to-end supply chain. RFID (both active and passive) is required by DoD to:
1. Provide near real-time in-transit visibility for all classes of supplies and materiel.
2. Provide "in the box" content level detail for all classes of supplies and materiel.
3. Provide quality, non-intrusive identification and data collection that enables enhanced inventory management.
4. Provide enhanced unit pack level visibility.
Back to top
Standards and Tag Data Requirements
Q: What RFID standards will DoD support, ISO or EPC?
A: The DoD remains committed to support commercially available RFID standards to help drive adoption and foster competition for RFID solutions. The Department currently uses the UHF Gen 2 EPC standard. EPCglobal’s GEN 2 standard has been ratified by the International Organization for Standardization (IOS) as 18000-6C.
Q: Do I need to join EPCglobal to do business with DoD?
A: While we encourage suppliers to consider the benefits of joining EPCglobal, membership is not a requirement to do business with the DoD. Non-EPCglobal members should encode all tags being shipped to the DoD with the DoD tag data construct.
Q: What are the technical specifications for passive RFID tags?
A: For all contracts written after 19 May 2006, containing the RFID Defense Federal Acquisition Regulations Supplement (DFARS) clause, the DoD established a sunset date (last allowable date) of 28 February 2007, for EPC Generation 1, Class 0 and 1, specification tags. As of 1 March 2007, the DoD will only accept UHF Gen 2 EPC standard tags. The frequency range for these tags is 860 to 960 MHz with a minimum read range of 3 meters. This corresponds to DoD’s goal of using an open UHF Gen 2 EPC standard tag that will support the end-to-end integration of the DoD supply chain. For more information on the technical specifications for passive RFID tags, please see the Supplier Guide at http://www.acq.osd.mil/log/rfid/supplierguide.htm.
Q: What are the passive UHF RFID tag data structure requirements?
A: The DoD will accept tags encoded per the instructions provided in the most recent EPC Tag Data Standards document, available at http://www.epcglobalinc.org/standards.
Q: How will a supplier know where to place a tag on a shipment?
A: Please see section 3.7, “Tag Placement,” in the DoD Suppliers’ Passive RFID Information Guide for guidance on tag placement (available at http://www.acq.osd.mil/log/rfid/supplierguide.htm).
Q: What serial number information do I input in the "serial number" data construct of the RFID tag ID?
A: The “serial number” required in the RFID tag ID data construct does not refer to the serial number of the product being shipped. The “serial number” in the RFID tag ID is merely a unique number assigned by the supplier to represent a specific RFID tag. For example, this “serial number” combined with the supplier’s Government Managed Identifier, or CAGE code, together with the header and filter values comprise the RFID tag ID (see the DoD 96-bit Identity Type below). It is the responsibility of the supplier, with which the Department holds the contract, to ensure that every RFID tag the supplier ships to the Department is encoded with a globally unique identifier (unique tag ID), regardless of the selected tag encoding scheme. It is never acceptable for a supplier to repeat a tag ID across two or more RFID tags. Please see section “3.6 Identity Types” in the DoD Supplier Guide at http://www.acq.osd.mil/log/rfid/supplierguide.htm for examples.
DoD-96 Identity Type
![Identity Type](https://webarchive.library.unt.edu/eot2008/20090109150817im_/http://www.acq.osd.mil/log/images/dod_96_identity_type.gif)
Back to top
Contractual Requirements
Q: How do I determine if passive RFID tags are required on my shipments to DoD?
A: Three factors determine if you are required to apply RFID tags at the case (exterior container or shipping container) and pallet (palletized unit load) level. These are:
1) You have a contract with the DoD that contains the DFARS clause requiring RFID tags.
2) Your equipment/commodity falls under the classes of supply required to be tagged as described in the DFARS clause in your contract.
3) Your equipment is being shipped to one of the locations defined in the DFARS clause in your contract.
To help determine if your equipment falls under the specified classes of supply to be tagged, please visit the Class of Supply lookup tool at http://www.acq.osd.mil/log/rfid/Class_of_supply_lookup_tool.htm and follow the steps provided. This lookup tool requires the National Stock Numbers (NSNs) of your commodities. If you do not know the NSN, you can visit http://www.dlis.dla.mil/WEBFLIS, click "Public Query," then query by Part Number and CAGE Code. This action will return the NSN. This tool approximates when a commodity is affected by the DoD RFID policy. The final determination of when a commodity is affected is made by your respective Contracting Officer.
Q: Can you please update me regarding the DoD's time table for requiring RFID?
A: DoD has published two Defense Federal Acquisition Regulations Supplement (DFARS) clauses that contractually require suppliers to affix passive RFID tags to materiel at the case (exterior container or shipping container) and pallet (palletized unit load) level for specific commodities being shipped to specific locations.
The Final Defense Federal Acquisition Regulations Supplement (DFARS) clause took effect 14 November 2005. This clause required suppliers to affix RFID tags to all cases (exterior containers or shipping containers) and pallets (palletized unit loads) for shipments of Class I (Packaged Operational Rations only), Class II, Class VI and Class IX items being shipped to Defense Distribution Depot, Susquehanna, PA (DDSP) and Defense Distribution Depot, San Joaquin, CA (DDJC). Suppliers with contracts containing this clause (Class I (Packaged Operational Rations only), II, VI and IX commodities being shipped to Defense Distribution Depot, Susquehanna, PA (DDSP) and Defense Distribution Depot, San Joaquin, CA (DDJC)) will not have to comply with expanded clause (described below) until the that clause is inserted into their contracts.
A subsequent interim DFARS, effective immediately upon release, was published 19 May 2006 and expanded the 14 November 2005 rule.
This subsequent clause expanded the requirement for suppliers to affix passive RFID at the case (exterior container or shipping container) and pallet (palletized unit load) level for shipments of Class I (Packaged Operational Rations only), II, III(P), IV, VI, VIII (excluding Pharmaceuticals, Biologicals and Reagents), and Class IX items being shipped to the following DoD locations:
Defense Distribution Depot, Albany, GA
Defense Distribution Depot, Anniston, AL
Defense Distribution Depot, Barstow, CA
Defense Distribution Depot, Cherry Point, NC
Defense Distribution Depot, Columbus, OH
Defense Distribution Depot, Corpus Christi, TX
Defense Distribution Depot, Hill Air Force Base, Ogden, UT
Defense Distribution Depot, Jacksonville, FL
Defense Distribution Depot, Tinker Air Force Base, Oklahoma City, OK
Defense Distribution Depot, Norfolk, VA
Defense Distribution Depot, Puget Sound, WA
Defense Distribution Depot, Red River, TX
Defense Distribution Depot, Richmond, VA
Defense Distribution Depot North Island, San Diego, CA
Defense Distribution Depot, Tobyhanna, PA
Defense Distribution Depot, Warner Robins, GA
Air Mobility Command Terminal, Charleston Air Force Base, Charleston, SC
Air Mobility Command Terminal, Naval Air Station, Norfolk, VA
Air Mobility Command Terminal, Travis Air Force Base, Fairfield, CA
The DoD has many contracts with its suppliers that are renewed and recompeted regularly. As these new contracts are effective, the DFAR clause requiring RFID will continue to be included according to the supplier implementation plan, available at http://www.acq.osd.mil/log/rfid/implementation_plan.htm.
Q: The supplier implementation plan is phased by classes of supply. What are the definitions of the different classes?
![](https://webarchive.library.unt.edu/eot2008/20090109150817im_/http://www.acq.osd.mil/log/images/different_classes.gif)
Back to top
Q: What happens if a supplier does not comply with the policy or if materiel is delivered with a faulty (i.e., non-working) RFID tag?
A: Contracting officers will work with non-compliant vendors to ensure that they are meeting the requirements of their contracts.
Q: If a manufacturer ships to a wholesale distributor who then ships to the DoD, whose responsibility is it to tag cases and pallets going to the DoD?
A: The responsibility for the RFID requirement (including readability) rests with the entity with which DoD holds the contract.
Q: May I apply Passive RFID tags to all commodities that I am shipping to DoD, even if my contract does not contain the DFARS Clause requiring RFID tagging?
A: Yes, with some exceptions. For purposes of implementing standard business processes, suppliers are allowed to apply RFID tags even in contracts in which the DFARS Clause requiring RFID tagging has not been included. However, suppliers are not allowed to apply passive RFID tags to the following commodities: Class V (munitions/explosives) and Class VIII (biologicals and reagents).
Q: Our company has several different CAGE codes that we ship under, and the CAGE code is required in the data construct. Can we choose one of our CAGE codes for all of our products?
A: You can use either the same Cage code for all of your products or multiple CAGE codes for each of your products provided the serial number is unique within the CAGE code. To illustrate this point, if two or more divisions of the company are writing tags with the same CAGE, they need to ensure they are not using the same serial numbers.
Q: A contractor is awarded a contract. The contractor selects a partner (with a different CAGE) to manufacture the product. Is the Prime Contractor’s CAGE or the Subcontractor’s CAGE used on the RFID tag?
A: In this scenario, the CAGE of the entity who ships the product should be used on the tag.
Q: What exactly is the RFID label supposed to look like? I can’t find specifications identifying what should be printed on the surface of the RFID tag (as opposed to what is encoded on the tag).
A: If you are referring to an RFID tag that has been embedded in a blank label, there is no specific requirement for human readable components. Some suppliers are printing the RFID Tag ID on the tag label, but this is not required. In fact, the RFID tag does not need to be applied as a label — some suppliers are attaching the tag itself (not as part of a label). In either case, a separate shipping label is applied. Another option is to integrate the tag with the shipping label. All of the MIL-STD-129 marking requirements apply to shipping labels. Please refer to section "3.7 Tag Placement" in the DoD Suppliers Guide for detailed guidance about placement of RFID tags (http://www.acq.osd.mil/log/rfid/supplierguide.htm).
Q: The Supplier's Guide states the tags must be “readable at the time of shipment.” What exactly does this mean? If pre-printed tags are purchased and stored over a length of time, do they have to be re-verified when they are used?
A: The requirement is for the supplier to ensure that the tag he/she affixes to the package is readable. This can be accomplished in a variety of ways. Tags that were verified as readable at the time of purchase may be used at a later date for shipments. Similarly, RFID printers establish readability during the printing process (unreadable tags are rejected). Therefore, tags created using an RFID printer do not have to be re-verified. A hand-held reader may also be used to verify readability. Quality Assurance Representative (QAR) personnel are not required to review and certify each RFID tag.
Q: Should we continue to apply barcodes if there is an RFID requirement?
A: Any existing additional label requirements (e.g., 2-D barcode) remain regardless of the RFID requirement. The RFID requirement does not supersede or replace any other marking/labeling requirements.
Q: Has the sunset date for DoD’s acceptance of EPC Gen 1 RFID tags been finalized and printed in the General Register? If so, what is the final date?
A: For all contracts written after 19 May 2006, containing the RFID Defense Federal Acquisition Regulations Supplement (DFARS) clause, the DoD established a sunset date (last allowable date) of 28 February 2007, for EPC Generation 1, Class 0 and 1, specification tags. As of 1 March 2007, DoD will accept UHF Gen 2 EPC standard tags only for these contracts. For all contracts written prior to 19 May 2006, containing the DFARS clause, Class 0 and Class 1 Generation 1, specification tags are still allowed, but suppliers are encouraged to use UHF Gen 2 EPC standard tags due to the improved performance over previous generations of the technology. A deviation has been prepared with this information and is on our homepage at http://www.acq.osd.mil/log/rfid/index.htm under 19 October 2006 — Passive Tag Deviation.
Q: How should the cost of RFID be incorporated into the contract?
A: The cost of implementing and operating RFID technology is considered a normal cost of business. The DoD contractors should work directly with their contracting officers concerning any questions regarding this requirement.
Q: Can you clarify the requirement for suppliers to ensure that each RFID tag that is applied to a shipment contains a unique number?
A: It is the responsibility of the supplier, with which the Department holds the contract, to ensure that every RFID tag the supplier ships to the Department is encoded with a globally unique identifier (unique tag ID), regardless of the selected tag encoding scheme. It is never acceptable for a supplier to repeat a tag ID across two or more RFID tags.
Back to top
Advance Shipment Notice (ASN) Requirement
Q: What is the ASN requirement for RFID?
A: All suppliers who are contractually obligated to affix passive RFID tags to materiel must also send an ASN via WAWF. Please refer to http://www.acq.osd.mil/log/rfid/advance_shipment_ntc.htm for more details on the ASN requirement.
Q: I have a large number of RFID tags to enter into WAWF. Is there a way to enter them all at once or do I have to enter each one separately?
A: There are three options for entering data into the WAWF website. You can manually enter the RFID tag ID into the data, use an 856 Electronic Data Interchange (EDI) document, or use a User Defined File (UDF) to transfer into WAWF. The latter two methods facilitate a more automated data capture and Advance Shipment Notice (ASN) creation process. For more information please refer to the DoD's Supplier's Passive RFID Guide (http://www.acq.osd.mil/log/rfid/supplierguide.htm), which provides information on how to send RFID information through WAWF using an ASN.
Additional questions should be directed to the Wide Area Workflow helpdesk at 1-866-618-5988 or 801-605-7095. You can also get additional information by accessing WAWF training at http://www.wawftraining.com if you are a first-time user or by visiting the WAWF homepage at https://wawf.eb.mil.
For additional assistance in EDI or FTP testing, vendors must initiate a trouble ticket with the DISA Customer Service Center (WAWF Help Desk) at 1-866-618-5988 or 801-605-7095. The Customer Service Center will put the vendor in contact with the Joint Interoperability Test Command (JITC), which provides EDI and FTP testing assistance.
Q: Can you provide an example of entering RFID tags in WAWF where the number of required unique tag IDs exceeds the quantity per CLIN?
A: Assuming the RFID clause applies, suppliers are required to apply passive RFID tags, with unique tag IDs, to all cases (shipping containers and exterior containers) and pallets (palletized unit loads). Currently, WAWF will not allow the commercial vendors to enter more unique tag IDs (referred to as ‘Package IDs’ in WAWF) than the quantity per CLIN. The DoD is working on a solution to fix this problem. In the meantime, DoD commercial vendors should tag all cases (shipping containers and exterior containers) and pallets (palletized unit loads) as required and enter the maximum number of unique tag IDs that WAWF will allow per CLIN.
The scenarios described below are illustrative examples of how tags should be applied and entered into WAWF. The examples are intended to act as a guide only and the final authority on how tags should be applied resides with the contracting officer.
Example: A single CLIN item (quantity 1) that requires shipping in more than one box. (For example, a bundle of items, such as a computer (monitor and CPU) sold as a single CLIN requires two shipping boxes.)
A: In this example, suppliers are required to apply passive RFID tags, with unique tag IDs, to both exterior containers. Since WAWF cannot accommodate multiple tags for CLIN quantity 1, suppliers should enter one of the unique tag IDs into WAWF.
Example: A single CLIN item (quantity 1) consists of multiple exterior containers, palletized together for handling convenience.
A: In this example, suppliers are required to apply passive RFID tags, with unique tag IDs, to all exterior containers and the pallet (palletized unit load). Since WAWF cannot accommodate multiple tags for CLIN quantity 1, suppliers should enter one of the unique tag IDs into WAWF.
Q: Single CLIN Quantity Delivered in Multiple Shipments — A single CLIN item consists of two or more exterior containers (cases) that are delivered in partial lots. An example is a radio, which is delivered in two shipments. The first shipment consists of the antenna and mast and the second shipment consists of the radio. A Quantity of 1 for the example CLIN consists of a radio, antenna and mast.
A: In this example, suppliers are required to apply a unique passive tag to each exterior container for the radio, antenna and mast. Since WAWF cannot accommodate multiple tags for CLIN quantity 1, suppliers should enter one of the unique tag IDs into WAWF.
Q: Sometimes, contracts give clear instructions when quantities of a CLIN are to be palletized. Vendors sometimes palletize for their own convenience, for product protection or as a cost-saving measure. If a contract does not call for palletization, but the vendor chooses to palletize for the reasons above, is an RF Pallet Tag required?
A: If the contract does not call for Palletized Unit Loads, but the vendor has chosen to palletize the load, and the vendor anticipates the palletized load will be handled as a single unit to its final destination, the vendor is required to apply a unique passive tag to the pallet and communicate the tag ID through WAWF.
Back to top
Additional Information for Suppliers
Q: Our company needs to purchase RFID-related hardware and software. Do you have a list of vendors who supply these products?
A: Unfortunately, the DoD is unable to recommend a specific vendor of RFID-related technology and does not keep a list of RFID vendors. If you determine that you need to apply RFID tags to your shipments, you are required to use EPCglobal-compliant tags. Please visit their website at http://www.epcglobalinc.org/certification/hw_cert/ which provides a list of vendors who manufacture RFID hardware (readers, tags and printer/encoders). Please note that we are migrating to Class 1 Generation 2 EPC tags exclusively. The current DFARS for new contracts has established a sunset date (last allowable date) for Class 0 and Class 1 Gen 1 tags of 28 February 2007). We encourage you to use Class 1 Generation 2 tags because of the improved performance of these tags.
Q: Are there any RFID training opportunities in my area in the near future?
A: Your local Procurement Technical Assistance Center (PTAC) representative should be able to assist you. Please visit http://www.dla.mil/db/procurem.htm, choose your State of residence, and then contact your local PTAC office representative. PTAC representatives have been trained by DoD to offer assistance to small- and medium-sized businesses who need to be RFID-compliant. For information on PTACs who have been trained on DoD RFID implementation and policy, please visit http://www.acq.osd.mil/log/rfid/suppliered_training.htm.
Back to top
RFID and UID
Q: What is the difference between the UID and RFID policies?
A: The UID policy addresses the identification and marking of individual items with a unique identifier as specified by the UID policy. The RFID policy relates to the application of passive RFID tags to the packaging of items at the case (exterior container or shipping container), and pallet (palletized unit load) level.
Q: Is the RFID tag data construct the same as the UID construct?
A: There is no relationship between the UID and RFID encoding schemes — each is designed for a specific purpose. The “serial number” required in the RFID tag ID data construct does not refer to the serial number of the product being shipped. The “serial number” in the RFID tag ID is merely a unique number assigned by the supplier to represent a specific RFID tag. This “serial number” combined with the supplier’s Government Managed Identifier, or CAGE code, together with the header and filter values comprise the RFID tag ID (see the DoD-96 Identity Type below). It is the responsibility of the supplier, with which the Department holds the contract, to ensure that every RFID tag the supplier ships to the Department is encoded with a globally unique identifier (unique tag ID), regardless of the selected tag encoding scheme. It is never acceptable for a supplier to repeat a tag ID across two or more RFID tags. Please see section “3.6 Identity Types” in the DoD RFID Supplier Guide at http://www.acq.osd.mil/log/rfid/supplierguide.htm for examples.
DoD-96 Tag Identity
![](https://webarchive.library.unt.edu/eot2008/20090109150817im_/http://www.acq.osd.mil/log/images/dod_96_identity_type.gif)
Back to top
IT System Impact
Q: How will the implementation of RFID impact other IT systems?
A: The use of RFID to help achieve the vision for knowledge-enabled logistics must include the integration of RFID event data into the DoD logistics information systems. The DoD Components are developing strategies to achieve compliance with the DoD Business Enterprise Architecture - Logistics (BEA-LOG).
Back to top
Direct Vendor Shipments
Q: Does the policy apply to direct vendor deliveries (DVDs)?
A: If the contract governing direct vendor delivery has the Defense Federal Acquisition Regulations Supplement (DFARS) clause inserted, RFID tagging is required in accordance with the specifications in the DFARS.
Back to top
Foreign Military Sales (FMS)
Q: Does the DoD RFID policy apply to Foreign Military Sales (FMS)?
A: If the contract governing the FMS has the Defense Federal Acquisition Regulations (DFAR) clause inserted, RFID tagging is required in accordance with the specifications in the DFAR.
Back to top
Electromagnetic Effects and the Safety of RFID Devices
Q: Is the RFID equipment that is currently available for purchase safe for use around personnel?
A: Prior to being made available for purchase within the DoD, all passive RFID equipment will be reviewed by DoD to ensure that this equipment has been licensed by the Federal Communications Commission (FCC) for production and use. According to the U.S. Dept. of Commerce National Telecommunications and Information Administration’s “Manual of Regulations for Federal Radio Frequency Management” all non-licensed COTS products purchased by the Federal Government (including the DoD) are required to bear the appropriate markings indicating conformance to part 15 of the FCC’s Rules and Regulations (47 CFR 15). The document 47 CFR 15 cites IEEE C95.1-1991 as the basis for determining acceptable exposure limits for humans in a radio frequency (RF) energy electromagnetic environment.
DoD Instruction 6055.11, the supporting doctrine behind the DoD Hazards of Electromagnetic Radiation on Personnel (HERP) policy also cites IEEE C95.1-1991 as the basis for determining the permissible exposure limit (PEL) for DoD personnel to radiated RF energy. Therefore, equipment certified by the FCC as compliant with 47 CFR 15 will be in compliance with the DoD HERP policy.
Q: What is DoD doing to address electromagnetic effects and safety concerns surrounding RFID devices?
A: The DoD is committed to the safe and secure use of RFID, both active and passive technology, in the DoD supply chain. To this end, the DoD focuses on the three primary electromagnetic effects that are present with the radio frequency electromagnetic energy propagation that occurs with RFID device use. These three effects are:
HERO — Hazards of Electromagnetic Radiation on Ordnance (munitions)
HERP — Hazards of Electromagnetic Radiation on Personnel
HERF — Hazards of Electromagnetic Radiation on Fuels
The active RFID technology that the DoD has procured to date, as well as the passive RFID technology that the DoD plans to acquire, is commercial technology that falls under the specific guidelines of the Code of Federal Regulations Title 47 (Telecommunications) Part 15 (Federal Communications Commission) Regulations for Unlicensed Devices. Although the DoD is bound by the requirements of the U.S. Department of Commerce National Telecommunications and Information Administration (NTIA) Manual of Regulations and Procedures for Federal Radio Frequency Management Annex K — “Technical Standards for Federal Non-Licensed Devices,” the NTIA Annex K is based in part on the FCC Part 15. Both regulations require that telecommunications devices radiating in specific bands of the electromagnetic spectrum meet identified standards for safety of use.
The Department has completed extensive testing of the specific active RFID technology in use in DoD today and has published detailed guidelines for the safe use of this technology (fixed readers, hand-held readers, RF relays, RFID tags) around munitions, fuels, and personnel. Once the specific items of passive RFID technology (readers, relays, antennae, tags) have been selected for DoD use and scheduled for placement on appropriate DoD contracts, appropriate testing will be conducted for each device against the most stringent “worst case scenario” requirements relating to munitions, fuels, and personnel. Following completion of this testing, detailed DOD guidelines will be published with instructions for the safe operational use of this technology.
Back to top
Blanket Purchase Agreement
Q: Who is permitted to use the Blanket Purchase Agreements (BPAs) for RFID technology managed by the PM J-AIT office?
A: The Blanket Purchase Agreements for RFID equipment and services are for use by all military services including the Coast Guard, other Federal Agencies, foreign military sales, and contracts in support of DoD. For more information on these BPAs, please see the PM J-AIT website at http://www.eis.army.mil/ait/contracts/contracts.asp.
Back to top
|