The Nation's Combat Logistics Support Agency
Final Annual
Report for 2010
ADMINISTRATION OF THE DLMS AND DLSS STATUS REVIEW
PART I -- PROPOSED CHANGES
|PROPOSED CHANGE NO. | |REPLY STATUS |
|TITLE |BRIEF DESCRIPTION | |
|DATE ISSUED |OF CHANGE | |
|ACTION OFFICER | | |
|PDC ORIGINATOR | | |
| | |DATE DUE |REC’D FROM |COMMENT |
|PDC 201 |This change allows for a PRN unique to the BSM |12/29/05 | |Approval pending -awaiting associated |
|Use of Purchase Request Number in Logistics |implementation to be used as a transaction | | |procedures from DLA. |
|Reassignment Memorandum Due-in (MILSTRAP DDX/DS |reference number for DI Code DDX Memorandum Due-in| | | |
|527D) (Supply) |transactions initiated from BSM. | | |SPRC mtg 08-01: Followed up for DLA |
|12/08/05 | | | |response. |
|Johnson | | | | |
|DLA | | | |4/11/2011 - Provided DLA with draft PDC|
| | | | |201A with procedures for review/comment|
| | | | |before staffing w/SPRC. DLA response |
| | | | |due 4/29/2011 |
|Proposed Addendum to ADC 221A, Revised Procedures|This proposal supplements ADC 221 with more |05/16/11 |Navy FMS |Concurs with comment. |
|associated with the DLMS Enhancement for |appropriate business rules for conversion of | | | |
|Communication of Unit Price |transaction formats between DLMS and MILS. All | |USMC | |
|(Supply/Finance/MILSTRIP/MILSTRAP/MILSBILLS) |other aspects of ADC 221 are unchanged. This | | |Concurs with comments. |
|03/30/11 |change also provides business rules for additional| |DLA | |
|Hilert |DLMS transactions supporting MILSTRAP and | | |Concurs with this PDC w/o comment. |
|NAVSUP E3 |MILSBILLS functionality that were not addressed in| | | |
| |the original ADC 221. | |Navy |Concurs with Addendum to ADC221A as |
| |Revise procedures for DLA Transaction Services | | |written and submits no additional |
| |Defense Automatic Addressing System (DAAS) | | |changes or amendments. |
| |conversion mapping from DLMS to MILSTRIP legacy 80| | | |
| |record position formats to block the perpetuation | | |Concurs w/o comments. |
| |of any price exceeding 7 positions (5 digits | |Air Force | |
| |dollars and 2 digits cents). | | |No comments/concerns at this time. |
| |Revise procedures for conversion mapping from MILS| |DPAP/IUID | |
| |to DLMS to block the perpetuation of any price | | |Concurs |
| |consisting of all “9”s | |Army | |
|Proposed Addendum to ADC 245C, Notification for |This change expands DoD WebSDR business rules |5/19/11 |USTRANSCOM |Abstains |
|Distribution Depot Product Quality Deficiency |associated with ADC 245. Under these procedures, | | | |
|Report (PQDR) Exhibit Receipt - Product Data |WebSDR will route action or information copies of | |USMC | |
|Reporting and Evaluation Program-Automated |DLMS 842A/W SDR transactions containing a | | |Concurs with comment |
|Information System (PDREP-AIS) Interface |Discrepancy Code Q11 (Returned PQDR Exhibit | |DLA | |
|(Supply/SDR) |Deficiency) from DSS to the PDREP-AIS to update | | |Response date extended to 06/10/11. |
|04/04/11 |the related PQDR’s exhibit information. | | | |
|Hilert | | | | |
|NAVSUP | | | | |
|PDC 288, |DLA’s Enterprise Business System (EBS) requires |3/10/08 |DLA |Concur. No impact ICAN. |
|Revise DLMS 527D to Allow Supply Condition Code |that a supply condition code be included in a | | | |
|with Logistics Reassignment Memorandum Due-In |DDX/DFX Logistics Reassignment Memorandum Due-In| |DLA |DDC, DLA MILSTRAP POC, and EBS concur. |
|(Procurement Instrument Source) (MISTRAP DDX) |transactions. DLA states that if an SCC is not | | |EBS has no impact. |
|(Supply) |included, the transactions will reject at EBS. | | | |
|2/7/08 | | | |Response to PDC staffing note regarding|
|Johnson | | |USAF |current process for DD_/DDX rp 71: |
|DLA | | | |USAF passes SCC 'A' on all DD_/DDX |
| | | | |transactions in rp 71 with the |
| | | | |exception of PR data which would be |
| | | | |blank. |
| | | | | |
| | | | |Concurs |
| | | | | |
| | | |Army |Legacy applications expect a condition |
| | | | |code in the 71 record position for DD_ |
| | | |Navy |transactions. |
| | | | | |
| | | | |Draft ADC 423 sent to Army, Marine |
| | | | |Corps, GSA, on 4/11/2011, requesting |
| | | | |clearer guidance on legacy processing |
| | | | |of SCC in DI Code DDX. Response due |
| | | | |4/29/2011. |
|PDC 299, |Revise the Inventory Control Effectiveness (ICE) |12/15/08 | |Reissued as PDC 299A 6/03/09. |
|Revise the DOD Inventory Control Effectiveness |Report-General Supplies, DD Form 2338-2 (Sep | | | |
|(ICE) Report (General Supplies) and Revise Type |2000), identified in DOD 4000.25-M, DLMS, Volume 2| | | |
|Physical Inventory/Transaction History Codes C |(reference 3a), Chapter 6, and DOD 4000.25-2-M, | | | |
|and Z (Supply) |MILSTRAP (reference 3b), Chapter 7, Appendix A6, | | | |
|11/13/08 |to enhance data analysis and Inter/Intra Service | | | |
|Johnson |reporting. This change proposes a complete | | | |
|DLA-JPIWG |revision of the ICE Report. | | | |
|PDC 299A, |1. Revise DOD 4000.25-2-M, MILSTRAP chapter 7, as |7/06/09 |Navy |Concurs without changes |
|Revise the DOD Inventory Control Effectiveness |revised by ADC 297 (reference 3d), as shown in | | | |
|(ICE) Report (General Supplies) and Revise Type |Enclosures 1 and 2. | |USAF |Comments provided. |
|Physical Inventory/Transaction History Code C and|2. Make corresponding changes to DOD 4000.25-M, | | | |
|Add Code Z (Supply/MILSTRAP) |DLMS, volume 2, chapter 6, as revised by ADC 307 | | |Comments under review by JPIWG Chair. |
|6/03/09 |(reference 3e), (changes not shown). | | | |
|Johnson |3. Revise DD Form 2338-2, Inventory Control | | |Concurs with comments. |
|DLA- JPIWG |Effectiveness Report (ICE) (General Supplies) as | |Army | |
| |shown in the Enclosure | | | |
| |4. Refer to DoD 4000.25-2-M, Appendix 1.2, for | | | |
| |the current ICE Report (General Supplies) format | | | |
| |( | | |
| |strap/AP1_Index.asp). | | | |
| |5. Update DLMS Data Dictionary and MILSTRAP | | | |
| |Appendix 2.2 Type Physical Inventory/Transaction | | | |
| |History Code to revise code C definition and add | | | |
| |new code Z. | | | |
|PDC 301, |Provide alternative to LASE by using DOD EMALL |6/30/08 |USTRANSCOM |Abstains |
|Alternative to Logistics Asset Support Estimate |Supportability Analysis Stock Out Report (SA-SOR) | | | |
|(LASE) Process for DLA Managed Assets Using DOD |Tool for DLA managed assets. DLA indicates this | |Navy | |
|EMALL Supportability Analysis Stock Out Report |tool is only available for DLA managed assets, | | |No objection to PDC as written. |
|Tool (Supply/MILSTRAP) |hence LASE would still be required for Service | | | |
|5/29/08 |managed assets, unless the Services can also | |Army |Nonconcurred on 6/20/08. DLMSO asked |
|Johnson |identify alternatives for providing the asset | | |Army for more information regarding |
|DLA |information. | | |nonconcurrence on 6/23/08 and followed |
| | | | |up for response on 7/20/08, 8/6/08, and|
| | | | |9/3/08. |
| | | | | |
| | | | |Army withdrew their nonconcurrence to |
| | | | |PDC 301. |
| | | | | |
| | | | |1/17/2010 Army submitted related PDC to|
| | | | |eliminate Army use of LASE under their |
| | | | |modernized system (LMP). |
|PDC 309, |a. This change documents the new procedures that | | |Awaiting finalization of reengineering |
|MAPAD Update to Military Assistance Program |are applicable to the reengineered MAPAD. | | |prior to publishing as an ADC |
|Address Directory Procedures |b. The MAPAD is undergoing a reengineering effort | | | |
|(MAPAD) |by DAASC. In its current form, all updates to | | | |
|4/23/08 |MAPAD address information are handled by DAASC. | | | |
|Hammond |The reengineered version will allow the Central | | | |
|PRC Chair |Service Points (CSP) to create and maintain data | | | |
| |directly through an internet-based application. | | | |
| |These enhancements are intended to improve the | | | |
| |overall quality of the MAPAD data. | | | |
|Proposed Addendum to ADC 317B, Action Activity |Action activities often respond to SDRs from |03/28/11 |USTRANSCOM/ |Concur |
|Replies to Transshipper-Prepared Supply |transshippers with replies that make it apparent | |AMC | |
|Discrepancy Reports (SDRs) (Supply/SDR) |that the SDR was processed as if it were reported | | | |
|02/10/11 |by the customer. For example, action activities | |Air Force | |
|Hilert |sometimes respond that credit is recommended or | | |Concurs with ADC 317B without comments.|
|PRC Chair |that the materiel was shipped as requisitioned. | | | |
| |Establishing an edit on inappropriate | |USMC |Has reviewed the subject PDC and |
| |disposition/reply codes will help ensure more | | |concurs as written. |
| |appropriate responses are provided. This proposal | | | |
| |is provided to formally document the inappropriate| | | |
| |replies so that a standard approach can be used by| | |Published as Approved Addendum to ADC |
| |all DoD applications that prepare SDR replies. | | |317B on 06/01/11 |
| |Although replies are not required when the SDR | | | |
| |Action Code 3B is used, many applications allow | | | |
| |systemic generation of Disposition/Reply Code 144.| | | |
| |This is appropriate; however, forwarding a high | | | |
| |volume of these replies via email (as used by | | | |
| |transshippers) clutters the in-box and obscures | | | |
| |emails with more significant responses. | | | |
|PDC 330, |Provides a new DS 527R beginning segment action |12/08/08 |Navy |Interposes no objection to the PDC as |
|Revisions to DS 527R to Add Code for MILSTRAP DRB|code to provide functionality of MILSTRAP | | |written. |
|Functionality and to Address Enhancement for |(reference 3a) (Document Identifier (DI) Code | | | |
|Advice Codes Used with Receipt and Response to |DRB-Materiel Receipt Acknowledgement (MRA) Reply | | |PDC 330 was approved and released as |
|Inquiry for Materiel Receipt (Supply) |to Follow-up. | | |Request for Implementation Date for ADC|
|11/06/08 | | | |313 on 12/24/08. Refer to DLMS Status |
|Johnson | | | |Report Part II - Request for |
|PRC Chair | | | |Implementation Dates. |
|PDC 341, |This change addresses DOD IG Report D-20008-090 |3/23/09 |USTRANSCOM |Abstains |
|Proposed Changes to DLMS and MILSTRAP to Address |recommendations related to DOD 4000.25-2-M, |Response due | | |
|Owner/Manager Research of Inventory Adjustments |MILSTRAP |date extended |GSA | |
|(Accounting Error) (MILSTRAP D8B/D9B, DLMS 947I) | |to 5/01/09. | |Agree with concept of inventory |
|(Supply/MILSTRAP) | | | |reconciliation; however, any review to |
|3/06/09 | | | |implement any of the supporting |
|Johnson | | | |transactional requirements outlined in |
|PRC Chair | | | |this proposal are being deferred for |
| | | | |our supply system modernization. |
| | | | | |
| | | | |Concurs |
| | | | | |
| | | |DFAS |PRC Chair to restaff as PDC 341A due to|
| | | | |significant number of comments |
| | | | |received. |
| | | | | |
| | | | | |
| | | | | |
|PDC 341A, |This change addresses DOD IG Report D-20008-090 |6/30/09 |USTRANSCOM |No comments. |
|Proposed Changes to DLMS and MILSTRAP to Address |recommendations related to DOD 4000.25-2-M, | | | |
|Owner/Manager Research of Inventory Adjustments |MILSTRAP | |USAF | |
|(Accounting Error) (MILSTRAP D8B/D9B, DLMS 947I) |PDC 341 proposed changes to MILSTRAP to address | | |Granted extension to 7/14/09 as |
|(Supply/MILSTRAP) |the DODIG report recommendations. However many | | |requested. |
|6/04/09 |comments were received to PDC 341 and DLA | |GSA | |
|Johnson |expressed concern that PDC 341 intertwined | | |No comments. |
|PRC Chair |procedures for Inventory Adjustments for | |Army | |
| |Accounting Error with procedures for Inventory | | |Concurs with comments. |
| |Adjustments associated with Physical Inventory in | | | |
| |a way which might cause confusion. This revised | | | |
| |PDC attempts to more clearly separate and identify| | |Published as ADC 414 on 03/28/11 |
| |the owner/manager requirements for research of | | | |
| |Inventory Adjustments (Accounting Errors). | | | |
|PDC 344, |This change to the WAWF ASN authorizes additional |06/22/11 |USTRANSCOM |Approves with comment. |
|Revise Advance Shipment Notice (ASN) (DLMS |data content in support of DMLSS requirements for | | | |
|Supplement (DS) 856) for Additional Content for |vendor shipment notice. The change adds new codes | |Army | |
|Defense Medical Logistics Standard Support |for materiel identification; allows notification | | |Concurs |
|(DMLSS)/Wide Area Workflow (WAWF) Interface |that the contents require special handling due to | |Air Force | |
|(Supply/Contract Administration/Finance) |perishable, refrigerated, or hazardous items; and | | |Concurs with PDC 344, and concur with |
|06/07/11 |includes additional characteristics relevant to | | |the modifications. |
|DMLSS |these items including batch/lot information. | | | |
| | | |DLA |Concurs without comment. |
|PDC 365, |This change revises applicable DS to carry SFIS |1/17/11 |USAF |Requested due date extension until |
|DLMS Revisions for Standard Financial Information|data elements. This change proposal describes two | | |01/28/11 granted |
|Structure (SFIS) (Supply/Finance) |concepts for exchanging SFIS data: the proposed | | | |
|11/16/10 |approach to carry all SFIS data in DLMS, as | |USTRANSCOM |Request DLMSO include wording in ADC |
|Hammond |discrete data elements, and an alternative to use | | |that allows for a 90 day period between|
|BTA |referential data exchange as the primarily method | | |when the ADC is released and when it is|
| |for acquiring SFIS data elements. This PDC is | | |effective, in order to provide that |
| |intended to provide guidance for “Target” ERP AISs| | |time to IGC PMO to make any necessary |
| |to allow them to transform and modernize with the | | |changes to our system. |
| |capability to be both SFIS and DLMS compliant as | | | |
| |mandated by current DoD policies. | | |Comments provided. |
| | | |DMLSS Program, | |
| | | |JMFLDC | |
| | | | | |
| | | |GSA |Preference for referential data |
| | | | |(approach 2) w/ comments |
| | | | | |
| | | |DLA Supply |Comments provided. |
| | | | | |
| | | |DFAS | |
| | | | |Responded with comments and did not |
| | | | |endorse either |
| | | | |approach in the PDC. |
| | | |Air Force | |
| | | | |Preference for referential data |
| | | |USMC | |
| | | | |Concurs with comments. |
| | | |Navy | |
| | | | |Selection of referential data is the |
| | | | |preferred approach. |
| | | |DLA | |
| | | | |Prefers referential data using fund |
| | | | |code |
| | | |HQDA DCS | |
| | | |G-44(S) |Prefers option 2 of DLMS proposed |
| | | | |approaches as stated in PDC 365. |
|PDC 377, |1. This change provides clarification and enhanced|9/24/10 |HQMC |Concurs as written. |
|Automated Data Capture for Serialized Item |procedures supporting automated data capture in |Due date for | | |
|Shipments and Preparation of the Issue |association with the preparation of the DD Form |comments has | |Due date extended to 10/5/10 for review|
|Release/Receipt Document (IRRD) (DD Form 1348-1A |1348-1A or DD Form 1348-2. |been extended |DLA |and analysis. – comments provided |
|or DD Form 1348-2) Continuation Page |2. This change establishes a mandatory |to 10/29/10. | | |
|(MILSTRIP/Supply) |continuation page for the DD Form 1348-1A or DD | | |Abstains |
|8/10/10 |Form 1348-2 when used for serialized item | |USTRANSCOM | |
|Hilert |shipments as required by DoD or intra-Component | | | |
|HQMC, PRC Chair, and USTRANSCOM |policy or for UIT. The continuation page contains| |USAF |Concurs with PDC 377 without comments. |
| |machine readable bar code symbols for the encoded | | | |
| |content information to include the serial numbers | | |Concurs w/ comments |
| |and UII. | |Navy | |
| | | | |Concurs |
| | | |Army | |
| | | | |Published as ADC 399 on 03/18/11 |
|PDC 384, |This change proposes procedures and a new DLMS |4/30/10 |Navy |Concurs |
|New DS 940S, Warehouse Service Request (for |transaction to communicate a Warehousing Service | | | |
|Materiel Protection/Re-Warehousing, Staging, and |Request (DS 940S) including requests for | |DLA |Concurs. |
|Picklist/Callout), New DS 943A, Warehouse Service|re-warehousing and/or protection, staging, or | | | |
|Advice, and Associated Procedures under Navy BRAC|picklist/callout actions, to the Distribution | |USMC |Concur without comment |
|SS&D/IMSP (Supply) |Depot in support of NSY and FRCs operating under | | | |
|4/20/10 |the Navy-DLA BRAC 2005 SS&D CONOPS. A new DLMS | |DLA Finance |Concurs |
|Hilert |transaction communicating Warehouse Service Advice| | | |
|DLA |(DS 943A) allows the Distribution Depot to provide| |Army | |
| |positive or negative status on the requested | | |Concurs |
| |action. | |DFAS | |
| | | | |No comment |
| | | | | |
| | | | |Procedures revised and supplemented for|
| | | | |USMC in PDC 384A |
|PDC 384A, |This change updates data content applicable to the|9/17/10 |USTRANSCOM |Abstains |
|Procedures and Data Content for DLMS Warehouse |Navy and highlights impact to associated | | | |
|Service Request (940S) and Warehouse Service |procedures. Navy procedures not specifically | |USMC | |
|Advice (943A) under Navy and Marine Corps BRAC |revised in this document are unchanged from | | |Initial non-concurrence withdrawn. |
|(Supply) |original PDC 384 staffing | | | |
|9/02/10 |This change updates data content applicable to the| | | |
|Hilert |Marine Corps and establishes the associated | | |ADC being finalized |
|DLA |procedures. | | | |
|PDC 399, |To establish a new SCC T for ‘Serviceable |5/03/10 |Navy |Concurs with PDC 399 as written and |
|Proposed New Supply Condition Code (SCC) T, |(Training Use Only)’. | | |submits no additional changes or |
|Serviceable (Training Use Only) (Supply/MILSTRAP)| | | |amendments. |
|4/01/10 | | | | |
|Johnson | | | |Concurs. SCR will be required. |
|Navy/NAVSUP | | |DLA | |
| | | | |Concurs |
| | | | | |
| | | |Army |Nonconcur with comment |
| | | | | |
| | | |USAF |Nonconcur with comments. |
| | | | | |
| | | |USMC |No objections/comments. |
| | | | | |
| | | |DPAP WAWF/IUID | |
| | | | | |
| | | | |PDC 399 will be discussed at the June |
| | | | |21-23, 2011 SPRC Meeting. |
|PDC 400, |Army decision is not to initiate a requirement for|4/26/10 |USA | Concur |
|Exclude Army from using the Logistics Asset |programming this capability in their modernized |5/03/10 | | |
|Support Estimate (LASE) Process (Supply/MILSTRAP)|system aka Logistics Modernization Program (LMP). | |USN |Concur. The Navy's position is that we|
|3/25/10 |Army modernized system will not provide the | | |recommend elimination of the LASE |
|Johnson |ability for customers to submit LASE transactions | | |process. We have not found any |
|Army, HQAMC |to Army. In addition, under LMP, Army does not | | |interest in this process within Navy, |
| |generate LASE transactions to other Components, | | |and we do not plan to continue this |
| |nor will Army use LASE on an intra-Army basis. | | |process with Navy ERP. |
| |Army is not offering an alternative to LASE, but | | | |
| |instead requests its use with Army be | | |The Air Force concurs with PDC. We |
| |discontinued. | | |agree with the Army and Navy position |
| | | |USAF |that we eliminate the LASE process. In|
| | | | |fact, the Air Force does not plan to |
| | | | |continue this process with Air Force |
| | | | |ERP. |
| | | | | |
| | | | |This Headquarters has reviewed the |
| | | | |impact of the cancellation of LASE to |
| | | | |Marine Corps and concurs with |
| | | |USMC |cancellation of LASE. |
| | | | | |
| | | | |Concurs |
| | | | | |
| | | | |Do not see any impact to WAWF, GFP |
| | | | |CONOPS, IUID Registry, GFP Hub, or IUID|
| | | |DLA |Policy |
| | | | | |
| | | |DPAP contractor|Abstains |
| | | |support | |
| | | | | |
| | | | | |
| | | |USTRANSCOM | |
|PDC 403, |This change revises DLMS/MILSTRAP/SDR procedures |03/17/11 |USTRANSCOM |Abstains |
|Revised Procedures for Processing Depot Returns |as follows: | | | |
|(including Receipt and Supply Discrepancy Report)|To support DLA Distribution Depot processing and | |DLA | |
|(DLMS/MILSTRAP and SDR) |automatic disposal of materiel categorized as | | |Comments provided. |
|01/31/11 |Supply Condition Code (SCC) H, Unserviceable | |Air Force | |
|Hilert |(Condemned).[1] | | |Non-concurs. |
|DLA |To revise the dollar value associated with | |USMC | |
| |automatic disposal | | |Has reviewed the subject PDC and |
| |To revise the time standard for providing | | |concurs as written. |
| |disposition on materiel identified upon receipt in| |HQDA DCS | |
| |SCC K, Suspended (Returns).[2] | |G-44(S) |Concurs with PDC 403 with comment. |
| |To clarify manual procedures associated depot | | | |
| |receipt of material where the NSN is not known and| |Navy | |
| |offer an automated alternative. | | |Concur with comments |
| |Administrative revisions to MILSTRAP procedures to| | | |
| |ensure consistency with SDR procedures under DLMS | | | |
| |Chapter 17. | | | |
| |This change also establishes/documents enhanced | | | |
| |procedures for improving transmission of SDRs to | | | |
| |the appropriate owner/manager/shipping activity. | | | |
|PDC 405, |This change request proposes adding a new Quantity|4/30/10 |USTRANSCOM |Abstains |
|DLMS 947I Inventory Adjustment to Identify Loss |or Status Adjustment Reason Code ‘AP’ for use on |DLA Due date | | |
|due to Destructive Test in Support of Navy-DLA |DLMS 947I Inventory Adjustment loss (MILSTRAP DI |extended |Navy | |
|BRAC SS&D/IMSP (Supply/Finance) |Code D9_ functionality), to indicate that the |5/14/10 | |Concurs |
|4/15/10 |inventory adjustment loss is the result of | |USMC | |
|Johnson |material being destroyed in test. | | |Concur without comment |
|DLA | | |USAF | |
| | | | |Concurs without comment. |
| | | |Army | |
| | | | |Concurs |
| | | | | |
| | | | |Due date extended to 5/14/10 for DLA |
| | | | |review and analysis |
| | | | | |
| | | | |Published as ADC 378 on 03/16/11 |
|PDC 409, |Request that DLA Transaction Services Defense |05/09/11 |USTRANSCOM |Abstains |
|Requisition Document Number Julian Date Edit |Automatic Addressing System (DAAS) implement a | | | |
|(MILSTRIP/Supply) |permanent edit to check for an appropriate Julian | |DSCA | |
|03/24/11 |Date in requisitions prior to forwarding to DLA | | |Comments provided. |
|Hilert |for processing. | |IUID and WAWF | |
|DLA | | |Contract |No comment. |
| | | |Support | |
| | | | | |
| | | |HQDA D-44(S) | |
| | | | | |
| | | |Air Force |Concurs with PDC 409 |
| | | | | |
| | | |USMC | |
| | | | |Concurs with PDC 409 |
| | | | | |
| | | | |Response date extended to 06/01/11. |
|PDC 417, |This change adds 3-Hotel-(Alpha) to the existing |06/22/11 |Joint Staff |Acknowledging receipt and concurrence |
|Revision to Project Code Procedures Authorizing |3-Juliet-(Alpha) series project codes for the | | |with PDC 417. |
|3H-Series Project Codes for Assignment by the |Joint Materiel Priorities and Allocation Board | |USTRANSCOM | |
|Joint Material Priorities Allocation Board |(JMPAB) use. | | |Abstains |
|(JMPAB) | | | | |
|5/23/11 |This change also reflects administrative | | | |
|Madrigal |updates/clarification of project code procedures, | | | |
|J627 |including procedures for dissemination of | | | |
| |CJCS-assigned project codes. | | | |
|PDC 419, |This change proposes new procedures and updates to|10/22/10 |USTRANSCOM |Abstains |
|Revise DLMS 527D Prepositioned Materiel Receipt |DLMS transactions to communicate enhanced 527D PMR| | | |
|(PMR) and 527R Receipt and Associated Procedures |data and 527R Receipt data between the MCMC and | |USAF | |
|to Support Marine Corps BRAC SDI |DLA at the Distribution Depots operating under the| | |Concurs with PDC w/o comments. |
|Supply/Logistics |DSS. | | | |
|10/07/10 | | |USMC |Concurs with comments. |
|Johnson | | | |- Additional USMC comments to PDC |
|DLA | | | |provided 4/12/2011. |
| | | | | |
| | | |DFAS |No comment |
| | | | | |
| | | |Navy |Concurs |
| | | | | |
| | | |Army |Concurs |
|PDC 424, Shipment Status for Local Delivery |To establish procedures for use of the DS 856S, |03/07/11 |DLA Transaction|The SDR Group at DLA Transaction |
|Manifested, Outbound MILS Shipments on Behalf of |Shipment | |Services |Services didn't see any impact to SDR |
|On-Base Customers, Re-Warehousing Actions between|Status, to document the application of pRFID | | |in this PDC. |
|Distribution Depots, and non-MILS Shipments to |tagging for shipments that are either local | | | |
|Off-Base Customers, with Passive Radio Frequency |delivery manifesting to base customers, outbound | |USTRANSCOM | |
|Identification (RFID) (Supply/Transportation/AIT)|MILS shipments on behalf of on-base customers, | | |Approves PDC 424 |
|03/07/11 |rewarehousing | |Navy | |
|Daverede |actions/transshipments between Distribution Depots| | | |
|DLA |in support of ‘Home’ Industrial Activity site and | | |Concurs with PDC 424 as written and |
| |‘Forward Support’ Industrial Activity site | | |submits no additional changes or |
| |material requirements, or outbound non-MILS | | |amendments. |
| |shipments (e.g., DD1149) to off-base customers. | |DFAS | |
| |Implementing pRFID | | |No comment. |
| |tagging on these shipments will provide enhanced | |DLA | |
| |intransit visibility and enable use of pRFID | | |Concurs without comment |
| |tag reads to trigger the automated receiving | |Air Force | |
| |business processes/transactions at the customer | | |Withdraws its non-concur. AF now |
| |location. | | |concurs with PDC |
| | | | |424, w/comment. |
| | | |USMC | |
| | | | |Concurs as written. |
| | | |HQDA DCS | |
| | | |G-44(S) |Concurs with PDC 424 without comment. |
| | | | | |
| | | | | |
| | | | |Published as ADC 417 on 04/26/11 |
|PDC 428, |To modify the definition and usage of Advice Code |11/18/10 |Army |Requested extension until |
|Advice Code 2W for Free Issue (MILSTRIP/Supply) |2W restricting to Navy and Marine Corps only. | | |4 Jan 11 granted. |
|11/03/10 |Under MILSTRIP, this code was originally | | | |
|Hilert |authorized for FMS customers only. However, DAAS | |DLA |Concurs |
|NAVSUP |history from 2007 to present shows no Security | | | |
| |Assistance requisitions citing Advice Code 2W. | |USAF |Concurs |
| |Army customers appear to be using the code (plus | | | |
| |USCG requisition in 2007). All Components | |USMC |Concurs |
| |(including International Logistics Control Offices| | | |
| |(ILCOs) and the Defense Security Cooperation | |DSCA |Concurs with PDC 428 as it has no |
| |Agency (DSCA) were asked to verify if there is a | | |impact on the Army and Navy FMS |
| |continued requirement for the use of Advice Code | | |community. |
| |2W for Military Assistance Program/Military | | | |
| |Assistance Service Funded (MAP/ MASF). | | |Published as ADC 418on 04/06/11 |
|PDC 429, |Administrative change to update RIC field note in |05/23/11 |USTRANSCOM |Approves with comment |
|Administrative Revisions to DLMS Supplements to |the DLMS to remove obsolete references to future | | | |
|Remove Obsolete Routing Identifier Code (RIC) |streamlining. | |Navy | |
|“Streamline” Notes and Update MILSTRIP/DLMS |Administrative update to the RIC assignment rules | | |Concurs with PDC429 as written and |
|Documentation Associated with Routing Identifiers|to reflect Washington Headquarter | | |submits no additional changes or |
|(Supply/MILSTRIP/DODAAD) |Service (WHS) is now responsible for update of | | |amendments. |
|04/07/11 |“Other DoD DoDAACs (H series)”. | | | |
|Hilert | | |DLA |Concurs without comment. No system |
|PRC Chair | | | |impacts. |
| | | | | |
| | | |USMC |Concurs |
| | | | | |
| | | |HQDA G-44(S) |Concurs with PDC 429 without comment. |
|PDC 430, |This change documents and incorporates the |04/28/11 |USTRANSCOM |Abstains |
|To Map Intra-Army Document Identifier (DI) Code |intra-Army use DI Code BZE data requirements in | | | |
|BZE, Consumption Report (Government Furnished |DLMS. The data provides value-added information | |IUID and WAWF | |
|Materiel (GFM)), to the DLMS 846I (Supply) |for Army. | |Contract |No comment. |
|003/29/11 | | |Support | |
|Hilert | | | | |
|USAMC LOGSA | | |Air Force | |
| | | | | |
| | | |Army |Concurs |
| | | | | |
| | | |USMC |Granted extension to 16 May. |
| | | | | |
| | | | |Concurs |
|PDC 432, |DLA Disposition Services will require the use of a|03/14/11 |USTRANSCOM |Approves with recommendation that the |
|Intra-DLA Revisions to Procedures and DLMS 511R |unique number referred to as the Disposal | | |ADC contain verbiage directing |
|Requisition to Support Directed Release of |Consolidation Number (DCN) to support the grouping| | |implementation to occur no sooner than |
|Material (Post-Post Action) by DLA Disposition |of property issued during the disposal process. A| | |90 days from date of issuance. |
|Services Field Offices under Reutilization |separate qualifier is being requested so that the | | | |
|Business Integration (RBI) |DCN can be uniquely identified on the 511R | | |No comment. |
|(Supply/Logistics) |transactions set. DLA Disposition Services will | |DFAS | |
|02/11/11 |require the use of a new data element to designate| | |Concurs without comment. Any system |
|Hilert |the Disposition Category Code and Disposition | |DLA |changes required will be part of the |
|DLA |Sub-Category Code which will help EBS to determine| | |RBI Build effort. |
| |what type of the sales document to create when a | | | |
| |511R DLA-Directed MRO transaction is received from| | |Concurs with PDC 432 w/o comments. |
| |DSS. The two disposition categories are Disposal | | | |
| |(DS) and Sales (SL). The only applicable | |Air Force |Concurs as written. |
| |sub-categories are associated with sales and are | | | |
| |identified as Commercial Venture (CV), and Scrap | | |Concurs with PDC 432 as written and |
| |Venture (SV). | |USMC |submits no additional changes or |
| | | | |amendments. |
| | | |Navy | |
|PDC 433, |This change covers modifications to the 527D PMR |02/04/11 |USTRANSCOM |Abstains |
|Intra-DLA Revisions to Procedures and DLMS 527D |(also known as Advance Receipt Information (ARI) | | | |
|Pre-Positioned Materiel Receipt (PMR) to Add |in DLMS). With the inclusion of the RBI | |USAF | |
|Container ID for use with Relocation of Material |functionality in DSS and EBS, the 527D PMR | | |Concurs without comment. |
|between DLA Disposition Field Offices Under RBI |transaction needs to be updated to include passing| |Navy | |
|(Supply) |of Container Identification (ID). | | |Concurs with PDC 433 as written and |
|01/05/11 | | | |submits no additional changes or |
|Johnson | | | |amendments. |
|DLA Disposition Services | | | | |
| | | |DFAS |No comment. |
| | | | | |
| | | |DLA |Concurs w/ comment. |
| | | | | |
| | | |USMC |Concurs as written. |
| | | | | |
| | | |IUID and WAWF |We do not see any impact on WAWF or the|
| | | |Contract |IUID Registry |
| | | |Support | |
| | | | | |
| | | |Army | |
| | | | |Concurs. |
| | | | | |
| | | | |Published as ADC 410 on 2/25/11 |
|PDC 434, |This change enhances the business process using |07/20/11 |USTRANSCOM |Approves |
|Intra-DLA Revisions DLMS 527R Receipt and |the DLMS 527R Receipt transaction to accommodate | | | |
|Associated Procedures for Use by DLA Disposition |the additional information that will be needed | | | |
|Services under RBI |when NSN or LSN material is turned in to a DLA | | | |
|06/20/11 |Disposition Services Field Office, and the field | | | |
|Johnson |office processes a receipt in DSS and sends the | | | |
|DLA |receipt transaction to the DLA Disposition | | | |
| |Services ICP (EBS). The transaction will provide | | | |
| |EBS with visibility of the inventory owned by DLA | | | |
| |Disposition Services as it is receipted. | | | |
|PDC 435 |EBS plans to leverage the existing 832N |02/14/11 |USTRANSCOM |Abstains |
|Intra-DLA Revisions to the DLMS Supplement 832N, |transaction to transmit catalog information to DSS| | | |
|Catalog Data Support, and associated Procedures |when EBS creates or updates a Local Stock Number | |Navy | |
|under RBI (Supply/logistics) |(LSN). EBS will use an LSN when a DLA Disposition | | |Concurs with PDC 435 as written and |
|01/13/11 |Services item cannot be identified by a National | | |submits no additional changes or |
|Hilert |Stock Number (NSN) or when an item is turned into | | |amendments. |
|DLA |a DLA Disposition Services Field Office as a | | | |
| |quantity less than the FLIS unit of measure. | |DLA |Provided comments. |
| | | | | |
| | | |Air Force |Concurs with PDC 435 without comments. |
| | | | | |
| | | | |Concurs with comments. |
| | | |USMC | |
| | | | |Concurs without comment. |
| | | |HQDA DCS | |
| | | |G-44(S) | |
|PDC 436, |This transaction will be used to communicate a |02/14/11 |Navy |Concurs with PDC 436 as written and |
|IntraDLA Change - Establish New DLMS Supplement |change in disposition category code between DLA | | |submits no additional changes or |
|846C, DLA Disposition Category Update Transaction|Disposition Services Inventory Control Point (ICP)| | |amendments. |
|and Procedures for use by DLA Disposition |(Routing Identifier Code S9D/S9W) (which use EBS) | | | |
|Services Under RBI (Supply) |and the DLA Disposition Services Field Offices | | |No comment. |
|01/14/11 |(which use DSS). The Disposition Category Code | |DFAS | |
|Johnson |assigned to a Disposal Turn-In Document (DTID) | | |Concurs with PDC 436 without comments |
|DLA |will impact which system will be responsible for | |Air Force | |
| |issuing the inventory and the stowage process. In| | |Concurs as written. |
| |addition, a Disposition Sub-Category Code will be | | | |
| |added that will alert DSS if the item is a | |USMC |Concurs without comment |
| |Commercial Venture (CV) or Scrap Venture (SV). | | | |
| | | |Army | |
|PDC 437, |This PDC covers modifications to the 846R Location|03/09/11 |USMC |Has reviewed subject PDC and concurs as|
|Revise DLMS Supplement (DS) 846R, Location |Reconciliation Request transaction (846R beginning| | |written. |
|Reconciliation Request in Support of RBI (Supply)|segment BIA02 Report Type Code ‘LC’ (MILSTRAP DI | | | |
|02/10/11 |Code DZH functionality)) and the Location | |Navy |Concurs with PDC 437 as written and |
|Madrigal |Reconciliation Notification transaction (846R | | |submits no additional changes or |
|DLA |beginning segment BIA02 Report Type Code ‘X4’ | | |amendments. |
| |(MILSTRAP DI Code DZN functionality)). With the | | | |
| |inclusion of the RBI functionality in DSS, this | | |Concurs with 437 846R with comment. |
| |transaction needs to be updated to include passing| |HQDA DCS | |
| |a DTID number, and the DEMIL code. DLA | |G-44(S) | |
| |Disposition Services use the DTID number to | | | |
| |uniquely identify individual property, as well as | | | |
| |performing all inventories and accounting | | | |
| |processes. The DTID number is also used to track,| | | |
| |control and perform all disposition of all DLA | | | |
| |Disposition Services property. | | | |
|PDC 438, |To establish an interface through DLA Transactions|02/05/11 |USTRANSCOM |Concurs |
|Hazardous Material/Hazardous Waste (HM/HW) |Services to electronically convey HM/HW HWPS | | | |
|Profile Transaction, DS 996H, in Support of |information for shipments to DLA Disposition | |Navy | |
|Reutilization Business Integration (RBI) |Service Field Offices. The interchange will | | |Concurs with PDC438 as written and |
|(Supply/DLA Disposition Services) |accommodate the existing GenComm Standard v5.0 in | | |submits no additional changes or |
|01/05/11 |either pipe-delimited or XML schema transaction | | |amendments. |
|Daverede |formats from either GenComm or the individual | | | |
|DLA |Component generator systems. DLA Transactions | |Air Force |Concurs with PDC without comments. |
| |Services will convert these transactions to a DS | | | |
| |996H, HM/HW, Electronic Data Interchange | | |Concurs with PDC 444 with comments. |
| |transaction for routing to the applicable DLA | |USMC | |
| |Disposition Service Field Office. | | |We do not see any impact on WAWF or the|
| | | | |IUID Registry. |
| | | |IUID and WAWF | |
| | | |Contractor | |
| | | |Support | |
| | | | |Concurs with PDC 438 without comment. |
| | | |HQDA DCS | |
| | | |G-44(S) | |
|PDC 439, |DLA Disposition Services requires the use of a |01/17/11 |USTRANSCON |Abstains |
|Intra-DLA change to |unique number to support the grouping of property | | | |
|Revise DLMS 867I Issue to Support Relocation of |relocated during the disposal process. The unique | |Navy | |
|Material between Disposition Field Offices to |number, the Disposal Consolidation Number, is a 10| | |Navy concurs with PDC439 as written and|
|Support Reutilization Business Integration (RBI) |digit number with positions 1-3 equal to the DLA | | |submits no additional changes or |
|12/17/10 |Disposition Service Field office RIC and positions| | |amendments. |
|Johnson |4-10 equal to a unique alphanumeric serial number.| | | |
|DLA |A separate qualifier is being requested so that | |DLA |Concurs with this PDC w/o comment. |
| |the DCN can be uniquely identified on the 867I | | |System change will be captured as part |
| |Issue transaction. | | |of RBI implementation. |
| |Since the document number for the transaction will| | | |
| |become part of a consolidated RDO, DLA Disposition| | |No impact. |
| |Services will also require the perpetuation of the| |WAWF/ | |
| |original DTID, as a secondary number in the | |IUID | |
| |transaction, to support identifying inventory at a| | |Concur as written |
| |level lower than the document number or DCN. | |Army | |
| |Therefore, the DTID number will be included on | | |No comment. |
| |each individual issue transaction under this | |DFAS | |
| |process. | | |Concurs w/o comments. |
| | | |Air Force | |
| | | | |Concurs as written. |
| | | |USMC | |
| | | | |Published as ADC 409 on 2/14/11 |
|PDC 440, |The 869C Requisition Cancellation is used to |02/14/11 |USTRANSCOM |Abstains |
|Revises DS 869C, Requisition Cancellation and |cancel customer requisitions from DLA Disposition | | | |
|associated Procedures in Support of RBI (Supply) |Services. With the inclusion of the RBI | |Navy | |
|01/14/11 |functionality in EBS, this transaction needs to be| | |Concurs with PDC 440 as written and |
|Hilert |updated to include passing a DTID number | | |submits no additional changes or |
|DLA | | | |amendments. |
| | | | | |
| | | |DFAS |Has no comment. |
| | | | | |
| | | |DLA |Submits comments. |
| | | | | |
| | | |Air Force |Concurs with PDC 440 without comments. |
| | | | | |
| | | | |Concurs as written. |
| | | |USMC | |
| | | | |Concurs with PDC 440 with comment. |
| | | |HQDA DCS | |
| | | |G-44(S) | |
|PDC 441, |This change updates the DLMS 940R Material Release|02/19/11 |USTRANSCOM |Abstains. |
|Intra-DLA Revisions to the DLMS 940R, Release |transaction sent between DLA Disposition Services | | | |
|Order, and associated Procedures to Support |ICP (using EBS) and the DLA Disposition Services | |USMC | |
|Directed Release of Material under RBI (Supply) |Field Offices (using DSS). EBS will send DSS a | | |Concurs as written. |
|01/19/11 |940R when property is ready to be released to a | |DLA | |
|Hilert |customer. It will also be sent to communicate a | | |Concurs. |
|DLA |cancellation, and to communicate a follow-up | |DFAS | |
| |request for the status of an action. This will | | |Has no comment. |
| |all be done at the DTID level of detail, except as| |Air Force | |
| |noted for small arms/light weapons (SA/LW). | | |Concurs with PDC 441 w/o comments. |
| | | | | |
| | | |Army |Concurs w/comments |
| | | | | |
| | | |HQDA DCS |Concurs with PDC 441 without comment. |
| | | |G-44(S) | |
|PDC 442, |The 945A transaction will be modified to include |02/26/11 |USTRANSCOM |Requests implementation no sooner than |
|Intra-DLA Revisions to the DLMS 945A, Materiel |passing reasons for rejection in response to a MRO| | |90 days from issuance. |
|Release Advice, Cancellation Reason Code, |that had been sent from EBS to DSS. Depending on | | | |
|Management Code, and Associated Procedures under |the issue encountered in DSS that does not allow | |Navy |Concurs with PDC 442 as written and |
|RBI (Supply) |the delivery to be fully delivered (or only | | |submits no additional changes or |
|01/26/11 |partially delivered), a reason for rejection will | | |amendments |
|Hilert |be included in the 945A sent back to EBS. This | | | |
|DLA |reason for rejection will be utilized by EBS | | |Provided comments. |
| |either to cancel the sales order in its entirety | |DLA | |
| |by sending separate transactions for each | | |Concurs with PDC 442 without comment. |
| |DTID or to cancel a specific line item based on | |HQDA DCS | |
| |the DTID Number passed in the transaction. | |G-44(S) | |
|PDC 443, |This change proposes interim and longer term |04/06/11 |NSA |Concurs |
|DOD Activity Address Directory (DoDAAD) |procedures to correct inconsistent Break Bulk | | | |
|Modification to Break Bulk Point (BBP) |Points (BBPs) for TAC1 and TAC2 addresses. | |DODIG |Concur with no comments. |
|(DoDAAD/Supply) | | | | |
|03/07/11 | | |USTRANSCOM |Abstains |
|Hammond | | | | |
|PRC Chair | | |Army | |
| | | | |Concurs without comment. |
| | | |DPAP IUID/WAWF | |
| | | | |Has no comment. |
| | | |DLA | |
| | | | | |
| | | |DFAS | |
| | | | |Concurs without comment. |
| | | |Navy | |
| | | | |Has no comment. |
| | | | | |
| | | | |Concurs as written and submits no |
| | | | |additional changes or amendments. |
| | | | | |
| | | | |Published as ADC 424 on 05/09/11. |
|PDC 444, |To establish procedures for the originating |1/10/11 |DSCA |Concur with comment. "Army FMS wants |
|Update Functionality for DS 856S Shipment Status |activity (RIC-From) to generate an update to the | | |DAASC to provide them with the revised |
|and DS 945A Material Release Advice |DS 856S, Shipment Status, and the DS 945A, | | |shipment status. They want the revised|
|(Supply/AIT) |Material Release Advice (Material Release | | |status to overlay the original status |
|11/24/10 |Confirmation) in the event the outbound shipment | | |in their legacy system (CISIL)" |
|Daverede |details change from what was originally | | | |
|HQ DLA Distribution J4 |transmitted to DLA Transaction Services (formerly | | |Concur w/comment. IGC requested a |
| |known as DAASC) for routing to designated status | | |90-day delay in |
| |recipients. | |USTRANSCOM |implementation from the date the ADC is|
| | | | |published. |
| | | | | |
| | | | |It is Navy's preference to have the |
| | | |Navy FMS |updated/replacement AS_ transaction |
| | | | |suppressed from being sent to MISIL. |
| | | | | |
| | | | |No comment |
| | | |DFAS | |
| | | | |Concurs |
| | | |DMLSS Program, | |
| | | |JMFLDC | |
| | | | | |
| | | |Air Force |Concurs with PDC 444 w/o comments. |
| | | | | |
| | | | |Concurs |
| | | |DLA | |
| | | | |Concurs with PDC 444 with comments. |
| | | |USMC | |
| | | | |Concurs without comment. |
| | | | | |
| | | |HQDA DCS | |
| | | |G-44(S) | |
| | | | |Published as ADC 411 on 04/12/11 |
|PDC 445, |The intent of the transaction routing change is to|1/06/11 |DMLSS Program |Concurs |
|DoD WebSDR Transmission of “Historical” Navy |enable the DoD WebSDR to forward historical | |JMFLDC | |
|Supply Discrepancy Reporting System (NSDRS) SDRs |customer SDRs (identified as SDR Document Type 6 | | | |
|as Information Copies to Product Data Reporting |and type 7) from one Navy-sponsored system to | |NAVSUP | |
|and Evaluation Program (PDREP) (Supply |another. | | |Non-concurs |
|SDR/Quality Assurance) | | |Army FMS | |
|11/22/10 | | | |No impact on US Army FMS. We do believe|
|Hilert | | | |however, that Army SDRs induction into |
|NAVSEA | | | |the PDREP would be a good thing. It |
| | | | |would capture the quality deficient |
| | | | |SDRs and perform trend analysis. |
| | | | | |
| | | |USMC |Deferred until Navy position is |
| | | | |clarified. |
| | | | | |
| | | |Army |Concurs |
| | | | | |
| | | |Air Force |Concurs w/o comment |
| | | | | |
| | | | |"ON HOLD (pending internal Navy |
| | | | |decision)" |
|PDC 446, Support to Missile Defense Agency (MDA) |The MDA is soon to be established as an IA for |4/14/11 |USTRANSCOM |Abstains |
|as a Foreign Military Sales (FMS) Implementing |Foreign Military Sales related to a new weapon | | | |
|Agency (IA) and Assignment of New Service and |system and support parts. In order for standard | |Army | |
|Agency (S/A) Code “I” |logistics systems to recognize transactions | | |Concurs with comment |
|Supply/MAPAD/SDR |associated with MDA FMS, a new S/A Code to | |DSCA DPAP | |
|2/28/11 |identify “MDA - Security Assistance Only” will be | |IUID/WAWF |Comments received |
|Hilert |established under this change proposal. The new | | |Has no comment. |
|MDA |S/A Code will allow tracking and independent | |USMC | |
| |processing for MDA which is currently using Army | | | |
| |systems for support. | | | |
| | | |Air Force |Has reviewed subject PDC and concurs as|
| | | | |written. |
| | | |Navy | |
| | | | |Concurs. |
| | | | | |
| | | | |Concurs with PDC446 as written and |
| | | | |submits no additional changes or |
| | | |DLA |amendments. |
| | | | | |
| | | | |Concurs, with one minor comment. |
| | | | | |
| | | | |Published as ADC 428 on 5/23/11 |
|PDC 448, |This change modifies the DLMS to require contract |07/13/11 | | |
|Additional Contract-Related Data for 870S with BV|related data be included in the DLMS 870S (DI Code| | | |
|Status (Supply/MILSTRIP) |AE_) Supply Status transaction when BV Status is | | | |
|06/13/11 |provided (Item Procured and on contract for direct| | | |
|Hilert |shipment to the consignee). This will enable the | | | |
|PRC Chair |recipients to integrate destination acceptance | | | |
| |contract data within logistics systems used during| | | |
| |receipt processing because the relevant contract | | | |
| |data will have been received electronically from | | | |
| |the prior supply status transaction. This also | | | |
| |eliminates the need for manual research | | | |
| |destination acceptance contract data within | | | |
| |Electronic Document Access (EDA). | | | |
|PDC 450, |To modify the DS 856S, Shipment Status (AS3/AS8) |02/14/11 |USTRANSCOM |Abstaining. IGC will need to be |
|Revises DLMS Supplement 856S, Shipment Status, in|transaction to add the DTID Number and the | | |modified, but can accommodate quickly |
|Support of Reutilization Business Integration |Hazardous Waste Profile Sheet (HWPS) Number | | |after ADC. |
|(RBI) (Supply/Disposition Services) |supporting the turn-in of Hazardous | | | |
|01/13/11 |Material/Hazardous Waste (HM/HW) and to add the | |Navy |Concurs with PDC 450 as written and |
|Daverede |Container ID Number in support of the Disposition| | |submits no additional changes or |
|DLA |Containerization business process. | | |amendments. |
| | | | | |
| | | | |Concurs with PDC 450 without comments. |
| | | |Air Force | |
| | | | |No comment. |
| | | | | |
| | | |DFAS |Concurs with comment. |
| | | | | |
| | | |HQDA DCS | |
| | | |G-44(S) | |
|PDC 450A, |To modify the DS 856S, Shipment Status (AS3/AS8) |03/14/11 |USTRANSCOM |Approves PDC 450A |
|Revises DLMS Supplement 856S, Shipment Status, in|transaction to add the DTID Number, the HWPS | | | |
|Support of RBI (Supply/Disposition Services) |Number, Disposal Authority Code, Disposition | |DLA | |
|02/11/11 |Services Indicator Code, Item Nomenclature, Supply| | |Concurs without comment. Any system |
|Daverede |Condition Code, Special Material Identification | | |changes required will be part of the |
|DLA |Code, Material Management Aggregation Code, and | | |RBI Build effort. |
| |Demilitarization Code supporting the turn-in of | | | |
| |HM/HW and to add the Container Identification | |Air Force |Concurs with PDC 450A without comments |
| |Number in support of the Disposition | | | |
| |Containerization business process. | | |Concurs as written. |
| | | |USMC | |
| | | | |Concurs with PDC450A as written and |
| | | |Navy |submits no additional changes or |
| | | | |amendments. |
| | | | | |
| | | | |Concurs with comment. |
| | | | | |
| | | |HQDA DCS | |
| | | |G-44(S) | |
|PDC 452, Intra-DLA Revisions to Procedures and |This change proposes the addition of the |03/07/11 |DFAS |No comment |
|DLMS |‘Container ID Change’ functionality to DLMS 846A | | | |
|846A Asset Reclassification Transaction to Add |Asset Reclassification transaction. In order to | |Air Force |Concurs with PDC 452 w/o comments. |
|Container ID Number Change |maintain container synchronization between EBS and| | | |
|Functionality for use by DLA Disposition Services|DSS, this proposed change will account for the | | |Concurs without comment. ADC will be |
|Under RBI (Supply) |removal or switching of an item from one container| |DLA |implemented as part of RBI build |
|02/03/11 |to another container. | | |effort. |
|Johnson | | | | |
|DLA Disposition Services | | | |Concurs |
| | | |Army | |
| | | | |Concurs with PDC 452 as written and |
| | | | |submits no additional changes or |
| | | |Navy |amendments. |
| | | | | |
| | | | |Concurs without comment. |
| | | | | |
| | | |Army |Concurs as written. |
| | | | | |
| | | |USMC | |
|PDC 455, |This PDC addresses additional data and label |06/06/11 |USTRANSCOM |Abstains due to no known impact. |
|Additional Data Element Requirements for the |requirements for the DD Form 1348-1A or DD Form | | | |
|Issue |1348-2 that will provide DLA Disposition Services | |DSCA |Concurs w/ comment. |
|Release/Receipt Document (IRRD) (DD Form 1348-1A |with printed data in Block 27 to support the | | | |
|or DD Form 1348-2) Continuation Page Supporting |current Disposition Services supply processes. | |DLA |Concurs without comment. Any system |
|Reutilization Business Integration | | | |changes will be handled by the RBI |
|(Supply/Disposition Services) | | | |build effort. |
|05/06/11 | | | | |
|Daverede | | | |Has reviewed subject PDC and concurs |
|DLA Disposition Services | | |USMC |with comments. |
| | | | | |
| | | | |Concurs w/o comment. |
| | | |DFAS | |
| | | | |Concurs with PDC455 as written and |
| | | |Navy |submits no additional changes or |
| | | | |amendments. |
| | | | | |
| | | | |Concurs with PDC 455 without comment. |
| | | | | |
| | | |HQDA DCS | |
| | | |G-44(S) |Concurs without comments. |
| | | | | |
| | | |Air Force | |
|Proposed Addendum 456 to ADC 384, Special |This amends ADC 384 to establish DLMS procedures |04/04/11 |USTRANSCOM |Abstains |
|Programs for Non-DoD/Non-Federal Agency |for additional Special Programs in support of DLA | | | |
|Requisitioners; Additions in Support of DLA |Reutilization Business Integration, where the | |OIG DoD | |
|Disposition Services Under RBI (DoDAAD and |requisitioner is neither a Federal Agency nor a | | |Concurs |
|Supply) |DoD entity. This change establishes DoDAAC series | |DLA | |
|03/03/11 |to clearly identify such programs. | | |Concurs without comment. |
|Hammond | | |DPAP IUID/WAWF | |
|DLA | | | |Has no comment. |
| | | |DLA Transaction| |
| | | |Services | |
| | | | | |
| | | | |Concurs |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | |Published as ADC 384A on 04/07/11 |
|PDC 457, |The purpose of this requested action is to provide|5/26/11 |Navy |Concurs with PDC457 as written and |
|Requirements for Estimated Shipment Date in the |DLA Disposition Services an estimated shipment | | |submits no additional changes or |
|DLMS Shipment Status (856S) Supporting the |date for items that are transferred to DLA | | |amendments. |
|Estimated Shipment Date (Supply) |Disposition Service Field Offices when the retail | | | |
|04/26/11 |supply system does not automatically send the | | |Concurs without comment. |
|Daverede |shipment status. | |DLA | |
|Air Force |DLA Disposition Services requires the shipment | | |Has reviewed subject PDC and concurs as|
| |status transaction to create a due-in record | |USMC |written. |
| |within DAISY in order to process the receipt of | | | |
| |the shipment. | | |Concurs |
| | | |USAF | |
| | | | |No comment on this. DFAS does not |
| | | |DFAS |expect to use the 856S. |
| | | | | |
| | | | |Concurs with PDC 457 as written. |
| | | | | |
| | | |HQDA DCS | |
| | | |G-44(S) |Approves PDC 457 with the following |
| | | | |comments. |
| | | |USTRANSCOM | |
| | | | |Published as ADC 433 on 06/24/11 |
|PDC 458, |To allow the FMS customer sufficient time to |03/28/11 |USTRANSCOM |Abstains |
|Timeframe Change for Security Assistance (SA) SDR|submit an SDR for reconsideration after in-country| | | |
|Requests for Reconsideration. |receipt of returned SDR exhibit item. | |USMC | |
|02/10/11 | | | |Concurs |
|Hilert | | |HQDA DCS | |
|AFSAC/IARGB | | |G-44(S) |Concurs without comment. |
| | | | | |
| | | |Air Force | |
| | | | | |
| | | | |Concurs with PDC 458 without comments. |
| | | |DLA | |
| | | | |Concurs (w/updated version) |
| | | | | |
| | | | |Published as ADC 430 on 06/13/11 |
|PDC 459, |To establish a MILSTRIP-authorized value for the |4/14/11 |USTRANSCOM |Abstains |
|Establish New MILSTRIP-Authorized Value for First|first position of requisition document number | | | |
|Position of Requisition Document Number Serial |serial number, also referred to as the DLMS | |HQDA DCS | |
|Number and DLMS Utilization Code H for Military |Utilization Code, to be used within the Navy | |G-44(S) |Concurs with PDC 459 without comment. |
|Sealift Command (MSC) (Supply/MILSTRIP) |solely by the MSC. | | | |
|2/28/11 | | |USMC | |
|Hilert | | | |Concurs as written. |
|MSC | | |USAF | |
| | | | |Concurs |
| | | |Navy | |
| | | | |Response date extended to June 06, |
| | | | |2011. |
| PDC 461, |Revise the DLMS to allow for the identification of|04/25/11 |HQDA DCS |Concurs with PDC 461 without comment. |
|Intra-Navy DLMS 511R, Requisition, Inclusion of |the desired storage activity from which the | |G-44(S) | |
|Requested Storage Activity (Supply/MILSTRIP) |requisitioned item is to be supplied. This change| | | |
|03/24/11 |will be adopted as an intra-Navy DLMS enhancement | |USTRANSCOM |Abstains |
|Hilert |in support of organic maintenance requisitioning | | | |
|NAVSUP E3 |procedures associated with Project Code Z5X. | |DLA | |
| | | | |Concurs without comment, no system |
| | | |Navy |impacts. |
| | | | |Concurs with PDC 461 as written and |
| | | | |submits no additional changes or |
| | | | |amendments. |
| | | | | |
| | | |Air Force |Concurs |
| | | | | |
| | | |IUID and WAWF |No comment. |
| | | |Contract | |
| | | |Support | |
| | | | | |
| | | | | |
| | | | |Published as ADC 426 on 05/10/11 |
|PDC 463, |The DLMS 940R Material Release Order (MRO) will |6/10/11 |USTRANSCOM |Abstains |
|Intra-DLA change to Revise DLMS 940R, Release |facilitate the communication between DLA | | | |
|Order, to Support Directed Release of Material in|Disposition Services SCOs responsible for awarding| |USMC | |
|Support of Reutilization Business Integration |property to public customers and field activity | | |Response date extended to 06/22/11. |
|(RBI) Public Sales Process |personnel responsible for supervising the physical| | | |
|(Order Fulfillment) |removal of property from Disposition Services | |Air Force |Concurs. |
|05/26/11 |Field Offices. | | | |
|Hilert | | |DLA |Concurs without comment. |
|DLA Disposition Services | | | | |
| | | |Navy |Concurs with PDC463 as written and |
| | | | |submits no additional changes or |
| | | | |amendments. |
|PDC 467, |This change proposes that DLA Transaction Services|06/15/11 |USMC |Response date extended to 06/22/11. |
|Exception Rules to Accommodate Communication of |split large quantities for ammunition communicated| | | |
|Ammunition Quantities in Excess of Five Digits |via DLMS Transaction into two legacy 80-record | | |Approves with comments. |
|(Supply/MILSTRIP/MILSTRAP) |position transactions without creating or changing| |USTRANSCOM | |
|05/31/11 |the suffix code. | | | |
|Hilert | | |Army |Response date extended to June 30, |
| | | | |2011. |
| | | | | |
| | | |Air Force |Concurs |
|PDC 469, |Changes to WAWF will allow for the prepopulation |06/22/11 |DSCA |No impact. |
|Revise Advance Shipment Notice (ASN) (DLMS |of all data that is present in EDA and WAWF to be | | | |
|Supplement (DS) 856) to add the Purchase Request |pre-populated from EDA into WAWF. EDA currently | |USTRANSCOM |Concur with comment. |
|(PR) Number supporting the Electronic Document |contains data that could be pre-populated that is | | | |
|Access (EDA)/Wide Area Workflow (WAWF) Interface |not. With the addition of the PDS, all | |Air Force | |
|(Supply/Contract Administration/Finance) |contracts should be in the form of data and thus | | |Concurs without comments. |
|06/07/11 |allow for further pre-population. EDA has some | |DPAP | |
|Hilert |data | | |Concurs. |
| |elements that are not currently on WAWF documents,| |DLA | |
| |one of which is the PR Number. Program changes to | | |Concurs without comment. |
| |WAWF will add these elements to the WAWF | | | |
| |documents. A business process review indicates the| | | |
| |EDI 4010 856, ASN, requires additional data | | | |
| |elements to support the addition of the PR Number | | | |
| |to WAWF. | | | |
|PDC 470, |This change is to require the user to make a |07/09/11 |DLA Transaction|Concurs |
|Change to DoDAAC Authority Code Assignment |decision about which Authority Code to assign when| |Services | |
|Process |creating a new DoDAAC vice defaulting to Authority| | | |
|06/09/11 |Code “00”. | |USMC | |
|Hammond | | | | |
|PRC Chair | | | |Fully concurs. We are full speed ahead |
| | | | |with implementation. |
| | | |DoDEA | |
| | | | |Concurs |
| | | |NGA | |
| | | | |Concurs |
| | | |NSA | |
| | | | |Concurs |
| | | |Navy | |
| | | | |Concurs |
| | | |GSA | |
| | | | |Concurs |
| | | |DCAA | |
| | | | |Concurs |
| | | |DSS | |
| | | | |Concurs with the proposal as written. |
| | | | | |
| | | |DeCA |Concurs. |
| | | | | |
| | | |USCG |Concurs. |
| | | | | |
| | | |WHS |Concurs/no comments. |
| | | | | |
| | | |DCMA |Concurs |
| | | | | |
| | | |DISA |Concurs |
| | | | | |
| | | |HQUSSOCOM |Concurs with no comment. |
| | | | | |
| | | |USMC Systems | |
| | | |Command |Concurs as written. |
| | | |USTRANSCOM | |
| | | | | |
| | | |DODIG |Abstains |
| | | | | |
| | | |DLA | |
| | | | |Concur with changes. |
| | | | | |
| | | | |Concurs |
PART II -- REQUESTS FOR IMPLEMENTATION DATES
|CHANGE NUMBER | | |
|TITLE |BRIEF DESCRIPTION |STATUS |
|DATE ISSUED |OF CHANGE | |
|ACTION OFFICER | | |
| | |DATE DUE |REC’D FROM |STATUS/COMMENTS/ |
| | | | |RECOMMENDED IMPL DT |
|Revised Request for Implementation Date for Approved |Provides a means of identifying, |4/30/98 | |Components to validate continued |
|MILSTRAP Change Letter (AMCL) 3 |segregating, and controlling |RFID | |requirement per SPRC 99-4. |
|Supply Condition Code (SCC) W for Unserviceable |unserviceable warranted assets. |extension | |Awaiting Component response. |
|Warranted Assets | |10/1/99 | |Joint implementation with DLA recommended.|
|11/28/97 | | | |12/04 |
|Johnson | | | |Navy reassessing and withdraws 7/99 date. |
| | | |USA | |
| | | |USN |Ready to implement. |
| | | | |No comment. |
| | | |USAF |Any date acceptable. |
| | | |DSCA |Ready to implement. |
| | | |GSA | |
| | | |USCG | |
|Revised Request for Implementation Date for Joint |Revises formats to incorporate the | | |Revised request for implementation date |
|Approved MILSTRAP 5 & MILSTRIP Change 13 |date packed/expiration date field for | | |tabled pending DLA validation of |
|Date Packed/Expiration Date for Subsistence Items |subsistence items in applicable | | |requirement. |
|Revised RFID on hold. |transactions. Permits Inventory | | | |
|Johnson/Hilert |Control Points’ direction of issues by| | |SPRC mtg 08-1 and 09-1: Followed up to DLA|
| |date packed/expiration date within | | |for validation of requirement. |
| |supply condition code. | | |Nov 09, DLA advised requirement is |
| | | | |obsolete – AMCLs to be withdrawn. |
|Request for Implementation Date ADC 12 Revised |Revises LR procedures to ensure |8/3/98 | |Joint implementation required |
|Procedures for Logistics Reassignment (LR) |accountability and control of assets | | |SPRC 02-1: To be addressed under for |
|(Supply/Joint MILSTRIP/ MILSTRAP) |being logistically reassigned. | | |modernization/ERP |
|6/3/98 | | | |SPRC 02-3 Conclusion: Components unable |
|Hilert/Johnson | | | |to establish date in modernized systems. |
| | | | |Request premature. Components should |
| | | | |assure modernized systems are aware of |
| | | | |requirements, and need for joint |
| | | | |implementation when applicable. |
| | | | | |
| | | | |2/01 -No date available due to legacy |
| | | | |system freeze |
| | | |USN |2002 |
| | | | |Will coincide with USAF. |
| | | |USAF |No impact. |
| | | |USMC |No impact. |
| | | |DTRA | |
| | | |NSA | |
|Request for Implementation Date for Approved |Allows for partial reversal, i.e., |3/14/08 | |This replaces the Request for |
|MILSTRAP Change Letter (AMCL) 13, Partial Reversal of|reversal of less than the original | | |Implementation Date released 5/5/1998. |
|Select MILSTRAP Transactions |transaction quantity of selected | | | |
|2/14/08 |transactions. | | |The Navy Management Information System for |
|Johnson | | |DSCA |International Logistics (MISIL) does not |
| | | | |generate or receive the AMCL 13 |
| | | | |transactions. |
| | | | | |
| | | | |AMCL 13 functionality will be covered by |
| | | |Navy |Navy ERP, when it is released. Not |
| | | | |implemented in Navy legacy systems. |
| | | | | |
| | | | |Response date extended to 4/10/08 |
| | | | | |
| | | |Army | |
| | | | |Comments provided to include: Since GCSS-MC|
| | | | |is COTs, we are relying on the core, basic,|
| | | |USMC |out-of-the-box functionality; we are not |
| | | | |creating actual transactions like D9_s for |
| | | | |internal activities. The way Oracle will |
| | | | |work this is; If instead of doing an |
| | | | |inventory gain of 100, I do one for 1000, |
| | | | |then I'll have to do a loss for 900. |
| | | | |Transactions will be linked with references|
| | | | |and they will of course be captured. |
| | | | |GCSS-MC will not have the capability to |
| | | | |accept reversals, full or partial. |
| | | | |Legacy systems will not be modified due to |
| | | | |the implementation of GCSS-MC. |
| | | | | |
| | | | |Has implemented CSRDs in our D035 wholesale|
| | | | |(A) and retail (K) systems to allow us to |
| | | | |process partial reversals for D4, D6, D8, |
| | | |USAF |and D9 transactions sent by DSS. No |
| | | | |changes were made to the legacy systems |
| | | | |(D035A/K) for any other MILSTRAP |
| | | | |transaction DOC-IDs for partial |
| | | | |reversals--they will have to wait for our |
| | | | |future ECSS system (2012). |
| | | | | |
| | | | |Not yet implemented. Concur with the |
| | | | |concept. Implementation estimated sometime |
| | | | |in FY10 |
| | | | | |
| | | |GSA |Discussed at SPRC 09-1. Action: Each |
| | | | |Component provide implementation date |
| | | | |12/1/09 so a coordinated joint |
| | | | |implementation date can be established. |
| | | | |DLMSO will publish in manuals with footnote|
| | | | |citing Implementation date once |
| | | | |established. |
| | | | |Implementation date: Mar 2015. |
| | | | |Implementation corresponds to the planned |
| | | | |date for ECSS to subsume SCS and CAV-AF |
| | | | |functionality. |
|Request for Implementation Date ADC 18 Pseudo Closure|Modifies MRA procedures to expand use | | |Approved change to reflect expanded use by|
|Procedures (Supply/MILSTRIP) |of DI Code ARH to provide notice to | | |SA per SPRC 99-3 and DSCA. |
|8/24/99 |storage activity to close open MRO | | |Joint implementation with DLA |
|Hilert |records. | | |SPRC 02-1: Army to revalidate |
| | | | |requirement. |
|Request for Implementation Date ADC 21Storage |Data Sharing. Defines |8/28/00 |DTRA |No impact. Any date. |
|Activity On-hand Asset Balance Data Sharing |on-hand asset balance at storage | |USCG |No impact. |
|6/27/00 |activities that is to be shared by | |GSA |No impact. Any date. |
|Johnson |multiple organizations. | | | |
|Revised Request for Implementation Date Approved |Requires the ICP to reject Material | | |Joint implementation recommended. |
|MILSTRIP Change 35 Inventory Control Point (ICP) |Returns Shipment Status transactions | | | |
|Generation of FTR Transactions |that contain NSNs that cannot be | | |Implementation date not available pending |
|7/23/98 |identified or do not match a | | |modernization. |
| |previously submitted offer/automatic | | | |
| |return. This corrects automatic | | | |
| |rerouting of the offer by DAASC to | | | |
| |another ICP. | | | |
|Request for Implementation Date for Special Program |This change establishes a minimum |3/14/08 | |This replaces the Request for |
|Requirements (SPR) Process Minimum and Maximum |quantity check option and modify | | |Implementation date released 5/25/2006. |
|Quantity Checks, and New SPR Status Codes |existing SPR status are currently not | | | |
|(Supply/MILSTRAP) |specific enough to ensure transactions| | |Implemented. |
|2/13/08 |process through appropriate logic; | |DLA |Implemented Dec 2002. |
|Johnson |therefore, DLA recommends an existing | |Navy |Concur with proposed changes and request |
| |status code be redefined to fit only a| |USAMMA |earliest implementation date. |
| |single purpose and 2 new codes be | | | |
| |established. | | |DLMSO followed up for USA and USAF |
| | | | |response 6-18-09. Response due 6-30. |
| | | | |USAF ECSS target implementation date is |
| | | | |March 2015 |
| | | | | |
| | | | |Discussed at SPRC Mtg 09-1. |
| | | | |DLMSO requested interim solution for |
| | | | |staggered Service implementation from DLA.|
|Request for Implementation Date ADC 39 Special |Proposes using SPR status transaction |6/26/06 | |SPRC mtg 02-1: Followed up for responses.|
|Program Requirements (SPR) Process Use of Reject |to provide MILSTRAP DI Code DZG reject| | |New RFID and Request for Review of |
|Status Codes and Review of Alternative if Not Being |advice codes. | | |Alternative released May 2006. |
|Implemented in Legacy Systems | | | |SPRC mtg 07-2: ADC to be withdrawn |
|(Supply) |ADC was not being implemented in | | | |
|5/25/06 |Service legacy systems. Modernized | | |Withdrawn on 2/13/08 – see Part IV section|
|Johnson |systems should program for DLMS 824R | | |-- inactive hold/withdrawn changes |
| |reject transactions. | | | |
|Revised Request for Implementation Date Approved |Provides automated transactions to | | |DLSS implementation for Components to be |
|MILSTRIP Change 39 |replace the manual messages used to | | |withdrawn. SPRC 00-1 approved for DLMS |
|Verification of Excessive Quantity Requisitions |verify what appear to be excessive | | |implementation only. SA implementation |
|7/23/98 |requisition quantities. | | |under DSAMS being considered. |
|Hilert | | | |Concurrent implementation recommended. |
| | | | |ADC to be released. |
|Request for Implementation Date Approved MILSTRAP |Provides for automated followup and |11/9/98 | |Staggered implementation recommended. |
|Change 49A |reconciliation of due-in between the | | |SPRC 02-3: Army, DLA, Navy asked to |
|Reconciliation and Followup Procedures for Dues-in |losing and gaining inventory managers | | |ascertain if implemented and in use. |
|After Logistics Reassignment (LR) |during LR. | | |USAF response required. |
|9/10/98 | | | | |
|Johnson | | | |Status Provided in 2002 |
| | | | | |
| | | | |Implemented 1/99. Problems encountered |
| | | | |when tested with DLA required program |
| | | |USA |corrections. |
| | | | |Implemented. This process is activated |
| | | | |for intra-DLA transfers. To activate the |
| | | | |process with the Service(s) would require |
| | | |DLA |a small systems change for SAMMS. |
| | | | |Programmed - but corrections are required |
| | | | |to match DLA. |
| | | | |Will coincide with USAF. |
| | | | |Implemented. |
| | | | | |
| | | |USN |SPRC mtg 08-01: Requested all Components |
| | | | |provide updated implementation status. |
| | | |USMC | |
| | | |GSA |Status Provided in 2008: |
| | | | | |
| | | | |Legacy will not now be modified to fully |
| | | | |comply. |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | |USN | |
|Request for Implementation Date for Approved Defense |Qualifier ‘ZZ’ is used in DLMS |9/20/08 |Navy |Navy ERP is planning to code for the use |
|Logistics Management System (DLMS) Change (ADC) 295, |transactions for materiel | | |of "ZZ" in their DLMS mappings for release|
|Use of DLMS Qualifier for Local Stock |identification “to identify | | |1.1. And since FEB 2010 is when they are|
|Number/Management Control Numbers (Supply) (Staffed |nonstandard materiel when all other | | |scheduled to "go live" then Navy will have|
|as PDC 319) |authorized qualifiers do not apply or | | |implemented ADC 295 after 2010 in their |
|8/06/08 |cannot be determined (includes MCNs | | |ERP solution |
|Johnson |and locally assigned stock numbers). | | | |
| |Qualifier ‘ZZ’ may also be used for | | |GSA will comply once GSA has converted to |
| |DLSS-to-DLMS conversion when the | | |DLMS EDI. |
| |translator cannot determine a more | |GSA | |
| |appropriate code.” Qualifier ‘ZZ’ | | | |
| |supports existing MILSTRIP appendix | | | |
| |AP2.5 which identifies what data that | | | |
| |can be entered in the generic DLSS | | | |
| |(e.g., MILSTRIP, MILSTRAP, etc) ‘stock| | | |
| |or part number’ field. | | | |
|Request for Implementation Date for ADC 313, |a. Provides a new DS 527R beginning |2/09/09 |USAF |Target implementation date is March 2015 |
|Revisions to DS 527R to Add Code for MILSTRAP DRB |segment action code to provide | | |under ECSS. |
|Functionality and to Address Enhancement for Advice |functionality of MILSTRAP (reference | | | |
|Codes Used with 527R Receipt and Response to Inquiry |3a) DI Code DRB-MRA Reply to | |USMC |Expects that ADC 313 will be fully |
|for Materiel Receipt (Supply) (Staffed as PDC 330) |Follow-up. | | |implemented no later than FY16. |
|12/24/08 |b. Highlights the procedures for a | | | |
|Johnson |1990 MODELS (now known as DLMS) | | |Projected implementation for GCSS-Army is |
| |enhancement (reference 3b) for use of | |Army Retail |3rd Qtr FY2012 (Release 1.2); SARSS legacy|
| |advice codes with DS 527R receipt | | |system will not implement. |
| |transaction and with the DS 527R | | | |
| |response to inquiry for materiel | | |Pending more information to be gathered |
| |receipt transaction. | |Army National |the middle of 2011 when HQ AMC approves |
| | | |wholesale system |LMP's new work schedule, Army's wholesale |
| | | |(LMP and SDS) : |level implementation date is 2015 |
| | | | | |
| | | | |Cannot provide an ADC 313 implementation |
| | | |Navy |date for Navy ERP at this time. |
| | | | |Implementation would be no earlier than |
| | | | |2013, but could be later. |
| | | | | |
| | | | |Implementation date: Mar 2015. |
| | | | |Implementation corresponds to the planned |
| | | | |date for ECSS to subsume SCS and CAV-AF |
| | | | |functionality. |
| | | | | |
| | | | |Followed up for Navy and DLA response |
| | | | |4/10/2011. |
|Request for Implementation Date for ADC 384, Special |This change establishes DLMS |7/26/10 |DAAS |Edits shall be implemented within 60 days |
|Programs for Non-DoD/Non-Federal Agency |procedures for Special Programs where | | |of publication of the approved change - in|
|Requisitioners and Administrative Change for |the requisitioner is neither a Federal| | |place on or before July 25, 2010. |
|Contractor DoDAACs (DODAAD/Finance/Supply) (Staffed |Agency nor a DoD entity, and | | | |
|as PDC 397) |establishes a new DoDAAC series to | | |Approved DLMS Change 384 and the |
|5/26/10 |clearly identify such programs | | |associated Request for Implementation Date|
|Hammond | | | |are deferred to allow for further |
|PRC Chair | | | |evaluation before implementation. |
|Request for Implementation Date ADC 384, Special |This change establishes Defense |02/18/11 |DSS |ADC 384 does not impact DSS and we are ok |
|Programs for Non-DoD/Non-Federal Agency |Logistics Management Standards (DLMS) | | |with whatever date is decided upon. |
|Requisitioners and Administrative Change for |procedures for Special Programs where | | | |
|Contractor DoDAACs (DODAAD/Finance/Supply) (Staffed |the requisitioner is neither a Federal| | |Has no issue with this ADC... proceed with|
|as PDC 397) |Agency nor a DoD entity, and | |SAF/FMP AFAFO |implementation as |
|01/18/11 |establishes a new DoDAAC series to | | |recommended by other stakeholders. |
|Hammond |clearly identify such programs. | | | |
|Army, DLA, GSA | | | |Earliest to implement could be end of |
| | | |DLA |FY12. |
| | | | | |
| | | | |(D035A) can accept requisitions from |
| | | |Air Force |Non-DoD/Non-Federal Agencies as long as |
| | | | |the customer orders* using a DoDAAC in |
| | | | |their Document Number. |
ADMINISTRATION OF THE DEFENSE LOGISTICS MANAGEMENT SYSTEM
DLMS STATUS REVIEW
PART III -- APPROVED CHANGES
|APPROVED CHANGE NO. | | | |
|TITLE |BRIEF DESCRIPTION |IMPLIMENTA-TION/ |IMPLEMENTATION STATUS/ |
|DATE ISSUED |OF CHANGE |EFFECTIVE |COMPONENT IMPL DATE |
|ACTION OFFICER | |DATE | |
| | | | |
|AMCL 1A (MILSTRIP) |Establishes procedures to control access to DoD|11/1/90 |Published in MILSTRIP Interim Change |
|Control of Access to DoD Materiel Inventories |material inventories by defense contractors. | |91-2 (9/27/91) |
|Required by Defense Contractors | | |Implemented by all except: |
|8/1/90 | | |USA (retail) 12/04 |
|AMCL 2 (MILSTRIP) |Provides restrictions to reduce the amount of |11/1/91 |Last reported implemented by all except: |
|Reduction in the Use of Exception Data |exception data in requisitions. | |DLA (Subsistence) |
|Requisitions | | | |
|10/4/88 | | | |
|ADC 4 |Supports DoD Care of Supplies in Storage |1/25/99 |Revised SDR instruction published. Component |
|Revised Procedures for Discrepant Packaging |(COSIS) Program within DoD Stock Readiness | |implementation ongoing. DLMSO note: Requires|
|(Supply/SDR) |Program. Changes include annotating the SDR to| |further integration for transactional |
|9/23/97 |differentiate major/secondary items; providing | |exchange. |
|Hilert |breakout of repackaging costs for labor and | | |
| |material; modifies distribution of SDRS for | | |
| |vendor shipments. | | |
|AMCL 5 (MILSTRIP) |Establishes procedures for requesting and/or |11/1/92 |Last reported implemented by all except: |
|DoDAAC of Initial Transportation Shipping |providing the DoDAAC of the initial shipping | | |
|Activity |activity | |GSA and DLA (Subsistence) |
|10/20/89 | | | |
|AMCL 6 (MILSTRIP) |Permits the timeframe for returning material to|12/31/99 |Published in MILSTRIP Formal Change 8 |
|Modify Material Returns Program Reporting |start with the receipt of the shipment status | |(5/18/95). |
|Timeframes |(FTM) from the customer thereby allowing | |Restaffed as RRFID and reported implemented by|
|(In work) |additional time so that delays intransit will | |all except: |
|Hilert |not result in denial of credit. | |USN - No date available due to legacy system |
| | | |freeze |
|AMCL 6 (MILSTRAP) |Improves inventory record accuracy between ICP |11/1/91 |Last reported implemented by all except: |
|Improved Inventory Accuracy |and storage activities by requiring storage | | |
|7/14/89 |activities to enter the date processed on | |DLA (Subsistence) |
|Johnson |inventory adjustment. | | |
|Approved DLSS/DLMS Change 6 Identification of |Adds identification of FSCAP to the Defense |Staggered beginning 4/98|Last reported as implemented by all except: |
|Flight Safety Critical Aircraft Parts (FSCAP) |Turn-In Document/DLMS transaction and the | |USN - No date available due to legacy system|
|on Shipments to Disposal (MILSTRIP/Supply) |Disposal Release Order (DRO) format. | |freeze |
|10/28/98 | | |USA - December 2004 |
| | | |Published in MILSTRIP IC 99-8 |
|AMCL 7 (MILSTRIP) |Requires the supply source to use the RDD to |11/1/90 |Last reported implemented by all except: |
|Required Delivery Date (RDD) for Subsistence |fill subsistence requisitions. | |DLA (Subsistence) |
|Requisitions | | |USN - No date available due to legacy system |
|11/21/88 | | |freeze |
|Joint Approved MILSTRAP Change 7 and MILSTRIP |Expands the Cooperative Logistics Program |12/31/03 |Approved for implementation under Defense |
|Change 22 Cooperative Logistics Supply |Support Code (CLPSC) to differentiate a FMS | |Security Assistance Management System (DSAMS).|
|Support Arrangements |Order (FMSO) I requisition from a FMSO II | | |
|11/8/99 |requisition. Also requires use of the MILSTRAP| |DLMSO requested DSCA update implementation |
|Johnson/Hilert |Demand Code P in CLSSA termination/drawdown | |status 12/20/07 |
| |requisitions related to SPRs. | |USN - No date available due to legacy system |
| | | |freeze |
|AMCL 8 (MILSTRIP) |Added bar coded FMS data to the IRRD. |11/1/91 |Last reported implemented by all except: |
|Bar Coded Foreign Military Sales (FMS) Data on| | | |
|DD Form 1348-1A, Issue Release/Receipt | | |USN & USMC |
|Document (IRRD) | | | |
|4/17/89 | | | |
|Third Addendum to AMCL 8A (MILSTRAP) |Publishes two new types of Physical Inventory/ |N/A |Component implementation ongoing. |
|Revised Procedures for Physical Inventory |Transaction History codes to accommodate | | |
|Control |Distribution Standard System warehouse control | |USA 12/04 |
|8/9/96 |system requirements and incorporates all | | |
|Johnson |previous AMCL 8A changes. | | |
|AMCL 9 (MILSTRIP) |Eliminated requirement to change priority on |11/1/91 |Last reported implemented by all except: |
|Priority Designator for JCS Project Code |CJCS project code requisitions. | | |
|3/6/89 | | |DLA (Subsistence) |
|AMCL 9A (MILSTRAP) |Supersedes AMCL 9. Prohibits reporting of |4/4/05 |Published in MILSTRAP CH 4. |
|Processing Materiel Receipts Not Due-In for |depot receipts from non-procurement sources to | | |
|GSA Managed Items |GSA unless the storage activity has PMR. | | |
|4/4/05 |Requires the Components to establish the means | | |
|Johnson |to account for and maintain owner visibility of| | |
| |such material and effect disposition, else DLA | | |
| |depot will receipt to local system for use by | | |
| |depot or disposal. | | |
|ADC 10, |Provides an automated means of identifying a |7/1/99 |Published in MILSTRAP. |
|Expanded Definition for Management Code R for |denial that occurred during the “issue from | | |
|use with Denials (MILSTRAP) |receiving process,” and necessitates the | | |
|5/29/98 |reversal of an erroneous receipt. | | |
|Johnson | | | |
|Revised Joint AMCLs 10 |Identification of product quality deficiency |Staggered implementation|AMCL 10 Published in MILSTRAP CH 4 and |
|(MILSTRAP) and 34 |related materiel. |is authorized beginning |MILSTRIP CH 1 |
|(MILSTRIP), Identification of | |July 2004. |DRMS has implemented the SCC Q, however will |
|Product Quality Deficiency | | |not implement the appropriate management codes|
|Report (PQDR) Material |Joint implementation with DLA recommended. | |until ERP modernization (date TBD). In the |
|(Supply/MILSTRIP/MILSTAP) | | |interim, all Q material sent to DRMS will be |
|1/21/04 | | |destroyed. |
|Hilert | | | |
| | | |Partial Army implementation. |
| | | |USAF Implemented 7/15/98. |
| | | |Navy awaiting ERP. |
| | | |USMC – SPRC requested implementation status |
|AMCL 11 (MILSTRIP) |Requires supply source to reject requisitions |5/1/89 |Last reported implemented by all except: |
|Source of Supply (SOS), Federal Supply |if the FSC is incompatible with the NIIN. | | |
|Classification (FSC) and National Item | | |DLA |
|Identification Number (NIIN) Edit | | | |
|4/5/89 | | | |
|Joint Approved MILSTRAP Change 11 and MILSTRIP|Establishes DoD closed-loop system to monitor |Various during 1998-1999|Published in MILSTRIP/MILSTRAP/DLMS |
|Change 15 with Addendum 1&2 |receipt of wholesale stock shipments and assure| | |
|Expanded Materiel Receipt Acknowledgment |proper accountability is maintained by the | |Component implementation issues/programming |
|Procedures |receiving activity. | |corrections ongoing. |
|9/28/90 | | |Specific programming errors identified to USMC|
|Addendum 6/11/91 (STRIP) | | |12/18/07 |
|Addendum 7/8/96 (STRAP) | | | |
|Johnson | | | |
|Third Addendum to Joint Approved MILSTRAP |Establishes management evaluation requirement |2/8/98 |Implementation/program corrections ongoing. |
|Change 11 and MILSTRIP Change 15 |under Customer Wait Time (CWT). Revised the | | |
|Expanded Materiel Receipt Acknowledgment |format and routing of the pseudo shipment | | |
|Procedures |status (DI ASH) transaction. | | |
|1/9/98 | | | |
|Johnson | | | |
|AMCL 12 (MILSTRAP) and 43 (MILSTRIP) |Provide for accurate DOD accountability and |approved for immediate |AMCL 12 (MILSTRAP) and 43 (MILSTRIP) |
|Maintaining Accountability During Maintenance |financial accounting for items scheduled for |staggered implementation|Maintaining Accountability During Maintenance |
|Actions (DLMS Supply/MILSTRIP/MILSTRAP) |maintenance by DMISAs and for items undergoing | |Actions (DLMS Supply/MILSTRIP/MILSTRAP) |
|2/2/06 |commercial and intra-Service or Agency | | |
|Johnson/Hilert |maintenance actions. Accommodate variations | |Partial implementation reported between DSS |
| |among the Service and Agency supply and | |and individual Service applications: |
| |financial internal control system. IG and GAO | |LMP implemented. |
| |Audit Reports (references 1a and 1b) and the | |USAF in process. |
| |MILSTRAP Staff Assistance Visit Report | | |
| |(reference 1c) identified weaknesses in DOD | |Relationship with WAWF property transfer |
| |accountability for items during inter-service | |functionality to be better defined/integrated.|
| |and commercial maintenance actions | |Published updates in MILSTRIP Reissue, Oct |
| | | |2007 |
|AMCL 14 |Provides wholesale activities with access to |Immediately except as |Implemented by all except USAF has not |
|Revised Asset Status Reporting and Logistics |visibility of below wholesale assets through |noted for USAF. |implemented the 2 new asset status reporting |
|Asset Support Estimate (LASE) Procedures for |asset reporting procedures. Provides below | |codes. |
|Total Asset Visibility (TAV) |wholesale activities with access to visibility | |USAF impl date: 12/03. |
|3/6/02 |of wholesale assets through LASE procedures. | | |
|Johnson | | |Published in MILSTRAP Change 1. |
|AMCL 15 (MILSTRAP) |Permits automated identification and accounting|12/1/04 |Published in MILSTRAP CH 4. |
|New Ownership Code 0 (Zero) to Identify DoD |for assets owned by SOF. | |Prior to publication in CH 4, Service SPRC |
|Special Operations Forces (SOF) Ownership | | |representatives were asked to verify that AMCL|
|8/9/00 | | |15 had been implemented. No Service SPRC |
|Johnson | | |representative indicated that AMCL 15 was not |
| | | |implemented. |
| | | | |
| | | |Discussed at SPRC mtg 07-2. Army to identify |
| | | |which Army systems have implemented AMCL 15 |
| | | |and document current procedures on how this |
| | | |type of material is stored and issued and how |
| | | |it will be handled when LMP is implemented. |
| | | |Army response due 12/06/07. |
| | | |Followup to Army on 1/25/08. |
|AMCL 16 (MILSTRIP) |Requires shipment status to DRMS on all |11/1/92 |Last reported implemented by all except: |
|Revised Dollar Threshold for Shipment Status |shipments regardless of dollar value. (AMCLs | | |
|(DI AS3) to DRMS |17 and 158B should be implemented with AMCL 16 | |USAF & USMC |
|4/17/89 |as they affect the same procedures and | | |
|Hilert |transactions.) | | |
|AMCL 17 (MILSTRIP) |Requires unit price on shipment status to DRMS.|11/1/92 |Last reported implemented by all except: |
|Unit Price on DI AS3 for Shipments to DRMOs |(AMCLs 16 and 158B should be implemented with | | |
|7/3/89 |AMCL 17 as they affect the same procedures and | |USAF & USMC |
| |transactions.) | | |
|ADC 20A |This revision removes the applicability of the |DAAS implementation date|Components may defer associated automated |
|Revision of Status Code CX; Application of |Status Code CX for the AM_, Requisition |7/15/03 |processing pending logistics systems |
|Status Code D7 for Modifier Rejects |Modifier. The generic Status Code D7 for | |modernization |
|(MILSTRIP/SUPPLY) |invalid data on the AM_ will be applied. | | |
|(Staffed as PDC 20A) | | | |
|6/07/03 | | | |
|Hilert | | | |
|ADC 22 |Updates SDR guidance to direct the action |TBD |Implementation deferred to coincide with full |
|SDR Validation in Accordance with Material |activity to consider MRA information during SDR|SA-2003 |MRA implementation (correction of known |
|Receipt Acknowledgment (MRA) Procedures |validation. | |problems) |
|(Supply/SDR) (Staffed by PDC 32) | | |SA automated implementation under DSAMS. |
|3/22/00 | | | |
|Hilert | | | |
|AMCL 22 |Expands the CLPSC to differentiate a Foreign |Approved for |No implementation date available for Navy due |
|Cooperative Logistics Supply Support |Military Sales ORDER (FMSO) I requisition from |implementation under |to legacy system freeze. |
|Arrangements (Joint with MILSTRAP AMCL 7). |a FMSO II requisition |Defense Security | |
| | |Assistance Management |Refer to AMCL 7 |
| | |System (DSAMS) December | |
| | |31, 2003. | |
|AMCL 26 (MILSTRIP) |Assigns one RI to identify the GSA activity to |11/1/93 |Published in MILSTRIP Formal Change 8 |
|Single RI on Customer Excess Reports |receive customer excess reports. | |(5/18/95) |
|Transmitted to GSA | | |Requirement to be withdrawn when GSA policy |
|12/13/89 | | |closing warehouses is implemented. |
| | | |Implemented by all except: |
| | | |USA 12/04 |
|AMCL 30 (MILSTRIP) |Includes Status Code BZ in processing sequence |11/1/92 |Last reported implemented by all except: |
|Source of Supply Processing Cancellation |of cancellation requests. | | |
|Requests for which Supply Status BZ Provided | | |DLA (Subsistence) |
|12/13/89 | | | |
|Approved MILSTRIP Change 32 |Requires mandatory entry of the controlled |2/1/01 |Staggered implementation authorized. |
|Mandatory Entry Blocks on Material Release |inventory item code (CIIC) and shelf-life code | |Revised publication in MILSTRIP Interim Change|
|Documents |on the DD 1348-1A for issues from stock. | |02-4. |
|2/1/01 | | |Last reported not implemented by: |
|Hilert | | |USN - No date available due to legacy system |
| | | |freeze |
|ADC 33 |Revises inventory prioritization procedures to |DSS: 5/31/01 |Implementation staggered with DLA DSS. Change|
|Revised Inventory Prioritization Model |place responsibility for owner’s inventory | |published in MILSTRAP. |
|12/6/00 |prioritization methodology with the owner |Services: |DLA ICP does not plan to implement. |
|Johnson |rather than the storage activity. |No scheduled | |
| | |implementation. | |
|AMCL 33 (MILSTRIP) |Clarifies MOV report to reflect only |5/1/90 |Last reported implemented by all except: |
|Clarification of Requirements for MOV Reports |cancellations actually requested by the | |USAF (Need CSRD for wholesale system. No |
|1/31/90 |requisitioner via the MOV response. | |estimated date.) |
| | | |USMC |
|ADC 34 |Transfers responsibility for the MRA Management|8/9/00 |DAASC MRA report under review. |
|MRA Management Information Report |Information Report to the Supply PRC and DAASC.| | |
|8/09/00 | | | |
|Johnson | | | |
|AMCL 36 ( MILSTRIP) |Modifies the definition for Status Code D8 to |11/1/00 |Staggered implementation approved. |
|Status Code D8 |explain the reason for rejection and the | | |
|6/1/00 |process for resubmission of FMS requisitions | |DLA No impact. |
|Hilert |for publications that are controlled/ have | |All Components report partial implementation. |
| |restricted access. | | |
|AMCL 37 |Establishes procedures for Inter-Service use of|11/1/90 |Last reported as not implemented by USAF and |
|Temporary Exemption of Selected Units from the|Distribution Code 6 | |USMC. |
|MOV Process | | | |
|AMCL 38 |Ensures that MOV requests are forwarded to the |11/1/91 |Last reported as not implemented by USAF and |
|Inter-Service Use of Distribution Code 6 |proper activity when Distribution Codes 7 and 8| |USMC. |
| |are used. | | |
| | | |Implementation date: Mar 2015. Implementation|
| | | |corresponds to the planned date for ECSS to |
| | | |subsume SCS and CAV-AF functionality. |
|AMCL 40 (MILSTRIP) |Notifies customers of nonresponse to MOV |Various |Approved for staggered implementation |
|Notification of Customer Nonresponse to |requests when backordered requisitions are in | |beginning 03/00 |
|Material Obligation Validation (MOV) Request |pre-award status. This alerts the customer | |Initial implementation intra-Navy 04/00 |
|2/14/00 |that the material will be shipped and billed | |MILSTRIP publication deferred pending |
|Hilert |unless canceled. | |inter-Component implementation |
|AMCL 41 (MILSTRIP) |Authorizes the DAASC to reject Security |Various |DAAS implementation 30 days from release. |
|DAAS Reject of Requisitions With Invalid |Assistance transactions that do not have valid | |Components may defer automated processing |
|Ship-to and Mail-to Addresses in the MAPAD |ship-to/ mail-to addresses. | |pending logistics system modernization. |
|11/13/2001 | | | |
|Hilert | | | |
|ADC 44 |This change adds a two-dimensional bar code to |Various |USN - October 2005; |
|Two-dimensional Bar Code On Issue |the IRRD that would encompass current linear | |USAF - December 2002; |
|Release/Receipt Document (DD Form 1348-1A) |bar code and allow user to scan one bar code | |USMC - in progress |
|(Supply/MILSTRIP) |versus three. PDF 417 would allow for | |DLA – May 2002. |
|8/24/01 |additional data elements. | | |
|PDC 61/61A | | |See below 44B. |
|Hilert | | | |
|ADC 44B |This approved addendum 44B updates guidance |Staggered and phased |This Addendum 44B replaces Addendum 44A in its|
|Approved Addendum Inclusion of Supplemental |applicable to addendum 44A supplemental data |implementation dates |entirety. |
|Information for UIT/SIM in the Two-Dimensional|fields to the PDF 417 2D symbol for the purpose| |Published in MILSTRIP Reissue, Oct 2007 |
|Symbol on the IRRD (DD Form 1348-1A) |of unique item tracking. The additional | | |
|(Supply/MILSTRIP) |optional data fields will allow for | | |
|6/6/06 |identification of the manufacturer; the | | |
|Hilert |(current) part number (may be included in | | |
| |addition to the NSN; specific individual item | | |
| |by serial number; and the single value of the | | |
| |UII. These elements are identified using a | | |
| |range of ANSI MH10.8.2 data identifiers (DIs). | | |
|AMCL 44 (MILSTRAP) |Assigns two new management codes for use in D4_|5/1/86 |Last reported implemented by all except: |
|3/1/85 |receipt transactions to identify contractor | |USAF & USMC |
|Johnson |misdirected shipments and overages. | |USN - No date available due to legacy system |
| | | |freeze |
|Approved MILSTRIP Change 44 |Expands the explanation of no demand code O, |Various |Staggered implementation under |
|Recurring/Nonrecurring Demand Data |requires adjustment of demand data whenever a | |modernization/DLMS authorized. |
|8/20/01 |cancellation request is processed, and revises | | |
|Hilert |the format of the Referral Order (A4_) to | | |
| |identify the demand code. | | |
|ADC 48 |This change modifies the DS 940R Material |Approved for | |
|Revisions to DSs: Material Release Order and |Release and DS 945A Material Release Advice to |implementation | |
|Material |provide administrative corrections, | | |
|Release Advice |clarifications, and additional coding to | | |
|(Supply) |support lateral redistribution | | |
|12/01/01 |orders/responses. | | |
|Hilert | | | |
|ADC 48A |This change modifies the DS 940R Material |Approved for | |
|Addendum for Revision to DS: Material Release |Release to add an additional data element to |implementation | |
|Order |support lateral redistribution orders. | | |
|(Supply) |Apparently, this data element was inadvertently| | |
|12/26/02 |dropped during development of the LRO under | | |
|Hilert |DLMS. The DLSS field legend identifies the data| | |
| |element as “Date of | | |
| |Receipt of Demand.” | | |
|ADC 48B |This change modifies the DS 940R, Material |Approved for | |
|Addendum for Revision to DS 940R, Material |Release to add an additional code required to |implementation | |
|Release Order |support DLMS/DLSS conversion. | | |
|(Supply) | | | |
|3/05/02 | | | |
|Hilert | | | |
|ADC 48C |This change modifies the DS 945A Material |Approved for | |
|Addendum for Revision to DS 945A, Material |Release Advice to add an additional code to |implementation | |
|Release Advice |support DLMS/DLSS conversion. | | |
|(Supply) | | | |
|3/14/02 | | | |
|Hilert | | | |
|ADC 48D |This change modifies the DS 945A Material |Approved for | |
|Addendum for Revision to DS 945A, Material |Release Advice to support DLMS/DLSS conversion |implementation | |
|Release Advice |and make | | |
|(Supply) |administrative corrections. The “must use” | | |
|4/01/02 |designation is removed from the date/time | | |
|Hilert |segment in the detail level and associated | | |
| |notes are adjusted. Additionally, the | | |
| |capability to pass the Special Requirements | | |
| |Code (containing coded entries from the | | |
| |Required Delivery Date field) is provided on an| | |
| |interim basis to support conversion. | | |
|ADC 48E |Adds new qualifier for identification of the |Approved for | |
|Addendum for Revision to DS 945A, Material |POE for use during conversion processing during|implementation | |
|Release Advice |DLSS/DLMS transition. Use of different | | |
|(Supply) |qualifiers | | |
|6/03/02 |for the different types of POEs under DLMS does| | |
|Hilert |not support conversion processing which cannot | | |
| |distinguish between the three-position codes | | |
| |for air and water terminal (air terminal codes | | |
| |are always 3 alpha characters, water terminals | | |
| |may be all alpha or | | |
| |alphanumeric). | | |
|ADC 49 |This change modifies the DS to open the |Approved for | |
|Revision to DS 517M, Material Obligation |2/QTY03/10 to accommodate the unit of issue |implementation | |
|Validation (MOV) |applicable to the material being validated. | | |
|(Supply) | | | |
|12/12/01 | | | |
|Hilert | | | |
|ADC 49A |ADC 49 opened the unit of issue data element |Approved for | |
|Revision to DS 517M, MOV |for DLMS use in the 517 DS. This change |implementation | |
|(Supply) |identifies correct placement of the associated | | |
|12/17/01 |note. Additionally it inserts the Document | | |
|Hilert |Identifier Code for use during DLSS/DLMS | | |
| |transition. | | |
|ADC 49B |ADC 49/49A opened the unit of issue data |Approved for | |
|Revision to DS 517M, MOV |element, provided for correct placement of the |implementation | |
|(Supply) |associated note, and opened the LQ qualifier | | |
|02/12/02 |for | | |
|Hilert |Document Identifier Code in the detail table. | | |
| |This revision opens the LM/LQ loop in the | | |
| |header table for identification of the Document| | |
| |Identifier Code during DLSS/DLMS transition. | | |
| |(Item 3 is new to ADC 49B.) | | |
|AMCL 50 (MILSTRAP) |Adds requirement to monitor Supply Condition |11/1/89 |Last reported implemented by all except: |
|Added Requirements to Monitor Supply Condition|Codes J, K, and R assets for timely | | |
|Codes J, K, and R assets |reclassification. | |DLA (Subsistence) |
|11/28/86 | | | |
|Johnson | | | |
|ADC 57 |Clarifies and revises business rules relating |Various |Deferred implementation pending modernization |
|Enhanced Edits for the Required Delivery Date |to the use of the RDD field and its | |is authorized. |
|(RDD) Data Field in Requisitions |compatibility with the priority designator | |DAAS/DLA implementation 1/7/02. |
|(Supply/MILSTRIP) (Staffed as PDC 65) and |(PD). Revises demand sequencing to eliminate | |Published in MILSTRIP Interim Change 02-04. |
|Withdrawal of Approved MILSTRIP Change (AMC) |providing precedence to requisitions with an | | |
|40, Processing Cooperative Logistics Supply |RDD/RAD earlier than the computed SDD or | | |
|Support Arrangement Requisitions (CLSSA) |containing an expedited transportation signal. | | |
|5/23/02 | | | |
|Hilert | | | |
|ADC 69A |This change accommodates the BSM SAP |Immediately |Implemented by DLA |
|DLMS Mapping for Requisition Exception Data |requirement for receiving requisition exception| | |
|Transaction, DI Code |data. ADC 69 modified the IC/DS 511R, | | |
|YRZ |Requisition, to transmit the data content of | | |
|(Supply) |the DLA DI Code YRZ. This change extends that | | |
|12/21/05 |capability to the IC/DS for the 511M and the | | |
|Hilert |869F. This approved change includes additional| | |
| |clarification developed subsequent to staffing | | |
| |of the proposed change 69A | | |
|ADC 71B |This is an admin change to adjust the mapping |Immediately | |
|Admin Correction for DLMS Mapping for MRO |of clear text addressing in the DS 940R, MRO. | | |
|Exception Data Transaction (Supply) |This change corrects the placement of address | | |
|4/28/05 |lines 3 and 4 when DAAC conversion is required | | |
| |from Component unique DI Code CGU/ZGU. | | |
|ADC 73 |This change revises DS 527R to provide the |Published 1/15/02 and |DLA reports that as of 1/31/08 EBS has not yet|
|Revision to DS 527R MRA to Provide for Current|capability to submit a MRA transaction without |approved for immediate |implemented ADC 73. Interim workaround |
|Functionality of MILSTRAP Materiel Receipt |a stock or part number in support of MRA |implementation |pending EBS implementation of ADC 73 is being |
|Acknowledgement |requirements. This change | |addressed by DLMSO, DLA and DAASC so that |
|(MRA) Process. |will also allow for MILSTRAP MRA transactions | |affected MRA transactions are not rejected. |
|1/15/02 |(Document Identifier (DI) Code DRA/DRB), which | | |
|Johnson |are submitted with a blank stock/part number | |DLA: DLA has done SCR BOF-08-010. |
| |field, to process in DLMS during a mixed | |Implementation date unknown at this time and |
| |DLSS/DLMS environment. | |will be provided when determined – 2/07/08 |
| | | | |
| | | |On 6/02/09 DLA reports ADC 73 has been |
| | | |implemented in EBS. |
|ADC 75 |This change accommodates the BSM SAP |DAAS & DLA has advanced |Requisition implemented; Modification and |
|DLA Unique Identification of Internal Delivery|requirement for a delivery date on |authorization to employ |Cancellation pending DLA BSM acceptance |
|Date in Requisitions (Staffed by PDC 78) |requisition/order transactions. The new date |procedures under EBS | |
|(Supply) |will be calculated by DAASC translator and |testing-allowing | |
|8/26/02 |inserted in the requisition series |sequential | |
|Hilert |transactions. |implementation in order | |
| | |to prevent rejection | |
|ADC 76 |This USAF data element will be used within our |Published 8/26/02 – |Pending DLA BSM acceptance or full version |
|USAF Unique Management Coding for NMCS/MICAP |supply system to provide justification related |approved for |control |
|(Staffed as PDC 76) (Supply) |to a NMCS/MICAP that is currently identified in|implementation | |
|8/26/02 |the Required Delivery Date field (rp 62-64). | | |
|Hilert | | | |
|ADC 77 |The unique code MMAC is used in conjunction | |Pending DLA BSM acceptance or full version |
|USAF Unique Management Coding for MMAC |with/at the end of the NSN (rp 21-22 of DLSS | |control |
|(Supply) |transactions), to identify NSNs to be managed | | |
|(Staffed as PDC 75) |by a specific manager. |DLA |Implementation deferred |
|8/26/02 | |DAAS |Work-around in place |
|Hilert | | | |
|ADC 81 |Proposes establishment of 2 new DSs and Fed |Published 10/22/02 and |Authorized in 2002 for interim use by DLA |
|New DS and Federal IC for Transaction Set |ICs: 140B, and 888B, UIT under DLMS is to be |authorized for immediate|Phase 1 UIT until such time as DLA implemented|
|140B, UIT Reporting, and 888B, UIT Data Change|accomplished with standard logistics |use for DLA UIT Phase 1 |527R Receipt, after which time 527R would be |
|(Supply) |transactions, however certain functionality |interface. |used to convey serial number information for |
|10/22/02 |does not exist in current transactions, such as| |receipt transactions. |
|Johnson |submission of a request to sight verify UIT | |During Phase 1 UIT, DLA DSS processed MILS |
| |assets, as well as UIT data correction | |receipt transactions (DI Code D4_/D6_) and the|
| |requirements. DS 140B and DS 888B will fill | |serial number information was conveyed by DS |
| |the void for functions not addressed by | |140B. Use of 140B would not be required for |
| |standard logistics transactions. | |receipt transactions when DSS implemented the |
| | | |DLMS 527R Receipt. |
| | | | |
| | | |No additional requirement for 140B has been |
| | | |identified. |
| | | | |
| | | |No requirement for DLMS 888B has been |
| | | |identified. |
|ADC 86 |This change incorporates data elements for the |DAAS & DLA has advanced |To be implemented during modernization |
|Revision to DS 511R to Transmit Requisition |requisition image in DLA unique transactions DI|authorization to employ | |
|Image Transactions (Supply) |Code CH1, Memorandum Requisition Data to |procedures under EBS | |
|(Staffed as PDC 89) |DAAS-OCONUS, and DI Code CHA, Memorandum |testing-allowing | |
|17 December 02 |Requisition Data to DAAS-CONUS. |sequential | |
|Hilert | |implementation in order | |
| | |to prevent rejection | |
|ADC 88 |This change incorporates the functionality of |01/16/03 | |
|DLMS Mapping for MILSTRIP DI Code AFT, Request|the MILSTRIP DI Code AFT in the DLMS. All data | | |
|for Shipment Tracing on Registered Insured, |contents and associated procedures are the same| | |
|and Certified |as described in MILSTRIP. Refer to MILSTRIP | | |
|Parcel Post (Supply) (Staffed as PDC 94) |paragraph C3.42, Shipment Tracing, and appendix| | |
|January 16, 2003 |AP3.46. | | |
|Hilert | | | |
|ADC 89 |Adds supplemental optional data fields to the |Effective Immediately | |
|Inclusion of Supplemental Information for |PDF 417 2D symbol for the purpose of unique | | |
|UIT/SIM in the Two-Dimensional Symbol on the |item identification. Allows for identification| | |
|Issue Release/Receipt Document (IRRD) (DD Form|of the manufacturer, part, and specific | | |
|1348-1A)(Supply/MILSTRIP) |individual item using a range of ANSI MH10.8.2 | | |
|(Staffed as PDC 83) |data identifiers, which may be employed as | | |
|14 Jan 2003 |applicable to the requirement. | | |
|Hilert | | | |
|ADC 93 |This change corrects documented procedures for |Staggered Implementation| |
|Inclusion of Status Code BP in MOV Procedures |MOV to include Status Code BP. | | |
|(Supply/MILSTRIP) | | | |
|3/17/03 | | | |
|Hilert | | | |
|ADC 102 |This change reassigns the use of Service/Agency|Phased implementation |Implemented |
|Revised Service Code V Use in Routing |Code V applicable to RICs to the Navy. The |steps which facilitate | |
|Identifier Codes (RICs) (Supply/ MILSTRIP) |V-series when used as the RI-To was previously |transition off the | |
|(Staffed as PDC 103) |assigned to the National Aeronautics and Space |V-series by NASA, and | |
|2/12/09 |Administration (NASA). All new RIC assignments|re-assignment to the | |
|Hilert |in the V-series will belong to the Navy for use|Navy. Effective date of| |
| |to designate Navy contractor locations. Any |August 15, 2009. | |
| |existing V-series RI values previously assigned| | |
| |for NASA will be deleted. | | |
|ADC 104 |ADC 44 (reference 3.a.) added a two-dimensional|Staggered implementation|DLA implementation July 2004 |
|Addition of RI of the Activity Originating the|(2D) symbol (Portable Data File (PDF) 417) that|is authorized. | |
|Order MRO/LRO/DRO to the 2D Symbol on the IRRD|included the current linear bar code data | | |
|(DD Form 1348-1A) |elements plus additional elements to the IRRD. | | |
|9/22/03 |ADC 89 (reference 3.b.) incorporated additional| | |
|Hilert |data elements for the purpose of unique item | | |
| |identification | | |
| |/management/tracking. This proposal adds an | | |
| |additional data field to the 2D symbol to | | |
| |reflect the RI of the activity originating the | | |
| |MRO/LRO/DRO, which is currently carried in rp | | |
| |67-69. | | |
|ADC 105 |This change requires clear-text identification |Staggered implementation|AF implementation in retail systems |
|Identification of Items on United States |on all DOD shipments of items shown on the USML|is authorized. |(SBSS/CMOS). |
|Munitions List (USML) for U.S. Customs |to transportation/traffic management offices | | |
|Clearance (Supply/MILSTRIP) |for the United States Customs Service. | |DLA uses DEMIL code approach for |
|8/22/03 | | |identification. |
|ADC 107, |This revision updates the 861 Federal IC by |Immediately | |
|Revised Federal IC 861 for WAWF Receiving |adding qualifier to identify the Standard | | |
|Advice/ |Document Number (SDN). | | |
|Acceptance Certificate (Contract | | | |
|Administration) | | | |
|09/22/03 | | | |
|Hilert | | | |
|ADC 110A, |This is an administrative change to modify an |Immediate implementation|USAF Implemented |
|DAASC Processing of AF Requisitions and Others|ADC 110 MILSBILLS edit to permit reversal bills|is authorized. | |
|with Billing Restrictions- Revised |to process. | | |
|03/14/05 | | | |
|Hilert | | | |
|ADC 110B, |This change expands the United States USAF |11/31/05 |USAF Implemented |
|Additional USAF (AF) Requisition and |requested edits approved under ADC 110 and ADC | | |
|Interfund Bill Restrictions (Supply/Finance) |110-A. This change further revises requisition| |DAASC Implemented 11/17/05 |
|10/31/05 |and interfund bill processing to reject | | |
|Hilert |transactions which identify a bill-to party | | |
| |reflecting an USAF DOD Activity Address Code | | |
| |(DODAAC) not authorized for use as the bill-to | | |
| |party. | | |
|ADC 110C |This change expands the USAF requested edits |No Later than 4/16/06 |Implemented at DAASC |
|Additional AF Requisitions to Interfund Bill |approved under ADC 110, ADC 110-A and ADC | |Published in MILSTRIP Reissue, Oct 2007 |
|Restrictions |110-B. This change further revises requisition;| | |
|(Supply/Finance) |turn in of material and hazardous waste to | | |
|3/16/06 |Defense Redistribution and Marketing Service | | |
|Hilert |(DRMS), and interfund bill processing to reject| | |
| |transactions which identify a requisitioner or | | |
| |bill-to party reflecting an AF DOD DODAAC not | | |
| |authorized for use as the bill-to party. | | |
| | | | |
| | | | |
|ADC 110D |Under the original ADC 110 (reference 3.b.), an|Immediately |Implemented at DAASC |
|U.S. USAF (USAF) Interfund Bill Restrictions |edit was established to trigger DAAS rejection | | |
|(Finance) |of bills containing USAF DODAACs which may not | | |
|6/29/06 |be used in interfund billing. Under ADC 110A | | |
|Hilert |(reference 3.c.), a revision was authorized so | | |
| |that credit bills (SBR begins with FS2) were | | |
| |allowed to process. This change revokes ADC | | |
| |110A, and restores the original ADC 110 edits. | | |
| |Revisions are identified in bold italics. | | |
|ADC 110E |This change expands the USAF edits approved |Immediately |Implemented at DAASC |
|Additional U.S. USAF (USAF) Interfund Bill |under ADC110, to trigger DAAS rejection of | | |
|Restrictions |bills containing USAF DODAACs that may not be | | |
|(Finance) |used in billing. Comments received during | | |
|10/3/06 |formal staffing are enclosed. | | |
|Rhone-Jones | | | |
|ADC 111 |This change incorporates the functionality of |EBS implementation | |
|Weapon System Data Change DS 888W |the DLA weapon system data change transaction |planned for late 2005 or| |
|(Staffed by PDC 102) |formats into the DLMS for the purpose of |early 2006 | |
|Supply) |interfacing between legacy systems and the DLA | | |
|1/28/04 |BSM program. | | |
|Hilert | | | |
|AMCL 117 |Provides additional Advice Codes to Appendix |5/1/87 |Last reported as not |
|Addition of Advice Codes, Appendix B15 |B15 | |implemented by USAF. |
|ADC 118 |This change modifies the DS 536L LR Management |DAASC and DLA have | |
|Revision to DS 536L Logistics Reassignment |Data to incorporate data elements necessary to |authorization to employ | |
|(LR) Management Data. |carry data contained in MILSTRAP DI Code DLT, |these procedures | |
|(Staffed by PDC 119) |LR Backorder and Demand Data transaction, |immediately under EBS | |
|Supply (MILSTRAP) |Record 4. Also accommodates in DLMS, the data | | |
|4/26/04 |approved by ADC 115 for MILSTRAP DLT Record 4, | | |
|Johnson |and supports the DLA BSM SAP use of the DLMS | | |
| |536L to pass LR backorder and demand data. | | |
|ADC 122, |The 856 is modified to support capture of |Immediately |Implemented in WAWF |
|Revision to Federal IC 856, Ship |foreign currency in association with the | | |
|Notice/Manifest, Supporting Foreign Currency |contract unit price for the IUID item on the | | |
|Requirement for UID Registry |IUID registry | | |
|(Contract Administration) | | | |
|06/24/04 | | | |
|Hilert | | | |
|AMCL 122 |Provides Media and Status Codes to indicate |11/1/85 |Last reported |
|Media and Status Codes to Indicate Status to |status to both the Requisitioner and | |as not implemented by USAF. |
|Both the Requisitioner and Supplemental |Supplemental Addressee | | |
|Addressee | | | |
|AMCL 123C |Updates Requisition Modifier procedures |11/1/85 |Last reported as not implemented by USMC |
|Requisition Modifier Procedures | | | |
|AMCL 124 |Provides procedures for Document Identifier |11/1/86 |Last reported as not implemented by USAF |
|Document Identifier Code AE8/AS8 for Supply |Code AE8/AS8 for Supply Source initiated | | |
|Source Initiated Requisition Status |requisition status | | |
|ADC 125 |This change revises DS 846D and MILSTRAP |Immediately by DLA and |Published in MILSTRAP CH 4. |
|DLA Unique Change to Logistics Reassignment |DEE/DEF to |DAASC | |
|(LR) Transfer/Decapitalization to |support Intra-DLA functionality requiring use | | |
|Add Price Type Indicator to MILSTRAP DEE/DEF |of the contract unit price; and makes | | |
|and to Add Contract Unit Price to DS 846D, and|administrative changes to DS 846D for | | |
|Admin DS 846D Changes (Supply) |corrections and for consistency with other DS. | | |
|(Staffed by PDC 125) | | | |
|07/15/04 | | | |
|Johnson | | | |
|ADC 126 |This is an intra-DLA change that applies in |DLA and the DAASC are |Published in MILSTRAP CH 4. |
|DLA Unique Change to MILSTRAP DAC and DS 947I,|both the DLSS and DLMS. It applies only to |authorized to | |
|Inventory Adjustment – Dual (Condition |procurement-related DI Code DAC transactions |employ these procedures | |
|Transfer) and Admin Changes to DS 947I |going to DLA ICP from any DLA distribution |immediately. | |
|(Supply) (Staffed by PDC 128) |activity. For procurement -related DACs, DLA | | |
|07/21/04 |cites the PIIN, CLIN and Call Order Number to | | |
|Johnson |ensure accurate mapping of the adjustment | | |
| |transaction to the correct procurement line | | |
| |item information. | | |
|ADC 127 |This change updates the DLMS Shipment Status |DLA and the DAASC are |RFID implementation on-going; UID implantation|
|UID of Items and RFID in DLMS Shipment Status |856S to carry UID information and passive RFID |authorized to |date not available |
|(Supply) |tag information. |employ these procedures | |
|(Staffed as PDC 122A) | |immediately. | |
|07/29/04 | | | |
|Hilert | | | |
|ADC 129, |The 856 is updated to provide additional |Immediately | |
|New DS for DLMS ASN Following Federal IC 856, |functionality to include the ability to capture| | |
|Shipment Notice/Manifest |IUID information consistent with IUID policy | | |
|(Contract/Administration) |and WAWF-RA, RFID information consistent with | | |
|(Staffed as PDC 117) |RFID policy, and for clarification of specific | | |
|10/01/04 |data fields. A DS is also provided to reflect | | |
|Hilert |the WAWF extract data content. | | |
|ADC 131 |This change creates two new DLMS transactions |Approved for |Phase I implementation: DSS and DLA interface|
|DLMS Submission of Electronic DD Form 1225, |for use within the stock readiness function to |implementation |with DAAS pass-thru, implemented February 08. |
|SQCR (Supply) |pass DD Form 1225, SQCR, data between | | |
|(Staffed as PDC 129) |distribution depots and Inventory Control | | |
|12/07/04 |Points. This change includes a DS 842SQ, SQCR,| | |
|Hilert |and a DS 842SR, SQCR Reply | | |
|ADC 132 |This change updates the Acceptance Report to | Jan 10, 2005 |DLA implementation within Distribution |
|DS for AR for UID and New Shipment/Acceptance |provide additional functionality to include | |Standard System. |
|Discrepancy (DLMS/MILSCAP) |ability to capture UID information consistent | | |
|(Staffed as PDC 116) |with UID policy and establishes a DS for DLMS | | |
|9/24/04 |use in reporting acceptance. | | |
|Hilert | | | |
|AMCL 132B (MILSTRIP) |Adds Status Code DA for requisition rejections |11/1/87 |Last reported implemented by all except: |
|Status Code DA for Federal Supply Schedule |to indicate the source of supply is direct | | |
|Rejections |ordering from the Federal Supply Schedule. | |USAF |
|ADC 133 |Revises the 527R to be consistent with the |Immediate implementation|Published in MILSTRAP CH 4. |
|Revision to DS 527R, Receipt, Inquiry, |placement of the mapping product data in DLMS | | |
|Response, and MRA to Accommodate |transactions developed under ADC 71A, Sep 2004,| | |
|Commodity-Unique (Mapping Products) Data |DLMS Mapping for Materiel Release | | |
|(Supply/DLMS) |Order/Disposal Release Order Exception Data | | |
|(Staffed as PDC 135A) |Transaction. | | |
|10/01/04 | | | |
|Johnson | | | |
|ADC 134 |Revises DS 846P, Physical Inventory Request, to|Immediate implementation|Published in MILSTRAP CH 4. |
|Revision to DS 846P, Physical Inventory |add the physical Inventory Cutoff Date | | |
|Request, to Add Physical Inventory Cutoff Date| | | |
|(Supply/DLMS /MILSTRAP) | | | |
|(Staffed as PDC 139) | | | |
|10/07/04 | | | |
|Johnson | | | |
|ADC 135 |Under the NIMS concept of operation, DLA will |Immediate optional |Published in MILSTRAP CH 4. |
|Revise DS 527D ARI and MILSTRAP DWK PMR to |own materiel for DLA-managed NSNs down to the |implementation | |
|Carry Status Code “BD” When Assets are Not |retail level based on agreements between DLA | | |
|Available to Replenish a National Inventory |and the Service. Replenishment of DLA owned | | |
|Management Strategy (NIMS) Site |assets will be accomplished under a push | | |
|(Implementation DoD Component Optional) |scenario (redistribution of DLA owned assets | | |
|(Supply/DLMS/MILSTRIP/ |from a distribution depot to a NIMS site when | | |
|MILSTRAP) (Staffed as PDC 140/140A) |assets at NIMS site fall below Reorder Point) | | |
|10/06/04 |vice the traditional pull scenario (submission | | |
|Vitko |of a requisition when assets fall below retail | | |
| |reorder point). | | |
|ADC 136 |This change accommodates data requirements for |Immediate implementation| |
|Revision to DS 846R Location Reconciliation |commodity unique (mapping products) data; | | |
|Request to Support Commodity-Unique (Mapping |additional MILSTRAP functionality; and | | |
|Product) Data and to Support MILSTRAP DZN/DZP |administrative updates. | | |
|functionality(Supply/MILSTRAP)(Staffed by PDC | | | |
|120A) | | | |
|11/04/04 | | | |
|Johnson | | | |
|ADC 139 |This change revises DS 830R (Planning Schedule |Immediate optional | |
|Revision to DS 830R to Accommodate Demand Data|with Release Capability) to include DLA BSM |implementation by | |
|Exchange (Transmitting Forecasts of Recurring |planning functionality of Demand Data Exchange.|agreement | |
|and Non-Recurring Demand Data) (Supply/DLMS) | | | |
|(Staffed by PDC 131) | | | |
|1/06/05 | | | |
|Johnson | | | |
|AMCL 139A (MILSTRIP) |Provides procedures, formats, and codes for |11/1/86 |Last reported implemented by all except: |
|Requisitioning DoD Excess Personal Property |requisitioning material from disposal. | | |
|from Disposal | | |DLA |
|8/7/86 | | | |
|ADC 140 |Admin change to add the Shipper RI Code to DS | |Withdrawal of ADC 140 – Published on 3/07/07 -|
|Revise DS 527R to Acknowledge Navy Requirement|527R consistent with requirement established | |withdrawal action is based upon ADC 216, dated|
|for Shipper Routing Identifier Code in Support|for DS 527D by ADC 124, July 8, 2004, Subject: | |November 7, 2006, which revised DS 527R |
|of Navy Commercial Asset Visibility - Organic |ADC 124, Revise MILSTRAP DWK, PMR to | |receipt in support of CAV, and deleted |
|Repairables Module (Supply) |Acknowledge Navy | |qualifier “SF-Ship From” and its associated |
|01/10/05 |Requirement for Shipper RI Code in Support of | |notes from the DS. |
|Johnson |Navy CAV - Organic Repairables Module. | | |
|ADC 143 |This change uses the valued added services of |4/30/05 |On hold pending re-validation of requirement |
|Fund Code and other DLMS Support for |DAASC, interfund billing records, and the | |under SFIS |
|Intra-Governmental Transactions (IGT) |expanded fund code reference table to support | | |
|(Finance) |financial requirements for IGT. | | |
|12/14/04 | | | |
|Velez | | | |
|ADC 144 |This update modifies both the SDR submission |Immediately |Phased implementation is ongoing |
|SDR Transaction Exchange Business Rules |(842A/W) and the SDR Reply (842A/R) DS to make | | |
|(Supply) |adjustments which are required to support | | |
|03/15/05 |desired | | |
|Hilert |functionality. | | |
|ADC 145 |New DS to support the Medical community |Immediately | |
|New DS and Federal IC 650C, Component Packing |requirement for a DLMS Component Packing | | |
|Confirmation, in Support of Medical |Confirmation transaction. | | |
|Requirements (Staffed by PDC 127) (Supply) | | | |
|Johnson | | | |
|1/06/05 | | | |
|AMCL 145 (MILSTRIP) |Modifies definitions for Document Number |11/1/89 |Last reported implemented by all except: |
|Revision to Alphabetic Codes Contained in |alphabetic codes for codes M, R, and S. | | |
|Document Number, Column 40, Appendix B7 | | |USN, USAF, & USMC |
|7/25/85 | | | |
|ADC 146 |This change modifies one segment of the DS |Immediately | |
|Revise Small Arms Data Change, DS 888A |888A, | | |
|(Supply) (Staffed by PDC 151) |Small Arms Data Change and the commensurate | | |
|01/10/05 |DAAS map to reflect additional conditions | | |
|Johnson |required by the Small Arms Multi-Field | | |
| |Corrections, MILSTRAP DI Code DSA. | | |
|ADC 147 |This change modifies DS 140A, Small Arms Data |Immediately | |
|Revise DS 140A Small Arms Reporting to Reflect|Change, to revise all occurrences of | | |
|Serial Number and Other Admin Change (Supply) |terminology ‘UII’ to ‘Serial Number’. This | | |
|(Staffed by PDC 156) |change is necessary to clarify that small arms | | |
|01/10/05 |serial numbers do not comprise a UII under | | |
|Johnson |conditions imposed by the DoD UID initiative. | | |
|ADC 148 |This change updates DS 527D and 527R |Implementation dependent| |
|Inclusion of Data Supporting UID of Items in |transactions to carry unique item identifier |on Components. | |
|DLMS 527D Due-in, Advance Receipt, Due |(UII) data for unique identification (UID) of | | |
|Verification and DLMS 527R Receipt, Inquiry, |assets. Component system changes which are | | |
|Response and MRA (Supply) (Staffed by PDC 114)|required to support the integration of the UII | | |
|01/12/05 |data are not identified in this change and must| | |
|Johnson |be addressed by the Components. | | |
|AMCL 148 (MILSTRIP) |Establishes RDP for conventional ammunition |11/1/87 |Last reported implemented by all except: |
|Required Delivery Period (RDP) |requisitions. | |USAF – As of 4/28/03 USAF plans to implement |
|8/30/85 | | |RDP in 2 years under CAS 2.0. |
| | | | |
| | | |AMCL 148 was not implemented under CAS 2.0 and|
| | | |is not planned for implementation other than |
| | | |when the AF implements a later version of ECSS|
| | | |(estimate of 2012). |
|ADC 149 | |Immediately |ADC 149 is superseded by |
|DS 650A in Support of Requirements for the | | |ADC 149A |
|Medical Unit Assembly Program | | | |
|ADC 149A |ADC 149A revises DS 650A as published by ADC |Immediately | |
|Correction to DS 650A in Support of |149, to correct a syntax error in the MTX | | |
|Requirements for the Medical Unit Assembly |segment as described in paragraph 4 below. | | |
|Program | | | |
|5/25/05 | | | |
|Johnson | | | |
|ADC 150 |This is an administrative change to revise DS |Immediately | |
|Revise DS 830W, War Materiel Requirements, |830W, War Materiel Requirements, with admin | | |
|with Admin Changes (Supply) |changes and corrections. | | |
|01/24/05 | | | |
|Johnson | | | |
|AMCL 150C (MILSTRIP) |Establishes procedures to reinstate canceled |11/1/90 |Last reported implemented by all except: |
|Reinstatement of Canceled Transactions |requisitions. | |USN – No date available due to legacy system |
|5/21/90 | | |freeze |
|ADC 151 |This change modifies both the 846L and 846S DS |Immediately | |
|Admin Revisions to DS 846L, Logistics Asset |to incorporate admin updates for consistency | | |
|Support and 846S, Logistics Reassignment |with other DS and to incorporate approved | | |
|Storage Transfer/Order/Reply (Supply) |changes as needed. | | |
|02/24/05 | | | |
|Johnson | | | |
|ADC 152 |This change modifies both the 888I and 867D to |Immediately | |
|Admin Revisions to DS 888I, Storage Item |incorporate administrative updates for | | |
|Correction and 867D, Demand (Supply) |consistency with other DS. | | |
|02/10/05 | | | |
|Johnson | | | |
|AMCL 152 |Establishes Advice Codes 34 and 39 |5/1/87 |Last reported as not implemented by USAF |
|Use of Advice Codes 34 and 39 | | | |
|ADC 153 |This change updates DS 867I to carry UII data |Implementation dependent| |
|Inclusion of Data Supporting UID of Items in |for UID of assets. Component system changes |on Components. | |
|DS 867I, Product Transfer and Resale Report |which are required to support the integration | | |
|(Issue) and Other Admin Changes (Supply) |of the UII data are not identified in this | | |
|(Staffed by PDC 157) |change and must be addressed by the Components.| | |
|02/10/05 | | | |
|Johnson | | | |
|ADC 155 |This change updates DS 846A, 846F and 846I to |Implementation dependent| |
|Inclusion of Data Supporting UID of Items in |carry unique item identifier (UII) data for |on Components. | |
|DS 846A, Asset Reclassification; 846F, |unique identification (UID) of assets. | | |
|Ammunition Freeze/Unfreeze; and 846I, Asset |Component system changes which are required to | | |
|Status Inquiry/Report (Supply) |support the integration of the UII data are not| | |
|(Staffed by PDC 159) |identified in this change and must be addressed| | |
|02/24/05 |by the Components. | | |
|Johnson | | | |
|AMCL 155 (MILSTRIP) |Changes use of DI Code AB_ from intra- to |11/1/89 |Last reported implemented by all except: |
|Inter-Service Use of DI Codes AB_ for Direct |inter-Service. | | |
|Delivery From Procurement | | |DLA (Subsistence) and GSA |
|4/16/87 | | | |
|ADC 156 |This change updates DS 947I (version 4030) to |Implementation dependent| |
|Inclusion of Data Supporting UID of Items in |carry unique item identifier (UII) data for |on Components. | |
|DS 947I, Inventory Adjustment |unique identification (UID) of assets. | | |
|(Supply) (Staffed by PDC 160) |Component system changes which are required to | | |
|2/15/05 |support the integration of the UII data are not| | |
| |identified in this change and must be addressed| | |
| |by the Components. | | |
|AMCL 156 (MILSTRIP) |Clarifies use of status transactions for FMS. |11/1/90 |Last reported implemented by all except: |
|FMS Status Procedures | | |DLA (Subsistence) |
|3/11/87 | | | |
|ADC 157, |This change updates DS 527D and 527R |Implementation dependent| |
|Optional Capability for Sending Information |transactions to provide |on Components. | |
|Copy of DS 527D and 527R to a Component UIT |capability to send an information copy of the | | |
|Registry (Staffed by PDC 163) (Supply) |transactions to a stand-alone Component UIT | | |
|03/31/05 |registry. Also adds URL to the list of code | | |
|Johnson |structures available for the registry, such as | | |
| |DUNS, DODAAC, etc. | | |
|ADC 158 |This change is necessary to support existing |Already implemented by |Published in MILSTRAP CH 4. |
|RFID for ADC 158, Requirement for |DOD policy |some Components and can | |
|Prepositioned Materiel Receipt (PMR) |requiring that a current record of all |be implemented on a | |
|(Supply/MILSTRAP/SDR) |anticipated materiel receipts shall be |staggered basis by the | |
|06/27/05 |available to receiving storage activities. In |remaining Components. | |
|Johnson/Hilert |addition, this change provides for notification| | |
| |to the owner/manager that | | |
| |prescribed procedures for establishing a PMR | | |
| |have not been observed. | | |
|AMCL 158B (MILSTRIP) |Establishes intransit control procedures for |11/1/92 |Last reported implemented by all except: |
|Intransit Control Procedures for Shipments to |shipments to DRMOs. (AMCLs 16 &17 should be | | |
|DRMOs |implemented with 158B as they affect the same | |USAF & USMC |
| |procedures/transactions.) | | |
|ADC 159 |This update corrects a DLMS note in the 867D |Immediately | |
|Admin Correction to DS 867D, Demand (Supply) |DS. | | |
|0303/05 | | | |
|Johnson | | | |
|ADC 160, |This change creates a new DS 824R Reject |Immediately | |
|New Federal IC and DS 824R Reject Advice |Transaction. In DLMS, this transaction will be | | |
|Transaction |used in place of the MILSTRAP DI DZG Reject | | |
|(Supply) (Staffed by PDC 165) |transactions. Initial development is to provide| | |
|04/11/05 |reject capability formerly provided by MILSTRAP| | |
|Johnson |DI Code DZG and so DS 824R applies to a select | | |
| |group of DS | | |
|ADC 161, |This revision corrects the 945A DS by adding |Immediately | |
|Admin Revision to DS 945A, Material Release |missing | | |
|Advice, to add Advice Code (Supply) |qualifier to identify the Advice Code. Advice | | |
|04/04/05 |Code is present in the equivalent MILSTRIP | | |
|Hilert |format for A6_, Material Release Denial, but | | |
| |was inadvertently dropped from the DLMS format.| | |
|AMCL 161 (MILSTRIP) |Defines procedures for quantity adjustment |11/1/87 |Last reported implemented by all except: |
|Unit of Issue in Materiel Management |related to requisitions with Advice Codes 2D, | | |
|5/14/87 |27, or 29. | |DLA (Subsistence) and GSA |
|ADC 162 |This revision corrects both the 4010 856 and |Immediately |Incorporated in WAWF release 3.12 for standard|
|Correction to DSs 4010 856 ASN and 4010 861 |4010 861 DSs by adding missing qualifiers for | |transaction format. |
|Acceptance Report to Add Missing Qualifiers |identification of Component unique data. | | |
|for Component Unique Data Content | | | |
|(Supply/Contact Administration) | | | |
|4/14/05 | | | |
|Hilert | | | |
|AMCL 162 (MILSTRIP) |Provides correct unit of issue when original |11/1/87 |Last reported implemented by all except: |
|Requisition Rejection, Incorrect Unit of Issue|unit of issue on the requisition could not be | | |
|9/3/87 |converted. | |USN and DLA (Subsistence) |
|ADC 164 |Incorporate data elements necessary to support |Immediately | |
|Revision to DS 846P, Physical Inventory |the functionality of MILSTRAP DI Code DZM, End | | |
|Request, to Accommodate Functionality of End |of Day Accountable Transaction Count. | | |
|of Day Transaction Count (MILSTRAP DZM) and to| | | |
|Provide Transaction Clarification and admin | | | |
|changes (Supply) (Staffed by PDC 166). | | | |
|5/06/05 | | | |
|Johnson | | | |
|ADC 165 |This change updates DS 856, 856S, 861, 867I, |Implementation dependent| |
|Optional Capability for Sending Information |870M, 945A, and 947I to provide capability to |on Components. | |
|Copy of DS 856, 856S, 861, 867I, 870M, 945A, |send an information copy of the transactions to| | |
|and 947I to a Component UIT Registry (Supply) |a standalone | | |
|6/10/05 |Component UIT registry when/if an integrated | | |
|Johnson |AIS approach is not used for UIT. | | |
|AMCL 166 (MILSTRIP) |Establishes Status Code BP indicating |11/1/92 |Last reported implemented by all except: |
|Status Code for Planned Program Requirements |requisition deferred with estimated shipping | | |
|11/5/87 |date provided. | |DLA (Subsistence) |
|ADC 167 |This change incorporates Component unique data |immediately |DLA BSM implementation scheduled for early |
|Component Unique Data Content within DS 888W, |content within the DLA weapon system data | |2006. DAASC will provide conversion until |
|Weapon System Data Change |change transaction formats. This will ensure | |Component implementation. |
|(Supply)(Staffed as PDC 168) |that Component required information is | | |
|6/13/05 |perpetuated within the DLMS as it was under | | |
|Hilert |legacy system processing. | | |
|AMCL 167 |Modifies the Material Returns Program (MRP) to |5/1/90 |Last reported by implemented USMC |
|Modified Material Returns Program (MRP) to |include part Numbered excess reports | | |
|Include Part Numbered Excess Reports | | | |
|Approved Addendum to ADC 167A, New Transaction|This change provides a new value for the |Approved for | |
|Originator Code (TOC) Designating DoD E-MALL |Transaction Origination Code (TOC) to be |implementation June 21, | |
|for use in DS 888W, Weapon System Data Change |recognized on DLMS transactions associated with|2010. | |
|(Supply) |the Weapon Systems Support Program (WSSP) as | | |
|5/21/10 |indicating that the transaction originated | | |
|Hilert |within DoD EMALL. This change is an addendum | | |
|DLA |to approved procedures documented under ADC | | |
| |167. | | |
|ADC 168 |This change migrates the Federally-approved IC |immediately | |
|New DS 4010 567C, Contract Completion Status |567 transaction from X12 version 3050 to 4010, | | |
|(DLMS Contract Completion Statement/Unclosed |identifies the new IC as 567C, and provides a | | |
|Contract Status/Contract Close-out Extension) |corresponding DS. The DLMS transaction 4010 | | |
|(Supply) |567C is provided for Contract Administration | | |
|8/15/05 |Offices (CAOs) for use in reporting to POs, | | |
|Hilert |both closed and unclosed contract file status. | | |
| | | | |
| | | | |
| | | | |
|AMCL 168 (MILSTRIP) |Requires the entry of CIICs on DTIDs. |5/1/88 |Last reported implemented by all except: |
|Controlled Inventory Item Codes on Turn-Ins to| | | |
|Defense Reutilization and Marketing Offices | | |NIMA |
|11/30/87 | | | |
|ADC 169 |This change updates the DLMS 511R, 511M, 940R, |Implementation dependent| |
|Inclusion of UID of Items in DLMS Requisition |and 945A, transactions to carry UID data. |on Components. | |
|and Material Release Transactions. |Component system changes which are required to | | |
|(Supply) (Staffed as PDC 153) |support the integration of the UID data | | |
|6/14/05 |requirements are not identified in this change.| | |
|Hilert | | | |
|ADC 170 |This change updates DS 180M and 870M to carry |Implementation dependent| |
|Inclusion of Data Supporting UID of Items in |unique item identifier (UII) data for unique |on Components. | |
|DS 180M, |identification (UID) of assets | | |
|and 870M, (Supply/UIT) | | | |
|6/30/05 | | | |
|Hilert | | | |
|ADC 171, |This change updates DS 140A to carry the unique|Implementation dependent| |
|Inclusion of Data Supporting UID of Items in |item identifier (UII) in support of DOD UID |on Components. | |
|DS 140A (Supply)(Staffed as PDC 162) |policy. | | |
|6/22/05 | | | |
|Johnson | | | |
|ADC 172, |ADC 172 establishes two indicators for use in |Implementation dependent|DLA DSS release 7.1. |
|RFID for Approved DLMS Change (ADC) 172, New |the DS 527D, ARI transaction (formerly PMR |on Components. |DAAS-populated RFID Indicator supporting DLA |
|UIT Designator Code, and Inclusion of UID and |transactions in MILSTRAP), in support of UID | |implemented Feb 08. |
|RFID Indicators in DS 527D Advance Receipt |and RFID policy. The intent is to provide an | | |
|Information (Supply/UID/RFID) (Staffed by PDC |automated mechanism for the ICP to notify the | | |
|149) |receiving activity in advance that that there | | |
|8/18/05 |is a contractual requirement for UID or passive| | |
|Johnson |RFID. | | |
|ADC 173 |This update deletes code “ABR – Assigned by |Immediately | |
|Admin Correction to DS 846A, Asset |Receiver | | |
|Reclassification (Supply) |in the LQ segment of DS 846A; and provides an | | |
|8/12/05 |admin update to delete a DLMS note in the LIN | | |
|Johnson |segment. | | |
|ADC 174 |This change updates business processes using |Approved for phased | |
|Inclusion of Data Supporting UID of Items in |DOD WebSDR and the DS 842A/W to carry UII data |implementation beginning|Implemented for transaction exchange. Web |
|DS 842A/W, SDR, WebSDR (Supply/SDR) |for UID of assets. Component system changes |March 2006 |entry deferred. |
|(Staffed by PDC 172) |which are required to support the integration | | |
|2/23/06 |of the UII data are not identified in this | | |
|Hilert |change and must be addressed by the Components.| | |
| |The DLMS and DOD4140.1-R, DOD Supply Chain | | |
| |Materiel Management Regulation, provide for | | |
| |unique item tracking (formerly called serial | | |
| |number tracking) for specific DOD UIT programs.| | |
|ADC 176 |Provides DADMS notification if the received |Immediately |Implemented. |
|Revision to Requisition Format to Accommodate |requisition is the first request or if the | | |
|Commodity-Unique (Mapping Products) Data |received requisition was previously sent to | | |
|(Supply) (Staffed by PDC 180) |DADMS. This will prevent DADMS from resending | | |
|8/29/05 |the requisition to MSODS to fill. MSODS | | |
|Hilert |includes their RIC so DADMS will understand | | |
| |that MSODS was unable to satisfy the | | |
| |requisition received from DADMS. The presence | | |
| |of the RIC SD7 in the requisition is a denial | | |
| |mechanism for the DADMS/MSODS interface. | | |
|ADC 177 |This change request makes available for use |WAWF | |
|ASN 856 Cancellation and Correction |additional codes within the Beginning Segment |Implementation 12/19/05.| |
|Functionality (Post Acquisition/MILSCAP) |(BSN) of the 856 ASN transaction to support | | |
|(Staffed by PDC 181) |capability to identify cancellations and |BSM implementation is | |
|9/15/05 |corrections |planned for Release 2.2 | |
|Hilert | |in January 2006. | |
|ADC 178 |The C2L transaction provides the requisition |1/01/2006 | |
|DS 511R Requisition to Support DEPMED Unit |data to the source of supply for DEPMED units | | |
|Assembly |which require assembly. Its basic structure | | |
|(Order Fulfillment/Supply) |mirrors the | | |
|(Staffed by PDC 179) |MILSTRIP Requisition, DI Code A0_. It is not | | |
|9/07/05 |currently translated by DOD DAASC into DLMS | | |
|Hilert |X12. This PDC requests the DLMS and DAASC maps | | |
| |be updated to incorporate the C2L transaction | | |
| |in the DS 511R. | | |
|ADC 179 |This change expands the scope of DS 824R, |Implementation Dependent| |
|Revisions to DS 824R, Reject Advice, to |Reject Advice. |on Components. | |
|include DAASC Narrative Rejects, and Expansion| | | |
|for Rejection of Additional DLMS Transactions | | | |
|(Contract Administration / Supply) (Staffed by| | | |
|PDC 171) | | | |
|9/13/05 | | | |
|Johnson | | | |
|ADC 180 |The change is provided to support the medical |12/2005 |Implemented. However full capability under |
|Revision to Material Release 940R DS to add |and industrial kitting community requirements. | |DLMS not available at this time. |
|AIN and BDN |The basic processes involved in the information| | |
|(Supply) (Staffed by PDC 184) |exchanges | | |
|9/27/05 |covered by this change are consistent with | | |
|Hilert |current processes used by the DLA and USAMMA, | | |
| |however, the medium of exchange will be the | | |
| |DLMS ASC X12 standard transaction set rather | | |
| |than the current DLSS DLA-unique MRO A5_ | | |
| |transaction used to requisition medical kits. | | |
|ADC 181 | | |-------WITHDRAWAL --- |
|Withdrawal of ADC 181, FMS SDR for Latent | | | |
|Defects | | |ADC 181A replaces ADC 181 |
|11/9/05 | | | |
|Hilert | | | |
|ADC 181A |This change adds clarifying information for |Immediately |Published in DLMS Manual, Vol II, Chapter 17, |
|Foreign Military Sales (FMS) SDR for Latent |submittal of a latent defect under the Supply | |Change 4 |
|Defects |Discrepancy Report “Latent Defects” submission | | |
|(Supply/SDR) |criteria. It also clarifies intent to process | | |
|(Staffed by PDC 174/ADC 181) |quality-related SDRs under PQDR procedures. | | |
|6/6/06 | | | |
|Hilert | | | |
|ADC 182 |This change request makes available for use |12/19/05 |Scheduled for DSS/WAWF implementation by Jan |
|Increased Functionality for DLMS 861, |additional codes within the BRA and RCD Segment| |06. |
|Acceptance Report |codes of the DLMS 861, Acceptance Report (AR). | | |
|(MILSCAP/Post Acquisition) (Staffed by PDC |Additional clarifying notes are added to the | | |
|182) |DS. | | |
|9/22/05 | | | |
|Hilert | | | |
|ADC 183 |This change provides for identification of |12/31/05 |DLA advised implemented during the design |
|DS 511R Requisition Revisions Supporting DOD |contract number, unique order number, sales | |stage |
|EMALL Part Number Catalog Orders |price, and contract price in the 511R as | | |
|(Staffed by PDC 185) |applicable to part number orders for DLA | | |
|10/12/05 |supplied items under DLA contracts for DOD | | |
|Hilert |EMALL. | | |
|ADC 184 |This change revises SDR business rules for |Immediately |Implemented |
|Redistribution Order (RDO) – based Supply |routing SDRs resulting from RDO shipments using| |Published in DLMS Manual, Vol II, Chapter 17, |
|Discrepancy Report (SDR) |the DLMS 842 transaction and the DOD WebSDR for| |Change 4 |
|(Supply/SDR) |distribution. This change provides new rules | | |
|10/24/05 |for routing action copy to the shipping depot | | |
|Hilert |and information copy to the material owner. | | |
|ADC 185 |This change modifies the 536L DS to incorporate|Immediately | |
|Admin revision to DS 536L (Supply) |administrative updates to remove erroneous | | |
|10/13/05 |codes, and for consistency with other DS. | | |
|Johnson | | | |
|ADC 186 |The TAMMIS/DMLSS generates a transaction that |Immediately | |
|DLMS Requisition Revisions to Support TEWLS |provides the requisition data to the source of | | |
|(Order Fulfillment/Supply) |supply. Its basic structure is a MILSTRIP | | |
|(Staffed by PDC 188) |Requisition, DI Code A0_. The TEWLS | | |
|12/16/05 |requisition format optionally contains an | | |
|Hilert |Account Processing Code (APC) in rp 75-78 that | | |
| |enables the requesting customers to identify | | |
| |the financial account. | | |
|ADC 187 |This change documents current procedures for |Immediately |Implemented at DAAS and AFSAC. DSS and BSM |
|Revise SDR Reply Procedures for Forwarding |forwarding SDRs within the DOD WebSDR and | |implementation scheduled for June 06. |
|SDRs to New Action Activity, E-mail Addresses,|proposed changes to accommodate more | | |
|and SoS |appropriate transaction design. This ADC | | |
|(Supply/SDR)(Staffed as PDC 191A) |documents use of WebSDR to generate/distribute | | |
|12/13/05 |a new report when the original was sent to the | | |
|Hilert |wrong action activity and distribution of | | |
| |reports and replies via e-mail based upon | | |
| |e-mail address extracted from the incoming | | |
| |transaction. This change also reflects | | |
| |identification of the source of supply on the | | |
| |reply transaction. | | |
|ADC 188 |This change defines reporting of quality |Jan – Feb 2006 |Implemented |
|Quality-Related Discrepancies Identified |discrepancies during receipt and storage when | |Published in DLMS Manual, Vol II, Chapter 17, |
|During Distribution Depot (DD) Receipt and |DOD material owners specifically request | |Change 4 |
|In-Storage Screening (Supply/SDR/SQCR) |screening from Defense DD. | | |
|(Staffed by PDC 190) | | | |
|1/9/06 | | | |
|Hilert | | | |
| | | | |
|ADC 189 |This change incorporates in DS 650C, |1/14/05 | |
|Revise DS 650C, Component Packing |functionality which exists in the 80-record | | |
|Confirmation, to Allow for Functionality of |position Document Identifier (DI) Code C2F, | | |
|Decimal Capability in Quantity Packed (Supply)|Component Packing Confirmation transaction. | | |
| |The DLA-unique DI Code C2F provides for up to | | |
|(Staffed by PDC 192) |two decimal positions for quantity packed. | | |
|12/14/05 | | | |
|Johnson | | | |
|ADC 190 |This change provides procedures for registering|New management codes are| |
|Visibility and Traceability for U.S. Weapons |weapons when a DOD agency assumes title and |authorized for use in | |
|Purchased or Produced Under a DOD Contract and|accountability for U.S. weapons purchased or |the DLMS. DAASC will | |
|Shipped Directly to Security Assistance or |produced under a DOD contract, and then shipped|support conversion | |
|Other Customers Outside of the DOD |directly to Security Assistance or other |between MILS and DLMS | |
|(DODSASP) |customers outside of the DOD. The purpose is to|transactions | |
|(Staffed by PDC 197) |ensure that all weapons are reported and | | |
|12/19/05 |registered when the DOD assumes title and | | |
|Johnson |accountability. | | |
|ADC 191 |This change establishes two new management |Immediately |Published in MILSTRIP Reissue, Oct 2007 |
|Management Codes on Supply Status Transaction |codes for use on the Supply Status transaction.| | |
|(Supply/MILSTRIP) |Both new management codes are authorized for | | |
|(Staffed as PDC 198) |use in the DLMS. The DAASC will support | | |
|3/14/06 |conversion between MILS and DLMS transaction | | |
|Hilert |when used. | | |
|ADC 192 |This administrative update opens the ST03 data |Immediately | |
|Admin Revision to DS 4030 856S, Shipment |element in the 4030 856S and adds clarification| | |
|Status (Supply) |notes. | | |
|3/14/06 | | | |
|Hilert | | | |
|ADC 193 |This admin update adds missing data to the 856S|Immediately | |
|Admin Revision to DS 4030 856S, Shipment |and 870S DS. BSM is already using the GP | | |
|Status and 4010 870S, Supply Status (Supply) |qualifier for their DLMS equivalent of the | | |
|4/4/06 |Supply Status (AE8). | | |
|Hilert | | | |
|ADC 195 |This change provides for DOD 4000.25-M, DLMS, |Immediately | |
|DLMS Unique Item Tracking (UIT) Procedures |Volume 2, UIT (formerly called serial number | | |
|(Staffed by PDC 147A) (Supply/UIT) |tracking) procedures. The purpose is to | | |
|4/10/06 |support the changing environment for | | |
|Hilert |maintaining visibility of uniquely identified | | |
| |assets for the primary purpose of inventory | | |
| |control and/or engineering analysis and to | | |
| |develop procedures to support evolving UIT | | |
| |systems. | | |
|ADC 196 |This change request defines the proposed |Estimated implementation|Partial implementation |
|Business Rules for SDRs Resulting from LRO for|routing and |date (for phase I) is | |
|DLA-Managed/NAMI Owned |processing of SDRS that result from DLA ICP/IMM|6/15/06 |Published in DLMS Manual, Vol II, Chapter 17, |
|Material (Supply/SDR) |directed LRO shipments under the TAV program. | |Change 4 |
|(Staffed by PDC 210) | | | |
|5/16/06 | | | |
|Hilert | | | |
| | | | |
|ADC 197 |DLA requests the establishment of a new Type of|Immediately |DLMSO comment: DLA required the change for |
|Request for New Type of Physical |Physical Inventory/Transaction History code for| |their modernized system, BSM, interface with |
|Inventory/Transaction History Code and Add |use with Transaction History Requests DS 846P | |DSS. Implementation by other DoD Components is|
|Code to Historical Transactions (DS 527R, |/MILSTRAP DI Code DZJ and DZK) to differentiate| |optional, but all were encouraged to consider |
|867I, 940R, 945A) (Staffed by PDC 219) |transaction history associated with annual | |the requirement for their modernized systems. |
|6/5/06 |reconciliation from other transaction history. | | The intent was not to require changes to |
|Johnson | | |legacy systems such as CCSS |
|ADC 198 |The capability to identify that no history is |Immediately | |
|Revise DS 846P to Provide Capability to Advise|available in response to a request for | | |
|When No History is Available in Response to a |transaction history exists in MILSTRAP, but was| | |
|Transaction History Request |not incorporated in DLMS. (DLA has identified | | |
|(Supply) (Staffed by PDC 207A) |the requirement for this capability for DSS and| | |
|6/6/06 |EBS. DS 846P, Physical Inventory Request, is a | | |
|Johnson |multipurpose transaction currently used to | | |
| |request physical inventory; to | | |
| |respond to a physical inventory request | | |
| |(without asset balances); and to request | | |
| |transaction history. | | |
|ADC 199 |These changes allow MRA to be processed in the |Immediately | |
|Revisions to DS 527R to Support Requirements |Defense Logistics Agency’s EBS from the DMLSS | | |
|for Tailored Vendor Relationships Materiel |for the TVR process. | | |
|Receipt Acknowledgment Transactions | | | |
|(Supply)(Staffed by PDC 204) | | | |
|6/14/06 | | | |
|Johnson | | | |
|ADC 200 |These changes allow receipts to be processed in|Immediately | |
|Revisions to DS 527R to Support Requirements |the Defense Logistics Agency’s EBS from the | | |
|for Army |DMLSS for AMMA prime vendor and purchase card | | |
|Medical Material Agreement Receipt |processes. | | |
|Transactions | | | |
|(Supply)(Staffed by PDC 215) | | | |
|6/14/06 | | | |
|Johnson | | | |
|ADC 201 |This change is to allow a price to be included |Immediately | |
|Revisions to DS 867I to Support Requirements |in AMMA issues of material. The price will | | |
|for the Army Medical Material Agreement Issue |allow the sale and resulting customer bill in | | |
|Transactions |DLA EBS to be priced appropriately. This | | |
|(Supply)(Staffed by PDC 216) |change also provides for use of a local catalog| | |
|6/22/06 |identification as issues from AMMA sites may be| | |
| |for a local catalog number and not a NSN. The | | |
| |Local Catalog Identification can reference | | |
| |multiple prime vendor part numbers for a | | |
| |specific site. | | |
|ADC 202 |This change is to allow inventory adjustments |Immediately | |
|Revisions to DS 947I to Support Requirements |for local catalog items at DMLSS and TEWLS | | |
|for the Army Medical Material Agreement |sites as part of AMMA. | | |
|Inventory Adjustment Transactions(Supply) | | | |
|(Staffed by PDC 217) | | | |
|6/7/06 | | | |
|Johnson | | | |
|ADC 203 |Revise DS 947I Inventory Adjustment to add 3 |Staggered implementation| |
|Revise DS 947I to Provide Distinct Qualifiers |qualifiers to the LQ segment for use with dual |dependent upon | |
|for Dual Adjustment Codes (Supply) (Staffed as|adjustments to distinctly identify the old |Components operating in | |
|RFID PDC 220) |supply condition code, ownership code and |DLMS. | |
|9/19/06 |purpose code from the new supply condition, | | |
|Johnson |ownership and purpose codes. |DLA DSS: | |
| | | | |
| | | |DSS SCR was submitted on 6/16/06 (INFO/MAN |
| | | |#132309). |
| | | |ADC 203 will be implemented in June 2007, in |
| | | |DSS Release 8.1. |
| | |DLA BSM: | |
| | | |BSM implemented in April 2007 (SCR |
| | | |BOF-06-074). |
| | |USAMMA | |
| | | | Response 8/30/2006: TEWLS Action Item 00797 |
| | | |has been created for ADC 203. This currently |
| | | |is not on the Functional Priority List and |
| | | |there is no foreseen completion date at this |
| | | |time. |
| | | | |
| | | |Reports on 12/28/07 ADC 203 has been completed|
| | |DLA | |
|ADC 204 |This change is to allow the IRM process to work|Immediately | |
|Revision to DS 846P and 846R to Support |for local catalog items at DMLSS and TEWLS | | |
|Requirements for the Army Medical Material |sites as part of the AMMA. | | |
|Agreement Inventory Records Management Process| | | |
| | | | |
|(Supply)(Staffed by PDC 225) | | | |
|8/6/06 | | | |
|Johnson | | | |
|ADC 205A |This change includes an admin update the DS |Immediately |ADC 205A Replaces ADC 205 |
|Assignment of MILSTRIP Document Number Serial |940R, and 945A. The change modifies the DLMS | |Published in DLMS Manual Vol II, Change 4 & |
|Number RP40/DLMS Utilization Code M for BRAC |note for use of the Utilization Code and | |MILSTRIP Reissue, Oct 2007 |
|(Staffed as PDC 218) |perpetuates the Utilization Code from the | | |
|9/11/06 |release order to the confirmation. | | |
|Hilert | | | |
|ADC 206 |This change establishes procedures and a new |9/1/06 |Implemented at DAASC. |
|Discrepancy Reporting for WPM |discrepancy code to be used for reporting | |DLA reports has been completed Published in |
|(Supply/SDR) |shipments containing non-compliant WPM under | |DLMS Manual Vol II, Chapter 17, Change 4 & |
|(Staffed by PDC 221) |reference 3a. | |MILSTRIP Reissue, Oct 2007 |
|8/14/06 | | | |
|Hilert | | | |
|ADC 207 |This change establishes new discrepancy codes |Immediately |Implemented at DAASC. |
|New Discrepancy Codes for Identification of |under | |Published in DLMS Manual Vol II, Chapter 17, |
|Hazardous Material Supply/SDR/SQCR |references a and b, and DLMS procedures, to | |Change 4 |
|(Staffed by 213A) |identify supply and storage discrepancies which| | |
|8/15/06 |pertain specifically to discrepant hazardous | | |
|Hilert |material identified at time of receipt or in | | |
| |storage. | | |
|ADC 208 |(1) Adds capability to include an Inspected |Published on 3/19/07 and| |
|Revised Inspection/Acceptance Report (DS 861)|Date, Inspection Location, and Acceptance |approved for | |
|to Support Inspection Advice and Shipment |Location to support source inspection and |implementation | |
|Level Acceptance |acceptance at other than the ship-to location. | | |
|(Contract Administration) (Staffed by PDC 205)|(2) Adds data content and usage notes to | | |
|3/19/07 |support shipment level acceptance as | | |
|Hilert |implemented under Navy modernization. | | |
|ADC 209 |This change establishes procedures for |Immediately |Implemented by DAAS and DoD EMALL and in use |
|Processing CFM requisitions between Government|processing Army CFM requisitions from Army | |for Army pilot programs. |
|Sources of Supply and Army contractors |Contractors which are authorized to utilize DLA| |Published in MILSTRIP Reissue, Oct 2007 |
|(Staffed as PDC 186) |as a SOS within Army PBL and associated | | |
|11/29/06 |contracts. Although this ADC is written to | | |
|Hilert |accommodate the Army business rules for | | |
| |contractor requisitions; the new controls | | |
| |established for CFM requisitions will be | | |
| |available to all Components. | | |
|ADC 210 |This modifies DoD WebSDR so that the existing |Immediately |Implemented |
|DRMS and NIMS Shipment Types Identified for |data element SDR Type Document Code may be | | |
|SDR Processing under DLMS |assigned as a result of direct user input via | | |
|Supply/SDR(Staffed by PDC 209) |the web. In addition, this change to both | | |
|10/18/06 |screens and the DLMS 842 transaction adds | | |
|Hilert |capability to identify specific types of SDRs | | |
| |as a sub-type of the original basic Type | | |
| |Document Code. This change allows visibility | | |
| |of the type on WebSDR record displays. This | | |
| |change also provides a format for a DRMS | | |
| |query/report. | | |
|ADC 210B |This change provides a new set of one-position |Implementation of the |Implemented with exception of DRMS reports |
|Identification of SDR Document Type (includes |type codes for the identification of non-DSS |procedures discussed in |(reporting requirement incorporated with |
|NIMS and Non-DSS Receipts) |wholesale material discrepant receipts. These |this addendum must |standard report/query functionality) |
|(Supply/SDR) |will distinguish DSS wholesale receipts from |coincide with DLA EBS | |
|3/27/07 |those at a NIMS site, non-DSS DD, or other |implementation. The | |
|Hilert |non-DSS location (e.g., commercially operated |target implementation is| |
| |storage facility). The DRMS portion of ADC |August 9, 2007. | |
| |210 is modified to isolate the second position | | |
| |into a separate data element. The DRMS reports| | |
| |functionality form ADC 210 remains valid. | | |
|ADC 211 |The change provides an exception/deviation to |Immediately |Implemented |
|Exception Processing for GFM for Packaged Fuel|the current requirements under MILSTRIP, | |Published in MILSTRIP Reissue, Oct 2007 |
|Additives Managed by DLA |Chapter 11, Contractor Access to Government | | |
|(Supply/Finance) |Supply Sources. | | |
|(Staffed as PDC 229) |This change establishes an automated DAASC | | |
|9/18/06 |edit/interface to provide MCA validation on a | | |
|Hilert |temporary basis for DESC-sponsored GFM | | |
| |requisitions of selected stock numbers. | | |
|ADC 212, |1. Add new qualifier to DS 846R, 2/ REF01/140 |Approved for immediate |DLA: Per email 10/26/09, ADC 212 is |
|Revise DS 846R, Location Reconciliation |to accommodate the functionality of MILSTRAP |implementation |implemented in EBS. |
|Request to Accommodate MILSTRAP DZH |Document Identifier (DI) Code DZH, record | | |
|Consecutive Transaction Number |position (rp) 60-66, ‘consecutive transaction |Request that within 45 | |
|(Supply/MILSTRAP) (Staffed as PDC 311) |number’. |days from the date of | |
|8/06/08 | |memorandum, DLA provide | |
|Johnson |2. Administrative update to identify that a |an EBS implementation | |
| |‘document number’ is a DLMS enhancement for |date for ADC 212. | |
| |location reconciliation requests and therefore | | |
| |requires a PDC to develop associated business | | |
| |rules for use. | | |
|ADC 213 |This change modifies the DS 940R to |Approved for |All changes to the DLMS documentation are |
|Admin Revision to DS 940R, Disposal Shipment |specifically identify the ICP/IMM to receive |implementation within 30|administrative to ensure that the published |
|Confirmation Inquiry, and Associated |the disposal shipment confirmation |days (11/18/06) |manual conforms to existing business rules. |
|Procedures (Supply) |inquiry/follow-up (equivalent to the MILSTRIP | | |
|10/18/06 |DIC AFX/AFZ which directs routing to the DoDAAC| | |
|Hilert |reflected in the document number of the | | |
| |receipt). In addition, this change updates, | | |
| |clarifies, and corrects DLMS procedures | | |
| |applicable to this process to reflect | | |
| |procedures prescribed by MILSTRIP. | | |
|ADC 214 |This change was staffed by referenced PDC 232. |Immediately |DLA: BSM and DSS will not implement any |
|Revision to DS 945A Material Release Advice |The change is approved to support the medical | |earlier than FY08. |
|and 947I Inventory Adjustment to Add |and industrial kitting community requirements: | | |
|Assemblage Identification Number, BDN and |(1) DS 945A-DLA requested revision of DLMS 945A| | |
|Admin Updates (Staffed as PDC 232) |transaction to add the BDN and AIN to identify | | |
|10/12/06 |kitting build orders. (2) DS 947I-DLA requested| | |
|Johnson |revision of DLMS 947I | | |
| |transactions to add the BDN and AIN to identify| | |
| |kitting build orders. | | |
|ADC 215 |This change documents a current Army-unique |Approved for |Published in DLMS Manual Vol II, Change 4 & |
|Material Receipt Status (Material Returns |capability within MILSTRIP DI Code FTZ, ICP/IMM|implementation within 30|MILSTRIP Reissue, Oct 2007 |
|Program (MRP)) Credit Reversal Amount |Material Receipt Status (Material Returns |days (11/18/06) | |
|(Supply/Finance) |Program) transaction, and perpetuates this | | |
|(Staffed by PDC 202) |capability into the DLMS. In addition to the | | |
|10/18/06 |current MILSTRIP purpose to notify customers of| | |
|Hilert |the amount of pending credit, it is Army | | |
| |practice to also use this transaction to | | |
| |identify the amount of credit reversals, when | | |
| |applicable, after receipt and inspection. | | |
|ADC 216 |This change supports CAV requirements for the |Immediately | |
|Revise DS 527R Receipt in Support of CAV and |DS 527R Receipt. It provides clarification of | | |
|Admin Change for AMMA |specific DS 527R CAV receipt data; the addition| | |
|(Supply) (Staffed by PDC 211) |of additional data required by CAV; and | | |
|11/07/06 |corrected CAV mapping for certain data. This | | |
|Johnson |change also | | |
| |incorporates DLMS expanded field length | | |
| |requirements for unit price identified by PDC | | |
| |222, Communication of Unit Price and Total | | |
| |Price under DLMS | | |
|ADC 217 |This change identifies new passive RFID |2/15/07 |Discrepancy Codes implemented at DAAS, DSS, |
|Passive Radio Frequency Identification (RFID) |discrepancy codes be added to the current | |EBS. |
|Discrepancy Codes (Supply/SDR) |applicable discrepancy code list under the | | |
|(Staffed by PDC 230A) |Packaging/Marking section (P300 series) for | | |
|1/09/07 |SDRs. The new codes will be used to identify | | |
|Hilert |discrepant, missing RFID marking/labeling on | | |
| |material, and to identify reader | | |
| |problems/issues which interfere with RFID | | |
| |processing by DOD receiving organizations. | | |
|ADC 218 |DS 527R, as revised by referenced PDC 211, to |Immediately | |
|Revise DS 527R and MILSTRAP Receipt |provide for DSS entry of the OCN in receipt | | |
|Transactions to Document Use of Distribution |transactions regardless of materiel owner, to | | |
|Standard System Operations Control Number and |support current use of OCN by Army, Navy, and | | |
|Additional Z4/Z6 Requirements |Mapping. DLMS 527R documentation currently | | |
|(Supply/MILSTRAP) |limits DSS use of the operations control number| | |
|(Staffed by PDC 233) |to DLA-owned materiel. | | |
|11/14/06 | | | |
|Johnson | | | |
|ADC 219 |This change establishes data requirements for |Immediately | |
|RFID Visibility Transactions |registering passive RFID readers at DAAS for | | |
|(Supply/Transportation) |the purpose of identifying the location of the | | |
|(staffed by PDC 236) |reader so that subsequent tag reads can be | | |
|12/7/06 |associated with the physical location of the | | |
|Daverede |read. This change also establishes data | | |
| |requirements for sending scanned tag read | | |
| |identification and reader identification to | | |
| |DAAS via middleware (e.g., Savi Site Manager, | | |
| |Globe Ranger, etc.). | | |
|ADC 220 |The purpose of this change is to support the |Approved for immediate | |
|In Two Parts, Part I: Revise Definitions for |changing environment for maintaining visibility|implementation | |
|Small Arms to Address Light Weapons, and Part |and reporting of small arms and light weapons | | |
|II: Visibility and Traceability of Captured, |(SA/LW) serial number data within DOD. | | |
|Confiscated or Abandoned Enemy Small Arms and | | | |
|Light Weapons (Staffed by PDC 134A) | | | |
|ADC 221 |This change expands the field size for the unit|Approved for phased and |Published in MILSTRIP Reissue, Oct 2007 |
|DLMS Enhancement for Communication of Unit |price and total dollar value on the Issue |staggered implementation| |
|Price and Total Price |Release/Receipt Document (IRRD) (DD Form |beginning no sooner than| |
|(Supply/MILSTRIP) |1348-1A). This change establishes a |6 months from | |
|(Staffed as PDC 222) |corresponding field size for the unit price in |publication. | |
|2/1/07 |the DLMS transactions. | | |
|(Corrected Copy 2/8/07) | | | |
|Hilert | | | |
|ADC 222 |This change modifies and adds |2/15/07 |Implemented for WebSDR interface systems. |
|Discrepancy Disposition/Status (Reply) Code |Disposition/Status Codes available for use in | | |
|Revisions |SDR replies. Includes new codes to indicate | | |
|(Supply/SDR) |prior response is superseded and to notify | | |
|(Staffed by PDC 231A) |customer that the SDR was rejected due to | | |
|1/09/06 |missing/invalid wrong item information. | | |
|Hilert | | | |
|ADC 223 | This change specifically requests |Approved for phased and |DLA: EBS implementation date is 11/12/2009 |
|DLMS Shipment Status Enhancements: Secondary |implementation of enhancements identified |staggered | |
|Transportation Number, Initial Shipping |during the development of the DLMS for a |implementation. DAASC | |
|Activity, Carrier Identification, and Port of |secondary transportation number and |changes to accommodate | |
|Embarkation (POE) |identification of the initial shipping |transition will be | |
|(Supply) (Staffed by PDC 224) |activity. It provides clarification on how |effective within 6 | |
|3/19/07 |DLMS handles identification of the Port of |months of publication. | |
|Hilert |Embarkation (POE) | | |
|ADC 224 |This change incorporates multiple revisions to |2/21/07 |Published in MILSTRIP Reissue, Oct 2007 |
|Revised Procedures for Logistics |procedures for maintaining accountability | | |
|Accountability During |during maintenance. | | |
|Maintenance(Supply/MILSTRIP)(Staffed by PDC | | | |
|208) | | | |
|2/21/07 | | | |
|Hilert | | | |
|ADC 225, |This change establishes procedures for |Approved for |Implemented IAW ADC 225B |
|DOD WebSDR Requirement for Information |WebSDR/DAAS creation/ transmission of an |implementation. DAAS | |
|Copy(Supply) |information copy of an SDR in response to an |implementation on or | |
|(Staffed by PDC 240) |SDR reply reject code sent to DAAS. The reject|before 7/01/07 | |
|1/22/07 |condition applies when the DD is the action | | |
|Hilert |activity, and the SoS, e.g., DLA cannot process| | |
| |the DD reply due to lack of a record | | |
| |establishing the basic report. | | |
|ADC 225A |The first addendum to the approved change added| |Implemented IAW ADC 225B |
|Approved Addendum to ADC 225A, DOD WebSDR |procedures which require DAAS/WebSDR to verify | | |
|Requirement for Information Copy (Supply/SDR) |whether an information copy had been provided | | |
|(Staffed as PDC 225A) |to EBS for applicable report types. | | |
|7/02/07 | | | |
|Hilert | | | |
|ADC 225B, |This second addendum is provided to modify |8/2007 |Implemented |
|Second Addendum to ADC 225B, DOD WebSDR |reply codes and clarify procedures used when |(DLA EBS, DAASC) | |
|Requirement for Information Copy New Reply |requesting an information copy via reject reply| | |
|Codes |code. | | |
|(Supply/SDR) | | | |
|8/09/07 | | | |
|Hilert | | | |
|ADC 226 |This change establishes a new edit for DODAACs |3/1/07 |Implemented at DAAS |
|Revision of MILSTRIP, MILSBILLS and DLMS to |by Authority Code in order to restrict | |Published in MILSTRIP Reissue, Oct 2007 |
|add DODAAC Authority Code edits |requisitioning, shipment and billing by DODAAC.| |Published in DoD 4000.25-M Volume 6 Mar 2008 |
|(Supply/Finance/MILSTRIP /MILSBILLS/DODAAD) |This revises DLMS, MILSTRIP and MILSBILLS to | | |
|(Staffed as PDC 235) |identify DODAAC authority and reject | | |
|3/1/07 |requisitions or bills, as appropriate. | | |
|Hammond | | | |
|ADC 228 |This change establishes procedures that allow |Approved for phased and |DLA reports on 12/28/07 ADC 228 has been |
|New Status Code for Free Issue Post-Post |the source of supply to modify post-post |staggered implementation|completed |
|Orders (Supply/MILSTRIP/Finance) (Staffed as |non-reimbursable requisitions so that they are |beginning no sooner than|Published in MILSTRIP Reissue, Oct 2007 |
|PDC 237) |processed as reimbursable with concurrent |September 2007 | |
|4/04/07 |generation of supply status notification. | | |
|Hilert | | | |
|ADC 229, Material Processing Center (MPC) |This change establishes procedures for |DSS phased |DAAS/DSS implemented |
|Material Receipt and Delivery Supply Status |preparation of supply status transactions (DLMS|implementation beginning|Published in MILSTRIP Reissue, Oct 2007 |
|(Supply) (Staffed as PDC 254) |870S, equivalent of MILSTRIP Document |3/26/07 |To be published in DLMS Manual Vol II, Change |
|3/06/07 |Identifier AE8) by the Distribution Standard | |5 |
|Hilert |System (DSS) upon MPC receipt or delivery of | | |
| |material. This supply status provides | | |
| |notification to the Navy ship/customer and | | |
| |other status recipients for tracking material | | |
| |and for performance metrics. This change | | |
| |adapts a currently-used Navy-unique process for| | |
| |inter-Navy-DDC use under DLMS. | | |
|ADC 230 |Administrative updates to DS 846R to cite ANSI |Approved for | |
|Admin updates to DS 846R, Location |qualifiers DLMSO requested for this DS that |implementation | |
|Reconciliation Request (Supply) |have been approved for version 5030, and to | | |
|3/15/07 |correct erroneous DLMS notes | | |
|Johnson | | | |
|ADC 231, |This change updates Fed IC 4010 857, Shipment |Approved for | |
|Inclusion of Data Supporting WAWF Transaction |and Billing Notice, for use in vendor |implementation | |
|Exchange for IUID, Zero Lot Shipments, and |communication with (WAWF-RA). It also updates | | |
|Performance Notification for Services |the Federal IC 856 Shipment Notice Manifest, | | |
|(Contract Administration/Supply) |used by vendors, and the corresponding DS 856 | | |
|(Staffed as PDC 200) |ASN, used internal to DOD. | | |
|3/20/07 | | | |
|Hilert | | | |
|ADC 232 |Admin update to revise the MILSTRAP AP 2.5 (and| | |
|Admin Update to MILSTRAP and DLMS to Clarify |corresponding DLMS Data Dictionary) for Supply | | |
|that Supply Condition Code Q is Authorized for|Condition Codes to add SCC Q to the list of | | |
|Turn-in to Defense Reutilization and Marketing|SCCs that can be sent to the DRMO, in support | | |
|(Supply) |of current procedures. | | |
|3/23/07 | | | |
|Johnson | | | |
|ADC 233, |The purpose of this change is to map the Navy’s|Approved for |Navy indicates requirement as defined in ADC |
|New DLMS Information Exchange for Tracking |current unique transactions to a new DLMS |implementation no sooner|233 is considered OBE. Alternative procedures|
|NRFI Carcass Return (Supply) (Intra-Navy/USMC)|transaction identified as DS 856C for use in |than 9/2008 |under development. |
| |the Navy procedures associated with carcass | | |
|(Staffed as PDC 206) |tracking of depot-level reparables (DLR). | | |
|4/05/07 | | | |
|Hilert | | | |
|ADC 234, |This change incorporates data elements in DLMS |Approved for | |
|Identification of Intra-Army Data Requirements|required to accurately process intra-Army data |implementation | |
|for DLMS 527R and 527D, and Admin Update to |for nonprocurement source receipts, dues-in, | | |
|Batch/Lot and UII Length (Supply)(Staffed by |and advance receipt information (ARI) (formerly| | |
|PDC 250) |prepositioned materiel receipt (PMR) under | | |
|4/09/07 |MILSTRAP). | | |
|Johnson | | | |
|ADC 235, |Revise DLMS 867I Issue transaction to add the |Approved for | |
|Revise DS 867I and MILSTRAP Issue Transactions|Navy issue on request code in support of an |implementation | |
|to Support Navy Issue On Request Code and |existing Navy requirement. Navy uses the issue| | |
|Admin DS 867I Updates (Supply) (Staffed by PDC|on request code when interfacing with DLA DSS. | | |
|242) |Revise MILSTRAP to document existing Navy use | | |
|4/17/07 |of the issue on request code in DI Code D7_ | | |
|Johnson |issue transaction | | |
|ADC 236, |This ADC revises the property accountability | Approved for |Published in DLMS Manual Vol II, Change 4 |
|Revise the Property Accountability Accuracy |records accuracy level currently published in |implementation |MILSTRAP reissue scheduled for calendar year |
|Goal for Controlled Inventory Items Not |DOD 4000.25-M, and DOD 4000.25-2-M, from 85 | |2008 |
|Subject to Annual Complete Physical Inventory |percent to 95 percent, for controlled inventory| | |
|(Supply) |items that are not subject to an annual | | |
|(Staffed as PDC 251) |complete physical inventory. | | |
|4/25/07 | | | |
|Johnson | | | |
|ADC 237, |This change revises MILSTRAP (reference 3.a.) |Approved for |Published in DLMS Manual Vol II, Change 4 |
|Rename Location Audit Program to Record |and DLMS (reference 3.b.), to rename the |implementation |MILSTRAP reissue scheduled for calendar year |
|Reconciliation Program |Location Audit Program to the Record | |2008 |
|(Supply) (Staffed as PDC 253) |Reconciliation Program. DLMSO will also need | | |
|4/25/07 |to request a corresponding change to DD Form | | |
|Johnson |2338-1 ICE Report Ammunition) and DD Form | | |
| |2238-2 (ICE Report General Supplies), to revise| | |
| |the Part I, section 3 title from ‘Location | | |
| |Audit Program’ to ‘Record Reconciliation | | |
| |Program’ | | |
|ADC 238, |This change updates DS 888A, Small Arms Data |Approved for | |
|Update of DS 888A Small Arms Data Change |Change, to stipulate that the DODSASP procedure|implementation | |
|(Supply) (Staffed as PDC 262) |for changing a serial number does not extend to| | |
|4/27/07 |the IUI,D UII, and to make various admin | | |
|Johnson |updates to DS 888A necessary to correct or | | |
| |clarify information. | | |
|ADC 239, |This change updates DLMS Unit of Material | |Conversion Guide updated |
|DLMS Unit of Material Measure (Unit of Issue |Measure Conversion Guide to add Units of | | |
|/Purchase Unit) Conversion Guide Update |Measure values that are valid under ASC X12 | | |
|(Supply) |transactions with their corresponding DOD Unit | | |
|5/14/07 |of Measure values. | | |
|Hilert | | | |
|ADC 239A, |This change reflects a “wall to wall” review |Approved for immediate |Conversion Guide updated |
|DLMS Unit of Material Measure (Unit of Issue |and update of the DLMS Unit of Material Measure|implementation | |
|/Purchase Unit) Conversion Guide Update |(Unit of Issue/Purchase Unit) Conversion Guide.| | |
|(Supply/Distribution) |This change supplements ADC 239 which added | | |
|7/02/07 |four new Unit of Measure values. | | |
|Hilert | | | |
|ADC 240 |This approved DLMS change defines a requirement|Phase I-Feb 2008 | |
|DLMS Transactions for Stock Screening |for new DLMS transactions to be used by supply | | |
|Request/Reply and Web-Enhanced Stock Screening|chain owners/managers to request storage sites | | |
|Requests and SQCR) |to perform stock screening actions and allow | | |
|(Supply/Stock Readiness) |storage sites to reply to the owners/managers | | |
|(Staffed as PDC 248) |electronically. | | |
|6/13/07 | | | |
|Hilert | | | |
|ADC 241, |This change updates DS 856R, Shipment Status |Approved for | |
|IUID and RFID in DS 856R, Shipment Status |Material Returns, to carry IUID information and|implementation on a | |
|Material Returns (Supply) |passive RFID tag information. This ADC is a |phased and staggered | |
|(Staffed as PDC 255) |planning tool for establishing techniques for |basis during the | |
|11/06/07 |accommodating IUID and RFID tag data within |calendar 2008 | |
|Hilert |transactional exchanges under the DLMS to | | |
| |support business process improvements | | |
|ADC 242, |This change establishes a requirement to |Approved implementation |DSS Implemented |
|Shipment Status DS 856S: Priority Designator |provide additional data elements in the DLMS |beginning no earlier | |
|(PD), Transportation Priority (TP), Project |856S. All shipment status under DLMS shall |than 5/21/07 with phased|DLA EBS has completed/released ADC 242 in EBS |
|Code, Special Requirements Code (Supply) |include the following data elements when |and staggered |(Release 11.1B) on 11/26/10 |
|(Staffed as PDC 263) |applicable and available. These data elements |implementation for full | |
|5/21/07 |shall be perpetuated from the requisition to |DLMS compliance | |
|Hilert |the shipment status by all SoS /ICPs/IMMs. The| | |
| |DSS will perpetuate these data elements from | | |
| |the material release order. | | |
| |- Project Cod e- Special Requirements Code | | |
| |(MILS RDD coded entries, e.g. 999, N for Not | | |
| |Mission Capable, etc.) - Priority Designator | | |
|ADC 242A, |Shipment status may include the unit price |Approved for phased and |DSS Implemented |
|Approved Addendum to DLMS ADC 242A, Inclusion |(required for DSS-generated shipment status; |staggered implementation| |
|of Unit Price on DLMS Shipment Status (DS |otherwise optional). |beginning no sooner than|DLA EBS has completed/released ADC 242A in |
|856S) (Supply) | |2/2008 |EBS (Release 11.1B) on 11/26/10 |
|11/07/07 | | | |
|Hilert | | | |
|ADC 242B, |This change allows for the inclusion of |August 1, 2009 |Implemented |
|Inclusion of Additional Customers under |additional customers identified by the DDC, | | |
|Material Processing Center (MPC) Shipment |regardless of Service/Agency, to receive a copy| | |
|Status Distribution Rules (Supply) |of the DLMS 856S, Shipment Status, from DAAS to| | |
|7/08/09 |support DSS MPC processing. | | |
|Hilert | | | |
|ADC 243, |This change revises the DLMS to include |Authorized immediate |DAASC changes have been implemented |
|Identification of SSF Requisitioning Actions |Army-unique data elements required to |Army implementation to |Published in MILSTRIP Reissue, Oct 2007 |
|and EAC Authorization (Supply/MILSTRIP) |accurately process requisitions and related |support Army LMP 8/2007 | |
|(Staffed as PDC 243) |transactions in the Army wholesale system that |release | |
|5/10/07 |originate from the Army retail system for SSF | | |
|Hilert |activities. | | |
|ADC 244, |Provide a definition for Reconciliation, Small |Approved 5/11/07 | |
|Definition for Reconciliation, Small Arms and |Arms and Light Weapons, based upon the intent | | |
|Light Weapons and Clarification of Procedure |of the Small Arms Reconciliation Request | | |
|(Supply) (Staffed as PDC 244) |transactions (MILSTRAP DI Code DSR and DS 140A | | |
|5/11/07 |with 1/BGN07/20 Transaction Type Code W5 - | | |
|Johnson |Weapons Control Report Reconciliation). | | |
|ADC 245, |This change request defines new routing and | |See below |
|Notification for Distribution Depot (DD) |processing changes for SDRs prepared by DDs to | | |
|Product Quality Deficiency Report (PQDR) |notify USAF managers of the arrival of | | |
|Exhibit Receipt (Supply/SDR) |USAF-owned PQDR exhibits and is designed to | | |
|(Staffed as PDC 247) |support expansion for other Services. Two new| | |
|6/08/07 |data elements are added to the SDR transaction | | |
|Hilert |to support the USAF requirement and | | |
| |pre-position cross-reference information to | | |
| |support exhibit tracking for other Services. | | |
|ADC 245A, |Update to the Approved Process Step 5 is |Routing change available|See below |
|Notification for DD PQDR Exhibit Receipt |provided to further clarify the procedures. |upon AF approval 10/2007| |
|(Supply/SDR) | | | |
|(Staffed as PDC 247) | |DSS SDR format update to| |
|7/13/07 | |include cross-reference | |
|Hilert | |numbers is targeted for | |
| | |implementation mid-year | |
| | |2008 | |
|ADC 245B, |This document re-publishes ADC 245A with |Effective 6/26/08 by |Partially implemented - No date is available |
|Approved Addendum Notification for |updates to remove the requirement for Accession|request of the USAF |for the data element update in the SDR |
|Distribution Depot (DD) PQDR Exhibit Receipt |Number and instead use the PQDR Report Control | |transaction for implementation by DSS. |
|(Supply/SDR) |Number. | | |
|7/03/08 | | | |
|(Staffed as PDC 245B) | | | |
|Hilert | | | |
|ADC 246, |When sending MILSTRAP Document Identifier (DI) |Approved for |DLA reports on 10/11/07 that ADC 246 is in |
|Revise DS 527R and MILSTRAP Receipt |Code D6_ receipt to the Navy, DAASC will send |implementation |production in DSS and DDC is awaiting feedback|
|Transactions to Document Use of Navy MTIS |MTIS indicator in position 7 of the D6_ to the | |from Navy |
|Indicator (Supply/MILSTRAP) |Navy if it contains an ‘S’. This change | | |
|(Staffed as PDC 249) |incorporates the MTIS indicator in DLMS 527R | |DLA reports on 12/28/07 ADC 246 has been |
|5/22/07 |receipt. | |completed |
|Johnson | | | |
|ADC 247, |Revise DS 527R, and corresponding DLMS XML and |Approved for |DLA: EBS implementation date is 11/12/2009 |
|Revise DS 527R to Authorize Use of TCN with |DOD XML constructs, to authorize use of the TCN|implementation | |
|MRA and Receipt (Supply) |in the MRA transaction and in the receipt | | |
|(Staffed as PDC 246) |transaction. USAF identified requirement for | | |
|7/03/07 |inclusion of TCN in the MRA. DLMSO supports | | |
|Johnson |that requirement and identified additional | | |
| |requirement to include TCN in receipt | | |
| |transactions when available. | | |
|ADC 248 |This change revises DS 824R, Reject Advice, to |Approved for | |
|Admin Update to DS 824R, Reject Advice |acknowledge qualifiers approved in version |implementation | |
|(Contract Administration/Supply) |5040, or version 5050, for the 2/REF/020 | | |
|7/17/07 |segment which equate to beginning segment codes| | |
|Johnson |of transactions being rejected by DS 824R. | | |
| |These qualifiers address beginning segment | | |
| |information which is used by some DLMS | | |
| |transactions but that is not covered by the | | |
| |824R 2/OTI/010 OTI segment. | | |
|ADC 249 |DLMSO administrative updates include | | |
|Admin Updates to DS 140A, 846A and 846F to |documentation of UID policy limitations on the | | |
|Include Updates for Batch/Lot and UII Field |maximum field size for UII and the batch/lot | | |
|Length Limitations (Supply) |number. | | |
|7/18/07 | | | |
|Johnson | | | |
|ADC 250, |Incorporate DS 846I changes to support Army | |Army: Implemented 01/08. |
|Revise DS 846I and MILSTRAP DZA Asset Status |requirements for Asset Status Report and the | |DLA-DDKS: Implemented 01/08. |
|Transactions to Support Army Distribution |corresponding MILSTRAP DI Code DZA Asset Status| | |
|Operations, and Revise DS 846I for Use of UTC |transaction, to accommodate recording the on | | |
|and for Admin Updates (Supply) (Staffed by |hand quantity of assets being held in the DLA | | |
|PDC 270) |ownership at DDKS, Kuwait, to support an Army | | |
|7/30/07 |requirement. | | |
|Johnson | | | |
|ADC 252, |Revise DS 947I guidance to provide for use of |Approved for | |
|Revise DS 947I Inventory Adjustment to Provide|the UI in DS 947I inventory adjustment |implementation | |
|for Use of Unit of Issue and Various Admin |transactions. Also updates to cite UID policy | | |
|Updates (Supply) |field size limitations for unique item | | |
|(Staffed as PDC 268) |identifier, batch/lot, and serial number. | | |
|8/02/07 | | | |
|Johnson | | | |
|ADC 253, |This change specifically defines secondary |Approved as authorized |DLA: EBS implementation date is 11/12/2009 |
|DLMS Material Release Confirmation: Secondary |transportation numbers and carrier |DLMS enhancement | |
|Transportation Number, Carrier Identification,|identification. It also provides clarification| |DSS has implemented 253. |
|and POE (Supply) (Staffed as PDC 265) |on how DLMS handles identification of the POE | | |
|8/27/07 |(for air or water) or the CCP which are mapped | | |
|Hilert |to the same record positions in the MILS. | | |
|ADC 254 |This change incorporates the inclusion of the |Approved with an | |
|DLMS Mapping for Army Material Release Order |Army-unique DI Code B99 (Offline MRO Image) to |estimated implementation|Implemented |
|Shipment Status, DI Code B99, and Admin |the DLMS mappings maintained by DAASC. All |date of 8/2008 | |
|Updates for DS Mapping of the UII (Supply) |data elements, with the exception of the DI | | |
|(Staffed as PDC 267) |Code, are identical to the already mapped MILS | | |
|10/04/07 |A5 transactions. | | |
|Hilert | | | |
|ADC 255, |This change modifies procedures for the |Approved for | |
|Storage Activity Accountability to Service |Causative History Summary whereby the storage |implementation | |
|Materiel Owners |activity sends a quarterly summary of causative| | |
|(Supply/Physical Therapy) |research results by the error classification | | |
|(Staffed as PDC 241A) |code for each NIIN to the Inventory Owners or | | |
|11/20/07 |ILCO for all adjustments of extended dollar | | |
|Johnson |value greater than $16K. | | |
|ADC 256 |This change approves two new edits: Follow-up |Approved for phased |Deferred pending higher priorities |
|WebSDR/SDR Transaction Edits: Forwarding and |transactions will be edited to ensure that an |implementation by 6/2008| |
|Follow-up Timeframes (Supply/SDR) |appropriate time has elapsed before follow-ups | | |
|(Staffed as PDC 226) |may be submitted. SDR replies requesting | | |
|12/19/07 |forwarding of the SDR to a new action activity | | |
|Hilert |(reply code 504), may not be used to forward | | |
| |transactions which lack data content necessary | | |
| |to establish a basic SDR report. Forwarding | | |
| |for historical transactions will be authorized.| | |
|ADC 257, |This change documents the preparation of the |Approved for |Implemented |
|DLMS Shipment Status Generated by the CCP |DLMS Shipment Status by the CCP using the DSS |implementation | |
|(Supply) (Staffed as PDC 275) |in order to provide passive RFID information to| | |
|11/15/07 |the customer. | | |
|Hilert | | | |
|ADC 258, |This change is provided to document procedures |Approved for | |
|DLMS Enhancement - Addition of Project Code |for the use of a proposed DLMS enhancement to |implementation | |
|field to DRO (Supply) (Staffed as PDC 223) |include the Project Code data element in the | | |
|11/26/07 |format for the DRO. | | |
|Hilert | | | |
|ADC 259, |Revise DLMS 867I transaction to add a “Reason |Approved for immediate | |
|Revise DS 867I and MILSTRAP Issue Transactions|for Reversal Code” in support of an existing |implementation by DSS | |
|to Support Navy Issue Reversal Code (Supply) |Navy legacy system requirement for an issue |and DAASC | |
|(Staffed as PDC 264) |reversal code Revise DLMS 867I Issue | | |
|11/09/07 |transaction to add a “Reason for Reversal Code”| | |
|Johnson |in support of an existing Navy legacy system | | |
| |requirement for an issue reversal code | | |
|ADC 260, Revise DLMS and MILSTRAP to Support |This requirement applies only for intra-Army |Approved for immediate | |
|Intra-Army Logistics Reassignment (LR) |logistics reassignment, i.e., LR from an Army |implementation | |
|Requirement, DS 846D, and DS 846S LR |LIM to an Army GIM. Precedence for | | |
|Transactions (Supply/MILSTRAP) |attributing assets to the two or, in the case | | |
|(Staffed as PDC 273) |of Army intra-Army LR, three quantity fields | | |
|12/03/07 |being identified in MILSTRAP DZC/DZD, and DLMS | | |
|Johnson |846S | | |
|ADC 261 |Army has identified a requirement for using the|Approved for | |
|Migrate Navy Serial Number and Lot Number |NAVSUP P-724 BG1/BG2 data in DLMS under the |implementation | |
|Transactions (NAVSUP P-724 BG1/BG2) to DLMS |Army (LMP to support an existing interface | | |
|527R Receipt, 867I Issue, and 947I Inventory |between Army and the Naval Operational | | |
|Adjustment (Supply) |Logistics Support Center (NOLSC) Ordnance | | |
|(Staffed by PDC 261) |Information Systems (OIS). | | |
|01/07/08 | | | |
|Johnson | | | |
|ADC 262 |Revise MILSTRIP/DLMS procedures to include |Approved for immediate | |
|Deleted DoDAAC, Cited on Open Orders |instructions on cancellation of orders, citing |implementation | |
|(Supply/MILSTRIP) (Staffed as PDC 277) |a ship-to or bill-to DoDAAC that has been | | |
|12/19/07 |deleted, as identified in the (DoDAAD. | | |
|Hilert | | | |
|ADC 263 |The SBSS transmits the unit price on all |Approved for |DAASC action complete as of 12/14/2007 |
|Inclusion of Unit Price in Requisition |requisition modifiers, requisition cancellation|implementation | |
|Modification and Cancellation |requests, and follow-ups on cancellation | | |
|(MILSTRIP/Supply) |requests. Change opens the DLMS unit price | | |
|(Staffed as PDC 278) |field to carry this unit price, and establish | | |
|12/17/07 |business rules for DAASC conversion between | | |
|Hilert |DLMS and MILS for intra-AF transactions. | | |
|ADC 264 |Under the AF Jump Start program, part-numbered |On or before February |AF Jump Start to be implemented May 08 |
|DLMS Enhancement for Part-Numbered Requisition|requisitions (MILSTRIP A02 and A0B), will be |15, 2008 | |
|Format and USAF Unique Rules for Descriptive |produced in DLMS XML using the DLMS 511R | | |
|Information including T.O. Number |format, and will need to perpetuate applicable | | |
|(Supply/MILSTRIP) |descriptive information including T.O. number, | | |
|(Staffed as PDC 282) |end item description, commodity name, etc. | | |
|1/30/08 | | | |
|Hilert | | | |
|ADC 265 |This DLMS change is in support of the AF Jump |Approved for |DAAS conversion implemented. |
|USAF Reason for Requisition Cancellation |Start program. The intent is to include an |implementation DAASC |AF Jump Start to be implemented May 08 |
|(Excess Cause) Code (Supply/MILSTRIP) |existing AF unique data element used on the |conversion support will | |
|(Staffed as PDC 281) |requisition cancellation, to identify the |be available by | |
|01/10/08 |reason for the cancellation. |1/31/2008 | |
|Hilert | | | |
|ADC 266 |This DLMS change is in support of an AF Jump |Approved for |DAASC complete (12/18/2007) |
|USAF Lateral Requisition Routing Identifiers |Start program. This change supports |implementation |AF Jump Start to be implemented May 08 |
|(Supply/MILSTRIP) |identification of two additional routing | | |
|(Staffed as PDC 283) |identifiers in lateral requisitions to identify| | |
|12/17/07 |the DoD source of supply (as different form the| | |
|Hilert |lateral source of supply), and the | | |
| |requisitioner. | | |
|ADC 267 |Army process for Direct Support/Reparable |Approved for intra-Army |Temporary deviation from standard DOD process |
|Interim Change for DLMS 527R Receipt to |Exchange (DS/RX) includes the decapitalization |implementation |to accommodate a legacy Army requirement. |
|Support Intra-Army Direct Support/ Reparable |of assets Operations and Maintenance Army (OMA)| |Change will be rescinded when Army Exchange |
|Exchange Decapitalization Transaction |funds from the Tactical level to Army Working | |Pricing is implemented (estimated for April |
|(Supply/MILSTRAP) |Capital Funds (AWCF) for National level. | |2009) |
|1/30/08 | | | |
|Johnson | | | |
|ADC 268 |This change documents the inclusion of the PQDR|Approved for immediate | |
|Inclusion of PQDR Report Control Number (RCN) |RCN in |implementation by DAASC | |
|on Security Assistance (SA) SDR |the SDR reply transaction format. This data |and PDREP in early | |
|Quality-Related Reply (DS 842A/R) (Supply/SDR)|element was previously added to the SDR report |Feb2008 | |
|1/31/08 |format under reference 3b. | | |
|Hilert | | | |
|ADC 270 |Administrative update to revise DS 846P, |Approved for | |
|Administrative Revision to DS 846P to Clarify |Physical Inventory Request. Transaction to |implementation | |
|Date Qualifiers in Transaction History |clarify use of the transaction history request | | |
|Requests (Supply/MILSTRAP) |report start and end dates | | |
|2/21/08 | | | |
|Johnson | | | |
|ADC 271 |DLA requires visibility of the BDN in DS 867I |Approved for | |
|Revisions to DS 867I Issue to Add Build |since DLA owns the material at the TEWLS/AMMA |implementation | |
|Directive Number (BDN) to Support the TEWLS, |site until the items are issued at the retail | | |
|and DS 867I Administrative Updates (Supply) |level. This change supports the medical and | | |
|(Staffed by PDC 298) |industrial kitting community requirements for | | |
|2/27/08 |the BDN in order to identify kitting build | | |
|Johnson |orders. | | |
|ADC 272 |Incorporate changes to DLMS 527R to support the|Approved for | |
|Revise DLMS 527R and MILSTRAP Receipt |existing Intra-Army Single Stock Fund (SSF) |implementation | |
|Transactions to Add Discrepancy Indicator |Discrepancy Receipt Process. | | |
|Codes for use with Intra-Army SSF Discrepancy | | | |
|Receipt Process (Supply/MILSTRAP) | | | |
|(Staffed as PDC 292) | | | |
|3/04/08 | | | |
|Johnson | | | |
|ADC 273, |Administrative updates to provide information |Approved | |
|Administrative Update to DS 947I, Inventory |useful in a mixed DLSS-DLMS environment, | | |
|Adjustment (Supply/MILSTRAP) |showing how the DS 947I W19 Segment codes | | |
|3/25/08 |correlate to the MILSTRAP inventory adjustment | | |
|Johnson |DI codes. | | |
|ADC 274, |EP is a business process improvement mandated |See below |The Army anticipated implementation date is |
|DLMS and DLSS Changes to Support Army Exchange|by the OSD C, to mitigate the financial | |May 1, 2009. The Defense Automatic Addressing|
|Pricing |problems the Army has experienced with granting| |System conversion capability will support this|
|(Supply/Finance/MILSTRIP/ |excess credit through its current supply | |date. |
|MILSTRAP/MILSBILLS) (Staffed as PDC 269) |practices, and allows credit for reparable | | |
|4/01/08 |items to provide incentive for organizations to| | |
|Hilert |turn-in unserviceable component parts, that AMC| | |
| |repairs and returns to inventory to support | | |
| |unit readiness needs | | |
|ADC 274A, |Changes included in this Addendum is to include|Approved |The Army anticipated implementation date is |
|Approved Addendum to ADC 274A, DLMS and DLSS |the additional Army Service Designators (“A” | |May 1, 2009 |
|Change to Support Army Exchange Pricing to |and “C”) to the DAASC Mappings for 511M, 511R, | | |
|Correct DLMS 870M Routing for Delta Bill |527R, 810L, 856S, 869F, 870M, 870S, and 940R. | | |
|Trigger Transactions and Addition of Army |The implementation of the Service Designator | | |
|Service Designators to DAASC Mappings |change in the DAASC Mappings is secondary to | | |
|(Supply/MILSTRIP) |the DLSS FTZ/DLMS 870M routing changes. The | | |
|10/16/08 |routing changes are of primary concern to the | | |
|Hilert |Army as it is affecting the testing of the end | | |
| |to end Exchange Pricing process. | | |
|ADC 275, Administrative Changes to Eliminate |This change modifies the 812L and 812R to |Approved for | |
|Override Procedures for DS 812L, Logistics |clearly identify as an enhancement (not |implementation | |
|Bill Adjustment Request Reply and 812R, |approved for current use) the use of Table 1 | | |
|Logistics Bill Adjustment Request (Finance) |Code Source Information in cases where the | | |
|(Staffed as PDC 300) |Agency code is applicable to all Table 2 | | |
|4/03/08 |iterations. This change also removes the use of| | |
|Hammond |override procedures for Code Source | | |
| |information, as override is no longer | | |
| |recognized as a recommended procedure. | | |
|ADC 276, |This change establishes capability to identify |This change is required | |
|Addition of Party to Receive Copy to Support |a “Party to Receive Copy” in a requisition, |for an upcoming DLA | |
|Requirements for TEWLS Requisitions. |modification, and follow-up, and subsequent |Enterprise Business | |
|(Supply) |transmission of a copy transaction to the |System release to | |
|(Staffed as PDC 296) |identified party by the DAAS. This allows |support TEWLS. The | |
|6/24/08 |visibility of the GSA/Non-DLA requisitions for |target date for | |
|Hilert |medical and industrial kitting component parts,|implementation is | |
| |when DLA is acquiring the parts, as the Medical|January 2009. | |
| |Executive Agent, in support of Army under the | | |
| |TEWLS/AMMA business model. | | |
|ADC 278 |This change established a distinct DS for DDE, |Approved for immediate |Per 10/30/09 email from DLA SPRC rep, SCR |
|Establish New DS 830D, Version 4030, for |rather than combining the DDE transaction with |implementation by the |entered under DLA EBS Planning process; ranked|
|Demand Data Exchange (DDE) Projected Supply |the DLMS 830R SPR transaction. A change |Services. Services |#106 which realistically is not on radar at |
|Plan, in Place of DS 830R, Version 4030, |incorporated into this ADC based on DLA comment|which implement DLMS for|this time, therefore, it is hard to provide |
|Special Program Requirements (SPR)/DDE |to PDC 297, is that the use of the term “DDE |DDE must do so using DS |even a ballpark time. Implementation would |
|Forecast (Supply) (Staffed as PDC 297) |Forecast” has been revised to “DDE Projected |830D. |likely be several years out, FY13+, unless |
|9/22/08 |Supply Plan”. | |Planning has reason to reprioritize. |
|Johnson | | | |
| | | |DAASC must convert between Service generated |
| | | |830D and DLA 830R until such time as DLA EBS |
| | | |implements ADC 278 830D. Accordingly, DLA |
| | | |must advise DLMSO when an implementation date |
| | | |is established. |
|ADC 279 |This change establishes procedures for GSA |Phased implementation is|DAAS portion of change implemented. GSA |
|Automated Downgrade for Priority Abuse and |compliance with MILSTRIP business rules for |authorized. |pending. |
|Reporting Procedures (Supply/MILSTRIP) |requisition priority validation for F/AD I | | |
|7/03/08 |activities on requisitions submitted directly | | |
|Hilert |to GSA for purchase of GSA-managed items This | | |
| |change removes the current PD 01 exclusion from| | |
| |automatic downgrading for selected requisitions| | |
| |which do not identify authorized DoDAACs, and | | |
| |are originated via internet using GSA | | |
| |Advantage/Global or DoD EMALL. | | |
|ADC 280 |This change to MILSBILLS will allow for better |Approved for | |
|Product Quality Deficiencies Report |tracking of credits for PQDRs, SDRs and TDRs. |implementation on 1/Feb/| |
|PQDR/SDR/Transportation Discrepancy Report | |2010 to allow all | |
|(TDR) Credit Tracking (Finance) (Staffed as | |systems to implement | |
|PDC 284) | |simultaneously | |
|8/18/08 | | | |
|Hammond | | | |
|ADC 281, |Administrative correction to include missing |Approved for immediate | |
|Administrative Revision to DS 517M, Material |qualifier that identifies nonstandard material.|implementation. | |
|Obligation Validation (MOV), to Include |This qualifier is necessary for conversion | | |
|Qualifier for Material Identification |between MILSTRIP and DLMS. | | |
|10/27/09 | | | |
|Hilert | | | |
|ADC 282, |This proposal identifies data content and |Implemented by DSS 8.2 |WebSDR implemented. |
|Consolidation and Containerization Points |process changes supporting generation of |Release July through | |
|(CCP)-Originated SDRs including Noncompliant |electronic DLMS SDRs by the CCP. This change |September 2008. |EBS implementation of incoming transactions |
|Wood Packaging Material (WPM) Procedures and |also identifies a new Shipment Hold code to be | |for Type W scheduled for Feb 2010. |
|Shipment Hold Code (Supply/SDR) (Staffed as |used internally by the CCP in conjunction with | | |
|PDC 295) |noncompliant WPM shipments. | |DSS implementation of incoming Type W |
|5/08/08 | | |scheduled for 2010. |
|Hilert | | | |
|ADC 282A |In association with this and the submitter |Implemented by DSS 8.2 |EBS implementation of incoming transactions |
|Addendum to ADC CCP-Originated SDRs including |process which is allows closure upon SDR |Release July through |for Type W scheduled for Feb 2010. |
|Noncompliant WPM Procedures with Cost |generation, there are new procedures for |September 2008. |DSS implementation of incoming Type W |
|Breakdown and New Procedures for Closing WPM |DAAS/WebSDR to post action activity replies to | |scheduled for 2010. |
|and Passive RFID SDRs (Supply/SDR) |history without forwarding to the SDR | | |
|(Staffed as PDC 282A) |submitter. | | |
|7/16/08 | | | |
|Hilert | | | |
|ADC 283, |This change revises the Federal IC and DS 846R,|Approved for | |
|Migrate Serial Number and Lot Number |Location Reconciliation Request, to incorporate|implementation. | |
|Transactions (NAVSUP P-724 BG1/BG2) to DLMS |data contained in Navy NAVSUP P-724 (reference | | |
|846R Location Reconciliation Request |3.a) Serial Number and Lot Number Reports | | |
|(Supply/MILSTRAP) |(requirement has only been identified for an | | |
|(Staffed as PDC 306) |existing Army and Navy interface). | | |
|5/12/08 | | | |
|Johnson | | | |
|ADC 284, |This change is to allow the inclusion of the |Implementation |See below. |
|Revisions to DSs to Add Shop Service Center |shop service center (SSC) identifier (also |is planned for | |
|(SSC) for BRAC IMSP (Supply) (Staffed as PDC |referred to as Shop Store Identifier) on DLMS |IMSP in July 2008. | |
|305) |standard transactions. | | |
|5/13/08 | | | |
|Hilert/Johnson | | | |
|ADC 284A, |This ADC replaces the original ADC 284 and |Approved for |Implemented |
|Revisions to DSs to Add Shop Service Center |provides updated format/notes to identify the |implementation. | |
|(SSC) for BRAC IMSP (Supply) |“type of code” used for identification of the |Initial implementation | |
|6/22/09 |SSC. |is planned for August | |
|Hilert/Johnson | |2009. | |
|ADC 285, |This revision updates the MILSTRIP/DLMS |Approved for | |
|Administrative Revision to MILSTRIP and DS |procedures, the DS 869C, and DAAS conversion |implementation | |
|869C, Requisition Cancellation, for Inclusion |mapping for MILSTRIP AC_/AK_ transactions. All| | |
|of Missing Passing Activity Identification |now permit inclusion of the party passing the | | |
|(Supply/MILSTRIP) |transaction in the cancellation and | | |
|6/10/08 |cancellation follow-up | | |
|Hilert | | | |
|ADC 286, |Adjustment is required for conversion mapping |Approved for |Implemented |
|Administrative Update for MILS/DLMS Conversion|between two MILSTRIP cancellation formats: the|implementation by DAASC | |
|for MILSTRIP ACP/ACM Cancellation Formats |ACP and ACM are mapped to DS 869C, Requisition | | |
|(Supply/MILSTRIP) |Cancellation. | | |
|6/02/08 | | | |
|Hilert | | | |
|ADC 286B, |The ADC 286 was provided to correct conversion |Approved for |Implemented |
|Administrative Update for MILS/DLMS Conversion|mapping between two MILSTRIP cancellation |implementation | |
|for MILSTRIP ACP/ACM Cancellation Formats |formats, the ACP and ACM, which are mapped to | | |
|(Supply/MILSTRIP) |DS 869C, Requisition Cancellation. ADC 286B | | |
|8/12/08 |identifies an additional update. Currently, | | |
|Hilert |neither the DS nor the DAAS map indicates a | | |
| |specific data element as the party to receive | | |
| |the transaction per the MILSTRIP ACP/ACM format| | |
| |(rp 4-6). | | |
|ADC 287, |- Updates to DoD 4000.25-M (reference 1a) , |Approved for | |
|Revision to DLMS 870L, SPR/LASE Status and |DLMS, Volume 2, Chapter 2, as revised by PDC |implementation | |
|Corresponding DLMS Manual Procedures; |297 (reference 1b) | | |
|Administrative Update to DLMS 830R, SPR |- Update DS 870L to support elimination of the | | |
|(Supply/MILSTRAP) (Staffed as PDC 303) |MILSTRAP/DLMS procedural incompatibility | | |
|6/24/08 |- Update DS 830R and 870L to identify the | | |
|Johnson |correlation to the corresponding MILSTRAP DI | | |
| |code functionality. | | |
|ADC 288, |This change updates the DLMS shipment status |Approved for |Implemented |
|Local Delivery Manifesting Shipment Status |procedures and the DLMS Version 4030 856S, |implementation by the | |
|(Supply) (Staffed as PDC 313) |Shipment Status transaction. It authorizes |DSS and DAASC on or | |
|6/23/08 |expanded use of the CCP shipment status format |about 6/27/08. | |
|Hilert |(see reference above) to include other | | |
| |consolidation processes performed subsequent to| | |
| |creation of shipment status, such as local | | |
| |delivery manifesting, for the purpose of | | |
| |providing passive RFID and updated status. | | |
|ADC 289, |This change identifies administrative revisions|Approved. This change | |
|Revisions to Security Assistance Program |to the MILSTRIP Chapter 6, Security Assistance |is effective | |
|Procedures, Modification of the Definition of |Program (Enclosure 2); DLMS dictionary, and |immediately. | |
|the Security Assistance Type of Assistance and|MILSTRIP Ap2.19, Security Assistance Type of | | |
|Financing Codes (MILSTRIP/Supply) and Policy |Assistance and Financing Codes (Enclosure 3), | | |
|Change to Billing Procedures |and MILSBILLS Chapter 2, Billing Procedures | | |
|(MILSBILLS/Finance) (staffed as PDC 289) | | | |
|10/21/09 | | | |
|ADC 290, |This change modifies the DS 810L, 812L and 812R|Approved for | |
|Administrative Revisions to DS 810L, Logistics|to incorporate administrative updates for |implementation | |
|Bill, 812L, Logistics Bill Adjustment Request |consistency among the DS. This change includes | | |
|Reply and 812R, Logistics Bill Adjustment |some DLMS enhancements, which may not be | | |
|Request |received or understood by the recipient’s | | |
|(Finance) (Staffed as PDC 287) |automated processing system. | | |
|6/24/08 | | | |
|Hammond | | | |
|ADC 292, |Administrative updates to DLMS Volume 2, |Approved for |The changes to the DLMS manual will be |
|Administrative Update to DLMS, Volume 2, |chapter 14, Issue, Loan, Demand, and |implementation |published in the next reissuance of the |
|Chapter 14, and DLMS Supplement 846F, |Freeze/Unfreeze Transactions, to address the | |manual. |
|Ammunition Freeze/Unfreeze Transaction |ASC X12 transactions beginning segment report | | |
|(Supply/MILSTRAP) |type codes and their correlation to MILSTRAP DI| | |
|7/23/08 |Code functionality. This information is useful | | |
|Johnson |in a mixed DLSS/DLMS environment. | | |
|ADC 293 |This change identifies revisions to SDR |Approved for phased |DAASC, DLA EBS, DSS implemented. Published in|
|Revised Time Standards, Codes, and Procedures |procedures and time standards for customers (SA|implementation |DLMS manual. |
|for Reporting and Processing of Supply |and U.S.), International Logistics Control | | |
|Discrepancies (Supply/SDR) (Staffed as PDC |Offices (ILCOs), and action activities | | |
|316) |including Distribution Depots (DDs) and | | |
|8/13/08 |Inventory Control Points/Integrated Item | | |
|Hilert |Managers (ICPs/IMMs). | | |
|ADC 294 |As a result of the Treasury Bulletin No. |Approved for |The changes to the DLMS manual will be |
|Elimination of Treasury Suspense Account F3885|2007-07, changes are required to MILSBILLS to |implementation |published in the next reissuance of the |
|(Finance) |discontinue the use of suspense account F3885 | |manual. |
|(Staffed as PDC 310A) |for the interfund transactions. | | |
|7/31/08 | | | |
|Hammond | | | |
|ADC 296 |This change includes an update to Chapter 24, |Approved for | |
|Passive Radio Frequency Identification (RFID) |Passive RFID Transactions and the requirement |implementation | |
|Transactions (Staffed as PDC 315) |to add “Delivered” and “Undelivered/Attempted | | |
|8/12/08 |Delivery” to the XML Visibility transaction in | | |
|Daverede |support of local delivery. | | |
|ADC 297, |This change documents and enhances an existing |Approved for |Implemented |
|Defense Automatic Addressing System Center |value-added DAASC process to support DLA |implementation by DAASC | |
|(DAASC) Passive Radio Frequency Identification|implementation of pRFID by inserting a |during October 2008 | |
|(pRFID)-Required Exclusion Table for DLMS 527D|pRFID-required indicator in DLMS 527D ARI | | |
|Advance Receipt Information |transactions (known as PMR in MILSTRAP). This | | |
|(ARI)/Prepositioned Material Receipt (PMR) |change expands the criteria used to determine | | |
|(Supply) (Staffed as PDC 321) |when the indicator is needed. | | |
|9/04/08 | | | |
|Hilert | | | |
|ADC 298, |This change documents the proposed procedures |Approved for |The changes to the DLMS manual will be |
|DODAAD Enhancements (Staffed as PDC 308) |that are applicable to the reengineered DoDAAD.|implementation |published in the next reissuance of the |
|9/16/08 |One change calls for adding the new GSA unique |by DAASC on or |manual. |
|, which |fields to the DAASINQ and enhanced eDAASINQ. |about October 1, |All changes implemented At DAASC except for |
| |One change establishes DoD policy that |2008. |GSA using DAASC system, which is pending |
| |Component governing directives require that | |implementation planned for Feb 2010. |
| |deploying units have current DoDAAC information| | |
| |prior to deployment. The remaining changes | | |
| |expand the capability of the DoDAAD web update | | |
| |page. | | |
|ADC 299, |- This ADC is provided to document correction |Approved for | |
|DLMS Lateral Redistribution Order Shipment |to the DLMS and DAAS conversion to properly |implementation | |
|Status (DLMS 856S/MILSTRIP AS6) and Party to |identify the party to receive credit and the | | |
|Receive Credit (Supply) (Staffed as PDC 307) |transaction originator when the shipment status| | |
|Hilert |is provided as LRO status. This requires an | | |
| |update to the DS 856S as indicated; | | |
| |perpetuation of code changes to the DLMS XML | | |
| |X12 EDI format, and a small adjustment to how | | |
| |the DAAS conversion program populates the | | |
| |“From” activity. | | |
| |- Based upon lack of interest in establishing | | |
| |such a requirement, the planned DLMS | | |
| |enhancement to separately identify different | | |
| |parties to receive credit for material and | | |
| |PCH&T are removed from DLMS. These may be | | |
| |reinstated at a future time. | | |
|ADC 301, |ADC 261 and 283 (references 3.b and 3.c) did |This change is approved | |
|Recognize Use of Ownership Code in Migrated |not reflect that the NAVSUP P-724 BG1/BG2 |for immediate Army, | |
|Navy Serial Number and Lot Number Transactions|transaction formats could have an ownership |Navy, and DAASC | |
|(NAVSUP P-724 BG1/BG2) Associated with DLMS |code. The BG1/BG2 transaction format showed |implementation. | |
|527R, 846R, 867I, and 947I (Supply) (Staffed |purpose code only. This change recognizes and | | |
|as PDC 322) |documents for mapping purposes, that the field | | |
|9/15/08 |in DI Code BG1/BG2 identified as ‘purpose code’| | |
|Johnson |is used for either ownership code or purpose | | |
| |code. | | |
|ADC 303, |Modifies WAWF to correctly handle |Approved for |Implementation WAWF release 4.1. |
|Transportation Identification Numbers in WAWF |transportation ID numbers and carrier ID codes.|implementation | |
|(Supply/Contract |It is required to make the TCN data field in | | |
|Administration/Transportation) (Staffed as PDC|WAWF compliant with DoD business rules and | | |
|323) |enhance the visibility of secondary | | |
|10/07/08 |transportation numbers and other transportation| | |
|Hilert/Daverede |related numbers. The existing data field for | | |
| |bill of lading number is modified to allow | | |
| |proper identification of the type of BL | | |
| |(commercial vs. Government). Corresponds to | | |
| |WAWF ECPs 517 and 518. | | |
|ADC 304, |Revise DAAS map document for the material |Approved for |Implemented |
|AFY Material Identification and Quantity |identification and quantity within the |implementation | |
|Mapping to DLMS 869A, Requisition |implemented DLMS transaction 869A, Requisition | | |
|Inquiry/Supply Assistance Request (Supply) |Inquiry/Supply Assistance Request | | |
|(Staffed as PDC 317) | | | |
|11/10/08 | | | |
|Hilert | | | |
|ADC 305, |This administrative change establishes a Table |Approved for | |
|Administrative Revision to DOD 4000.25-M, DLMS|of Contents and Chapter 1 - Introduction, which|implementation | |
|Manual, Volume 3 - Transportation |provides instructions applicable to the use of | | |
|10/23/08 |Volume 3 - Transportation. The change also | | |
|Transportation/ Supply/MILSTRIP |establishes a Chapter 3 - Passive RFID | | |
|Daverede/Hilert |Transactions, previously approved in ADC 296 | | |
| |and published as DoD 4000.25-M, Volume 2, | | |
| |Chapter 24. | | |
|ADC 306, |This administrative change updates the DoD |Approved for | |
|Administrative Change to Rail Transportation |codes, definitions, X12 conversion and MILSTRIP|implementation | |
|Mode/Method Codes and Definitions |references to authorized data source for | | |
|(Transportation/Supply (MILSTRIP)) |transportation mode/method codes associated | | |
|11/07/08 |with rail movements. | | |
|Daverede/Hilert | | | |
|ADC 307, |Administrative update to DLMS Volume 2, Chapter|Approved. The updated | |
|Administrative Update to DLMS, Volume 2, |6 to position the chapter for a future combined|chapter will be included| |
|Chapter 6, Physical Inventory Control, and DS |MILSTRAP/DLMS manual. Administrative updates |either in the next DLMS | |
|846P, 846R, and 888I (Supply/MILSTRAP) |to DS 846P, 846R, and 888I to clearly identify |manual formal change or | |
|11/10/08 |beginning segment transaction in the context of|reissuance, whichever | |
|Johnson |the applicable DLMS chapter and corresponding |comes first. | |
| |MILSTRAP DI Code functionality. | | |
|ADC 308, |DLMSO is revising DoD 4000.25-M, DLMS, to |Approved for | |
|Administrative Update to DLMS Chapter for |establish a separate chapter for Asset Status |implementation. | |
|Asset Status Reporting and Migrate Army SSF |Reporting and for administrative updates to the| | |
|Asset Balance Reporting Transaction, Document |chapter to incorporate correlation of the DS |This change supports an | |
|Identifier Code BSS, to DLMS 846I, Asset |846I beginning segment Report Type Code to the|Army Logistics | |
|Status, for Intra-Army Use (Supply) |corresponding DoD 4000.25-2-M, MILSTRAP DI |Modernization Program | |
|(Staffed by PDC 327) |code, for information in a mixed DLMS/DLSS |release. | |
|1/12/09 |environment consistent with other MILSTRAP | | |
|Johnson |related DLMS chapters. In addition to these | | |
| |administrative changes, DLMSO will revise the | | |
| |chapter to address the intra-Army use of DS | | |
| |846I Asset Status Report transaction for the | | |
| |function associated with Army DI Code BSS. | | |
|ADC 309, |Resolves a DLMS/MILS conversion issue between |Type Pack Code 463L | |
|Notice of Availability (NOA) and NOA Reply |the MILSTRIP AD5 and the comparable DLMS 870N, |Pallets is effective | |
|Transaction Data Content/Mapping including |Notice of Availability Reply. Revisions are |immediately. There is | |
|Addition of Type Pack Code for 463L Pallets |identified to add a code and DLMS note to DS |no current schedule for | |
|(Supply/Transportation) (Staffed as PDC 318) |870N supporting what the DAAS map has already |DLMS implementation | |
|6/03/09 |implemented, and add a future enhancement to |NOA/NOA Reply by the | |
|Hilert/Daverede |the process to identify the NOA submitter. |Distribution Standard | |
| |Modifies the location of the type pack code in |System. Coordination | |
| |the DS 856N, Notice of Availability. Updates |between DAASC and | |
| |MILSTRIP Appendix 3.30 to correctly identify |USTRANSCOM for | |
| |the authorized data source for valid DoD Type |integrated data | |
| |Pack Codes. Updates the Type Pack Code |environment is requested| |
| |Conversion Guide to add a type pack code for |prior to map updates | |
| |463L pallet and its applicable X12 conversion |projected for October | |
| |code. Updates the DLMS and MILSTRIP Manuals |2009. | |
| |References and Abbreviations sections to | | |
| |include a definition of United States | | |
| |Transportation Command’s (USTRANSCOM) Table | | |
| |Management Distribution System (TMDS) and its | | |
| |associated URL | | |
|ADC 311, |The change standardizes the attachment process |Approved for |Scheduled for Feb 2010 implementation by |
|SDR Attachment Interface (Supply/SDR) (Staffed|for all Service/Agencies interfacing with the |implementation |AFSAC, PDREP, and NSDRS. |
|as PDC 332) |DoD WebSDR. Currently the DoD WebSDR System |approximately October 1,| |
|5/13/09 |interfaces cannot transmit or receive SDR |2009 | |
|Hilert |attachments via the GEX or MQ Series SDR | | |
| |interface connections. This change allows the | | |
| |Services and Agencies interfacing with the DoD | | |
| |WebSDR to transmit and receive attachments via | | |
| |a standard process. | | |
|ADC 312, |This change requests that the denial management|Approved for all | |
|Denial Management Code in a Supply Status |code approved by ADC 191 for use on a supply |Components using a | |
|Transaction (Supply/MILSTRIP) (Staffed as PDC |status transaction on an intra-Army basis be |phased implementation | |
|334) |established for DOD usage. The volume of Army |approach. A projected | |
|01/22/09 |orders supported on an inter-Service basis |implementation date is | |
|Hilert |drives the need for this functionality to be |not available at this | |
| |extended beyond intra-Army. |time. | |
|ADC 314, |This administrative update to DLMS Volume 2, |Approved. The change to| |
|Administrative Update to DLMS, Volume 2, |Appendix 5 corrects erroneous paragraph number |the DLMS manual will be | |
|Appendix 5, Instructions for Submission of DoD|references, for DoD 4140.1-R, cited in the |published in the next | |
|UIT Program Candidates (Supply/UIT) |Instructions for Submission of DoD UIT Program |reissuance of the | |
|12/22/08 |Candidates. |manual. | |
|Johnson | | | |
|ADC 315, |This change modifies the DS 810L to incorporate|Approved for | |
|Administrative Change to DLMS Note for Fund |an administrative change to correct an |implementation | |
|Code in DLMS 810L, Logistics Bill (Finance) |incorrect DLMS note regarding the qualifier DG | | |
|01/05/09 |(Fund Code), which incorrectly states that the | | |
|Hammond |fund code may not be used with Interfund bills | | |
|ADC 316, |Implement a standardized interchange between |Approved for | |
|Retail Transportation and Supply Receipt and |retail transportation and supply through the |implementation | |
|Acknowledgement Transactions |use of EDI transactions, specifically the | | |
|(Transportation/Supply), (Staffed as PDC 324) |Warehouse Shipping Order, 940R, and Warehouse | | |
|2/19/09 |Shipping Advice, 945A. | | |
|Daverede | | | |
|Approved Addendum to ADC 316A, USAF |The purpose of this requested action is to |Approved for | |
|Requirements for Item Record Data and UIT |enhance the SBSS - CMOS interface in |implementation | |
|using the Materiel Release (DS 940R) under |association with implementation of the ADC 316 | | |
|Transportation and Supply Receipt and |procedures for retail transportation and supply| | |
|Acknowledgement Interchange |receipt and acknowledgement interchange. The | | |
|(Supply/Transportation) (Staffed as Proposed |change will allow SBSS to perpetuate selected | | |
|Addendum to ADC 316A) |item record (NSN) data and serialized control | | |
|6/26/09 |numbers/UII in the 940R Material Release | | |
|Daverede/Hilert |transaction. CMOS requires selected item | | |
| |record data for each shipment record that CMOS | | |
| |builds. This information, derived from FLIS, | | |
| |is not currently available to CMOS. This | | |
| |change provides for the inclusion of serial | | |
| |number and unique item identifiers for | | |
| |applicable items in support of an approved UIT | | |
| |program for PIC NWRM (UID Designator Code AAJ).| | |
|Approved Addendum to ADC 316B, New |The purpose of this change is to clearly |Approved for | |
|Distribution Code (111) for the Retail |identify the transactions used for the Retail |implementation | |
|Transportation and Supply Receipt and |Transportation and Supply Receipt and | | |
|Acknowledgement Interchange for the 940R and |Acknowledgement Interchange. The distribution | | |
|945A (Transportation/ Supply Chain Visibility |code identified for use in ADC 316 was “1”, | | |
|and Accountability) (Staffed as Proposed |which was reserved for use. After a review by | | |
|Addendum to ADC 316B) |DAASC, it was determined there were a small | | |
|6/26/09 |number of transactions using distribution code | | |
|Daverede/Hilert |“1”, but not in Retail Transportation and | | |
| |Supply interchange transactions. In order to | | |
| |eliminate any confusion on the use of the | | |
| |distribution code for the Retail Supply and | | |
| |Transportation interchange, a new code is | | |
| |proposed. The new code is “111”. | | |
|Approved Addendum to ADC 316C, Revise DS 940R |This addendum to ADC 316 (Retail Transportation|Approved for | |
|Material Release and DS 945A Material Release |and Supply Receipt and Acknowledgement |implementation | |
|Advice, to Support Unique Item Tracking for |Transactions), authorizes the generation of an | | |
|USAF PIC under the Retail Transportation and |information copy of the 940R and 945A | | |
|Supply Receipt and Acknowledgement Interchange|transactions (Distribution Code “111”) for a | | |
|(Supply/Transportation) |specific USAF PIC NWRM need. This change | | |
|1/15/10 |utilizes the established standardized | | |
|Daverede/Hilert |interchange between retail transportation and | | |
|USAF |supply through the use of EDI transactions, | | |
| |specifically the Material Release, 940R, and | | |
| |Material Release Advice 945A. For this | | |
| |addendum, USAF PIC Fusion will receive an | | |
| |information copy (image) of the 940R and 945A | | |
| |transactions that use the Retail | | |
| |Transportation/Supply Interchange (Distribution| | |
| |Code of “111”), for NWRM data requirements. | | |
|Approved Addendum to ADC 316D, USAF-Unique |DAASC requires maps for internal USAF-Unique |Approved for | |
|Document Identifier Code Mappings to 940R |DICs that will be used in support of the Retail|implementation | |
|under the Retail Transportation and Supply |Transportation and Supply interface, so that | | |
|Receipt and Acknowledgement Transactions |they can properly translate and route these | | |
|(Transportation/Supply) |transactions. | | |
|8/03/10 | | | |
|Daverede | | | |
|USAF | | | |
|ADC 317, |This change authorizes two new SDR action codes|Approved for |EBS implementation of transactions for Type W |
|Revised Business Rules for |to distinguish between SDRs requiring expedited|implementation upon |scheduled for Feb 2010. |
|Transshipper-Prepared SDRs (Supply/SDR) |response to resolve frustrated freight problems|completion of new | |
|(Staffed as PDC 333) |and those requiring no response, but which may |routing rules (estimated|DSS implementation of incoming Type W |
|2/17/09 |be used by the action activity to correct |implementation March 31,|scheduled for 2010. |
|Hilert |shipping/packaging errors, recoup money from |2009). | |
| |noncompliant vendors, and identify trends. A | |DSS IOC for FY10.1 Increment is scheduled for |
| |time standard of 5 days is established | |19 April - 4 June 2010. |
| |expedited response. This change authorizes | | |
| |special routing rules related to | | |
| |transshipper-prepared SDRs based upon Component| | |
| |request. This change will support immediate | | |
| |use of DoD WebSDR for submission of SDRs by | | |
| |aerial ports by authorizing the use of SDR Type| | |
| |W via WebSDR and future inclusion of additional| | |
| |data fields specific to transshipment SDRs | | |
|Approved Addendum to ADC 317A, |This change provides additional discrepancy |Approved for |DAASC implementation date is 11/02/09. |
|Transshipper-Prepared SDRs for Documentation |codes to specifically target high volume |implementation beginning| |
|and Labeling Discrepancies (Supply/SDR) |discrepancies encountered by transshippers | |EBS implementation of transactions for Type W |
|9/15/09 |(refer to Enclosure 1 for details). In |11/01/09 |scheduled for Feb 2010. |
|Hilert |addition, this change modifies the text names | | |
| |associated with existing documentation | |DSS IOC for FY10.1 Increment is scheduled for |
| |discrepancy codes so that they may be used for | |19 April - 4 June |
| |various types of documentation, including | |2010. |
| |vendor shipment documentation. Four-position | | |
| |detail codes are assigned for consistency with | | |
| |concept of generic vs. detailed codes similar | |Transaction exchange implemented for DLA EBS |
| |to those used in the packaging area. The | |April, 2010 (based on Feb 2010 release) |
| |existing Code H6 discrepancy is re-assigned | | |
| |(and split among two codes) under the D-series | | |
| |to make it easier for transshippers to locate. | | |
| |Two new discrepancy codes are added to the | | |
| |Packaging Discrepancy code list in the Improper| | |
| |Marking series to call out discrepancies | | |
| |related to the Military Shipping Label (MSL). | | |
|Approved Addendum to Approved Defense |Action activities often respond to SDRs from |Approved for phased | |
|Logistics Management System (DLMS) Change |transshippers with replies that make it |implementation of new | |
|(ADC) 317B, Action Activity Replies to |apparent that the SDR was processed as if it |edit requirements. | |
|Transshipper-Prepared SDRs (Supply/SDR) |were reported by the customer. For example, | | |
|(Staffed as PDC 317B) |action activities sometimes respond that credit| | |
|06/01/11 |is recommended or that the materiel was shipped| | |
|Hilert |as requisitioned. Establishing an edit on | | |
|PRC Chair |inappropriate disposition/reply codes will help| | |
| |ensure more appropriate responses are provided.| | |
| |This change is provided to formally document | | |
| |the inappropriate replies so that a standard | | |
| |approach can be used by all DoD applications | | |
| |that prepare SDR replies. | | |
|ADC 318, |This change documents the procedures that are |Approved for |Implemented as DAASC |
|DODAAD Country Codes in the DODAAD (Staffed as|applicable to the country code listing of the |implementation | |
|PDC 325) |DoDAAD and procedures for notifying CSPs of | | |
|3/24/09 |country code changes. This change reiterates | | |
|Hammond |that CSPs are responsible for ensuring their | | |
| |Component DODAAC information is current and | | |
| |that Component CSPs must take action to ensure | | |
| |DoDAAC country code information is validated | | |
| |whenever there is a change to the country code | | |
| |listing. This change also excludes activity | | |
| |codes applicable to programs and not to | | |
| |countries from being entered into the address | | |
| |field of the DODAAD | | |
|ADC 319, |Corrects identification of Service code |Approved for | |
|Use of Two-Position Service/Agency Codes for |assignments used to recognize contractor |implementation | |
|DLA and the USCG (Supply) (Staffed as PDC |DoDAACs. This change supports requisition | | |
|342) |processing associated with Government-furnished| | |
|4/06/09 |material (GFM) and contractor-furnished | | |
|Hilert |material (CFM), as well as any other logistics | | |
| |processes which require recognition of | | |
| |contractor DoDAACs | | |
|ADC 320, |1). Adds the ‘transaction creation date’ to |Approved for | |
|Revises DS 846P to Add Transaction Creation |846P. This supports both MILSTRAP DI Codes DZM|implementation | |
|Date; and for Intra-Navy Changes to Migrate |(rp 70-73) and DZJ (rp 73-76). 2). Map Navy DI| | |
|Navy BZA/BZC Data Requirements to 846P End of |Codes BZA and BZC data to DLMS 846P for | | |
|Day Transaction Count Function (Supply) |CAV-ORM, and OIS; MSC applications –ShipCLIP, | | |
|(Staffed by PDC 272) |WebCLIP and FMS; SPAWAR Rsupply, NAVFAC SUPMIS,| | |
|6/15/09 |and CAV II usage. These applications are | | |
|Johnson |migrating from MILS to DLMS transactions. Navy| | |
| |currently uses (1) CAV II (BZC) and (2) CAV-| | |
| |ORM (BZA/BZC ) transactions, and requests that | | |
| |DLMSO revise 846P to accommodate the BZA/BZC | | |
| |data, and that data maps be developed to map | | |
| |BZA and BZC to DLMS 846P. 3). This change also| | |
| |maps Navy DI Code BZC and BZA data to DLMS 846P| | |
| |for CAV-ORM. In response to staffing of PDC | | |
| |272, Navy also requested the addition of a | | |
| |qualifier in segment 2/REF/140 to identify when| | |
| |the End of Day Count transaction was generated | | |
| |by CAV-ORM to satisfy the Navy ICP and ERP | | |
| |requirements. This supports Navy DI Code BZC | | |
| |and BZA data requirement by means of mapping | | |
| |the "C" in position 80 of BZA/BZC transactions | | |
| |which is currently used to indicate that the | | |
| |BZA/BZC was generated by CAV-ORM. | | |
|ADC 321, |This change documents the procedures that are |Approved for |Implemented at DAASC. |
|DOD Activity Address Directory (DODAAD) Bill |applicable to the BLOC in the DoDAAD, and |implementation | |
|of Lading Code (BLOC) (Staffed as PDC 343) |changes the source of input from the DODAAD | | |
|4/14/09 |Administrators to the Authoritative BLOC | | |
|Hammond |information source, Table Management | | |
| |Distribution System (TMDS). This will improve | | |
| |timeliness and accuracy of the BLOC data. | | |
|ADC 322, |This change adds the capability to identify a |Approved for | |
|Addition of Local Catalog ID qualifier to |local catalog ID in requisitions and supply |implementation. The | |
|Support Requirements for TEWLS Requisitions |status. This will allow AMMA sites to |DLMS 511R, Requisition, | |
|(Supply) (Staffed as PDC 347) |communicate the local catalog ID to EBS in |format is required for | |
|5/07/09 |requisitions to allow purchase orders to be |immediate | |
|Hilert |created for the material that will be receipted|implementation. The | |
| |into inventory via the DLMS 527R. Stock buys |other formats are | |
| |are funded with DLA DWCF under the TEWLS/AMMA |planned for later | |
| |business model so inventory must be accounted |implementation. | |
| |for in DLA systems. | | |
|ADC 323, |This change documents enhancements recommended |Approved for |All changes implemented at DAASC except for |
|DoDAAD Enhancements to DoDAAD Including |by the DoDAAD PRC at the March 10, 2009 PRC |implementation |multiple contracts assigned to a single |
|Contracting Data and other Enhancements |meeting. Included are enhancements to | |DoDAAC. |
|(Staffed as PDC 348) |strengthen controls for contractor DoDAACs and | | |
|5/19/09 |other enhancements. | | |
|Hammond | | | |
|Approved Addendum 323A to ADC 323, Rescind |This amends ADC 323 to delete the approved |Approved for | |
|Multiple Contracts per DoDAAC Change(Proposed |enhancement for adding multiple contracts |implementation | |
|Addendum 323A) |assigned to a single DoDAAC to the DoDAAD and | | |
|01/21/11 |for modifying the eDAASINQ search capability to| | |
|Hammond |query the multiple contract fields. | | |
|PRC Chair | | | |
|ADC 324, |This change documents procedures for materiel |Approved for |Implemented for Spiral I |
|DLMS Procedures for Materiel Returns from |returns to the DLA under the NIMS the 2005 BRAC|implementation | |
|National Inventory Management Strategy (NIMS)|decision. The change addresses communication | | |
|Sites and Industrial Sites under BRAC |between customer, the distribution depot, and | | |
|(MILSTRAP, MILSTRIP, MILSBILLS, DLMS) (Staffed|the DLA ICP, and establishes new procedures for| | |
|by PDC 312) |authorizing and processing customer credit for | | |
|6/24/09 |the returned materiel. | | |
|Hilert/Johnson/Hammond | | | |
|ADC 325, |Navy systems use the BHJ transaction to notify |Approved for |Navy’s expected implementation date is |
|Revise DS 867D, Demand Reporting to Address |the NAVICP about sales of non-NSN material to |implementation |February 2010, with testing to be conducted |
|Navy BHJ Transaction Requirements (Supply) |customers. These transactions allow the NAVICP| |prior to that date. |
|(Staffed by PDC 346) |to keep track of the demand for these items. | | |
|5/27/09 |If there is enough demand for the item then | | |
|Johnson |NAVICP will request that the item be catalogued| | |
| |by FLIS. Navy-ERP needs to provide the ICPs | | |
| |with the capability to accept, record, and | | |
| |control demand data for non-stock numbered | | |
| |actions resulting from local purchase or | | |
| |manufacture. The collection and recording of | | |
| |this demand is an important element in | | |
| |identifying future material requirements and in| | |
| |positioning material. | | |
|ADC 326, |Purpose is clarification of intent for mapping |Approved for | |
|DS 869A, Requisition Inquiry/Supply Assistance|purposes and to assign correct beginning |implementation | |
|Request, Correction and Clarification of Data |segment value for the AFY. | | |
|Mapping, Administrative Updates, and | | | |
|Coordination of Procedures for | | | |
|Transaction-Based Supply Assistances Requests | | | |
|(Supply) (Staffed as PDC 349) | | | |
|8/31/09 | | | |
|Hilert | | | |
|ADC 328, |This change requests an interface be |Approved for phased |Navy concurs concept, however, cannot commit |
|“Off-Line” Requisition Processing: Internet |established between the various internet |implementation. Initial|to systems changes at this time. |
|Ordering Application Request for Component |ordering applications and the applicable |implementation will be | |
|Verification of Funds Availability and |Component financial application, so that fund |through a pilot program |Army FCM ready Sep 2009 |
|Recording of the Financial Obligation |availability can be checked before allowing the|with the Army projected | |
|(Finance/Supply/MILSTRIP/MILSBILLS) (Staffed |requisition to be processed, and, as a |for early 2010. |DoD EMALL delayed; target implementation |
|as PDC 266) |separate, subsequent action, establish the | |Spring 2010 |
|7/28/09 |associated obligation within the applicable | | |
|Hilert |financial system. | |USMC planning for 2nd implementation |
| | | | |
| | | |The FCM integration is schedule for release in|
| | | |Jun 10. |
| | | | |
| | | |GSA: April, 2011 timeframe |
| | | |DoD EMALL and Army Funds Control interface |
| | | |Sept 2010. |
|ADC 329, |This change identifies revisions to DLMS Manual|Approved for | |
|Use of Borrowed and Migration Codes in DLMS |4000.25-M Volume 1, Chapter 8 to include |implementation | |
|Supplements (Supply/Finance/Contract Admin) |clarifications regarding the use of Borrowed, | | |
|(Staffed as PDC 335) |Local and Migration codes. | | |
|6/23/19 | | | |
|Lyons | | | |
|ADC 330, |To specify appropriate Data Element 1065 |Approved for | |
|Revision to DS 824R, Reject Advice (Supply) |qualifier in DS 824R in the NM1, Individual or |implementation | |
|(Staffed PDC 354) |Organization Name, segment. | | |
|6/08/09 | | | |
|Johnson | | | |
|ADC 331, |This change is applicable to the vendor |Approved | |
|Revised 857, Shipping and Billing Notice, for |submission of the Shipment and Billing Notice | | |
|Vendor Submission to Wide Area Workflow (No |857, Combination Receiving Report (RR) and | | |
|WAWF Trading Partner Impact) (WAWF/Contract |Commercial Invoice (CI), to WAWF. This | | |
|Administration) |transaction is not used within DoD. WAWF | | |
|4/08/10 |output splits the 857 to the separate receiving| | |
|Hilert |report (856) and commercial invoice (810). | | |
|BTA |This change is published for documentation of | | |
| |revisions to the Federal IC perpetuated from | | |
| |previously approved changes to the RR and CI | | |
| |data content. | | |
|ADC 332, |The purpose of this change is to map the Navy’s|Approved for | |
|Intra-Navy Exchange Price Billing for Depot |current billing transactions for depot level |implementation | |
|Level Repairables (MILSBILLS/Finance) (Staffed|repairables (DLRs) under the Navy Carcass | | |
|as PDC 345) |Tracking program to DS 810L, Logistics Bill. | | |
|7/08/09 |This change will support the Navy migration to | | |
|Hammond |DLMS, and will support mapping in a mixed | | |
| |DLMS/MILS environment. | | |
|ADC 333, |DLMSO has an ongoing initiative to combine the |Approved for | |
|Revision to DLMS, Volume 2, Chapter for |DLSS and DLMS manuals. The current process of |implementation | |
|Logistics Asset Support Estimate (LASE); and |maintaining two sets of publications, which | | |
|Administrative Updates to DLMS 846L, 870L, |contain essentially the same information for |Changes to | |
|LASE Request Codes and Reject Advice Codes |the different formats, is resource intensive, |DLMS and MILSTRAP will | |
|(Supply/MILSTRAP) (Staffed as PDC 355) |duplicative in nature, and no longer practical.|be published in the next| |
|8/05/09 |This change makes administrative updates to the|reissuance of the | |
|Johnson |DLMS, Volume 2 (reference 3b) LASE chapter, |manuals. | |
| |which positions the chapter for movement to a | | |
| |combined manual. In addition administrative | | |
| |updates to DLMS 846L, 870L, LASE Request Codes | | |
| |and Reject Advice Codes | | |
|ADC 334, |This change documents the process by which the |Approved for |Implemented |
|Supply Discrepancy Report Process for AF |AF will identify a supply discrepancy and |implementation | |
|Retail Storage Activity Denials (Supply/SDR) |request credit as the result of storage | | |
|(Staffed as PDC 357) |activity denials after DLA assumes SS&D | | |
|8/31/09 |functions at the three Air Logistics Centers. | | |
|Hilert | | | |
|ADC 337, |This change adds a free-form note field to the |Approved for |Implemented at DAASC |
|DOD Activity Address Directory (DoDAAD) |DOD Activity Address File (DODAAF), which will |implementation | |
|Internal Note Field (Staffed as PDC 362) |be viewable and downloadable in the Enhanced | | |
|8/28/09 |DAASC Inquiry System (eDAASINQ) by DODAAC | | |
|Hammond |Central Service Points (CSPs) and Monitors, | | |
| |according to their existing role-based access | | |
| |for updating, adding or deleting DODAACs. | | |
|ADC 338, |This change request is for the assignment of a |Approved for |Implemented at DAASC |
|New Advice Code for Surge Requirements of |new MILSTRIP Advice Code for use on applicable |implementation | |
|Mission Support Material (MSM) under Navy BRAC|DLMS transactions associated with |approximately January | |
|IMSP (MILSTRIP/ Supply) (Staffed as PDC 358) |requisitioning to identify surge requirements |2010. | |
|9/28/09 |for MSM under DLA-Navy BRAC IMSP. The Advice | | |
|Hilert |Code will be used to trigger special processing| | |
| |rules in DLA’s EBS. | | |
|ADC 338A, |This change republishes ADC 338 to replace the |Approved for |No impact for Army |
|Surge Requirements of Mission Support Material|assigned advice code with a new management code|implementation | |
|(MSM) under Navy BRAC SS&D IMSP |for use on DLMS transactions associated with |approximately January | |
|(Supply/MILSTRAP/MILSTRIP) |requisitioning to identify surge requirements |2011 | |
|8/24/10 |for Mission Support Material (MSM) under | | |
|Hilert |DLA-Navy BRAC IMSP. Use of a management code | | |
|DLA |(in lieu of an advice code) to identify surge | | |
| |requirements will allow for continued | | |
| |independent use of applicable advice codes on | | |
| |the requisition. The management code will be | | |
| |used to trigger special processing rules in | | |
| |DLA’s EBS. | | |
|ADC 339, |This approved change updates the DoD codes, | It is critical that |At that time, DAASC will begin using the |
|Change to Transportation Mode/Method Codes and|definitions, X12 conversion and MILSTRIP |Components plan their |updated table. Components shall not implement|
|Definitions (Transportation/Supply (MILSTRIP))|references with an authorized data source for |implementation of this |earlier, otherwise their data will be |
|Staffed as PDC 339) 10/20/09 |transportation mode/method codes. |change for a |unsynchronized at the enterprise level. If |
|Daverede/Hilert | |synchronized logistics |you are unable to implement on October 1, |
| | |domain implementation |2010, request you coordinate with DAASC in |
| | |date of October 1, 2010.|advance. |
| | | | |
| | | |DLA EBS has completed/released ADC 339 in EBS |
| | | |(Release 11.1B) on 11/26/10 |
|ADC 341, |Revise DLMS to support CAV II data requirements|Approved for the |Navy provided an implementation date of |
|Revise DS 867I Issue in Support of Navy ERP |by adding specific data elements and code |earliest implementation |October 2, 2009 |
|and CAV II Systems with Interim Measure for |values to DS 867I Issue transaction, and |date agreed upon by Navy| |
|CAV Detail Issue Transaction (Supply) (Staffed|provides interim process for Navy ERP |and DAASC. | |
|by PDC 351A) |requirement for separate, multiple “detail” | | |
|10/07/09 |transactions for a given issue transaction to | | |
|Johnson |accommodate CAV in Navy ERP release 1.1. | | |
|ADC 342, |Revise DLMS to support Navy ERP and CAV II |Approved for the |Navy provided an implementation date of |
|Revise DLMS 527D Advance Receipt Information |requirements by adding specific data elements |earliest implementation |October 2, 2009 |
|and 527R Receipt in Support of Navy ERP and |and code values to DS 527D Advance Receipt |date agreed upon by Navy| |
|CAV II Systems with Interim Measure for CAV |Information (ARI)/ Prepositioned Materiel |and DAASC. | |
|Detail Receipt Transaction (Supply) (Staffed |Receipt (PMR) and 527R receipt transactions. | | |
|by PDC 352A) |Includes interim process for Navy ERP | | |
|10/07/09 |requirement for separate, multiple “detail” | | |
|Johnson |transactions for a given receipt transaction to| | |
| |accommodate CAV in Navy ERP release 1.1. | | |
|ADC 343 |Revise DLMS to support Navy ERP and CAV II data|Approved for the |Navy provided an implementation date of |
|Revise DS 947I Inventory Adjustment |requirements by adding specific data elements |earliest implementation |October 2, 2009 |
|Transaction in Support of Navy ERP and CAV II |and code values to DS947I. Includes interim |date agreed upon by Navy| |
|Systems with Interim Measure for CAV Detail |process for Navy ERP requirement for separate, |and DAASC. | |
|Inventory Adjustment Transaction (Supply) |multiple “detail” transactions for a given | | |
|(Staffed by PDC 353 and the Addendum to PDC |inventory adjustment transaction to accommodate| | |
|353) |CAV in Navy ERP release 1.1. | | |
|10/07/09 | | | |
|Johnson | | | |
|ADC 344, |This change establishes revisions to the DLMS |Approved for testing and| |
|Revised DLMS Shipment Status (856S) in Support|shipment status DS 856S to support continued |subsequent | |
|of Navy ERP and CAV II Systems and Carrier |use of the CAV business process known as “Proof|implementation effective| |
|Name Field Length in Material Release Advice |of Shipment (POS).” This transaction will be |immediately | |
|(945A) (Supply) (Staffed as PDC 350) |used as the interim vehicle to transmit | | |
|10/27/09 |shipment information from CAV II to Navy-ERP. | | |
|Hilert |This change also increases the field length | | |
| |carrier as it appears in the Shipment Status | | |
| |and Material Release Advice. | | |
|ADC 346, |This change publishes procedures for DoD |Approved for |This will be included in the next publication |
|DLMS Interfund Billing System Procedures |4000.25-M, DLMS Volume 5 (Finance), Chapter 5 -|implementation |of DoD 4000.25-M. |
|(Finance) (Staffed as PDC 367) |Interfund Billing System Procedures. | | |
|10/26/09 | | | |
|Hammond | | | |
|ADC 347, |This change revises DLMS receipt, issue, |To ensure a synchronized| |
|Revise DS 527R Receipt, 867I Issue, 945A |materiel release advice, and inventory |implementation between | |
|Materiel Release Advice, and 947I Inventory |adjustment (DS 527R, 867I, 945A, and 947I) to |DSS, PIC Fusion, and | |
|Adjustment to Support Unique Item Tracking for|allow a new action code which will clearly |DAAS, request that by | |
|USAF PIC (Supply) (Staffed as PDC 370) |identify their use as “image” transactions |November 17, 2009, DLA | |
|10/27/09 |which do not affect the accountable records |identify the earliest | |
|Johnson |when the balance-affecting accountable |possible implementation | |
| |transaction bypassed the normal DAASC |date for DSS and USAF | |
| |transaction flow. Once available as an image |identify the earliest | |
| |transaction, the DLMS transaction containing |possible implementation | |
| |information pertaining to the specific business|date for PIC Fusion. | |
| |process and the applicable serial number(s) may| | |
| |be passed to a designated party for | | |
| |information. | | |
|ADC 348, |Mapping Customer Operations (MCO) is in the |MCO has a DLA imposed | |
|Revise DS 527R and 527D in Support of Mapping |process of designing and deploying a new |deadline to launch MEBS | |
|Product Requirements (Supply) (Staffed as PDC |system, Mapping Enterprise Business System |by June 2010. | |
|371) |(MEBS). This change provides a means to convey|Transitioning from | |
|10/26/09 |the Edition Date, and other mapping product |current production to | |
|Johnson |data, between the Distribution Standard System |MEBS will begin February| |
| |(DSS) and MEBS in DLMS format. |2010. | |
|ADC 349, |To transmit MAC from a Losing Inventory Manager|Approved for | |
|Revise DS 536L Logistics Reassignment (LR) |(LIM) to a Gaining Inventory Manager (GIM) |implementation | |
|Management Data to Add a Moving Average Cost |during a LR. | | |
|(MAC) Field (Supply/Finance) (Staffed as PDC | | | |
|369) | | | |
|11/16/09 | | | |
|Johnson | | | |
|ADC 350, |The purpose of this change is to map the Navy’s|Approved for | |
|Navy Budget Project for Billing |current MILS billing transactions for the |implementation | |
|(MILSBILLS/Finance) (Staffed as PDC 373) |Summary Bill to DS 810L, Logistics Bill by | | |
|11/16/09 |including a DLMS qualifier called “budget | | |
|Hammond |project identifier” for Navy “budget project”. | | |
| |This change will support the Navy migration to | | |
| |DLMS, and will support mapping in a mixed | | |
| |DLMS/MILS environment. | | |
|ADC 351, |This change allows for the 527R FA2 Accounting |Approved for | |
|Revisions to DS 527R for FA2 Accounting Data |Data segment to be propagated on DLMS 527R |implementation | |
|Segment to Support AMMA Receipt Processing |receipt transactions from AMMA sites to DLA’s | | |
|(Supply/Finance) (Staffed as PDC 372) |EBS for procurement source 527R receipt | | |
|11/24/09 |transactions DI Code D4_ transactions under | | |
|Johnson |MILSTRAP) | | |
|ADC 352, |This change authorizes the assignment of a new |Approved for | |
|Management Code for Product Quality Deficiency|management code for use on DLMS MILSTRIP |implementation January | |
|Report (PQDR) Replacement Requisitions |requisitions The new code will indicate the |2011 for BRAC IMSP | |
|(Staffed as PDC 380) (Supply) |materiel is being re-requisitioned upon | | |
|2/18/10 |determination that the originally requisitioned| | |
|Hilert |materiel was deficient and subsequent to | | |
|DLA |submission of a PQDR. | | |
|ADC 353, Procedures for Pre-positioned |This change provides notification of shipment |Approved for phased |ADC 353A replaces ADC 353 in its entirety. |
|Materiel Receipt (PMR) and Shipment Status for|of a returned item of supply and an appropriate|implementation | |
|Retrograde and Directed Discrepant/Deficient |PMR. It proposes modification of the DS 856R | | |
|Materiel Returns (Staffed as PDC 331) |and 527D and associated business rules to | | |
|07/01/10 |discretely identify the type of materiel return| | |
|Hilert |(discrepant/deficient return, retrograde) and | | |
|NAVICP |provide a matching PMR and materiel returns | | |
| |shipment status to the receiving activity. | | |
| |This change specifically requires assignment of| | |
| |an appropriate TCN to retrograde and directed | | |
| |return shipments (to eliminate reuse). | | |
|ADC 353A, |ADC 353A revisions are highlighted in yellow. |Approved for phased | |
|Revised Procedures for PMR and Shipment Status|Revisions are limited to the SA/FMS time |implementation | |
|for Retrograde and Directed |standard for discrepant return and the | | |
|Discrepant/Deficient Materiel Returns |associated Estimated Due Date (EDD) for the PMR| | |
|Including Corrected Time Standard for Security|Document. All other aspects of this document | | |
|Assistance/Foreign Military Sales (SA/FMS) |are carried forward from the original version | | |
|(Supply/SDR/PQDR/TDR/Retrograde) |without change. | | |
|8/25/10 | | | |
|Hilert | | | |
|Navy | | | |
|ADC 354, |To clarify procedures for DAASC DoDAAC edits on|Approved for | |
|DoDAAC Edits on Logistics Bills and |logistics bills and requisitions. |implementation | |
|Requisitions (Finance/DoDAAD/Supply) (Staffed | | | |
|as PDC 368) | | | |
|2/04/10 | | | |
|Hammond | | | |
|PRC Chair | | | |
|ADC 355, |Navy modernized system development is being |Approved for | |
|Revise DS 846I, Asset Status Inquiry/Report to|programmed to be DLMS compliant. The legacy |implementation | |
|Address Intra-Navy Use of Transaction |systems DI Code DZA data reflected in | | |
|Preparation Date in Multiuse Field of MILSTRAP|intra-Component multiuse field needs to be | | |
|DZA Transaction (Supply) (Staffed as PDC 390) |mapped to the 846I Asset Status Inquiry/Report | | |
|2/05/10 |transaction. | | |
|Johnson | | | |
|Navy | | | |
|ADC 356, |Navy modernized system development is being |Approved for | |
|Revise DS 846I, Asset Status Report to Address|programmed to be DLMS compliant. The legacy |implementation | |
|Intra-Navy Requirements for Navy Document |systems DI Code BA7 matches well with the DLMS | | |
|Identifier BA7, Cyclic Asset Status Report - |equivalent 846I Inventory Inquiry/Advice | | |
|Mobile Activities (Supply) |transaction, but has never been mapped to it | | |
|2/05/10 | | | |
|Johnson | | | |
|Navy | | | |
|ADC 357, |DLA requires visibility of the BDN in the DS |Approved for | |
|Revisions to DLMS SDR to Add Build Directive |842 series (report and reply). This change |implementation in 2011 | |
|Number (BDN) (Supply/SDR) |supports the medical and industrial kitting | | |
|2/18/10 |community requirements for tracking all | | |
|Hilert |reported discrepancies by a specific BDN in | | |
|DLA |order to identify kitting assembly production | | |
| |impacts. | | |
|ADC 358, |This change addresses multiple issues |In ADC 358 | |
|SDR Transaction |associated with the content of SDR transactions|Refer to the | |
|Content/Business Rule Revisions/Clarification |and associated guidance, where applicable. |implementation schedule | |
|and Administrative Updates | |in the attachment for | |
|(SDR) (Staffed as PDC 356) | |the implementation date | |
|4/28/10 | |applicable to specific | |
|Hilert | |revisions. | |
|PRC Chair | | | |
|ADC 359, |This change request authorizes the perpetuation|Approved for |Army Concurs |
|Perpetuation of the Denial Management Code to |of existing management codes on a DLMS |implementation December | |
|the DLMS Requisition, and Modification of USAF|requisitioning transaction to indicate a denial|2010 | |
|BRAC IMSP SDR Procedures (Supply/SDR) (Staffed|has occurred on a prior requested release of | | |
|as PDC 381) |materiel purchased by the AF from DLA under | | |
|2/23/10 |BRAC SS&D IMSP business rules. | | |
|Hilert | | | |
|DLA | | | |
|ADC 360, Procedures and Content Requirements |This change establishes the DLMS Supply, |Approved for | |
|for Catalog Data Support under Navy and Marine|Storage and Distribution (SS&D) catalog data |implementation | |
|Corps BRAC (Staffed as PDC 360/360A/360B) |support procedures and transactional interface.| | |
|01/05/11 |This document consolidates the Navy and the | | |
|Hilert |Marine Corps (MC) BRAC usage which were staffed| | |
|DLA |separately. The same transaction will serve | | |
| |both the Navy and MC interfaces, but procedures| | |
| |and data content will differ. | | |
|ADC 361, |This change documents the process for a new |Approved for |Army detail comments: |
|Requirement for Exception Distribution of a |e-mail communication approach for low volume |implementation |-SCE-BTL - No system change for SCE required. |
|Minimal Content SDR via E-mail (Staffed as PDC|customers reporting supply discrepancies though| |Concur in 30 April |
|391) |a third party or otherwise lacking ability to | |2010 implementation date. |
|3/15/10 |receive encrypted SDR e-mail. | |-AMMO - concur, no ammunition impact. |
|Hilert | | | |
|PRC Chair | | | |
|Approved Addendum 361A |This addendum supplements ADC 361 adding |April 30, 2010, is the | |
|to ADC 361, Requirement for Exception |procedure documentation for encrypted FOUO |milestone date for | |
|Distribution of a Minimal Content SDR via |SDR-related e-mail and abridged SDRs/SDR |adoption of the enhanced| |
|(E-mail (Staffed as PDC 391) |replies to the DLMS manual. |controls | |
|4/06/10 | | | |
|Hilert | | | |
|PRC Chair | | | |
|ADC 362, |This change documents WAWF enhancements to the |Approved for | |
|Revised DS 856, ASN/RR: Void, Replace, |vendor submission of the ASN using the DLMS 856|implementation | |
|Change, and Contract Number Type |transaction. These changes are based upon | | |
|(WAWF/Contract Administration/Supply |three ECPs approved by the WAWF ORC and JRB for| | |
|Interface) (Staffed as PDC 359) |WAWF Release 4.2. | | |
|4/08/10 | | | |
|Hilert | | | |
|BTA | | | |
|ADC 363 |Navy modernized system development is being |Approved for | |
|Revise DS 511R, Requisition to Address |programmed to be DLMS compliant. The legacy |implementation | |
|Requirements of Navy Usage of Management Code |systems DI Code A4A Management Code needs to be| | |
|in Multiuse Field of A4_ (Referral |mapped to the 511R/Requisition transaction. | | |
|Order/Lateral Redistribution Order for Retail | | | |
|Assets) (Supply/MILSTRIP) (Staffed as PDC 402)| | | |
| | | | |
|4/13/10 | | | |
|Hilert | | | |
|Navy | | | |
|ADC 364 |The Navy is implementing ERP 1.1 starting in |Approved | |
|Revise DOD Physical Inventory Requirements to |February 2010 with rollout to storage | | |
|Allow Annual Complete Inventories as |activities scheduled for February 2011. The | | |
|Alternative to Statistical Sampling and |ERP 1.1 WM solution statistical sample | | |
|Location Survey Requirement |functionality is based on dollar value and will| | |
|5/18/10 |not meet DoD statistical sample requirements as| | |
|(Staffed as PDC 375A) |discussed during the March 25, 2009 JPWIG | | |
|Johnson |meeting (reference 3.e.). Instead of | | |
|NAVSUP |developing a new statistical sampling tool, the| | |
| |Navy would like to use the COTS functionality | | |
| |provided in SAP. | | |
|ADC 365, |This change is to improve the validation of the|Approved for | |
|DoDAAD Zip Code Validation (Staffed as PDC |CONUS city, state and zip code data by |implementation. | |
|392) |establishing procedures for DODAAC entries that| | |
|5/06/10 |do not match the USPS authoritative source. | | |
|Hammond | | | |
|PRC Chair | | | |
|ADC 366, |If DLA receives an SPR from any AF user (DoDAAC|Approved for |DLA and USAF identified an implementation date|
|New SPR Status Code to Reject USAF SPRs |beginning with an F or J), DLA shall reject the|implementation |of March 2010. |
|Submitted for Planning for PDMC Flight |SPR with the new SPR status code instructing | | |
|(Supply/MILSTRAP) (Staffed as PDC 398) |the AF submitter to contact the AF Global | | |
|4/16/10 |Logistics Support Center (AFGLSC) PDMC Flight | | |
|Johnson |Office. | | |
|DLA | | | |
|ADC 368, |This change requires assignment of Navy |Approved for | |
|Procedures and Assignment of Navy DODAACs to |(N-series) DoDAACs for DLA’s use under BRAC |implementation | |
|DLA for Use on DLA Requisitions to Military |SS&D/IMSP and documents associated procedures. | | |
|Service/GSA Sources of Supply (SoSs) in |DLA will control and assign document numbers | | |
|Support of Navy IAs under BRAC SS&D/IMSP |using these unique Navy DODAACs when | | |
|(Supply/DoDAAD) (Staffed as PDC 385) |requisitioning from other SoSs in support of | | |
|12/07/10 |Navy IA including NSYs and FRCs. This change | | |
|Hilert |establishes a new business process for Navy | | |
|DLA, J-3311 |BRAC IMSP requisitioning. It impacts DAAS | | |
| |routing rules and establishes DAAS rules for | | |
| |creation of supply and shipment status | | |
| |associated with these requisitions. Other DoD | | |
| |Components processing rules are not impacted. | | |
|ADC 369, |This change establishes alternative procedures |Approved for | |
|MOV Request Distribution Exception Rule for |for MOV requirements to support FRCs and NSYs |implementation | |
|DoD SoSs and Alternative Procedures for MOV |under a DLA IA support agreement. The change | | |
|under Navy BRAC SS&D/IMSP (Staffed as PDC 386)|also establishes a new DoD SoS requirement | | |
|6/22/10 |applicable to the determination of the MOV | | |
|Hilert |recipient under MILSTRIP. | | |
|DLA | | | |
|ADC 370, |This change provides procedures associated with|Approved | |
|Requisitioning for Off-Station Forward Site |storage and distribution of materiel associated| | |
|Support and New Non-Inventory Affecting Denial|with a forward (remote) maintenance site. | | |
|Management Code indicating Off-Station |While under DLA ownership, materiel will be | | |
|Materiel under Navy BRAC SS&D IMSP (Staffed as|physically located at the forward site, | | |
|PDC 388) |however, the accountability for the materiel | | |
|5/18/10 |will remain at the primary Distribution Depot | | |
|Hilert |which is co-located with the responsible Navy | | |
|DLA |IA. DLA will not have visibility that materiel| | |
| |is located at the forward site and may attempt | | |
| |to release the materiel for another customer. | | |
| |This change assigns a new denial management | | |
| |code for use on the Materiel Release Denial | | |
| |(945A, Document Identifier A6_) indicating the | | |
| |denial is the result of materiel being | | |
| |physically located outside the physical | | |
| |confines of the storage site to which the MRO | | |
| |was directed. | | |
|ADC 371, |This change documents multiple changes |Approved for |Marine Corps-wide DoD WebSDR routing rules |
|Marine Corps SDR Distribution Rules and Navy |applicable to preparation of SDRs. It revises |implementation. |must be available for implementation September|
|and Marine Corps SDR and SQCR Procedures and |the original PDC 387 requirement for a | |2010. Marine Corps BRAC changes must be |
|Data Content under BRAC (Supply/SDR/SQCR) |secondary document number on Navy IA SDRs using| |available October 2010. Navy BRAC changes |
|(Staffed as PDC 387A) |a different business process and requiring | |must be available December 2010. |
|8/03/10 |pre-population of the value when applicable. | | |
|Hilert |Although the requisition alert business process| |Implementation dates subsequently delayed. |
|DLA |is only applicable to the Navy, the required | | |
| |Distribution Standard System capability to | | |
| |generate customer SDRs will also be applicable | | |
| |to the MCMCs under a DLA IA support agreement. | | |
|ADC 372, Request for Discrepancy Indicator |This change request is for the assignment of a |Approved for | |
|Code to Identify 527R MRA Generated Based on |new Discrepancy Indicator code for use on DLMS |implementation | |
|“Virtual Receipt” to Support Navy BRAC |527R standard transactions indicating the MRA | | |
|SS&D/IMSP (Supply/Finance) (Staffed as PDC |is the result of a virtual receipt being posted| | |
|389) |in a Navy Maintenance system (Material Access | | |
|5/21/10 |Technology (MAT), or Material Resource Planning| | |
|Johnson |(MRP) II (MRPII)). | | |
|DLA |This change allows 527R MRA transactions which | | |
| |are generated from the Navy ‘virtual’ receipt | | |
| |process to include an MRA Discrepancy Indicator| | |
| |code to facilitate recognition by external | | |
| |parties (e.g., logistics response time (LRT), | | |
| |perfect order fulfillment (POF), etc.). | | |
|ADC 373, |This change documents requirement for |Approved for | |
|Document Process for Material Control Tracking|additional data on DLMS 527D, 527R, 940R, and |implementation | |
|(MCT) Tag Number and Revise DLMS 527D, 527R, |945A, and documents MCT process at the NYSs | | |
|940R, and 945A in Support of Navy BRAC |2005 BRAC SS&D sites. This process is used | | |
|SS&D/IMSP (Supply) (Staffed as PDC 393) |specifically at NSYs to track specific items | | |
|7/30/10 |removed from a ship to perform repairs and | | |
|Johnson |request same item be reinstalled on the ship | | |
|DLA |when repairs are completed. | | |
|ADC 374, |This change request is for modification to the |Approved for | |
|Revise DLMS 846I Asset Status Report in |current process for the DLMS 846I Asset Status |implementation | |
|Support of Navy BRAC SS&D/ IMSP (Supply) |Reporting, and for additional data elements to | | |
|(Staffed as PDC 394) |support the maintenance mission at the BRAC | | |
|6/24/10 |SS&D sites. | | |
|Johnson | | | |
|DLA | | | |
|ADC 375, |This change request is for the assignment of a |Approved for | |
|New Management Code for Navy Funded |new Management Code for use on applicable DLMS |implementation | |
|Non-Production Support Materiel Ordered under |transactions associated with requisitioning of | | |
|BRAC SS&D/IMSP (MILSTRIP/MILSTRAP Supply) |Navy-funded non-production support materiel | | |
|(Staffed as PDC 401) |ordered under DLA-Navy BRAC IMSP. The | | |
|9/15/10 |Management Code will be used to trigger special| | |
|Hilert |processing rules in DLA’s EBS. | | |
|DLA | | | |
|ADC 376, Revise DLMS 846A Asset |In support of BRAC Retail Supply, SS&D/IMSP, |Approved for | |
|Reclassification and 947I Inventory Adjustment|the Asset Reclassification transaction (DS |implementation | |
|to Support Navy BRAC SS&D/IMSP (Supply) |846A) will be used in support of three | | |
|(Staffed as PDC 376A) |independent processes to support FRCs and NSYs | | |
|9/09/10 |mission | | |
|Johnson | | | |
|DLA | | | |
|Addendum to ADC 376, |Subsequent to publication of referenced ADC |Approved for | |
|Revise DLMS 846A Asset Reclassification and |376, DLA advised that for DLA IA support |implementation | |
|947I Inventory Adjustment to Support Navy BRAC|agreement with Navy, the quantity in the 846A | | |
|SS&D/IMSP (Supply) |Asset Reclassification Request transaction will| | |
|10/20/10 |be perpetuated in the DS 846A Asset | | |
|Johnson |Reclassification Response Denial transaction. | | |
|PRC Chair |As documented in ADC 376, DS 846A did not | | |
| |authorize use of the quantity (QTY Segment) in | | |
| |response transactions. | | |
|ADC 377, |This change establishes procedures to provide |Approved for | |
|Transaction Copies Required for DLA Support of|visibility to DLA of the NSYs and FRCs-prepared|implementation | |
|Navy BRAC |requisitions for DLR, Navy program-managed | | |
|SS&D/IMSP Depot Level Reparables (DLRs), Navy |materiel, and nuclear consumable support | | |
|Program-Managed Materiel, and Nuclear |materiel requisitions, and subsequent | | |
|Consumable Support Materiel (Staffed as PDC |transactions, in support of the Navy-DLA BRAC | | |
|404) |2005 SS&D CONOPS. This change establishes a | | |
|6/23/10 |requirement for DAAS to provide a copy of | | |
|Hilert |requisition (including modification, | | |
|DLA |cancellation, and follow-ups), supply status, | | |
| |and receipt acknowledgement transactions to DLA| | |
| |based upon transaction content and prescribed | | |
| |business rules. | | |
|ADC 378, |This change request proposes adding a new |Approved for | |
|Revise DLMS 947I Inventory Adjustment to |Quantity or Status Adjustment Reason Code |implementation | |
|Identify Loss due to Destructive Test in |‘AP-Inventory Adjustment Decrease (Destructive | | |
|Support of Navy-DLA BRAC SS&D/IMSP |Test).’ for use on DLMS 947I Inventory | | |
|(Supply/Finance) (Staffed as PDC 405) |Adjustment loss (MILSTRAP DI Code D9_ | | |
|03/16/11 |functionality), to indicate that the inventory | | |
|Johnson |adjustment loss is the result of material being| | |
|DLA |destroyed in test. | | |
|ADC 379, |Preparation of supply status transactions (DLMS|Approved for | |
|New and Revised Supply Status Procedures to |870S, equivalent of MILSTRIP Document |implementation | |
|Support “Virtual Receipt” and Requisition |Identifier AE8) by DSS. This supply status | | |
|Alert Processes under Navy BRAC SS&D/IMSP |provides notification to the Navy BRAC SS&D | | |
|(Staffed as PDC 406) |sites of material upon arrival at the local DSS| | |
|6/15/10 |IA worksite and delivery when material is | | |
|Hilert |processed on a local manifest within DSS. | | |
|DLA |Creation of the new supply status for arrival | | |
| |and delivery supplements MILSTRIP requirements | | |
| |for materiel release confirmation (DLMS 945A) | | |
| |and shipment status (DLMS 856S) when directed | | |
| |release is triggered by a materiel release | | |
| |order (DLMS 940R). | | |
|ADC 381, |This change establishes additional data |Approved for | |
|Procedures and Additional Data Content |elements on multiple DLMS transactions |implementation | |
|supporting Requisitions, Requisition Alerts, |supporting the DLA interface with NSYs and FRCs| | |
|and Unit of Use Requirements under Navy BRAC |operating under the Navy-DLA BRAC 2005 SS&D | | |
|SS&D/IMSP (Supply/Finance) (Staffed as PDC |CONOPS. This is one of a series of change | | |
|366A) |proposals designed to support implementation of| | |
|07/01/10 |the Navy-DLA BRAC requirements. | | |
|Hilert | | | |
|DLA | | | |
|Approved Addendum to ADC 381A, Procedures and |This change authorizes a data field on multiple|Approved for | |
|Additional Data Content supporting Unit of Use|DLMS transactions to provide a cross reference |implementation | |
|Requirements under Marine Corps BRAC SDI |to the assigned LSN when a unit of use |approximately February | |
|(Supply/Logistics) |requirement applies to that materiel. This |2011 | |
|11/02/10 |field will be used on transactions supporting | | |
|Hilert |the interface between the DLA-operated storage | | |
|DLA |depot under DSS and the MCMC. This addendum | | |
| |supplements procedures under ADC 381 which | | |
| |remains in effect. | | |
|ADC 381B, |This administrative addendum clearly identifies|Approved for | |
|Administrative Revision to Identify Delivery |delivery location positions in the following |implementation | |
|Location Position in Transactions |DLMS Supplements: 511R, 511M, 527D, and 869F. | | |
|(Supply) | | | |
|05/06/11 | | | |
|Johnson | | | |
|PRC Chair | | | |
|Administrative ADC 382, |The current X12 code mappings for Truck and Van|Approved for | |
|Type Pack Code Conversion Guide Update |Chassis are incorrectly stated. The X12 and |implementation | |
|(Supply/Transportation) |DOD code mapping for Envelope is missing. | | |
|5/13/10 |Finally, the DOD 4000.25-M, Appendix 4 URL for | | |
|Daverede |the Type of Pack Conversion Guide needs to be | | |
|PRC |updated. | | |
|ADC 383, |This change is to implement the use of the |Phase I of the attached |Army conversion date for |
|DOD Activity Address Directory (DoDAAD) |Break Bulk Point (BBP) and Container |change to is approved |Phase 2 implementation is June 2011. |
|Container Consolidation Point (CCP) (DODAAD |Consolidation Point (CCP) data fields in the |for immediate | |
|and Supply) (Staffed as PDC 379) |DoDAAD for their intended purpose under DoDAAD |implementation. Request |Total implementation by the USAF is estimated |
|5/18/10 |reengineering, as separate, discrete data |that Components/Agencies|to be FY 2015 |
|Hammond |fields, rather than as a single, multi-use |identify the earliest | |
|DLA |field. This will require phased implementation.|implementation date for |NGA sends negative response to ADC383 |
| | |phase two to DLMSO by |specifically implementation date for |
| | |June 11, 2010. |Phase 2. NGA does not have a system that |
| | | |utilizes the BBP data field for Consolidation |
| | | |Point information. |
|ADC 384, |This change establishes Defense Logistics |Approved for |Approved DLMS Change 384 and the associated |
|Special Programs for Non-DoD/Non-Federal |Management Standards (DLMS) procedures for |implementation. |Request for Implementation Date are deferred |
|Agency Requisitioners and Administrative |Special Programs where the requisitioner is | |to allow for further evaluation before |
|Change for Contractor DoDAACs |neither a Federal Agency nor a DoD entity, and | |implementation. |
|(DODAAD/Finance/Supply) (Staffed as PDC 397) |establishes a new DoDAAC series to clearly | | |
|5/21/10 |identify such programs. | | |
|Hammond | | |DLA concurs with this ADC. Earliest |
|PRC Chair | | |implementation will likely be in FY12. |
|Deferral of ADC 384, Special Programs for |This change establishes Defense Logistics | |Navy cannot give an implementation date for |
|Non-DoD/Non-Federal Agency Requisitioners and |Management Standards (DLMS) procedures for | |this ADC. We are in the midst of our |
|Administrative Change for Contractor DoDAACs |Special Programs where the requisitioner is | |protracted ERP implementation and it is quite |
|(DODAAD/Finance/Supply) (Staffed as PDC 397) |neither a Federal Agency nor a DoD entity, and | |probable that this ADC will require us to make|
|6/01/10 |establishes a new DoDAAC series to clearly | |some ERP changes. AT the moment, our |
|Hammond |identify such programs. | |functional and technical resources that need |
|PRC Chair | | |to do the in depth analysis on the ADC are |
| |Approved DLMS Change 384 and the associated | |tied up with the implementation. |
| |Request for Implementation Date are deferred to| | |
| |allow for further evaluation before | | |
| |implementation. | | |
|ADC 384A, |This amends ADC 384 to establish DLMS |Approved for | |
|Special Programs for Non-DoD/Non-Federal |procedures for additional Special Programs in |implementation. | |
|Agency Requisitioners; Additions in Support of|support of DLA RBI, where the requisitioner is | | |
|DLA Disposition Services Under Reutilization |neither a Federal Agency nor a DoD entity. This| | |
|Business Integration (RBI) (DoDAAD and Supply)|change establishes DoDAAC series to clearly | | |
|(Staffed as Proposed Addendum 456 to ADC 384) |identify such programs. | | |
|04/07/11 | | | |
|Hammond | | | |
|DLA Disposition Services | | | |
|ADC 385, |This change is to designate query and download |Approved for | |
|DoD Activity Address Directory (DoDAAD) |of information for multiple DoDAACs from the |implementation. | |
|Enhanced Inquiry and Download for Multiple |eDAASINQ web site as “For Official Use Only. | | |
|DoDAACs (DODAAD) | | | |
|5/21/10 | | | |
|Hammond | | | |
|PRC Chair | | | |
|ADC 386, |The requested requirements are critical for use|DoD WebSDR will be | |
|Revised Data Content for DLMS Inventory |in MEBS because they aid in identifying the |available to support the| |
|Adjustment and Supply Discrepancy Report (SDR)|correct products currently in inventory. |new data requirement by | |
|Supporting Mapping Enterprise Business System |Products are receipted in inventory in DSS |December 2010. | |
|(MEBS) and National Geospatial-Intelligence |using the required data fields and are to be | | |
|Agency (NGA) Product Code Value Update |passed from DSS to MEBS and vice versa. Any or| | |
|(Staffed as PDC 396) |all of the fields may appear on the product for| | |
|5/21/10 |unique identification. The most current | | |
|Hilert |Geospatial Information and Services (GI&S) | | |
|DLA |products may not be issued due to the required | | |
| |data not being received in DLMS format. | | |
|ADC 387, |Documents and highlights DLMS |Approved for | |
|DLMS Enhancement: DS 846A Asset |transaction/capability which provides means for|implementation | |
|Reclassification Transaction and Associated |ICPs to direct storage activities to reclassify| | |
|Procedures, and Administrative Update to DS |material from one SCC to another SCC. | | |
|947I Inventory Adjustment (Supply) (Staffed as| | | |
|PDC 408) | | | |
|07/02/10 | | | |
|Johnson | | | |
|PRC Chair | | | |
|ADC 388, |This change request is for the use of |Approved for | |
|Automated Method of Detecting System Downtime |Requisition Inquiry (DLMS 869A/AF1) and Supply |implementation | |
|or Excessive Processing Times in USAF BRAC |Status (DLMS 870S/AE1) transactions in order to| | |
|SS&D/IMSP Expedited Requisition Process and |determine whether data systems are processing | | |
|Associated Dual Function Materiel Release |USAF BRAC SS&D/IMSP expedited requisitions | | |
|Order (MRO) Process (Staffed as PDC 407) |within the required timeframe. When excessive | | |
|Hilert |processing time is detected a unique dual | | |
|USAF |function MRO process will be initiated. A new | | |
| |Downtime Detection Indicator and business rules| | |
| |are established for this process. This | | |
| |proposal also documents the dual function MRO | | |
| |used by the AF to issue DLA assets to the AF | | |
| |(recorded on a post-post MRO requisition) and | | |
| |immediate issue of these assets as AF-owned to | | |
| |the maintenance unit. | | |
|ADC 389, |This proposed change documents an alternative |Approved | |
|Inventory Control Point /Integrated Item |process for providing GFM to contractors | | |
|Manager (ICP/IMM)-Directed Shipments of |without initializing the requirement via a | | |
|Non-Requisitioned Government Furnished |requisition. Under this process materiel is | | |
|Materiel (GFM) (Staffed as PDC 383) |“pushed” from the supply system rather than the| | |
|8/03/10 |“pulled” per current MILSTRIP procedures. | | |
|Hilert | | | |
|DLA | | | |
|ADC 390, |The 527R transaction had no requirement for the|Approved for | |
|Revise DLMS 527R MRA and Receipt Functions to |contractor that uses GFM or CFM/CAP to cite the|implementation | |
|Require the DOD Contract Number for |contract number (and call/order number when | | |
|Transactions Associated with GFM, and for MRA |applicable) of the contract that authorized the| | |
|Associated with CFM (Supply and Contract |use of the GFM (in the MRA or, for Navy CAV, | | |
|Administration) (Staffed as PDC 374) |the receipt) or purchase of CFM/CAP from | | |
|01/28/11 |Government supply sources (for MRA only). This| | |
|Johnson |limitation was based on the requirements | | |
|OSD/DPAP/PRC Chair |established under the constraints of the 80 | | |
| |record position MILSTRAP DI Code DRA MRA | | |
| |transaction format and MILSTRAP DI Code D6_ | | |
| |Receipt transaction format. This change now | | |
| |requires inclusion under DLMS of the DoD | | |
| |contract number and associated call/order | | |
| |number, when applicable, authorizing GFM for | | |
| |MRA and Receipt transactions, and the DoD | | |
| |contract number, and associated call/order | | |
| |number, when applicable, authorizing CFM for | | |
| |MRA. | | |
|ADC 391, |This change request authorizes the use of a new|Approved for | |
|New Denial Management Code to Support the New |management code on the DLMS 945A, Material |implementation | |
|Protection |Release Denial, indicating a denial has | | |
|Process at the Navy Shipyards (NSYs) when |occurred on a request for a Navy Shipyard (NSY)| | |
|Protection Document Number/Job |maintenance customer. | | |
|Order does not Match DSS Records under BRAC | | | |
|SS&D/IMSP (Staffed as PDC 412) | | | |
|8/10/10 | | | |
|Hilert | | | |
|DLA | | | |
|ADC 392, |This change is to remove the manual setting of |Approved for | |
|DOD Activity Address Directory (DoDAAD) |the flag for CONUS or OCONUS data field in the |implementation | |
|Setting the CONUS/OCONUS Indicator (Staffed as|construction of DoDAACs and to set the flag | | |
|PDC 411) |programmatically based on the TAC 2 address or | | |
|8/03/10 |the TAC 1 address if no TAC 2 address is | | |
|Hammond |entered. An alternative considered was to | | |
|PRC Chair |remove the field from the DoDAAD, if it serves | | |
| |no purpose; however, it was determined in | | |
| |staffing that the indicator has value and | | |
| |should be retained. | | |
|ADC 393, |This change recognizes the requirement to carry|Approved for | |
|Revise DLMS 846P, Response to Transaction |2 Type Physical Inventory/Transaction History |implementation | |
|History Request When No History Available, to |Codes in 846P when it is used as a “Response to| | |
|Add a Second Iteration of Type Physical |Transaction History Request (No History | | |
|Inventory/Transaction History Code (Supply) |Available)”. DLA requests an optional second | | |
|(Staffed as PDC 416) |iteration of 2/LQ01/270 with qualifier FC which| | |
|8/04/10 |is intended be used to cite the type of | | |
|Johnson |transaction history code which appeared on the | | |
|DLA |associated Transaction History Request, in | | |
| |addition to code value 8 or 9. | | |
|ADC 394 |This change corrects a problem with the last |Approved for | |
|DOD Activity Address Directory (DoDAAD) |line of the overseas address lines for Canada |implementation | |
|Overseas Address Line Change for Canada and |and Mexico. | | |
|Mexico (DoDAAD and Supply) (Staffed as PDC | | | |
|413) | | | |
|8/17/10 | | | |
|Hammond | | | |
|PRC Chair | | | |
|ADC 395, |To authorize the use of supply status code “BX”|Approved for |CMOS is targeting calendar year 2012 for |
|Request for New Transportation Activity |to report property that has not arrived at the |implementation |implementation of this approved change. |
|Processing Supply Status Code |servicing transportation activity, but the | | |
|(Supply/Transportation) |prepositioned data has been received via DS | | |
|(Staffed as PDC 410) |940R, Materiel Release, transaction from | | |
|9/01/10 |supply. | | |
|Daverede | | | |
|USAF | | | |
|ADC 396, Revised Procedures and Data Content |This change proposes new procedures and updates|Approved for | |
|for DLMS Materiel Release Order (940R) and |the DLMS Material Release Order (DS 940R) and |implementation | |
|Material Release Advice ((945A) and New Denial|Material Release Advice (DS 945A) between the |approximately February | |
|Management Code for Marine Corps BRAC SDI |MCMC and DLA Depots operating under the DSS. |2011. | |
|(Staffed as PDC 422) (Supply/Logistics) | | | |
|10/06/10 | | | |
|Hilert | | | |
|DLA | | | |
|ADC 397, |During recent passive RFID (pRFID) testing by |Approved for | |
|Deletion of the Passive RFID Reader ID Number |the IDE-GTN Convergence (IGC) program, test |implementation | |
|from the Reader Registration Table |personnel identified a conflict in the test | | |
|(Supply/Transportation/AIT) (Staffed as PDC |transaction data and the published DLMS | | |
|418) |guidance regarding pRFID data requirements for | | |
|10/26/10 |the standard XML pRFID schema. Subsequent | | |
|Daverede |research determined that the DLMS manual | | |
|PRC Chair |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. | | |
|ADC 398, |The DS 846A Asset Reclassification transaction |Approved for | |
|Revise DLMS 846A Asset Reclassification, 947I |will be used in support of Marine Corps and DLA|implementation | |
|Inventory Adjustment, and Associated |re-identification of assets to support less | | |
|Procedures to Support Marine Corps BRAC |than unit of issue functionality at the Marine | | |
|Storage and Distribution Interface (Supply) |Corps Maintenance Centers (MCMC). | | |
|(Staffed as PDC 421) | | | |
|10/20/10 | | | |
|Johnson | | | |
|DLA | | | |
|ADC 399, |1. This change provides clarification and |Approved for phased |The DLA Distribution timeline for ADC 399 |
|Automated Data Capture for Serialized Item |enhanced procedures supporting automated data |implementation. |change is estimated for FY 12 to be included |
|Shipments and Preparation of the Issue |capture in association with the preparation of | |in Distribution Standard System 12.2 release. |
|Release/Receipt Document (IRRD) (DD Form |the DD Form 1348-1A or DD Form 1348-2. | |Components are requested to share |
|1348-1A or DD Form 1348-2) Continuation Page |2. This change establishes a mandatory | |implementation schedules with the DLA |
|(MILSTRIP/ SUPPLY) (Staffed as PDC 377) |continuation page for the DD Form 1348-1A or DD| |Logistics Management Standards Office. |
|03/18/11 |Form 1348-2 when used for serialized item | | |
|Hilert |shipments as required by DOD or intra-Component| | |
|HQMC/J627/USTRANSCOM |policy or for Unique Item Tracking (UIT). The | | |
| |continuation page contains machine readable bar| | |
| |code symbols for the encoded content | | |
| |information to include the serial numbers and | | |
| |unique item identifiers (UII). | | |
| |3. This change also removes optional use of the| | |
| |Automated Packing List (APL) in association | | |
| |with MILSTRIP. There are no known systems that| | |
| |use the MILSTRIP APL. | | |
|ADC 402 |This change provides new procedures and updates|Approved for | |
|Revise DLMS 947I Inventory Adjustment |to a DLMS |implementation | |
|Transaction and |transaction to communicate DS 947I Inventory | | |
|Associated Procedures to Support Marine Corps |Adjustment Quantity or Status Adjustment Reason| | |
|BRAC Storage and Distribution Interface |(QSAR) Code ‘AG-Ownership Change’ for a new | | |
|(Supply) (Staffed as PDC 423) |(second) purpose specific to USMC BRAC to | | |
|10/29/10 |identify a gain or loss resulting from | | |
|Hilert |ownership change associated with | | |
|DLA |re-warehousing. This ownership change can be | | |
| |requested by the Marine Corps or can occur as a| | |
| |result of material identified as discrepant | | |
| |upon receipt. | | |
|ADC 403, Administrative Update to Identify |This administrative change updates the DOD |Approved for publication| |
|MILSTRAP Transactions Authorized for Reversal |MILSTRAP (AP3) Introduction to identify in a |in the next reissuance | |
|(Supply/MILSTRAP) |single list, all MILSTRAP transactions that are|of MILSTRAP | |
|04/25/11 |authorized for reversal. Currently to | | |
|Johnson |determine if a MILSTRAP transaction can be re | | |
|PRC Chair |reversed, you must review the AP3 format for a | | |
| |given transaction, and check to see if the | | |
| |quantity field in that format references the | | |
| |AP3 footnote for reversal. This change clearly| | |
| |identifies all transactions authorized for | | |
| |reversal in once place for easy reference and | | |
| |information. This change also incorporates | | |
| |portions of AMCL 13 in the AP3 Introduction. | | |
| |AMCL 13 is not yet published in MILSTRAP | | |
| |because a joint implementation date for use of | | |
| |partial reversals addressed by AMCL 13 was | | |
| |never established. However, the section of | | |
| |AMCL 13 documenting information about the | | |
| |structure of the MILSTRAP reversal indicator | | |
| |used in place of the former “11-zone overpunch”| | |
| |can be published. | | |
|ADC 404, |Revise DoD 4000.25-M, DLMS, and DoD |Approved for | |
|Revision to Small Arms and Light Weapons |4000.25-2-M, MILSTRAP (references 4.a. and 4.b.|implementation | |
|Procedure to Address Reporting Foreign Weapon |respectively) to: | | |
|Serial Numbers and Definition Updates |Provide the procedures for assignment of serial| | |
|(Supply/MILSTRAP) (Staffed as PDC 326) |numbers for foreign weapons with unrecognizable| | |
|12/09/10 |serial number characters. | | |
|Madrigal |Revise the definitions to reflect “Small Arms | | |
|PRC Chair |and Light Weapons” in place of “Small Arms” | | |
| |where needed, and clarify that the SA/LW | | |
| |Active, Inactive and History registry files | | |
| |apply to both the DoD and Component registries.| | |
|ADC 405, |With the implementation of the Expeditionary |Approved for | |
|DLMS Mapping for USAF Unique Transactions Used|Combat Support System (ECSS), the AF is |implementation | |
|between USAF Locations and Expeditionary |eliminating the need for some AF unique |approximately February | |
|Combat Support System (ECSS) (Supply) (Staffed|transactions. This request establishes DLMS |1, 2011 | |
|as PDC 427) |mapping for unique AF transactions used between| | |
|12/28/10 |AF locations and ECSS: | | |
|Hilert |The BF7, Follow-up by ICP to Shipping Activity,| | |
|AF/A4IT |transaction is used by the AF ICP to request | | |
| |status on a Redistribution Order (RDO) shipment| | |
| |request sent to an internal AF storage location| | |
| |or an AF base retail activity. | | |
| |The BL0, Redistribution Order Shipment | | |
| |Confirmation, transaction provides the shipment| | |
| |details to the AF ICP | | |
| |The B7A, Redistribution Order Denial, | | |
| |transaction informs the AF ICP of the RDO | | |
| |denial. | | |
|ADC 406, |The DoDAAD database contains some unused |Approved for | |
|DoDAAD Removal of Unused Fields (DoDAAD and |fields, which leads to confusion in the user |implementation | |
|Supply) (Staffed as PDC 426) |community. This Change corrects the problem by | | |
|01/31/11 |removing the unused fields. | | |
|Hammond |-The Delete Indictor field has been removed in | | |
|PRC Chair |the ADC because it was determined during | | |
| |staffing that the Delete Indictor is used and | | |
| |supported by DLA Transaction Services. The | | |
| |“Distribution” field is not currently used, but| | |
| |its potential use is under review, so it will | | |
| |not be deleted. | | |
|ADC 407 |This change will allow for the inclusion of UII|Approved for | |
|Requirements for Unique Item Tracking (UIT) in|and/or Serial Number data in DLMS 870S |implementation | |
|the DLMS Supply Status (870S) Supporting the |transactions in support of the supply | | |
|Cargo Movement Operations System (CMOS) |transportation interchange. The supply status| | |
|Interface (MILSTRIP/Supply/Transportation |applicable to this change is generated by ILS-S| | |
|Interchange) |(USAF retail supply system). | | |
|12/127/10 |-The PDC authorizes the generation of an | | |
|Hilert |information copy of the 870S to satisfy a | | |
|USAF |specific USAF PIC NWRM need. | | |
|ADC 408 |This change is to correct the DAASINQ display |Approved for | |
|DOD Activity Address Directory (DoDAAD) |for RIC query results. |implementation | |
|DAASINQ RIC Display | | | |
|12/21/10 | | | |
|Hammond | | | |
|PRC Chair | | | |
|ADC 409, |DLA Disposition Services requires the use of a |Approved for | |
|Intra-DLA Revisions to DLMS 867I Issue and |unique number to support the grouping of |implementation | |
|Associated Procedures to Support Relocation of|property relocated during the disposal process.| | |
|Material between DLA Disposition Services |The unique number, the Disposal Consolidation | | |
|Field Offices under Reutilization Business |Number, is a 10 digit number with positions 1-3| | |
|Integration (RBI) (Supply) |equal to the DLA Disposition Service Field | | |
|2/14/11 |office RIC and positions 4-10 equal to a unique| | |
|Johnson |alphanumeric serial number. A separate | | |
|DLA |qualifier is being requested so that the DCN | | |
| |can be uniquely identified on the 867I Issue | | |
| |transaction. | | |
| |Since the document number for the transaction | | |
| |will become part of a consolidated RDO, DLA | | |
| |Disposition Services will also require the | | |
| |perpetuation of the original DTID, as a | | |
| |secondary number in the transaction, to support| | |
| |identifying inventory at a level lower than the| | |
| |document number or DCN. Therefore, the DTID | | |
| |number will be included on each individual | | |
| |issue transaction under this process. | | |
|ADC 410, |This change covers modifications to the 527D |Approved for | |
|Intra-DLA Revisions to Procedures and DLMS |PMR (also known as Advance Receipt Information |implementation | |
|527D Pre-Positioned Materiel Receipt (PMR) to |(ARI) in DLMS). With the inclusion of the RBI | | |
|Add Disposition Container ID for use with |functionality in DSS and EBS, the 527D PMR | | |
|Relocation of Material between DLA Disposition|transaction needs to be updated to include | | |
|Field Offices Under Reutilization Business |passing of Disposition Container Identification| | |
|Integration (RBI) (Supply) (Staffed as PDC |(ID). | | |
|433) | | | |
|2/25/11 | | | |
|Johnson | | | |
|DLA Disposition Services | | | |
|ADC 411, |To establish procedures for the originating |To facilitate a | |
|Update Functionality for DLMS 856S Shipment |activity (RIC From) to generate an update to |coordinated | |
|Status and DLMS 945A Material Release Advice |the DLMS 856S, Shipment Status, and the DLMS |implementation by | |
|(Supply/AIT) (Staffed as PDC 444) |945A, Material Release Advice (Material Release|impacted systems, DLA | |
|04/12/11 |Confirmation) in the event the outbound |Transaction Services | |
|Daverede |shipment details change from what was |will implement the | |
|DLA Distribution J4 |originally transmitted to DLA Transaction |modified transaction | |
| |Services for routing to designated status |maps on July 15, 2011. | |
| |recipients. |Systems are requested | |
| | |not to implement prior | |
| | |to this date. | |
|ADC 414, |DOD Inspector General (IG) Report D-2008-090, |Approved for |This change will be published in the next |
|Revisions to DLMS and MILSTRAP Procedures to |Controls Over Reconciling Army Working Capital |implementation |reissuance of the MILSTRAP and DLMS manuals, |
|Address Owner/Manager Research of Inventory |Fund Inventory Records (reference 3a), | |which are anticipated for publication in |
|Adjustments (Accounting Error) (MILSTRAP |contained recommendations for establishing | |Calendar Year 2011. |
|D8B/D9B, DLMS 947I) (Supply/MILSTRAP) (Staffed|requirements for owners/managers to research | | |
|as PDC 341A) |Inventory Adjustments (Accounting Error) | |USAF: Earliest date AFMC could comply with |
|03/28/11 |transactions (DS 947I with Quantity or Status | |requirement is estimated at mid-2014. |
|Johnson |Adjustment Reason Code ‘AB’; or MILSTRAP | | |
|PRC Chair |Document Identifier (DI) Code D8B/D9B). The | | |
| |overall objective of the report is to bring | | |
| |owners/managers research requirements for | | |
| |Inventory Adjustments (Accounting Error) | | |
| |Transactions in line with the storage | | |
| |activities research requirements for physical | | |
| |inventory adjustment (DS 947I with Quantity or | | |
| |Status Adjustment Reason Code ‘AA’ ; MILSTRAP | | |
| |DI Code D8A/D9A). The research requirements | | |
| |are published in DLMS Vol. 2, Chapter 6 | | |
| |(reference 3b) and MILSTRAP Chapter 7 | | |
| |(reference 3c). | | |
|ADC 417, |To establish procedures for use of the DS 856S,|Approved for | |
|Shipment Status for Local Delivery Manifested,|Shipment Status, to document the application of|implementation | |
|Outbound MILS Shipments on Behalf of On-Base |pRFID tagging for shipments that are either | | |
|Customers, Re-Warehousing Actions between |local delivery manifesting to base customers, | | |
|Distribution Depots, and non-MILS Shipments to|outbound MILS shipments on behalf of on-base | | |
|Off-Base Customers, with Passive Radio |customers, re-warehousing | | |
|Frequency Identification (RFID) |actions/transshipments between Distribution | | |
|(Supply/Transportation/AIT/SDR) (Staffed as |Depots in support of ‘Home’ Industrial Activity| | |
|PDC 424) |site and ‘Forward Support’ Industrial Activity | | |
|04/26/11 |site material requirements, or outbound | | |
|Daverede |non-MILS shipments (e.g., DD1149) to off-base | | |
|DLA Distribution J4 |customers. Implementing pRFID tagging on these| | |
| |shipments will provide enhanced intransit | | |
| |visibility and enable use of pRFID tag reads to| | |
| |trigger the automated receiving business | | |
| |processes/transactions at the customer | | |
| |location. | | |
|ADC 418, |To modify the definition and usage of Advice |Approved for | |
|Advice Code 2W for Free Issue |Code 2W restricting to Navy and Marine Corps |implementation effective| |
|(MILSTRIP/Supply) |only. Under MILSTRIP, this code was |immediately | |
|(Staffed as PDC 428) |originally authorized for FMS customers only. | | |
|04/06/11 |However, DAAS history from 2007 to present | | |
|Hilert |shows no Security Assistance requisitions | | |
|NAVSUP-E |citing Advice Code 2W. Army customers appear | | |
| |to be using the code (plus USCG requisition in | | |
| |2007). All Components (including | | |
| |International Logistics Control Offices (ILCOs)| | |
| |and the Defense Security Cooperation Agency | | |
| |(DSCA) were asked to verify if there is a | | |
| |continued requirement for the use of Advice | | |
| |Code 2W for Military Assistance | | |
| |Program/Military Assistance Service Funded | | |
| |(MAP/ MASF). | | |
|ADC 420, |Remove code value ‘UID’ and associated guidance|Approved for | |
|Administrative Update to Eliminate Unique Item|from the UITDC. |implementation | |
|Tracking Designator Code Value 'UID' in Favor | | | |
|of New FLIS Cataloging Code for Item Unique | | | |
|Identification (IUID) under Serialized Item | | | |
|Management (SIM) | | | |
|(Not Staffed as a PDC) | | | |
|04/05/11 | | | |
|Johnson | | | |
|PRC Chair | | | |
|ADC 424, |This change approves interim and longer term |Approved for | |
|DOD Activity Address Directory (DoDAAD) |procedures to correct inconsistent Break Bulk |implementation | |
|Modification to Break Bulk Point (BBP) |Points (BBPs) for TAC1 and TAC2 addresses. | | |
|(DoDAAD/Supply) (Staffed as PDC 443) | | | |
|05/09/11 | | | |
|Hammond | | | |
|PRC Chair | | | |
|ADC 426, |Revise the DLMS to allow for the identification|Approved for |Implemented by DLA Transaction Services |
|Intra-Navy DLMS 511R, Requisition, Inclusion |of the desired storage activity from which the |implementation | |
|of Requested Storage Activity |requisitioned item is to be supplied. This | | |
|(Supply/MILSTRIP) (Staffed as PDC 461) |change will be adopted as an intra-Navy DLMS | | |
|05/10/11 |enhancement in support of organic maintenance | | |
|Hilert |requisitioning procedures associated with | | |
|PRC Chair |Project Code Z5X | | |
|ADC 428, |The MDA is soon to be established as an |Use of the assigned | |
|Support to Missile Defense Agency (MDA) as a |Implementing Agency (IA) for Foreign Military |Service/Agency Code “I” | |
|Foreign Military Sales (FMS) Implementing |Sales related to a new weapon system and |is contingent upon | |
|Agency (IA) and Assignment of New Service and |support parts. In order for standard |signed MDA Foreign | |
|Agency (S/A) Code “I” (Staffed as PDC 446) |logistics systems to recognize transactions |Military Sales case | |
|5/23/11 |associated with MDA FMS, a new Service and |designating MDA as the | |
|Hilert |Agency (S/A) Code to identify “MDA - Security |implementing agency. | |
|MDA |Assistance Only” will be established under this|Estimated implementation| |
| |change proposal. The new S/A Code will allow |date is 1st quarter FY | |
| |tracking and independent processing for MDA, |12. | |
| |which is currently using Army systems for | | |
| |support | | |
|ADC 428A, |This addendum is provided to make |Estimated implementation| |
|Support to Missile Defense Agency (MDA) as a |administrative corrections to the approved |date is 1st quarter FY | |
|Foreign Military Sales (FMS) Implementing |change documentation and document additional |12. | |
|Agency (IA) and Assignment of New Service and |requirements for new distribution code and fund| | |
|Agency (S/A) Code “I” |codes to support MDA as an IA. | | |
|(MILSTRIP/MILSBILLS/SDR/Supply) | | | |
|06/09/11 | | | |
|Hilert | | | |
|MDA | | | |
|ADC 430, |Establish an exception to the 45 day |Approved for immediate | |
|Timeframe Change for Security Assistance (SA) |reconsideration timeframe for FMS customers who|implementation | |
|Supply Discrepancy Report (SDR) Requests for |are receiving a returned exhibit item as a | | |
|Reconsideration |result of their previous SDR submission. This | | |
|06/13/11 |change will re-instate the 90 day | | |
|Hilert |reconsideration timeframe where | | |
|PRC Chair |materiel/exhibits must be returned to the | | |
| |customer, thereby allowing additional time for | | |
| |the return-to-customer transportation and the | | |
| |customer’s re-evaluation of their returned | | |
| |property. | | |
|ADC 433, |Add the estimated shipment date in the DS 856S |Approved for | |
|Requirements for Estimated Shipment Date in |(DIC AS3) Shipment Status transaction. When |implementation effective| |
|the DLMS Shipment Status (856S) (Supply) |the 856S (AS3) contains an estimated shipment |90 days from published | |
|(Staffed as PDC 457) |date it will not contain the actual carrier |date of 06/24/11. | |
|06/24/11 |release date or mode of shipment. |- The delay is to enable| |
|Daverede | |synchronized | |
|Air Force |ILS-S will implement a system change to ensure |implementation by | |
| |the 856S contains the unit price. |impacted systems with | |
| | |DLA Transaction | |
| | |Services. | |
|MILSTRIP Interim Change 94-2 |Provides the procedures necessary to effect | |Published in MILSTRIP Formal Change 8 |
| |lateral redistribution of retail assets as | |(5/18/95) |
| |directed by the integrated material manager. | | |
| | | |USA 12/04 |
PART IV – INACTIVE/HOLD/WITHDRAWN CHANGES
|PROPOSED/APPROVED CHANGE NO. | |REPLY STATUS |
|TITLE |BRIEF DESCRIPTION | |
|DATE ISSUED |OF CHANGE | |
|ACTION OFFICER | | |
|PDC ORIGINATOR | | |
| | |REC’D FROM |COMMENT |
|PDC 29 |Provides instructions for use of PD. Specifically addresses | |On hold. |
|Requisition Priority Designator (PD) Validation|requisitioning in support of deployed or off-station F/AD I | |AF implementation under DLSS not |
|(Supply/MILSTRIP) |units. | |feasible. Proposal to be reworked for |
|3/10/99 | | |DLMS implementation. |
|Hilert | | | |
|PRC Chair | | | |
|Withdrawal of RFID ADC 39, Special Program |The ADC 39 requirement was intended to allow DOD 4000.25-2-M, |N/A |Withdrawal of ADC 39 was discussed at |
|Requirements (SPR) Process Use of Reject Status|MILSTRAP, reject transaction codes to be used with SPR Status | |Supply PRC meeting 07-02 in October |
|Codes (Supply/MILSTRAP) |transactions, to facilitate SPR rejection for Service legacy | |2007, and DLA, which originated this |
|2/13/08 |systems that had not fully implemented the MILSTRAP Document | |change, subsequently confirmed that |
|Johnson |Identifier Code DZG Reject transactions with the SPR process. | |the requirement could be withdrawn. |
|DLA | | | |
|Revised RFID Proposed MILSTRIP Change 40 | | |Withdrawn – See ADC 57 |
|Processing Cooperative Logistics Supply Support| | | |
|Arrangement (CLSSA) Requisitions | | | |
|PDC 62 |This change reduces or eliminates DAASC mailing of transactions| |DAASC will phase out mailers as |
|Proposed Change to the DAASC Mailing Process |related to MILSTRIP and MILSBILLS processes. | |alternatives are adopted and identify |
|3/31/00 | | |high volume activities for review. |
|Hilert | | | |
|DAASC | | |11/23/05 - USASAC concurs with the |
| | |USASAC |proposal to adopt the terminate |
| | | |default option for DAASC mailings to |
| | | |Army FMS customers. This methodology |
| | | |already used by AF; awaiting response |
| | | |from Navy (follow-up to Navy |
| | | |11/27/06). |
|PDC 98 |The MILSTRIP/DLMS revision is minimal and consists only of | |On hold pending USTRANSCOM further |
|Clarification of Transportation Control Number |providing clarification to the entry instructions for the TCN | |research. |
|Usage for Modes 9 and X |field. The substantive change required to support this revision| | |
|(Supply/Transportation/ MILSTRIP) |must be accomplished in the MMR and the DTR. Exclusions by mode| | |
|02/04/03 |of shipment are not recognized. This change would allow for | | |
|Hilert |optional assignment of the TCN for modes 9 and X. | | |
|DLA | | | |
|PDC 103 |This change proposes reassigning the use of Service Code V, in | |Published as ADC 102 February 12, 2009|
|Revised Service Code V Use (Supply/MILSTRIP) |record positions 4, 67, and 74 to the Navy (designating the | | |
|April 30, 2003 |start of the Routing Identifier field in MILSTRIP and MILSTRAP | | |
|Hilert |logistics transactions). V is currently assigned to NASA. | | |
|NAVICP | | | |
|PDC 108 |This change requires mandatory identification of the CIIC on | |Withdrawn by DRMS |
|Mandatory Identification of CIIC on Transfers |the Defense Turn-in Document (DTID), DD Form 1348-1A or DD Form| | |
|to DRMO |1348-2. | | |
|(Supply/MILSTRIP) |Additionally, the heading for block 9 is revised and | | |
|07/24/03 |instructions for block 15 are updated. | | |
|Hilert | | | |
|DRMS-BA | | | |
|PDC 141 |This change creates two new DLMS transactions for the |GSA |Concur w/comment |
|DSs– 846M Supply Support Request Information |inter-Component Integrated Material Management (provisioning | | |
|and 846O Supply Support Output Information |support) program to submit supply support information and its | |TABLED – Awaiting confirmation of |
|(Logistics) |related output (supply support output information consisting of| |requirement for DLMS format. |
|10/06/04 |interim advice, accept, reject, reply to offer, follow-up, and | | |
|Hilert |reply to follow-up messages). | |Supply Support Request Work Group |
|DLA | | |convened January 16-17, 2008. |
| | | |Redesign/enhancement of business |
| | | |process and transactions under |
| | | |consideration. |
|Proposed Addendum for ADC 142A |This change forwards the 856A Due-In Data Maintenance designed | |OBE - Effective January 2006, the DTEB|
|856A Due-In Data Maintenance - Shipment Notice |to replace the DS 856SC established under ADC 142. The | |Committee approved changes to the |
|for Shipments to a CCP |attachment | |existing 856A IC to support the |
|11/16/05 |is the format used for coordination of the 856A revisions by | |migration of the legacy MILS |
|Hilert |the Defense Transportation EBusiness (DTEB) and has been | |CDP/CDF/CDY/CBF transactions into EDI |
|DLA/ |provided to the Supply PRC for comment. | |and to support the implementation of |
|TRANSCOM | | |passive RFID into Due-in Notices |
|PDC 271 |This change accommodates the Army’s LMP requirement for |Army |Placed on hold by submitter - awaiting|
|DLMS Mapping for Army Electronic Product |receiving requisition exception data from the AEPS system. | |update |
|Support (AEPS) Requisition Exception Data |This change modifies the DLMS 511R to transmit the data content| | |
|(Supply) |of the AEPS generated requisition exception data and format. | |Placed on hold/deferred - as of |
|7/12/07 | | |6/13/08 |
|Hilert | | | |
|Army LMP | | | |
|PDC 176, |Requires mandatory identification of four-digit packaging | |USAF requests application to non-USAF |
|Mandatory Identification of Detail Level |discrepancy sub-codes in the DoDWebSDR system. This change | |customers – resolution pending. |
|Packaging Discrepancy Codes for USAF DOD WebSDR|only applies to direct web input by USAF submitters | | |
|Users (SDR/Supply) | | |To be modified and re-staffed per SDR |
|6/28/05 | | |Mtg 06-1 - Delayed as low priority |
|Hilert | | |change |
|USAF | | | |
|PDC 176A, |This change establishes a mandatory requirement for the |DSCC-BAOA |Concurs |
|Mandatory Identification of Four-Character |applicable four-position packaging discrepancy subcodes when | | |
|Packaging Discrepancy Codes (Supply/Supply |packaging discrepancies are reported using a phased | |Tabled pending completion of higher |
|Discrepancy Report (SDR)/Storage Quality |implementation approach. | |priorities. |
|Control Report (SQCR/DD 1225)) | | | |
|6/24/08 | | | |
|Hilert | | | |
|USAF | | | |
|PDC 183 |Requests a new Discrepancy Code to accommodate situations where|DLA |DLA |
|Withdrawal of New Supply SDR Discrepancy Code |the shipping discrepancy was caused by a customer |DSCA |Concur |
|(W7) to Identify Shipping Discrepancies due to |requisitioning error. |USA |Nonconcur |
|Customer Requisitioning Error (Supply/SDR) | | | |
|7/05/05 | | |Withdrawn by Submitter |
|Hilert | | | |
|DLA/J-3731 | | | |
|PDC 193 |Abolishes current and all future version/release restrictions |DSCA |Concurs |
|DLMS Unit of Issue and Purchase Unit (UI/PU) |for ASC X12 unit of measure codes used by DLMS for conversion |USTRANSCOM |Negative comments |
|Conversion Guide |to DOD unit of issue and purchase unit. | | |
|(Supply/Logistics, Procurement, Contract | | | |
|Administration, | | |Controversial issue - On hold pending |
|Distribution, Supply Discrepancy Report, | | |resolution of comments |
|Transportation) | | | |
|10/24/05 | | |Concept reworked - refer to PDC 274 |
|Hilert | | | |
|PRC Chair | | | |
|PDC 203 |This change establishes a new combination Advice Code for 2G | |Withdrawn for rework by Navy and DoD |
|New Advice Code for the Combination of 2N |and 2N. | |Shelf-life Committee |
|(Continuous Length) and 2G (Shelf Life) Advice | | | |
|Codes (Supply) | | | |
|3/20/06 | | | |
|Hilert | | | |
|Navy | | | |
|PDC 431 |With the addition of DLA Disposition Services business |Defense |Officially Withdrawn by submitter on |
|Revises DLMS Supplements 140A, Small Arms & |processes into the DSS system, data elements and transaction |Logistics Agency|01/24/11 |
|Light Weapons (SA/LW) Reporting, 888A, Small |information needs to be introduced in a DLMS transaction to |Disposition | |
|Arms & Light Weapons (SA/LW) Data Change in |provide the DLA Disposition Services customers a means to |Services | |
|Support of RBI (Supply) |input, submit, receive information and track transactions that | | |
|Withdrawn on 1/24/11 |they have previously entered in the DAISY system | | |
|Madrigal | | | |
|DLA | | | |
|ADC 166, |This announces the formal withdrawal of ADC 166, published May | |Proposes withdrawal on 5/28/09 |
|Withdrawal of ADC 166, and Withdrawal of DS |25, 2005. ADC 166 established DS 846V, Supply Planning | | |
|846V (Version 4030) to Accommodate Electronic |Inquiry/Advice as proposed by the DLA. On May 28, 2009, DLA | |No objection against the withdrawal of|
|Data Interchange of Supply Planning |advised DLMSO that DLA had never implemented, and no longer |GSA |ADC 166. |
|Inquiry/Advice between DOD and Vendors |required, DS 846V. DLA requested that ADC 166 and DS 846V be | | |
|(Supply/DLMS) (Staffed by PDCs 169/169A) |withdrawn. This withdrawal of ADC 166 retracts the DS 846V | |Concurs with withdrawal |
|6/12/09 |transaction along with the associated business rules published | | |
|Johnson |in DOD 4000.25-M, DLMS. DLMSO coordinated this withdrawal of |USTRANSCOM |Published Withdrawal of ADC 166 on |
|DLA |ADC 166 with the Supply Process Review committee by e-mail on | |6/12/09 |
| |May 28, 2009, and no objections to withdrawal were received. | | |
| | | |Withdrawal of ADC 166 is effective |
| | | |immediately. |
|Withdrawal of Approved Military Change Letter |Removed date packed for subsistence items and expiration date |DLA |This announces the formal withdrawal |
|(AMCL) 5 and 13, Date Packed/Expiration for |for subsistence items from the following DLMS Supplements | |of AMCL 5 and 13. Both were placed on|
|Subsistence Items (Staffed by PMCLs 3) | | |hold at the request of DLA prior to |
|(Supply/MILSTRIP/MILSTRAP) | | |the 1992/1993 implementation date. In|
|2/18/10 | | |response to a Supply Process Review |
|Hilert/Johnson | | |Committee action item, DLA confirmed |
| | | |that the original requirement is |
| | | |considered obsolete and requested that|
| | | |both AMCL 5 and 13 be withdrawn. The |
| | | |withdrawal of AMCL 5 and 13 also |
| | | |retracts associated business rules |
| | | |published in DOD 4000.25-M, DLMS. |
| | | |Withdrawal of AMCL 5 and 13 is |
| | | |effective March 1, 2010. |
|PDC 274 |Revise the DLMS Unit of Material Measure Conversion Guide to |Army |Requested extension |
|Establishment of Borrowed Codes for DLMS Unit |include new borrowed/substitute codes to provide DOD equivalent|DSCA |Comments provided |
|of Material Measure(Unit of Issue/Purchase |codes for conversion processing at ANSI ASC X12 EDI version |USAF |Under review |
|Unit) Conversion Guide Update |4010 or higher, up to the version at which the correct X12 code| | |
|(Supply, Distribution, Procurement and Contract|becomes available. | | |
|Administration) | | | |
|8/09/07 | | | |
|Hilert | | | |
|PDC 294, |This change is provided to document proposed procedures for FMS| |Comments being integrated by DLA. |
|Foreign Military Sales (FMS) Requisitioning |customers to access, query, and order materiel through DoD | |Procedures for EMALL FMS to be |
|Procedures for Use of DoD EMALL (supply) |EMALL to include DAAS procedures and the use of MILDEP-assigned| |finalized at later date – PDC on hold |
|5/08/08 |RICs for use by FMS customers and supporting U.S. Government | |at this time. |
|Hilert |personnel for internal record keeping purposes when utilizing | | |
| |EMALL. | | |
|PDC 328, |The objective is to correct an invalid cross-reference caused | |Finalization deferred. |
|Administrative Update to ANSI ASC X12 Unit of |by an incorrect ANSI X12 code reference in the DLMS/ANSI Unit | | |
|Material Measure (Unit of Issue/Purchase Unit) |of Issue and Purchase Unit Conversion Guide. | | |
|Conversion Guide (Supply) | | | |
|9/23/08 | | | |
|Hilert | | | |
|PRC Chair | | | |
-----------------------
................
................
In order to avoid copyright disputes, this page is only a partial summary.
To fulfill the demand for quickly locating and searching documents.
It is intelligent file search solution for home and business.
Related searches
- face the nation audio
- the nation s report card
- the nation s report card 2018
- the people s history of the united states
- a nation s culture is quizlet
- what s the world s largest city
- which cities are nation s capital
- a nation s nominal gross domestic product gdp
- masjid muhammad the nation masjid
- alzheimer s and dementia support group
- the nation newspaper kenya news
- logistics support incorporated