Edmund Gray, Technical Editor on Architecture and Mathodologies at CEN BII, UN/CEFACT TBG1 Vice Chair: „Global e-Business Standards and UN/CEFACT“

Edmund Gray

CEN BII Technical Editor on Architecture & Methodology

UN/CEFACT Supply Chain Projects Co-Ordinator Chair Irish Standards (NSAI) e-Procurement

Delegate to EU Multi-Stakeholder Forum

GLOBAL STANDARDS

• Standards setting bodies involved in e-Business

• ISO

• IEC

• ITU

• UN/ECE

• OASIS A Memorandum of Understanding (MOU) – tries to ensure no duplication of effort.

STANDARDS IN EU • CEN – non-profit organisation whose mission is to foster

the European economy in global trading, the welfare of European citizens and the environment

• 33 CEN Member countries • Members are National Standardization

Organizations. • Most standards are initiated by industry. • Other standardization projects can come from

consumers, Small and Medium-sized Enterprises (SMEs) or associations, or even European legislators.

CEN PRODUCTS

• European Standards (ENs)

• A European Standard is a standard that has been adopted by one of the three recognized ESOs: CEN, CENELEC or ETSI.

• Technical Specifications

• Where agreement cannot be achieved on an EN. It may co-exist with competing national standards

• Technical Reports

• Provides information, so no obligation to implement

• Workshop Agreements.

• Allows participation by non-EU countries but cannot conflict with an EN

CHOOSING STANDARDS

• How to choose?

• Two EU projects select suitable e-Business standards from SSOs.

• PEPPOL – Providing interoperability between Service Providers

• CEN BII – Designed for Public Procurement

– Also business to business

– Providing message standards for end to end e-Procurement

CEN BII • The vision of the BII Workshop is that all organizations, public or private are

enabled to conduct e-business in an effective and efficient manner, significantly lowering costs for transaction processing.

• The CEN WS/BII Workshop mission is to spread and facilitate the use of e-procurement standards by suppliers and buyers, and especially public administrations, by:

– identifying requirements (including legal);

– providing a general framework for the organizational and semantic levels of interoperability;

– supporting the implementation with guides;

– providing organizational support to ensure the governance and maintenance for those requirements.

8

WHAT IS CEN WS/BII? • Business Interoperability Interfaces for public

procurement in Europe (CEN WS/BII)

• A workshop under CEN

9

CWA 16560 BII Use of profiles in the tendering

process

CWA 16562 BII Post Award

profiles

CWA 16561 BII eCatalogue

profiles

CWA 16559 BII Tender

Notification profile

CWA 16558 Architecture

10

The implementation guide

The standards

UN/CEFACT SIMPLE, TRANSPARENT AND EFFECTIVE PROCESSES

FOR GLOBAL BUSINESS.

The implementation

The focus of BII is on collecting European requirements and to provide guidance for consistent implementation of existing international developments.

SCOPE OF WORK

The scope of work for the workshop continues to be on achieving interoperability along whole procurement process, with a B2G perspective, including where possible also a B2B perspective (which in the post-award is very close to B2G perspective).

OUR APPROACH A Profile is a technical specification describing:

– the choreography of the business process(es) covered,

– the electronic business transactions exchanged as part of the business process,

– the business rules governing the execution of that business process(es), its business collaborations and business transactions, as well as any constraints on information elements used

– the information content of the electronic business transactions exchanged documented in the form of transaction Information Requirement Models.

Goal

Requirements

Syntax

Validation

POST-AWARD – CWA 16562 • Grouping of profiles into processes :

– Ordering

– Fulfillment

– Invoicing

– Payment

13

ARCHITECTURE - CWA 16558

A. BII - Guideline - Profile Architecture

B. BII - Guideline - Capturing of Business Requirements

C. BII - Guideline - Conformance and Customizations

D. BII - Guideline - Implementation and Use of Validation Artifacts

E. BII - Guideline - Business Rules Description Mechanism

F. BII - Guideline - Code List Management

G. BII - Code Lists

H. BII - Guideline - Data format

I. BII - Guideline - Message Envelope Specification

J. BII - Guideline - Attachments Handling

K. BII - Guideline - Syntax Binding Methodology

L. BII - Guideline - Application of Electronic Signature

M. BII - Profile 36 - Message Level Response

N. BII - Report - Long Term Governance

O. BII - Report - Versioning and Change management

• BII - Report - Governance Model - V1.0.0

• BII - Presentation - Governance of the Life Cycle Management

14

BII IS OPERATIONAL!

15

CEN

WS/BII3

Base for the coming EN on electronic invoicing to public sector in Europe ?

e-notification e-tendering

Pre-award

e-catalog

Post-award

e-cataloge-ordering e-fulfilment e-ivoicing Other

e-Prior / Open e-PRIOR Dev Dev Prod Prod Prod Prod

PEPPOL / OpenPEPPOL Prod Prod Dev Prod

Austria Prod

Denmark Dev Prod

Iceland Dev

Ireland Prod

Italy Prod Prod

Nederland Prod

Norway (EHF) Dev Dev Prod Prod Prod Prod

Spain Prod Prod

Sweden Dev Dev Prod Prod Prod

Denmark Dev

How is BII relevant to the up-coming European Standard for electronic

invoicing?

Technology specific

Technology neutral

A robust and tested methodology

BII profile

Business goals

Business Requirements

Business process Information Requirement Model Business rules

European business requirements

BII Syntax Binding

Implementation guidance

BII Validation Tools

Compliance

Global business requirements

Business Requirement

Specification &

Required Information Model (Semantic model)

Message Model &

syntax standards

Technology specific

Technology neutral

Relevant deliverables

18

BII profile

Business goals

Business Requirements

Business process Information Requirement Model Business rules

European business requirements

BII Syntax Binding

Implementation guidance

BII Validation Tools

Compliance

Invoicing BII01 – Invoice Only BII05 – Billing (invoice and Credit Note) Trns010 – Invoice Trns014 – Credit Note UBL Invoice 2.1 UN/CEFACT CII D11A

• The goals

EXAMPLE FROM BII 05 - BILLING

EXAMPLE FROM BII05 – BILLING

20

• The business process

EXAMPLE FROM BII05 – BILLING

21

Business requirements

Information requirements

Business processes: • Accounting • Invoice verification • VAT reporting • Auditing • Payment • Inventory • Delivery process • Customs clearance • Marketing • Reporting

EXAMPLE FROM BII05 – BILLING

22

• Business rules

EXAMPLE FROM BII05 – BILLING

23

• Information Requirement Model

EXAMPLE FROM BII05 – BILLING

24

• Syntax binding

VALIDATION TOOL

25

An engaged and growing user community

e-notification e-tendering

Pre-award

e-catalog

Post-award

e-cataloge-ordering e-fulfilment e-ivoicing Other

e-Prior / Open e-PRIOR Dev Dev Prod Prod Prod Prod

PEPPOL / OpenPEPPOL Prod Prod Dev Prod

Austria Prod

Denmark Dev Prod

Iceland Dev

Ireland Prod

Italy Prod Prod

Nederland Prod

Norway (EHF) Dev Dev Prod Prod Prod Prod

Spain Prod Prod

Sweden Dev Dev Dev Dev Prod

• The BII deliverable have been, or are in the process of being, implemented in several countries – especially in the area of invoicing!

PEPPOL – A CEN BII USER

“Among the EU public-sector programs, PEPPOL is a rising star.

The adoption of PEPPOL by the UK’s Department of Health marks the largest organisation private or

public of this international standard”

Neelie Kroes

Vice-President of the European Commission responsible for the Digital Agenda

*Extract from the blog post: The future of public procurement?

Page 27

PEPPOL: the Future of Public Procurement

PEPPOL: THE VISION

The PEPPOL Vision is: “To enable businesses to communicate electronically with any European government institution in the procurement process, increasing efficiencies and reducing costs.”

The PEPPOL project (2008-2012) was launched to address the key e-Procurement challenges in Europe. It has been jointly funded by the EC and a consortium of 18 government agencies from 11 Member States and Associated Countries.

The e-Procurement

landscape

KEY CHALLENGES:

Closed networks, locked-in solutions and lack of interoperability, resulting in “islands of e-Procurement”

Multitude of standards and formats, resulting in need for conversion and increased cost and complexity

Lack of focus on the big picture: the complete purchase-to-pay process resulting in single process oriented solutions

HOW PEPPOL SOLVES THEM:

Open and secure network, as the backbone of the e-Procurement Infrastructure in Europe, connecting communities through Access Points

Standard-based specifications for e-Procurement documents to be exchanged over the PEPPOL network

Focus on the complete process and the critical phases, covering pre and post award processes

PEPPOL Overview

• PEPPOL is not an e-Procurement platform but instead provides a set of technical specifications that can be implemented in existing eProcurement solutions and services to make them interoperable between disparate systems across Europe.

• PEPPOL enables trading partners to exchange standards-based electronic documents over the PEPPOL network (based on a 4-corner model). These documents include e-Orders, e-Advance Shipping Notes, eInvoices, eCalogues, Message Level Response, etc..

• PEPPOL Access Points connect users to the PEPPOL network and exchange eProcurement documents based on the PEPPOL specifications. Buyers and suppliers are free to choose their preferred Access Point provider to connect to all PEPPOL participants already on the network. (Connect once, connect all)

Page 30

Use of PEPPOL for e-Invoicing

– The European Commission implemented its own e-invoicing platform (e-PRIOR)

based on PEPPOL specifications and connected to the PEPPOL transport infrastructure.

– Austria: From 2014, eInvoicing to the Federal government will be mandatory. Use

of PEPPOL specifications and network is one of the two options allowed.

– Denmark: National eInvoicing platform - NemHandel - (mandatory since 2005) is

PEPPOL enabled.

– France: French State connected to a PEPPOL Access Point; Healthcare

communities implementing eCatalogues. UGAP (Central Governmental

Procurement Agency) planning deployment of PEPPOL e-Invoicing with local

authorities. PEPPOL e-Invoices accepted by the central administration system

(Chorus)

– Ireland: Irish Health Service require a PEPPOL compliant e-Invoicing solution

– Italy: Intercent-ER (Emilia Romagna) with many Healthcare authorities and ENI

implementing eOrdering & eInvoicing; Telecom Italia implementing eInvoicing.

Region of Lombardia to implement e-Orders with PEPPOL for all CAs in the region

Use of PEPPOL for e-Invoicing

– Netherlands: National eInvoicing initiative ‘SimplerInvoicing’ implemented PEPPOL

specification for eInvoicing in the B2B and B2G during summer 2013 with successful

results. Soft national roll-out to started in 2014.

– Norway: From July 2012 eInvoicing to the government is mandatory, based on PEPPOL

specifications and PEPPOL network use recommended. Vast majority of central

government organisations can receive PEPPOL-based eInvoices.

– Poland: PEPPOL to be part of the national eInvoicing strategy. PEPPOL Authority to be

established in 2015. Ministry of Economy in charge of implementing the eInvoicing

Directive in public procurement is the candidate authority.

– Sweden: eOrdering and eInvoicing mandatory for governmental agencies but used also

frequently in municipalities and regions even if it is on voluntary basis. PEPPOL

recommended for Catalogue without response, Order, Despatch advice and Billing;

Invoice and Credit Note.

– United Kingdom: In 2014, the NHS England recommended the adoption of PEPPOL for

eOrders, eInvoices and eAdvanced Shipping Notes, throughout the healthcare sector.

PEPPOL e-Invoicing: Norway

– Scope: B2G; B2B; G2B; B2C.

– Use of PEPPOL approach reduces risk and cost as operational solutions are available and ready to be used for wider parts of the public procurement process

– Fastest growing e-invoicing network in Norway

– Private sector use has outgrown public sector use

– Public sector use of e-Invoicing benefits both government and businesses

Page 33

Some key figures:

22.023 recipients registered (as of September 2014)

Approximately 14% are public sector recipients while 86 % are private.

Vast majority of central government organisations and municipalities can receive PEPPOL-based eInvoices

4,7 million transactions reached

Out of the first million transactions exchanged over the PEPPOL network, nearly 50% are Business-to-Government, and the remaining is Business-to-Business.

44 Access Points facilitating both domestic and cross border invoicing

PEPPOL e-Invoicing:

National Health Service England

– Scope: Health Care

– NHS e-Procurement Strategy mandates use of PEPPOL for:

– e-Ordering

– e-Invoicing

– e-Advanced Shipping Notes

– Using the PEPPOL Network (4-corner model)

– PEPPOL Authority to be set up ensuring public sector governance

Page 34

Some key figures:

NHS England revenue budget is set at around £110 billion

The NHS eProcurement strategy is part of the Procurement Efficiency Programme, which project savings £1.5 billion by the end of the financial year 2015-2016

Some estimate suggest that e-Invoicing could save the UK public sector and its suppliers a minimum of £2 billion per annum

Join the OpenPEPPOL and CEN BII community!

www.peppol.eu

E-mail: [email protected]

[email protected]

More information:

http://www.cenbii.eu

Hvala na pažnji!