CEF Grants eprocurement and einovice

CEF Grants eprocurement and einovice 2017

CEF Grants eprocurement and einovice eprocurement EUR 4 million total for the entire call no limit on individual grants Up to 75 % of eligible costs Consortium of at least two legal entities, can be public and/or private Deadline for submission is 21 st September 2017 Difi will apply einvoice EUR 10 million total for the entire call no limit on individual grants Up to 75 % of eligible costs Consortium of at least two legal entities, can be public and/or private Deadline for submission is 28 th November 2017 Not certain that Difi will apply

CEF Grants eprocurement Pre-award - ESPD, etender, transport AS4

CEF Grants - eprocurement The priority outcomes of this call for proposals are to help complete the transition to eprocurement in the Member States. In particular, they will facilitate cross-border bidding and contribute to simplify public procurement procedures in the Member States. Implementation of a "customised" European Single Procurement Document (ESPD) Integration of e-certis into existing software solutions Making their eprocurement systems interoperable using edelivery with the use of etender documents.

What is ESPD, ecertis and PEPPOL network. - ESPD is the electronic self-declaration form used in the competition phase in a public procurement. All public authorities are required to use electronic ESPD in their tenders, and suppliers must provide their own declaration (ESPD) to send to the contractor on the standardized form. - ecertis is the European database that provides information about what other countries call their documents like tax certificates, company certificates and certificates of various kinds. In a tender, there may be questions about documents that are different from what you are used to. Then you can connect to the ecertis database and find out what documents are meant. - The PEPPOL network is currently used to exchange invoices, catalogues and orders in the EHF and PEPPOL BIS format. This is based on a common agreement in a standard setup between the players in the network. The PEPPOL network can be set up with various security solutions and messaging protocols depending on needs. This project provides support for connecting to the PEPPOL network through the AS4 messaging exchange protocol. edelivery service provider is mandatory for the implementation of the etendering interface - BIS 46 - Subscribe to Procedure, BIS 60a - Tender Status Inquiry, BIS 47x - Call For Tender with ESPD, BIS 54 - Submitt Tender

CEF Grants - eprocurement 1) Implementation of a "customised" European Single Procurement Document (ESPD) in existing eprocurement systems in the Member States. An ESPD compatible service can be implemented via the: a. Integration of the ESPD data exchange model (the latest available version) b. Reuse of the open source code provided by the European Commission ESPD services implemented in Member States must be able to import and export an ESPD XML file (request and response) -------------------------------------- 2) Integration of e-certis into existing software solutions of private companies and contracting authorities. It is recommended for implementers of an ESPD service to also integrate the e-certis interface in their proposed Actions.

CEF Grants - eprocurement Deployment of edelivery is included in the proposal, support will be given to activities aiming to: a. Deploy access points and/or operating access points; b. Deploy service metadata publishers (SMP) and/or operate service metadata publishers; c. Upgrade data exchange solutions to be fully comply with, the CEF edelivery standards. A typical upgrade involves adding or configuring functionality to the data exchange solution to support the CEF edelivery standards (e.g. encryption algorithm, four-corner model support, support of dynamic discovery, etc.). For the purposes of this call, an Access Point is an implementation of PEPPOL AS4

CEF Grants eprocurement Project period January 2018 December 2018 Call closing 21.09.2017 Signature of grant agreements: June 2018 You can start developing from September 21 st but on you own risk One payment after the project is finished + 4-8 weeks (April 2019)

Some useful links CEF Grants eprocurement call: https://ec.europa.eu/inea/en/connecting-europe-facility/cef-telecom/apply-funding/2017-cef-telecom-call-eprocurement-cef-tc-2017-2 CEF Work prograrm 2017 (see page 38-41): https://ec.europa.eu/inea/sites/inea/files/c_2016_5768_1_annex_en_v1_p1_861116.pdf CEF Call test: https://ec.europa.eu/inea/sites/inea/files/2017-2_eprocurement_calltext_superfinal_060517_.pdf PEPPOL.eu: http://www.peppol.eu/ www.anskaffelser.no: https://www.anskaffelser.no/verktoykasse-systemleverandorer/ehf-infrastruktur-konkurransegjennomforing/aksesspunkt

Activities and milestone

M A Aktivitet 1 1 Project management 1 2 Difi - coordinating the consortium Difi - Develop EHF ESPD v1 based on the commission data model (ESPD v1.0.2) and XSD, including guidelines, validator 2 1 and tet files 3 1 Difi - Contribute to the development of PEPPOL BIS ESPD v2 based on ESPD v2 using UBL2.2 3 2 Difi - Develop EHF ESPD v2 based on PEPPOL BIS ESPD v2, includign guidelines, validator and test files 4 1 Install EHF ESPD v1 (based on ESPD 1.0.2) 5 1 Install or upgrade to EHF ESPD v2 + PEPPOL BIS ESPD v2 5 2 Install or upgrade to the last version of ecertis integrated in your own system (using ecertis api from the commission) 6 1 Install an Access Point with AS4 using Oxalis multi-protocol (preferred) or Domibus 6 2 Operate a AS4 Access Point for 1 year Install or upgrade to etender documents EHF and BIS 60a - Tender Status Inquiry, BIS 47x - Call For Tender with ESPD, 6 3 BIS 54 - Submit Tender Be a part of the OpenPEPPOL pre-award coordinating community (PRaCC) - Make/connect to the 4-corner model of 6 4 OpenPEPPOL (membership, make an Access Point, operate the Access Point) during the project Contribute to the adaptation of the PEPPOL transport infrastructure agreement (PEPPOL TIA) for handling of ESPD and 6 5 other pre-award document types in the PEPPOL edelivery network (4-corner model) 7 1 Marketing pre-award submission of tender documents through the 4-corner model 7 2 Marketing pre-award Access Point (AS4) use 7 3 Marketing your own solutions for EO on submission of tender documents through the 4-corner model 7 4 Marketing the use of EHF ESPD v1 and/or v2 as the only format for use in Norway 7 5 Increase the number of users of etendering solutions implementing electronic ESPD on the 4-corner model

Milestone for eprocurement: 1 Project management 31.des.18 2 EHF ESPD v1 ready from Difi 01.feb.18 3 EHF ESPD v2 ready from Difi 15.sep.18 4 Installed EHF ESPD v1 in production 01.mai.18 5 Installed or upgraded to EHF ESPD v2 and PEPPOL BIS ESPD v2 in production by at least one etendering platform 15.des.18 6 Installed or upgraded EHF and PEPPOL BIS etendeer documents in production by at least one etendering platform 31.des.18 7 All participants have started on marketing showing increase use of ESPD files via 4-corner model 01.okt.18 8 Participants show marketing results on increasing the use of ESPD files via 4-corner model 15.des.18 M A Aktivitet from to jan.18 feb.18 mar.18 apr.18 mai.18 jun.18 jul.18 aug.18 sep.18 okt.18 nov.18 des.18 jan.19 1 1 Project management jan.18 des.18 Final report 1 2 Difi - coordinating the consortium jan.18 des.18 Final report 2 Difi - Develop EHF ESPD v1 based on the commission data model (ESPD v1.0.2) and XSD, including guidelines, validator 1 and tet files jan.18 jan.18 3 1 Difi - Contribute to the development of PEPPOL BIS ESPD v2 based on ESPD v2 using UBL2.2 jan.18 okt.18 3 2 Difi - Develop EHF ESPD v2 based on PEPPOL BIS ESPD v2, includign guidelines, validator and test files jun.18 des.18 4 1 Install EHF ESPD v1 (based on ESPD 1.0.2) feb.18 apr.18 5 1 Install or upgrade to EHF ESPD v2 + PEPPOL BIS ESPD v2 okt.18 des.18 5 2 Install or upgrade to the last version of ecertis integrated in your own system (using ecertis api from the commission) jan.18 des.18 6 1 Install an Access Point with AS4 using Oxalis multi-protocol (preferred) or Domibus jan.18 des.18 6 2 Operate a AS4 Access Point for 1 year jan.18 des.18 6 Install or upgrade to etender documents EHF and BIS 60a - Tender Status Inquiry, BIS 47x - Call For Tender with ESPD, 3 BIS 54 - Submit Tender jun.18 nov.18 6 Be a part of the OpenPEPPOL pre-award coordinating community (PRaCC) - Make/connect to the 4-corner model of 4 OpenPEPPOL (membership, make an Access Point, operate the Access Point) during the project jan.18 des.18 6 Contribute to the adaptation of the PEPPOL transport infrastructure agreement (PEPPOL TIA) for handling of ESPD and 5 other pre-award document types in the PEPPOL edelivery network (4-corner model) jan.18 des.18 7 1 Marketing pre-award submission of tender documents through the 4-corner model jan.18 des.18 7 2 Marketing pre-award Access Point (AS4) use jan.18 des.18 7 3 Marketing your own solutions for EO on submission of tender documents through the 4-corner model jan.18 des.18 7 4 Marketing the use of EHF ESPD v1 and/or v2 as the only format for use in Norway jan.18 des.18 7 5 Increase the number of users of etendering solutions implementing electronic ESPD on the 4-corner model jan.18 des.18

CEF Grants einvoice European Norm on einvoice

CEF Grants - einvoice The call aims to promote the uptake of compliant einvoicing solutions by public and private entities, which will facilitate the implementation of the European standard (EN) on electronic invoicing and the set of ancillary standardisation deliverables, as mandated by the einvoicing Directive Uptake of einvoicing solutions compliant with the EN and its ancillary deliverables by public entities Update of einvoicing solutions compliant with the EN and its ancillary deliverables by solution providers and public authorities Integration of edelivery services with AS4

CEF Grants - einvoice Integration of edelivery services All proposals should address edelivery for the purpose of document delivery by deploying the edelivery Building Block or proving the use of edelivery through a service provider for cross-border communication as the minimal accepted scope. Support for the integration of edelivery services will only be awarded if carried out in conjunction with activity 1 or 2. If the deployment of edelivery is included in the proposal, support will be given to activities aiming to: a. deploy access points and/or to operate access points for one year; b. deploy Service Metadata Publishers (SMP) and/or to operate Service Metadata Publishers for one year; c. upgrade data exchange solutions (Commercial Off-the-Shelf (COTS), Open-Source Software (OSS) and other) to support, and therefore fully comply with, the CEF edelivery standards. A typical upgrade involves adding or configuring functionality to the data exchange solution to support the CEF edelivery standards (e.g. encryption algorithm, four-corner model support, support of dynamic discovery, etc.). For the purposes of this call, an Access Point must be an implementation of the e-sens AS4 Profile (developed by e-sens and now maintained by CEF). The Service Metadata Publisher (SMP) must be an implementation of the SMP Specification developed by e-sens on top of the OASIS SMP Specification, also maintained by CEF.

CEF Grants einvoice Project period January 2018 December 2018 Call closing 28.11.2017 Signature of grant agreements: August 2018 You can start developing from November 28 th but on you own risk One payment after the project is finished + 4-8 weeks (April 2019)

Some useful links CEF Grants eprocurement call: https://ec.europa.eu/inea/en/connecting-europe-facility/cef-telecom/apply-funding/2017-cef-telecom-call-einvoicing-cef-tc-2017-3 CEF Work prograrm 2017 (see page 38-41): https://ec.europa.eu/inea/sites/inea/files/c_2016_5768_1_annex_en_v1_p1_861116.pdf CEF Call test: https://ec.europa.eu/inea/sites/inea/files/2017-3_einvoicing_calltext_final_280617.pdf PEPPOL.eu: http://www.peppol.eu/ www.anskaffelser.no: https://www.anskaffelser.no/verktoykasse-systemleverandorer/ehf-infrastruktur-konkurransegjennomforing/aksesspunkt

Validation of the application

Selecting criteria 1. Admissibility conditions Submitted on time Complete 2. Eligibility Consortium composition 3. Exclusion No misconduct 4. Selection criteria Financial capacity Operational capacity

Selecting criteria Financial capacity No aid to actions receiving founds from other sources of EU financing Non-profit principle No grants may be awarded retrospectively for actions already completed Operational capacity Dispose own human resources Dispose knowledge and capabilities

Direktoratet for forvaltning og IKT Scoring (0 5) Failure 0. The proposal fails to address the criterion under examination or cannot be judged due to missing or incomplete information. 1. Very poor: The criterion is addressed in an inadequate manner, or there are serious inherent weaknesses. 2. Not satisfactory: While the proposal broadly addresses the criterion, there are significant weaknesses. Accepted 3. Good: The proposal addresses the criterion well, although improvements would be necessary. 4. Very Good: The proposal addresses the criterion very well, although certain improvements are still possible. 5. Excellent: The proposal successfully addresses all relevant aspects of the criterion in question. Any shortcomings are minor.

Direktoratet for forvaltning og IKT 5. Award criteria SCORE A1 Relevance (0-5) Alignment with objectives of the call Alignment with national and European policies and strategies A2 Quality and efficiency of the implementation (0-5) Maturity of solution, Coherence of work plan Quality of participants, Support for the solution Attention to relevant frameworks and regulations A3 Impact and sustainability (0 5) Approach for wider deployment and take-up Long term sustainability

Direktoratet for forvaltning og IKT Who gets money «Total score» as long as there is money left Cross-boarder consortia will be preferred

The application

Your application - remember Relevance to the call Do not be greedy be realistic ask for what you need and not any more You must use internal recourses not consultants All expenses must be documented incase of INEA control No double founding: Applicants who already benefit from funding for generic services covered in the previous calls (e-certis and/or ESPD activities) may not submit applications under this call for the same generic services.

How to do the application This is what you must do: 1. Start reading and fill out all documents. 2. Start filling out document 3. DO NOT sign and stamp the documents 4. The Excel spreadsheet 6 Financial capacity check you shall fill out the 4 first flaps (Overview, Introduction, Balance Sheet, Profit & Loss Account). On flap 5 (Ratio Analysis) you will see if you are economic eligible for the CEF Grants call. 5. When you have fill out all documents send them to jens.aabol@difi.no. Mark the title of the e-mail CEF einvoice documents from <company name> 6. When all the documents are received, I will punch them into the CEF Call application online form. 7. You will than get the application forms back for signing and stamping. Please do this quickly. 8. The application must be finished and accepted one week before deadline or you will be removed from the application.

Documents you need Certificate of registration (firmaattest) VAT/tax evidence (skatteattest) Banking evidence Annual Report - Economy 2016 (årsrapport for virksomheten) CV for each participant Confirmation from your government representative The application documents (budget, what and why are you going to do, etc.)

After the application is sent Make a detail budget Monthly meetings with all the consortia members (net meeting) No f2f meeting will be held Monthly status report from each consortia member Help other consortia members when they have difficulties when developing solutions Be an active part in the test of etender documents with Access Point both within the consortia and when testing with other consortia members Difi will facilitate the CEF Call All communication between INEA and the consortia is done by Difi Your contact in Difi is Jens.Aabol@Difi.no The payment from INEA is sent to Difi. Difi will do the settlement between the consortia members according to the amount in the application (that has been documented)

Difi responsibility Difi can not be held responsible if the application is not granted All communication between INEA and the consortia is done by Difi The payment are sent to Difi who will do the settlement between the consortia members Difi will develop the guides for EHF Difi will develop the validator for EHF Difi will coordinate EHF with PEPPOL BIS when it is ready Difi will develop the Oxalis multi-protocol

Questions