1. Infor Confidential Template V.24, 1-Mar-2007 Copyright © 2001-2007 Infor Global Solutions Infor Open SOA Overview for OAGi Pat O’Connor BOD Father

2. Template V.24, 1-Mar-2007 2Copyright © 2001-2007 Infor Global Solutions Who is Infor

3. Template V.24, 1-Mar-2007 3Copyright © 2001-2007 Infor Global Solutions Who is Infor Provia Infinium (fka Software2000) Mercia Baan Mapics BPCS EXE E-piphany SystemsUnion Group (Sun Systems) Datastream JBA Lilly Brain Geac CAPS Logistics Frontstep Planning FACTSInfor NxTrend DMAS SCT Adage PRMS TakeStock Varial Ironside Technologies Aperum daly.commerce Hansen SoftBrands Workbrain IncoDev Visual LN LX Extensity Syteline COM WM 9 SupplyWeb

4. Template V.24, 1-Mar-2007 4Copyright © 2001-2007 Infor Global Solutions Current Architecture Monolithic ERP Many application development companies built monolithic solutions.

5. Template V.24, 1-Mar-2007 5Copyright © 2001-2007 Infor Global Solutions Current Architecture Infor VISUAL Manufacturing Infor VISUAL Quality Infor VISUAL CRM Infor VISUAL DCMS Integration points are often application specific. Written only for the unique combination of applications.

6. Template V.24, 1-Mar-2007 6Copyright © 2001-2007 Infor Global Solutions Infor VISUAL Manufacturing Infor VISUAL Quality Infor VISUAL CRM Infor VISUAL DCMS Infor BUS Components communicate through a standard interface Components are then interchangeable

7. Template V.24, 1-Mar-2007 7Copyright © 2001-2007 Infor Global Solutions Infor VISUAL Manufacturing Infor VISUAL Quality Infor VISUAL DCMS Infor BUS Infor SyteLine CRM Customers can select the suite of products that match their requirements without affecting core applications Components are then interchangeable

8. Template V.24, 1-Mar-2007 8Copyright © 2001-2007 Infor Global Solutions Proposed Centers of Excellence Post Sales Service CustomerRelationshipManagementSupplierRelationshipManagement Suppliers Common Services & Architecture Supply Chain Planning Inventory Logistics Manufacturing Execution Systems Project Manufacturing Quality Production and Assembly Product Life Cycle Management Financials Human Resources Enterprise Asset Management Customers Manufacturers and Distributors

9. Template V.24, 1-Mar-2007 9Copyright © 2001-2007 Infor Global Solutions Adding, Replacing or Upgrading Features ExistingERP EAM SupplyWeb Sales and Service WMS HCM LegacyFinancials New Financials Infor Bus Web Store Transportation Costing

10. Template V.24, 1-Mar-2007 10Copyright © 2001-2007 Infor Global Solutions Process example – Financials Center of Excellence Invoicing Accounts Receivable Treasury Budgeting Chart of Accounts Financial Reporting Cash Management Cash Forecasting Journal Processing Apportionment Tax Maintenance Accounts Payable The Bus Any combination of processes can be implemented. Purchase only what you need!

11. Template V.24, 1-Mar-2007 11Copyright © 2001-2007 Infor Global Solutions Updates Invoicing Accounts Receivable Treasury Chart of Accounts Financial Reporting Cash Management Cash Forecasting Journal Processing Apportionment Tax Maintenance Accounts Payable The Bus Because of the standard interface, processes can be updated individually thus avoiding a “big bang” when upgrading Budgeting Version 2.0

12. Template V.24, 1-Mar-2007 12Copyright © 2001-2007 Infor Global Solutions Reporting and Analytics Reporting Services SOA-based Architecture Administration Analytic Reporting Business Logic OLAP BPA BSA Page-based (BIRT) Excel 3rd Party Query & Analysis Infor ESB Export Services Security Reporting Services Engine Import Services MDM Reporting Database Integrated User Experience Database Adapter Infor Solution A Infor Solution B Other Solution OAGIS BODS Personalized Content ScorecardsMetricsReports Web Client Rich Client Microsoft Office® Role-based Home Pages Role-based Analytic Applications

13. Template V.24, 1-Mar-2007 13Copyright © 2001-2007 Infor Global Solutions MyDay

14. Template V.24, 1-Mar-2007 14Copyright © 2001-2007 Infor Global Solutions Infor Messaging  Only one system owns a piece of information.  The primary system is the SOR  If data is replicated in another system it is subordinate  SOA  Document Based  Canonical Data format

15. Template V.24, 1-Mar-2007 15Copyright © 2001-2007 Infor Global Solutions DB Synchronization Traditional way doing MDM #1 1.Requires in depth knowledge of each DB schema and any update / change can have unforeseen results 2.Any local logic (CRM/ERP) needs to be implemented in the sync process 3.High volume data can freeze / lock your DB 4.Very costly implementation when adding new application (new DB scripts to synch) 5.Agreeing on super customer definition takes a long time Customer Hub “super definition” CRMERP New? customer Enters customer DB Synch

16. Template V.24, 1-Mar-2007 16Copyright © 2001-2007 Infor Global Solutions Traditional way doing MDM #2 1.Uses EAI technologies at the Hub, connecting to the remote applications (spokes) 2.Synchronous interaction from Hub to spokes 3.Requires high-end infrastructure 4.Very costly implementation when adding new application (new EAI adapters) 5.Agreeing on super customer definition takes a long time Customer Hub CRMERP Enters customer EAI Transaction New? “super definition” customer Hub & Spoke

17. Template V.24, 1-Mar-2007 17Copyright © 2001-2007 Infor Global Solutions Infor BUS Component BComponent A Event Driven – Services Oriented Architecture OAGIS Infor MDM strategyInfor Open SOA

18. Template V.24, 1-Mar-2007 18Copyright © 2001-2007 Infor Global Solutions Infor Master Data Management Infor ESB Customer MDM Enters customer CRM ERP OAGIS

19. Template V.24, 1-Mar-2007 19Copyright © 2001-2007 Infor Global Solutions OAGi

20. Template V.24, 1-Mar-2007 20Copyright © 2001-2007 Infor Global Solutions Application 1 Application 2 Application 3 Application 4 12 Connections The mathematics of scaling up

21. Template V.24, 1-Mar-2007 21Copyright © 2001-2007 Infor Global Solutions The mathematics of scaling up n = 55(4) = 20 n = 1010(9) = 90 n = 1515(14) = 210 n = 2020(19) = 380 Number of components to integrate Apply traditional formula Cost of traditional integration @ 0.1 FTE 2 FTEs 9 FTEs 21 FTEs 38 FTEs The number of possible connections among any number of items is n(n-1) for two way connections.

22. Template V.24, 1-Mar-2007 22Copyright © 2001-2007 Infor Global Solutions The mathematics of scaling up The number of possible connections among any number is n * 2.0 Number of components to integrate Best practices formula n = 5 5 * 2.0 = 10 n = 10 10 * 2.0 = 20 n = 15 15 * 2.0 = 30 n = 20 20 * 2.0 = 40 1 FTE 2 FTEs 3 FTEs 4 FTEs Cost of best practices integration @ 0.1 FTE

23. Template V.24, 1-Mar-2007 23Copyright © 2001-2007 Infor Global Solutions Where does OAGi fit 1.Canonical model is necessary for reducing the number of connections. 2.Agreeing on super customer definition takes a long time 3.A long time means a lot of money 4.Infor has implemented 113 Nouns 5.Or 113 times a lot of money

24. Template V.24, 1-Mar-2007 24Copyright © 2001-2007 Infor Global Solutions Disaster Recovery Implementation and Disaster Recovery Accept Requests Notify Enterprise Standard Message Flows SOR Sync Process Acknowledge Get Show Sync

25. Template V.24, 1-Mar-2007 25Copyright © 2001-2007 Infor Global Solutions Tooling  JMS  JiBX  EclipseLink  CSI  DEM/DCA  Noun MetaData

26. Template V.24, 1-Mar-2007 26Copyright © 2001-2007 Infor Global Solutions CSI  A common message audit data store to keep copies of all messages (routed through the Infor BUS) for auditing, tracing and error processing purposes.  An error tracking, processing, and escalation process for either Infor ESB or Fortress generated errors.  A notification component to deliver notification events to users or groups through different notification methods.  Capability to resubmit Audited messages

27. Template V.24, 1-Mar-2007 27Copyright © 2001-2007 Infor Global Solutions DEM/DCA  Define the environment  Servers  Resources  Containers  Components  Define the routes  Monitor the events  Missing events

28. Template V.24, 1-Mar-2007 28Copyright © 2001-2007 Infor Global Solutions Noun MetaData

29. Template V.24, 1-Mar-2007 29Copyright © 2001-2007 Infor Global Solutions Noun MetaData

30. Template V.24, 1-Mar-2007 30Copyright © 2001-2007 Infor Global Solutions Noun MetaData