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
6. Workshop vision The CEN/BII Workshop vision is that all organizations, independently of public or private nature, size, or nationality, must be enabled to make electronic business in an efficient and effective manner and with low transaction costs. 2
7. Workshop mission The CEN/BII Workshop mission is to spread and facilitate the use of eProcurement standards by suppliers and buyers, including public administrations, by: supporting the convergence of commonly applied international standards of electronic procurement; providing a general framework for the organizational and semantic levels of the electronic documents; identifying the requirements for the eProcurement standards of interoperable tools; providing organizational support to ensure the maintenance and governance for those requirements. 3
8. BII objective Business Interoperability Interfaces for electronic Procurement in Europe - BII The objective of the work in BII is to “provide a basic framework for interoperability in pan-European electronic transactions, expressed as a set of technical specifications that are compatible and cross-refer to relevant standards in order to ensure global interoperability.” Interoperability is defined by the European Interoperability Framework,version 2 as “the ability of information and communication technology (ICT) systems and of the business processes they support to exchange data and to enable the sharing of information and knowledge” BII European Interoperability Framework, version 2 4 8
9. BII2 workshop Key Facts and Figures BII2 currently have 24 organizations from 9 different countries registered as workshop participants These organizations have so far nominated 68 experts to contribute to our work.
10. PEPPOL + BII = true The timeline of PEPPOL and BII2 are synchronized so that BII could benefit from the lessons learned in PEPPOL before publishing the results from BII2. BII1 BII2 BII profiles Joint work Lesonslearned PEPPOL Production Production pilot Test pilot PoC 13 10
11. BII addresses the whole eProcurement process The specifications provided by BII support the whole procurement process from publication of the Prior Information Notice through to the final Invoice. Based on, and supports, relevant EU directives 6 11
12. Profile key components Business process The behaviour of two or more Business Partners in order to achieve a common business goal. Process could be sourcing, ordering or billing Collaboration Business collaboration describes in detail the choreography of message exchange between two or more involved partners. Business partners take part in a business collaborations by playing an authorized role in it. Can be linked together to form business processes (such as dispute invoice, order cancellation) Transaction A business transaction is used to inform/synchronize/request the trading partner of an event. (Submit order, request delivery, request qoute) The transaction defines a set of data (information entities), relevant to the activity Syntax message A electronic message containing marked up information entities
15. Many profiles Catalogues, statement, ofl. BII01 - Catalogue only BII02 - Catalogue update BII17 - Multi party catalogue BII16 - Catalogue deletion BII23 - Invoice only with dispute BII09 - Customs Bill BII15 - Scanned Invoice BII18 - Punch-out BII20 - Customer Initiated Sourcing BII21 - Statement Tendering, support tools BII10 - Tender Notification BII11 - Qualification BII12 - Tendering Simple BII14 - Prior Information Notice BII22 - Call for Tender BII24 - Attachment Document BII25 - Status Request BII26 - Retrieve Business Document
16. PEPPOL BIS? What is that? The set of formal requirements for ensuring interoperability of pan-European Public eProcurement are specified as PEPPOL Business Interoperability Specifications (BIS). PEPPOL uses extensions i.e. adds Business Rules, to meet the PEPPOL specific Legal and Organisational Requirements A BIS is a guideline that specifies how a CEN/BII profile should be implemented in the PEPPOL context
20. Follow laws Be faster, more agile Trading Partner Goals Make money Simplify work Be productive Good relations Need automated invoice matching Need to get a response on an order Requirements on the electronic collaboration so that goals can be fulfilled Need to route information to the correct person Need to know when to deliver Need to know the delivery address Need to have tax information The delivery date must be stated The Invoice must be issued after delivery Can be defined and enforced by business rules Total amount should be the sum of the line amounts The supplier must accept or reject the order The Invoice must refer to the order
21. Follow laws Be faster, more agile Trading Partner Goals Make money Simplify work Be productive Good relations Requirements on the electronic collaboration so that goals can be fulfilled Need automated invoice matching Need to get a response on an order Need to route information to the correct person Can be defined and enforced by business rules Need to know when to deliver Need to know the delivery address Need to have tax information Business rules can be expressed in many ways Regular descriptive text The delivery date must be stated The Invoice must be issued after delivery Total amount should be the sum of the line amounts The supplier must accept or reject the order The Invoice must refer to the order UML or CCTS Data models (relationships, cardinalities) Business term names, definitions and data types. Guiding texts for rules that are not sutable for formal descriptions Process diagrams
22. Follow laws Be faster, more agile Goals Make money Simplify work Be productive Good relations Requirements CENBII Profiles and Transactions Business rules Need automated invoice matching PEPPOL BIS National additional rules Need to get a response on an order Need to route information to the correct person Need to know when to deliver Business rules expressed in various formats Need to know the delivery address Need to have tax information Regular descriptive text The delivery date must be stated The Invoice must be issued after delivery Total amount should be the sum of the line amounts An actual XML-message can be tested/validated against business rules using several techniques National Schematron BII Schematron PEPPOL Schematron UBL XML Schema * The supplier must accept or reject the order The Invoice must refer to the order Executable tools XSD Schemas Schematron, Stylesheet rules * For PEPPOL - Currently only UBL, can be additional in the future
31. 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
32. 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
33.
34. 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.
35. Service Levels Access Points 98,5% availability during business hours94% availability during the remaining time SMP 98,5% availability during business hours94% availability during the remaining time Defined contact points Reporting to Regional Authority in case of major faults (more than 4 hours down-time) It is free for providers to deliver higher levels of availability (and charge for the added value to their customer). It is not allowed to charge other APs participants/customers. See more details about this in the provider agreements. PEPPOL is free from roaming-charges between AP's and SMP's Page 32
