USC-8_Att_1_EDI_Reports_DRAFT_Dec_14.pdf

USC-8 Attachment 1 – Electronic/EDI Reporting

Electronic / EDI Reporting

Shipment Status Reporting: The Contractor shall provide accurate shipment status reports using the 315 transaction sets. Transaction sets shall be submitted in accordance with the Department of Defense (DoD) Transportation Electronic Business (DTEB) Implementation Convention (IC) ANSI X-12 EDI standard or via IBS OCI to SDDC.

Table 3.A.10.3.1 identifies specific events that require reporting. The Contractor shall submit all reports within 24 hours of accomplishment.

Table 3.A.10.3.11 of Reportable Shipment Status Events

CODE DEFINITION NOTES

EE Empty spotted Container pick up in lieu of actual spot is acceptable for shippers having container pools. Required for other than pool locations.

(NOT REQUIRED FOR BREAKBULK)

W Pickup of Loaded Container/Breakbulk

This transaction is required at the time customer turns over possession to Contractor. This transaction is only applicable upon Contractor pick-

up. There should be exactly one W transaction per shipment. If erroneous W transactions are submitted, contractor shall invalidate them via the Pipeline Asset Tool (PAT) EDI invalidator tool to ensure only one valid transaction is reflected per shipment.

I In-gate at Port of Embarkation (POE)

This transaction is required at the POE. This transaction is only applicable at the POE. There should be exactly one (1) transaction per shipment. If erroneous I transactions are submitted, contractor shall invalidate them via the Pipeline Asset Tool (PAT) EDI invalidator tool to ensure only one valid transaction is reflected per shipment.

AE Loaded on Vessel This transaction is required at the POE and required at all transshipment ports.

VD Vessel Departure This transaction is required at POE and required at all transshipment ports.

VA Vessel Arrival This transaction is required at the Port of Debarkation (POD) and required at all transshipment ports.

UV Vessel Discharge This transaction is required at the POD and required at all transshipment ports.

OA Out-gate from POD This transaction is required at the final POD for all cargo, regardless of whether booked to port or to door. This transaction is only applicable at the POD. Only one OA transaction is permitted per shipment. If erroneous OA transactions are submitted, contractor shall invalidate them via the Pipeline Asset Tool (PAT) EDI invalidator tool to ensure only one valid transaction is reflected per shipment.

X6 Waypoint This transaction is required (when the Daily ITV accessorial is ordered and) for cargo is transiting the Northern Distribution Network and Pakistan Ground Line of communications (PAKGLOC). This transaction will be auto-generated based on Contractor date input to the Carrier In Transit Visibility Entry Tool (CIET) to document a shipment passing specified waypoints along the route.

AV Cargo Booked to- Door Available for Delivery (Applicable to Exigency areas only; Optional Transaction)

For Exigency Areas only, and only for bookings to-door; the Contractor may submit an AV request upon entering in line outside the final destination gate to document accrual of driver wait time, if applicable.

AV, for these locations only, is valid only if submitted prior to RDD for metric purposes.

AV Cargo Booked to- Port Available for Delivery; Optional Transaction)

For bookings to-port; the Contractor may submit an AV if all 3 of following conditions have been met (a) Contractor has completed any Customs-clearance actions required of Contractor, and (b) Breakbulk that was flatracked/containerized for carrier’s convenience has been stripped from the flatrack/container and is ready for loading onto the Government-arranged truck, and (c) Contractor has submitted all required notifications to SDDC and/or consignee that cargo is at POD ready for pickup.

EC Return of Empty Container to Contractor Prior to Delivery (X1)

This transaction is required for container shipments when the Contractor has regained possession of its asset prior to delivery (X1). An example of the proper use of an EC Code would be when cargo is deconsolidated at a transship point, the container is returned to the Contractor prior to X1, and the cargo is moved as pallet loads to the final consignee. Each container shipment container return event should be documented with either an RD or an EC but never both.

(NOT REQUIRED FOR BREAKBULK)

X1 Delivery to Consignee

This transaction is required when shipment is delivered to customer, or possession is turned over to the USU.S. Government. This transaction is only applicable upon actual physical delivery. There should be exactly one X1 transaction per shipment. If erroneous X1 transactions are submitted, contractor shall invalidate them via the Pipeline Asset Tool (PAT) EDI invalidator tool to ensure only one valid transaction is reflected per shipment.

RA Carrier Notified Empty Container Available for Pick-up

This transaction will be auto-generated via PAT to document USGU.S.

GovernmentSG notification to the Contractor that an empty container is available for pick-up. This transaction will be auto-generated based on the date of notification, if the Contractor does not dispute availability within seven (7) days of notification.

(NOT REQUIRED FOR BREAKBULK)

RD

Return of Empty Container to Contractor After Delivery (X1)

This transaction is required for every container shipment when the contractor regains possession of its asset after delivery (X1). Each container shipment container return event should be documented with either an RD or an EC but never both.

(NOT REQUIRED FOR BREAKBULK)

HG Entry into USU.S.

Government-directed Staging

This transaction will be auto-generated based on Contractor date input to the PAT Delay Request and Authorization Portal (D-RAP) after receiving and executing USU.S. Government direction to stage a shipment, to include staging at ports or holding yards. The transaction will be auto-generated based on the date the shipment entered into staging.

HR Release from USU.S.

Government-directed Staging

This transaction will be auto-generated based on Contractor date input to the D-RAP after receiving USU.S. Government direction to end staging of a shipment, to include staging at ports or holding yards. The transaction will be auto-generated based on the date the shipment exited staging.

SD Authorized Shipment Delay (Not caused by the USU.S.

Government)

This transaction will be auto-generated upon USU.S. Government approval of a Contractor requested delay submitted via the D-RAP. This transaction will be triggered for delays which are not caused by the US government. U.S. Ggovernment.

BD End of Authorized Shipment Delay (Not caused by the

USU.S.

Government)

This transaction will be auto-generated upon USU.S. Government approval of a Contractor request to end a shipment delay submitted via the D-RAP. This transaction will be triggered for delays which are not caused by the US government). U.S. governmentGovernment).

A1 Authorized Shipment Delay (Caused by the USU.S.

This transaction will be auto-generated upon USU.S. Government approval of a Contractor requested delay submitted via the D-RAP.

This transaction will be triggered for delays which are caused by the US

Government) government. U.S. Ggovernment.

A2 End of Authorized

Shipment Delay (Caused by the

USU.S.

Government)

This transaction will be auto-generated upon USU.S. Government approval of a Contractor request to end a shipment delay submitted via the D-RAP. This transaction will be triggered for delays which are caused by the US government. U.S. Ggovernment.

Additional Rules for AV Transactions for cargo booked to door

AV transactions for cargo booked to door are permitted for Exigency Areas only.

AV is a required transaction to document accrual of driver wait time. AV may only be requested upon entering in line outside the gate at final destination. There are no other acceptable uses of AV for cargo booked to door. In the event that an AV transaction is not requested, the USU.S. Government will assess that driver wait time was not incurred at final destination for the associated shipment. AV transactions submitted for these locations will be considered in measuring RDD compliance.

Once AV has been submitted, the contractor may not request a delay for that cargo. Staging direction may occur after AV has been submitted, which must be initiated by the USU.S. Government.

Additional Rules for AV Transactions for cargo booked to port

AV transactions for cargo booked to port are permitted only after contractor has completed all its responsibilities with regards to the cargo so that it is releasable to the GovernmnetGovernmentnmnet, including but not limited to Contractor responsibilities with regards to Customs Clearance, notifications to Government that cargo is ready for pickup, and removal of cargo from carrier equipment (flatrack/container) for breakbulk cargo flatracked/containerized for Ccarrier convenience.

Additional Rules for HG/HR Transactions

HG and HR transactions: The HG and HR transactions will be auto-generated by the D-RAP based on Contractor input in D-RAP to indicate start and stop of USU.S. Government-directed staging, to include staging at ports or holding yards. Authority for staging is the SDDC cognizant Contracting Officer Representative (COR)COR.

HG: Following receipt of a written USU.S. Government staging request via the D-RAP, the Contractor will execute movement of the shipment to the staging location. Within 24 hours of entry into the staging location, the Contractor will input the date of entry into the D-RAP. As a result of the date input into the D-RAP, the HG transaction will be auto-generated and distributed.

HR: Following receipt of a written USU.S. Government staging release (e.g. call forward) via the D-RAP, the Contractor will execute movement of the shipment from the staging location. Within 24 hours of departure from the staging location, the Contractor will input the date of departure into the D-RAP. As a result of the date input into the D-RAP, the HR transaction will be auto-generated and distributed. Cargo must commence dispatch from staging within required timelines outlined in Section 3.G.6 or Section 6.E upon receipt of written USU.S. Government request. For large volumes of cargo, contractor will be responsible for managing dispatch in the most expeditious manner. Contractor will provide dispatch timelines to cognizant BNBattalionsN and COR until cargo has dispatched from staging area.

The HG/HR transaction pair, generated via the D-RAP, may recommit the Contractor to a new delivery date defined as: RDD + (# days elapsed between HG and HR). For a shipment RDD to be potentially amended, both an HG and HR transaction must be generated.

If an onward movement EDI is submitted prior to the direction to end the staging is transmitted, the D-RAP will queue the staged shipment record for auto-closing. If an end staging direction is not sent within 96 hours of the queuing of the shipment record for auto-closing, an HR transaction ending the staging will be auto-triggered by the

D-RAP. The HR event date will equal the event date of the onward movement EDI and the RDD will be adjusted accordingly.

Additional Rules for SD/BD/A1/A2 Transactions

SD, BD, A1 and A2 transactions: The SD, BD, A1 and A2 transactions will be auto-generated by the D-RAP based on USU.S. Government approval to indicate start or stop of an authorized delay. These transactions will be auto-generated only upon authorization from the cognizant SDDC COR.

SD and A1: The Contractor shall submit a request for an authorized delay to the cognizant SDDC COR via the D- RAP within 2 business days of the event causing the delay. The SDDC COR has 2 business days to respond to the request from the Contractor via the D-RAP.

Following USU.S. Government authorization of a Contractor’s request for delay via the D-RAP, the SD or A1 transaction will be auto-generated and distributed. If an authorization is not approved or denied by the SDDC COR in the D-RAP within 2 business days, the SD or A1 transaction will be auto-generated and distributed. The Contractor must submit supporting documentation with the delay request submitted via the D-RAP. The COR may void the delay authorization if supporting documentation with adequate justification is not provided.

BD and A2: The Contractor shall submit a request to end the authorized delay via the D-RAP with supporting documentation. Following USU.S. Government authorization of a Contractor’s delay end via the D-RAP, the BD or A2 transaction, as applicable, will be auto-generated and distributed. If the SDDC COR determines that the Contractor’s reporting of the delay duration is inflated, the delay authorization may be voided. If an onward movement EDI is submitted prior to the request to end the delay, the D-RAP will queue the delayed shipment record for auto-closing. If an end delay request is not submitted within 96 hours of the queuing of the shipment record for auto-closing, a BD or A2 transaction ending the delay will be auto-triggered by the D-RAP. The BD or A2 event date will equal the event date of the begin delay SD or A1 transaction, as applicable, resulting in no adjustment to the shipment RDD.

The SD/BD and A1/A2 transaction pairs generated via the D-RAP may recommit the Contractor to a new delivery date defined as: RDD + (# days elapsed from SD/A1 to BD/A2). For a shipment RDD to be potentially amended, both an SD and BD or A1 and A2 transactions must be authorized and generated via the D-RAP.

Determination of whether a delay is USU.S. Ggovernment caused or not USU.S. Ggovernment caused will be made by the USU.S. Government COR approving the delay request. A guide to what will be considered a U.S.

Government (USG) vs non –U.S. Government (non-USG) delay is provided:

Border Closure Non-USG Cargo Discharge/Load Delay at Terminal Either USG or non-USG, depending on circumstances Constructive Staging USG Country Clearance Issue Either USG or non-USG, depending on circumstances Customs Issues Either USG or non-USG, depending on circumstances Delivery Scheduling USG DIP Note Issues Either USG or non-USG, depending on circumstances Foreign-Govt. Imposed Travel Restriction Non-USG Holiday Non-USG Inclement Weather Non-USG Insufficient Space For Cargo Non-USG Missing Cargo Details Either USG or non-USG, depending on circumstances Missing Documentation Either USG or non-USG, depending on circumstances Missing Health Certificates Either USG or non-USG, depending on circumstances Missing LEW Either USG or non-USG, depending on circumstances Pickup Issue/Shipper Not Ready USG

Port Authority Non-USG Port Closed Non-USG Port Congestion Non-USG Road Impassable Non-USG Tax Clearance Non-USG Terrorist Threat Non-USG Unavailable Equipment at Port Either USG or non-USG, depending on circumstances Vessel Labor Issue Either USG or non-USG, depending on circumstances VET Certificate Revision By Shipper USG