No Reference Action Item Responsibility Target Due Date Status Notes 1 Minutes § b.(4) Page 3 Navy provide additional information if there is a specific MRA Report requirement relating to part numbers. Navy 30 Jan 2014 19 SEP 2014 Closed 8/20/2/14 – No additional input. The Defense Logistics Management Standards Office (DLMSO) will close Action Item if no input by 9/19/2014. 11/10/14-DLMSO closed Action Item; no additional Navy input was received. 2 Minutes § c.(3) Page 4 DLA Transaction Services review requirement for adding the three data pattern COMMRIs and identify any issues with the requirement. DLA Transaction Services 18 Nov 2013 Closed 10/11/13 – Initial response from DLA Transaction Services indicates the three data pattern COMMRIs are feasible. Multiple issues/questions raised that will be addressed in PDC 1086. 6/18/2014 – DLMSO released ADC 1086. 3 Minutes § d Page 5 Supply PRC representatives to review the examples of the receipt scenario cited for each Component in draft PDC 1087, and provide language to include in PDC for their Component. All Supply PRC Representatives 12 Nov 2013 Closed 11/5/13 – DLMSO followed up for responses. 11/12/13 – Interim Navy explanation of MRA & Navy ERP. 11/17/13 - Army provided response. 1/7/14 - PDC 1087 released for 30 day staffing. 6/12/2014 – released ADC 1087.
4 Minutes § d Page 5 Identify if your Component is compliant in generating MRA follow-ups under MILSTRAP rules, and if not, provide the anticipated timeline for implementation. Army Air Force Marine Corps Provide in response to PDC 1087 Closed 11/12/13 – Navy Response: Navy not sending follow-ups for delinquent MRA. 12/20/13 – DLA Response: DLA is compliant with MRA follow-up process. 6/12/14 – Army confirmed not sending follow-ups for delinquent MRA. Pending corrected logic in LMP 3/14/14 – Air Force response confirmed they are compliant with MRA follow-up process using MILSTRAP legacy DIC DRF 2/11/14 – Marine Corps response confirmed they are compliant with MRA follow-up process 6/12/2014 – DLMSO released ADC 1087. 5 Minutes § h Page 6 Air Force and Navy Supply PRC representatives provide input on the pending questions identified on the MRA Report business rules decision tree. Air Force Navy 30 Jan 2014 22 Jan 2014 Closed 12/4/13 – Received Air Force Response. 1/10/14 – DLMSO response to Air Force for clarification of several Air Force responses. 1/28/2014 – Received Air Force clarification 1/10/14 – DLMSO follow-up on the 9/10/13 response DLMSO set to Navy to clarify the Navy MRA questions. 1/30/2014 and 1/31/2014 – Received Navy response/ clarification
17 Minutes § n Page 9 Services review procedures to ensure that the proper suffixes are identified in the MRA transactions to align with the suffixes identified in the corresponding shipment status. All 30 Jan 2014 19 Sep 2014 10 Dec 2014 Open 6/16/15 – When Navy ERP generates an outgoing requisition (A0_) to DLA, and DLA splits the order, Navy ERP should send corresponding suffix-coded MRA transactions. Navy will submit a trouble ticket/Change Request to require these transactions in Navy ERP. 6/23/15 – AF Retail (ILS-S) reply: ILS-S MRA programs generate accurate DLMS 527Rs with the correct suffix code contingent upon base user entering correct value on REC input. 18 Minutes § n Page 9 Marine Corps to research why MRA transactions are being sent to the RIC – LA9 (Advanced Military Packaging – MILSTRIP Orders, Oshkosh, WI. LA9 is not a valid wholesale ICP RIC per LMARS business rules and confirmed during the staffing of ADC 1025. If LA9 is in fact a wholesale ICP RIC, then Marine Corps needs to submit PDC to update LMARS business rules to reflect that change. USMC 30 Jan 2014 19 Sep 2014 10 Dec 2014 Open No updates received 19 Minutes § n Page 9 Navy submit a PDC to define and document their Service unique data requirement for RP 77-80 (Service-use field) in the MRA legacy transaction (DRA) and clarify the procedures being used. Navy 30 Jan 2014 19 Sep 2014 10 Dec 2014 Open 6/16/15 – PDC should not be required. The two examples provided identify that the site/user basically copied the last transaction they received (AE1 status) and changed the DIC to DRA. In doing this, the structure/card columns (ccs) did not match the DRA layout.
20 Minutes § n Page 10 GSA provide feedback on the results of their internal analysis of why some shipment status transactions are not being sent and take action to correct processing issues where not consistent with MILSTRIP procedures. GSA 30 Jan 2014 10 Dec 2014 Open 8/21/14 – GSA did not comment on the results on the analysis on the 100 document numbers, but it appears the problem was related to issues out of GSA distribution centers. GSA is closing their two distribution centers by 31 Dec 2014, and implementing a DLMS compliant Order Management System (OMS). The next OMS release is planned for July 2015 which should address this issue. 21 Minutes § n Page 10 Army research Army-directed shipments that result in MRA transactions with no corresponding shipment status. (If from wholesale assets, both a shipment status and MRA are required.) Army 30 Jan 2014 19 Sep 2014 10 Dec 2014 Open No updates received