CSMS# 12-000002 - New Arrival Functionality in ACE M1
U.S. Customs and Border Protection sent this bulletin at 01/11/2012 12:57 PM ESTYou are subscribed to Automated Broker Interface for U.S. Customs and Border Protection. This information has recently been updated, and is now available.
01/11/2012 12:53 PM EST
Automated Broker Interface
New Arrival Functionality in ACE M1
On December 14, 2011, as part of the ACE eManifest:Rail and Sea (Drop M1) deployment, new functionality was deployed that impacts arrival processing in the Ocean mode of transportation for carriers using both ACE M1 and AMS. The net effect is that the correlated arrival process in ACE M1 is now enabled and will perform arrivals on all manifests received, including manifests it receives from AMS. The dual processing between ACE M1 and AMS ensures that events generated from ACE M1 should be sent to AMS participants. Please note that some issues have already been identified with this process and that these issues are being fixed. These fixes will be communicated when available.
The arrival process steps and conditions are listed below.
1 ACE M1 correlates all Manifests received by “Unique Voyage Identifier” (UVI) data element. All manifests identified as associated with the same UVI arriving at a specific port of arrival are correlated. (NOTE: This data element, although available, has not been defined by CBP or trade partners and is not yet in use)
2 ACE M1 correlates all Manifests received by Stowage Plan. All manifests identified as associated with a vessel arriving at a specific port of arrival are correlated.
When the Arrival is performed:
a. Via EDI by actual vessel operating carrier or
b. By CBP Officer using CBP interface
3a ACE M1 arrives all manifests correlated in steps 1 and 2 with the vessel arriving at the port. This establishes the date and time of arrival in ACE.
c. When the manifest/Master BOL is arrived all House BOLs associated with that arrival are also arrived (same as current AMS process)
d. In-bonds associated with the Manifest/BOL are arrived and the in-bond clocks are started
e. Entries associated with the Manifest/BOL are arrived and the entry clocks are started
f. General Order clocks are started for all unentered BOLs associated with the arrival at the port of unlading.
g. ACE (M1) updates the status of all BOL(s) of type FROB to ‘closed’ if no holds exist on the BOL
h. ACE (M1) updates the status of all BOL(s) of type “Empty” to ‘closed’ if no holds exist on the BOL.
4a ACE M1 sends out arrival notifications for all arrived manifests and BOLs. All arrival notifications in ACE M1 are sent to AMS for distribution to AMS partners.
a. ACE (M1) generates Conveyance Arrival notification (AAD) to the each Carrier that filed manifest on the Conveyance. AMS will send to non-pilot participant.
b. ACE (M1) generates “Conveyance Arrival” notification (19) for designated Brokers specified on each arrived BOL. AMS or ACS will send to non-pilot participants as appropriate.
c. Notifications withheld until Arrival will be released. AMS will send to non-pilot participant.
When the Arrival is Performed by a Carrier other than the Vessel Operator
3b ACE M1 arrives only the manifest associated with the carrier that is arriving at the specified port. This establishes the date and time of arrival in ACE.
a. When the manifest/Master BOL is arrived all House BOLs associated with that arrival are also arrived (same as current AMS process)
b. In-bonds associated with the Manifest/BOL are arrived and the in-bond clocks are started
c. Entries associated with the Manifest/BOL are arrived and the entry clocks are started
d. General Order clocks are started for all unentered BOLs associated with the arrival at the port of unlading.
e. ACE (M1) updates the status of all BOL(s) of type FROB to ‘closed’ if no holds exist on the BOL
f. ACE (M1) updates the status of all BOL(s) of type “Empty” to ‘closed’ if no holds exist on the BOL.
4b ACE M1 sends out arrival notifications for all arrived manifests and BOLs. All arrival notifications in ACE M1 are sent to AMS for distribution to AMS partners.
a. ACE (M1) generates Conveyance Arrival notification (AAD) to the Carrier that filed manifest on the Conveyance. AMS will send to non-pilot participant.
b. ACE (M1) generates “Conveyance Arrival” notification (19) for designated Brokers specified on each arrived BOL. AMS or ACS will send to non-pilot participants as appropriate.
c. Notifications withheld until Arrival will be released. AMS will send to non-pilot participant.
Cancelling the Arrival
1 If a carrier intends to cancel an arrival, they must contact CBP. CBP must manually cancel an arrival in the ACE Portal.
2 If the arrival is correlated via UVI and stow plan, all correlated manifest/BOLs arrivals will be reset to not arrived.
3 If the arrival is at the single manifest level only with no correlation, the manifest and all house BOLs will be reset to not arrived.
4 (M1) generates Cancel Conveyance Arrival notification (COC) to the notification parties as appropriate. Notifications will be sent out via AMS for non-pilot participants.
New Arrival Functionality in ACE M1
On December 14, 2011, as part of the ACE eManifest:Rail and Sea (Drop M1) deployment, new functionality was deployed that impacts arrival processing in the Ocean mode of transportation for carriers using both ACE M1 and AMS. The net effect is that the correlated arrival process in ACE M1 is now enabled and will perform arrivals on all manifests received, including manifests it receives from AMS. The dual processing between ACE M1 and AMS ensures that events generated from ACE M1 should be sent to AMS participants. Please note that some issues have already been identified with this process and that these issues are being fixed. These fixes will be communicated when available.
The arrival process steps and conditions are listed below.
1 ACE M1 correlates all Manifests received by “Unique Voyage Identifier” (UVI) data element. All manifests identified as associated with the same UVI arriving at a specific port of arrival are correlated. (NOTE: This data element, although available, has not been defined by CBP or trade partners and is not yet in use)
2 ACE M1 correlates all Manifests received by Stowage Plan. All manifests identified as associated with a vessel arriving at a specific port of arrival are correlated.
When the Arrival is performed:
a. Via EDI by actual vessel operating carrier or
b. By CBP Officer using CBP interface
3a ACE M1 arrives all manifests correlated in steps 1 and 2 with the vessel arriving at the port. This establishes the date and time of arrival in ACE.
c. When the manifest/Master BOL is arrived all House BOLs associated with that arrival are also arrived (same as current AMS process)
d. In-bonds associated with the Manifest/BOL are arrived and the in-bond clocks are started
e. Entries associated with the Manifest/BOL are arrived and the entry clocks are started
f. General Order clocks are started for all unentered BOLs associated with the arrival at the port of unlading.
g. ACE (M1) updates the status of all BOL(s) of type FROB to ‘closed’ if no holds exist on the BOL
h. ACE (M1) updates the status of all BOL(s) of type “Empty” to ‘closed’ if no holds exist on the BOL.
4a ACE M1 sends out arrival notifications for all arrived manifests and BOLs. All arrival notifications in ACE M1 are sent to AMS for distribution to AMS partners.
a. ACE (M1) generates Conveyance Arrival notification (AAD) to the each Carrier that filed manifest on the Conveyance. AMS will send to non-pilot participant.
b. ACE (M1) generates “Conveyance Arrival” notification (19) for designated Brokers specified on each arrived BOL. AMS or ACS will send to non-pilot participants as appropriate.
c. Notifications withheld until Arrival will be released. AMS will send to non-pilot participant.
When the Arrival is Performed by a Carrier other than the Vessel Operator
3b ACE M1 arrives only the manifest associated with the carrier that is arriving at the specified port. This establishes the date and time of arrival in ACE.
a. When the manifest/Master BOL is arrived all House BOLs associated with that arrival are also arrived (same as current AMS process)
b. In-bonds associated with the Manifest/BOL are arrived and the in-bond clocks are started
c. Entries associated with the Manifest/BOL are arrived and the entry clocks are started
d. General Order clocks are started for all unentered BOLs associated with the arrival at the port of unlading.
e. ACE (M1) updates the status of all BOL(s) of type FROB to ‘closed’ if no holds exist on the BOL
f. ACE (M1) updates the status of all BOL(s) of type “Empty” to ‘closed’ if no holds exist on the BOL.
4b ACE M1 sends out arrival notifications for all arrived manifests and BOLs. All arrival notifications in ACE M1 are sent to AMS for distribution to AMS partners.
a. ACE (M1) generates Conveyance Arrival notification (AAD) to the Carrier that filed manifest on the Conveyance. AMS will send to non-pilot participant.
b. ACE (M1) generates “Conveyance Arrival” notification (19) for designated Brokers specified on each arrived BOL. AMS or ACS will send to non-pilot participants as appropriate.
c. Notifications withheld until Arrival will be released. AMS will send to non-pilot participant.
Cancelling the Arrival
1 If a carrier intends to cancel an arrival, they must contact CBP. CBP must manually cancel an arrival in the ACE Portal.
2 If the arrival is correlated via UVI and stow plan, all correlated manifest/BOLs arrivals will be reset to not arrived.
3 If the arrival is at the single manifest level only with no correlation, the manifest and all house BOLs will be reset to not arrived.
4 (M1) generates Cancel Conveyance Arrival notification (COC) to the notification parties as appropriate. Notifications will be sent out via AMS for non-pilot participants.
Update your subscriptions, modify your password or e-mail address, or stop subscriptions at any time on your Subscriber Preferences Page. You will need to use your e-mail address to log in. If you have questions or problems with the subscription service, please contact support@govdelivery.com.
This service is provided to you at no charge by U.S. Customs and Border Protection.
Privacy Policy | GovDelivery is providing this information on behalf of U.S. Department of Homeland Security, and may not use the information for any other purposes.
 |
 |