Governments as innovators and market drivers<br />Mikkel Hippe Brun<br />Technical Director, PEPPOL<br />Chief Consultant,...
Gartner’s Hype Cycle for E-Procurement <br />Peak of Inflated Expectations<br />Plateau of<br />Productivity<br />Trough o...
Imagine 10 years from now...<br />European E-Invoicing is mainstream<br />23 million SME’s have adopted E-Invoicing<br />3...
Imagine 10 years from now...<br />Are these savings on e-invoicing equal to a competitive advantage in 2019?<br />NO<br />...
E-Invoicing Product Life Cycle<br />Maturity<br />E<br />A<br />R<br />L<br />Y<br />G<br />R<br />O<br />W<br />T<br />H<...
Mainstream adoption in 10 years<br />Maturity<br />23 mill.<br />Volume<br />Mainstream adoption<br />Time<br />10 years<b...
Mainstream adoption in 5 years<br />Maturity<br />23 mill.<br />Volume<br />Mainstream adoption<br />Time<br />10 years<br...
Barriers<br /><ul><li>Business requirements vary a lot
No agreed upon businesses processes
Huge difference in business models
High barriers in previous legislation
Member states implement directives differently
Two dominating standards
OASIS UBL and UN/CEFACT CII
Incompatible technical solutions
Shared infrastructure components are missing</li></ul>Org A<br />Org B<br />
Removing barriers<br />Private sector<br />The private sector can provide good solutions<br />E.g. banks, VAN’s and other ...
Removing barriers<br />Public sector<br />Government is the single largest buyer in the EU<br />Approximately 1,800 Billio...
What can be done to the barriers?<br /><ul><li>Mandate minimal business processes
Set-up a well defined governance process
Multilateral peering agreement
Loosen technical requirements
Align MS implementation of directives
Mandate a minimal set of data-elements
Accept syntax mappings will co-exist
Upcoming SlideShare
Loading in …5
×

PEPPOL key note at EXPP-SUMMIT - E-Invoicing and E-Procurement

768 views
615 views

Published on

European Governments as innovators and market drivers

The vision of the Pan-European initiative for the entire procurement process from eTendering to ePayment
Work Packages of the joint project
Experience and Status of the Pilot
Strategy to encompass all EU Member States
Expected impact on private sector

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
768
On SlideShare
0
From Embeds
0
Number of Embeds
6
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

PEPPOL key note at EXPP-SUMMIT - E-Invoicing and E-Procurement

  1. 1. Governments as innovators and market drivers<br />Mikkel Hippe Brun<br />Technical Director, PEPPOL<br />Chief Consultant, Danish IT- and Telecom Agency<br />Email: mhb@itst.dk<br />Twitter: @hippebrun<br />EXPP-SUMMIT 2009<br />Amsterdam<br />September 21st 2009<br />
  2. 2. Gartner’s Hype Cycle for E-Procurement <br />Peak of Inflated Expectations<br />Plateau of<br />Productivity<br />Trough of<br />Disillusionment<br />Innovation<br />Trigger<br />Slope of Enlightenment<br />Procure-to-Pay Solutions<br />Business Process Networks<br />Web-to-Print Applications<br />Extended Purchasing Suites<br />Expectations<br />E-procurement<br />Multienterprise Business Process Platform<br />SaaS Procurement Applications<br />E-Invoicing<br />E-Procurement Network<br />Supplier Portals<br />Time<br />Years to mainstream adoption<br />2 to 5 years<br />less than 2 years<br />5 to 10 years<br />Selected applications from: Hype Cycle for Procurement Applications, Gartner 2009<br />
  3. 3. Imagine 10 years from now...<br />European E-Invoicing is mainstream<br />23 million SME’s have adopted E-Invoicing<br />3 million public sector E-Invoicing endpoints*<br />1-2 billion invoices sent to public sector pr. year*<br />&gt;100,000 work years are being saved in public sector pr. year*<br />How did we get to this situation?<br />What role did governments play?<br />
  4. 4. Imagine 10 years from now...<br />Are these savings on e-invoicing equal to a competitive advantage in 2019?<br />NO<br />Competitive advantage implies that:<br />We reach mainstream adoption ahead of the curve<br />We have gone much further in digitizing the full procurement chain<br />
  5. 5. E-Invoicing Product Life Cycle<br />Maturity<br />E<br />A<br />R<br />L<br />Y<br />G<br />R<br />O<br />W<br />T<br />H<br />L<br />A<br />T<br />E<br />G<br />R<br />O<br />W<br />T<br />H<br />I<br />NTR<br />ODUCTION<br />Volume<br />Mainstream adoption<br />Time<br />
  6. 6. Mainstream adoption in 10 years<br />Maturity<br />23 mill.<br />Volume<br />Mainstream adoption<br />Time<br />10 years<br />8 years<br />5 years<br />
  7. 7. Mainstream adoption in 5 years<br />Maturity<br />23 mill.<br />Volume<br />Mainstream adoption<br />Time<br />10 years<br />4 years<br />5 years<br />
  8. 8. Barriers<br /><ul><li>Business requirements vary a lot
  9. 9. No agreed upon businesses processes
  10. 10. Huge difference in business models
  11. 11. High barriers in previous legislation
  12. 12. Member states implement directives differently
  13. 13. Two dominating standards
  14. 14. OASIS UBL and UN/CEFACT CII
  15. 15. Incompatible technical solutions
  16. 16. Shared infrastructure components are missing</li></ul>Org A<br />Org B<br />
  17. 17. Removing barriers<br />Private sector<br />The private sector can provide good solutions<br />E.g. banks, VAN’s and other Service Providers<br />A competitive environment fosters innovation<br />E-government services are lagging behind<br />Government should stay out<br />“We do not want this creeping public sector standardization”<br />
  18. 18. Removing barriers<br />Public sector<br />Government is the single largest buyer in the EU<br />Approximately 1,800 Billion Euro<br />Government should be a locomotive<br />For standardization <br />For establishment of infrastructure<br />Government should raise the bar<br />E.g. make E-Invoicing mandatory<br />Governments have historically solved large scale market coordination failures<br />E.g. ARPANET, GSM<br />
  19. 19. What can be done to the barriers?<br /><ul><li>Mandate minimal business processes
  20. 20. Set-up a well defined governance process
  21. 21. Multilateral peering agreement
  22. 22. Loosen technical requirements
  23. 23. Align MS implementation of directives
  24. 24. Mandate a minimal set of data-elements
  25. 25. Accept syntax mappings will co-exist
  26. 26. Mandate a transport standard
  27. 27. Establish and fund core infrastructure</li></ul>Org A<br />Org B<br />
  28. 28. Solution?<br />Use Tax Payers Money to<br />Establish the core infrastructure services <br />Secure funding<br />Set up a governance framework<br />Shared by public and private sector<br />Step back<br />Allow the private sector to innovate<br />
  29. 29. The PEPPOL pilot<br />Consortium member<br />Enlarged consortium<br />Reference group member‏<br />Regional node<br />20 beneficiaries from 14 countries<br />Total budget: ~30 M€ <br />Project start up: 1 May 2008, duration 42 months<br />A Pilot A under the CIP program<br />
  30. 30. PEPPOL vision<br />Pan European exchange of business documents between any private company and any EU governmental institutionshould be as easy as sending emails.<br />VCD<br />Catalogue<br />Order<br />Invoice<br />(eSignature and Infrastructure)<br />
  31. 31. Strategy<br />National solutions <br />will not be replaced<br />Will be aligned with common standards<br />Will be linked through a common infrastructure<br />Common EU Standards and Infrastructure<br />
  32. 32. PEPPOL results<br />Transport Infrastructure specifications<br />Operational Infrastructure<br />Since May 2009<br />PEPPOL Demonstrator Client<br />Reference implementation<br />Middleware implementations<br />Off the shelf<br />Initial versions of<br />Peering agreement<br />Governance model<br />
  33. 33. Overall production plan<br />PEPPOL – high level approach<br />6 months<br />extension<br />Sustainable <br />operation of<br />infrastructure <br />Construction phase<br />Pilot phase<br />Design phase<br />Developing Proof of <br />Concept-pilot<br />Group 2 beneficiaries<br />1.<br />Group 1<br />Test Pilot<br />”Dummy data”<br />Group 3<br />2.<br />Production Pilot<br />”Real transactions”<br />3.<br />2010-11-01<br />2011-05-01<br />2011-11-01<br />2009-05-01<br />2008-05-01<br />2010-05-01<br />2009-11-01<br />2012-05-01<br />EC – <br />financed<br />operations<br />and roll-out<br />1st proposal – 18,75 mill € - 8 nations<br />6 months<br />extension<br />1.<br />Enlarg. proposal – 9,15 mill € - 6 nations<br />2.<br />ORG Ref Group – 2,8 mill €<br />18 nations<br />3.<br />4.<br />Start transfering<br />Financing<br />
  34. 34. E-invoicing adoption<br />Every month of delay counts…<br />If politicians just new…<br />23 million SME’s have adopted E-Invoicing<br />3 million public sector E-Invoicing endpoints*<br />1-2 billion invoices sent to public sector pr. year*<br />&gt;100,000 work years are being saved in public sector pr. year*<br />
  35. 35. Call for action<br />Join us<br />Government are implementing<br />&gt;30,000 endpoints from May 1st 2010<br />Sustainable and robust infrastructure<br />Multilateral Legal framework<br />Mix and match<br />We are prepared to listen and change<br />Connect to the PEPPOL Infrastructure<br />
  36. 36. How to get involved<br />Go to Copenhagen October 21st- 23rd<br />Free 3-day conference<br />21st : Executive day<br />22nd : Architecture day<br />23rd : Hands-on day<br />Who should attend?<br />Service providers<br />Public sector organizations<br />ERP & Middleware suppliers<br />Sign up now at http://peppol.eu<br />
  37. 37. http://www.peppol.eu<br />
  38. 38. PEPPOL Infrastructure<br />Interoperabilitythroughcommon<br /><ul><li>Transport standards
  39. 39. Content standards
  40. 40. Business process standards</li></li></ul><li>Did you know?<br />E-Invoicing? years<br />
  41. 41. Timeline until launch<br />Beta Implementation Phase<br />Final Beta Implementation Phase<br />Implementation<br />
  42. 42. PEPPOL Infrastructure<br />SML = Service Metadata Locator (interface)<br />SMP = Service Metadata Publisher (interface)<br />AP = Access Point (Operated by a Service Provider)<br />

×