Solution Architecture

							   Interoperability with MfgPro
   Seamless connectivity and automation




Presented By: Hector Torres / Steve Lamb
Agenda


 Bio

 Johnson Controls, Inc

 Interface Architecture Diagram

 Problem Definition

 Solution Expectations

 MfgPro Integration Architecture
    As-is

    To-be

 Cost Justification Analysis

 Qxtend considerations

 Questions?
Bio



 Héctor      Torres
   More than ten years experience in Progress and MfgPro
   MfgPro Technical Consultant
       MfgPro Implementation and Support
       MfgPro development

   Solution Architect
       MfgPro Development
       MfgPro Integration
       Project Management
Johnson Controls, Inc
Company Profile

 Founded in 1885
 More than 1,300 locations worldwide
 Milwaukee, WI
 Three divisions:
   Automobile Experience
   Power Solutions
   Building Efficiency


 Fiscal 2007 was the 61st consecutive year of sales increases, the 17th consecutive year
  of earnings increases and the 32nd successive year of dividend increases. Dividends
  have been paid consecutively since 1887.
Johnson Controls, Inc
MfgPro Installation – Automotive Group NA

                                                                    Interface-related dev

 120 MfgPro eB2 SP1 Instances sharing one code base
              100.0%


                            100.0%
               90.0%
                                                                                93.6%

 Over 1400 MfgPro users
               80.0%


               70.0%

 Around 70 in-house-developed interfaces handling 3-5 Million
                                        73.6%            73.9%
                    68.4%
               60.0%

messages per day
               50.0%



 Integration team manages and monitors more than 800 queues
               40.0%




created to support MfgPro interfaces
               30.0%


               20.0%


 Close to 85% of Production Issues reported today are related to
               10.0%


MfgPro interfaces
                0.0%
                       Rel 2.28a   Rel 2.29   Rel 3.01   Rel 3.02               Rel 3.03



 81.9% of the MfgPro development completed on ‘07 was Interface-
related
Interface Architecture Diagram
Problem Definition



Problem Statement
MfgPro integration layer is deficient, limited, and unreliable, which represents a challenge
meeting customer demands.

Solution Requirements
Provide global solution that brings stability, flexibility and scalability to MfgPro’s Integration
layer
 Reduction of up to 70% on production support time spent with Integration-related issues
 Streamline development by using “What You See Is What You Get” (WYSIWYG) tools
 Reduce troubleshooting time and increase proactiveness by using monitoring tools and
dashboard indicators
Solution Expectations


 Standardization of MfgPro’s integration layer
   Facilitates code development  Efficiency
   Enables MfgPro team to provide solutions for most integration needs  Scaling Transparency
   Provides a common roadmap in-line with QAD’s platform direction  Scalability
   Non-intrusive Integration with MfgPro  Flexibility

 Leverage Progress OE language features
   Improved product scalability and performance

 Supportable Service Interface
   Access to native APIs
   Reduced dependency on UI changes

 Benefits to middleware
   Reduction in messaging traffic by eliminating unnecessary data elements and message duplicity
   Less failure points
   Reduction in support by decreasing number of MQ Queues from 800 to less than a dozen
Solution Expectations (cont…)



 Reduction on development time by using APIs and QDocs out of the box
 Flexible architecture that supports all MfgPro versions at JCI (including other
  Progress-based applications)
 Must support Integration with JCI’s Enterprise Service Bus (IBM Websphere)
 Scalable solution since it conforms to the SOA (Service Oriented Architecture)
model
   Loosely coupled services (flexible business processes)
   Easier Integration
   Reusable components
MfgPro Architecture at JCI NA (AS-IS)
Custom Adapters
Architecture Diagram




                           Business Logic
         EI                                              EI
                                     Outbound
                       Inbound API
                                       API

                           RAW Repository


                                                 BO
                                                Engine
Solutions considered



    Microsoft BizTalk                         Progress Sonic MQ



                        QXtend 1.4


                                     Upgrade Custom Adapters

                   JBoss
MfgPro Architecture at JCI NA (TO-BE)
Shipment Reconciliation
Example Application
Qxtend Considerations



 Additional Hardware is required for QXtend
   N-Tier configuration is recommended to minimize impact to MfgPro messaging
   Windows and Unix supported

 A complete plan needs to be developed to migrate existing interfaces
   Estimated Interface migration plan: 13 months

 Qxtend will support various MfgPro versions across three different
regions (NA, EU, and AP)
Cost Justification Analysis
Current versus Projected Time spent on tasks



         100%
          90%
          80%
          70%
          60%
                                                                             Current %
          50%
                                                                             Projected %
          40%
          30%
          20%
          10%
           0%
                                          Message      Message support and
                  Message development
                                        Enhancements     troubleshooting
    Current %            10%                20%               70%
    Projected %           3%                11%               25%
 Questions?




Hector Torres           Steve Lamb
hector.torres@jci.com   sfl@qad.com