1 / 5

Approved DLMS Change ADC 217

Approved DLMS Change ADC 217. PDC 217, identifies new passive RFID (pRFID) discrepancy codes in the packaging/marking (P300) series

chacha
Download Presentation

Approved DLMS Change ADC 217

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Approved DLMS ChangeADC 217 • PDC 217, identifies new passive RFID (pRFID) discrepancy codes in the packaging/marking (P300) series • Used to identify discrepant, missing pRFID on material, and to identify reader problems/issues which interfere with pRFID processing by DOD receiving organizations • Supports monitoring of vendor performance • Requires contract clauses for pRFID and for WAWF receiving report in accordance with DoD policy • Requires prepositioned materiel receipt (PMR) “pRFID Required Flag” • Pending ERP capability, DAAS assigns flag by contract year for DLA implementation (March 2008) • ADC 297, pRFID-Required Exclusion Table for DLMS 527D PMR • Fine tunes DAAS criteria allowing exclusions e.g. waivers, for selected contractors and types of contracting vehicles

  2. Approved DLMS ChangeADC 217, continued • DLA flooded with pRFID SDRs: 1606 during March 2009 • P314 tag missing 8,863 • P315 tag visibly damaged & unreadable 453 • P316 tag present but unreadable (not visibility damaged) 501 • P317 no corresponding ASN 6,783 • P318 duplicates previously used tag ID 6 • DLA study to determine root cause of high volume - preliminary findings: • DoD AIT implementation issues • pRFID requirement documentation is confusing to suppliers • Suppliers have difficulty finding pRFID documentation

  3. Approved DLMS ChangeADC 217, continued • DLA issues • Invalid SDR reports from depots • Imprecise RFID business rules implementation in DLA • Multiple SDRs reports against a single delivery • Supplier issues • Disregard of requirement • WAWF manual data-entry issues • Receiving Report/Advance Shipment Notice (ASN) submitted after shipment • DCMA issues • Delay in releasing ASN for origin acceptance, shipment reaches depot prior to transaction

  4. Approved DLMS ChangeADC 217, continued • Preliminary recommendations • Provide suppliers with easily understandable RFID requirements summary • Establish time requirement for submission of ASN • Contract requirement and/or DFARS update • Conduct in-situ test of RFID process • Test end-to-end process and assess RFID enterprise efficacy • Track select packages and associated data flow in WAWF, DSS, and EBS from supplier to final destination • Compare package status/location to ASN data flow • Assess timeliness and accuracy of data transfer between WAWF, DSS, and EBS

  5. Approved DLMS ChangeADC 217, continued • Request RFID Tag vendors include “RFID” Acronym on Tags • Resolve reporting incongruities between depots • Assess receiving dock operations • Assess training program • Dispel ‘urban legend’ that ‘common carriers’ are routinely removing RFID tags

More Related