1 / 20

Electronic Document Interoperability in eGovernment and eBusiness

Electronic Document Interoperability in eGovernment and eBusiness. Tim McGrath eChallenges 2009 Istanbul, October 24 2009. Topics. Electronic document interoperability Painting the “PEPPOL Picture ” PEPPOL Work Packages Timeline. Business requirements vary a lot

charisse-lennox
Download Presentation

Electronic Document Interoperability in eGovernment and eBusiness

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Electronic Document Interoperability in eGovernment and eBusiness Tim McGrath eChallenges 2009 Istanbul, October 24 2009

  2. Topics Electronic document interoperability Painting the “PEPPOL Picture” PEPPOL Work Packages Timeline Pilot Implementation Planning Workshop

  3. Business requirements vary a lot • No agreed upon businesses processes • Huge difference in business models Barriers • High barriers in previous legislation • Member states implement directives differently • Different data models • Different coding systems • No common understanding • Incompatible technical solutions • Shared infrastructure components are missing Org A Org B

  4. Mandate minimal business processes • Set-up a well defined governance process What can be done to the barriers? • Multilateral peering agreement • Loosen technical requirements • Align MS implementation of directives • Define mandatory set of data-elements • Promote common standards • Accept syntax mappings will co-exist • Mandate a transport standard • Establish and fund core infrastructure Org A Org B

  5. PEPPOL vision Pan European exchange of business documents between any private company and any EU governmental institutionshould be as easy as sending emails. VCD Catalogue Order Invoice (eSignature and Transport infrastructure)

  6. The PEPPOL pilot Consortium member Enlarged consortium Reference group member‏ Regional node 20 beneficiaries from 14 countries Total budget: ~30 M€ Project start up: 1 May 2008, duration 42 months A Pilot A under the CIP program

  7. Painting the Big Picture • PEPPOL functions can be divided into three different types: • common infrastructure • document exchanges • services that support interoperability of information content • Only the last two are specific to Public e-Procurement. Pilot Implementation Planning Workshop

  8. As is situation ?

  9. PEPPOL Topology Pilot Implementation Planning Workshop

  10. PEPPOL Transport Infrastructure Pilot Implementation Planning Workshop

  11. Functional Requirements for WP 8 Pilots Application Application Interface START Interface Access point Trusted Access Points START certificates SMP Certificate Server SML Application Access point Application Interface START Interface Trusted SMPs SMP Pilot Implementation Planning Workshop

  12. PEPPOL Signature Verification Pilot Implementation Planning Workshop

  13. Functional Requirements for WP 2 Pilots Application START Interface Transformation Application Interface Validation Other Interface Access point Following VCD Packaging Rules Application Access point START Interface Transformation Pre-VCD Tool Validation Application Interface Other Interface Ontology defined for both/all parties Following VCD Packaging Rules Pilot Implementation Planning Workshop

  14. Functional Requirements for WP 3 Pilots Application START Interface Transformation Application Interface Validation Other Interface Access point Following BII Profiles Application Access point START Interface Transformation Classification Template Service/Tool Validation Application Interface Other Interface Containing CA’s classification template Following BII Profile Pilot Implementation Planning Workshop

  15. Functional Requirements for WP 4 Pilots Application Transformation Application Interface Validation START Interface Access point Following BII Profiles Application Access point Transformation Validation Application Interface START Interface Following BII Profile Pilot Implementation Planning Workshop

  16. Functional Requirements for WP 5 Pilots Application Transformation Application Interface Validation START Interface Access point Following BII Profiles Certification Authority issues signature Application Signature Verification Service Access point Transformation Validation Application Interface START Interface Must trust sender’s certification authority Following BII Profile Pilot Implementation Planning Workshop

  17. PEPPOL Document Exchanges • VCD • VCD Package • BII01 Catalogue Only • BII18 Punch out • BII03 Basic Order Only • BII04 Basic Invoice Only • BII05 Basic Billing • BII06 Basic Procurement • BII07 Simple Procurement • BII19 Advanced Procurement Pilot Implementation Planning Workshop

  18. PEPPOL Services • Pre-VCD mapping • eSignature verification • EcOp Catalogue template tool (pre and post Award) • CA Catalogue template tool (pre and post Award) • Client Application/Web Services (and their libraries) Pilot Implementation Planning Workshop

  19. Overall Timeline Pilot Implementation Planning Workshop

  20. http://www.peppol.eu

More Related