The PEPPOL project aims to enable EU-wide public eProcurement by establishing an infrastructure for businesses to communicate electronically with any European contracting authority. It involves 18 beneficiaries from 12 countries working on 8 work packages over 4 years with a budget of 30.8 million euros. The PEPPOL vision is for any supplier in the EU, including SMEs, to be able to communicate electronically with any European contracting authority for all procurement processes. A 5-stage progress plan outlines building the PEPPOL community from basic components in 2010 to universal adoption after 2012. The PEPPOL infrastructure uses specifications for components like registries and transport protocols to allow participants to locate and exchange messages with each other across Europe in a standardized way. Governance

1. PEPPOLWorkshop – Overview and OSOR Martin Forsberg, Ecru Consulting

2. The PEPPOL project The PEPPOL project is the result of the European Competitiveness and Innovation Programme (CIP) ICT Policy Support Programme (ICTPSP) 2007 and 2009 Call for Proposals Pilot A objective: Enabling EU-wide public eProcurement 50% EU contribution for achieving interoperability Coordinated by the Norwegian Agency for Public Management and eGovernment (Difi) Consortium and scope: 18 beneficiaries from 12 countries Total budget 30,8 M€ 8 work packages, <1.600 person months and 10 M€ on sub-contractors Project start up: 1 May 2008, duration 48 months* *Current project duration is 42 months (+6 months extension subject to European Commission's approval)

3. Any supplier (incl. SMEs) in the EU can communicateelectronically with any European contracting authority for all procurement processes. The PEPPOL Vision 3

4. eProcurement

5. Progress plan for building the PEPPOL community READY: Since May 2010, basic PEPPOL components and services are in place for a limited number of invited test pilot participants. PROVEN: From now until mid 2011, a growing number of production pilots create an integrated community between PEPPOL consortium members, using PEPPOL to perform real business. Recruitment of non-PEPPOL consortium members as pilot participants evolves. IN USE: By the end of 2011, we will have a substantial number of pilots performing real business through PEPPOL among both PEPPOL and non-PEPPOL consortium members. ESTABLISHED: By mid 2012, the PEPPOL Community expands beyond those recruited by PEPPOL to recruitment by commercial market driven adoption. UNIVERSAL: After mid 2012, a critical mass of adoption sees PEPPOL used by a majority of eProcurement communities across Europe. Page 5

6. Page 6 The PEPPOL Infrastructure – An overview

7. Typical scenario today ID:731923449 Sending document to ID:731923449, using operator ID:OPERATOR_123 A message to trading partner ID:731923449 Operator checks if routing information exists Ok! Connection exists!

8. Typical scenario today A message to trading partner ID:731923449 Operator checks if routing information exists Not found! No peering agreement exists – no routing possible ID:731837732

9. BusDox – the specifications behind the PEPPOL infrastructure SMP (registry) – Describes how a registry should be accessed and what infromation needed to be exposed. The SMP is a service registry, not a traditional partner capability registry. SML(registry/service locator) – Describes how the interface against the DNS works. The SML is used to add/update/delete information about the registry in where a particular participant is located START(transport protocol) – Describes how the message exchange is performed in a reliable and secure way using web services. LIME(transport protocol) – Describes how a accounting system/E-invoicing system connects to a service provider. A bit like the POP3 protocol for emails (look for a list of document, download received documents, upload documents)

10. The PEPPOL-way PEPPOLs registry locator (DNS) Service registry (SMP) Resolving a REST-URL for the participant. Is automatically directed by the DNS to the relevant registry Service metadata (where to send to, what to send) ID:731923449 Sending messge according to the service metadata A message to trading partner ID:731923449

11. How does it work? A URL is build based on the receving partipcant’s ID, and the domain of the PEPPOL central locator A bit simplified: http://SE5523222312.sml.peppolcentral.orgPoints towards registry ABC Andhttp://DK4723222753.sml.peppolcentral.orgPoints towards registry XYZ Exactly as http://mail.ecru.sepoints the our mail server and http://www.ecru.sepoints to our web server (located and hosted by different providers) The URL is built using the same mechanism ALL THE TIMEYou only need to know the participant’s identifier to retreive the necessary data for the service that receives the documents

13. Type of supported messages (and customizations)

14. Type of supported process

15. Type of supported transport protocol/profile

17. The PEPPOL-way again PEPPOLs registry locator (DNS) Service registry (SMP) Resolving a REST-URL for the participant. Is automatically directed by the DNS to the relevant registry Service metadata (where to send to, what to send) ID:731923449 Sending messge according to the service metadata A message to trading partner ID:731923449

18. Page 15 The PEPPOL Governance Model

19. The PEPPOL Governance Model The basis for PEPPOL is that national infrastructures exist and will continue to exist also in the future (In addition, privately operated e-procurement communities exist within and across borders) The objective of PEPPOL is to provide interoperability between existing solutions so that “any supplier (incl. SMEs) in the EU can communicate electronically with any European contracting authority for all procurement processes”. The specifications and technology used by PEPPOL may be candidate solutions for domestic adoption/recommendation The proposed governance model for the PEPPOL transport infrastructure respects this basis and is thus built around two levels of coordination: The European wide coordination providing governance over all common components of the transport infrastructure. The regional coordination providing governance over the implementation and use of the transport infrastructure within a domain.

20. Regional domain Regional domain AP AP Contracting Authority Economic Operator SMP SMP SML Coordinating Authority Regional Authority Two levels of governance Provides European wide governance for: the PEPPOL Technical Standards the PEPPOL Service Specifications the PEPPOL SML the PEPPOL Agreements Provides regional governance for: the implementation and use of the transport infrastructure the legal framework for specific AP and SMP agreements specific requirements applicable within a domain

21. Page 18 The PEPPOL Transport Infrastructure Agreements

22. PEPPOL Transport Infrastructure Agreements The aim of the PEPPOL Transport Infrastructure Agreements is to regulate the roles and responsibilities of the actors involved in the governance and operation of the PEPPOL transport infrastructure. Three separate agreements with a common set of annexes. Contact points Definitions Service and Service Levels Technical Standards Regional domain and its specific services and service levels Change Procedures The PEPPOL Governance Model and model agreements

23. Key principles Inspired by other initiatives, but reflects the uniqueness of the PEPPOL initiative: An open community where interoperability is achieved through common specification and not point-to-point agreements. The PEPPOL Transport Infrastructure Agreements provides governance for the PEPPOL Transport Infrastructure based on: a European wide coordination over all common components of the transport infrastructure; a regional coordination and supervision of the implementation and use of the transport infrastructure within a domain; and open and transparent provision of SML, SMP and AP services based on a common set of agreements as well as common definition of services and service levels.

24. PEPPOL Transport Infrastructure Agreements PEPPOL Community Agreement “… terms and conditions under which the Parties shall provide governance for the PEPPOL Transport Infrastructure.” A model agreement regulating the “… terms and conditions under which: the PEPPOL AP Provider shall provide the required PEPPOL AP Services; the PEPPOL Regional Authority shall ensure that the services provided by the PEPPOL AP Provider are provided and maintained in a reliable, professional and state of the art manner, in compliance with all applicable laws and all relevant technical specifications, to ensure consistency across the full PEPPOL Transport Infrastructure .” A model agreement regulating the “… terms and conditions under which: the PEPPOL SMP Provider shall provide the required PEPPOL SMP Services; the PEPPOL Regional Authority shall ensure that the services provided by the PEPPOL SMP Provider are provided and maintained in a reliable, professional and state of the art manner, in compliance with all applicable laws and all relevant technical specifications, to ensure consistency across the full PEPPOL Transport Infrastructure.” PEPPOL AP Provider Agreement Coordinating Authority I.e. PEPPOL GB Regional Authority E.g. VM SMP Provider E.g. ITELLA AP Provider E.g. ITELLA PEPPOL SMP Provider Agreement

25. eProcurementwithout borders in Europe www.peppol.eu