The BII initiative

1. The BII initiative The path towards more efficient procurement in Europe Brussels December 10, 2013 Jostein Frømyr CEN WS/BII3 Vice-chair, technical coordination

2. Agenda • What is CEN WS/BII? • What can we offer today? • What have we achieved so fare? • How are we relevant to the up-coming European Standard for electronic invoicing

3. Vision and mission • The vision of the BII Workshop is that all organizations – independent of whether they are public or private and whatever their size and nationality - are enabled to conduct electronic 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) regarding e-procurement standards; • providing a general framework for the organizational and semantic levels of interoperability for the electronic procurement documents; • supporting the implementation of commonly applied international e-procurement standards; • providing organizational support to ensure the governance and maintenance for those requirements.

4. What is CEN WS/BII? • Business Interoperability Interfaces for public procurement in Europe (CEN WS/BII) • A workshop under CEN • Phase 1  CWA 16073 • Phase 2  5 CWAs • CWA 16559 • BII Tender Notification profile • CWA 16560 • BIIUse of profiles in the tendering process • CWA 16561 BIIeCatalogue profiles • CWA 16562 BIIPost Award profiles • CWA 16558 • Architecture

5. UN/CEFACT SIMPLE, TRANSPARENT AND EFFECTIVE PROCESSES FOR GLOBAL BUSINESS. BII guides implementation of standards • The focus of BII is on collecting European requirements and to provide guidance for consistent implementation of existing international developments. The standards The implementation guide The implementation

6. Scope of work Pre-awarding phases Post-awarding phases The scope of work for the workshopcontinues 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). Notification identify need call for tender preparation Access eSubmission Awarding Contract Fulfilment Invoicing Ordering Payment

7. Our approach Goal 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. Requirements Validation Syntax

8. Core information requirements • BII is defining core information requirement models • the set of information elements sufficient to cater for the generally expressed business requirements applicable throughout the European market. • BII specifications can be implemented as is, but are also intended for further customization. BII Business Transaction Customized Business Transaction

9. Consistancythrougout the whole Procurement process Pre-awarding phases Post-awarding phases Notification identify need call for tender preparation Access eSubmission Awarding Contract Fulfilment Invoicing Ordering Payment CWA 16559 eNotification CWA 16560 eTendering CWA 16561 eCatalogue CWA 16562 Post-award CWA 16558 Architecture

10. Liaison eTendering  eNotification One type of business process to submit the publication of a procurement notice and to retrieve status Deliveries: Profile specification: Profile BII-10 eNotification Linked with the eTendering profiles Transaction information requirements: BiiTrns064 Pre-award Publication Library F1Prior information notice, F2 Contract notice, F3 Contract award notice BiiTrns065 NoticePublicationResponse Syntax binding to UBL Validation tool eNotification – CWA 16559

11. eTendering - CWA 16560

12. eCatalogue – CWA 16561

13. Post-award – CWA 16562 • Grouping of profiles into processes : • Ordering • Fulfillment • Invoicing • Payment

14. Architecture - CWA 16558 • BII - Guideline - Profile Architecture • BII - Guideline - Capturing of Business Requirements • BII - Guideline - Conformance and Customizations • BII - Guideline - Implementation and Use of Validation Artifacts • BII - Guideline - Business Rules Description Mechanism • BII - Guideline - Code List Management • BII - Code Lists • BII - Guideline - Data format • BII - Guideline - Message Envelope Specification • BII - Guideline - Attachments Handling • BII - Guideline - Syntax Binding Methodology • BII - Guideline - Application of Electronic Signature • BII - Profile 36 - Message Level Response • BII - Report - Long Term Governance • BII - Report - Versioning and Change management • BII - Report - Governance Model - V1.0.0 • BII - Presentation - Governance of the Life Cycle Management

15. Scalable solutions Trough the use of Profiles, BII provides for flexible and scalable implementation of the various business processes in eProcurement

16. BII is operational! • Base for the coming EN on electronic invoicing to public sector in Europe ? CEN WS/BII3

17. BII is a success at least in Norway • Since July 1, 2012 central government agencies has been mandated to receive electronic invoices according to the EHF specification. • EHF is an implementation/customization of BII. • Today we have • More than 8.000 businesses sending more than 320.000 invoices in October 2013. • More than 90% of businesses and 50% of transactions is in private sector. • A monthly growth rate of some 30% • If this growth continues there will be some 61 million invoices exchanges next year, covering approximately 1/3 of the total invoice volume in Norway.

18. Denmark • Planning to implement Dispatch Advice in a pilot in NemHandel beginning of next year • Assuming the pilot is a success we will move on to implement the other BII documents • In the beginning I think we will focus on documents/profiles that we do not already have in OIOUBL - like pre-award.

19. Sweden • Since 2008 all government agencies have been mandated to receive and send electronic invoices. • The standard that they shall use iSvefaktura; from UBL; i e an earlier version of the CEN/BII invoice. • Next year it will also be the CEN/BII Invoice (PEPPOL BIS) as an alternative. • The agencies shall now continue with ordering process electronically and the standard is CEN/BII Order Only profile. • Municipalities and regions have started with e-invoicing and the whole ordering-invoice process since many years. • Also using deliverables from CEN/BII. • Almost 70 % of all municipalities and 95 % of all regions/county councils have e-invoicing and many of them receive 50-75 % e-invoices(in structured format)

20. How is BII relevant to the up-coming European Standard for electronic invoicing?

21. A robust and tested methodology European business requirements Global business requirements Technology neutral BII profile Business Requirement Specification & Required Information Model (Semantic model) • Business goals • Business Requirements • Business process • Information Requirement Model • Business rules Technology specific Message Model & syntax standards BII Syntax Binding BII Validation Tools • Implementation guidance • Compliance

22. Relevant deliverables European business requirements Invoicing BII01 – Invoice Only BII05 – Billing (invoice and Credit Note) Trns010 – Invoice Trns014 – Credit Note UBL Invoice 2.1 UN/CEFACT CII D11A Technology neutral BII profile • Business goals • Business Requirements • Business process • Information Requirement Model • Business rules Technology specific BII Syntax Binding BII Validation Tools • Implementation guidance • Compliance

23. The goals Example from BII 05 - Billing

24. The business process Example from BII05 – Billing (2)

25. Business requirements Information requirements Example from BII05 – Billing (3) • Business processes: • Accounting • Invoice verification • VAT reporting • Auditing • Payment • Inventory • Delivery process • Customs clearance • Marketing • Reporting

26. Business rules Example from BII05 – Billing

27. Information Requirement Model Example from BII05 – Billing

28. Syntax binding Example from BII05 – Billing

29. Validation tool

30. The BII deliverable have been, or are in the process of being, implemented in several countries – especially in the area of invoicing! An engaged and growing user community

31. A short recap…..

32. Summary of achievements • Engaged stakeholders • Robust methodology • Useful deliverables • Actual implementation • Recognition of the added value BII is contributing to making procurement in Europe more efficient!

33. BII enables interoperablee-procurements solutions • BII Profiles allow for interoperability at the organizational level. • BII Information Requirement Models allow for interoperability at semantic level. • BII syntax binding and validation tools supports interoperability at technical level.

34. What’s in the future? • Continue the work initiated by CEN WS/BII, and further refined under CEN WS/BII 2, to support interoperability in electronic procurement and business. • Provide increased value to the BII user community by • Filling the gaps to ensure that all relevant aspects of e-procurement are covered • Facilitate increased use through capacity building • Securing the continued relevance of the BII deliverables by providing a focal point for governance and lifecycle management

35. More information: http://www.cenbii.eu/ THANK YOU FOR YOUR ATTENTION!