Interoperability With MFG/PRO: Seamless Connectivity
17
Interoperability with MfgPro Seamless connectivity and automation Presented By: Hector Torres / Steve Lamb
Transcript of Interoperability With MFG/PRO: Seamless Connectivity
Interoperability with MfgProSeamless 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 TorresMore 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, IncCompany 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.
120 MfgPro eB2 SP1 Instances sharing one code base
Over 1400 MfgPro users
Around 70 in-house-developed interfaces handling 3-5 Million messages per day
Integration team manages and monitors more than 800 queues created to support MfgPro interfaces
Close to 85% of Production Issues reported today are related to MfgPro interfaces
81.9% of the MfgPro development completed on ‘07 was Interface-related
Johnson Controls, IncMfgPro Installation – Automotive Group NA
68.4%
100.0%
73.6% 73.9%
93.6%
0.0%
10.0%
20.0%
30.0%
40.0%
50.0%
60.0%
70.0%
80.0%
90.0%
100.0%
Rel 2.28a Rel 2.29 Rel 3.01 Rel 3.02 Rel 3.03
Interface-related dev
Interface Architecture Diagram
Problem Definition
Problem StatementMfgPro integration layer is deficient, limited, and unreliable, which represents a challenge meeting customer demands.
Solution RequirementsProvide 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 AdaptersArchitecture Diagram
EIEIBusiness Logic
RAW Repository
Inbound APIOutbound
API
BO Engine
Solutions considered
Microsoft BizTalkProgress Sonic MQ
Upgrade Custom Adapters
QXtend 1.4
JBoss
MfgPro Architecture at JCI NA (TO-BE)
Shipment ReconciliationExample 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 AnalysisCurrent versus Projected Time spent on tasks
0%
10%
20%
30%
40%
50%
60%
70%
80%
90%
100%
Current %
Projected %
Current % 10% 20% 70%
Projected % 3% 11% 25%
Message developmentMessage
EnhancementsMessage support and
troubleshooting
