Transcript Slide 1

Infor Open SOA Overview for OAGi
Pat O’Connor
BOD Father
Infor Confidential
Copyright © 2001-2007 Infor Global Solutions
Who is Infor
2
Copyright © 2001-2007 Infor Global Solutions
Who is Infor
Brain
Syteline
SoftBrands
Geac
Provia COM
DMAS LN
Mercia Hansen
SCT Adage Visual
BPCS
SupplyWeb
Lilly
JBA
daly.commerce
FACTS
Infor
Ironside Technologies
WM 9
Infinium (fka Software2000)
IncoDev Extensity
SystemsUnion Group (Sun Systems)
E-piphany
Varial
Aperum
Baan
CAPS Logistics
PRMS
LX
3
EXE TakeStock
Datastream
Copyright © 2001-2007 Infor Global Solutions
Frontstep Planning
Mapics
Workbrain
NxTrend
Current Architecture
Many application
development companies
built monolithic solutions.
Monolithic
ERP
4
Copyright © 2001-2007 Infor Global Solutions
Current Architecture
Infor VISUAL
Quality
Infor VISUAL
Manufacturing
Infor VISUAL
CRM
Infor VISUAL
DCMS
5
Copyright © 2001-2007 Infor Global Solutions
Integration points are often
application specific.
Written only for the unique
combination of
applications.
Components are then interchangeable
Components
communicate through a
standard interface
Infor BUS
Infor VISUAL
Manufacturing
Infor VISUAL
Quality
Infor VISUAL
CRM
Infor VISUAL
DCMS
6
Copyright © 2001-2007 Infor Global Solutions
Components are then interchangeable
Customers can select the
suite of products that
match their requirements
without affecting core
applications
Infor BUS
Infor VISUAL
Manufacturing
Infor VISUAL
Quality
Infor SyteLine
CRM
Infor VISUAL
DCMS
7
Copyright © 2001-2007 Infor Global Solutions
Adding, Replacing or Upgrading Features
EAM
Costing
SupplyWeb
Transportation
Web Store
9
Copyright © 2001-2007 Infor Global Solutions
Infor Bus
Existing
ERP
Legacy
Financials
Sales and
Service
WMS
HCM
New Financials
Process example – Financials Center of Excellence
Any combination of
processes can be
implemented. Purchase
only what you need!
Chart of
Accounts
Financial
Reporting
Budgeting
Apportionment
The Bus
Treasury
Accounts
Receivable
Invoicing
10
Copyright © 2001-2007 Infor Global Solutions
Tax
Maintenance
Journal
Processing
Cash
Forecasting
Accounts
Payable
Cash
Management
Updates
Because of the standard
interface, processes can
be updated individually
thus avoiding a “big
bang” when upgrading
Chart of
Accounts
Financial
Reporting
Budgeting
Version 2.0
Apportionment
The Bus
Treasury
Accounts
Receivable
Invoicing
11
Copyright © 2001-2007 Infor Global Solutions
Tax
Maintenance
Journal
Processing
Cash
Forecasting
Accounts
Payable
Cash
Management
Reporting Services SOA-based Architecture
Personalized Content
Integrated User Experience
Microsoft
Office®
Web Client
ERP LN
DEMAND
DEMAND
RECENT ITEMS
Item XYZ (Purchase
Requirement)
SUPPLY
RESOURCES
!
5
Overdue job orders
Machine 87 down
3
3
Machine 46
overloaded
3
Role-based
Home Pages
10
8
Actual
6
TASKS
4
Exception messages
Job order dispatch list
Demand forecast
workbench
Pegging workbench
Resource allocation
Planned inventory
movements
Role-based
Analytic
Applications
Planned vs. Actual Productiont
(Clustered Column)
14
12
Units
FAVORITES
Open: 91
In Process: 396
Supply orders for release
Purchase 91
request:
2
0
Jan
Feb
Mar
UNPLANNED SCRAP BY REASON
Apr
May
Jun
Jul
% RESOURCE UTILIZATION
May 14, 2007 / 2:07 pm
Job Orders: 396
Distribution:
7
Unplanned Scrap
% ON TIME COMPLETIONS
REPORTS
Open orders
!
Excel
Exception messages
Late work orders
Broken
Lost
Wrong spec.
Infor
Solution
A
Database
Category 4
Infor
Solution
B
Database
Page-based (BIRT)
Query & Analysis
3rd Party
Other
Solution
Business Logic
BPA
OLAP
BSA
Administration
Reporting Services Engine
Database
OAGIS BODS
Reporting
Database
Infor ESB
12
Analytic Reporting
INVENTORY
May 14, 2007 / 2:07 pm
Alerts
Reports
Search
PRODUCTION TO PLAN
ALERTS
Late purchase receipts
Bicycles (Planned Job Order)
A2 Tiles (Item)
Metrics
Reporting and Analytics
Rich Client
Adapter
HOME
Welcome Bob l Sign Out
Scorecards
Copyright © 2001-2007 Infor Global Solutions
MDM
Export Services
Security
Import Services
MyDay
13
Copyright © 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
14
Copyright © 2001-2007 Infor Global Solutions
Traditional way doing MDM #1
DB Synchronization
Enters customer
Customer
Hub
CRM
ERP
customer
customer
DB Synch
“super
definition”
15
Copyright © 2001-2007 Infor Global Solutions
New?
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
Traditional way doing MDM #2
Hub & Spoke
Enters customer
Customer
Hub
EAI
Transaction
CRM
customer
16
“super
definition”
EAI
Transaction
New?
ERP
customer
Copyright © 2001-2007 Infor Global Solutions
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
Event Driven – Services Oriented Architecture
Infor
Infor
MDM
Open
strategy
SOA
Component A
Component B
OAGIS
Infor BUS
17
Copyright © 2001-2007 Infor Global Solutions
Infor Master Data Management
Customer MDM
Enters
customer
OAGIS
Infor ESB
CRM
18
Copyright © 2001-2007 Infor Global Solutions
ERP
OAGi
19
Copyright © 2001-2007 Infor Global Solutions
The mathematics of scaling up
Application 1
Application 2
Application 3
Application 4
12 Connections
20
Copyright © 2001-2007 Infor Global Solutions
The mathematics of scaling up
The number of possible connections among any number of
items is n(n-1) for two way connections.
Number of
components
to integrate
21
Apply traditional
formula
Cost of traditional
integration @ 0.1 FTE
n=5
5(4)
=
20
2 FTEs
n = 10
10(9)
=
90
9 FTEs
n = 15
15(14) = 210
21 FTEs
n = 20
20(19) = 380
38 FTEs
Copyright © 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
22
Best practices
formula
Cost of best practices
integration @ 0.1 FTE
n=5
5 * 2.0 = 10
1 FTE
n = 10
10 * 2.0 = 20
2 FTEs
n = 15
15 * 2.0 = 30
3 FTEs
n = 20
20 * 2.0 = 40
4 FTEs
Copyright © 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
23
Copyright © 2001-2007 Infor Global Solutions
Tooling
 JMS
 JiBX
 EclipseLink
 CSI
 DEM/DCA
 Noun MetaData
25
Copyright © 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.


26
Capability to resubmit Audited messages
Copyright © 2001-2007 Infor Global Solutions
DEM/DCA
Define the environment
Servers
Resources
Containers
Components
Define the routes
Monitor the events
Missing events
27
Copyright © 2001-2007 Infor Global Solutions
Noun MetaData
28
Copyright © 2001-2007 Infor Global Solutions
Noun MetaData
29
Copyright © 2001-2007 Infor Global Solutions
Noun MetaData
30
Copyright © 2001-2007 Infor Global Solutions