1. Opening Remarks and Welcomes
Introductions
Meeting Courtesies
Heidi on site, in person; she will go first, then Paul Blackwell; Heidi – what is the takeaway for each agenda item? Include in minutes
Tonja will take the lead in the room, Joanne will chime in via phone/DCS
WARFIGHTER FIRST 1

2. Agenda Meeting Ground Rules Facility J6 Non-Negotiables: Empower
Communication Minute
Background
Logistics Pipeline Dashboard
Topics for the PM PRC
Improper Discrepancy Codes Affect Performance Analysis
Proposed DLMS Change (PDC) Updates to DLM , Defense Logistics Management Standards, Volume 6, Logistics System Interoperability Support Services; Chapter 4, Pipeline Measurement
WARFIGHTER FIRST 2

3. Agenda (Cont.) PDC 1038A - LMARS Sub Category OTHER Change
Approved DLMS Change (ADC) 1025E - Provide Navy Unit Mobile Data and Update COCOMs, CONUS and OCONUS LMARS Data into the Logistics Metrics Analysis Reporting System (LMARS)
ADC 1025F - Approved Addendum for ADC 1025C Administrative Update of Air Force Routing Identifier Codes (RICs) in Logistics Metrics Analysis Reporting System (LMARS)
ADC Approved Defense Logistics Management Standards (DLMS) Change (ADC) 1264 Contract Number for Planned DVD Transactions under LMARS
LMARS Reports
LMARS Anomaly Code List
Way Ahead
WARFIGHTER FIRST 3

4. Meeting Ground Rules Do not place phone on hold
Mute phone when not speaking
Silence cell phones
Limit side conversations
Identify speaker; speak clearly and concisely
Stay focused on the topic under discussion
Respect differing views
Table parking lot issues for future discussion
WARFIGHTER FIRST 4

5. Facility Restrooms Coffee/Tea Restaurants
- Deli/Salad – Located on the 1st floor
- Local restaurants – short drive
WARFIGHTER FIRST 5

6. Non-Negotiables
Heidi – the Non-negotiables are DLA J6 – but we use them because we think they're useful
WARFIGHTER FIRST 6

7. Communication Minute
WARFIGHTER FIRST 7

8. DEFENSE LOGISTICS AGENCY THE NATION’S COMBAT LOGISTICS SUPPORT AGENCY
PM PRC
September 20, 2018
WARFIGHTER FIRST

9. Background
Provides a single authoritative source of Logistics Response Time (LRT) across the enterprise
Tracks materiel as it moves through the logistics pipeline and reports the associated response times.
Enables components to track trends and provides leadership the ability to measure actual performance against Time Definite Delivery (TDD) standards
Begins with customer submission of an order and results with the receipt of the ordered materiel
There are 12 measureable logistics pipeline segments. All reporting time frames are in terms of days.
Maintains data from its inception February Standard reports are available (via the web) on a monthly basis.
Volume 6, Logistics Systems Interoperability Support Services; Chapter 4, Pipeline Measurement in DLMS
DoDM DoD Supply Chain Materiel Management, Volumes 4, 8, 10 lay the foundation for Pipeline Measurement
WARFIGHTER FIRST

10. Logistics Pipeline Dashboard
Customer Requisition Lifecycle Events
Inventory Control Point Supply Processing Time (ISPT-Node)
Storage Activity Processing Time (ISPT-NODE)
In-Transit / In-Theatre Processing Time (ITIT-NODE)
Container Consolidation Point (CCP) Processing Time (CPT-NODE)
Requisition Submission Time (RST-NODE)
Service Processing Time (SPT-NODE)
Depot to Container Consolidation Point (CCP) Processing Time
CCP/ POE CONUS In-Transit Time (CIT-NODE)
Port of Embarkation Time (POET-NODE)
In-Transit to Port of Debarkation (POD) Time (ITTT-NODE)
Port of Debarkation (POD) Processing Time (PODT-NODE)
Receipt Take up Time (RTT-NODE)
Theatre Segment Time
Transportation Segment Time
Storage Depot Segment Time
ICP Processing Time
Requisition Submission Time 1 11 12 2 3 4 6 7 8 9 10 5
Total Pipeline Time (TPT-NODE) 13
OCONUS
OCONUS 10

11. Logistics Pipeline Dashboard
Segment 1 – Requisition Submission Time – Is the elapsed time from the date in the requisition number to the date that it was received by Defense Automatic Addressing System (DAAS)
Segment 2 – Internal Service Processing Time – Is the elapsed time beginning when DAAS releases a requisition for internal service or non-Wholesale action and ending when the requisition is returned and released to a Wholesale ICP
Segment 3 - Inventory Control Point Processing Time - Measures the time from DAAS release of a requisition to an ICP, until DAAS receipt of an MRO transaction directing shipment
Segment 4 - Storage Activity Processing Time - Is measured from the date DAAS receives the MRO to the date shipped/released in an AS/AR/AU/856S (Shipment Status) transaction
Segment 5 - Storage Activity to Consolidation Containerization Point Processing Time - is measured from the date shipped/released (AS/AR/AU/856S) to the CCP, to the date received (TAV/TAW/856A) by the CCP.
Segment 6 - Consolidation Containerization Point Processing Time - Is measured from the CCP’s date of receipt until the date of release(TAV/TAW/856A)
WARFIGHTER FIRST

12. Logistics Pipeline Dashboard Cont.
Segment 7 - CONUS In-Transit Time - Measurement starts with date shipped (AS/AR/AU/856S) by the shipper (may be contractor, storage depot, or CCP) and ends on the date received (DRA/DRB/D6S) by a CONUS customer or port of embarkation (POE) for overseas movements
Segment 8 - Port of Embarkation Processing - Is measured from the date of POE receipt to the date of POE release
Segment 9 - Port of Embarkation to Port of Debarkation In-Transit Time - Is measured from POE date of release to port of debarkation (POD) date of receipt
Segment 10 - Port of Debarkation Processing - Is measured from the date of POD receipt to date of POD materiel release
Segment 11 - In-Theater In-transit Time - Is measured from the POD release date to the consignee receipt or “tailgate” date, for all OCONUS areas
Segment 12 - Receipt Take-Up Time - Is the time between consignee receipt or “tailgate” date and the record posting date in the DRA (DLMS 527R) or DRB (DLMS 527R)
Total Pipeline Time is measured from the date in the requisition number (start of segment 1) to the date the customer posts it to the property record (end of segment 12)
WARFIGHTER FIRST

13. Topics for the PM PRC USTRANSCOM
Concerns with Navy reporting DRB transactions
Issue was addressed during Supply Chain Metrics Group
Components need to implement ADC 1114 and ADC 474
ADC Created MRA (Materiel Release Acknowledge) Discrepancy Code G
Discrepancy Code G only applicable to Navy DoDAACs beginning with V and R
This code was to identify Navy ships out of port and have not had the opportunity to pick-up their order
Navy Ships using Discrepancy Code G must be in receipt of Supply Status NL which indicates the material has been received by Navy Local Logistics Support Center (LSC) or Materiel Processing Center (MPC)
When ICP receives Discrepancy Code G, this allows to keep order open and the ICP will trigger another MRA follow up after 45 days have passed. Up to six MRA’s with Discrepancy Code G may be submitted
Prior to ADC 474, Navy was using Discrepancy Code F to identify these ships which resulted in skewed LRT metrics and DLA believing the order was missing
WARFIGHTER FIRST 13

14. Topics for the PM PRC
ADC 1114 Automated follow-up for delinquent materiel receipt acknowledgment (MRA) transactions
Revised MRA Follow-Up timeframes to align with TDD standards for delivery of materiel
Timeframes are based on the COCOM Region for transportation category
New Discrepancy Code of H to identify materiel still in transit
Use for MRA Reply to Follow-Up when responding to an MRA Follow-Up and the Component research identified that the materiel is still in transit.
The reporting activity may send up to six MRA transactions in response to follow-up, using MRA Follow-up transactions with Discrepancy Indicator Code H
WARFIGHTER FIRST 14

15. Improper discrepancy codes affect performance analysis
MAJ Dereck K. Wilson, TCJ4-LM
20 September 2018
Together, we deliver.

16. The Issue
When distribution timeframe is longer than expected and DRB response is received with “F” discrepancy code, an Incorrect material receipt date is recorded in LMARS
Data field still labelled as a “D6S” but date represents the first DRA or DRB recorded by LMARS
Slower transportation methods or poor performers with extended Logistics Response Time (LRT) are impacted the most
This issue will continue to occur until Services update their supply systems to implement new discrepancy codes (see ADC 474 and 1114), estimated for 2020 completion
Current SDDB-enhanced enforces time ordered process start / stop times therefore all distribution activities after the Incorrect D6S are blocked / not included in processed data
All valid process dates after Incorrect D6S are not included in SDDB-enhanced
These Incorrect D6S dates limit distribution performance analysis and result in aggregate performance actually reported better than reality (LRT times should be longer than reported)
Together, we deliver.

17. Identification of Incorrect D6S in SDDB
Determined a method to identify Incorrect D6S dates by comparing D6S dates of closed requisitions from SDDB-enhanced to DAAS data in IGC
⁻ Analysis looked for DRB with F discrepancy code as the first DRA or DRB recorded
⁻ Calculated against 12 months of SDDB closed requisitions (July June 2018)
Total requisition count and percent of Incorrect D6S dates summarized by transportation mode and Service with greatest impact to Ocean for Air Force and Navy
Jul17-Jun18
Air Force
Army
Marines
Navy
Total
# Reqs Incorrect D6S
Mode
% D6S
Incorrect
# Reqs
CONUS
1.9%
1,589,088
0.9%
1,693,147
0.3%
369,796
2.4%
2,001,140
Comm'l Air
13.0%
153,377
1.0%
348,673
37,042
3.6%
311,259
Military Air
9.8%
57,346
3.4%
288,422
3.0%
3,161
4.2%
42,592
Truck
5.7%
36,663
0.6%
138,820
18,355
2.3%
147,262
Grand Total
5.5%
1,921,050
1.3%
2,521,264
0.5%
447,928
3.1%
2,569,138
1.7% 5,653,171 94,724
4.1% 850,351 34,828
4.4% 391,521 17,297
29.6% 223,237 66,162
1.9% 341,100 6,314
2.9% 7,459, ,325
Ocean 55.8% 84, % 52, % 19, % 66,885
Together, we deliver.

18. Greatest Impact to Ocean
Chart shows when visibility is LOST due to early Material Receipt (Incorrect D6S)
- Incorrect D6S received most often during strategic transportation, when shipment is with USC carrier (Jan-Jun18)
Air Force
MRO to PODs = 68% Vol
Thru CSGNE AVAIL 29%
Source Supplier Transporter
Theater
Army*
MRO to PODs = 52% Vol
Thru CSGNE AVAIL 31%
Marines
MRO to PODs = 78% Vol
Thru CSGNE AVAIL 18%
Navy
MRO to PODs = 56% Vol
Thru CSGNE AVAIL 42%
*MRO to Carrier Pickup = 16%
Note: Limited visibility for "Consignee Available" is driven by lack of systems to collect timestamp (no more pRFID)
Together, we deliver.

19. Ocean Transporter Loss of Visibility Timeframe
All distribution process activities after the Incorrect D6S can not be analyzed
Recent six months (Jan-Jun18) of SDDB-E was analyzed to determine which Ocean transporter timestamps were missing due to being after the Incorrect D6S date
Data below measured requisitions in containers filled at DDSP/DDJC for all services
Data point on line shows how many requisitions lost visibility at that timestamp
Together, we deliver.

20. Backup
Together, we deliver.

21. Together, we deliver. SDDB: July 2017 – Jun 2018 Mode Method Air Force
Army
Marines
Navy
Total
% D6S
Incorrect
# Reqs
CONUS
Air Parcel Post
4.6%
43598
1.7%
110224
0.8%
21412
5.6%
55907
3.1%
231141
Air Sm Pkg
3.7%
432100
0.4%
460307
0.3%
110397
1.6%
767832
1.8%
Grnd Local
0.0%
750023
0.1%
28107
55935
442772
Grnd LTL
6.0%
21333
32750
0.7%
7447
4.8%
19924
81454
Grnd Scheduled
2.3%
46644
1.1%
731632
0.2%
106286
5.7%
321313
Grnd Sm Pkg
257377
295002
60929
294026
1.9%
907334
Other
3.6%
38013
35125
0.6%
7390
99366
4.2%
179894
Comm'l A
CAT A
36.2% 69
5.1%
21466
12.5% 32
212
5.2%
21779
Comm Express
13.0%
153308
327207
37010
311047
4.1%
828572
Military A
MILAIR
8.7%
52910
2.0%
47368
1.5%
1954
42109
144341
MILALOC
22.3%
4436
241054
5.3%
1207
483
4.0%
247180
Ocean
Ocean (DDSP/DDJC)
50.4%
67905
6.4%
49134
3.0%
19507
22.0%
61399
26.0%
197945
Ocean NIMH
78.2%
16671
6.6%
3068 67
27.4%
5486
58.3%
25292
Truck
Local Truck
6169
33441
15649
100744
1.3%
156003
Other Truck
14.4%
748
0.9%
6583 84
2633
10048
Scheduled Truck
6.3%
29746
0.5%
98796
2622
3.9%
43885
2.4%
175049
Grand Total
5.5%
1.3%
0.5%
3.1%
2.9%
SDDB: July 2017 – Jun 2018
Together, we deliver.

22. Topics for the PM PRC Output Report Specific Tables
Table A: Validate the two backorders codes
Table B: Explanation on how Army is processing Off-Line requisitions (DIC: BE9)
Table C: Validate fund codes with the Navy for “Initial Outfitting Requisition”
Table D: Validate Wholesale Inventory Control Points
ADC 1025F implemented for AF RICs
AF advised their RICs change often, so the ADCs rolled out from LMARS are typically outdated due to this
Table E: Equivalent DIC A5 (Materiel Release Order (MRO) transactions
Table F: Validate cancellation and rejection status codes
Table G: Validate DLA’s PMV, MRO, Perishable & Semi-perishable Computational Rules
Table H: Validate Service and/or Report Affiliation
These Tables (and the Anomaly file) are posted on the EBSO website. Click “Quick Links” and navigate to the PM PRC Committee page, or use this hyperlink:
WARFIGHTER FIRST 22

23. Topics for the PM PRC
Table A - Other Backorder Status Codes. This table is used to determine when the status of a document is backordered
Component
Code(s)
Navy
N7, NF
Table B - Requisition transaction identifiers: This table is used to determine which transactions are requisitions
Component
Code(s)
All
A0_, AM_ (if no A0/AT on file)
Army
AT_, BE9 (RP30 = A, C, W)
Navy
A4_, AT_, D7_ (RP30 = N, Q, R, V)
Air Force
A3_AT_, (RP30 = E, F, J)
Marine Corps
A3_, AT_ (RP30 = L, M)
DLA
CH1, CHA, D7_
GSA
CH1, CH
WARFIGHTER FIRST 23

24. Topics for the PM PRC
Table C - Initial Outfitting Requisition details: This table is used to identify document numbers that are for initial outfitting so they can be excluded from LMARS reporting
Component
Code(s)
Army
Total Package Fielding transactions BAY, BAZ
Navy
N, R, V in RP30 with N0, NO, QZ, V0, V7, VO in RP52-53
N, R, V in RP30 or RP 45 with 721 in RP57-59
Air Force
E, F in RP30 & to or from FFF, FG6, FH6, FL6, FP6
Marine Corps
M98835 in RP45-50
Table D - Wholesale Inventory Control Points: Identifies ICP Routing Identifier Codes
Component
Code(s)
Army
A12, A35, AKZ, AP5, B14, B16, B17, B64, B69, BAM, BR4
Navy
N52, NFZ, NRP
Air Force
F74, F77, F8U, F01, F06, F08, F13, F16, F24, F28, F2U, F46, F4U, F52, F59, F63, F78, F79, F81, F83, FG5, FGL, FGZ, FHZ, FL5, FLZ, FPD, FZZ, F25, F98
Marine Corps
LC3, MPB, MHQ
Coast Guard
ZNC, ZQC
DLA
SMS
GSA
USSOCOM
H9D, H92
WARFIGHTER FIRST 24

25. Topics for the PM PRC
Table E - Equivalent A5 (MRO) transactions: Identifies document identifier codes that equate to standard material release order
Component
Code(s)
Army
B99
Navy
A4_, D7_
Air Force
A2_, BF7
J/TAV
A4 with 2 or 3 in RP54
Table F - Other cancellation and rejection Status Code
Component
Code(s)
Army
A2, A5, A6, A7
Navy
R1 through R6, R9, RA through RH,
RJ through RL, RN, RP, RR, RT, RU, RY, RZ
Air Force
F2 through F6, F8, FB, FF, FG,
FK through FP, FR, FS, FU,
FW through FZ, JA
WARFIGHTER FIRST 25

26. Topics for the PM PRC
Services can pick up the Anomaly File, which identifies issues for the service to resolve
Currently, Services are not using the Anomaly File
This file identifies errors within the component
Task the services to identify Anomaly Codes as an action item
LMARS technical support to provide specific training on Anomaly File
DLA Special Feeds
Special feed data from DLA Philadelphia –Monthly
FFV – Fresh Fruit and Vegetables
Semi Perishables
MRO – Maintenance, Repair, and Operations
PVM – Prime Vendor Medical
Is DLA working to automate this process?
What needs to be accomplished to automate the DLA Special Feeds?
Mary to provide training on anomaly file
Special Feeds are off-line requisitioning; is there impact to Finance? Coordinate with Bob Hammond re: finance impact John Graybill was our last POC on special feeds; need to follow up with him
WARFIGHTER FIRST 26

27. Topics for the PM PRC
Change the LMARS reports to show Priority opposed to Groups (GP1-GP3)
Current Reports say Group 1, Group 2, Group 3
In the future, the reports will reflect IPG1, IPG2, IPG3
IPG is identified in Chapter Four
Definitions of priority groups
-IPG1–PRI 01-03
-IPG2–PRI 04-08
-IPG3–PRI 09-15
Validate Navy DoDAACs on the LRT File, Field Description: The following Fields used to indicate records are used in LMARS (Only on records sent to activities)
Origin/Comments: Note: The TPT field may contain a “W” in place of an “X” or a “Z” instead of a “Y”. This indicates this record was NOT included in the 95% figures, i.e. it was part of the 5% records with the highest TPT time.
When Navy is a customer or when the ICP begins with an N, P, Q, or V (organization not = 09111, 09112, 09114, 09115, 09116, 09124, 09131, 09132, 09136, 09167, 09808, 52841, 55616, and )
Note: Indicators can be “X” or “Y’. A “Y” indicates that model value exceeds UMMIPS standards.
UIC: , – delete or not valid
WARFIGHTER FIRST 27

28. Topics for the PM PRC GSA LMARS Type of Fill Criteria are incorrect.
PDC needed to update Type of Fill.
Concerns with Planned/Unplanned/Other LMARS Sub Category
GSA Transaction logic not correctly started in LMARS
Discussions of removing all GSA form the Type of Fill Criteria and moving this to the third and fourth line (GSA would use Planned and Unplanned Only)
WARFIGHTER FIRST 28

29. Proposed DLMS Changes
Frank will upload flow chart.– done; added hyperlink to file.
Heidi or Drex will brief -- ??????
WARFIGHTER FIRST 29

30. PDC 1211
PDC 1211 Updates to DLM , Defense Logistics Management Standards, Volume 6, Logistics System Interoperability Support Services; Chapter 4, Pipeline Measurement
Update the entire DLMS Chapter to streamline the verbiage and update the LMARS Chapter
For LMARS, we have a committee that meets annually to discuss any metrics issues, concerns and identify if changes are required in support of the community
The LMARS committee has identified members, identified under ADC 1240, who are considered voting members
PDC 1211 was sent to the PMPRC community prior to our office staffing and working this change
PDC 1211 allows the enhancement of readability and incorporates administrative changes and policy updates related to pipeline metrics performance
Add way ahead as last bullet for ADCs
WARFIGHTER FIRST 30

31. PDC 1038A PDC 1038A LMARS Sub Category OTHER Change
The requirement on this change will clarify the LMARS Fill Type Sub-Sections currently defined as OTHER and update the LMARS Fill Rules
Currently, DIC CH_ Transactions is causing Logistics Response Time (LRT) to reflect incorrect timeframes due to these requisitions being considered post-post transactions opposed to immediate issue. Main issue is with DLA Kentucky Logistics Operation Center (KYLOC)
LMARS Sub-Categories are
-Total
-Immediate Fill
-Planned DVD
-Backordered
-Unplanned
-Other
WARFIGHTER FIRST 31

32. ADC 1025E
ADC 1025E - Provide Navy Unit Mobile Data and Update COCOMs, CONUS and OCONUS LMARS Data into the Logistics Metrics Analysis Reporting System (LMARS)
Update the COCOMS and utilize the CONUS/OCONUS indicator in addition to the Combatant Command (COCOM) feed from DAAS
Used to report LRT to all DoD Customers with the exception of Navy Mobile Units afloat identified in the AFLOAT File
For Navy Mobile Units afloat, the Navy provides via Secure File Transfer Protocol (SFTP) at the end of the third week of each month.
LMARS will access this file from DAAS for reporting LRT by identifying the COCOM delivery areas, specified by beginning and ending date for Navy Mobile Units
Supports the LRT Files in LMARS and associated the correct COCOMs with the correct CONUS/OCONUS Areas
WARFIGHTER FIRST 32

33. ADC 1025F
ADC 1025F - Approved Addendum for ADC 1025C Administrative Update of Air Force Routing Identifier Codes (RICs) in Logistics Metrics Analysis Reporting System (LMARS)
The LMARS Key Report Reference Table D (DAAS LMARS web page) provides RICs used by Service/Agencies in Logistics Pipeline Segment 3, “Inventory Control Point (ICP) Processing Time.”
ICP processing time measures the time from when DAAS releases a requisition to the ICP, until DAAS receives a Materiel Release Order transaction directing shipment
In order to maintain correct ICP each Component must verify the accuracy of its RICs in the LMARS Key Report Data Table D and update the table as necessary
This change updated the LMARS Report Data Table D and Updated the Air Force RICs
WARFIGHTER FIRST 33

34. ADC 1264
ADC 1264-Approved Defense Logistics Management Standards (DLMS) Change (ADC) Contract Number for Planned DVD Transactions under LMARS
This change resulted in the modification of new Federal Acquisition Regulation (FAR) and Defense Federal Acquisition Regulation Supplement (DFARS) that defined the PIID.
For DLA orders, LMARS derived the contract data from the DLMS 870S Supply Status transaction, which contained the contract number (PIIN) for indefinite delivery contracts and the associated call/order number.
Now that the PIID call order is independent, the supply status will no longer contain the base contract number. LMARS requires the code from both the base contract number and call order number for visibility of indefinite delivery contracts to identify planned vs. unplanned DVD shipments.
DLA EDI 850 Purchase Order retains its functionality to include both the base contract number and the call/order number contracts.
LMARS will extract the base contract number and call order number for contract data from the DLA EDI 850 but will still receive the DLMS 870S Supply Status.
This will allow LMARS to provide visibility of indefinite delivery.
WARFIGHTER FIRST 34

35. DEFENSE LOGISTICS AGENCY THE NATION’S COMBAT LOGISTICS SUPPORT AGENCY
LMARS Reports
WARFIGHTER FIRST

36. LMARS Output Reports C4.6.5. Output Reports. All
Reports are displayed in a
standard format. The titles of the
Major Report Categories, the
Sections, and the Sub-sections
are all centered on report pages.
Guard
Reserves
Wholesale ICP
Contractor Wholesale ICP
Wholesale ICP Reparables NSNs
ICP GSA
No goal exists for this metric due to dependency on other variables (TDDs, Supply Availability Goals etc.)
WARFIGHTER FIRST 36

37. Logistics Metrics Analysis Report System
Proposed Area to add IPG1-3 opposed to GP1-3
WARFIGHTER FIRST 37

38. LMARS Anomaly Code List
Tool to aid in evaluating suspect data
Complete anomaly file available every month
Only one anomaly identified for each record
Correcting one anomaly will correct many
Some transactions with anomalies reported
Some transactions with anomalies eliminated from reports
Links to the Anomaly Files in the following slides:
Anomaly Spreadsheet:
Anomaly counts:
Heidi – this is a good chart – single line bullets.
WARFIGHTER FIRST 38

39. LMARS Anomaly Code List
Error No.
Description
RST (1)
SPT(2)
ISPT(3)
SAPT(4)
DCPT(5)
CPT(6)
CIT(7)
POET(8)
ITTT(9)
PODT(10)
ITIT(11)
RTT(12)
TPT(13) 1
Error in Converting the Date of Birth
error x 2
Span Too Large between Serial Date and Date of Birth: Span > 365 days 3
Error Comparing Serial Date to Date of Birth: Date of Birth < Serial Date Serial date after date of birth 4
Error Converting Serial Date from The Document Number 5
Invalid Date - Materiel Release Order Date 6
Invalid Date - Required Delivery Date 7
Invalid Date - Status Receipt Date 8
Invalid Date - Available For Shipment Date 9
Invalid Date - Shipment Date Released Carrier 10
Invalid Date - Materiel Release Confirm Date 11
Invalid Date - DAAS Receipt Date 12
Invalid Date - MRAD Customer Date 13
Invalid Date - CCP Receipt Date 14
Invalid Date - CCP Shipment Date 15
Invalid Date - POE Receipt Date 16
Invalid Date - POE Lift Date
17   
Invalid Date - POD Receipt Date
Eyechart – Heidi: embed a link to the excel spreadsheet in the slide, and have hard copies in the room.
WARFIGHTER FIRST 39

40. LMARS Anomaly Code List
Error No.
Description
RST (1)
SPT(2)
ISPT(3)
SAPT(4)
DCPT(5)
CPT(6)
CIT(7)
POET(8)
ITTT(9)
PODT(10)
ITIT(11)
RTT(12)
TPT(13)
18 
Invalid Date - POD Shipment Date x
error 19
Invalid Date - MRAD Consignee Receipt Date 20
Invalid Date - Requisition Transmission Date 21
Invalid Date - LOTS Item Receipt/LRT-Terminate Date
delete 26
Invalid Combination of D7­_ (D7A, D7B, D7C) and To-Ric (N P Q R) 27
Invalid S9M Record - Project Code, Advice Code, or RDD invalid for S9M 28
Invalid S9T Record - Project Code or Advice Code invalid for S9T 29
Invalid Date - AR Confirmation Received Date 30
Invalid Date - Shipment Receipt Date 31
Invalid Date - D6S Receipt Date 32
Invalid Date - Stat1 Date Generated 33
Invalid Date - Stat2 Date Generated 34
Invalid Date - Stat3 Date Generated 35
Materiel Confirmation Date - Not Available for Shipment 36
D6S Received - No Customer Receipt Date 37
D6S Received - No DVD or POD OCONUS 38
D6S Received - No Shipment Date Posted 39
Navy Receipt and no Consignee Receipt Date
WARFIGHTER FIRST 40

41. LMARS Anomaly Code List
Error No.
Description
RST (1)
SPT(2)
ISPT(3)
SAPT(4)
DCPT(5)
CPT(6)
CIT(7)
POET(8)
ITTT(9)
PODT(10)
ITIT(11)
RTT(12)
TPT(13) 40
Invalid Date - Status 1 ESD Date
delete 41
Shipment Date Received - No Shipment Date Posted x
error 42
D6S Received - Before Shipment Date 43
Only an MRAD transaction was received at the DAASC
44   
Future Document - Serial Date is greater than Date of Birth
45   
No MRO, Shipment, or MRAD for a 2-year-old transaction
46   
No MRO Denial, Shipment, or MRAD for a MRO that is 90 days old
47   
Only an MRAD document was received at the DAASC
48   
Perishable record rejected, DoDAAC and Bill-to not active
n/a
49   
Shipped Date Previously Reported – No Update
50   
Consignee Receipt Date Previously Reported – No Update
51   
Receipt Date Previously Reported – No Update 52
No MSoS record for SMS document 53
Quantity to large for MilStrip format
n/a - not applicable
delete - error message no longer required
x - field is eligible to be reported
error - this field will not be reported
WARFIGHTER FIRST 41

42. Way Ahead
Discussion on the future PM PRCs
WARFIGHTER FIRST 42