Electronic Data Interchange (EDI)

1
(No Transcript)
2
Electronic Data Interchange (EDI)
20 22 May 2003
3
Agenda

• Learning Points
• Definition of EDI
• EDI usage in UTi
• Case Studies
• EDI process
• Potential problem areas
• Summary

4
Learning Points

• What is EDI ?
• EDI adds value to our customers and our
  operations.
• Our EDI product is called uConnect.
• Most EDI solutions are unique due to the
  different demands from customers.
• Providing an EDI solution follows a well defined
  process in UTi and requires teamwork.

5
Definition of EDI
Electronic Data Interchange is the exchange of
data between computers in a pre-defined format
agreed upon by both parties.
6
Formats used in UTi solutions
ANSI X.12 Mainly US implementation 856
ASN 214 Status 850 Order 210 Invoice
EDIFACT IFTMIN Shipping Instruc IFTSTA Status
Update ORDER Purchase Order
USI
XML
Cargo-Imp Cargo Community Systems
IDOC SAP systems
7
EDI Usage Statistics
8
EDI Usage Statistics
9
EDI Usage Statistics
10
EDI Usage Statistics
11
Case studies Shipping instructions
Cost time savings Eliminate Faxing of
Instruction
eMpower
Client
UTi Operations
u C O N N E C T
Regional System
Pending shipment
Improved Data Quality Reduce Data Capture
uTrac
Visibility Client has status on own system
12
Case Study Reebok
eMpower
Reebok
UTi Operations
u C O N N E C T
uOrder
EDIFACT ORDER
uTrac
EDIFACT DESADV
134 man hours
13
Case Studies Dow Corning (Inbound)
eMpower
UTi Operations
Dow Corning
eSys
u C O N N E C T
ANSI 856
uTrac
uOp2000
ANSI 856
14
Case Studies Dow Corning (Outbound)
eMpower
UTi Operations
Road Carriers
u C O N N E C T
uTrac
Dow Corning
ANSI 214
1666 man hours
15
Case Studies Apple Computers (In)
eMpower
Apple OEMs
UTi Operations
u C O N N E C T
uTrac
ANSI 945
16
Case Studies Apple Computers (Out)
eMpower
Apple
u C O N N E C T
uTrac
ANSI 856
BridgePoint
772 man hours
ANSI 214
17
EDI Process
18
Potential problem areas

• No clear definition of the real requirements
• Incomplete analysis phase
• Changes in specifications/requirements mid-stream
• Data quality
• Timeliness of correct and complete data
• Incomplete or inaccurate data requirements
• Customer SOPs
• Non existent or out-dated
• Not addressing real data requirements from a
  business perspective
• Non compliance by operations

19
Summary
A successful EDI solution depends on a
partnership between the client, UTi operations,
regional and global IT teams
20
(No Transcript)