DRAFT

PDC 304DAAS-Generated Supply Status for In-transit Asset Visibility

1. ORIGINATOR :

a. Service/Agency: Navy, Naval Supply Systems Command (NAVSUP)b. Originator: LCDR Charles Dwy, DSN 430-1454 / COMM 717-605-

1454: or e-mail: charles.dwy@navy.mil

2. FUNCTIONAL AREA : Primary: Supply

3. REFERENCE : DLMSO Memorandum dated December 7, 2007 subject: Approved DLMS Change (ADC) 219, Passive RFID (pRFID) Visibility Transactions.

4. REQUESTED CHANGE :

a. Description of Change: This change establishes procedures for the preparation of supply status transactions (MILSTRIP Document Identifier AE_) by the Defense Automatic Addressing System (DAAS) upon receipt of passive Radio Frequency Identification (pRFID) asset visibility transactions from an Automated Information System (AIS), or associated middleware or transportation transactions (856A or others). This supply status will provide notification to Navy ships/customers and other status recipients, that material has arrived, departed, or observed at an intermediate supply/transportation location. This change provides the first efforts at end-to-end asset visibility for material in-transit. Changes to AE_ format are identified in bold italics.

b. Procedures: DAAS will capture passive RFID asset visibility transactions from an AIS or associated middleware and or transportation transactions as material moves through a supply point or transportation node. DAAS will then create an AE_ transaction: Using the DAASC Routing Indicator Code (RIC) of SGA (rp 4-6), Inserting a new Status Code indicating an asset visibility transaction

has occurred, and whether the transaction is a shipment arrival (VA), shipment departure (VD), or observation (VO), (rp 65-66),

Inserting the RIC of the submitting activity (rp 67-69), Inserting the date of the passive RFID read or transportation event (rp

70-73), Indicating the type of reader location code, i.e. DODAAC (D), Cage

(V), Aerial Port (A), Water Port (W) in (rp 74),

1

DRAFT

Inserting the location value based on the reader location code (i.e. 6-position DODAAC, 5-position CAGE, 3–position Port Code) (rp 75-80)

c. Background:

i. Since its inception, the DoD has faced on-going challenges with tracking and identifying shipments and inventory across its ever-changing global theater. In order to address these tracking and inventory issues, DoD is employing RFID technology as one of many tools to improve asset visibility and inventory accuracy. RFID technology consists of passive or active tags affixed to containers, equipment, and supplies that are stockpiled or shipped from one location to another. The DoD has been using active RFID technology since the early 1990s and began developing policy and pilot testing passive RFID in 2003. DoD promulgated Radio Frequency Identification (RFID) Policy on July 30, 2004 and directed each of the DoD Components to prepare supporting plans that “encompass both active and passive RFID technology in a cohesive environment to support the DoD vision.” Official implementation of pRFID began January 1, 2005, and all commodities, excluding bulk commodities, and Class V and VII materials, were required to have passive RFID tags affixed to them as of January 1, 2007

ii. Today, once a customer (shore or ship) receives a shipment transaction from the supply system they may not see another transaction until the material arrives. If however, material does not arrive the recipient is limited in their ability to perform causative research. By providing additional asset visibility transactions, as material moves through the transportation / supply nodes, the customer can more accurately determine where material is located and trace material not received.

iii. Joint Regional Inventory Material Management (JRIMM): JRIMM is a project between USTRANSCOM and the DoD Components originally designed to eliminate duplication of inventory and material handling. It was expanded to include the integration of pRFID technology to test the ability to collect and pass the information to the customers, using AE_ status transactions, in order to provide them greater visibility of material. The island of Oahu, Hawaii was selected for this test of the consolidation and coordination of inventory between the services due to its unique compressed geographic attributes. This isolated environment offers opportunities for testing of both the regional

2

DRAFT

inventory management and the improved asset tracking being planned in a controlled environment.

iv. While JRIMM is the start, the end state would be to collect both pRFID and transportation information and pass it to the customer and all status recipients using MILS Supply Status. This would provide the customer or supporting activity in a Distance Support environment, an end-to-end asset visibility picture and allow the greatest flexibility with regard to control over movement, placement, and redirection of material.

d. Approach: Providing pRFID / transportation asset visibility transactions will occur in four (4) phases:

Phase I : Limited prototype on Oahu, Hawaii, Phase II : Rollout of pRFID asset visibility transactions, Phase III : Inclusion of pRFID asset visibility information into the

Logistics Metrics Analysis Reporting System Customer Wait Time (LMARS/CWT),

Phase IV : Capture and reporting of transportation information as material flows through transportation nodes.

e. Detailed Procedure Revisions: DAASC will take existing asset visibility transactions, and those provided by any AIS or associated middleware and create an AE_ transaction to be sent to all status recipients.

i. Routing Identifier Codes (RICs):

a. SGA will appear in the AE_ RIC field, rp 4-6,

b. The RIC of the activity submitting the asset visibility / transportation transaction will appear in rp 67-69,

c. Services and Commands will follow DLMS/MILSTRIP Appendix 2.3 when assigning new RICs. RICs will be assigned as needed to facilitate the capture of pRFID or transportation information and submission of asset visibility transactions to DAASC.

ii. Status Codes: Revise DLMS/MILSTRIP Appendix 2.16, Supply Status, to include the following new codes: Supply Status VA, VD, and VO to indicate passive RFID or transportation status

3

DRAFT

transaction updates.

Code Explanation

VA In-transit asset visibility status derived from passive RFID or transportation transaction indicating material arrival at location identified by RIC in rp 67-69, and/or by code in rp 75-80 on the date indicated in rp 70-73.

VD In-transit asset visibility status derived from passive RFID or transportation transaction indicating material shipment from the location identified by RIC in rp 67-69, and/or by code in rp 75-80 on the date indicated in rp 70-73.

VO In-transit asset visibility status derived from passive RFID or transportation transaction indicating material observation at the location identified by RIC in rp 67-69, and/or by code in rp 75-80 on the date indicated in rp 70-73.

iii. Transaction Formats/DAAS Conversion Mapping:

a. There is a DLMS requirement to identify the organization sending the transaction. The degree of DLMS involvement will be dependent on the Phase of the project.

Phase I : The Phase I CONOPS is attached as Enclosure 4.

Phase II : Rollout of pRFID asset visibility transactions: DAAS rules for using pFID tag read will be:

o DAAS will match the pRFID value to the RFID Table to locate a corresponding shipment status (AE8).

o DAAS will use the document number and media and status code from the corresponding shipment status to prepare the supply status transaction and distribute using standard

4

DRAFT

MILS/DLMS distribution rules for distribution of the supply status to eligible status recipients.

Phase III : Inclusion of the new asset visibility information into the Logistics Metrics Analysis Reporting System Customer Wait Time (LMARS/CWT). Rules for DAAS including passive RFID transactions into LMARS/CWT will be determined later in the entire process.

Phase IV : Capture and reporting of transportation information as material flows through transportation nodes: Rules for reading and utilizing the 856A transaction will be determined later in the entire process.

iv. MILSTRIP Appendix 3.10 revisions are provided at Enclosure 1.

v. Procedures associated with this change are to be included in MILSTRIP Chapter 4 and DLMS Vol 2 manuals as provided as Enclosures 2 and 3.

5. REASON FOR CHANGE: Today Supply/Transportation Systems do not provide end-to-end visibility of material flowing from supply sources through transportation nodes to the end customer. This change will allow the collection and dissemination of information needed to accurately track and account for material. This is especially important in the future distance support environment where shore support activities will order, track, and possibly redirect material on its way from vendors/supply sources to the end user.

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages:

i. These transactions will provide better visibility / accountability of material flowing through the supply / transportation chain and a greater degree of flexibility to redirect material if required.

ii. These transactions will allow the more accurate calculation of Logistics Response Time (LRT) / Customer Wait Time (CWT) performance by providing data to determine problem areas at each step in the supply / transportation chain.

iii. These changes will allow the incorporation of pRFID into the total supply chain.

b. Disadvantages:

5

DRAFT

i. Determining the impact and programming changes required on Legacy AISs.

7. IMPACT:

a. Data Content/Procedures: This project will require changes to the following:

i. DLMS/MILSTRIP to accommodate the new Status Codes and AE_ changes.

ii. Navy applications to process the new Supply Status VA, VD, VO and changes to the AE_ transaction.

iii. The Type of Location Code (rp 74 of the AE_) is the only new data element created by this change.

b. Unresolved Issues: None Noted

c. Implementation: Incorporation of pRFID / transportation transactions into Supply Chain reporting will occur in four (4) phases. Any item passing through a supply / transportation node will trigger an asset visibility transaction that will be converted by DAASC to a status transaction and passed to the intended recipient. Details of each phase are:

o Phase I : Limited prototype on Oahu, will demonstrate the ability to collect pRFID information and pass a new status transaction to the end customer indicating that a pRFID read has occurred and the location of the read. The Phase I CONOPS is attached as Enclosure 3.

o Phase II : Rollout of pRFID asset visibility transactions across the services.

Asset visibility transactions will be passed to DAAS who will take the transactions and convert them to AE_ status transactions with the format shown in enclosure (1).

The middleware providing the transaction will ensure only one transaction is generated for each arrival (A), and delivery (D). Note: there could be multiple transactions if material moves internally within an activity thus generating observations (O).

Status will be provided to any activity that needs to monitor the asset as it passes through the supply/transportation pipeline. DAASC will receive

6

DRAFT

asset visibility transactions then provide status based on Media and Status Code (M&S) Appendix 2.4 and Distribution Code Appendix 2.12. Additionally, if not already routed, status will be provided to the BIRDTRACK application for asset tracking and customer wait time (CWT) calculations.

Roll out will occur in the following order : Commands located / home ported on the

West Coast and 3rd Fleet Operating Area,o Commands located / home ported in

Pearl Harbor, Commands located / home ported in the 7th

Fleet Operating area o Commands located / home ported in

Guam and Yokosuka, Commands located / home ported in the 5th

Fleet Operating Area, Commands located / home ported on the East

Coast (2nd Fleet Operating Area) and Europe (6th Fleet Operating Area)

o Phase III : Inclusion of the new asset visibility information into the Logistics Metrics Analysis Reporting System Customer Wait Time (LMARS/CWT). This will allow the information to be included in CWT calculations providing the ability to breakdown the CWT into smaller pieces for review and change. Rules for including passive RFID transactions into LMARS/CWT will be determined later in the process.

o Phase IV : Capture and reporting of transportation information as material flows through transportation nodes. This will allow an extra level of visibility as material flows to the end user. Rules for reading and utilizing the 856A transaction will be determined later in the process.

d. Publication:

i. This change will impact DOD 4000.25-M and implementing instructions.

ii. NAVSUP P-409, MILSTRIP/MILSTRAP Desk Guide, should be updated to include:

o Supply Status: VA, VD, and VO,o Reader Location Code: D, V, A, W

7

DRAFT

iii. NAVSUP P-485, Naval Supply Procedures, should be updated to include:

o Supply Status: VA, VD, and VO,o Reader Location Code: D, V, A, W

8

DoD 4000.25-1-M, October, 2007

Enclosure 1: MILSTRIP AE1 Revisions

AP3.10. APPENDIX 3.10

SUPPLY STATUS (ISSUES FROM STOCK)

FIELD LEGENDRECORD

POSITION(S) ENTRY AND INSTRUCTIONS

Document Identifier 1-3 Enter DI AE_.

Routing Identifier 4-6 Enter RI of the supply source furnishing the supply status (RI From). If used as a DI AE6 transaction, enter the RI of the supply source to which the transaction will be sent (RI To).1

Media and Status 7 Enter M&S as shown in the original requisition.

Stock or Part Number 8-22 Enter NSN or part number.

Unit of Issue 23-24 Enter U/I.

Quantity 25-29 a. Enter quantity for which status is provided.

b. For ammunition items only (FSG 13), enter an “M” in rp 29 to express in thousands any quantity exceeding 99,999. Example: A quantity of 1,950,000 will be expressed as 1950M (1950 in rp 25-28 and an “M” in rp 29).

Document Number 30-43 Enter document number as shown in the requisition.

Suffix 44 a. Enter suffix applicable to quantity in rp 25-29 when the requisitioned quantity is divided into separate supply actions.

b. When the requisition quantity is not divided, leave this field blank.

Supplementary Address 45-50 Enter data from original requisition.

Signal 51 Enter data from original requisition.

Fund 52-53 Enter date from original requisition.

1 When used by the Material Processing Center (MPC) to notify the Navy customer that materialhas arrived (NL Status) or been delivered (NW or Navy-unique BA Status), rp 4-6 will identify theMPC. RIC of SGA will be assigned by DAASC when used to provide in-transit asset visibility that material has arrived (VA Status) or been delivered (VD), or observed (VO) at an intermediate supply/transportation node. Refer to PDC 304.

i

DoD 4000.25-1-M, October, 2007

FIELD LEGENDRECORD

POSITION(S) ENTRY AND INSTRUCTIONS

Distribution 54-56 When used as an AE6 to provide status on the processing on an LRO, enter 2 for consumables or 3 for reparables in rp 54. Otherwise, enter data as shown in the requisition.

Project 57-59 Enter data from original requisition.

Priority 60-61 Enter data from original requisition.

Transaction Date 62-64 Enter the day that corresponds with the date of this reply.

Status 65-66 Enter status code to convey the information regarding the status of this transaction.

Routing Identifier 67-69 Enter the “last known source” to which authorized follow-up action will be directed. If used as a DI AE6 transaction, the RI will be the activity preparing the document.2

Estimated Shipping Date 70-73 When designated by the status code, enter the four-position ordinal day by which it is estimated the materiel will be shipped.3

Multiple Use4&5 74-80

Unit Price 74-80 Enter unit price of the stock or part number shown in rp 8-22. When the status code in rp 65-66 relates to an erroneously routed requisition, this field will be left blank.

OR

Blank (74-75) Leave blank.

Minimum Order Quantity (76-80) For C8 Status, enter the minimum order quantity.

OR

Blank (74-75) Leave blank.

Federal Supply

Schedule Number6(76-80) For DA Status, enter Federal Supply Schedule Number

constructed as follows:

rp 76-77 Group (numeric) rp 78-79 Part (numeric) rp 80 Section (alphabetic).

OR

2 When used by the Material Processing Center (MPC) to notify the Navy customer that material has arrived (NL Status) or been delivered (NW or Navy-unique BA Status), rp 67-69 will repeat the identification of the MPC. When used to report an asset visibility transaction this field indicates the RIC of the activity report the arrival, delivery, or observation of material.3 When used by the MPC, this will be the date associated with the material arrival (NL Status) or delivery (NW or Navy-unique BA Status). When used to provide in-transit asset visibility, transaction the date of the arrival (VA), departure (VD), or observation (VO) will be entered into this field.4When used by storage in response to a query by the ICP (DI AE6), this data may be omitted at Component option.5DI AE9 transactions generated by DAAS will always be blank in rp 74-80.6Requirement to use DA requisition rejection status to indicate the supply source is direct ordering from the Federal Supply Schedule last reported as not implemented by USAF. Refer to AMCL 132B.

ii

DoD 4000.25-1-M, October, 2007

FIELD LEGENDRECORD

POSITION(S) ENTRY AND INSTRUCTIONS

Type of Location Code (code used to identify the Reader Location or Transportation Transaction Submitter)

(74) Enter:

D = DODAAC,

V = CAGE Code

A = Aerial Port,

W = Water Terminal,

Location (75-80) Enter corresponding location value

6- position DODAAC

5 – position CAGE,

3 – position port code

For DI AE6 Transactions with Status Code BY

70-71 Leave blank.

72If status code (rp 65-66) is BY (previously denied MRO), enter appropriate denial management code.

73 Leave blank.

Unit Price7 74-80Enter unit price of the stock or part number shown in rp 8-22.

For DI Code AE_ Transactions with Status Code CE

79-80For transactions containing rejection Status Code CE in rp 65-66, supply source will enter the correct unit of issue in rp 79-808.

For DI Code AE_ Transactions with Status Code BD (Army only)Management Code 72 If status code (rp 65-66) is BD enter

denial Management Code R, indicating a denial/refusal to the Standard Army Retail Supply System (SARSS) operating under Army Single Stock Fund.

For DI AE6 Transactions with Status Code BY 70-71 Leave blank.

Management Code 72 If status code (rp 65-66) is BY (previously denied MRO),

7When used by storage in response to a query by the ICP (DI AE6), this data may be omitted at Component option.8Requirement to provide correct unit of issue when original unit of issue on the requisition could not be converted last reported as not implemented by USN and DLA (Subsistence). Refer to AMCL 162.

iii

DoD 4000.25-1-M, October, 2007

Enter appropriate denial management code. 73 Leave blank.

Unit Price9 74-80 Enter unit price of the stock or part number shown in

rp 8-22.

For DI AE6 Transactions with Distribution Code 2 and Status Code CB (Army/DLA Interface Only)Management Code 72 If status code (rp 65-66) is CB enter Management Code S,

indicating LRO under TAV procedures was denied because

it matched an existing suffix for the document number.

iv

DoD 4000.25-1-M, October, 2007

Enclosure 2: Changes to DoD 4000.25-1-M Chapter 4

DoD 4000.25-1-M Chapter 4

1. Paragraph C4.1.1: Will require changing: The MILSTRIP System requires that supply sources or MCAs provide status data to designated activities as notice of action taken or being taken on MILSTRIP transactions received, using status codes in AP2.16. Activities to receive status data and the type of data required are designated by entry of an M&S in rp 7 (see AP2.4). A significant distribution code in rp 54 also designates monitoring/control offices to receive all status data. In addition to supply sources furnishing status, the DAAS also generates status in selected situations as a result of receiving asset visibility transactions from supply points or transportation nodes and editing the stock number field of requisitions. The DAAS status will be AE_ for asset visibility transactions or the unique DI of AE9 and the DAAS RI (from) for status resulting from editing the sock number fields.

2. New paragraph – C4.1.4 (old paragraph C4.1.4 will be relabeled C4.1.5): Asset visibility transactions will be passed to DAAS for conversion to MILS AE_ transactions and forwarded to status recipients. DAAS format the transactions in the applicable format shown in the “3” series appendices, will assign status codes from AP2.16 based on the information from the asset visibility transaction, and will transmit the status as indicated by the M&S Code (AP2.4) or Distribution Code (AP2.12).

3. New paragraph - C4.3.7: Status update, AE_, from pRFID read / transportation transaction from a supply point or transportation node processing the material. These transactions should only be used for asset visibility / tracking purposes.

4. New paragraph - C4.5.2.1: When an AE_ status transaction with status code VA, VD, or VO, indicating a transaction from a pRFID reader or transportation source, is received; the receiver will not request additional status from the issuing source. This is only an asset visibility transaction.

5. Para C4.6.1.6: “Use status received as provided in Chapter 2, C2.13, prior to submission of follow-ups.” Revise this para to indicate that AE_ transactions with Status Code VA, VD, or VO are for asset visibility only and cannot be used for follow-ups.

6. New paragraph – 4.8.1.1: Issuing / transshipment supply points using pRFID, and transportation nodes, will pass transactions to DAASC indicating that assets have arrived, shipped, or were observed moving within the activity. These activities, or middleware supporting the activities submitting the transactions, will maintain a history file of the transactions for six (6) months, but will not be subject to MILS transaction follow-ups.

7. Para C4.12.1: Will have to be changed: When required, applicable status on requisitions, reinstated requisitions, redistribution orders, referral orders, responses to

i

DoD 4000.25-1-M, October, 2007

follow-ups, and asset visibility transactions, will be dispatched within the times prescribed below:

C4.12.1.1. Supply Status: C4.12.1.1.1 . Two days from receipt of PD 01-08 transactions or transactions

capturing movement of material through a supply point or transportation node (asset visibility transaction).

C4.12.1.1.2. Five days from receipt of PD 09-15 transactions. C4.12.1.1.3. Twenty-four hours after release of materiel obligation in PD

01-15. C4.12.1.2. Shipment Status: C4.12.1.2.1. Twenty-four hours after shipment (such as; release to

8. New Sub-paragraph 4.13.1.10: Asset Visibility Status Transactions (DI AE_ with Status Codes VA, VD, or VO).

ii

DoD 4000.25-M Volume 2, June 2005Change 2

Enclosure 3: Changes to DoD 4000.25-M Volume 2

DoD 4000.25-M Volume 2

1. New paragraph – C5.2.1.3: Asset Visibility Status: This status informs organizations that an item passed through a supply point or transportation node. These transactions should only be used for asset visibility / tracking purposes.

2. New paragraph – C5.2.4: Types of Asset Visibility Status: (Note: 5.2.4 Requisition Status will become 5.2.5)

a. New paragraph - C5.2.4.1 Status Code “VA:” This asset visibility status is the result of a passive RFID (pRFID) read or transportation transaction and indicates that an item has arrived at a supply point or transportation node.

b. New paragraph – C5.2.4.2 Status Code “VD:” This asset visibility status is the result of a pRFID read or transportation transaction and indicates that an item was delivered either to another supply point, transportation node, or customer.

c. New paragraph – C5.2.4.3 Status Code “VO:” This asset visibility status is the result of a pRFID read or transportation transaction and indicates that an item was moved internally within a supply point or transportation node.

3. New paragraph – C5.2.4.2.1 Follow ups on Asset Visibility Transactions: Activities receiving AE_ status with Status Codes “VA,” “VD,” or “VO,” indicating asset visibility transactions may not submit follow ups directly to the reporting activity. These transactions are only for asset visibility.

4. Paragraph C5.2.6.1 should be rewritten. Requirements. Supply sources must automatically send DS 870S when processing requisitions, redistribution orders (RDOs), cancellations, modifications, and requisition inquiries (follow-ups and requests for supply assistance). MCAs must send reject status for requisitions they process. Supply sources must maintain and send current supply status as provided below. For these purposes, MCAs and supply sources must maintain accessible requisition history records for a minimum of 6 months after completing a shipment of material or canceling a requisition, to provide for timely status responses. MCAs must maintain requisition history records until contract termination. In addition to supply sources furnishing status, DAAS will also generate status in selected situations as a result of receiving asset visibility transactions from supply points or transportation nodes.

5. New paragraph – C5.2.6.3 Asset Visibility Status Transactions: DAAS Asset Visibility status transactions will result from a supply point or transportation node receiving, delivering, or handling material then passing that asset visibility transaction to DAAS.

i

DoD 4000.25-M Volume 2, June 2005Change 2

6. Rewrite paragraph C5.2.6.5. Status Frequency. For each reinstated requisition, retransmitted (rerouted) requisition, requisition modifier, MRO processed, and item passing through a supply point or transportation node, supply / transportation sources must automatically send supply and/or shipment status, as appropriate.

7. New paragraph – C5.2.6.10: Asset Visibility Status Reporting: Issuing / transshipment supply points using pRFID, and transportation nodes, will pass transactions to DAASC indicating that assets have arrived, shipped, or were observed moving within the activity. These activities, or middleware supporting the activities submitting the transactions, will maintain a history file of the transactions for six (6) months, but will not be subject to MILS transaction follow-ups. Upon receipt, DAAS will convert the asset visibility transactions to the appropriate status transactions and make distribution to all eligible status recipients.

8. Rewrite paragraph C5.2.6.12: Time Standards for Providing Status Transactions. When required, supply sources shall dispatch applicable status on requisitions, retransmitted requisitions, reinstated requisitions, responses to requisition inquiries, and asset visibility transactions within the times prescribed below:

C5.2.6.12.1. Supply Status

C5.2.6.12.1.1 Two calendar days from receipt of PD 01-08transactions or transactions capturing the movement of material through a supply point or transportation node (asset visibility transaction)..

C5.2.6.12.1.2 Five calendar days from receipt of PD 09-15 transactions.

C5.2.6.12.1.3 Twenty-four hours after release of MOV requests.

ii

Phase I Prototype CONOPS

Enclosure 4: Phase I Prototype CONOPS:

Oahu pRFID ImplementationsNavy AIT

Objective: To provide increase asset visibility for material movement on Oahu for Navy and Marine Air Logistics requirements. The Navy goals for RFID are closely aligned with the USTRANSCOM DPO’s prescribed uses for AIT:

To improve data accuracy To reduce data capture cost and processing time To reduce data latency To enhance supply chain performance monitoring through improved asset

visibility

The islands of Hawaii were selected for this test of the consolidation and coordination of inventory between the services due to its unique compressed geographic attributes. This condensed environment offers opportunities for testing of both the regional inventory management and the improved asset tracking being planned.

The Navy AIT team visited the Oahu Implementation sites in December 2007 for the purpose of completing site surveys for pRFID implementation scheduled for these locations. Based on that site survey, the following actions are being taken:

PILOT: Demonstrate asset visibility through data transactions of pRFID reads to legacy AIS. Purpose of sending visibility transactions to legacy AIS is to gain confidence in accuracy of pRFID solution prior to use for receipt processing.In preparation for short term pilot, the Navy will:

1. Submit required NMCI paperwork to allow Navy pRFID solution to operate on NMCI network

2. Install pRFID readers and GlobeRanger (GR) middleware at selected Navy sites on Oahu.

a. Register all appropriate new pRFID readers with DAASC according to DLMSO Memorandum of Dec. 7, 2006, as is done today for the Alaska (ARI) project.

b. GR will filter all pRFID reads at Navy Oahu sites to eliminate duplicate reads of same tag at the same reader. GR will only send filtered visibility transaction from only those portals that will contribute to in-transit or in-storage visibility, e.g. no internal doors transitions.

3. GR will send filtered pRFID Visibility Transactions to DAASC as is done today for the Alaska (ARI) project.

4. Provide associated training to local material handling personnel5. Demonstrate visibility reads to local material handling personnel to gain

confidence in accuracy of data captured.

i

Phase I Prototype CONOPS

6. Socialize success of visibility reads and, with success of short term pilot, gain agreement to allow for receipt transaction to occur from pRFID reads.

7. Collect and monitor business and technical metrics.

CONOPS for Short Term Pilot:1. Sites shipping to Oahu Navy sites will create and send Advance Shipping

Notification (856S) to DAAS as usual.2. DAAS will forward Oahu-bound 856S transactions that are destined for the

DODAACs/UICs, identified in Appx A, Table 2 to specific IP addresses for two instances of GlobeRanger in Hawaii (see Appx A, Table 1) as is being done for the ARI project today.

3. GR will send filtered passive RFID portal reads to DAAS as usual. 4. GR will compare filtered passive RFID portal reads against previously received

856S and build an 870S transaction (current format) with “NL” status code5. GR will send 870S transaction to DAAS.6. DAAS will construct an AE1 from the 870S and forward the AE1 transaction

through normal channels to selected Navy AISs (BirdTrack, RSupply, eRMS and MAT) to AV application, to GTN, etc. as appropriate. Since this test will involve a minimum number of transactions to a limited number of locations, impact on LMARS, AV, and GTN should be negligible.

7. Navy will verify that the selected Navy Legacy AISs – BirdTrack, RSupply, eRMS and MAT receives AE1 transaction from DAASC using NL status code as expected.

DAAS and GR should conduct a limited test of this data flow during 4th week of March on a date convenient to DAASC to ensure CONOPS is sound and to work out any unexpected issues.

Enclosure 4, Appendix A - Oahu Passive RFID ImplementationIntroductionThere are two new RFID processes that are being deployed under the Oahu Passive RFID Implementation. 1) Navy AIS Increased Visibility with Visibility Transactions sent to Navy AIS systems

via DAASC.

2) Navy ATAC Retrograde Parts Repair with Increased Accuracy, Visibility and Traceability with RFID enabled ASN’s sent to DD?? locations via DAASC.

Both of these processes are currently being deployed in Hawaii and require DLMS file exchanges with DAASC. The requirements will be explained below.Process #1: Navy AIS Increased Visibility with Visibility Transactions sent to Navy AIS systems via DAASC.

ii

Phase I Prototype CONOPS

Current State:Currently the Navy AISs receive AE_ transactions in accordance with the current MILSTRIP transaction standard from DAASC related to the movement of supplies or goods through the supply chain. New Functionality:GR will send DLMS 870S transactions with “NL” status code to indicate that a passive RFID read event has occurred as RFID tagged goods and materials are passively observed moving from facility to facility in Hawaii. The 870S transaction will be constructed in part from the data in the 856S ASN EDI document GR will receive from DAASC. Additional fields will be filled in with default data, blank data or prescribed data in accordance with current DLMS guidelines. No change will be made to the current format of the 870S. The RIC in the 870S will be the same as the RIC of the location of the reader and the status code will be set to the value “NL.” Routing Requested:There are 2 instances of GR to manage the RFID infrastructure and visibility transactions at:

GLOBE RANGER SERVER LOCATION GLOBE RANGER SERVER IP ADDRESS

FISC / Navy Ship Yard Facilities (Buildings: 167, 158, 1770, 479)

TBD

Kaneohe Bay Facilities (Building 373) TBD

TABLE 1: GlobeRanger Instances

Each location will have a unique IP address (TBD) and will connect to DAASC over SFTP to push 870S transactions to DAASC. The Kaneohe Bay copy of GR will operate over a commercial broadband connection obtained from a local broadband company. The FISC/Navy Yard copy will operate on a government network provided by DLA.

GR has its own routing table that allows it to create 870S transactions on a per site, per building, per dock door and per direction (in / out) basis. For each unique location, GR can send 870S transactions to DAAS.

In accordance with the ARI implementation, DAAS will send 856S transactions generated by the shipping sites to any of the DoDAACs shown in TABLE 2 to the GR IP addresses identified in TABLE 1.

GR will build 870S transactions based on the 856S transaction data that we will have from DAAS.

DAAS will construct the AE1 transactions from the 870S transactions and route them to the Navy legacy AISs (BirdTrack, RSupply, eRMS and MAT) using current routing methods in place today.

iii

Phase I Prototype CONOPS

DODAACsPearl Harbor

N32253 – Navy Shipyard

N39290 – Building 1770 IMF

N3116B – Building 479 ATAC

Kaneohe Bay

N09124 – Bldg 373 MALS 24

R09124 – Bldg 373 MALS 24

N55668 – Bldg 373 MALS 24

R55668 - Bldg 373 MALS 24

TABLE 2: DODAACs for 856S Transactions Routed to GlobeRanger

Process #2: Navy ATAC Retrograde Parts Repair with Increased Accuracy, Visibility and Traceability with RFID enabled ASN’s sent to DDxx locations via DAASC.Current State:Currently, the eRMS systems at various Navy ATAC parts repair and distribution centers, as part of the pallet manifest process, build files that contain DWK information and send that file to DAASC which uses the information to build/send DWK/527D transactions to the Defense Logistics Agency DDC. Routing of the transactions is determined by the process DAASC uses to route DWK/527D transactions to DDC.

New Functionality:#1: GR is asking DAASC to send a 527D DLMS transaction based on the original DWK file that came from the Navy ATAC parts repair facilities.

Routing Requested:For the March deployment in Hawaii, we are asking that the 527D DLMS transactions be sent to the new GR accounts from originating DODAACs for the following ATAC location DODAACs:

iv

Phase I Prototype CONOPS

DODAACs for ATAC SitesPearl Harbor

N3116B – Building 479 ATAC

Kaneohe Bay

N09124 – Bldg 373 MALS 24

R09124 – Bldg 373 MALS 24

N55668 – Bldg 373 MALS 24

R55668 - Bldg 373 MALS 24

TABLE 3: DODAACs for 527D Transactions Routed to GlobeRanger

#2: GR is asking DAASC to create an account for GR to support the ability for it to send 856S DLMS transactions from the following DODAAC’s to DAAS so DAAS can forward them to DLA DSS.

DODAACs for ATAC SitesPearl Harbor

N3116B – Building 479 ATAC

Kaneohe Bay

N09124 – Bldg 373 MALS 24

R09124 – Bldg 373 MALS 24

N55668 – Bldg 373 MALS 24

R55668 - Bldg 373 MALS 24

TABLE 4: DODAACs for 856STransactions from GlobeRanger to DLA DSS

The routing of the 856S transactions to the DLA DSS will be routed to the proper site using procedures in place at DAASC today.

v