Interoperability With MFG/PRO: Seamless Connectivity


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Chronological order of events - Started in JCI as a developer assigned to the BO engine project - Participated in the design of the inbound adapter
  • + Started as a Consultant in the South CA area + Exposed to multiple mfgpro/progress flavors
  • Automobile Experience Interior systems including seating, overhead systems, doors, instrument panel, storage, electronics. Power Solutions Automotive batteries Building Efficiency Control systems for heating, ventilation, air-conditioning, lighting, security, and fire management.
  • Although the MfgPro outbound flow is represented with only one line, it represents various interfaces that we use today to send write messages into MQ Series. Some of this interfaces are triggered by MfgPro events, others are automated extracts, and others use a BO approach where a message includes specific business transactions.
  • Integration layer is deficient if you don’t pay attention to the 85% prod tickets we have open. 
  • This was the third time we contemplated Qxtend. We looked at other alternatives such as BizTalk, SonicMQ, and continuing supporting in-house interfaces.
  • Integration with MQSeries is limited. Only WebServices and File-dropping
  • Progress-based applications (EDIMAT)
  • This picture represents one instance of MfgPro which equals to one BU Entity.
  • Interoperability With MFG/PRO: Seamless Connectivity

    1. 1. Interoperability with MfgPro Seamless connectivity and automation Presented By: Hector Torres / Steve Lamb
    2. 2. Agenda <ul><ul><li>Bio </li></ul></ul><ul><ul><li>Johnson Controls, Inc </li></ul></ul><ul><ul><li>Interface Architecture Diagram </li></ul></ul><ul><ul><li>Problem Definition </li></ul></ul><ul><ul><li>Solution Expectations </li></ul></ul><ul><ul><li>MfgPro Integration Architecture </li></ul></ul><ul><ul><ul><li>As-is </li></ul></ul></ul><ul><ul><ul><li>To-be </li></ul></ul></ul><ul><ul><li>Cost Justification Analysis </li></ul></ul><ul><ul><li>Qxtend considerations </li></ul></ul><ul><li>Questions? </li></ul>
    3. 3. Bio <ul><li>Héctor Torres </li></ul><ul><ul><ul><li>More than ten years experience in Progress and MfgPro </li></ul></ul></ul><ul><ul><ul><li>MfgPro Technical Consultant </li></ul></ul></ul><ul><ul><ul><ul><li>MfgPro Implementation and Support </li></ul></ul></ul></ul><ul><ul><ul><ul><li>MfgPro development </li></ul></ul></ul></ul><ul><ul><ul><li>Solution Architect </li></ul></ul></ul><ul><ul><ul><ul><li>MfgPro Development </li></ul></ul></ul></ul><ul><ul><ul><ul><li>MfgPro Integration </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Project Management </li></ul></ul></ul></ul>
    4. 4. Johnson Controls, Inc Company Profile <ul><li>Founded in 1885 </li></ul><ul><li>More than 1,300 locations worldwide </li></ul><ul><li>Milwaukee, WI </li></ul><ul><li>Three divisions: </li></ul><ul><ul><ul><li>Automobile Experience </li></ul></ul></ul><ul><ul><ul><li>Power Solutions </li></ul></ul></ul><ul><ul><ul><li>Building Efficiency </li></ul></ul></ul><ul><ul><li>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. </li></ul></ul>
    5. 5. <ul><li>120 MfgPro eB2 SP1 Instances sharing one code base </li></ul><ul><li>Over 1400 MfgPro users </li></ul><ul><li>Around 70 in-house-developed interfaces handling 3-5 Million messages per day </li></ul><ul><li>Integration team manages and monitors more than 800 queues created to support MfgPro interfaces </li></ul><ul><li>Close to 85% of Production Issues reported today are related to MfgPro interfaces </li></ul><ul><li>81.9% of the MfgPro development completed on ‘07 was Interface-related </li></ul>Johnson Controls, Inc MfgPro Installation – Automotive Group NA
    6. 6. Interface Architecture Diagram
    7. 7. Problem Definition <ul><li>Problem Statement </li></ul><ul><li>MfgPro integration layer is deficient, limited, and unreliable, which represents a challenge meeting customer demands. </li></ul><ul><li>Solution Requirements </li></ul><ul><li>Provide global solution that brings stability, flexibility and scalability to MfgPro’s Integration layer </li></ul><ul><li>Reduction of up to 70% on production support time spent with Integration-related issues </li></ul><ul><li>Streamline development by using “What You See Is What You Get” (WYSIWYG) tools </li></ul><ul><li>Reduce troubleshooting time and increase proactiveness by using monitoring tools and dashboard indicators </li></ul>
    8. 8. Solution Expectations <ul><li>Standardization of MfgPro’s integration layer </li></ul><ul><ul><ul><li>Facilitates code development  Efficiency </li></ul></ul></ul><ul><ul><ul><li>Enables MfgPro team to provide solutions for most integration needs  Scaling Transparency </li></ul></ul></ul><ul><ul><ul><li>Provides a common roadmap in-line with QAD’s platform direction  Scalability </li></ul></ul></ul><ul><ul><ul><li>Non-intrusive Integration with MfgPro  Flexibility </li></ul></ul></ul><ul><li>Leverage Progress OE language features </li></ul><ul><ul><ul><li>Improved product scalability and performance </li></ul></ul></ul><ul><li>Supportable Service Interface </li></ul><ul><ul><ul><li>Access to native APIs </li></ul></ul></ul><ul><ul><ul><li>Reduced dependency on UI changes </li></ul></ul></ul><ul><li>Benefits to middleware </li></ul><ul><ul><ul><li>Reduction in messaging traffic by eliminating unnecessary data elements and message duplicity </li></ul></ul></ul><ul><ul><ul><li>Less failure points </li></ul></ul></ul><ul><ul><ul><li>Reduction in support by decreasing number of MQ Queues from 800 to less than a dozen </li></ul></ul></ul>
    9. 9. Solution Expectations (cont…) <ul><ul><li>Reduction on development time by using APIs and QDocs out of the box </li></ul></ul><ul><ul><li>Flexible architecture that supports all MfgPro versions at JCI (including other Progress-based applications) </li></ul></ul><ul><li>Must support Integration with JCI’s Enterprise Service Bus (IBM Websphere) </li></ul><ul><li>Scalable solution since it conforms to the SOA (Service Oriented Architecture) model </li></ul><ul><ul><ul><li>Loosely coupled services (flexible business processes) </li></ul></ul></ul><ul><ul><ul><li>Easier Integration </li></ul></ul></ul><ul><ul><ul><li>Reusable components </li></ul></ul></ul>
    10. 10. MfgPro Architecture at JCI NA (AS-IS)
    11. 11. Custom Adapters Architecture Diagram
    12. 12. Solutions considered <ul><li>Microsoft BizTalk </li></ul>Progress Sonic MQ Upgrade Custom Adapters QXtend 1.4 JBoss
    13. 13. MfgPro Architecture at JCI NA (TO-BE)
    14. 14. Shipment Reconciliation Example Application
    15. 15. Qxtend Considerations <ul><li>Additional Hardware is required for QXtend </li></ul><ul><ul><ul><li>N-Tier configuration is recommended to minimize impact to MfgPro messaging </li></ul></ul></ul><ul><ul><ul><li>Windows and Unix supported </li></ul></ul></ul><ul><li>A complete plan needs to be developed to migrate existing interfaces </li></ul><ul><ul><ul><li>Estimated Interface migration plan: 13 months </li></ul></ul></ul><ul><li>Qxtend will support various MfgPro versions across three different regions (NA, EU, and AP) </li></ul>
    16. 16. Cost Justification Analysis Current versus Projected Time spent on tasks
    17. 17. Questions? Hector Torres [email_address] Steve Lamb [email_address]