3

problems with the MRA process. (The MRA process and associated problems, unrelated 

to the Alaska project, was a separate agenda topic addressed in more detail at this 

meeting.) 

 

 (2) Joint Regional Inventory Material Management (JRIMM) Pilot. 

The JRIMM Pilot is a Navy initiative that will use passive RFID technology to improve 

asset visibility for material moving from the DLA depot at San Joaquin, California, 

through the CCP, to the aerial port at Travis AFB with the ultimate destination at the 

Navy Shipyard in Pearl Harbor, Hawaii. Under the initial implementation, AE_ supply 

status transactions will be prepared as a result of passive RFID tag reads. The supply 

transactions will provide notification to Navy customers and other status recipients that 

material has arrived, departed, or been observed at an intermediate supply/transportation 

location. Globe Ranger middleware will be used to construct a supply status transaction 

(AE_) under first phase implementation in April 2008. Further enhancement of business 

processes requires coordination under Proposed DLMS Change (PDC) 304 (below). 

 (3) Draft PDC 304, DAASC Generated Supply Status for In-transit 

Asset Visibility. This draft PDC is in support of the JRIMM project and establishes 

procedures for the preparation of supply status transactions (AE_) by DAASC. Ms. Mary 

Maurer, DAASC, indicated that from a DAASC perspective, preparing these AE_ 

transactions would constitute a very large increase in the DAASC workload, adding 

about 80 to 200 million reads a month to the LOTS data base. She indicated that LOTS 

was not designed to do this and the DAASC processing time would be impacted. Several 

alternatives to reduce the number of reads were discussed to include limiting the 

transactions to only high priorities and having Globe Ranger determine which visibility 

transactions need the status transaction, but no solution was reached. Ms. Maurer 

indicated that the best way to make this work might be to build another data base 

specifically for this project. DLMSO suggested that DAASC provide a cost estimate and 

a recommended solution. ACTION: DAASC to provide a cost estimate to implement 

the PDC and alternative solutions. 

b. DoD Activity Address Director (DoDAAD) Re-engineering. Mr. Bob 

Hammond, DLMSO, provided a briefing on the DoDAAD reengineering project which 

was implemented to improve data accuracy and timeliness of the DoDAAD updates. In 

addition, a robust Web Query capability was implemented. The next steps include 

elimination of the last batch transaction updates, and continued efforts to improve data 

quality. In addition, DAASC planning has started on reengineering of the Military 

Assistance Program Address Directory (MAPAD), with the same goals of improving data 

accuracy and timeliness. Implementation at the first site is schedule for August 2008 

with the Distribution Standard System (DSS). Mr. Dale Yeakel, DLMSO, walked 

through screen shots of the new inquiry capability which provides an enhanced ability to 

refine the search; two types of wild card searches, and the ability to download the results 

of any query to either a MS Excel format or a delimited text file. Ms. Hilert indicated she 

had identified two issues highlighted during review of the new query. One is that there 

can be multiple RICs associated to each DoDAAC, but only one RIC appears on the 

query. Mr. Yeakel indicated this problem would be fixed. SUBSEQUENT to the 
4

meeting, the query was changed and all RICs now display. The second issue is that for a 

contractor DoDAAC, the contract number, expiration date for the contract, sponsor and 

CAGE are optional fields in the DoDAAF. Mr. Yeakel indicated there would be a 

change to make these mandatory. In addition, there was a discussion regarding a single 

DoDAAC being used for multiple contracts and a single contract number using multiple 

DoDAACs. A single contract number with multiple DoDAACs is used by contractors for 

teaming agreements is accommodated in the DoDAAF. A single DoDAAC with multiple 

associated contracts numbers is not accommodated in the DoDAAF, and there is some 

confusion as to what the policy is regarding this practice. Ms. Hilert indicated that 

Mr. Hammond and the DoDAAC PRC should initiate a policy review and prepare a 

DLMS change proposal to document planned way ahead. ACTION: DLMSO, in 

conjunction with the DoDAAC PRC, develop a DLMS change to document contractor 

DoDAAC policy. 

c. Business Transformation Agency (BTA) Wide Area Workflow (WAWF) 

Direct Vendor Delivery Proposal. Mr. Keith Rineaman, BTA, briefed the committee 

on a proposal to change the DFAR to allow a “construed” acceptance, and therefore, 

payment to the vendor of direct vendor delivery (DVD) shipments, based on a MRA. 

He explained the current policy requires government receipt/acceptance as a prerequisite 

for paying vendors for goods and services and identifies WAWF as the authoritative 

source for invoice acceptance and/or documentation required to make payment. 

Requiring customers to do acceptance in WAWF puts an unreasonable burden on the 

warfighter and would require different processes for depot shipments and DVDs. In 

addition, the Services are reluctant to invest in changes to legacy logistics system to add 

functionality to create acceptance transactions because of the modernization focus. Some 

of the issues Mr. Rineaman raised include changes required to EBS; the fact that not all 

receiving systems send MRAs; and the requirement to identify acceptor by name and 

organization. In addition, during the discussions, several other concerns were raised by 

the group to include: changes to WAWF so that the receiver of the material will not have 

to be registered as an acceptor. Normally for destination acceptance, the ship-to 

DoDAAC will be the acceptor; under this plan, the acceptor will be the DLA ICP. The 

legal aspect of DLA accepting responsibility as the acceptor when not actually receiving 

the material was discussed. There will be further discussions as this plan is vetted with 

senior management and all participating parties. 

d. DLA Receipting Way Ahead Integrated Process Team (IPT). Mr. Don 

Virostko, DLA, provided a briefing on the finding of the IPT tasked by DLA HQ to 

analyze receipt related processes and recommend short- and long-term solutions for 

obtaining timely receipt/acceptance as a prerequisite for vendor payment and interfund 

billing. The members of the team are from DLA HQs, the DDC, DLMSO, DORRA and 

representatives from all the DLA ICPs. The team is evaluating the lack of timely or no 

destination acceptance/receipt acknowledgments, sometimes resulting in late vendor 

payments and interest penalties. Some of the causes and contributing factors include lack 

of compliance with MRA policy and procedures; no standard processes for notifying 

receipt/acceptance where material is obtained through non-tandard ordering methods 

(e.g., DoD EMALL and DLA Tailored Vendor Relationships). In addition, some MRA 
5

transactions are not posting in EBS due to processing errors. Further investigation is 

required to evaluate EBS edits and customer construction of the MRA transaction. The 

IPT plans to develop a proposed DLMS change to document DoD procedures for 

reporting receipt/acceptance of material obtained through nonstandard ordering 

processes, and incorporate receipt/acceptance reporting metrics in Performance Based 

Agreements (PBA) with the Services. The IPT will identify low reporting activities and 

attempt to work together to resolve the issues. 

e. Update to Supply PRC on monthly EBS LMP Meeting. Mr. John Ampela, 

DLA, briefed the committee on the high level Senior Executive monthly meetings 

between DLA and the Army regarding interface issues between EBS and the Army’s 

Logistics Modernization Program (LMP). These meetings began in December 2006 and 

include many topics which have applicability to all of the Services. Summarized below 

are the top three priorities: (refer to briefing slides for all issues discussed). 

 (1) Non-Receipt of BJ Supply Status for Distribution Depot 

Shipments. The Army reported not receiving BJ status which indicates that the order 

quantity was changed to conform to unit pack or because of allowable direct delivery 

contract variance. The BJ status is generated when either the depot or the ICP round a 

customer’s requisition quantity to accommodate unit pack. Lack of BJ status creates 

problems for the Army with follow-on transaction rejecting, bills not matching 

obligations, and unnecessary follow-ups. DLA has made changes to both EBS and DSS 

to ensure rounding is done correctly and BJ status is properly sent. There will be a 60 

day validation that the process is working properly before the issue is closed. 

 

 (2) Response to AC1 (cancellation) for Items on Contract. Army 

customers require either a B8 (quantity requested for cancellation or diversion was not 

accomplished) or a BQ (cancelled) status to properly update records when attempting 

cancellation action. EBS was not always creating status which caused Army records to 

remain open indefinitely. The solution is the timely generation by EBS of definitive 

supply status or shipment status to update customer records. A change to EBS to provide 

positive confirmation of the intent to cancel or the inability to cancel as completed 

February 7, 2008. The Army will validate that the process is working correctly. 

 (3) Non-Receipt of BH Supply Status. The Army reported not receiving 

BH status which indicates a Service coordinated/approved substitutable/interchangeable 

item identified in stock number field will be supplied, when EBS supplied an alternate 

item of supply. BH status was provided for the supplied quantity only, not the quantity 

that was backordered. This prevented the Army from updating records properly, followon transactions rejected, bills didn’t match obligations and unnecessary follow-ups were 

generated. A change in EBS to correct the problems was completed February 7, 2008, 

and the Army has agreed this issue can be closed. 

f. Material Receipt Acknowledgement (MRA) DLMSO has reenergized our 

review and analysis of the draft MRA report with a goal toward identifying any needed 

changes and/or improvements and finalizing the report for SPRC use. The analysis was 
6

conducted by Brenda Meadows and Robert Vitko, DLMSO, with the following 

recommendations/findings: 

 (1) General restructuring of the Summary Report was recommended, to 

include dollar value and percentages. The updated Summary Report should reflect 

counts, dollar value, and percentage of total shipments without MRAs and counts, dollar 

value, and percentage of total shipments with MRAs. 

 

 (2) It was requested that data be collected and displayed under the Service 

of the ship-to DoDAAC, not the Service of the requisitioning DoDAAC. The only 

exception to this recommendation would be if the ship-to DoDAAC was a DSS depot; if 

so, data would be collected under the Service of the requisitioning DoDAAC. 

 (3) It was revealed that the "NO MRA Report for DVDs and Stock 

Shipments" is incorrect. The MILSTRAP requirement is to have a break out of 

"nonresponses" by DVD and stock shipment; however, the current report is a breakout of 

qualifying shipments (based upon business rules) by DVD and stock shipment. It was 

further recommended that the new report would be separated into two categories: 

(1) Stock Shipments Without MRA; and, (2) DVD Shipments Without MRA. 

 

 (4) Recommendation to delete all Special Reports and development of 

AD HOC Query capability: 

• by time frame versus monthly increments 

• by DoDAAC, by DoDAAC exceeding "X" number of 

nonresponses, by DoDAAC with a nonresponse rate exceeding 

"X" percent of their total 

• by ICP RIC, by Federal Supply Class 

• by extended dollar value of shipment 

 (5) Recommendation to delete "MRA by Discrepancy Indicator Report" 

which is displayed by shipping depot. The new WebSDR management reports for 

Supply Discrepancy Reports, currently under development, will provide better data based 

upon actual discrepancy type. 

 (6) General concerns for further analysis: 

• Collection of data under invalid and/or deleted DoDAACs. 

• Method used to determine CONUS/OCONUS designations. 

• DAASC indicated there may be some system constraints on 

providing the recommended AD HOC inquiries. 

ACTION: DLMSO to formalize request and forward to DAAS for assessment/action. 

SUBSEQUENT TO THE MEETING DAASC made the change described in (3) above. 

g. Base Realignment and Closure (BRAC) Supply, Storage and Distribution 

(SS&D). 
7

 (1) Ms Louise Terrell, DLA, provided the committee with an overview of 

the BRAC SS&D process. She said that SS&D decision will reconfigure wholesale 

storage and distribution around four regional Strategic Distribution Platforms (SDPs) – 

Susquehanna, Warner Robins, Oklahoma City, and San Joaquin. The remaining 

distribution depots will act as Forward Distribution Points (FDPs) and consolidate their 

supply, storage, and distribution functions and associated inventories with those 

supporting industrial activities such as maintenance depots and shipyards. With the 

implementation of the BRAC decisions, DLA will be able to distribute the workload on a 

regional basis; satisfy wait time requirements; improve strategic flexibility and surge 

options; consolidate all supply and storage functions at maintenance depots and 

shipyards, with DLA being responsible from receipt of requirements to delivery to 

mechanic; and reduces unnecessary duplication, functions and inventory. The BRAC 

vision is to extend DLA’s core capability of managing the supply chain processes closer 

to the war fighter; focus on weapon systems support and implement integrated demand 

and supply planning, sourcing, delivery and disposal to produce point of consumption 

effects. To mitigate implementation risks, the functions and people will transfer “where 

is, as is.” To date, Warner Robins ALC and Oklahoma City ALC have transferred, with 

Ogden scheduled in June 2008. This will be followed by the Navy, Marine Corps, and 

then the Army. Ms. Hilert asked if there was an effort to standardize the business rules as 

these activities were implemented. Ms. Terrell indicated this would be pursued. 

 (2) PDC 305, Revisions to DLMS Supplements to Add Shop Service 

Center (SSC) for BRAC Inventory Management and Stock Positioning (IMSP). 

This proposed change will allow the addition of the SSC on DLMS standard transactions 

to include the requisition, follow-up, modifier, release order, release order confirmation, 

status transactions and demand data exchange. This will allow demand to be captured at 

the SCC level in support of maintenance activities. Ms. Hilert indicated that the PDC is 

in support of the BRAC implementation at the three ALCs, however it may be used by 

other Services as BRAC SS&D is implemented at those sites. ACTION: All 

Components to review and respond to the PDC staffing by May 6, 2008. 

 

h. Jump Start Status. 

 (1) Jump Start Metrics. Mr. Dale Yeakel, DLMSO, provided an 

overview of the DLMS migration Jump Start Program. This is a BTA sponsored 

program to motivate and assist Components to migrate to DLMS by providing “seed 

money” as well as program management and enterprise support. Four systems received 

funding in 2007; The Army LMP, Navy R-Supply, Air Force ILS/SBSS and Marine 

Corps MAISTER. Mr. Yeakel provided metrics that show that there were 16.4 million 

DLMS transactions processed in April 2006 and almost 40 million in March 2008. This 

means that 30 percent of all transactions in and out of DAASC are in the DLMS format. 

The goal for the end of 2008 is 35 percent, which Mr. Yeakel feels is attainable. These 

metrics are reported monthly to the BTA and semiannually to Congress. Mr. Yeakel said 

that beginning in July 2008, transportation transactions, which had not previously been 

counted, will be included in the metrics. These will be counted separately for the first 

month, so that the increase can be explained. 
8

 (2) Army – LMP. Mr. Michael Guerrieri, Army, briefed the committee 

on the LMP migration to DLMS which began in December 2006, continued with 

17 transactions migrating in April 2008, and the final 12 scheduled for August 2008. He 

indicated that the direct Army to Army interface will remain MILS. He discussed 

lessons learned for other systems planning to migrate specifically mentioning the need for 

early communication with DAASC to leverage existing DAASC maps, and early 

communication with DLMSO to understand existing DLMS implementation conventions. 

He emphasized the need to work with both DLMSO and DAASC to identify servicespecific requirements, recommended an incremental development and implementation 

approach, and stressed the need for extensive testing. Ms. Hilert said that the Army 

should review the all new ADCs to ensure that common-use DLMS enhancements are 

integrated with LMP. Global Combat Support System (GCSS) Army, which is the 

replacement for the Standard Army Retail Supply System (SARSS), should also look 

toward DLMS enhancement capability during development. She also requested that the 

Army provide an update on the GCSS. ACTION: The Army to provide a briefing at the 

next Supply PRC Meeting on the status of GCSS development with focus on DLMS 

interfaces and enhancement capability. 

 (3) Air Force – Integrated Logistics Systems-Supply (ILS-S). Mr. Pete 

Talamonti, Air Force, provided a briefing on the ILS-S migration to DLMS. ILS-S, 

which is the modernized version of the legacy Standard Base Supply System (SBSS) will 

be migrating 80 transactions to DLMS and will implement in June 2008. Mr. Talamonti 

provided an enlightening account of lessons learned including: Do not migrate too many 

transactions at one time; validate the data content in your MILS transactions prior to 

attempting migration; understand the PDC/ADC process; build flexibility into conversion 

software to allow for easy modifications to transaction conversion rules; establish a solid 

test plan and with participation of testing partners early in the process. The AF has 

identified several DLMS enhancements that will be implemented at a later date. These 

include: identification of weapons system designation on the requisition; specifying the 

aircraft tail number on requisitions; using plain text to clarify urgency/priority on 

requisitions; additional item identification data to better track reparable items; and adding 

RFID and IUID to selected transactions. 

 (4) Marine Corps – MAISTER. Mr. Jackie Mitchell, Marine Corps, 

briefed the group on the DLMS migration of MAISTER. The migration is divided into 

two phases. Phase I will migrate 5 DLMS transactions and is expected to be completed 

in May 2008, implementation of the remaining transactions has not been determined. 

Mr. Mitchell said that testing with DAASC has not started because connectivity had not 

yet been established. This problem was caused because the Marine Corps Authority to 

Operate/Connect (ATO/ATC) with DAASC has expired. They are working on getting 

this approved so testing can begin. He indicated that no DLMS enhancements would be 

implemented and that incoming transactions would be translated to MILS, with additional 

data elements stored in the data base but not used. Outbound transactions will not carry 

any information other than the 80 record positions currently used in MILS. Ms. Hilert 

indicated that would be a problem for the Marine Corps when they implement the 
9

interface with WAWF if the new data elements are not in the 861 (Acceptance Report) 

going to WAWF. 

 5. Navy – Retail Supply (R-Supply). Ms. Susan Bess, Navy, provided a 

briefing on the DLMS migration of R-Supply. R-Supply plans to migrate two MILS 

transaction, the AS_ and the AU_ to a DLMS 856S. No implementation data has been 

determined. Lessons learned will be provided after the Release Readiness Review (RRR) 

which is scheduled for April 30, 2008. Ms. Bess said that DLMS enhancements such as 

RFID and UII would not be implemented now, but the additional data elements would be 

stored, but not used. She also said that new data elements for any inbound transactions 

would be stored and that outbound transactions would only contain core MILS data 

elements. 

i. Monitoring for Requisition Priority Abuse – PDC 280, Automated 

Downgrade for Priority Abuse and Reporting Procedures. The proposed change 

establishes procedures for GSA compliance with MILSTRIP business rules for 

requisition priority validation for F/AD I activities on requisitions submitted directly to 

GSA for purchase of GSA managed items. In addition to the GSA requested change, 

DLMSO recommends the current PD01 exclusion from automatic downgrading be 

terminated for requisitions which do not identify authorized DoDAACs and are 

originated via internet using GSA Advantage/Global or DoD EMALL. DLMSO also 

recommends inclusion of the original (downgraded) Priority Designator (PD) in the 

DLMS Supply Status with BK status. This will clarify the reason and specific change 

associated with the multipurpose BK status. Ms. Hilert said this proposed change has 

been out for staffing since December 2007 and has been concurred in by all Components 

except the Air Force. She indicated that GSA was ready to implement and asked the 

Air Force to concur in the parts that could be implemented and provide plans for those 

items that will be implemented in the future. ACTION: Air Force to provide response 

ASAP. 

j. FMS Topics. Ms. Linda Kimberlin, DLA brief the committee on the following 

proposed DLMS changes: 

 (1) DRAFT PDC 294 Revised Procedures for Security Assistance Use 

of DoD Electronic Mall (EMALL). This proposed change is to document proposed 

procedures for FMS customer to access, query, and order material through DoD EMALL. 

This includes DAASC procedures and the use of military department assigned RICs for 

use by FMS customers and supporting U.S. personnel for internal record keeping 

purposes when using EMALL. FMS requisitions will be recorded in the FMS legacy 

systems using a unique MILDEP RIC to identify them internally as EMALL orders. The 

requisitions will then be processed in the Security Cooperation Information Portal 

(SCIP), where the active Requisition File will be matched against the EMALL Hold File. 

The matched requisitions will be then be combined with the shopping cart data and 

returned to DoD EMALL for processing, and, finally, sent to DAASC for transmission to 

the Source of Supply. DLMSO will release this PDC for formal coordination in early 

May. 
10

 (2) PDC 289, Revisions to Security Assistance Program Procedures, 

Modification of the Definition of the Security Assistance Type of Assistance and 

Financing Codes and Policy Change to Billing Procedures. This change identifies 

MILSTRIP Appendix 2.19, Security Assistance Type of Assistance and Financing Codes 

and MILSBILLS Chapter 2, Billing Procedures, as well as administrative revisions to the 

MILSTRIP Chapter 6, Security Assistance Program. It also supports billing the FMS 

customer for storage costs of material held in U.S. custody due to a failure to respond to a 

Notice of Availability. Ms. Hilert solicited any additional updates to Chapter 6 of the 

MILSTRIP Manual, which outlines procedures for the Security Assistance Program. 

Mr. Vitko noted that the terminology updates will also need to be applied to other areas 

of the manual such as the Material Obligation Validation (MOV) procedures in 

Chapter 7. DLMSO will search the manual for remaining references to MAP before 

final publication. The PDC does not specifically identify any systems changes, but 

Ms. Hilert indicated that the Components need to verify whether their processing is 

compliant with rules for use of the two Type of Assistance and Financing Codes 

discussed. Ms. Hilert asked if issues of excess material made to Grant Aid customers 

will be processed as free issue (MILSTRIP paragraph C6.21.1.2). This appears to be in 

conflict with the reimbursable policy for foreign customers. She indicated the DLA 

policy needs to be verified and coordinated with the ILCOs and then the MILSTRIP 

paragraph clarified. ACTION: DLMSO to address MAP term through out MILSTRIP 

and other DLMSO-administered manuals. ACTION: DLA to verify the free issue 

policy. All components verify if system changes are required to implement this PDC 

and provide comments by May 22, 2008. 

k. AMCL 15, New Ownership Code 0 (Zero) to Identify Special Operation 

Forces (SOF) Ownership. This requirement is rooted in Public Law 99-433, GoldwaterNichols DoD Reorganization Act, which directed establishment of a Unified Combatant 

Command for DoD Special Operations Forces, and created Major Force Program 11 

funding with DoD for programming and funding of requirements. Although the change 

was approved and had an implementation date of 2004, the Army reported that they had 

not implemented due to their modernization efforts. Subsequently, Navy surfaced a 

problem of Navy owned SOF assets, stored at Army sites, which Army commingles with 

other Service-owned SOF assets, without visibility of true owner. Inability to obtain 

visibility of these assets is an unsatisfactory situation, not only to the Navy. The Army 

agreed to reopen this requirement and assess impact on LMP rollout, and changes which 

would be required to the Army's Storage and Distribution System, which currently does 

not recognize/store by O/P. ACTION: Army to co-host a meeting with Navy, to 

discuss interim proposal by Army that would address SPECWARCOM concerns 

regarding use of Project Code 841 - RIC NDX to address overall O/P issues. DLMSO 

asked to be invited. Additionally, Army has agreed to fully address the SOCOM zero 

ownership code in its LMP rollout. This topic will be continued as an item of interest to 

be reviewed at the next SPRC meeting. Interim status update will be provided to 

DLMSO after meeting between Army and Navy. 
11

 l. Combining DLSS/DLMS Manuals. Recent changes in the publishing 

procedures of Washington Headquarters Service have impacted DLMSO's publication of 

the MILS manuals, e.g., Military Standard Requisitioning and Issue Procedures 

(MILSTRIP), Military Standard Transaction Reporting and Accounting Procedures 

(MILSTRAP), Military Standard Billing System (MILSBILLS), etc., and the Defense 

Logistics Management Standards (DLMS) manuals. Since the DoD Components are 

migrating to a DLMS environment, DLMSO is exploring combining the MILS and 

DLMS manuals. The current process of maintaining two sets of manuals which contain 

essentially the same information in different formats is resource intensive and duplicative 

in nature. The DoDAAD and MAPAD manuals have been updated for publication under 

DLMS and the MILS manual will be discontinued. We are also proposing to incorporate 

MILSTRIP and MILSTRAP requirements into DLMS Volume 2, Supply. This would 

require DLMSO to maintain visibility of MILS peculiar terminology in the DLMS text. 

In preparation for this, all MILS code lists and formats are being moved to the DLMSO 

website (refer to http://www.dla.mil/j-6/dlmso/elibrary/TransFormats/140_997.asp for 

matrix of DLMS Supplements and their MILS equivalent with links for all applicable 

formats). DLMSO is working with DUSD(L&MR)SCI and WHS to get relief from the 

stylized manner in which WHS mandates their regulations/manuals to be displayed, e.g., 

paragraph numbering, elimination of URLs, etc. DLMSO is also working on the DLMS 

manual to ensure that all MILS-related procedures have been updated over the time and 

to better align the DLMS chapter structure to that of the present MILS chapter structure. 

In a related discussion, Ms. Hilert asked DAASC to provide DLMSO with the latest 

version of the DAASC maps and to explore approaches to making map updates more 

accessible, e.g. using a web-accessible, controlled-access table and (possibly) a 

subscriber program so that users can be alerted to map updates. ACTION: DLMSO 

action described is on-going. DAASC long-term action to be determined. 

m. DLMS Changes recently approved, in staffing, under development or old 

requests for implementation dates needing a fresh look. 

 (1) PDC 295, Consolidation and Containerization Points (CCP) 

Originated Supply Discrepancy Reports including Noncompliant Wood Packaging 

Material (WPM) Procedures and Shipment Hold Code. This change is requested to 

support generation of SDRs at the CCPs. The initial use will involve shipments using 

noncompliant WPM and shipping through the CCPs to OCONUS sites. Responses on 

this PDC were due April 18, 2008, and not all have been received. ACTION: All 

Components were to provide comments as soon as possible. DLMSO will publish the 

ADC in early May; this process will be implemented in July 2008. It is anticipated that 

the revised SDR format will cause processing problems for implemented SDR systems. 

 (2) PDC 201, Use of Purchase Request Number (PRN) in Logistics 

Reassignment Memorandum Due-in. This proposed change allows for a PRN unique 

to the BSM implementation to be used as a transactions reference number of document 

identifier code DDX Memorandum Due-in transactions initiated from EBS. The 

approval of the change is pending DLA providing the associated MILSTRAP Chapter 11 

procedures to include with the ADC and to publish in the MILSTRAP/DLMS manual. 
12

ACTION: DLA to provide procedures needed for the approval of PDC 201 within 30 

days of the date of these minutes. 

 (3) Revised RFID for Joint Approved MILS Changes (AMCL) 5 

(MILSTRAP) & 13 (MILSTRIP) -- Date Packed/Expiration Date for Subsistence 

Items. The release of a revised request for implementation date for Joint AMCLs 5 

(MILSTRAP) and 15 (MILSTRIP) has been on hold for years pending DLA validation of 

the AMCL requirement. As part of a DLMSO effort to address old changes that have not 

been implemented, Ms. Johnson requested that DLA validate the AMCL requirement. 

ACTION: DLA to provide information on validity of the AMCL requirement within 

30 days of the date of these minutes. 

 (4) Request for Implementation Date for AMCL 13, Partial Reversal 

of Select MILSTRAP Transactions. This approved change allows the reversal of less 

than the original quantity of select MILSTRAP transactions. An implmentation date was 

never established for this old approved change. As part of a DLMSO effort to address 

old changes that have not been fully implemented, Ms. Johnson released a new request 

for implementation date to ascertain the status of AMCL 13 implementation. DLA and 

the Army had not responded. ACTION: DLA and Army to provide implementation 

status. 

 (5) Request for Implementation Date for AMCL 49A (dated 

September 10, 1998), Reconciliation and Follow-up Procedures for Dues-in After 

Logistics Reassignment. This approved change provides a standard automated 

procedure to reconcile the due-in records of the Gaining Item Manager and the Losing 

Item Manager 90 days after the effective transfer date and then semi-manually as 

necessary. An implementation date was never established in response to the September 

1998 request for implementation date. The latest status, provided in 2002, indicated that 

the Services were in varying states of implementation, and DLA provided status for 

SAMMS vice EBS. As part of a DLMSO effort to address old changes that have not 

been fully implemented, Ms. Johnson requested that the Services, and DLA for EBS, 

provide updated implementation status. ACTION: All Components to provide updated 

implementation status within 30 days of the date of these minutes. 

 (6) DRAFT PDC 296, Addition of Party to Receive Copy to Support 

Requirements for Theater Enterprise Wide Logistics (TEWLS) Requisitions. This 

change requests the capability to identify a “Party to Receive Copy” in a requisition, 

modification and follow-up and subsequent transmission of a copy transaction to the 

identified party by DAAS. This allows visibility of Military Service requisitions for 

GSA/Non-DLA material for medical and industrial kitting component parts when the 

DLA Defense Working Capital Funds (DWCF) are expended under the TEWLS/AMMA 

business model. ACTION: ADC publication is pending receipt of DLA J-8 concurrence 

(requested by DLMSO due to concurrent (rather than prior) verification of funds 

availability when Army is ordering using DLA DWCF funds.