1 / 20

Electronic Data Interchange (EDI)

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.

verlee
Download Presentation

Electronic Data Interchange (EDI)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Electronic Data Interchange (EDI) 20 – 22 May 2003

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

  3. 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.

  4. Definition of EDI Electronic Data Interchange is the exchange of data between computers in a pre-defined format agreed upon by both parties.

  5. 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

  6. EDI Usage Statistics

  7. EDI Usage Statistics

  8. EDI Usage Statistics

  9. EDI Usage Statistics

  10. Case studies: Shipping instructions Shipping instruction Create shipment USI Status update Status trigger 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

  11. Case Study : Reebok Client Purchase Order Create PO Link PO & HB Despatch Advice Shipment info DA Status eMpower Reebok UTi Operations u C O N N E C T uOrder EDIFACT ORDER uTrac EDIFACT DESADV 134 man hours

  12. Case Studies : Dow Corning (Inbound) Delivery Order Delivery Order Pick Confirm Create Job Goods Issued USI Create TM Create HB USI eMpower UTi Operations Dow Corning eSys u C O N N E C T ANSI 856 uTrac ANSI 856 uOp2000

  13. Case Studies : Dow Corning (Outbound) POD Delivery POD Actual Delivery Date Road Carriers eMpower UTi Operations u C O N N E C T uTrac Dow Corning ANSI 214 1666 man hours

  14. Case Studies : Apple Computers (In) Warehouse Shipping Advice Create HB Finalize HB & Assign to MAWB eMpower Apple OEMs UTi Operations u C O N N E C T uTrac ANSI 945

  15. Case Studies : Apple Computers (Out) Advance Shipping Notification BO Status RV, DA, AR, DC Status Status Update eMpower Apple u C O N N E C T uTrac ANSI 856 BridgePoint 772 man hours ANSI 214

  16. EDI Process Business must give the green light to go ahead with the project. Client contact report 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 Confirm process and data correctness with the client

  17. 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

  18. Summary A successful EDI solution depends on a partnership between the client, UTi operations, regional and global IT teams

More Related