Connecting to PEPPOL - different perspectives

720 views

Published on

Incentives for connecting to the PEPPOL infrastructure for service providers and large buyers.

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
720
On SlideShare
0
From Embeds
0
Number of Embeds
11
Actions
Shares
0
Downloads
20
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Connecting to PEPPOL - different perspectives

  1. 1. Connecting to the PEPPOL Infrastructure<br />Mikkel Hippe Brun<br />Technical Director, PEPPOL<br />Chief Consultant, Danish IT- and Telecom Agency<br />Email: mhb@itst.dk<br />Twitter: @hippebrun<br />Pan European eProcurement with PEPPOL<br />Copenhagen, Denmark<br />October 21th – 23rd 2009<br />
  2. 2. The PEPPOL exchange challenge<br />?<br />
  3. 3. Who is involved?<br />Buyers<br />Suppliers<br />Software suppliers<br />Business Software<br />Middleware<br />Service Providers<br />Banks<br />VANs<br />eProcurement Platform Providers<br />?<br />
  4. 4. The peer-2-peer-model<br />Characteristics (simplified)<br />Agreed upon standards for transport <br />open or proprietary<br />Perhaps - agreed upon standards for content<br />Difficult to match business requirements<br />
  5. 5. The three-corner-model<br />Characteristics (simplified)<br />Proprietary standards (whole stack)<br />Risk of service provider lock-in / Limited competition<br />Customers may have to connect to more than one service provider<br />
  6. 6. The four-corner-model<br />Characteristics (simplified)<br />Agreed upon standards for transport <br />open or proprietary<br />Perhaps - agreed upon standards for content<br />Freedom to choose service provider<br />
  7. 7. Business requirements<br />
  8. 8. The PEPPOL exchange challenge<br />?<br />
  9. 9. PEPPOL Infrastructure<br />SML = Service Metadata Locator (interface)<br />SMP = Service Metadata Publisher (interface)<br />AP = Access Point (Operated by a Service Provider)<br />
  10. 10. Our foundation<br />Content and business process standards<br />CEN/ISSS WS BII<br />OASIS UBL<br />UN/CEFACT Cross Industry Invoice<br />Internet and web services standards<br />OASIS<br />W3C<br />IETF<br />
  11. 11. We provide<br />Specifications<br />Central infrastructure<br />Open Source Software<br />Reference Implementations<br />Hands-on workshops and support<br />Legal framework<br />
  12. 12. Mainstream adoption in 10 years<br />Maturity<br />23 mill.<br />Volume<br />Mainstream adoption<br />Time<br />10 years<br />8 years<br />5 years<br />
  13. 13. Mainstream adoption in 5 years<br />Maturity<br />23 mill.<br />Volume<br />Mainstream adoption<br />Time<br />10 years<br />4 years<br />5 years<br />
  14. 14. We need concerted action<br />Suppliers of <br />Business Software<br />ERP solutions<br />Middleware software<br />Service Providers<br />Banks<br />Value Added Network Operators<br />eProcurement Platform Providers<br />Governments and large private buyers<br />
  15. 15. Problems as seen from a software supplier<br />ERP and Business Software suppliers<br />Convergence between standards is slow<br />No standardized way of exchange<br />No standardized interface to service providers<br />Lack of critical mass<br />
  16. 16. Poll<br />Q: Do you represent a software supplier?<br />Q: Are these assumptions correct?<br />
  17. 17. PEPPOL for Software suppliers<br />Suppliers of Business Software and ERP<br />Agree to standardized business processes<br />Support standardized data models<br />Support standardized “connections” to Service Providers<br />PEPPOL is at your service<br />
  18. 18. Problems as seen from a middleware supplier<br />Is it a mature specification?<br />Will a new specification get traction?<br />Will centralized components survive?<br />How big is the market?<br />When is ROI?<br />
  19. 19. Poll<br />Q: Do you represent a middleware supplier?<br />Q: Are these assumptions correct?<br />
  20. 20. PEPPOL for Middleware suppliers<br />Suppliers of Middleware<br />Mix and match – Use Service Metadata Interfaces without transport specifications and vice versa.<br />Join us in our work to harden specifications<br />Countries are shifting entire infrastructures to PEPPOL specifications – Make your products available<br />Market PEPPOL compliance to Service Providers<br />PEPPOL is at your service<br />
  21. 21. Problems as seen from a Service Provider<br />Giving access to all is difficult<br />300-500 service providers across Europe<br />Most interconnections are <br />Bilateral and <br />Ad hoc<br />No shared infrastructure<br />There are many different formats?<br />
  22. 22. Poll<br />Q: Do you represent a Service Provider?<br />Q: Are these assumptions correct?<br />
  23. 23. PEPPOL for Service Providers<br />Service Provider<br />Enter the PEPPOL peering agreement<br />Take advantage of the shared components<br />Use Middleware that supports PEPPOL specifications<br />Promote that you are connected to PEPPOL to your customers<br />PEPPOL is at your service<br />
  24. 24. Call for action<br />Join us<br />Government are implementing<br />&gt;30,000 endpoints from May 1st 2010<br />Sustainable and robust infrastructure<br />Multilateral Legal framework<br />Mix and match<br />We are prepared to listen and change<br />Connect to the PEPPOL Infrastructure<br />
  25. 25. http://www.peppol.eu<br />

×