# Presentation: 089042

## e-Manifest: Trucks (Release 4) Electronic Data Interchange (EDI) Information Session 

**Panelists:**
- Thomas Fitzpatrick, CBP
- Karen Tilghman, eCP
- Dale Wilson, CBP
- James Wolford, CBP
- Michelle Miller, eCP
- Bill Nolle, CBP
- Elizabeth Phillips, eCP
*	*

**Presenters:**
- Steven Graham, eCP
- Michael Boshes, eCP Adam Houston, eCP
- William Miller, eCP
- Luke McCormack, CBP
- Bud Blankenship, CBP
- Pat Young. eCP
- Kiran Gowda, eCP
- Don Kozacki, CBP
- Karen Henderson, CBP
*	*

- June 28 - 29, 2004

## e-Manifest: Trucks (Release 4) EDI Information Session 

- Electronic Meeting Process
- Michael Boshes, eCP

## Explanation of the Electronic Meeting Process 

## e-Manifest: Trucks (Release 4) EDI Information Session 

- Introductions and Session OverviewSteven Graham, eCP

## Agenda

- Introductions
- Explanation of the electronic meeting process
- Overview of ACE e-Manifest: Trucks (Release 4)
- Portal and EDI methods of Submission
- Release Types
- Portal Presentation
- Carrier Accounts - MEDPID
- Communications for EDI (MQ Series)
- Release 4 – e-Manifest: Trucks (Release 4)– ANSI X12
- Process flows
- Looping constructs and changes
- ANSI X.12 message details
- Release 4 – e-Manifest: Trucks (Release 4) – EDIFACT
- Test and Validation
- Final Questions and Answers

## EDI Overview

**Connecting to ACE using ANSI X.12:**
- Messages transmitted to U.S. Customs and Border Protection (CBP)
- 309	Complete Manifest or Preliminary Shipments
- 358	Truck Manifest (Trip/Consist)
- 353	Event Advisory Message (Manifest Commit)
- Messages transmitted from CBP
- 997	Functional Acknowledgement
- 355	CBP Acceptance/Rejection
- 350	CBP Status Information

## EDI Overview

**Connecting to ACE/FAST using EDIFACT:**
- Messages transmitted to CBP
- CUSCAR	Customs Cargo Report
- CUSREP	Customs Conveyance Report
- PAXLST		Passenger List
- CUSDEC 	Customs Declaration
- Messages transmitted from CBP
- CUSRES	Customs Response
- REQDOC	Request for Documents
- CONTRL	Functional Acknowledgment

## Web Links

**ACE Release 4: Truck Manifest  Power Point Presentation, Sept. TSN**
- 	_[www.cbp.gov](http://www.cbp.gov/)__ Trade Support Network > September 2003 TSN Meeting Highlights > ACE Release 4: Automated Truck Manifest_
**ACE EDI Message Drafts**
- 	_[www.cbp.gov](http://www.cbp.gov/)__ 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
- DRAFT CATAIR Changes for ACE Release 3 Periodic Monthly Statement
- New/Modified EDI Messages for ACE Release 4 - Truck Manifest
**Multi-Modal Manifest (MMM) Data Matrix**
- 	_[www.cbp.gov](http://www.cbp.gov/)__ Trade Support Network > Committee Requirements > Multi Modal Requirements > Manifest Data Elements > Manifest Data Elements Spreadsheet_
**Standard and Preferred Data Element Details for Truck Manifest**
- 	_[www.cbp.gov](http://www.cbp.gov/)__  Trade Support Network > Committee Requirements > Multi-Modal Requirements > Manifest Data Elements > Manifest Submission by Carriers_

## e-Manifest: Trucks (Release 4) EDI Information Session

- Overview
- Adam Houston, eCP

## e-Manifest: Trucks Process Overview

## 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: Trucks Functionality by Shipment Type

|  | e-Manifest
filing | e-Release | Portal view |
| --- | --- | --- | --- |
| PAPS/BCS |  |  |  |
| Section 321 |  |  |  |
| BRASS |  |  |  |
| In-Bond |  |  |  |
| FAST  |  |  |  |

## e-Release: FAST Overview

- FAST transactions will be filed in the same manner as today
- ACE will support the release of FAST shipments
- 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 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

## 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: 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: 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

**Notes:**
(j) Except for mail importations (see §§145.31 and 145.32 of this chapter), or in the case of personal written or oral declarations (see §§148.12, 148.13 and 148.62 of this chapter), a shipment of merchandise not exceeding $200 in value which qualifies for informal entry under 19 U.S.C. 1498 and meets the requirements in §10.151 or §10.152 of this chapter may be entered by presenting the bill of lading or a manifest listing each bill of lading (see §§10.151, 10.152 and 128.24(e) of this chapter). The following information is required to be filed as a part of such entry: 
(1) Country of origin of the merchandise; 
(2) Shipper name, address and country; 
(3) Ultimate consignee name and address; 
(4) Specific description of the merchandise; 
(5) Quantity; 
(6) Shipping weight; and 
(7) Value.

Title 19: Customs DutiesPART 10—ARTICLES CONDITIONALLY FREE, SUBJECT TO A REDUCED RATE, ETC. Importations Not Over $200 And Bona Fide Gifts 
Browse Next
§ 10.151   Importations not over $200.
Subject to the conditions in §10.153 of this part, the port director shall pass free of duty and tax any shipment of merchandise, as defined in §101.1 of this chapter, imported by one person on one day having a fair retail value, as evidenced by an oral declaration or the bill of lading (or other document filed as the entry) or manifest listing each bill of lading, in the country of shipment not exceeding $200, unless he has reason to believe that the shipment is one of several lots covered by a single order or contract and that it was sent separately for the express purpose of securing free entry therefore or of avoiding compliance with any pertinent law or regulation. Merchandise subject to this exemption shall be entered under the informal entry procedures (see subpart C, part 143, and §§128.24, 145.31, 148.12, and 148.62, of this chapter).
[T.D. 94–51, 59 FR 30293, June 13, 1994, as amended by T.D. 95–31, 60 FR 18990, Apr. 14, 1995; T.D. 95–31, 60 FR 37875, July 24, 1995; T.D. 97–82, 62 FR 51769, Oct. 3, 1997]

## 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

## 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)

## ACE Secure Data Portal – e-Manifest: Trucks (Release 4)

- ACE Secure Data Portal – e-Manifest: Trucks (Release 4)

- Bill Miller, eCP

## ACE Secure Data Portal

- Conceptual design for discussion purposes only

## ACE Secure Data Portal - Trip

- Conceptual design for discussion purposes only

## ACE Secure Data Portal - Conveyance

- Conceptual design for discussion purposes only

## ACE Secure Data Portal - Crew

- Conceptual design for discussion purposes only

## ACE Secure Data Portal - Equipment

- Conceptual design for discussion purposes only

## ACE Secure Data Portal – Link Shipments to Trip

- Conceptual design for discussion purposes only

## ACE Secure Data Portal - Shipment

- Conceptual design for discussion purposes only

## ACE Secure Data Portal – Shipment Commodity

- Conceptual design for discussion purposes only

## ACE Secure Data Portal – Change Shipment Type

- Conceptual design for discussion purposes only

## Carrier Accounts Management  (MEDPID)

***	****	**	*

- Carrier Accounts Management  (MEDPID)

- Panelists:
- Karen Henderson, CBP
- Michelle Miller, eCP
*	**	**	*

- Patricia Young, eCP

## Purpose of MEDPID Message

- Electronic Data Interchange (EDI) solution for the trade community to submit master data to a carrier’s account for use in e-Manifest: Trucks (Release 4)
- Master data includes:
- Crew
- Equipment
- Conveyance
- Actions:  Add, deactivate, and modify

## Purpose of MEDPID Message

- Existing translators can be used
- MEDPID is compatible with United Nations/Electronic Data Interchange for Administration, Commerce, and Transport (UN/EDIFACT) MEDPID standard rules and guidelines
- New CBP EDI messages under consideration
- MEDPID equivalent ANSI X.12 transaction set (359 set)
- UN/EDIFACT message for CBP use (MEDPID “replacement”)
- To be sent to EDI standards bodies (UN/EDIFACT and ANSI X.12) for approval

## MEDPID Message Constraints

- Up to 9999 master data records can be sent in one MEDPID
- Send 1 MEDPID per interchange (UNH-UNT)
- Limit one interchange per message transmission
- Limit MEDPID message to one category (crew, conveyance, or equipment) per message transmission
- Only one Message Group (UNG-UNE) per message transmission
- Message Group is optional
- Maximum message size is 4MB

## To Add Crew Information

- Standard Carrier Alpha Code (SCAC)
- First, last, and middle name (if middle name exists)
- Gender
- Date of Birth
- Nationality/Citizenship
- Driver’s License, State/Province and Country, Hazmat Endorsement
- Travel Documents

- An Automated Commercial Environment Identification
- (ACE ID), once deactivated from the previous account,
- or the following is required:

## To Add Conveyance and/or Equipment

- Conveyance
- SCAC
- Conveyance type
- Conveyance number/ID
- License plate with state/province, country
- Vehicle Identification Number (VIN)
- Transponder number, if it exists

- Equipment
- SCAC
- Equipment type
- Equipment number/ID
- License plate with state/province, country

- An ACE ID, once deactivated from the previous account, or the following is required:

## To Deactivate or Modify Information

- Deactivate Crew
- ACE ID
- Driver’s license, state/province and country

- Deactivate
- Conveyance
- ACE ID
- VIN

- Deactivate
- Equipment
- ACE ID
- Equipment number/ID

- To Modify: above fields plus changed fields only

## MEDPID Response

- CBP responds back to the trade community user with a MEDPID Response
- Entire message received is returned with approval/disapproval code and free text (for errors)
- Approvals and disapprovals can be returned in the same message
- Maximum combination of approvals and disapprovals is 99 in a given message

## MEDPID Process with Error Reporting

- Trade community user transmits MEDPID message
- EDI translator returns functional acknowledgments (FA) to sender
- EDI compliance error or success
- Configurable (for every message or for no messages)
- Translator mapped data is sent to ACE
- ACE sends response
- ACE responses are translated to MEDPID and conveyed to sender
- Entire received message is sent back with error codes and messages

**3 Data**

## Test and Validation

- To use MEDPID, trade community user must pass test and validation
- ACE Test and Validation Procedures will be similar to existing CBP Test and Validation Procedures
- Test and Validation briefing will provide more details

## Communications Architecture and Trade Interfaces 

- Luke McCormack, CBP

- Communications Architecture and Trade Interfaces

- Bud Blankenship, CBP

## Communications Architecture and Trade Interfaces

- Customs EDI Communications –  ACE
- Supported Communications
- MQ Frame Relay
- Value Added Networks (VANs)
- Application Service Providers (ASPs)
- Service Centers
- Communications Not Supported in ACE
- LU6.2 SNA
- RJE Dial-Up

## Communications Architecture and Trade Interfaces

- Customs EDI Communications Architecture

_*Trade*_

- CBP MQ
- Message
- Broker
- Interface

_*CBP*_
- Automated
- Commercial
- Environment
- (ACE)

_***Manifests***_

_***Accounts***_

_***Periodic***_
_***Statements***_

**Value Added Networks**
**Service Centers**
**Carriers**
**Brokers**

**TCP/IP Frame**
** ****Relay Network**

## Communications Architecture and Trade Interfaces

- MQ Frame Relay Program
- Features:
- IBM Messaging Technology
- Sprint Digital Networking Technology
- Cylink Encryption Technology
- T1 connections to Sprint for Trade and Participating Government Agency (PGA) Interfaces
- Conforms with CBP Disaster Recovery Strategy
- Interconnection Security Agreement (ISA) required

## Communications Architecture and Trade Interfaces

- Service Centers, ASPs and VANs
- MQ Frame Relay to CBP
- Provide flexible communications interfaces to their client base (ie. FTP, HTTPS)
- In-service data translation/transformation
- Refer to list of vendors and service providers on CBP website
- Support ANSI X.12 and UN/EDIFACT messaging
- CBP does NOT pay for electronic data exchange

- ANSI X.12

- Kiran Gowda, eCP

## ANSI X.12 Manifest

- Messages transmitted to CBP
- 309     Complete Manifest or Preliminary Shipments
- 358     Truck Manifest (Trip/Consist)
- 353     Event Advisory Message (Manifest Commit and In-Bond Arrival)
- Messages transmitted from CBP
- 997     Functional Acknowledgement
- 355     CBP Acceptance/Rejection
- 350     CBP Status Information

## ANSI X.12 

- Option 1:
- Original manifest (trip and shipments) via the ANSI X.12 transaction set 309 “Customs Manifest”
- Option 2:
- Preliminary shipments via 309
- Trip via ANSI X.12 transaction set 358 “Customs Trip Information” with shipments listed in MBL segment “Bill of Lading”
- Option 3:
- Preliminary shipments via 309 with trip number in M10 segment “Manifest Identifying Information”
- Trip via 358 “Customs Trip Information”

- Manifest EDI Submission Options

**Notes:**
If a manifesting carrier is in possession of full shipment and trip information, the carrier may transmit an original manifest message (309 Customs Manifest) identifying the trip, conveyance, crew, equipment and shipments associated therewith.  This is considered a complete manifest and no further 358 Consist Information (Trip Information) message or 353 Events Advisory Details message will be required.  
The manifesting carrier may send individual preliminary shipment manifests (309 Customs Manifest) without identifying the trip, conveyance, crew, or equipment.  When shipments are scheduled for movement, the manifesting carrier will transmit a 358 Customs Consist Information (Trip Information) transaction set providing trip, conveyance, crew, and equipment data.  The 358 Customs Consist Information transaction set will be used to link preliminary shipment numbers to the Trip. 
If a manifesting carrier is able to schedule a trip prior to associating the shipments for the trip, the carrier will transmit a 358 Customs Consist Information message (Trip Information) transaction set providing trip number (M1006), conveyance, crew, and equipment data.  When the shipments for the trip have been identified, the carrier will transmit the shipment manifests in the 309 Customs Manifest transaction set as preliminary shipments, making sure to include the M1006  trip number provided prior on the 358 Customs Consist Information (Trip Information) transaction set.  This will enable CBP to automatically associate the preliminary shipments (309’s) with the Trip information. 
     In the second and third scenario, the manifesting carrier will be required to transmit a 353 Customs Events Advisory Details transaction set with a code ‘Z’ ‘End of Manifest’ in the M1501 to signify  the completion of the manifest.  Once the 353 transaction set has been sent to say the manifest is complete, any changes to trip, conveyance, crew, equipment or shipment information will be considered a manifest amendment, and subject to the restrictions provided by law and Regulation. 

## ANSI X.12Manifest EDI and ACE Secure Data Portal Submission Options

- Option 1:
- Preliminary shipments via 309
- Create trip on ACE Secure Data Portal
- Locate and link shipments on ACE Secure Data Portal
- Option 2:
- Preliminary shipments via 309 with trip number in M10 segment
- Update trip on ACE Secure Data Portal
- Option 3:
- Preliminary shipments on ACE Secure Data Portal
- Trip via 358 with shipments listed in MBL segment

## ANSI X.12 Functionality

- Identifiers:

- Trip Identifiers (Standard Manifest) = Trip Number, Estimated Date of Arrival
- Trip Identifiers (Preferred Manifest) = Trip Number
- Shipment Identifiers (Standard Manifest) = Shipment Control Number, Bill Control Number (if applicable)
- Shipment Identifiers (Preferred Manifest) = Shipment Control Number

## ANSI X.12 Functionality

- 309: Truck Manifest / Shipments

| Type of Msg | Data | Description | Functionality |
| --- | --- | --- | --- |
| M1009 = 'W' (Original)M1017 = '8' (Standard)/'9' (Preferred) | Trip and Shipment data | Manifest (Trip + Shipments created) - marked complete and submitted to CBP. | Create Manifest |
| M1009 = 'P' (Preliminary)M1017 = '8' (Standard)/'9' (Preferred) | Shipment data only. Trip Number = 'SYSTEM'. | Unassociated Shipments created | Create Shipment |
| M1009 = 'P' (Preliminary)M1017 = '8' (Standard)/'9' (Preferred) | Trip identifiers provided and Shipment data provided. | Trip with only Trip identifiers created. Shipments created and attached to Trip. | Create Manifest |
| M1009 = 'P' (Preliminary)M1017 = '8' (Standard)/'9' (Preferred) | Trip information provided and Shipment data provided. | Manifest (Trip + Shipments created) - not yet completed | Create Manifest |
| M1009 = 'Y' ('Update' at Trip level)M1303 = 'A'.('Add' at Shipment level)M1017 = '8' (Standard)/'9' (Preferred) | Trip identifiers provided and Shipment data provided. | If any Trip information is changed, Trip updated.A new Shipment created and linked to the existing Trip specified. | Update Manifest |

## ANSI X.12 Functionality

- 309: Truck Manifest / Shipments (Continued)

| Type of Msg | Data | Description | Functionality |
| --- | --- | --- | --- |
| M1009 = 'Y' ('Update' at Trip level)M1303 = 'D'. ('Delete' at Shipment level)M1017 = '8' (Standard)/'9' (Preferred) | Trip identifiers and Bill identifiers(s) provided. | If any Trip information is changed, Trip updated. Shipment cancelled. | Update Manifest |
| M1009 = 'Y' ('Update' at Trip level)M1303 = 'M'. ('Update' at Shipment level)M1017 = '8' (Standard)/'9' (Preferred) | Trip identifiers provided and Shipment data provided. | If any Trip information is changed, Trip updated. Shipment modified | Update Manifest |
| M1009 = 'Y' ('Update' at Trip level)M1303 = 'D'. ('Delete' at Shipment level)M1017 = '8' (Standard)/'9' (Preferred) | Trip Number = 'SYSTEM'.  Bill identifier(s) provided. | Shipment cancelled. | Cancel Shipment |
| M1009 = 'Y' ('Update' at Trip level)M1303 = 'M'. ('Update' at Shipment level)M1017 = '8' (Standard)/'9' (Preferred) | Trip Number = 'SYSTEM'.  Bill identifier(s) provided. | Shipment modified. | Update Shipment |
| M1009 = '3'  ('Delete' at Trip level)M1017 = '8' (Standard)/'9' (Preferred) | Trip identifiers provided. | Cancel Manifest (Trip and associated Shipments) | Cancel Manifest |

## ANSI X.12 Functionality

- 358: Trip Information

| Type of Msg | Data | Description | Functionality |
| --- | --- | --- | --- |
| M1009 = 'S' (Preliminary)M1017 = '8' (Standard)/'9' (Preferred) | Trip data provided | Trip created and marked as Empty. Manifest still preliminary | Create Trip |
| M1009 = 'S' (Preliminary)M1017 = '8' (Standard)/'9' (Preferred) | Trip data provided and Bills listed in MBL (Boarded Qty for Split Shipment may be provided) | Trip created and Shipments specified are linked to this TripPre-condition: Shipment should have been filed earlier. | Create Trip.Link Shipments. |
| M1009 = 'Y' ('Update' at Trip level)M1017 = '8' (Standard)/'9' (Preferred) | Trip data provided | Trip information updated. If Shipments already exist in the system with this Trip identifier, the Trip and Shipments are linked. | Update Trip. Automatically link Shipments to Trip. |
| M1009 = 'Y' ('Update' at Trip level)M1303 = 'A' ('Add' at Shipment level)M1017 = '8' (Standard)/'9' (Preferred) | Trip data provided and Bills listed in M13 (Boarded Qty for Split Shipment may be provided in MBL) | Trip updated and Shipments specified are linked to this Trip.  | Update Trip.Link Shipments to Trip. |
| M1009 = 'Y' ('Update' at Trip level)M1303 = 'D' ('Delete' at Shipment level)M1017 = '8' (Standard)/'9' (Preferred) | Trip data provided and Bills specified in M13 | Trip updated and Shipments specified are de-linked from this Trip. The Shipments are still available to be used on another Trip. | Update Trip.De-Link Shipments from Trip. |

## ANSI X.12 Functionality

- 358: Trip Information (Continued)

| Type of Msg | Data | Description | Functionality |
| --- | --- | --- | --- |
| M1009 = 'Y' ('Update' at Trip level)M1303 = 'M' ('Update' at Shipment level)M1017 = '8' (Standard)/'9' (Preferred) | Trip data provided and Bills listed in MBL and Boarded Qty for Split Shipment provided | Trip updated and Boarded Qty on Shipments specified is updated. | Update Manifest |
| M1009 = '3'  ('Delete' at Trip level)M1017 = '8' (Standard)/'9' (Preferred) | Trip identifiers provided | Cancel Manifest (Trip and associated Shipments) | Cancel Manifest |

## ANSI X.12 Functionality

- 353: Events Advisory Details

| Type of Msg | Data | Description | Functionality |
| --- | --- | --- | --- |
| M1501 = '1' (Arrival by In-bond Number)/ '2'(Arrival by Bill of Lading Number)/ '3'(Arrival by Equipment Number) | In-Bond number/Bill number/Equipment ID | In-Bond Arrival | In-Bond Arrival |
| M1501 = 'Z' (End of Manifest)M1017 = '8' (Standard)/'9' (Preferred) | Trip identifiers | Mark Manifest complete and submit to CBP. | Submit to CBP |

**Notes:**
In-Bond arrival by Equipment ???

## ANSI X.12 Functionality

| Type of Message Segment | Data | Description | Functionality |
| --- | --- | --- | --- |
| M1009 = ‘P’ (Preliminary)/ ’W’ (Original) Manifest | Manifest Data | Response to a Manifest submission via 309 | Manifest accept/reject |
| M1009 = ‘S’ (Trip) | Manifest Data
 | Response to a trip submission via 358 | Manifest accept/reject |
| M1009 = ‘Y’ (Amendment)) | Manifest Data
 | Response to an update to a Manifest submitted via 309/358 | Manifest accept/reject |
| M1009 = ‘3’ (Deletion) | Manifest Data
 | Response to an delete to a Manifest submitted via 309/358 | Manifest accept/reject |
| M1009 = ‘I’ (In-Bond Arrival) | In-Bond arrival information | Response to an In-Bond arrival submitted via 353 | In-Bond Arrival accept/reject |

- 355: CBP Acceptance/Rejection

**Notes:**
In-Bond arrival by Equipment ???

## ANSI X.12 Functionality

| Type of Message Segment | Data | Description | Functionality |
| --- | --- | --- | --- |
| V901 = ‘AAD’ (Arrival) | Trip Data | Arrival of conveyance at first U.S. port | Arrival notification |
| V901 = ‘HCR’ (Crew)/ ‘HEQ’ (Equipment)/ ‘HMI’ (Conveyance)/ ‘HTR’ (Trip) Hold | Trip Data | Trip, conveyance, crew, equipment Held | Hold notification |
| V901 = ‘RCR’ (Crew)/ ‘REQ’ (Equipment)/ ‘RCO’ (Conveyance)/ ‘RTR’ (Trip) Released | Trip Data | Trip, conveyance, crew, equipment released
 | Release notification |

- 350: CBP Status Information

**Notes:**
In-Bond arrival by Equipment ???

## ANSI X.12 Functionality

- 350: CBP Status Information (Continued)

| Type of Message Segment | Data | Description | Functionality |
| --- | --- | --- | --- |
| X407 = 1C Entered and Released, General Examination1H Customs hold placed at port of discharge1I  Customs hold removed at port of discharge1J  In-bond Movement Authorized1T Seized 11  Arrival of In-bond, complete movement12 Arrival of In-bond, bill of lading13 Arrival of in-bond, container/equipment50 Export of in-bond - complete movement51 Export of in-bond – bill of lading52 Export of in-bond – container/equipment57 Change arrival of in-bond - complete movement58 Change arrival of in-bond – bill of lading59 Change arrival of in-bond – container60 Change export of in-bond – complete movement61 Change export of in-bond – bill of lading62 Change export of in-bond – container63 Delete arrival of in-bond - complete movement 64 Delete arrival of in-bond – bill of lading65 Delete arrival of in-bond – container66 Delete export of in-bond - complete movement 67 Delete export of in-bond – bill of lading68 Delete export of in-bond – container | Shipment Data | Shipment disposition | Shipment notification |

**Notes:**
In-Bond arrival by Equipment ???

## ANSI X.12 Functionality

- 997 Functional Acknowledgement (FA)
- FAs are used to identify EDI syntax errors within transactions sent to CBP systems
- Generation of the 997 FA is an all or nothing proposition based upon the request of the trading partner
- If trading partner chooses not to receive the 997 FAs they may not, under certain circumstances, receive any acknowledgement from ACE

## Process Flows – One Step Process

**Broker Download**

**Broker Entry Package may be filed**

## Process Flows – Multi Step Process

***SHIPMENT ***

***INFO***

**Preliminary **
**Shipment **
**data**

**Accept/**
**Reject**
**(AR) **

**CBP/ACE/ABI**

**AR**

**Conveyance Arrival**

**Status Release  or Hold.  **
**In-bond Authorized**

**Truck Carrier**

***ENTRY***

***INFO***

***350 ***

***355 ***

***358 ***

***309 p***

**Entry information**

***350 ***

***355***

**Functional Acknow-ledgment. Optional  (FA)**

***997***

**FA**

***997***

***353 ***

**Trip Departure Submit**

**FA**

***355***

**AR**

***997***

**Truck Trip**

**Broker Checks  ABI-**
**Cargo Selectivity **
**results**

**U.S. Entry Filers**

**Broker Download**

**Broker **
**Entry filed**

## Process Flows – Amendments

***309 p***

**Preliminary**
**Manifest**

**Accept/Reject (AR)**

** ****Manifest**
**update**

***355***

***309 y****** ***

***355***

***358***

***355***

***350 ***

**AR**

**AR**

***Broker Entry Package   Filed**

***358***

***355***

***358***

**AR**

***355***

***Broker Checks ABI-Cargo Selectivity results**

**End Of Manifest**

***353***

***355***

***997***

***997***

**Functional**
**Acknowledgement (FA)**

**Functional**
**acknowledgment**

***997***

***997***

**FA**

***997***

**A**
**R**

**FA**

***997***

**FA**

**Manifest  update**

**A**
**R**

**Truck Trip Data**

**FA**

**Conveyance Arrival**

**A**
**M**
**E**
**N**
**D**
**E**
**D**

***Entry INFO***

**U.S. Entry Filers**

**CBP/ACE/ABI**

**Truck Carrier**

***350 ***

**Status Release  or Hold. / In-bond Authorized**

**Broker **
**Download**

## Process Flows – In-Bond

***309 p***

**Original Manifest**

**Accept/ Reject**
**  ****(A/R) **

***355***

***358***

***355***

**Truck**
**Trip **
**Data**

***997***

**Broker Entry Package Filed**

*** ***

*** ***

*** ***

***Broker Checks ABI-**
**Cargo Selectivity results**

***353***

**Arrival at **
**In-Bond **
**Destination**

***355***

*** ******350***

***353***

**AR**

**In-Bond**
**Authorization/ Holds**

***350***

***355***

***997***

**Functional**
**Acknow ledgment**
**(FA)**

*** ***

***997***

**FA**

**A**
**R**

**End **
**of **
**Manifest**

**FA**

**FA**

***997***

**A**
**R**

**In-Bond **
**Shipment **
**Releases &**
**Holds**

***Entry INFO***

**CBP/ACE/ABI**

**Truck Carrier**

**U.S. Entry Filers**

***350***

**Conveyance Arrival**

**Broker download**

## Looping Constructs and Changes

## Split Shipment

- _Scenario:_
- A shipment contains 100 pcs.
- 1st border crossing:
- Trip #1 consists of tandem trailers.
- 75 pcs. are contained within the 2 trailers (30 in trailer #1 and 45 in trailer #2)
- 2nd border crossing:
- Remaining 25 pcs. are on Trip #2 in trailer #1

## Split Shipment

- _ANSI messages:_
- 309 (Preliminary) with the N1001 Trailer = “NC” Quantity = 100
- 358 for Trip #1 with
- VID = Trailer #1 and Boarded Quantity (MBL06) = 30;
- VID = Trailer #2, Boarded Qty (MBL06) = 45
- 353 End of Manifest for Trip #1
- 358 for Trip #2 with
- VID = Trailer #1 and Boarded Quantity (MBL06) = 25
- 353 End of Manifest for Trip #2

## ANSI X-12 Message Details

- Donald Kozacki, CBP

*	**	**	**	**	*
*	**	**	*

## Scenario 1:309 Set Complete Manifest

- ISA*00*               *00*          *02*XXXX           *ZZ*CBP-ACE-TEST   *   040704*0930*^*00406*023182085*0*P*:
- GS*SO*XXXX*CBP-ACE-TEST*20040704*0930*987654321*X*004060USCBP
- ST*309*987654321
- M10*XXXX*T***2004070401*TRUCK***W***0987
- VEH**AB123456789*******KEG123*ON*********BT***A**DOT123456789
**NM1*EJ*1*BLIVIT*MARVIN*R**
**DMG*DB*12251957*M*8*CA**
**REF*ACW*X12345670**CA**
**REF*5K*ON456789012*ON**
- N3*900 SASSAFRAS ST
- N4*ERIE*PA*01234
- P4*0901*07042004***2330
- LX*1
- M11*123456789101*14094*******00*HALIFAX**XXXX************K
- N1*SH*HOSER ARTIFACTS LTD
- N3*751 YORKE ST
- N4*TORONTO*ON*987 1E6
- N1*CN*NEW JERSEY WIDGETS CO
- N3*123 GARDEN STATE PKWY
- N4*NEWARK*NJ* 012345
- VID*OE*********I*DD*KEG345*ON***A
- M7*09876543
- N10*50*WIDGETS,FINELY GRAINED*MADE IN INDIA****L*2000*BOX
- N10**SOLID STEEL
- VID*OE*********I**BUF234*NY***A
- M7*01234567
- N10*50*WIDGETS FINELY GRAINED*MADE IN INDIA****L*2000*BOX
- N10**SOLID STEEL
- SE*27*987654321
- GE*1*987654321
- IEA*1*023182085
**Note:  Segment Terminator is implied**
**NO 358 Set**
**NO 353 Set**

## Scenario 1: 355 Set Acceptance/Rejection of a 309 Set

- ISA*00*          *00*          *ZZ*CBP-ACE-TEST   *02*XXXX           *040704*0932*^*023182085*0*P*:
- GS*SO*CBP-ACE-TEST*XXXX*20040704*0932*987654320*X*004060USCBP
- ST*355*987654321
- M10*XXXX*T***2004070401*TRUCK***W**0987
- P4*0901*7042004***2330
- LX*1
- K3*XXXX0407032300000100100001000000000000000000000000100027
- SE*6*987654321
- GE*1*987654320
- IEA*1*023182085
**Note:  Segment Terminator is implied**

## Alternative Scenario 1: 358 SetCustoms Trip Information

- ISA*00*           *00*          *02*XXXX           *ZZ*CBP-ACE-TEST   *   040704*0930*^*00406*023182087*0*P*:
- GS*SO*XXXX*CBP-DATA-TEST*20040704*0930*987654321*X*004060USCBP
- ST*358*987654321
- M10*XXXX*T***2004070401*TRUCK***S***12345
- VEH**AB123456789*******KEG123*ON*********BT***A**DOT123456789
- M7*098765432*987654321
**NM1*EJ*1*GRAHAM*STEVEN*R**
**DMG*DB*12251957*M*8*CA**
**REF*ACW*X12345670**CA**
**REF*5K*ON456789012*ON**
- N3*900 SASSAFRAS ST
- N4*ERIE*PA*01234
- P4*0901*07042004***2330
**VID*OE*********I****KEG345*ON***A**
**VID*OE*********I****BUF234*NY***A**
- SE*14*987654321
- GE*1*987654321
- IEA*1*023182087
**Note:  Segment Terminator is implied**
**309 pending**
**No 353**

## Alternative Scenario 1: 309 SetPreliminary Bill, After 358

- ISA*00*               *00*          *02*XXXX           *ZZ*CBP-ACE-TEST   *   040704*0935*^*00406*023182086*0*P*:
- GS*SO*XXXX*CBP-DATA-TEST*20040704*0935*987654321*X*004060USCBP
- ST*309*987654321
- M10*XXXX*T*** 2004070401*TRUCK***P***5432
- P4*0901*070404***2330
- LX*1
- M11*123456789101*14094*******00*HALIFAX**XXXX************K
- N1*SH*HOSER ARTIFACTS LTD
- N3*751 YORKE ST
- N4*TORONTO*ON*987 1E6
- N1*CN*GREATER BUFFALO WIDGETS CO
- N3*123 DEARBORN ST
- N4*BUFFALO*NY*14220
**VID*OE********I**DD***KEG345*ON***A**
- M7*09876543
- N10*50*WIDGETS,FINELY GRAINED****L*2000*BOX
- N10**SOLID STEEL
**VID*OE*********I****BUF234*NY***A**
- N10*50*WIDGETS,FINELY GRAINED*****L*2000*BOX
- N10**SOLID STEEL
- SE*18*987654321
- GE*2*987654321
- IEA*1*023182086
**Note:  Segment Terminator is implied**

## Alternative Scenario 1: 353 SetCustoms Events Advisory Details

- ISA*00*           *00*          *02*XXXX           *ZZ*CBP-ACE-TEST   *   040704*1000*^*00406*023182086*0*P*:
- GS*SO*XXXX*CBP-DATA-TEST*20040704*1000*987654321*X*004060USCBP
- ST*353*987654318
- M10*XXXX*T*** 2004070401*TRUCK ***H***6789
- P4*0901*07042004***2330
**M15*Z*2004070401*07032004**XXXX*2130**
- SE*5*987654318
- GE*1*987654321
- IEA*1*023182086
**Note:  Segment Terminator is implied**

## Scenario 2: 309 SetPreliminary Bill, No Trip

- ISA*00*           *00*          *02*XXXX           *ZZ*CBP-ACE-TEST   *   040704*0930*^*00406*023182084*0*P*:
- GS*SO*XXXX*CBP-DATA-TEST*20040704*0930*987654321*X*004060USCBP
- ST*309*987654321
- M10*XXXX*T***SYSTEM*TRUCK***P***3214
- P4*0901*07042004***2330
- LX*1
- M11*123456789101*14094*******00*HALIFAX**XXXX************K
- N1*SH*HOSER ARTIFACTS LTD
- N3*751 YORKE ST
- N4*TORONTO*ON*987 1E6
- N1*CN*GREATER BUFFALO WIDGETS CO
- N3*123 DEARBORN ST
- N4*BUFFALO*NY*14220
**VID*NC**
- N10***100***WIDGETS,FINELY GRAINED*****L*2000*BOX
- N10**SOLID STEEL
- SE*14*987654321
- GE*2*987654321
- IEA*1*023182084
**Note:  Segment Terminator is implied**
**358 Set Pending**
**353 Set Pending**

- ISA*00*           *00*          *02*XXXX           *ZZ*CBP-ACE-TEST   *   040704*0935*^*00406*023182088*0*P*:
- GS*SO*XXXX*CBP-DATA-TEST*20040704*0935*987654321*X*004060USCBP
- ST*358*987654321
- M10*XXXX*T***2004070401*TRUCK** *****S***2345
- VEH**AB123456789*******KEG123*ON**********BT*****123456789
- M7*098765432*987654321
- NM1*EJ*1*GRAHAM*STEVEN*R
- DMG*DB*12251957*M*8*CA
- REF*ACW*X12345670**CA
- REF*5K*ON456789012*ON
- N3*900 SASSAFRAS ST
- N4*ERIE*PA*01234
- P4*0901*07042004***2330
**VID*OE*********I*DD*KEG345*ON***A**
**MBL*XXXX*123456789101*30**
**VID*OE*********I**BUF234*NY***A**
**MBL*XXXX*123456789101*45**
- SE*16*987654321
- GE*1*987654321
- IEA*1*023182088
**Note:  Segment Terminator is implied**
**309 preliminary already on file**

- Scenario 2: 358 SetCustoms Trip Information Trip 1

## Scenario 2: 353 SetCustoms Events Advisory Details Trip 1 

- ISA*00*           *00*          *02*XXXX           *ZZ*CBP-ACE-TEST   *   040704*1100*^*00406*023182089*0*P*:
- GS*SO*XXXX*CBP-DATA-TEST*20040704*1100*987654321*X*004060USCBP
- ST*353*987654318
- M10*XXXX*T***2004070401*TRUCK***H***8765
- P4*0901*07042004***2330
**M15*Z*2004070401*07042004**XXXX*2130**
- SE*5*987654318
- GE*1*987654321
- IEA*1*023182089
**Note:  Segment Terminator is implied**

## Scenario 2: 358 Set Customs Trip Information Trip 2

- ISA*00*           *00*          *02*XXXX           *ZZ*CBP-ACE-TEST   *   040704*1200*^*00406*023182080*0*P*:
- GS*SO*XXXX*CBP-DATA-TEST*20040704*1200*987654321*X*004060USCBP
- ST*358*987654321
- M10*XXXX*T***2004070501*TRUCK****S***6745
- VEH**AB123456790*******KEG103*ON**********BT*****123456789
- M7*098765433*98765422
- NM1*EJ*1*SARANU*SRINIVAS*X
- DMG*DB*01011957*M*8*CA
- REF*ACW*X12345670**CA
- REF*5K*ON456789013*ON
- N3*900 SASSAFRAS
- N4*ERIE*PA*01234
- P4*0901*07052004***0830
**VID*OE*********I**KEG456*ON***A**
**MBL*XXXX*123456789101*25**
- SE*14*987654321
- GE*1*987654321
- IEA*1*023182080
**Note:  Segment Terminator is implied**

## Scenario 2: 353 SetCustoms Events Advisory Details Trip 2

- ISA*00*           *00*          *02*XXXX           *ZZ*CBP-ACE-TEST   *   040704*1210*^*00406*023182083*0*P*:
- GS*SO*XXXX*CBP-DATA-TEST*2004070*1210*987654321*X*004060USCBP
- ST*353*987654318
- M10*XXXX*T*CA**2004070501*TRUCK***H***9056
- P4*0901*07052004***0830
**M15*Z*2004070501*07042004**XXXX*2200**
- SE*5*987654318
- GE*1*987654321
- IEA*1*023182083
**Note:  Segment Terminator is implied**

## Scenario 1: 309 Set In-bond Complete Manifest

- ISA*00*           *00*          *02*XXXX           *ZZ*CBP-ACE-TEST   *   040704*2300*^*00406*023182082*0*P*:
- GS*SO*XXXX*CBP-DATA-TEST*20040704*0930*987654321*X*004060USCBP
- ST*309*987654321
- M10*XXXX*T***2004070401*TRUCK***W***0043
**VEH*********************1234567890*AID*A**
**CII*TRANSPORTERS*A12345*2004*50000**
**NM1*EJ*1******A7*1234567890**
- N3*900 SASSAFRAS ST
- N4*ERIE*PA*01234
- P4*0901*07042004***2330
- LX*1
- M11*123456789101*14094*******00*HALIFAX**XXXX************K*DS
**N9*8S*073090112**
- N1*SH*HOSER ARTIFACTS  LTD
- N3*751 YORKE ST
- N4*TORONTO*ON*987 1E6
- N1*CN*NEW JERSEY WIDGETS CO
- N3*123 GARDEN STATE PKWY
- N4*NEWARK*NJ* 012345
- N1*CB*CHEATUM AND HOWE*BF*073
- N3*101*FRONT ST
- N4*BUFFALO*NY*14207-4207
- PER*IC**EM*CHEATHOWE@BROKERSCAPE.COM
- M12*61**4601*********Y**A123
- VID*OE*********I****KEG345*ON***A
- M7*09876543
- N10*50*FLAMMABLE LIQ FLASH POINT 32 F*MADE IN INDIA*J*4054567891*250000*L*1000*CAN
- N10**STAY FAR AWAY
- VID*OE*********I****BUF234*NY***A
- M7*01234567
- N10*50*FLAMMABLE LIQ FLASH POINT 32 F*MADE IN INDIA****L*1000*CAN
- N10**STAY FAR AWAY
- H1*X123****KIRAN GOWDA*****TE*7036681234
- SE*35*987654321
- GE*1*987654321
- IEA*1*023182082
**Note:  Segment Terminator is implied**

## Scenario 3: 355 Set Customs Acceptance/Rejection of 309 

- ISA*00*          *00*          *ZZ*CBP-ACE-TEST   *02*XXXX           *040704*0932*^*023182082*0*P*:
- GS*SO*CBP-DATA-TEST*XXXX*20040704*0932*987654321*X*004060USCBP
- ST*355*987654321
- M10*XXXX*T***2004070401*TRUCK***W***0043
- P4*0901*07062004***1330
- H1*X123******KIRAN GOWDA*****TE*7036681234
- K1*XXXX123456789101 0901*428 INV UN DANGER GOODS CODE
- K1*XXXX  BILL REJECTED XXXX
- K3*XXXX0407042300000100100001000000000000000000010000000032
- SE*8*987654321
- GE*1*987654321
- IEA*1*023182082
**Note:  Segment Terminator is implied**

## Scenario 3: 353 Set Customs Events Advisory Details

- ISA*00*          *00*          *ZZ*CBP-ACE-TEST   *02*XXXX           *040714*1300*^*023182081*0*P*:
- GS*SO*XXXX*CBP-DATA-TEST*20040714*1300*987654321*X*004060USCBP
- ST*353*987654321
- M10*XXXX*T*** 2004070401*TRUCK ***H***0043
- P4*0901*07042004***2330
**M15*2*123456789101*07142004**XXXX*2330**
- SE*5*987654321
- GE*1*987654321
- IEA*1*023182081
**Note:  Segment Terminator is implied**

## Scenario 3: 350 SetCustoms Status Information 

- ISA*00*          *00*          *ZZ*CBP-ACE-TEST   *02*XXXX           *           040714*1305*^*023182090*0*P*:
- GS*SO*CBP-DATA-TEST*XXXX*20040714*1305*987654321*X*004060USCBP
- ST*350*987654321
- M10*XXXX*T***200407401*TRUCK***W
**X4*123456789101***100*01*12012345678*07042004*2302*1C**XXXX***4601*****4601**
- SE*4*987654321
- GE*1*987654321
- IEA*1*023182090
**Note:  Segment Terminator is implied**

- UN/EDIFACT Standard Manifest

- Karen Henderson, CBP

## UN/EDIFACT Standard Manifest

- Messages transmitted to CBP:
- Customs Cargo Report (CUSCAR)
- Customs Conveyance Report (CUSREP)
- Passenger List (PAXLST)
- Messages transmitted from CBP
- Customs Response (CUSRES)
- Functional Acknowledgment (CONTRL)

## UN/EDIFACT Standard Manifest

- Components
- Trip identifier
- Conveyance (identifiers or details)
- Crew/passenger (identifiers or details)
- Equipment (identifiers or details)
- Shipment (identifiers or details)

## UN/EDIFACT Standard Manifest

-                                  **CUSCAR    CUSREP   PAXLST**
- Trip identifier/arrival date          Yes          Required   Required
- Conveyance details   	       Yes          Yes            No
- Crew Passenger
- Identifiers		        Yes         Yes            Yes
- Details		        	        No           No             Yes
- Equipment details                      Yes         Yes            No
- Shipment
- Identifiers                              Yes          Yes           No
- Details                                   Yes          No             No

## UN/EDIFACT Standard Manifest

- Option 1:
- Original manifest (trip and shipments) via the EDIFACT set CUSCAR “Customs Manifest”
- Option 2:
- Preliminary shipments via CUSCAR
- Trip via EDIFACT message set CUSREP “Customs Trip Information” with shipments listed in Segment Group 3
- Option 3:
- Preliminary shipments via CUSCAR with trip number in BGM segment
- Trip via CUSREP

- Manifest EDI Submission Options

**Notes:**
If a manifesting carrier is in possession of full shipment and trip information, the carrier may transmit an original manifest message (309 Customs Manifest) identifying the trip, conveyance, crew, equipment and shipments associated therewith.  This is considered a complete manifest and no further 358 Consist Information (Trip Information) message or 353 Events Advisory Details message will be required.  
The manifesting carrier may send individual preliminary shipment manifests (309 Customs Manifest) without identifying the trip, conveyance, crew, or equipment.  When shipments are scheduled for movement, the manifesting carrier will transmit a 358 Customs Consist Information (Trip Information) transaction set providing trip, conveyance, crew, and equipment data.  The 358 Customs Consist Information transaction set will be used to link preliminary shipment numbers to the Trip. 
If a manifesting carrier is able to schedule a trip prior to associating the shipments for the trip, the carrier will transmit a 358 Customs Consist Information message (Trip Information) transaction set providing trip number (M1006), conveyance, crew, and equipment data.  When the shipments for the trip have been identified, the carrier will transmit the shipment manifests in the 309 Customs Manifest transaction set as preliminary shipments, making sure to include the M1006  trip number provided prior on the 358 Customs Consist Information (Trip Information) transaction set.  This will enable CBP to automatically associate the preliminary shipments (309’s) with the Trip information. 
     In the second and third scenario, the manifesting carrier will be required to transmit a 353 Customs Events Advisory Details transaction set with a code ‘Z’ ‘End of Manifest’ in the M1501 to signify  the completion of the manifest.  Once the 353 transaction set has been sent to say the manifest is complete, any changes to trip, conveyance, crew, equipment or shipment information will be considered a manifest amendment, and subject to the restrictions provided by law and Regulation. 

## UN/EDIFACT Standard Manifest Manifest EDI and ACE Secure Data Portal Submission Options

- Option 1:
- Preliminary shipments via CUSCAR
- Create trip on ACE Secure Data Portal
- Locate and link shipments on ACE Secure Data Portal
- Option 2:
- Preliminary shipments via CUSCAR with trip number in BGM segment
- Update trip on ACE Secure Data Portal
- Option 3:
- Preliminary shipments on ACE Secure Data Portal
- Trip via EDIFACT message set CUSREP with shipments listed in Segment Group 3

## UN/EDIFACT Functionality

- CUSCAR

## UN/EDIFACT Functionality

- CUSREP

## UN/EDIFACT Functionality

- PAXLST

## UN/EDIFACT Standard Manifest

**Rough equivalents ANSI X.12 v. UN/EDIFACT**
**    **_**ANSI X.12 **_**                                     **_**UN/EDIFACT**_
- 309                                                CUSCAR
- 358                                                CUSREP
- 353                                                CUSCAR or CUSREP
- 997                                                CONTRL
- 355	                                               CUSRES
- 350					CUSRES
- 309/358				PAXLST

## Sample CUSCAR

| Pos. | Example | Description |
| --- | --- | --- |
| 0010 | UNH+TRADE12345+CUSCAR:D:03B:UN’ |  |
| 0020 | BGM+85+XYZU04180001+22’ | Complete manifest submission Trip=XYZU04180001 |
| 0030 | DTM+132:200406281300:203’ | Arrival date/time: 6/28/04,1 pm  EDT |
| 0040 | LOC+60+2304:77:111’ | Port of arrival = Laredo, TX (2304) |
| 0070 | RFF+ABO:LAR04180001’ | Transmission reference number |
| 0100 | NAD+CA+XYZU;109:182’ | Carrier code = XYZU |
| 0100 | NAD+VW+CREW654321’ | ACE id for responsible party |
| 0170 | TDT+11++03+TR++++142BGH:215:111’ | License plate = 142BGH |
| 0180 | LOC+89+TX:163:5’ | License plate registration = TX |
| 0210 | EQD+FL’ | Equipment is a trailer |
| 0326 | RFF+ABZ:ZZP5682’ | Trailer license plate 1 = ZZP5682 |
| 0327 | LOC+89+TX:163:5’ | Trailer license plate registration 1 = TX |
| 0326 | RFF+ABZ:4458SP2’ | Trailer license plate  2 = 4458SP2 |
| 0327 | LOC+89+AZ:163:5’ | Trailer license plate registration 2 = AZ |
| 0210 | EQD+4B+XYZL9823543’ | Container number = XYZL9823543 |
| 0260 | SEL+2QP456985221’ | Seal number |
| 0350 | CNI+1’ |  |
| 0370 | RFF+ICO:XYZU230404180025’ | Waybill # = XYZU230404180025 |
| 0410 | LOC+9+97119:277:310’ | Port of loading, Inland Schedule K |
| 0540 | NAD+OS+++NUEVO LAREDO SUPPLIERS+HIDALGO  6532+NUEVO LAREDO+TM:163:5++MX’ | Shipper name and address |
| 0540 | NAD+CN+99-9999999AA’ | Consignee’s EIN number |
| 0580 | CTA+IC’ |  |
| 0590 | COM+18005555555:TE’ | Consignee’s contact phone number |
| 0640 | GID+1’ |  |
| 0650 | PAC+200++CAS’ | Quantity:  200 cases |
| 0670 | FTX+AAA+++WOODEN GIZMOS’ | Commodity description |
| 0680 | MEA+AAI++K:2672’ | Item gross weight = 2672 kilos |
| 0700 | SGP+ XYZL9823543’ | Container in which goods are packed |
| 0720 | PCI++QUALITY GIZMOS IN A DIAMOND CASES NUMBERED 001 THROUGH 200’ | Marks and numbers |
| 0890 | UNT+30+ TRADE12345’ |  |

## Development and Testing

- Test and Validation

- Elizabeth Phillips

## 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)

**Notes:**
Give brief description of each stage of the testing process. 
Explain the color coding in that Red is done, Green is in process, Orange is yet to come. 
The gates do not represent periods of time but a point in which a particular period starts or ends. 
Testing with the trade on a limited basis will begin in SAT and is intended for self developers and vendors.
Participants operational testing will begin at PRR
Carrier participation will begin with one port and will expand one port at a time.l 

## EDI Test and Validation Plan

***	****	**	*

- Panelists:
- Dale Wilson, CBP
- Jim Wolford, CBP

***Unrestricted***

- Patricia Young, eCP

## Why is Test and Validation Necessary?

- 	Electronic Data Interchange (EDI) testing and validation with the trade community is executed to ensure that software developed and used by the trade community properly interfaces with the Automated Commercial Environment (ACE) and provides accurate data in support of CBP business processes.  The test also verifies a client’s ability to properly send data to ACE as well as receive messages from ACE, using the developed software.

## Test and Validation

- An ACE participant’s computer system software design and hardware, etc. must be completely developed, implemented and ready to interface with ACE prior to the initiation of the testing process with CBP.

## Test and Validation

- Getting Started.....

## Test and Validation

- Letter of Intent (LOI) -
- A “letter of intent” must be submitted by the trade participant identifying their intent to automate and interface with CBP.  It must be on corporate letterhead.
- It must also include information about their computer system requirements, their software vendor or provider, or if self-developer, and other details as noted by the CBP.

## Test and Validation

- The letter of intent is filed with the Client Representative Branch
- Once accepted and approved, allows for the assignment of a CBP Client Representative who works with the participant in support of their automation efforts.
- An ISA must be on file before communications are established

## Test and Validation

- The Client Representative:
- is the primary CBP contact for the trade participant in their automation efforts; working with other CBP staff to prepare for the new testing partner
- provides support to the client throughout the testing phase, including communication attempts; assists in troubleshooting any errors
- acquires the specific system information about the software and interface protocol from the client, service provider or vendor
- identifies the type of testing required of participants, providing them with the appropriate test package

## Test and Validation

- Next Steps:
- The Client Rep will assist in securing the following for the trade participant:
- New communication profiles and queues
-    established,  as appropriate

-  Queue name, etc. designated and provided for use by the
-    participant for access to the Test and Certification Environment

## Test and Validation

- These tests are administered to:
- Software developers and vendors
- Service providers (port authorities, service bureaus, etc.)
- Clients of the software vendors/service providers
- Clients (brokers, carriers, importers, etc.) developing their own application software
*VANs (Value Added Networks) are subject to a communication test only*

## Test and Validation

- Test Package:
- The user test guide (test package) documents the series of scenarios required of the participant in order to pass the test
- The test scenarios cover a variety of situations to ensure the software is capable of dealing with a multitude of conditions

## Test and Validation

- Types of tests:
- A long test will be administered to those participants developing software for ACE, be it for their own use or for distribution to the trade community
- A short test will be administered to those participants who have purchased a software package from an already tested ACE compatible software vendor or for those using a previously tested service provider

## Test and Validation

- Long Test:
- Is a comprehensive test package containing a variety of test case scenarios in an attempt to cover a multitude of CBP business processes
- Includes a communications test to ensure that connectivity is correct and appropriate
- Is administered to any developer of software to be used in the automated processes supported by CBP, including trade participants who are self-developers, software vendors who develop software for sale to trade participants and service bureaus/providers who develop their own software in support of trade participants

## Test and Validation

- Short Test:
- Is administered to trade participants using a vendor or software provider package
- Includes a communication test
- Is a subset of the long test
- Purpose of the short test is to:
- Demonstrate that a client can properly use the vendor’s software package or service provider’s system
- Verify the software program being used by the trade participant is the same version that was tested for this vendor

## Test and Validation 

- Steps required to pass each test scenario:
- A transmission of the EDI message must be sent and the appropriate response received without errors
- If an error message is received by the client, the client must identify the error and correct their software(or notify their vendor/software provider to do so) in order to retransmit the test scenario correctly

## Test and Validation

- The testing client continues to coordinate with the Client Representative for verification of their test results
- The Client Representative reviews all aspects of the transmitted EDI messages/transactions for correct and complete formatting, including optional fields, and troubleshoots problems as necessary

## 
Upon successful completion of the test, the CBP Client Representative authorizes the participant to progress to the status where they are permitted to transmit transactions to ACE in the production environment. 

The testing process must be repeated if the participant changes software packages, service providers, etc.

- Upon successful completion of the test, the CBP Client Representative authorizes the participant to progress to the status where they are permitted to transmit transactions to ACE in the production environment.
- The testing process must be repeated if the participant changes software packages, service providers, etc.

- Test and Validation

**Notes:**
When a client rep works with the vendor to troubleshoot an error in test or production, they will view the pre translated data (raw EDI message) and the post translated data to determine the source of the error. 
Once the user has completed the tests, there is sometimes a minimum time required by CBP prior to authorizing the initiation of ACE transmissions.  Some software vendors constantly test their software, so they have permanent test accounts.
The testing process must be repeated whenever the user desires to change their method of transmission.  For example;
from using a service center to making direct transmissions.
their software vendor changes software version.
the carrier changes service provider.
Once a software vendor passes the extensive test, their name is automatically included on the list of software vendors maintained by the Client Representative Branch of CBP.  That list is posted on the CBP web site and can be mailed to parties who request information related to becoming an ACE EDI participant.

## Test and Validation

- Upon completion of the extensive test by a Software Vendor:
- The company name is included on the list of software vendors maintained by the Client Representative Branch of CBP
- The Software Vendor (provider) list is available on the CBP web site and distributed to parties requesting information to become an ACE EDI participant

## Slide 113