CBP Posts its 2006 Quarterly Reports to Congress on ACE (Part I - Efforts to Address GAO Recommendations)
U.S. Customs and Border Protection (CBP) has recently posted to its Web site its quarterly reports on the Automated Commercial Environment (ACE) entitled Report to Congress on the Automated Commercial Environment. These reports cover the four quarters of calendar year 2006.
Sign up for a free preview to unlock the rest of this article
Communications Daily is required reading for senior executives at top telecom corporations, law firms, lobbying organizations, associations and government agencies (including the FCC). Join them today!
CBP states that these reports provide an update on ACE accomplishments, challenges, fiscal status, and upcoming program milestones.
CBP notes that these reports also address the ongoing CBP efforts to integrate ACE with other systems and engage other government agencies to participate in the ACE/International Trade Data System (ITDS).
This is Part I of a multi-part series of summaries on CBP's most recent quarterly report (October 1, 2006-December 31, 2006) and focuses on CBP's efforts to address certain open recommendations by the Government Accountability Office (GAO).
According to CBP, it has taken the following actions regarding several open GAO recommendations:
Extend/Use ACE Infrastructure to Support Other Homeland Security Applications
The GAO has recommended that CBP take appropriate steps to have future ACE expenditure plans specifically address proposals or plans to extend or use ACE infrastructure to support other homeland security applications.
CBP notes that it has not planned any ACE expenditures that would enable ACE infrastructure (equipment such as hardware environments) to support other homeland security applications. However, ACE program leadership is actively working to coordinate ACE with other homeland security applications (IT systems that provide tools and information to help front-line officers ensure the security of the U.S.). Although these coordination efforts have not resulted in the identification of specific cost savings for the ACE program or other related homeland security programs, CBP's Office of Information Technology (OIT) anticipates that this coordination will directly advance the agency's trade facilitation and homeland security goals. Specific examples of this coordination include the following (partial list) :
ACE Screening & Targeting (S&T) capabilities are being integrated with the Automated Targeting System (ATS);
When completed, ACE e-Manifest: All Modes - Cargo Control and Release (Release 6) and S&T capabilities will support the automation requirements of the Container Security Initiative (CSI) program;
ACE is leveraging the existing Treasury Enforcement Communications System (TECS) to provide front-line officers with commercial truck license plate and driver query capabilities;
Entry Summary, Accounts, and Revenue (ESAR): Master Data and Enhanced Accounts (A1) capabilities are being coordinated with the Customs-Trade Partnership Against Terrorism (C-TPAT). A1 will provide both CBP and trade representatives the ability to view the status of CBP programs such as C-TPAT;
ACE is being coordinated with the U.S.-Mexico Border Partnership Plan which will enable ACE to implement any cargo screening standards that are derived from Partnership Plan agreements; and
Future ACE export capabilities are being coordinated with the Automated Export System (AES), the current production system for CBP outbound cargo processing.
Establish ACE Performance Measures
GAO recommended that CBP develop a range of realistic ACE performance measures and targets needed to support an outcome-based, results-oriented accountability framework and fully address legislative conditions associated with measuring ACE performance and results.
CBP states that it has established a framework for the ACE performance measurement program based on the CBP Performance Reference Model. ACE performance measures were certified as complete and aligned with the CBP and DHS strategic plans. CBP has also developed the "critical few" performance targets to support the ACE accountability framework. As ACE proceeds through its lifecycle, CBP will update measures and targets, as appropriate, based on lessons learned, changes to system capabilities, and further refinement of the requirements for future ACE releases.
Minimize Overlap and Concurrency Across Ongoing and Future ACE Releases
GAO recommended that CBP minimize the degree of overlap and concurrency across ongoing and future ACE releases and that CBP should capture and mitigate the associated risks of any residual concurrency.
CBP responds by stating that key elements of its efforts to reduce concurrency include the decoupling of S&T releases from ACE secure cargo management releases to reduce interdependencies between development efforts; the use of Active Risk Manager software to track release-specific risks; and the establishment of a comprehensive program management foundation for managing ACE requirements, cost, schedule, and performance.
CBP further states that ACE releases have been divided into smaller groups of capabilities or "drops." Drops with similar development schedules are being managed as ACE "deliveries." According to CBP, this approach will improve planning and reduce contention for hardware environments and program staff, as well as resources required for system testing, legacy system integration, training, and development.
October 1-December 31, 2006 ACE quarterly report (posted 03/01/07) available at http://www.cbp.gov/linkhandler/cgov/toolbox/about/modernization/ace/newsletters/quarterly_reports/ace_report_to_congress_12312006.ctt/ace_report_to_congress_12312006.pdf.
January-September 2006 ACE quarterly reports (posted February 2007) available at http://www.cbp.gov/xp/cgov/toolbox/about/modernization/ace/newsletters/quarterly_reports/.