Connecting to the PEPPOL Infrastructure Mikkel Hippe Brun Technical Director, PEPPOL Chief Consultant, Danish IT- and Telecom Agency Email: [email protected]Twitter: @hippebrun Pan European eProcurement with PEPPOL Copenhagen, Denmark October 21th – 23rd 2009
Incentives for connecting to the PEPPOL infrastructure for service providers and large buyers.
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Risk of service provider lock-in / Limited competition
Customers may have to connect to more than one service provider
The four-corner-model
Characteristics (simplified)Agreed upon standards for transport
open or proprietary
Perhaps - agreed upon standards for content
Freedom to choose service provider
Business requirements
Business concern Service provider Large Organization Company
Low cost of entry Other cost of entry
(e.g.complexity, contractual, etc)
Low cost per msg
Technology comfort zone Reliability Integrity Transport-level non-repudiation Privacy Trust Avg. latency lower than 5 min. +
(tender?)High volume
The PEPPOL exchange challenge
?
PEPPOL Infrastructure
SML = Service Metadata Locator (interface)
SMP = Service Metadata Publisher (interface)
AP = Access Point (Operated by a Service Provider)
Our foundation
Content and business process standardsCEN/ISSS WS BIIOASIS UBLUN/CEFACT Cross Industry Invoice
Internet and web services standardsOASISW3CIETF
We provide
SpecificationsCentral infrastructureOpen Source SoftwareReference ImplementationsHands-on workshops and supportLegal framework
Mainstream adoption in 10 years
Vo
lum
e
Maturity
Mainstream adoption
23 mill.
Time
10
ye
ars
5 y
ea
rs
8 y
ea
rs
Mainstream adoption in 5 years
Vo
lum
e
Maturity
Mainstream adoption
23 mill.
Time
10
ye
ars
5 y
ea
rs
4 y
ea
rs
We need concerted action
Suppliers of Business SoftwareERP solutionsMiddleware software
Service ProvidersBanksValue Added Network OperatorseProcurement Platform Providers
Governments and large private buyers
Problems as seen from a software supplier
ERP and Business Software suppliersConvergence between standards is slowNo standardized way of exchangeNo standardized interface to service providersLack of critical mass
Poll
– Q: Do you represent a software supplier?
– Q: Are these assumptions correct?
PEPPOL for Software suppliers
Suppliers of Business Software and ERPAgree to standardized business processesSupport standardized data modelsSupport standardized “connections” to Service Providers
PEPPOL is at your service
Problems as seen from a middleware supplier
Is it a mature specification?Will a new specification get traction?Will centralized components survive?How big is the market?When is ROI?
Poll
– Q: Do you represent a middleware supplier?
– Q: Are these assumptions correct?
PEPPOL for Middleware suppliers
Suppliers of MiddlewareMix and match – Use Service Metadata Interfaces without transport specifications and vice versa.Join us in our work to harden specificationsCountries are shifting entire infrastructures to PEPPOL specifications – Make your products availableMarket PEPPOL compliance to Service Providers
PEPPOL is at your service
Problems as seen from a Service Provider
Giving access to all is difficult300-500 service providers across Europe
Most interconnections are Bilateral and Ad hoc
No shared infrastructureThere are many different formats?
Poll
– Q: Do you represent a Service Provider?
– Q: Are these assumptions correct?
PEPPOL for Service Providers
Service ProviderEnter the PEPPOL peering agreementTake advantage of the shared componentsUse Middleware that supports PEPPOL specificationsPromote that you are connected to PEPPOL to your customers