User Case Study: QXtend Implementation At Visteon

1

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

2
Introduction
3
Introduction
4
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

5
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

6
Customers Are Key
7
Global Manufacturing Capabilities

• 74 global facilities
• Asia Pacific 21
• Europe 28
• North America 19
• South America 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.
8
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
• gtgtThe largest QAD implementation in 2007 and
  2008ltlt
• 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

9
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

10
Case Study

• QXtend Inbound vs. CIM
• CIM Was Used Very Often In Integration Solutions,
  But
• 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, TailorPro) will fail
• End of life approach
• QXtend Is The Answer To The Problems With CIM

11
Case Study

• Service Oriented Architecture (SOA)
• SOA is a business operations strategy for
  leveraging information to meet the enterprises
  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

12
Case Study

• QXtend Inbound
• Supports versions eB 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

13
Case Study
QXtend Inbound (QXI)
Enterprise Interfaces
QAD App
QXtend Inbound
QXtend Outbound
QDoc
QAD App
QAD App
SOAP (XML) Over HTTP
QAD Custom Programs
14
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

15
Case Study
Bank Interfaces
QAD
MES BOM
Shipping Info For Customs (2TS)
(SRM) Spend Management
QAD .Net UI Or Batch Initiates Messaging (Event
Or DDP)
16
Case Study
Shared Service Model
QXO UI
Subscriber
Source Application
QDocs
MFG/PRO 1
QXO Server
MFG/PRO 1 (via QXI)
Adapter
MFG/PRO 2 (via QXI)
MFG/PRO 2
Adapter
MFG/PRO 3 (via QXI)
MFG/PRO 3
Adapter
JCAPS (EAI)
17
Case Study

18
Case Study

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

19
Case Study

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

20
Case Study

21
Case Study

22

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

23
Case Study

• Global Master Data Replications
• Business Requirements Challenges
• 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
• Potential use of replication to load new
  environments versus CIM loads
• No physical constraints on volume of data

24
Case Study

• Global Master Data Replications
• Solution With QXtend Inbound / Outbound
• User creates/modifies record in master data
  domain
• DB schema triggers used to record an event in
  QXtend
• QXtend extracts the raw data from QAD Enterprise
  Applications as an asynchronous from users
  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

25
Case Study

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

26
Case Study

• Global Master Data Replications
• The Keys To Success
• 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

27
Case Study
28
Case Study
29
Case Study

• Use Of QXtend In Customizations
• When There Is A Need To Send Data To QAD
  Maintenance Screens
• Traditional Approach CIM
• 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, TailorPro) will fail
• End of life approach

30
Case Study

• Use Of QXtend In Customizations
• When The Visteon Project Begins
• We Developed the QXtend Inbound Progress API
• QXtend Inbound API is an ABL (4GL) solution
• Based on WebService 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)

31
Case Study
32
Case Study
33
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

34
Case Study
35
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

36
Case Study

• Possible Future Enhancements
• Expand QXtend interfaces to legacy QAD systems
  (eB, eB2)
• 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

37
QXtend

• Questions?
• Contact John Pearson At jpearso2_at_visteon.com or
• Gary Yang At gary_yang_at_yahoo.com / LinkedIn