Electronic Data Interchange (EDI) transmits paper-based instructions and documents electronically (computer-to-computer). EDI is becoming the standard in intercompany transactions, particularly in ordering, distribution, and payable and receivable transactions.
EDI allows ASI to communicate with its customers. ASI has established a global information network based on a Sun Microsystems platform and actively communicates with its business partners through networks supported by third-party vendors.
ASI has established a communication platform to exchange information with its business partners:
| ASI Supported ANSI X12 Transaction Set Summary | ||||
|---|---|---|---|---|
| Trans. No. | Type | Description | Sent from/to | |
| 204 | Dray Request | To request rail delivery or pickup | Carrier/Terminal | |
| 301 | Booking | To accept a booking request | Carrier/Terminal | |
| 310 | Manifest | Contains all B/L and container data | Carrier/Terminal | |
| 315 | Status details | To notify terminal of Customs/Carrier releases | Carrier/Terminal | |
| 322 | Terminal Operations | In and out gate activity | Terminal/Carrier | |
| 324 | Vessel Stow Plan | To notify Carrier of vessel stowage | Terminal/Carrier | |
| 361 | Interchange Agreement | To notify Terminal of Insurance updates | Carrier/Terminal | |
| 850 | Purchase Order | To notify Terminal of Delivery information | Owner/Terminal | |
| 856 | Ship Notice | To notify Owner of Delivery made | Terminal/Owner | |
| UN/EDIFACT Transaction Set Summary | |||
|---|---|---|---|
| Transaction | Type | Description | From/To |
| BAPLIE | Bay Plan | Used for loading to Vessel Planing programs (Planmaster, Masterplan, Navis, Etc.) |
Planning Clerk/Planning Clerk |
| Proprietary File Formats | |||
|---|---|---|---|
| Transaction | Format | Description | From/To |
| Bay Plan | CSF | Used for loading to MCTS (Planmaster) | Planning Clerk/Planning Clerk |
| Interchange | Fixed Length | Used for updating Truckers Insurance | UIIA/Terminal |