e-Manifest: Trucks (Release 4) Status Update: Presenters: Susan Hutzell (TBD), CBP Robert Santos, eCP Thomas Fitzpatrick, CBP Jeremy Baskin, CBP Panelists: Matthew Myers, eCP June 30, 2004 e-Manifest: Trucks (Release 4) Status Update


Slide2: Introductions & Overview Susan Hutzell, CBP (TBD)


Agenda: Agenda Overview of e-Manifest: Trucks (Release 4) Development and Testing Unit Testing and Software Integration Testing (SWIT) Status System Integration Testing (SIT) & System Acceptance Testing (SAT) Test Readiness Review (TRR), Product Readiness Review (PRR), & Operational Readiness Review (ORR) e-release PAPS: Pre Arrival Processing System BCS: Border Cargo Selectivity BRASS: Border Release Advanced Selectivity System FAST: Free And Secure Trade / Preferred Manifest Section 321: Informal Release In-Bond Processing Broker Download & Information Session Status of the e-Manifest: Trucks Release 4 Federal Register Notice (FRN)


Overview, Development and Testing: Overview, Development and Testing Robert Santos, eCP


Overview: Overview The Automated Commercial Environment (ACE) will: Automate truck manifest filings with U.S. Customs and Border Protection (CBP) Utilize both Electronic Data Interchange (EDI) and web-based ACE Secure Data Portal technologies Interface with legacy release processes Consolidate CBP release mechanisms Incorporate transponder and proximity card technologies Support In-Bond processing


Web Links at www.cbp.gov: Web Links at www.cbp.gov ACE EDI message drafts Trade Support Network > related links: ACE EDI message drafts MEDPID EDI message for crew, conveyance and equipment Outline of EDI messages for ACE Releases 3 & 4  New/modified EDI messages for ACE Release 4 - truck manifest Multi-Modal Manifest data matrix Trade Support Network > committee requirements > multi-modal requirements > manifest data elements > manifest data elements spreadsheet Standard and preferred data element details for truck manifest Trade Support Network > committee requirements > multi-modal requirements > manifest data elements > manifest submission by carriers


ACE Secure Data Portal: ACE Secure Data Portal e-Manifest: Trucks


Unit Testing and Software Integration Testing (SWIT): Unit Testing and Software Integration Testing (SWIT) What is unit testing? The first tests in the overall testing process Tests are performed by the developers programming the application Tests are usually performed on the developer’s workstation The developer tests an individual piece of the application (module) to ensure it satisfies the requirements What is SWIT testing? The first test where all of the modules of the application are integrated into the complete application. This is the first point where existing systems e.g. ACS, FAST, BRASS, are integrated with the newly developed applications.


Unit Testing and SWIT Testing: Unit Testing and SWIT Testing Why do we do unit and SWIT testing? To allow the developers to verify that the applications perform per the requirements To have the development team perform these tests early in the testing process, allowing them to quickly identify and resolve basic integration problems prior to the independent test phase Who does unit testing and SWIT testing? The development teams


Software Integration Test (SIT) System Acceptance Test (SAT): Software Integration Test (SIT) System Acceptance Test (SAT) What is Software Integration Testing (SIT)? SIT tests the combination of subsystems, hardware, software products, data, commercial-off-the-shelf (COTS) products, personnel, and procedures for systems functionality What is System Acceptance Testing (SAT)? SAT tests if the design meets approved requirements for the system


The Why and Who of SIT and SAT: The Why and Who of SIT and SAT Why conduct SIT and SAT testing? SIT and SAT testing are done to independently verify the system satisfies the requirements Who conducts SIT & SAT testing? A test team, independent of the developers Testing will be conducted with the support of CBP Subject Matter Experts (SMEs)


Test Readiness Review (TRR)Product Readiness Review (PRR)Operational Readiness Review (ORR): Test Readiness Review (TRR) Product Readiness Review (PRR) Operational Readiness Review (ORR) What is Test Readiness Review (TRR)? TRR is the milestone where agreement is reached to proceed with Systems Acceptance Testing What is Product Readiness Review (PRR)? PRR is the milestone where agreement is reached among the business sponsor, project manager, supporting organizations, and senior management that the system may be deployed into the production environment What is Operational Readiness Review (ORR)? ORR is the milestone where agreement is reached among the business sponsor, project manager, supporting organizations, and senior management that the system may be deployed into full operation


PRR & ORR : PRR & ORR Why conduct TRR, PRR & ORR? To increase ongoing Office of Information Technology (OIT) involvement in review of ACE activities To provide a way for OIT to prioritize ACE activities and to be familiar with status throughout the ACE lifecycle To give OIT better access to and visibility into eCustoms Partnership (eCP) environments Gate Criteria Review Rollout


PRR & ORR (continued): PRR & ORR (continued) Benefits of criteria ownership model: Experts from organizations incurring the greatest impact will have the most influence in criteria decisions Gate criteria owners will have better opportunities to review deliverables and speak with eCP counterparts about ACE activities that directly impact their domain eCP will have focal points within CBP for discussion of ACE issues and gate criteria owners will have a mechanism to address ACE issues Gate criteria owners will have a method to plan for resources needed to address ACE activities Gate Criteria Review Rollout


Testing Plans: Testing Plans Unit Testing SWIT: Software Integration Testing (Spring 04) SAT: System Acceptance Testing (Summer 04) SIT: System Integration Testing (Spring 04) TRR: Test Readiness Review (Summer 04) PRR: Production Readiness Review (Fall 04) Dec./ Jan./ Feb./ Mar./ Apr./ May./ Jun./ Jul./ Aug./ Sep./ Oct./ Nov./ Dec./ Jan./ Feb ORR: Operational Readiness Review (Winter 04/05) Pilot Participants Limited Trade Samples e-Manifest: Trucks (Release 4) Full Participation 2004 2005 UAT: User Acceptance Testing (Fall 04)


e-Release: e-Release Tom Fitzpatrick


e-Manifest: Trucks Process Overview: e-Manifest: Trucks Process Overview


e-Manifest: Trucks Functionality At-A-Glance : e-Manifest: Trucks Functionality At-A-Glance Electronic truck manifest Multiple filing options ACE Secure Data Portal EDI Standardized data elements (MMM) In-Bond Consolidated Electronic Release (e-Release) Simplified and expedited cargo release Automated reconciliation of manifest and entry Improved intra-port communications - workflow Supports current shipment release programs On-line trade community access to data


e-Manifest and e-Release: e-Manifest and e-Release Trip Conveyance Crew (s) Passenger (s) Equipment (s) Shipment (s) – PAPS Shipment (s) - BCS Shipment (s)– In-Bond Shipment (s)– BRASS Shipment (s)– Section 321


e-Manifest: Trucks Functionality by Shipment Type: e-Manifest: Trucks Functionality by Shipment Type


e-Release: PAPS: e-Release: PAPS Entry pre-filed in ACS Border Cargo Selectivity Entry Entry Summary Bar Code will not be needed Shipment Control Number (SCN) and, if applicable, Bill Control Number (BCN) must match SCN/BCN number supplied on the entry Current limit of three PAPS shipments at primary will be removed Manifest and entry information is reconciled


e-Release: Section 321: e-Release: Section 321 19 Code of Federal Regulations Section 143.23(j) Country of origin and value will be entered into the manifest shipment records With these additional data elements the manifest becomes the entry Maximum value is 200 dollars


e-Release: BRASS : e-Release: BRASS C-4 code numbers will be entered by the carrier into the manifest shipment records BRASS bar codes will not be needed At the time of release entry number will be assigned


e-Release: In-Bond: e-Release: In-Bond In-Bond types supported 61 – Immediate Transportation (I.T.) 62 – Transportation and Exportation (T&E) 63 – Immediate Exportation (I.E.) In-Bond functionality supported In-Bond request and authorization In-Bond arrival Method of data transmission ACE e-Manifest: Trucks (Release 4) Electronic In-Bond via the Automated Broker Interface (record identifiers QP/WP) Customs Automated Forms Entry System – CAFES


e-Release: FAST Overview: e-Release: FAST Overview FAST transactions will be filed in the same manner as today ACE will support the release of FAST shipments FAST will support the submission of additional shipment information FAST transactions may be viewed via the ACE Secure Data Portal FAST transactions may not be created or modified via the ACE Secure Data Portal


e-Release: FAST Transition: e-Release: FAST Transition


e-Release : FAST Eligibility Requirements: e-Release : FAST Eligibility Requirements Driver must be a registered FAST participant with a proximity card Truck must be equipped with a transponder Carrier must be a Customs –Trade Partnership Against Terrorism (C-TPAT) participant Importer must be a C-TPAT participant Additional requirements on the Southern Border Manufacturer must be a C-TPAT participant Equipment must be sealed


Additional Issues: Additional Issues Broker Download Shipment data reported by the carrier will be forwarded to the ACS entry filer identified by the carrier Associated carriers Shipment data transmitted to ACE cannot be transferred from one carrier to another The issue of the carrier’s ability to transfer shipment data from one carrier to another is under review Export of In-Bond shipments must be reported via ABI (QP/WP)


e-Manifest: Trucks (Release 4) Status Federal Register Notice: e-Manifest: Trucks (Release 4) Status Federal Register Notice Jeremy Baskin


e-Manifest: Trucks (Release 4) Status : e-Manifest: Trucks (Release 4) Status When? No later than 90 days prior to program test Publication Date? August 2004 What will it cover? Qualifications & Eligibility Requirements for Truck Carrier Accounts Data elements Seven Ports: (Detroit, Port Huron, Buffalo, Champlain, Blaine, Otay Mesa, Laredo) Who will it cover? The “participant” is defined as the carrier Includes the “authorized agent” for the carrier Federal Register Notice


Slide31: ? Questions and Feedback Visit the Modernization & ACE site on www.cbp.gov or write us at: CBPMO@dhs.gov Visit the ITDS site at www.itds.treas.gov