WordPress Websites for Engineers: Elevate Your Brand
Natasja Paulssen S A P M D M And E S O A At Philips
1. MDM an enabler for eSOA
This Presentation Courtesy of the
International SOA Symposium
October 7-8, 2008 Amsterdam Arena
www.soasymposium.com
info@soasymposium.com
Founding Sponsors
Platinum Sponsors
Gold Sponsors Silver Sponsors
Data is an Asset!
Systems are temporary, but ...
data lasts forever
Freeing the flow of information!
MDM a prerequisite for eSOA
MDM an enabler
Philips IT Applications
Center of Expertise MDM
Mr. John AG Wenmakers
October 2008
Philips International BV, Philips IT
Applications, Mr. John AG Wenmakers 2008 1
2. MDM an enabler for eSOA
Who is talking to you?
• John Wenmakers
• Representing Philips IT Applications
– Philips Corporate IT Shared Service Center focusing on Business
Applications, mainly SAP
– ± 1500 SAP consultants (all flavors)
• 21 years in Philips IT in various roles of which 11 years in SAP, amongst
others team leader of SAP Basis, S&A and Development for 5,5 years
• Project Manager of a MDM project in the Content Management arena
(MDM Product Content Broker)
• Global team leader of the Center of Expertise MDM, since end of 2006
involved in SAP MDM
• Since very recent: Program Manager Business Line
Consumer Lifestyle
Philips International BV, John Wenmakers, October 2008 3
MDM a prerequisite for eSOA
• MDM SPOT Solution Design
• MDM SPOT Key-figures
• eSOA and the Product Control Room
• WHY MDM is needed in eSOA
• Lessons learned on MDM
• Q&A
Philips International BV, John Wenmakers, October 2008 4
Philips International BV, Philips IT
Applications, Mr. John AG Wenmakers 2008 2
3. MDM an enabler for eSOA
COCOON
COCOON XI
XI MDM PORTAL CCR
SPOT Solution Design (logical components)
MDM refers to
published XML
Files of COCOON XML import file
mapping/validation XML Export file
syndication
EAI
Application
Integration MDM refers to
Assets in DAM
SPOT Content Broker CCR
Import Mgr. MDM
Syndicator
XML File XML File
XML Rich COCOON:
Assets Assets Catalog driven
XML pipe line
processing tool
(incl. (rich
SAP XI Routing content and
translations)
EDI / XML XML Pipe-line
Transformation Processing Engine XML File
Engine
XML File XML File
Philips International BV, John Wenmakers, October 2008 5
Solution Design
read-only
SOAP
HTTP
Processing
…
…
COCOON: batch XML pipeline processing
• No direct access to COCOON from outside
• File (XML (XSLT 2.0))
XI Services Cocoon • Used for HTTP retrieval of mainly pictures
SAP XI for Application integration: interaction via
CMC2.0 Processing • SOAP = web services
• File (XML (XSLT 1.0))
Cocoon
Repository
• Oracle RDBMS of MDM: MDM SPOT Products
MDM • File system: Published XML assets of COCOON
XML • Oracle RDBMS of CCR (DAM): non-XML assets
Assets
Physical routing/transport
CMC2.0 Repository
• SAP XI File Adapter
Non-XML assets - CCR
Philips International BV, John Wenmakers, October 2008 6
Philips International BV, Philips IT
Applications, Mr. John AG Wenmakers 2008 3
4. MDM an enabler for eSOA
MDM SPOT Key figures
• MDM runs in a TWIN Center architecture, on a HACMP IBM AIX – ORACLE platform
• MDM runs in 2 LPAR’s with each 2-4 CPU’s, 16GB internal memory and 200GB Disc storage
• MDM has a 4 layer system landscape (SBX, DEV, QA and PRD)
• # of products in MDM SPOT is about 150.000, of which:
– 8000 Pending, reason no Master data available yet
– 7500 Marked as Deleted
– 48.000 of DAP, 73.000 of CE, 122 of Lighting, rest unknown
• # of links to Assets in MDM SPOT
– Asset types : 5000
– Asset links : 3.000.000
– Milestone links : 500.000
– Catalog links : 350.000
• Products repository size is approx 3.2 GB
• # of syndicated records per syndication run
– Weekly 4000 Commercial Type Numbers
– Daily 500.000 Assets to COCOON
– Weekly full load of Assets to COCOON: 3.500.000
• Biggest import XML file is 50Mb (catalogs), bigger files are chunked into 2Mb
• Biggest syndication XML file is 850Mb
• Throughput time of this biggest syndication file (850Mb) is 30 minutes
• CCR occupies 6TB disc storage and carries ±10.000.000 of pictures
• # of inbound interfaces: 16
• # of outbound interfaces: 10
Philips International BV, John Wenmakers, October 2008 7
eSOA and PCR
Philips International BV, John Wenmakers, October 2008 8
Philips International BV, Philips IT
Applications, Mr. John AG Wenmakers 2008 4
5. MDM an enabler for eSOA
eSOA and the Product Control Room
Imagine all product related information to be easily accessible via a common
user interface: “a single sign-on entry to everything you need in your work –
whether related to business, functions or communications on your company,
your organization and country.”
Imagine the Product Control Room
► It leverages the One Philips Portal framework
► It is role-based
► It can be personalized
► It contains trusted consistent data and it turns product data into valuable
information by providing context
► It has a consistent look-and-feel
► It is Enterprise wide accessible
► It is functionally easily scalable through adding modules
► It is powered by CMC2.0
Philips International BV, John Wenmakers, October 2008 9
eSOA and PCR
Philips International BV, John Wenmakers, October 2008 10
Philips International BV, Philips IT
Applications, Mr. John AG Wenmakers 2008 5
6. MDM an enabler for eSOA
iView Product Control Room
Data Aggregation level/user group
DWH
SPOT
“X”
Philips International BV, John Wenmakers, October 2008 11
11
Product Control Room
Philips International BV, John Wenmakers, October 2008 12
Philips International BV, Philips IT
Applications, Mr. John AG Wenmakers 2008 6
7. MDM an enabler for eSOA
COCOON XI MDM PORTAL CCR
Solution Design (logical components)
User interaction
Philips Enterprise Portal
Content entry Product Control Room ..
ESR WS Gateway
SPOT Content Broker
Import Mgr. MDM
Syndicator
XML File XML File
XML Rich
Assets Assets
SAP XI APACHE COCOON XML
EDI / XML Pipe-line Processing XML File
Engine
Transformation
XML File Engine XML File
Philips International BV, John Wenmakers, October 2008 13
WHY MDM is needed in eSOA
• To have a single trusted information source within
your enterprise
• To prevent eSOA projects to crash, eSOA can make
it even worse...
• ....in other words for proper eSOA you need to have trusted „Information
as a service“ available based on a information virtualization layer across
the enterprise
Philips International BV, John Wenmakers, October 2008 14
Philips International BV, Philips IT
Applications, Mr. John AG Wenmakers 2008 7
8. MDM an enabler for eSOA
Lessons learned on MDM
• MDM is immature and a niche market space
► Robustness expected in 2011
► MDM resources are scarce
► Bleeding edge technology
• Need for complementary Tools / Services
• Think BIG, start small....may be start with vendors (spent analysis)
• 20% IT, 80% Business aspects
► Data governance model
► Data ownership/stewardship
• THE issue is Data Quality improvement
• Business processes are vital for MDM
• Define your ambition level (DC / DH / CDM)
• Launch MDM projects via the business, not IT!
• Define Business cases, also for MDM projects
• Company cultural change involved
Philips International BV, John Wenmakers, October 2008 15
Questions & Answers
Philips International BV, John Wenmakers, October 2008 16
Philips International BV, Philips IT
Applications, Mr. John AG Wenmakers 2008 8