CBP Presentation on the ACE Cargo Control and Release Delivery

(Trade sources describe CCR as the ACE delivery that will provide the Manifest and Release functions.)

CCR Delivery to Standardize Cargo Control, Consolidate Data, Etc.

According to CBP, the objective of the CCR delivery is to:

• standardize cargo control processing, reporting tools and query capabilities across all transportation modes and to provide importers, exporters, customs brokers and transportation providers with one system for moving goods into or through the U.S. using ships, planes, trains, trucks, and ultimately pipelines;
• consolidate manifest, entry, reference file data and screening and targeting results via the Web-based ACE Secure Data Portal to help facilitate identification of shipments that may pose a potential risk; and
• provide Participating Government Agencies (PGAs) a single, integrated system and data repository to more efficiently control and evaluate shipments for security, commercial compliance and narcotics enforcement purposes.

CCR Functionality Overview

CBP provides the following CCR functionality overview:

Fall 2008 - e-Manifest: Ocean and Rail - M1 (e-Manifest: Ocean and Rail) is scheduled to be deployed in fall 2008¹.

Features of M1 include (partial list): vessel stowage plan (BAPLIE) to identify unmanifested containers and enhance cargo control; new functionality for ocean and rail trade partners via the trade portal; e-mail list serve capability for CBP to communicate with trade partners; extends the 'broker download' functionality into the ocean cargo environment; CBP will be able to place and remove holds at the container level; provides PGAs with hold/hold removal functionality; retires Automated Commercial System (ACS) ocean and rail manifest processing.

Benefits of M1 include: enhanced trade functionality, improved cargo control processes for CBP, and enhanced data capture.

Deployment strategy for M1 consists of six months of structured trade testing planned prior to go-live; the Automated Manifest System (AMS) will be run in parallel; builds on lessons learned from truck e-Manifest deployment; uses AMS as its baseline; essentially no changes to how the filer conducts business.

Second Quarter 2009 - e-Manifest: Air - M2.1 (e-Manifest: Air) is scheduled to be deployed in the second quarter of 2009².

Features of M2.1 include: inclusion of air cargo processing into ACE multi-modal manifest environment; processing of local transfers for air cargo; seamless movement of in-bond cargo across air-ocean-rail modes of transportation; holds at Master, House, Sub-house and simple bill of lading levels in air cargo; electronic transfer of bond liability between trade partners; electronic landing rights notification from CBP; new report capabilities for trade partners and CBP field officers via the ACE portal; broker download capability extended to air cargo environment; and retirement of the legacy Air AMS; etc.

Benefits of M2.1 include: addresses requests from trade for new functionality; facilitates intermodal movement of cargo between trade; improves cargo control for CBP; and brings PGAs into the air environment.

Fourth Quarter 2009 - e-Manifest: Truck - M2.2 (e-Manifest: Truck³, also referred to as Full Multi-Modal Manifest) is expected to be deployed in the fourth quarter of 2009².

Features of M2.2 include: bring truck processing into the multi-modal manifest environment; truck in-bond cargo control in ACE full multi-modal in-bond control across all modes; standard cargo control processes and reporting tools across all transportation modes; and retirement of legacy ACS manifest system.

Second Quarter 2010 - Cargo Release - M2.3 (Cargo Release) is scheduled to be deployed in the second quarter of 2010².

Features of M2.3 include: bring new PGAs into ACE Cargo Release application; support commercial identifiers in the multi-modal manifest bill of lading and in-bond identifier fields; provide custom reporting capabilities to CBP and PGA users; deliver additional electronic status notifications related to PGA requirements; enhance functionality for brokers via the ACE trade portal; and enable brokers to send electronic files (pdf, jpeg, etc.) to CBP in reply to information requests to facilitate cargo release.

Benefits of M.3 include: Termination of legacy ACS Cargo Selectivity application (the end of ACS in CCR area); Cargo Release and Cargo Control applications will share a common database environment that will allow for expanded functionality between transportation and entry filer communities; extends PGA functionality in ACE to over 20 different Federal agencies; and fully enfranchises the entry filer and transportation sectors of the trade in ACE.

Third Quarter 2011 - Exports and Mail Entry Writing System - M3 (Exports and Mail Entry Writing System) is scheduled to be deployed in the third quarter of 2011².

Features of M3 include: export cargo processing; export e-Manifest filing for ocean, rail, air and truck; and incorporation of the stand-alone Mail Entry Writing System (MEWS) into ACE.

(The final M drop, M4 (Bonded Facilities Control) is not included in this presentation; BP is checking to see if it is part of the CCR delivery.)

(See CBP's presentation for information on the full multi-modal database.)

¹Entry Summary and Accounts (ESAR) A2.1 (M1 Reference Data) will track the M1 schedule and be implemented before or with M1.

²These deployment dates are from an ACE Status Update PowerPoint presentation from the February 5-7, 2008 Trade Support Network (TSN) meeting. (Presentation, dated 02/06/08, available at http://www.cbp.gov/linkhandler/cgov/trade/automated/modernization/trade_support_network/session_highlights/feb_2008_tsn/ace_stat_update.ctt/ace_stat_update.pdf)

³e-Manifest: Truck will move from its own platform to the multi-modal platform.

CCR presentation (dated March 2008) available at http://www.cbp.gov/linkhandler/cgov/toolbox/about/modernization/ace/toolkit/ccr_overview.ctt/ccr_overview.pdf