December 15, 2003

DLMSO

MEMORANDUM FOR RECORD

SUBJECT: Defense Logistics Management System (DLMS) Supply Process 

Review Committee (PRC) Meeting 03-3, December 3-4, 2003.

Purpose: The Defense Logistics Management Standards Office (DLMSO) hosted the subject 

meeting at the Headquarters Complex, Fort Belvoir, Virginia. Specific discussion topics are noted 

below. A list of attendees is shown at Enclosure 1. All meeting handouts and briefing materials are 

available on the Supply PRC web page (refer to the meeting agenda): http://www.dla.mil/j6/dlmso/Programs/Committees/Supply/supplyPRC.asp. 

Brief Summary of Discussion: Ms. Ellen Hilert, Supply PRC (SPRC) Chair, Ms. Mary Jane 

Johnson, MILSTRAP Administrator, and Mr. Vermella Savage, MILSTRIP Administrator, facilitated 

discussion:

Review of Meeting Topics:

a. DLSS/DLMS Change Evaluation, Status Review, and Issue Resolution. The following 

specific changes were discussed:

 (1) Joint AMCLs 10 (MILSTRAP) and 34 (MILSTRIP), Identification of Product 

Quality Deficiency Related (PQDR) Material. BACKGROUND: These AMCLs provide a 

standard means for inter-Component identification and control of potential and/or confirmed product 

quality deficient materiel. Further, it employs the new standard Supply Condition Code Q and 

Management Codes O and S to distinguish which deficient materiel must be mutilated upon turn-in to 

the Defense Reutilization and Marketing Service (DRMS). DISCUSSION: During the meeting the 

Components were provided with an updated draft of the AMCL with revisions previously identified 

from the last SPRC meeting to include: (a) the Supply Discrepancy Report (SDR) may only be used to 

report product quality deficiencies by Security Assistance (SA) customers; (b) Elimination of the 

requirement to coordinate off-line with the DRMS activity for each required mutilation action 

associated with SCC Q material (c); the addition of a DAAS edit for Disposal Release Orders for 

CSI/FSCAP material in SCC Q to ensure that these contain Management Code S indicating that 

mutilation is required; (d) numerous administrative revisions. ACTION: The AMCL will be 

distributed as a draft prior to formal release for staggered implementation. DLA will research DRMS, 

DSS, and BSM status. The Army was requested to provide recommended implementation date for 

planning purposes. The DAAS change could be ready for implementation in April, 2004.
2

(2) ADC 20A, Revision of Status Code CX; Application of Status Code D7 for Modifier 

Rejects. BACKGROUND: This revision removes the applicability of the Status Code CX for the 

AM_, Requisition Modifier. The generic Status Code D7 for invalid data on the AM_ will be applied. 

This change was intended to provide relief to the Army whose internal processing triggered 

cancellation of the original order after the modification was rejected and resulted in large financial

loss. DISCUSSION: The Army continued to report a significant loss of deobligated funds resulting 

from cancellation of requisitions which, due to timing and other factors, the requisitioner was unable to 

establish a new obligation within the same fiscal year. The Army provided more statistical information 

at this meeting, however it still could not be determined from the data presented how much of the 

problem is internal Army or could be resolved through corrective action already available. The DLA 

representative again suggested that the least disruptive fix would be a reinstatement transaction 

modeled after the MOV process. However this could not be considered without sufficient justification. 

[Side issue: The Army indicated they are getting significant numbers of suspicious price changes from 

DLA, some of which represent a significant increase in the unit price. They were requested to contact 

the Finance PRC or the DLA Price Advocate in writing with any questions/concerns.] ACTION: The 

Army will examine a larger sampling of cancellations and provide more details for the next meeting. 

Based upon findings, they may draft a proposed change to reflect recommendations made during the 

meeting. 

(3) PDC 108, Mandatory Identification of Controlled Inventory Item Code (CIIC) on 

Transfers to DRMO. The proposed change requires mandatory controlled inventory item code 

(CIIC) identification under the MILSTRIP AP3.49, Transfers to Defense Reutilization and Marketing 

Information Office (DRMO) on DD Form 1348-1A or DD From 1348-2, Issue Release Receipt 

Document (IRRD). This initiator considers this change critical to facilitate identification of 

Cryptographic/cryptologic items being turned in to the DRMO that may be controlled by the National 

Security Agency. In addition, DRMS would like to change Block 9 of the pre-printed DD Form 1348-

1A from “PS” to “CIIC”. DISCUSSION: The committee discussed the non-concurring comments 

provided by respondents to the PDC staffing. These were considered insufficient arguments for 

disapproving the change; particularly in light of the nearly identical change already imposed on the 

1348-1A when used for non-disposal issues. The Chair regards this change as an extension of the 

previously approved change (AMCL 32) and advocated approval with staggered implementation. The 

committee discussed the possibility of changing block 9 of DD Form 1348-1A to print “UNK” when 

the CIIC of an item is blank. This would indicate to DRMS that an effort was made to determine the 

correct CIIC, however the DLIS data was blank and the CIIC could not be determined. ACTION: 

DLA will determine if DSS could be easily changed to print “UNK” vice leaving the CIIC blank on the 

1348-1A. DRMS will strengthen the justification for the change stressing timing factor -- need for the 

CIIC on the form required even though it could be retrieved systematically at a later point. DLMSO 

will release a draft an ADC for review prior to formal release. It will reflect the following changes 

clarification of the need provided by DRMS and will include procedures to reflect that a blank CIIC 

should not hold up disposal processing; and that material with a blank or “UKN” CIIC value should 

not be in disposed in batch/lots. As a separate action, the request to change the block name from the 

outdated “P/S” to CIIC is valid, but is not urgent and alone would not justify the expense. DLMSO 

will initiate a data call to determine if there are other changes required to the 1348-1A. 
3

(4) PDC 109, Revise DS 940R, Material Release to Accommodate UIT Functionality. This 

change proposal applies only the DLMS environment. Proposed changes must be used with ADC 81 

(New DS and Federal Implementation Conventions (IC) for Transaction Set 140B, UIT Reporting and 

Transaction Set 888B, UIT Data Change) and several other draft proposed DLMS changes to support 

Distribution Standard System (DSS) DOD UIT Phases 1 and 2. This change establishes a new 

standard data element to communicate special processing requests to the DSS under existing interComponent Agreements. DISCUSSION: The chair clarified for all that this proposed change is much 

broader than UIT; it serves to document the use by DSS of the Delivery Priority Code which 

communicates special processing requirements to DSS for depot shipments under agreements with 

various DOD Components, to include the Navy, NIMA, and the Air Force. There was discussion on 

whether these transactions go through DAAS and will therefore be subjected to the DAAS translation 

process. IF so, DAASC translation rules must be established since the code is carried in a multipurpose field. The delivery priority codes need to be better defined for DLMS manual publication after 

implementation. Specific rules must be applied so that the codes are not misused. ACTION: DLA 

will provide a better definition of the delivery priority codes. DLA will look into the source of these 

transactions to determine if translation is required. DLMSO will follow up with the Components for 

comments on the PDC after additional information is provided by DLA.

(5) Draft PDC 113, DI Code DLT, Addition of New Record 4 to Accommodate Existing 

USAF/DLA Process. Background: Several years ago, without DOD MILSTRAP authorization, 

DOD 4140.26-M published a new record 4 for MILSTRAP DI Code DLT, Logistics Reassignment 

(LR) Backorder and Demand Data Transaction. At that time Air Force and DLA, as a minimum, 

implemented DI Code DLT Record 4 in their legacy systems. Air Force and DLA proposed this 

change to revise MILSTRAP, appendix AP3.23 to add DLT Record 4 for optional use. 

DISCUSSION: Navy indicated that they had also implemented DLT Record 4. Given that the 

procedure is optional and Air Force, DLA and Navy have implemented, the committee agreed this 

could be released as an approved change rather than a PDC. Any Service that has not already 

implemented DI Code DLT record 4 should NOT revise their legacy systems to do so. DLA’s 

Business System Modernization (BSM) will implement LR transactions in the near future and is 

interested in the DLMS 536L mapping for record 4 data. ACTION: DLMSO will release an 

approved change to revise MILSTRAP as indicated in draft PDC 113, once the Integrated Materiel 

Management Chair provides record 4 data definitions and authoritative source information requested 

by email. DLMSO will also develop a PDC mapping the DLT record 4 data to the DLMS 536L.

(6) PDC 114, Inclusion of Unique Identification (UII) of Items in DLMS Transactions 

(Supply). This is a DLMS proposal in support of the OSD UID initiative discussed below. This 

change would update DLMS transaction to carry UII data. UII is a set of data elements that is globally 

unique and unambiguous, ensures data integrity and data quality throughout life and supports multifaceted business applications and users. DISCUSSION: The chair indicated that the proposal is not 

being staffed at this time, but is intended to begin to familiarize the Components with the concept of 

UII and to stimulate thought as far as requirements, issues, and recommendations that are required for 

including UII in DLMS transactions. The proposal will be briefed to the Unique Item Tracking 

Committee on 11 December, 2003. Changes resulting from that meeting as well as the SPRC will be 

incorporated into the proposal and provided to the Components. ACTION: DLA will identify the 

specific transactions used in the initial phases of DSS implementation of Unique Item Tracking to be 

used to limit the scope of this change to a more manageable number of transactions. DLMSO will 
4

update per comments at both meetings and provide a draft proposal to the Committee. DLMSO will 

seek OSD guidance on policy since no implementation will be pursued until logistics implementation 

strategy is clarified.

b. OSD Unique Identification (UID) Policy and Implementation Planning. Mr. Bruce 

Propert, Chair of the UID Technical Interface Working Group (TIWG), briefed the committee on the 

DOD’s approach to UID. The DOD has determined that in order to facilitate item tracking in the DOD 

business systems and provide reliable and accurate data for management, financial accountability and 

asset management purposes that tangible items delivered to the government will be uniquely identified 

and marked. UID will be required for property items based on a set of specific criteria to include;

acquisition cost, serially managed items, mission essential items, items that are the components of a 

delivered item, etc. UID is a mandatory DOD requirement on all solicitations issued on or after 

January 1, 2004. In addition Wide Area Workflow (WAWF) will be modified to capture UID data in 

April 2004 and form the basis of the DOD Registry.

 c. Army Briefing on Logistics Modernization Program (LMP). The briefing was not 

given. The Army LMP office did not respond to the request to provide an overview. A follow-up 

request will be made in an attempt to schedule the briefing at the next SPRC.

d. SDR Transformation Initiative. Ms. Ellen Hilert provided a briefing on the DOD Supply 

Discrepancy Reports Transformation Initiative. She emphasized that the goal of the system is to 

provide support for intr-Service/Agency transactional exchange and will not require Services to 

abandon existing SDR systems. The implementation approach and schedule was discussed. The 

implementation date for Phase I is January 2004 and will provide Web capability with pre-populated 

data; Web distribution based upon business rules and Component capabilities; and limited transactional 

exchanges. Phase II planning is underway and will provide the integration of Components systems; 

extensive ability to receive and route SDR information using transactional exchange; comprehensive 

SDR and response data base and a reports and query capability. OSD Business Initiatives Council 

(BIC) funding is being pursued to facilitate and ensure a timely Phase II implementation.

e. Global Transportation Network (GTN) Overview. Mr. Richard Cobb from 

TRANSCOM, provided a demonstration and overview of the GTN. The demonstration was very 

informative and provided committee members with information on what is available in the GTN to 

include the ability to track the status and location of shipments of material moving through the Defense 

Transportation System. GTN receives informational “feeds” from several systems as well as DAAS to 

determine status of material shipments. One question that came up during the overview was if GTN 21 

(an future increment of GTN with a more robust hardware platform) will be able to use a DLMS data 

feed from DAAS as well as the current MILSTRIP feed. This becomes more important as 

enhancements to the DLMS are made such as unique item tracking (UIT) functionality. The DLA 

DSS will be implementing DLMS shortly with UIT capability and customer may expect to track the 

movement of some item by its serial number. This is not possible using the 80 record position MILS. 

Mr. Cobb was unable to provide an answer. SUBSEQUENT TO THE MEETING: This 

question/concern was forwarded to Ms. Stephanie Lopez, the TRANSCOM/DLA Liaison Officer.

 f. DOD 4160.21-M Interim Guidance for Large Quantities. This discussion concerned a 

DRMS request to provide procedures to generating and disposal activities regarding the turn in of large 
5

quantities of excess material that exceeded the record positions in the quantity field. ACTION: DLA 

will request more information from DRMS to clarify the request and its justification. The impact of 

the suggestion to use suffixing vice a multiplier for the quantity field will have to be assessed during 

evaluation. DLA will assist DRMS with submission of a formal change proposal.

g. Supply/Transportation Priority Synchronization Initiative. LTC James Garner, 

TRANSCOM was scheduled to brief the committee on the initiative, however he was unavailable and 

Mr. Joseph Lapp, TRANSCOM, provided the briefing via VTC. The initiative is designed to improve 

the alignment of supply and transportation priority processes to support COCOM/Services 

requirements to deploy, employ and sustain. The goal is to allow personnel and material to flow 

through the distribution pipeline without the need for intervention. Three areas were identified for 

possible quick fixes to improve the process/ introduce a limited use project code; monitor FAD and 

priority abuse and line COCOM J4 with clearance authorities. DLA and DLMSO requested 

terminology used in the briefing be corrected; there was strong objection to referring to approved 

MILSTRIP procedures as “Priority Process Work Arounds.” ACTION: DLMSO will provide to 

USTRANSCOM background information on a previous Joint Staff study on the potential to stratify 

priority within project code. The Committee would like more information on the suggested use of 

project codes as a “quick win” solution. SUBSEQUENT TO THE MEETING: Additional charts 

from the initial meeting of the synchronization working group were forwarded to the Committee to 

provide more background information. These are also available from the Supply PRC web page 

(hyperlink above).

h. Updated Status on Items from SPRC Meeting 03-02. Refer to 03-2 minutes for 

background.

(1) PDC 98, Clarificationof Transportation Control Number (TCN) Usage of Modes 9 

and X. This PDC is still pending. DLMSO is considering requiring a TCN for all modes of shipment 

except customer pick-up (mode X). DLMSO is researching the lack of TCNs on the initial leg of an 

FMS shipment and will follow up with originators for non-compliance.

(2) PDC 99 Now ADC 104, DAAS Processing Rules for Project Code 3AD. This change 

was published as an approved change (ADC 103) and has been implemented at DAAS.

(3) PDC 100 Now ADC 104, Addition of Routing Identifier (RI) Code of the Activity 

Originating the MRO/LRO/DRO to the 2D Symbol on Issue Release/Receipt Document (DD 

Form 1348-1A). This change has been approved, but not implemented. ACTION: DLA will check 

with DSS for implementation status. 

(4) PDC 102, Weapon System Data Change DLMS Supplement (DS) 888W. This will be 

published as an approved DLMS change. On a related topic, the Air Force has also requested two new 

80 rp transactions for weapons systems program use. DLMSO has asked the Air Force to identify the 

functionality required versus a specific transaction format since OSD policy dictates that new 

development should use the DLMS.

(5) PDC 103, Revised Service Code V Use. An approved change will be issued as soon as 

the Navy provides an estimated date for when the Navy needs this change. The Navy indicated that 
6

their legacy systems can’t be changed to accommodate the change. ACTION: The PDC will be held 

pending input from the Navy.

 (6) PDC 104, Clarification of Supply Status BK. No additional action has been initiated on 

PDC 104.

 

 (7) PDC 106, United States Coast Guard Service Code Assignment. The MILSTRIP 

Administrator indicated that Components have failed to respond to this staffing. SUBSEQUENT TO 

THE MEETING: DLMSO forwarded a followup to non-responsive Components requesting their 

comments/concurrence no later than December 19, 2003.

 (8) Logistics Asset Support Estimate (LASE) Transactions. The MILSTRAP 

Administrator asked DLA for the status of LASE implementation in BSM. As noted at SPRC 03-2, 

BSM did not accommodate LASE functionality in Release 1 and would not provide a workaround 

solution to fill this void. ACTION: DLA will investiga te current status of BSM LASE 

implementation.

 h. Next Meeting. The SPRC 04-01 meeting is scheduled for 20-22 April 2004.

___/ SIGNED /__________

ELLEN HILERT

Supply PRC Chair

APPROVED:

__/ SIGNED /_

JAMES A. JOHNSON

Director, DLMSO

Enclosure