Container Automation and Air Waybill Automation in CW1 are automated services that feed each consolidation with routing dates and container dates. These dates play a significant role in consolidation and shipment visibility and the overall user experience in Logixboard.
This document briefly outlines the most important Container Automation / AWB Automation dates, the mechanics of setting up Container Automation & AWB Automation subscriptions on consolidations, and an overview of workflow events that represent the status of Container Automation and AWB Automation on each consolidation.
Ocean Consolidations - CW1 Container Automation
Container Automation Events
These are some of the main routing and container dates that load onto each ocean consolidation via container automation. Details about what roles these dates play in each shipment status in Logixboard can be found in this document.
ETD, ATD, ETA, ATA: Routing leg estimated and actual departures and arrivals.
GIN & GOU: Empty and full container Gate In and Gate Out.
PUP & DLV: Individual container pickup and delivery on the consolidation.
How to Activate Container Automation
Container automation activates as soon as the 3 fields listed below are entered on the consolidation. No other configuration is necessary.
1. Carrier Organization
The carrier organization must be entered on the Organizations subtab of the Details tab of the consolidation, as well as any relevant SEA routing legs. These fields are highlighted in the screenshots below.
2. Carrier Organization - SCAC Code
The carrier organization must also be configured with a SCAC code listed as code type ‘CCC’ on the Registration Numbers / Codes subtab of the organization (Organization → Details → Config → Registration Numbers/Codes).
A list of SCAC codes for the most common ocean carriers can be found at the end of the following CargoWise Update Note.
Additionally, the CW1 shipping line code (C1C code) should be entered on the Shipping Line/NVOCC/Agent subtab (Organization → Carrier → Configuration → Shipping Line/NVOCC/Agent). This code does not play a direct role in Container Automation, however, it is a good practice to configure the carrier organization with it as it gets validated during other processes such as electronic ocean bookings or shipping instructions.
The code can be looked up via the ‘...’ search button, using the SCAC code search filter.
3. Carrier Booking Ref/MBL
The other mandatory field for a successful container automation subscription is either the master bill of lading or the carrier booking reference number. Either one of these values will be sufficient for the subscription, but they can also be entered simultaneously.
Customs Declarations - CW1 Container Automation
Container automation on standalone customs declarations works the same way as on ocean consolidations. As soon as the ocean bill of lading and the carrier organization are entered, a container automation subscription will be created.
Air Consolidations - Air Waybill Automation
Estimated and Actual arrival and departure dates also load automatically to air consolidations via a similar process called Air Waybill Automation.
No special setup is required in order to receive Air Waybill Automation events. Just add the Master Air Way Bill (MAWB) and flight details to the consolidation, and the air consolidation will be automatically subscribed for AWB Automation. The list of airlines currently supported for AWB automation can be found here.
Container Automation / AWB Automation Subscription
CargoWise will attempt to create a Container Automation or AWB Automation subscription as soon as the mandatory fields listed above are entered on the consolidation. There are three distinct workflow events on the consolidation that indicate whether the subscription has been sent and accepted, after which the routing and container dates will automatically load on the consolidation.
SBR - Subscription Requested. This event indicates that the carrier and the MBL or the Carrier Booking Ref. have been entered on the consolidation and a container automation subscription has been requested. This does not indicate an active subscription yet, however, the mandatory fields have been entered.
IRA - Interchange Receipt Acknowledged. This event indicates that all mandatory details for container automation are valid and an active subscription has been created for the consolidation as well as each container. All relevant container and routing dates will now begin to load on the consolidation.
IRA - Interchange Rejected. This event indicates that a subscription was requested by CW1 but could not be accepted. The event reference will contain additional details about why the subscription was rejected. Chapter 2.2.1 of the container automation troubleshooting document contains additional details about the IRJ event and its mechanics.
Routing Legs - Validation
The vessel and aircraft routing dates (ETD, ETA, ATD, and ATA) are some of the most valuable data loaded by container and AWB automation. As soon as these dates are loaded on the consolidation, CW1 will attempt to write them on the corresponding routing legs, listed on the Routing tab of the consolidation. These are the fields that have to be valid for this data to populate successfully.
Ocean Consolidations
CW1 validates the UNLOCO of the inbound DEP and ARV events and compares them to the UNLOCO of the load and discharge ports of each routing leg. In other words, the LOC parameter in the event reference of the date that comes through automation has to match the UNLOCO of the load and discharge ports of each routing leg. The screenshot below demonstrates this example further.
Air Consolidations
The validation on air consolidations considers additional parameters besides the UNLOCO.
UNLOCO: Like on ocean consolidations, the LOC parameter in the event reference of the date that comes through automation has to match the UNLOCO of the load and discharge ports of each routing leg.
Flight Number: The VFL parameter in the event reference of the date that comes through automation has to match the flight number listed on each routing leg.
Flight Date: The FDT parameter in the event reference of the date that comes through automation has to match the ETD and ETA listed on each corresponding routing leg.
