Trade & CBP Discuss ACE Plan Forward, Outlines 'Agile' Approach
CBP and the Trade Support Network (TSN) discussed plans for developing new capabilities to the Automated Commercial Environment (ACE) during a recent Webinar, according to a document posted by CBP. Much of CBP's focus was on the use of "agile" development, meant to allow CBP to implement small pieces of ACE rather than in larger chunks. The approach is said to allow more flexibility as needs change.
Sign up for a free preview to unlock the rest of this article
Export Compliance Daily combines U.S. export control news, foreign border import regulation and policy developments into a single daily information service that reliably informs its trade professional readers about important current issues affecting their operations.
The documents describe in detail the "agile" approach to ACE, which will begin with three pilots, according to an ACE pilot overview (here). The agency recently provided an outline of its ACE plans in the near and long term (see 13022031). The agile pilots will focus on three areas of ACE:
- PGA Message Set -- Establish the first phase of bi-directional communications between PGAs and CBP. This pilot includes three PGAs.
- Automated Corrections/Deletions -- The ability to process, then accept (or deny) corrections or deletions sent via EDI by the Trade related to Entries already on file. The expectation is that the system will retain version control and highlight specific changes for easy identification.
- Initial Entry Summary Edits -- The ability to determine when Harbor Maintenance Fees in the Ocean Mode of Transportation are allowed.
Agile System
The agile pilots will include "core agile development" teams, each to be self-directed, according to CBP's Agile 101 document (here). The teams will be made up of team capabilities owners, agile team leads, subject matter experts, developers and testers, said CBP. The pilots will be used to establish the agile practices with the three teams, after which, CBP will add agile teams "in subsequent release on the established 12 week cadence," it said.
Under the agile approach, each piece should take about 6 months after a need is identified, said CBP. That 6 months will include a series of "sprints," two-week periods that include various stages of the component's development, including design, development and testing. CBP plans to engage with the trade on the development by asking the Trade Leadership Council to "deploy trade representatives to participate in development teams," it said. The TLC consists of ACE trade ambassadors and trade co-chairs of the TSN committees. CBP will also hold monthly conference calls with the TLC to discuss progress, it said.
The TSN Feb. 27 Webinar is (here) and the Feb. 28 Webinar is (here). CBP also provided a glossary of new terms used within the agile approach, but was later pulled down from the agency's Website. Email ITTNews@warren-news.com for a copy of the glossary.