1 / 46

THE QUE GROUP WOULD LIKE TO THANK THE 2013 SPONSORS

THE QUE GROUP WOULD LIKE TO THANK THE 2013 SPONSORS. Using EDI Efficiently - ATA SPEC2000 Implementation. Marcelo d`Arce EMBRAER - Nashville. Who am I … Marcelo d’Arce, Logistics and Tooling Director EAMS – EMBRAER Aircraft Maintenance Services Fully owned subsidiary of EMBRAER

cyrah
Download Presentation

THE QUE GROUP WOULD LIKE TO THANK THE 2013 SPONSORS

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. THE QUE GROUP WOULD LIKE TO THANK THE 2013 SPONSORS

  2. Using EDI Efficiently -ATA SPEC2000 Implementation Marcelo d`Arce EMBRAER - Nashville

  3. Who am I … • Marcelo d’Arce, Logistics and Tooling Director • EAMS – EMBRAER Aircraft Maintenance Services • Fully owned subsidiary of EMBRAER • EAMS has been part of the MRO network since 1991 • Bought by EMBRAER in 2002 as a parts of the company aftermarket strategy. • Quantum GoLive on 3/28/2008 • Some company facts: • 700 employees • 10 maintenance docks • 3500+ PN on our capabilities list • Over 200,000 man hours (2012)

  4. In This Session … • Introduction • Why was it implemented ? • Time line • Functionalities, Orchestration and Additional Enhancements • Gains • Points of concern • Lessons learned

  5. In This Session … • Introduction • Why was it implemented ? • Time line • Functionalities, Orchestration and Additional Enhancements • Gains • Points of concern • Lessons learned

  6. What is ATA SPEC2000? • It is a set of e-commerce specifications, products and services designed to create a “common language” amongst the airline industry (airlines, aircraft manufacturers, suppliers, MRO, etc). It is design to streamline communications and increase operational efficiencies.

  7. Introduction • This presentation is focused on the Embraer Nashville implementation • Business oriented • ATA SPEC2000 has 17 chapters. This presentation will be focused on: • Chapter 3 – Order Administration • Chapter 4 – Customer Invoicing • Other Chapters are: • Chapter 1 – Provisioning • Chapter 2 - Procurement Planning • Chapter 5 - Information and Data Exchange • Chapter 6 - Communications Commands • Chapter 7 - Repair Order Administration • Chapter 8 - Repair/Overhaul Planning • Chapter 9 - Automated Identification and Data Capture • Chapter 10 - SPEC2000/ASC X12 Implementation Guide • Chapter 11 - Reliability Data Collection/Exchange • Chapter 12 - Airline Inventory Redistribution System (AIRS) • Chapter 13 - Industry Performance Metrics • Chapter 14 – Warranty • Chapter 15 - Delivery Configuration Data • Chapter 16 - Electronic Parts Certification Forms • Chapter 17 - Electronic Logbook

  8. In This Session … • Introduction • Why was it implemented ? • Time line • Functionalities, Orchestration and Additional Enhancements • Gains • Points of concern • Lessons learned

  9. Why was it implemented? • Reduce work load on both ends of EMBRAER (Nashville and Customer Response Center – SJK) • Allow fast reponse time for all orders, especially AOGs; • “Test Bench” for future integrations • Support future developments

  10. FACTS • Biggest EMBRAER integration • Integration connects 4 main steps: • Data transactions: BNA CC E2Open SAP Info Info Info

  11. In This Session … • Introduction • Why was it implemented ? • Time line • Functionalities, Orchestration and Additional Enhancements • Gains • Points of concern • Lessons learned

  12. Time line Project Lauch 2009 ContractSigned 2010 Boarding meeting and documentation Tests initiated 2011 GoLive! 2012

  13. In This Session … • Introduction • Why was it implemented ? • Time line • Functionalities, Orchestration and Additional Enhancements • Gains • Points of concern • Lessons learned

  14. Functionalities, Orchestration and Additional Enhancements • Send, receive acknowledgements, send a change order, receive a change order, and cancel orders • Invoice Processing • How does it work? • Little tricks

  15. Send orders and receive order acknowledgments

  16. Send orders and receive order acknowledgments

  17. Send orders and receive order acknowledgments

  18. Send orders and receive order acknowledgments

  19. Send orders and receive order acknowledgments

  20. Send orders and receive order acknowledgments

  21. Send orders and receive order acknowledgments

  22. Send orders and receive order acknowledgments

  23. Send orders and receive order acknowledgments

  24. Seller change Requests

  25. Seller change Requests

  26. Seller change Requests

  27. Seller change Requests

  28. Seller change Requests

  29. Shipping Notices (AWB)

  30. Shipping Notices (AWB)

  31. Little Tricks

  32. Standard with a twist

  33. In This Session … • Introduction • Why was it implemented ? • Time line • Functionalities, Orchestration and Additional Enhancements • Gains • Points of concern • Lessons learned

  34. Gains • Paperless: Less mistakes • Reduced administrative time and cost • Updates: 33,000 transaction*30 seconds = 275 hours • PO creation: 15,000*45 seconds = 187 hours • Total: 462 hours • Lead time reduction: reduced inventory • Standard with a twist

  35. In This Session … • Introduction • Why was it implemented ? • Time line • Functionalities, Orchestration and Additional Enhancements • Gains • Points of concern • Lessons learned

  36. Points of Concern • Clear business definition and scope • Pre-planning • Size • Follow-up

  37. Clear business definition and scope • Is ther any other update/enhancements that should work together with this one? • Freight forward integration • Reports • Work-flows • automation • Time frames and responsibilities: who does what and when • Service Level Agreements

  38. Pre-Planning • Do you need to design your screens? • Did you involve all needed parties? • Should you align unit of measure with your business partners?

  39. Size • Do you have the right servers? • Do your partners have the right servers?

  40. Follow-up • Understand the important steps and measure them

  41. In This Session … • Introduction • Why was it implemented ? • Time line • Functionalities, Orchestration and Additional Enhancements • Gains • Points of concern • Lessons learned

  42. Lessons Learned • Training is never enough • Better undestanding of the consequences (receiving)

  43. Where to Find More Information • www.spec2000.com • http://en.wikipedia.org/wiki/Electronic_data_interchange

  44. Key Points to Take Home … • Think BIG • Pre-plan • Create the plan based on the previous step and follow it • Follow up your process until it is fully stable

  45. Your Turn! ? Questions? How to contact me: Marcelo d’Arce Marcelo.darce@embraer.com Cel.: +1 615 202 2528 Please remember to complete your conference evaluation

  46. Disclaimer The Content provided is expected to be for the sole use of paying members and not to be disseminated outside of its intended audience, or sold without prior consent of both the QUE Group and the originator of the document or presentation. For Questions regarding the QUE Group, please visit www.quegroup.org

More Related