Attachment 1 

ATTACHMENT TO ADC 397 

Deletion of the Passive RFID Reader ID Number from the Reader Registration 

Tables (Table C3.T1) 

1. ORIGINATOR: 

a. Service/Agency: DLA Logistics Management Standards Office

b. Originator: Heidi Daverede, DLA Logistics Management Standards Office, (703) 

767-5111

2. FUNCTIONAL AREA: 

a. Primary: Supply 

b. Secondary: Automatic Identification Technology (AIT) 

3. REFERENCES: 

a. DoD 4000.25-M, Defense Logistics Management System (DLMS), Volume 3, 

Chapter 3, Passive Radio Frequency Identification (pRFID) Transactions

b. DoD AIT Policy Website (URL): http://www.transcom.mil/ait/. 

4. REQUESTED CHANGE: Yellow highlighting identifies additions and revisions made 

subsequent to staffing of the PDC (PDC 418) to add clarity to the changes. 

a. Intent of the revision: During recent passive RFID (pRFID) testing by the IDEGTN Convergence (IGC) program, test personnel identified a conflict in the test transaction data 

and the published DLMS guidance regarding pRFID data requirements for the standard XML 

pRFID schema. Subsequent research determined that the DLMS manual guidance was incorrect. 

This revision deletes the requirement for the Passive RFID Reader ID Number and updates the 

attributes for both the Location Control Number and the Reader Registration Action located in 

the Data Requirements Tables in DoD 4000.25-M, Volume 3, Chapter 3. 

b. Scenario for which transaction is used: Passive tags should be applied at the case 

and pallet levels to all sustainment and retrograde shipments to support asset visibility within the 

DOD supply chain and improve logistics business processes. The DLMS Manual requires the 

registration of pRFID readers with DAAS, using the XML Reader Registration transaction. This 

proposed revision eliminates the requirement to include a Reader ID Number in the Reader 

Registration Transaction, as the information is functionally duplicative of information to identify 

the reader in another part of the transaction, in the RFID Location Control Number (LCN). This 

revision aligns the table in the manual with the previously implemented schema. 

c. Procedures, transactions, data elements, processing details in use today: 
Attachment 1 

1) All pRFID readers are required to be registered at DLA Transaction Services. 

The registration is accomplished through use of the standard XML Reader Registration 

transaction, in which a unique Location Control Number (LCN) is assigned to the reader by 

DAAS and the reader information is stored in the DLA Transaction Services “L” or location 

table. The LCN is used in every subsequent transaction sent to DAAS from the reader, and 

provides the reader location information. 

 

2) When the pRFID tag is subsequently read by a Registered Reader, the 

standard XML Visibility transaction is transmitted to DAAS by the user system with the Reader 

Location Control Number and the pRFID tag number that was read; this data is stored in the “V” 

table, is available through WEBVLIPS, and identifies the source reader by location. 

3) The necessary data is captured about both the shipment and its location, by 

associating the pRFID tag read to an LCN and the particular reader. The shipment information 

can then be accessed through WEBVLIPS at DLA Transaction Services. No change in this 

access capability will result from deleting the Reader ID Number data. 

5. PROPOSED CHANGES: 

a. Description of Change in Detail: This change deletes the requirement for reporting the 

pRFID Reader ID Number in the XML Reader Registration transaction. The Reader ID Number 

will be deleted from Table C3.T1 in Chapter 3, shown in enclosure 1. There are no system 

changes required from deleting the Reader ID Number entry from the table in the DLMS 

Manual, since the data element is not carried in the XML pRFID transactions. 

b. Administrative Changes: There are three administrative changes identified below as 

well, and are shown in detail in the tables at enclosure 1. 

1) The current Minimum/Maximum length for the Reader Location Control 

Number (LCN) element is changed to 1/16 (from 16/16) in Tables C3.T1, C3.T2, and C3.T3. 

2) The Minimum/Maximum for the Reader Registration Action element is 

changed to 1/2 (from 2/2) in Table C3.T1. 

3) The words “Expressed in hexadecimal” for the pRFID Tag Number are 

deleted from the “Values” column of Tables C3.T2 and C3.T3. 

   

6. REASON FOR CHANGES: These changes align the DLMS Manual DoD 4000.25-M, 

Volume 3, Chapter 3, and the Data Requirements Tables, with the actual implementations of 

these transactions by current trading partners. The Reader ID Number is not carried in the 

existing XML Reader Registration and Visibility transactions. The RFID Location Control 

Number (LCN) already provides the necessary unique reader identification information. 

Additionally, the Minimum/Maximum length for the RFID Location Control Number (LCN) and 

Reader Registration Action are changed to reflect the actual parameters for the full range of 

numbers that may be present in the field, such as a “0” or “1”. The reference to “expressed in 

hexadecimal” in the “Values” column of the tables is no longer required. 
Attachment 1 

7. ADVANTAGES AND DISADVANTAGES: 

a. Advantages: Updates the DLMS Manual documentation and related tables to reflect the 

actual implementation of the pRFID transactions and associated data. This change also supports 

implementation of pRFID data requirements stipulated by DOD AIT policy. The pRFID data 

requirements shown in the tables support shipment visibility across the DoD supply chain as 

passive tags are applied at the case and pallet levels. 

b. Disadvantages: None. There are no software code changes required as a result of this 

action. 

8. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: These changes were 

previously implemented in the XML Reader Registration Schema, which is already in use by 

pRFID trading partners. The DLMS Manual update, to align the DLMS Manual tables with the 

current implementation, will be made upon approval of this DLMS change. 

9. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: None. This is an administrative change to align 

DLMS manual tables with already implemented transactions.

10. IMPACT: No impact is expected in deleting the Reader ID Number, since it has not been 

carried in the XML schema since the original implementation of the pRFID XML schemas. The 

Location Control Number adequately assigns a unique identification number to each individual 

pRFID reader registered at DLA Transaction Services. The new minimum/maximum parameters 

identified now for the RFID Location Control Number and Reader Registration Action reflect 

the reality of the data currently transmitted to DLA Transaction Services in the XML schemas.

a. New DLMS Data Elements: None. 

b. Changes to DLMS Data Elements:

1) Reader ID Number: Delete. 

2) RFID Location Control Number: Change Minimum/Maximum length to 1/16. 

3) Reader Registration Action: Change Minimum/Maximum length to 1/2. 

4) Passive RFID Tag: Delete “Expressed in hexadecimal” from values column. 

c. DLA Transaction Services: None. 

d. IGC: None. NOTE: Since “Reader ID Number” was not implemented in the 

schema, no data was ever received for loading into the DAAS “L” table; therefore 

there will be no loss of data in the DAAS feed to the Enterprise Data Warehouse.
Enclosure 1 

Enclosure 1, Reader Registration and Visibility Transaction Data Requirements Tables (From 

DOD 4000.25-M, Volume 3, Chapter 3, Passive Radio Frequency Identification (RFID) 

Transactions) 

Table C3.T1. Passive RFID Reader Registration Data Requirements

Element Description Man/ 

Opt/ 

Con1

Minimum 

Lgth 

Maximum 

Lgth 

Values 

RFID 

Location 

Control 

Number 

(LCN) 

DAAS-assigned upon 

initial registration 

C 16 1 16 From site to DAAS: 

- Blank for initial 

registration request 

- LCN for update 

requests 

From DAAS to site: 

- LCN

Reader 

Registration 

Action 

Describes purpose 

of registration 

action or DAAS 

response to the 

registration action 

M 2 1 2 From Site to DAAS: 

E-establish reader 

U-update reader info 

D-delete reader 

From DAAS to Site:

CE-establish reader 

confirmed 

CU-update reader 

confirmed 

CD-delete reader 

confirmed 

NE-establish reader 

not accepted 

NU-update reader not 

accepted 

ND-delete reader not 

accepted 

Reader Type Location’s reader is 

fixed or mobile 

M 1 1 F = Fixed 

M-= Mobile 

Reader ID 

Number

Number assigned to 

this reader or group of 

readers by the site

M 10 10

Location DoDAAC, CAGE, 

Water Port or Aerial 

Port code for this 

location 

M 5 6 

                                                            1

 “Man” means “Mandatory;” “Opt” means “Optional;” and “Con” means “Conditional.” 
Enclosure 1 

Element Description Man/ 

Opt/ 

Con1

Minimum 

Lgth 

Maximum 

Lgth 

Values 

Location Text Further description of 

this location 

O 1 50 Free form text; 

Possible entries would 

be Area xxx, Bldg. 

xxx, Post xxx, Door 

xxx 

Type of 

Location 

Code to identify type 

of location 

M 1 1 D = DoDAAC 

V = Cage Code 

A = Aerial Port 

W = Water Port 

Table C3.T2. Passive RFID Visibility Transaction Data Requirements

Element Description Man/ 

Opt/ 

Con 

Minimum 

Lgth 

Maximum 

Lgth 

Values 

Passive 

RFID Tag 

Tag ID Value M 24 50 Expressed in 

hexadecimal

RFID 

Location 

Control No. 

DAAS assigned 

during the registration 

process 

M 16 1 16 

Reader 

Function 

Code 

Describes process 

associated with this 

Reader 

M 1 1 From site to DAAS;

A – Arrived 

D – Departed 

O – Observed 

F – Follow-up 

X – Delivered 

U – Undelivered/ 

Attempted Delivery 

From DAAS to site:

N – Not recorded 

Tag Read 

Date/Time 

Date/Time reported 

action took place 

M 12 12 ZULU 

CCYYMMDDHHmm 

(example: 

200612051459) 

 
Enclosure 1 

Table C3.T3. Passive RFID Visibility Response Transaction Data Requirements

Element Description Man/ 

Opt/ 

Con 

Minimum 

Lgth 

Maximum 

Lgth 

Values 

RFID 

Location 

Control No. 

DAAS assigned 

during the 

registration process 

M 16 1 16 

Tag Read 

Date Time 

Date/Time reported 

action took place 

M 12 12 ZULU 

CCYYMMDDHHmm

(example: 

200612051459) 

Reader 

Function 

Code 

Describes process 

associated with this 

Reader 

M 1 1 From DAAS to Site;

F – Follow-up 

Information 

N – No Information 

Found 

If N, the conditional 

fields will not be 

populated. 

Passive RFID 

Tag 

Tag Identification 

Value 

M 24 50 Expressed in 

hexadecimal

Shipment 

Notice Type 

X12 Transaction 

Type Code 

M 3 4 If F, enter “SHIP” 

If N, enter “NONE” 

Document 

Number 

Requisition Number C 14 14 

Suffix Requisition Number 

suffix 

C 1 1 Populated only if 

Document No. has it. 

Transportation 

Control 

Number 

TCN from Shipment 

notice 

C 17 17 

Shipment 

Date 

Date/Time from 

Shipment Notice 

C 12 12 ZULU 

CCYYMMDDHHmm

(example: 

200612051459) 

NSN/Part 

Number 

Stock Number/Part 

Number cited in 

Shipment notice 

C 13 15 

Ship Quantity Quantity Shipped 

cited in Shipment 

Notice 

C 5 9 
Enclosure 2 

Enclosure 2, Comment Resolution 

Item 

# 

Received From Comments Resolution/Remarks 

1. DLA Concurs without comment. No EBS 

impact. 

None required. 

2. Navy Concurs with PDC 418 as written and 

submits no additional changes or 

amendments. 

None required. 

3. Marine Corps Concurs as written. None required. 

4. USTRANSCOM Concurs. None required. 

5. WAWF (Contracting 

support) 

No impact for WAWF or the 

Registry, to include the Hub. 

None required. 

6. Air Force Concurs without comments. None required. 

7. DMLSS (JMFLDC) Concurs. None required. 

8. DLA Transaction 

Services 

Concurs. None required. 

9. Army Concurs. None required.