Honda Certification EDI ECommerce

1. Honda Certification EDI ECommerce MFG/PRO Midwest User Group 2001 Fall Conference

2. Agenda • Vision and its Drivers • EDI priorities • Honda Certification • Questions

3. QAD VisionPriorities • Integrated product suite for e-business solutions • e Business connectivity • Event-driven processing • Interoperability

4. MFG/PRO VisionPriorities • Global manufacturing featuring an outward facing, web-centric, designed-to-integrate ERP system • Event-driven Business • Interoperable Systems • Service and Support

5. EDI VisionEDI Priorities • Support QAD’s Interoperability Direction • Global EDI capabilities • Honda Certification • European Extensions • Library and Gateway Growth

6. Requirement Drivers Supply Chain Management Drivers “We very much believe in focusing on speeding the flow of information through all levels of the supply chain, a node at a time..”(Pam Lopker, Chairmen and President of QAD) Other Drivers Technology Competition Business Processes

7. Value Chain Participation

8. Facility Private Exchange Private Exchange Sell-Side Integration Buy-Side Integration Manufacturing Buy-Side Sell-Side Financials Service Full Supply Chain Support Enterprise EDI EDI EDI EDI Supplier Customer EDI Public Exchange Supply Visualization

9. EDI ECommerce XML Architecture Other Applications XML XML S N F • Exchange • Document • Master • Detail • MFG/PRO • Document • Master • Detail Communications Package EDI Map Load / Unload Transform Transfer RAW*EDI Mfg/Pro Gateways Map Description Mfg/Pro Transformation Logic Turnaround EDI Subsystem QAD - world RAW* - Raw files (EDIFACT, X12, ODETTE, VDA, Proprietary ...)

10. EDI Priorities

11. EDI ECommerce • De-coupling from MFG/PRO • Integration with Supply Visualization in ASP model • Common integration framework • Continually Expand: • API portfolio • Trading Partner Library • Gateways • XML, EDI, and other formats • Global EDI standards compatibility • Honda Certification

12. Honda Certification

13. Honda of America ManufacturingApproval Process • Purpose: • To establish an approval process to ensure EDI and bar code communications between Honda of America Manufacturing (HAM) and it’s suppliers meets specifications. • Goal: • To verify that the integrated EDI and bar code solution meets HAM’s 4010 EDI and bar code specifications. • Only software solutions approved by HAM may be used to communicate via EDI with HAM. • Process • Multi-phase process of gaining approval will be required. • Phase 1 thru 4.

14. HAM Certification Types • Software Solution Provider • HAM considers a “software solution” to be an integrated product or a strategic alliance of an EDI and bar code solution. • Requires complete certification of all Honda document and process requirements. • Supplier Hybrid Solution • Option for supplier to certify on-site only necessary Honda document and process requirements.

15. Project Plan • Phase 1 • Submit Project Plan • Communication Testing with IBM Global Services • Phase 2 • Ambassador Kit Testing – Submit Rip and Read docs • Process Ambassador Kit documents • Submit error free Analyzer reports, bar code labels and Master Packing List. • Send Submit completed check sheets • Phase 3 • Send Inbound to Honda documents • Submit ASN and Inv Advice screen prints. • Phase 4 • Site visit demo. Final approval processing of HAM data with the HAM Supplier Interface Team.

16. Honda America Mfg • Delta • GPCS • Star 830 Plan / 862 Delta Ship / 856 ASN / 864 Text 850 Order / 846 Inv / 820 Remit / 824 / 861 830 Plan / 862 Gpcs Ship / 856 ASN / 864 Text 850 Order / 846 Inv / 820 Remit / 824 / 861 850 Plan / 830 Ship / 856 ASN

21. 3.2.A1.Create an ASN (856 GPCS). Submit your data entry screen-print to NAP for this transaction. ·           Respond to the Purchase Order (850) test data with a NAP document ID Number: ZB0000072 ·           Create a valid ASN number ·           Create dates where necessary ·           Use the SCAC code listed in the 850 ·           Trailer number: 32A123 ·           Pallet and Container Packaging Type: XX ·           Ship the quantity on the PO Trailer #: 532AEF123 BOL #: 5FE789 (unless system generated) SCAC Code: CUOT P/N: 32140S84 Y400 Quantity: 15 Container type: XX Fixed Asset Tag S/N: N/A P/N: 32140S84 Y400 Quantity: 15 Container type: XX Fixed Asset Tag S/N: N/A PO Doc. ID #: ZB0000072 Ship to: ALB Ship date: 4/2/01 Ship time: 1300 Pallet type: XX Fixed Asset Tag S/N: N/A The purpose of this scenario is to verify: ·System’s replacement logic is working properly ·Ability to respond to 850 – Purchase Order ·Use of expendable containers ·Ability to process Project numberAbility to respond to STAR order

22. QAD Honda Partners • EC Subsystem • Trinary - EDI Windows • Oxford Consulting - Sterling Gentran • Others • Bar Code Integration • Eagle • Freedom

23. New Gateways • 864 Text Document • Interface to 830/846/850/862 • 846 Inventory Advice • Receive Inventory Advice cycle count • DSPS recipients send three types of Inventory Advices • Cycle count • Inventory Advice • Receipt Advice

24. Honda Certified • Where are we Today • One GPCS supplier certified Hybrid • Tentative plan 2nd week of December for final approval. Trinary / Eagle / MFG/PRO 9.0. • Next Gentran / Eagle / MFG/PRO eB. • Next ? / Freedom / MFG/PRO eB.

25. NAP Supplier Interface Approval Process Post-Testing Agreement The following were created to establish a uniform set of guidelines for NAP and the Approval Applicants. Software Update Policy: NAP initiated change: When NAP issues a major specification update, the change in the hybrid or software providers software must be completed and successfully tested with NAP within 90 days of specification change issuance, and must be installed at all applicable locations within 180 days of NAP specification change issuance. Supplier or software provider initiated change: After approval, if there is a major software change or upgrade, NAP must be contacted. Testing requirements will be determined on a case by case basis.

26. Questions?