Presentation on theme: "Electronic Data Interchange (EDI) 20 – 22 May 2003."— Presentation transcript:
Electronic Data Interchange (EDI) 20 – 22 May 2003
Agenda Learning Points Definition of EDI EDI usage in UTi Case Studies EDI process Potential problem areas Summary
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.
Definition of EDI Electronic Data Interchange is the exchange of data between computers in a pre-defined format agreed upon by both parties.
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 XML IDOC SAP systems Cargo-Imp Cargo Community Systems USI
EDI Usage Statistics
Case studies: Shipping instructions Regional System Shipping instruction uCONNECTuCONNECT uTrac Create shipment Client eMpower UTi Operations Status trigger Status update Pending shipment USI Cost & time savings : Eliminate Faxing of Instruction Improved Data Quality : Reduce Data Capture Visibility : Client has status on own system
Case Study : Reebok uOrder Client Purchase Order uCONNECTuCONNECT uTrac Link PO & HB Reebok eMpower UTi Operations Shipment info DA Status Despatch Advice Create PO EDIFACT ORDER EDIFACT DESADV 134 man hours
Case Studies : Dow Corning (Outbound) uCONNECTuCONNECT uTrac Dow Corning eMpowerUTi Operations Actual Delivery Date PODDelivery Road Carriers POD ANSI man hours
Case Studies : Apple Computers (In) Warehouse Shipping Advice uCONNECTuCONNECT uTrac Apple OEMs eMpower UTi Operations Finalize HB & Assign to MAWB Create HB ANSI 945
Case Studies : Apple Computers (Out) uCONNECTuCONNECT uTrac Apple eMpower BridgePoint BO Status Advance Shipping Notification RV, DA, AR, DC Status Status Update ANSI 856 ANSI man hours
EDI Process Client contact report Confirm process and data correctness with the client Develop SOP & train operational staff Deploy and activate the interchange Manage and monitor the interchange Evaluate client requirement Assign IT project leader Business Requirement definition & analysis Message specifications & Client EDI Agreement Project planning and scheduling Develop & Testing solution Business must give the green light to go ahead with the project.
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
Summary A successful EDI solution depends on a partnership between the client, UTi operations, regional and global IT teams