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 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 PN on our capabilities list Over 200,000 man hours (2012)

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

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

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

 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

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

 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

 FACTS – Biggest EMBRAER integration – Integration connects 4 main steps: – Data transactions: BNA Info CC E2O pen SAP

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

 Time line JanFebMarAprilMayJunJulAugSepOctNovDecJanFebMarAprilMayJunJulAugSepOctNovDecJanFebMarAprilMayJunJulAugSepOctNovDec Project Lauch ContractSigned Boarding meeting and documentation Tests initiated GoLive!

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

 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

 Send orders and receive order acknowledgments

 Seller change Requests

 Shipping Notices (AWB)

 Little Tricks

 Standard with a twist

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

 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

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

 Points of Concern – Clear business definition and scope – Pre-planning – Size – Follow-up

 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

 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?

 Size – Do you have the right servers? – Do your partners have the right servers?

 Follow-up – Understand the important steps and measure them

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

 Lessons Learned – Training is never enough – Better undestanding of the consequences (receiving)

 Where to Find More Information – – rchange rchange

 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

 Your Turn! ? Questions? How to contact me: Marcelo d’Arce Cel.: Please remember to complete your conference evaluation

 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