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