Visit www.invinet.org

CEN BII3 Amsterdam (II)

5th BII Open Plenary in Amsterdam

The meeting has been hosted by PIANOo, the Dutch Public Procurement Expertise Center. Mr Wouter Stolwijk did the opening plenary keynote speech.

Jostein Fromyr welcomed the 43 registered participants. Participants in the Workshop are from 29 different organizations belonging to 15 different countries. Jostein explained that editor selection was finalized and that editors have been appointed and the contracts accepted by the EC. Afterwards, Jaap van der Marel from NEN went through the minutes from Brussels 4th meeting. Jostein continued with a brief summary of the Architecture Team meeting done on Tuesday. You can see some notes here.

After the administrative introduction, Mr. Antonio Conte from DG ENTR made a teleconference speech on the status and ongoing proposal about the draft standardization request in the domain of e-invoicing. He explained the process and its deadlines. It was also explained which type of organization within CEN will do the work: It will be done by a Technical Committee or a Project Committee, not decided yet. These committees within CEN are composed by members engaged from National Standardization organizations. Each National Standardization organization can create a mirror committee that is in charge of nominating the expert(s). Experts participate on behalf of national committees mirroring the CEN TC. A Workshop like CEN BII can liaise with a TC but has no voting rights.

There were some concerns based on the complexity of things that will have to be solved in this TC. The experience in CEN BII has shown that there will be a significant number of very complicated and detailed questions, and to get consensus around them will become a tricky thing.

Following Mr. Conte, Marc Cristopher from DG MARKT made a presentation on the new Directive on e-invoicing for public procurement. He explained that trilogues were completed on 21st of January (Council, Parliament and the Commission). The approval and adoption is on its way. During the approval process, there have been some relevant modifications:

  1. The list of syntaxes has been limited
  2. Syntax bindings – as we have done in BII – will be provided
  3. There will also be a recommendations on transmission interoperability

There are also additional high level requirements such as the compliance with provisions of VAT Directive, the compatibility with international standards or the possibility to use the same European Norm in B2B. Specially interesting the requirement on testing of the standard. I have already said something about this here:

Regarding the deadline,  the Commission has to publish the new Directive within next 36 months, and there is a global implementation (entry into force) period of 54 months after publication, but linked to the availability of the standard.

Marc Cristopher also explained the challenges on the deployment of this new Directive, being the most important the timeline (only 36 months to finalise all standardisation deliverables), the decision on how to do testing (as an idea, CEN GITB3 deliverables could be used for  that purpose).

Last item on Marc’s presentation was about the next steps with the standardisation request to CEN by Q3 2014 and the publication due by Q3 2017 and final implementation during end of 2018 – beginning of 2019.

One of the questions to Marc was whether countries should wait until 2018-2019 to start doing something. He suggested that countries should not wait as what is currently available would not have to be dramatically amended.

To the question whether countries implementing CEN BII standards are safe, he said he would not think the final outcome for three years of the EN production process would be much different to the current CEN BII specifications.

After these interesting presentations, there was an Open Space session. The following topics and main ideas were dropped during the Open Space:

  • BII reference model
    • We have to allow the reuse of business terms
    • We have to link to international work
    • We need business term naming and description
    • We expect to implement it without breaking compatibility
    • We envisage multilingualism as a key benefit
    • We need it for clarity in definition, to facilitate integration,  show compliance and provide semantic bridge
  • Large Scale strategy implementation
    • The example in Norway and its success were explained
    • e-SENS on-going pilots were also explained
    • There is a need to collect usage statistics
    • Commission should issue a communication encouraging the adoption work of what is available currently in terms of eInvoicing,
  • Internal communication between the task teams
    • Question on how mailing lists should work.  Central administration by the secretariat was suggested
    • Would need to have minutes for f2f and conference calls in an open environment
    • To use collaboration tools to share information in an open and transparent way is needed
    • Need a tracking system because currently is hard to see what has been decided on a document. Use an issue tracking system to make decision visible
  • Conformance
    • New GITB WS was explained
    • We need to provide the means for self-conformance to the community
    • OpenPEPPOL and SFTI provide tools for self-conformance
    • It is important to produce the mapping exercise to certain syntaxes
    • Live demos for end-to-end testing were explained as examples in other sectors
  • Security and eID requirements
    • We need to engage Stork and e-SENS
    • We need common definitions and see what is in and out
    • Protection of metadata in transmission
    • Envelope task to includes security
  • Code list and classification
    • Challenges, do we have the correct code lists with the correct values?
    • There is a need for providing mapping between classification systems. Done by eCAT but not maintained

After the Open Space session, the Open Plenary closed and the group split into Pre-Award and Post-Award for working sessions.

Post a Comment

Your email is never shared. Required fields are marked *

*
*