Building the Foundation for Global Enterprise Integration

1. Building the Foundation for Global Enterprise Integration Pat SnackGM Loaned Executive AIAGAutomotive Industry Action Group (focus on P2B by Tim Thomasma)

2. AIAG Overview • Globally recognized automotive trade association – provide standards direction • Solve industry business problems to improve operations and trading partner collaborations • Focus: common business processes and technical solutions, implementation guidelines and education and training • Manufacturing has always been in scope

3. Strategic Relationships(Specific to Integration) • JAMA/JAPIA (Japan) • ODETTE / VDA (Europe) • STAR/NADA (Automotive Retail and Dealers) • National Institute of Standards and Technology (NIST) • KorBIT (Asia-Pacific Test Environment) • Enterprise Interoperability Centre (EIC-Europe) • PDES (STEP standard for design data)

4. StrategicRelationships cont’d) • National Standards: ANSI • International Standards Organizations: UN/CEFACT, ISO, IEC, ITU and Management MOU Group • OAGi • Reciprocal memberships with OASIS, WS-I

5. AIAG Standards Development Model Global Companies Government Regulation (US, EU, Japan) Standards to Run Business Resources Compliance • Automotive Implementation Guideline • Process • Data Formats • Technical Solutions • Regional Standards and Standards Development Organizations • ANSI • SASIG • OASIS • WS-I • International • Standards • UN/CEFACT • ISO • ITU • IEC • WTO • WCO • Examples: • Material Replenishment • Ergonomics • Safety • Warranty • Technology • - Bar Coding • - EDI/XML • - RFID • - STEP • Volunteers • Define Best • Practices: • Solve business problems • Develop technical solutions • Validate Integration Cost Compliance Costs Trading Partner Collaboration

6. Global acceptance You control your own destiny if you have standards Open standards lower costs International - International Standards Organizations (ISO) Regional - American National Standards Institute (ANSI) Industry Corporate - GM 1737 GM 1737 bar codes are fully compliant with ISO/ANSI/AIAG standards GM 1737 is fully compliant with GMNA verification and traceability requirements Practical Standards Application (in P2B Quality and Traceability we start by harmonizing several specific company standards) IS&S Global Manufacturing & Quality

7. Definition Languages SemanticDefinitions Policies Profiles & B2B Communication Framework DOM, Java Beans, JAX(X), .NET, SAX, Portal frameworks and related specs WSRP, JSR168, etc. (why AIAG always wants to drive standards convergence) UBL, OAGIS BODS, UNSPSC, VICS, PIDX, GISB, xCBL, etc. APIs XML, XML Schema, WSDL 1.1/1.2, XSLT. R e g i s t r y Management SNMP, JMX, WBEM, note: standards gaps exist in all areas of Change, Operational, Service Level, and Audit Management ebXML Registry, CPP/CPA, UDDI 2.0/3.0 Business Process and Transaction Services ExtendedMessaging Infrastructure Base Messaging Infrastructure Transports ebXML Messaging, AS1, AS2, WS Authorization, SAML, WS Federation, WS Reliability, WSReliable Messaging, WS Security, WS Trust, WS Policy, XML Signature, XML Encryption, XACML. Application Server Operating System WSCI, BPML, ebXML BPSS, WS-BPEL, Business Transaction Protocol, WS-Transaction TCP, IP v3, HTTP(S), FTP, SMTP SOAP 1.1, 1.2, SOAP with Attachments, DIME, WS Addressing, WS Routing, ebXML Messaging J2EE, .NET

8. AIAG Automotive B2B Vision AIAG Interoperability Approach • Consistent use of international standards to express business process design and data • Harmonize business global vocabularies • Utilize test environments to validate solutions • Provide industry users consumable artifacts to run business

9. AIAG Project Management Approach Core Components – ISO UN/CEFACT GEFEG EDIFIX Tool JAI Joint Automotive Data Model AIAG JAMA/JAPIA Odette STAR XML Schema – OAGIS BODs Modeling - UML/UMM Project Management Process Consistent Work Templates POC Testing Environment So far P2B has used these and the Rational Software Architect tool Regional Global

10. AIAG Project Management Process 2nd Qtr 2006 AIAG Governance 8/22/06 Idea Acceptance Pre-Plan Define / Model Analyze Phase Gate Project Nominated These phases may be repeated as needed “Call to Action” Project Qualification Organize Work Groups OK toPre-plan Obtain Resources & Leadership Define Overall Charter Current State Build Project Phases Ideal State Validate Business Case Definition Develop Project Plan Deploy Build Guideline Gap Analysis Prepare for Kick-Off Internal Review Future State POC Testing Stakeholder review • Narrative of: • - Current State • Ideal State • Gap Analysis • - Future State Guideline Project Charter • Business Case • -Governance • Model • -Project Scope • -Resource • Needs • Cost/Benefit Communication Plan Project Plan • Business Process Model • - Use Case Narrative and Diagrams • - Activity Flow Diagram • Sequence Diagrams • Collaboration Diagrams Templates & Work Products Kick-off Meeting • January 2007 • 2 P2B projects: • Quality/Traceability • Technical Framework

11. Auto Manufacturers Need Flexibility and Agility • Effective, Agile Product Launches • Global Integration and Collaboration • Materials and Manufacturing • Engineering • Quality • Sense and respond to problems quickly • Enable end-to-end data visibility

12. Automotive Manufacturing: 43,000 Suppliers, 14,000 Parts Per Vehicle Source: Tony Friscia, President & CEO, AMR Research, 08Dec05 “AMR Update: Current Trends in IT Spending”

13. AIAG Project Work • Inventory Visibility & Interoperability: Phase 2 – eKanban • ATHENA Grant Project (Europe—potential funding source) • RFID • Materials Off-shore Sourcing • Early Warning Standards-Warranty • eAPQP-Advanced Product Quality Planning • Quality Metrics – Gauge Integration • Plant Floor to Business (P2B)

14. Capabilities Being Tested • Semantic integration at payload level • Schema structures • Reliable and secure messaging with addressing • Web Services transport based on RAMP (Reliable Asynchronous Messaging Profile) • Collaboration with WS-I on Reliable Secure Profile (RSP) – stabilize cross industry

15. Supplier S eKanban(how everybody started doing B2B on web) Supplier has two customers What if they had five??? Customer SV with data from ERP (ERP gets data from plant system) IV Tool A C1 Hosted by 3rd Party Exchange IV Tool B Customer data from plant system C2 Hosted by C2

16. Tool A: Screenshot Supplier View – Customer 1

17. Tool B: Screenshot Supplier View – Customer 2

18. IV&I: Software Tools InteroperateUsing AIAG Solution Customer data from ERP Supplier selects tool of choice Tool A C1 Supplier S eKanban BODs & Protocol Tool B Customer data from plant system C2

19. Aggregated Data Screenshot

20. IV&I Phase 1 Published Artifacts (IBP-1) IVI Business Processes • Min/Max • Kanban • Sequencing • Schedules and Forecast IVI Business Processes • SyncShipment • SyncQOH • SyncDelivery Receipt IVI Data Messages (XML BODs) For P2B Transport: Web Services plus OPC-UA for device communication IVI Transport (ebXML) IVI Transport (Web Services) POC Whitepaper I-1 Note: Completed item

21. AIAG Automotive B2B Vision Plant Floor to Business • Lead participants: Ford, GM, Honda, American Axle, IBM, Rockwell Automation, Siemens • Build automotive industry model to support larger integration effort by ISA-95, OAGi, MIMOSA, WBF and OPC • Use case scenarios • Data terminology and formats • Contribute to schema design based on industry requirements • 45 companies have now joined

22. Manufacturing Interoperability Guideline Working Group (MIG) Process, Discrete, and Mixed-Mode Manufacturers ISA WBF OAGi OPC MIMOSA Mfg IOP Standards Customer Advisory Council(~30 large mfrs with ARC support) Mfg IOP Guideline Working Group(a collaborative venture) Advice & Direction Business scenarios Technologies Unified needs Deliverables: • Converge OAGIS, B2MML, and ISA-95 • Converge MIMOSA and OPC w/above • Converge OMAC and Make 2Pack w/above

23. Manufacturing Interoperability Guideline Working Group (MIG) Process, Discrete, and Mixed-Mode Manufacturers ISA WBF OAGi OPC MIMOSA Mfg IOP Standards Customer Advisory Council(~30 large mfrs with ARC support) Mfg IOP Guideline Working Group(a collaborative venture) Advice & Direction Business scenarios Technologies Unified needs Deliverables: • Converge OAGIS, B2MML, and ISA-95 • Converge MIMOSA and OPC w/above • Converge OMAC and Make 2Pack w/above

24. Generic Manufacturing Business Functions Engineering Systems Shop Floor Systems ERP/SCM Systems PLM ERP • Project Planning • Production Planning • Scheduling • Inventory Tracking CAPP • Eng Documents • Eng BOM • CAD Models • Images • Change Mgmt • Process Planning • Instruction Authoring Supplier Mgt • Purchasing • Supplier Quality • Scheduling MES • Work Order Execution • Data Collection • Labor Collection Asset Mgt Labor Reporting Systems • Accountability • Maintenance • Disposition QA T&A HR • Inspection Plans • Defect Tracking • Personnel • Training • Qualification

25. Complexity App 2 App 1 App 4 App 3 App 5 App 6 App 7 Ford Motor Company – P2B IntegrationDrivers – Ideal State • Domain Key Entities • Vehicle Orders • Stock Replenishment Orders • Order Schedule • Domain Key Processes • Accept Vehicle Customer Orders • Enter Order into Production & • Delivery Process • - Document & Monitor Orders Order Management Domain Vehicle Order Schedule Interactions • Domain Key Processes • Make Product • Package Product • Schedule & Perform • Maintenance Manufacturing Domain Order Status • Domain Key Entities • Vehicle • Part

26. P2B Scenario 1: Traceability/Quality ERP/SCM Systems Supplier Systems Shop Floor Systems MES Component / Assembly Identification ERP * Work Order Execution * Data Collection • Scheduling • Inventory Tracking • Genealogy Component / Assembly Identification QA * Work Order Execution * Data Collection Order Content/Sequence (broadcast) Component / Assembly Identification Order Defect Status MES * Inspection Plans * Defect Tracking Defects Order Content/Sequence (broadcast) Order Defect Status Order Content/Sequence (broadcast) Order Defect Status Supplier Mgt Shipping / Production Holds / Release QA • Purchasing • Supplier Quality • Scheduling * Inspection Plans * Defect Tracking

27. Why We Need Traceability • Rapid sense and respond to problems • Incoming part quality • Manufacturing defects • Feedback from warranty data and consumer related reporting • Need to root cause the problem – need supplier data: serial number, lot number, etc. • Government mandates • Continuous improvement

28. P2B Work Products • Business Process Work Group: • Use cases, data field list and messages • Alignment discussions with other AIAG projects • Technical Framework Work Group: • Infrastructure requirements • Reference architecture • AIAG Enterprise Interoperability Showcase – Rock Financial, Novi, MI on November 15, 2006

29. P2B BusinessProcess Group • You reviewed the use cases and data fields earlier this week • Other AIAG projects producing similar content: • Early Warning System – Warranty • eAPQP • Dimensional Markup Language • Quality Measurement Data Standard • Other similar content: • Material Safety Data Sheets • STAR RepairOrder

30. P2B TechnicalFramework Group Draft reference architecture Will be distributed for review in February

31. Next Steps • AIAG BOD Team working on EWS-Warranty now. Ready for us in March. • Preparation until then: • UML Class Diagrams • Identify key interactions in the sequence diagrams, and subsets of data for each • Begin BOD construction using GEFEG tool • Begin planning for Proof of Concept

32. In Summary • Have instituted a structured approach to solving business problems: • Based on international standards • Addresses both process and technical solve • Undertaking several simultaneous projects across the manufacturing enterprise • Cooperatively working with other organizations

33. For Further Information • Pat Snack – psnack@aiag.org • www.aiag.org • P2B • Tim Thomasma – tthomasm@ford.com • Steve Rudelic – srudelic@aiag.org • AIAG Enterprise Interoperability Showcase – Rock Financial, Novi, MI on November 15, 2006