1. Frank Schipplick Work Package Coordinator WP1 - eSignatures

2. High level vision of WP1  The aim is to provide cross European interoperability of electronic signatures, particular regarding the verification process. 3 steps to reach this goal.  Definition of a trust model for pan-european eProcurement processes to overcome the legal obstacles.  Specify the way of signing eProcurement data to enable cross-border eProcurement.  Provision of solutions for verification of signatures for awarding entities

3. WP 1 Participants Consortium Members WP 1 Members CNIPA (ITA) DGME (France) DIFI/DNV (NOR) City of Bremen/bos (GER)

4. Tasks of WP 1  Task 1: The design phase – specification – Analysing the legal, organizational and technical situation of the use of eSignatures in the field of E-Procurement in selected European countries. – Revision of existing studies on eSignature. – Defining a technical specification.  Task 2: The construction phase – implementation – Building up a validation authority  Task 3: The operational phase – pilot – Running the pilot

5. NoTitle Delivery Date D1.1 Specification of eSignature solution for eProcurement /Trust model Month 10 D1.2 Transnational verification solutions – Prototype documentation Month 24 D1.3 Demonstrator and revised specification for eSignature solution for eProcurement / trust model Month 30 D1.4 Pilot report and recommendations for European Roll-Out Month 36 Deliverables of WP 1

6. Final outcome of WP 1  Certificate Validation Service for Europe – Provide the receiver of signed documents a service to verify the signatures whereas the sender can sign these documents with his national signature solutions. – Integration of the validation service in some national applications  Demonstrator Software – Installation of validation authorities – Provision of client solutions (probably not in all languages) – Provision of APIs for the application integration  The validation service is application independent. – It can be used for every business process with signed documents. – Not only in the procurement segment.

7. Objective of the WP1 pilot  Allow the use of foreign eID signatures in eprocurement processes – Assumption 1: a national eProcurement application is able to verify signatures compliant to national laws – Assumption 2: If the existing eProcurement application can verify a foreign eID signature itself, the application does not have to use the WP1 solution  Proof of ability of the certificate validation infrastructure

8. Architecture of the pilot Direct access, if foreign CA known

9. Company ACompany B Country A Country B Operator 1 Company C Operator 2 PEDRI Access point, national Company F Operator 3 Access point 3, Operator 3 Company E PEDRI Registry Registry A Invoice Access point, VAN 1 Access point 2, Operator 2 Registry B Transport properties Secure Reliable Profile properties Transport + QoS Registry C Public agency D Security Token Server PEDRI Architecture

10. Direct access, if foreign CA known System boundaries between WP1 and WP8 Validation of certificates by sender‘s STS before sending. The role VA and STS can be merged in one component. Recipient can (re-)validate sender‘s certificates.

11. Pilot pre-requirements  All actors sign locally with own signature creation software – Signing in user interface of platform is optional – Platform/application cannot support all possible cards  Platform/application must support a download functionality for forms/documents that need to be signed  Platform must offer an upload functionality to submit signed documents and – A clever upload functionality with encryption (optional)

12. Pilot Member States Norway, Finland, Denmark, Germany, Austria, France, Italy

13. Implementation phase  Start of implementation work (adaptation of national infrastructures) in February 2009 after end of specification phase.  Detailed implementation plan has to be worked out and agreed with pilot partners. This is in progress. Actually 5 phases are defined:  Phase 1: Lab-Test, no WP 8 outcomes needed.  Phase 2: Lab-Test, integration phase with PEDRI.  Phase 3: Beta-Test, close cooperation with WP 8.  Phase 4: System scale up phase, close cooperation with WP 8.  Phase 5: Rollout phase.  End of implementation phase (phase 4): April 2010