User Case Study QXtend Implementation At Visteon Session

User Case Study: QXtend Implementation At Visteon – Session I John Pearson, Visteon Corporation Gary Yang, RCM Technologies

Introduction

Introduction

Reorganization • Filed for Chapter 11 protection in the U. S. on May 28, 2009 • Continuing operations throughout the reorganization process • Focused on emerging a strong, financially sound company, well-positioned to succeed in the global automotive industry

Product Portfolio ►Engine Induction ►HVAC Systems ►Powertrain Cooling ►Compressors ►Fluid Transport ►Cockpit Modules ►Instrument Panels ►Consoles ►Door Trim ►Audio and Infotainment ►Instrumentation and Displays ►Powertrain and Feature Controls ►Control Panels ►Front/Rear Lighting

Customers Are Key

Global Manufacturing Capabilities • 74 global facilities* – – Asia Pacific Europe North America South America 21 28 19 6 • Our focus: – – Lean, flexible production Continuous quality improvement World-class safety levels Lowest delivered cost to customer Balanced by Region and Product Group * As of Dec. 31, 2008. Includes consolidated joint ventures.

Case Study QAD Implementation Multiple ERP solutions, including Ford legacy system Ø Reduce TCO, promote global financial reporting (product line, region, customer, etc. ) Ø Hundreds of integration points (regional, enterprise & legacy apps) Ø Heavily customized financials >>The largest QAD implementation in 2007 and 2008<< Ø IT Challenges Need a robust integration infrastructure Ø Need a global master data replication strategy to meet complex business requirements Ø Customizations that need to be scalable Ø

Case Study QXtend As Interface Architecture Ø QXtend Inbound interfaces with master data and transactional screens Ø QXtend Outbound allows the event based or on demand data transmission to external systems Ø One of the first clients of QXE 1. 4, a re-architected release with WSDL support, enhancements in QXO, and improved QDoc structure

Case Study QXtend Inbound vs. CIM Ø CIM Was Used Very Often In Integration Solutions, But… q q q q Ø Sequence sensitive Easy to break Only works with character interface Difficult response tracking / exception handling Difficult to work across servers / databases / domains Maintenance programs with UI triggers (wrappers, ICT, Tailor. Pro) will fail End of life approach QXtend Is The Answer To The Problems With CIM

Case Study Service Oriented Architecture (SOA) Ø SOA is a business operations strategy for leveraging information to meet the enterprise’s objectives and deliver business capacity Ø SOA provides a set of principles of governing concepts used during phases of system development and integration Ø With loose coupling of services, SOA fulfils intra and inter-enterprise services reuse and process interoperability Ø SOA will automate business functions and deliver solutions cheaper, better and faster

Case Study QXtend Inbound Ø Ø Ø Ø Ø Supports versions e. B through QAD 2009 Receive QDocs via Web service and processed by a pool of sessions (multi threaded) Supports both standard and custom QDocs Security checking QAD Enterprise Applications authentication XML message validation E-mail alerts Minimize custom programming for interfaces Pre/post-processing available for added functionality

Case Study QXtend Inbound (QXI) Enterprise Interfaces QXtend Outbound QAD Custom Programs QDoc SOAP (XML) Over HTTP QXtend Inbound QAD App

Case Study QXtend Outbound Ø Ø Ø Ø Provides outbound QAD integration Event-based publish subscribe model Direct Data Publishing model (DDP) Publishes QDocs or other XML documents Delivers to subscriber via web-service or file Real time or batched Built-in email alerts

Case Study Bank Interfaces QAD MES BOM Shipping Info For Customs (2 TS) (SRM) Spend Management QAD. Net UI Or Batch Initiates Messaging (Event Or DDP)

Case Study Shared Service Model Source Application MFG/PRO #1 MFG/PRO #2 QXO UI QDocs Adapter Subscriber MFG/PRO #1 (via QXI) QXO Server MFG/PRO #2 (via QXI) MFG/PRO #3 Adapter JCAPS (EAI)

Case Study

Case Study Solutions Developed With QXtend Interfaces q Sun JCAPS as the messaging middleware (EAI) q Inbound interfaces: MES, exchange rate, PLM, AP q Outbound interfaces: MES, AR, AP, GL, NAFTA custom Ø Global Master Data Replications q QXtend Outbound publishes master data event q QXtend Inbound receives master data Ø Use Of QXtend Inbound In Customizations q Created QXtend API for developers q Easy to use / understand q Cross domain / database transactions become transparent Ø

Case Study Interfaces Ø Challenges WSI compliance (WSDL, XML schema, etc. ) q Working with a team not familiar with QAD q Exception handling q Ø Inbound Interfaces Built With JCAPS/QXtend Solution MES: backflush, shipment q PLM (GBC): item master, product structure (BOM), supplier item q Exchange rate and account payable (check cancellation) q Ø Outbound Interfaces Built With JCAPS/QXtend Solution q q q MES: BOM, Kanban, customer item xref AP: Positive. Pay, vendor report card, Spend Management, EAM PO, checks AR: ARCollect, invoice history GL: People. Soft, Hyperion, payroll Chart of account replication to JCAPS

Case Study

Case Study

User Case Study: QXtend Implementation At Visteon – Session II John Pearson, Visteon Corporation Gary Yang, RCM Technologies

Case Study Global Master Data Replications Ø Business Requirements & Challenges q q q The Master Data Management (MDM) Solution Single master repository On demand, near real time data replication Capability to target multiple database and or multiple domains – on the same or different servers Capability to replicate values globally (all database / domains) or to targeted databases and domains Capability to configure replication pattern by field Always send • Receive at target one time only • Never send • Ability to report “what” has been sent and “what” has been received by target q Potential use of replication to load new environments versus CIM loads q No physical constraints on volume of data q

Case Study Global Master Data Replications Ø Solution With QXtend Inbound / Outbound q q q q User creates/modifies record in master data domain DB schema triggers used to record an event in QXtend extracts the raw data from QAD Enterprise Applications as an asynchronous from user’s session - Minimized performance impact A QDoc is generated and sent to QXO subscribers (via Web service to QXtend Inbound) Real-time publication of QDocs E-mail alerts, archive and delete Replicate reports allows the business to review, clean up or even retry replication failures

Case Study Global Master Data Replications Ø How To Handle Locally Controlled Fields Using of QXO Delta Profile q Problem With Using QXO To Control The Fields That Are Locally Controlled • QXO Has no knowledge of the data in target domain/database q Using QXtend Inbound Pre-Processor • Can intercept QDoc before it is processed • Easy to deploy business logic which depends on the target system data q

Case Study Global Master Data Replications Ø The Keys To Success q q q q One source of the truth – globally Global and filtered targeting Selectable fields Ease and speed of use Scalable Configurable Business should be empowered with good tools to monitor the replications

Case Study

Case Study

Case Study Use Of QXtend In Customizations When There Is A Need To Send Data To QAD Maintenance Screens…… Traditional Approach: CIM q q q q Sequence sensitive Easy to break Only works with CHUI Difficult response tracking / exception handling Difficult to work across servers / databases / domains Maintenance programs with UI triggers (wrappers, ICT, Tailor. Pro) will fail End of life approach

Case Study Use Of QXtend In Customizations When The Visteon Project Begins…… We Developed the QXtend Inbound Progress API q q q q q QXtend Inbound API is an ABL (4 GL) solution Based on Web. Service model of QXtend More flexible than CIM Domain / database / server becomes transparent Easy to learn temp-table application interface for request / response Works with UI triggers Complete exception handling with response QDoc Lower upgrade barrier Ready for new QAD architecture (component based development)

Case Study

Case Study

Case Study Enhancements To QXtend Ø Ø Ø Ø AIX kernel parameter tuning gave 10 -fold improvement on QXI performance Data replication management report QXtend Inbound log report QXtend Outbound BO/Profile migration tool QXtend Outbound session monitor script QXtend Inbound Connection Pool monitor script Extensive use of QXI pre-processors A lot of patches

Case Study

Case Study QXtend Solutions Ø Ø Ø Dramatic reduction in errors and duplicate data entries 20 Event based QXtend Outbound interfaces 10 Direct Data Publishing QXtend Outbound interfaces 10+ Data objects for Master Data Replication Over 50 programs currently use QXtend Inbound API Business Benefits: “A Platform for Global Deployment” Users can manage master data in a complex environment with minimal IT intervention Ø Integrations are simpler to create, modify and support now that the infrastructure exists Ø Customizations affecting multiple domains and regions are simpler to develop and support Ø

Case Study Possible Future Enhancements Ø Ø Ø Ø Expand QXtend interfaces to legacy QAD systems (e. B, e. B 2) Use of QXtend Query Framework in interfaces (pre-validation) Use of QXtend in plant launches / data conversation More data replication objects Configurable QXO DB delete / archive utility Build QXtend Query Framework ABL API Build asynchronous QXtend Inbound ABL API Use of Service Interface (SI) API

QXtend Questions? Contact John Pearson At jpearso 2@visteon. com or Gary Yang At gary_yang@yahoo. com / Linked. In