C4.6.5.5.8. Spreadsheet Report Columns P and Q Logistics Pipeline Segment 8, (See C4.6.2.8.) “POE Processing” Report Spreadsheet Heading POE “8 – ACTIVITY” LMARS database name “POET – NODE”. POE receipt and release dates, provided by GTN or other In-Transit data transactions, are used to calculate OCONUS times. The average times and number of shipments processed by a POE will be shown. NOTE: For CONUS Area reporting where the source of materiel is in the CONUS and the Customer delivery point is in the CONUS, these columns will be blank, since CONUS shipments move don’t through CCPs, POEs, or PODs. C4.6.5.5.9. Spreadsheet Report Columns R and S Logistics Pipeline Segment 9, of Embarkation to Port of Debarkation “Port (See C4.6.2.9.) Time” Report Spreadsheet Heading POE to Port of Debarkation “9 – (POD)” LMARS database name “ITTT – NODE”. Measurement is from POE release to POD receipt. IGC provides the transactions needed to calculate this times. DLMS or other In-Transit segment’s data transactions, if available, may also be used. Times and numbers for these columns are shown similar to the previous segments. NOTE: For CONUS Area reporting where the source of materiel is in the CONUS and the customer delivery point is in the CONUS, these columns will be blank, since CONUS shipments not move through CCPs, POEs, or PODs. don’tdo C4.6.5.5.10. Spreadsheet Report Columns T and U Logistics Pipeline Segment 10, (See C4.6.2.10.) “POD Processing” Report Spreadsheet Heading POD “10 – Activity” LMARS database name “PODT – NODE”. IGC provides transactions with the POD receipt and release dates/times needed to calculate the OCONUS entries shown for this segment. NOTE: For CONUS Area reporting where the source of materiel is in the CONUS and the Customer delivery point is in the CONUS, these columns will be blank, since CONUS shipments do not move through CCPs, POEs, or PODs. don’t
C4.6.5.5.8. Spreadsheet Report Columns P and Q Logistics Pipeline Segment 8, “POE Processing” (See C4.6.2.8.) Report Spreadsheet Heading “8 – POE ACTIVITY” LMARS database name “POET – NODE”. POE receipt and release dates, provided by GTN or other In-Transit data transactions, are used to calculate OCONUS times. The average times and number of shipments processed by a POE will be shown. NOTE: For CONUS Area reporting where the source of materiel is in the CONUS and the Customer delivery point is in the CONUS, these columns will be blank, since CONUS shipments don’t move through CCPs, POEs, or PODs. C4.6.5.5.9. Spreadsheet Report Columns R and S Logistics Pipeline Segment 9, “Port of Embarkation to Port of Debarkation Time” (See C4.6.2.9.) Report Spreadsheet Heading “9 – POE to Port of Debarkation (POD)” LMARS database name “ITTT – NODE”. Measurement is from POE release to POD receipt. IGC provides the transactions needed to calculate this segment’s times. DLMS or other In-Transit data transactions, if available, may also be used. Times and numbers for these columns are shown similar to the previous segments. NOTE: For CONUS Area reporting where the source of materiel is in the CONUS and the customer delivery point is in the CONUS, these columns will be blank, since CONUS shipments don’tdo not move through CCPs, POEs, or PODs. C4.6.5.5.10. Spreadsheet Report Columns T and U Logistics Pipeline Segment 10, “POD Processing” (See C4.6.2.10.) Report Spreadsheet Heading “10 – POD Activity” LMARS database name “PODT – NODE”. IGC provides transactions with the POD receipt and release dates/times needed to calculate the OCONUS entries shown for this segment. NOTE: For CONUS Area reporting where the source of materiel is in the CONUS and the Customer delivery point is in the CONUS, these columns will be blank, since CONUS shipments don’t do not move through CCPs, POEs, or PODs.
03%20PDC_1211_DLMS_Vol6_Ch4.docx