1. ACE Development and Trade Engagement Michael Denning, CBP Rick Davenport, eCP June 30, 2004

2. Presenter’s Name June 17, 2003 2 Agenda  Future ACE Development – Rick Davenport  Trade Engagement in ACE Development – Michael Denning 1

3. Presenter’s Name June 17, 2003 3 Note: Relative sequencing - No dates implied = System is Operational Rollout Strategy Full Selectivity Tools (S4) Functionality Data Legal and Policy and Document Management Enforcement Business Intelligence MMM Receiving & Correlation Billing & Statements Collection & Receipt Accounts Receivable & Revenue Liquidation / Closeout Entry Summary Open Entry Summary & FI Conversion Accounts & Master Data Setup POST RELEASE PROCESSES & MULTI-MODAL MANIFEST DOCUMENT Release Verification (Admissibility, CCIE) Authorized Movements (Inbond) Cargo Tracking Electronic Manifest Receive Entry Open Item Conversion including Entry and Entry Summary PRE-RELEASE PROCESSES Drawback Protest IASS Process SEACATS Export FTZ / Warehouse Inventory Data Conversion Open Item Conversion ADDITIONAL CARGO MANIFEST LIFECYCLE FUNCTIONALITY Trade & Homeland Security Data Selectivity and Targeting Selectivity Foundation (S1) Targeting Foundation (S2) Advanced Targeting Capabilities (S3) 2

4. Presenter’s Name June 17, 2003 4 Next Steps for ACE Development  Global Business Blueprint (GBB) Completion - July 6, 2004  Business Process Flow models completed  Fit/Gap Analysis completed  Inputs to Program Plan  Upcoming months  Project Preparation - approximate 2-month duration  Planning efforts, including schedule development  Release Level Business Blueprint - approximate 6- month duration 3

5. Presenter’s Name June 17, 2003 5 Approach Global Business Blueprint Post Release Processes & MMM Document Selectivity & Targeting Workforce Transformation Business Process Security BI, Reporting, Analysis Technical Infrastructure Application Development EvaluationProject Preparation Business Blueprint Realization Final PreparationGo Live and Support Sustain Selectivity & Targeting 4

6. Trade Engagement in ACE Development Michael Denning 5

7. Presenter’s Name June 17, 2003 7  Approach & Trade Involvement  Roles & Responsibilities  Trade Representation within Business Process Areas  Benefits of Participation  TSN Committee Efforts Overview of Trade Involvement in ACE Development 6

8. Presenter’s Name June 17, 2003 8 Approach & Trade Involvement Business Blueprint Time Commitments  November 2004 through February 2005  24 to 40 hours per month (approximate) Participation: Combination of on-site participation and conference calls Nominations by TLC (Trade) by August 15 for on-site reps and back-ups. Final determination by CBP. Trade companies to sponsor for length of blueprint phase. Security requirements based on development topics and workshop participants. Expectations: “Ambassador” responsibility to communicate information to committee members Project milestones and/or tasks will determine specific time commitment and travel schedule to be on-site. Flexibility to be available on an as-needed basis for conference calls when not on-site with the project team.. Programmatic PIRA SDLC Phase Ascendant/ SDLC Phase 7 Release PIRA/PDCR PDRCDRTRRPRR Cut over ORRPIR Workforce Transformation Business Process Security BI, Reporting, Analysis Technical Infrastructure Application Development Project Preparation Business Blueprint Realization Final Preparation Go Live and Support Sustain Selectivity & Targeting Evaluation Realization Time Commitments (Prototype, UAT):  June 2005 through June 2006  24 hours every 3 months (approximate)

9. Presenter’s Name June 17, 2003 9 Roles & Responsibilities Business Blueprint  Provide the business process teams with the relevant business-specific information, documentation, and data for respective business process area(s)  Actively participate in workshops and presentations to review business processes and identify process re-engineering opportunities.  Help identify potential statutes & regulations that need to be changed  Act as project liaison to trade stakeholders.  Gain consensus on process design considerations within Trade Committees. Other: Ambassador Responsibility: Minimum of monthly follow-up meetings with TLC and Trade Committees 8 Workforce Transformation Business Process Security BI, Reporting, Analysis Technical Infrastructure Application Development Project Preparation Business Blueprint Realization Final Preparation Go Live and Support Sustain Selectivity & Targeting Evaluation

10. Presenter’s Name June 17, 2003 10 Trade Representation  Composition: Trade Representative per Business Process Area (Release dependent)  Accounts  Periodic representation from each account type  Finance  Trade expertise in accounts receivable  Post Release  Trade expertise in entry summary, liquidation, and reconciliation  Pre Release  Trade expertise in multi modal manifest 10

11. Presenter’s Name June 17, 2003 11 Benefits of Participation  Direct input to future ACE development  Business process re-engineering opportunities for the Trade Community  Increased integration and awareness of business processes across CBP, PGA, and the Trade Community  Assurance that the trade community’s business processes are consistent with CBP and PGA policy, procedures and regulations  Opportunity for ‘hands on’ discussions with CBP and PGAs in the development of the business process flows, definitions and procedures within your business process areas of expertise  Participation within security constraints in the design and development of future ACE functionality 9 Workforce Transformation Business Process Security BI, Reporting, Analysis Technical Infrastructure Application Development Project Preparation Business Blueprint Realization Final Preparation Go Live and Support Sustain Selectivity & Targeting Evaluation

12. Presenter’s Name June 17, 2003 12 TSN Committee Efforts  Ongoing TSN Committee Efforts  Evaluate existing TSN Business Process Recommendations  Status of pending requirements updated  Develop future TSN business process recommendations  Focus on business needs with scenarios to supplement  Recommendations will continue to be tracked via TSN input database  Use of business process flows to frame future recommendations, provide common context for discussion 11

13. Presenter’s Name June 17, 2003 13 Key concepts to continue at the Release level:  CBP/eCP co-leadership and involvement across the teams  Meaningful engagement of external stakeholders, including TSN and PGAs  Focus on value of an integrated process design  Balanced process/people/technology perspective in developing solution  Use of prototyping during project realization phase to help visualize future solution Key Takeaways for Future Release Success 13