e-Evidence Digital Exchange System (eEDES)...2019/09/04 · e-Evidence Digital Exchange System...
Transcript of e-Evidence Digital Exchange System (eEDES)...2019/09/04 · e-Evidence Digital Exchange System...
e-Evidence Digital Exchange System (eEDES)
Djamila BEN MILOUD – Project Manager
Toma MILIEKAITE – Business Manger
Cristian NICOLAU - Head of Unit: e-Justice, IT and Document Management
e-Evidence Exchange System (eEDES)
• Council Conclusion June 9, 2016;• EIO instruments (Directive 2014/41/EU) EN:
• MLA instruments;• Secure online portal for electronic requests and
responses concerning e-evidence;• Expert Group: 1 legal+1IT 14 meetings
CDB Criminal
Portugal(data centre)
Austria(data centre)
Austria:- competent authorities- rules for determining
competence
Sweden:- competent authorities- rules for determining
competence
Any Member State
Vienna
Graz
Innsbruck
LisbonProsecutor
European Commission(Secure Hosting Service)
AS4
CDB Criminal
Portugal(data centre)
Austria(data centre)
Austria:- competent authorities- rules for determining
competence
Sweden:- competent authorities- rules for determining
competence
Any Member State
Vienna
Graz
Innsbruck
LisbonProsecutor
European Commission(Secure Hosting Service)
What is the competent authority?
AS4
CDB Criminal
Portugal(data centre)
Austria(data centre)
Austria:- competent authorities- rules for determining
competence
Sweden:- competent authorities- rules for determining
competence
Any Member State
Vienna
Graz
Innsbruck
LisbonProsecutor
European Commission(Secure Hosting Service)
+ Vienna+
AS4
CDB Criminal
Portugal(data centre)
Austria(data centre)
Austria:- competent authorities- rules for determining
competence
Sweden:- competent authorities- rules for determining
competence
Any Member State
Vienna
Graz
Innsbruck
LisbonProsecutor
European Commission(Secure Hosting Service)
AS4
CDB Criminal
Portugal(data centre)
Austria(data centre)
Austria:- competent authorities- rules for determining
competence
Sweden:- competent authorities- rules for determining
competence
Any Member State
Vienna
Graz
Innsbruck
LisbonProsecutor
European Commission(Secure Hosting Service)
AS4
eEvidence Digital Exchange System Reference Implementation
eEDES RI next steps
• Testing/Stabilzing Version 1.0 of the portal: ongoing;
• Deployment package preparation;
• Deployment package distribution (Dec. 2019);
• Real User testing/feedback (Florence, Hague);
• DEMO Multilingual RI open for testing/training(Dec.
2019).
Roll-Out Actions
• Organisational• Technical• Testing• Deployment• Training• Operations• After-care
Actions for DG JUST•Support Services in Place (Level 1 and 2 helpdesk);
•Set up of a Confluence Space and give access to MS
•Certificates Acquisition via the Commission Services;
•Finalize RI Manuals and Training Materials:•Installation
•Administration
•User manuals;
Nov 2019
Oct 2019
Actions for DG JUST• Provide “Train the Trainer Sessions”
(business);
• Continuous testing for software and documentation with EXEC;
• Go-live checklist creation;
• Set up a multilingual DEMO/Training environment;
• Distribute the “production ready” RI software;
• Continuous RI enrolment: 2 MS / week
Dec 2019
Actions for DG JUST
• Continue Providing “Train the Trainer Sessions” (business);
• (Support) Continuous RI enrolment: 2 MS / week;
• Progressive GO LIVE!
• Support LIVE/PRODUCTION operation.
2020
Sli.do #L288
National Actions Plan• Prepare and submit the National Project
Plans to DG JUST (end October);
• Prepare the National Administration Manuals (Access points, user groups, authorities…);
• Validate the CDB-Criminal data;
• Submit proposals for grants (DDL 14/11/2019);
Nov 2019
Oct 2019
Sli.do #L288
National Actions Plan• RI installation (test, training, demo);• pModes generation and upload;• Test-bed preparation and configuration;• Creation of the National Structures
(Trainers, technical team for operations, local helpdesk, user management authority…);
• Go-Live Checklist Validation• Go Live!
2020
Dec2019
Sli.do #L288
Number Activity Foreseen Start date
Foreseen End date
Actual Start date
Actual End date Comments
Team allocated for e-Evidence ProjectLegal, Administrative and Procedural Provisions in placeNational helpdesk operationalProduce National Administration Manual (AP, User groups,Authorities…)Create the national structures: (trainers, technical team, usermanagement authority…)CDB Criminal Data validationPrepare Checklist for readiness
Infrastructure readiness:Test environmentProduction EnvironmentTraining Environment
Deployment ActivitiesConfiguration ActivitiesLocal Testing of e-Evidence SoftwareRemote Testing of e-Evidence SoftwareInteroperability Testing of e-Evidence Software
Deployment of the e-Evidence software in the production environment
Validate the deployment with smoke testing with other Member States
Provide Training to the technical users (who will operate the e-EvidencePortal)Provide Training to the end-users
Creation of users and user rolesGo-Live Date with EIO/MLA Exchanges
e-Evidence DES National Project Plan (NPP) AT - Austria
Activities
Infrastructure Set Up for e-Evidence DES
e-Evidence Digital Exchange System Deployment and Operation
Organisational Activities
NPP Updated on:
Foreseen dates meaning the provisional dates for the activity.Actual dates meaning the real dates which the activity is executed.ISO Country Code - Dropdown List with the country codes.NPP Update - Date and Author's name when the NPP was updated.
Legend
e-Evidence Digital Exchange System Rollout (all environments)
Training Activities
National Plan Consolidation
• NPP distributed officially to MoJ(Comm) – SEP;
• NPP receive replies end OCT-mid Nov;
• Consolidate plans Nov-Dec 2019;
• Review plans EG meeting Dec 2019.
Oct2019
Sep2019
Nov2019
Dec2019 Sli.do #L288
Expected Go Live – Sli.do #7336
• When do you think that the infrastructure will be in place at national level?
• What is your country's expected go live date?
• What support should the European Commission provide you to start operating the system?
Service Desk
e-Evidence Project 25
• Central Service Desk for e-Evidence DES• SPOC for all services related to e-Evidence DES
• e-Evidence DES Portal (incl. Reference Implementation)
• e-CODEX infrastructure for e-Evidence• editable PDF forms• CDB Criminal• Configuration Management Tool
• End-to-end handling of incidents and requests• Level 1 and Level 2 support• Coordination of resolution with other stakeholders
where necessary
Member Statee-Evidence contact
points
Service Desk
e-Evidence Project 26
e-Evidence Service Desk
e-Evidence Maintenance
TeamDG JUST DIGIT EXEC / Me-
CODEX
Service Desk
• Support to user community• from 8am to 6pm CET on week days• in English• limited to persons registered in Service
Desk contact list • Max 10 persons per MS• Contact person needed in each Member State to maintain the list 27
Service Desk
• e-Evidence Service Portal to share information•documentation•change and release information•plannings•FAQ
e-Evidence Project 28
Support for Deployment
• Deployment plan• Elaboration and maintenance of the plan• Coordination with Member States Contact person needed in each Member State
� Alignment between overall deployment plan and National plans� Status report
• Update and distribution of the common configuration files • Management of certificates whenever appropriate and needed
e-Evidence Project 29
Support for deployment
• Remote or on-site technical support can be requested for the following topics related to deployments:• Setup test and operation environment• Technical advice• Diagnose and address technical issues
• Note: MS remain fully responsible for the deployment of the application in their infrastructure.
e-Evidence Project 30
Conformance Testing
• Coordination, monitoring, support, and reporting on Member States' Conformance Tests• Set-up, configuration and management of the central Test Bed tool• Support for the usage of the test bed• Follow-up of conformance tests with each MS Contact person needed in each Member State
• Analyse test results;• Provide assistance in diagnosing the reported errors;• Analyse possible impact of MS errors and/or deviations on production;• Co-ordination via conference calls where needed.
e-Evidence Project 31
Conformance Testing
• Important artefacts• Deployment plan
includes Conformance Test organisation
• Conformance Test Protocol (CTP)Describes all the tests required to prove National application’s conformity to e-Evidence international
interface specifications
• Test Reference Package (TRP)Contains the business input uploaded to the test bed for conformance tests Includes the reference data, test message templates, country specific instantiation data, test cases, rules
and conditions.
e-Evidence Project 32
Conformance Testing
• Conformance Test steps:• Local Conformance Test (mode 1):
Local or unit testing by the MS of their deployment before moving to Mode2;
• Conformance Test (mode 2): The Member State tests its compliance against the Commission's Conformance Test environment;
• International Conformance Test (mode 3): The Member State tests its conformance against other voluntary Member States, if required;The Commission business sector defines in close collaboration with the Member States whether this third
test is optional or mandatory.
e-Evidence Project 33
Ad-hoc Testing
• On-demand test service for the integration of MS e-Evidence Portal• Punctual ad-hoc test with test bed
o System connectivity (infrastructure connectivity) o Interface communicationo End-to-end business scenario
• Via request to Service Desk
e-Evidence Project 34
Events
• CATS (Sep. 19);
• User Tests e2e (Sep. 19);
• Prosecutor’s General Assembly
(EUROJUST) (Oct. 19);
• EXEC tests (Dec. 19)
Oct2019
Sep2019
Nov2019
Dec2019
Recap and Next Actions
• National Project Plans (Nov.-Dec. 19);
• RI 1.0 distributed to MS (Dec. 19);
• RI Multilingual Demo/Training (Dec. 19);
• Start Roll-out (Dec. 19);
• Go live! (Dec. 19 onwards).
Oct2019
Sep2019
Nov2019
Dec2019 Sli.do #L288
Expected Go Live – Sli.do #7336
• When do you think that the infrastructure will be in place at national level?
• What is your country's expected go live date?
• What support should the European Commission provide you to start operating the system?
Me-CODEX Project
Cross-border
projects
Supporting Projects• EVIDENCE2e-CODEX;• EXEC;• MeCodex.• e-Codex national infrastructure
adaptations and development (ES);• e-Evidence platform Development (LV);• e-Evidence Digital Exchange System
Integration to Estonian Prosecutor's Information System (EE);
• BE-Evidence (BE);• PT e-Evidence (PT);• eTodiste (FI);
European Commission
Member States
National Projects
EJN, EJTN,
EUROJUSTCEPOL
Grants Information
• CEF-TC-2019-2: European e-Justice 14 Nov. 2019• https://ec.europa.eu/inea/en/connecting-europe-facility/cef-telecom/apply-
funding/2019-ejustice
• Info session (Q/A session):• https://ec.europa.eu/inea/en/news-events/events/2019-2-cef-telecom-call-virtual-
info-day
• Generic Services:• Hook-up;• Operation;• Maintenance.
E-evidence Digital Exchange System Integration to Estonian Prosecutor's Information System
EstoniaCRIS
Objectives/Expected Output
Prosecutor
MS
X‐road
E‐Codex
Courts’ ISPolice’ ISLegal Aid’ IS
Duration and RoadmapProject duration – 02.10.2019 – 01.10.2021Project roadmap:
02.10.19‐01.12.19
• Preliminary business analysis for development
04.12.19‐28.06.21
• Detailed technical analysis and development of the system
31.06.21‐01.10.21
• Final testing
Brussels - 16-09-2019
e-Evidence Digital Exchange System meeting
(SPAIN)
2017-ES-IA-0035 e-Codex national infraestructure adaptations and development
2. PROJECT DESCRIPTION & OBJECTIVES
Name: e-Codex national infraestructure adaptations and developmentParticipants: SpainObjectives: Preparing the Spanish infrastructure to be ready for e-Codex exchanges:
Allowing the exchange of Mutual Legal Assistance (MLA) and European Investigation Orders (EIO) with European judges and prosecutors (*), through the e-CODEX infrastructure (Gateway and Connector) and transport infrastructure LexNET. The first user community will be the International Prosecutor Cooperation
Office, using their backend system CJI.
(*) under the Spanish Law 3/2018 of 11 June about the mutual judicial international cooperation, transposition of the Directive 2014/41/EU of the European Parliament and of the Council of 3 April 2014 regarding the European Investigation Order in criminal matters
2018 20202019Adaptation of Spanish infrastructure and CJIAdaptation of Spanish infrastructure and CJI
Set up of national Access PointsSet up of national Access Points
TestingTesting
NOV2018NOV2018
StartStart SEP2019
RI Rollout PreparationRI Rollout Preparation Rollout of the RIRollout of the RI
Future: other Case Management SystemsFuture: other Case Management Systems
RI
Compliance to RI PortalCompliance to RI PortalNA*
Rollout of the MLA / EIORollout of the MLA / EIO
*NA = e-Codex nationalinfraestructure adaptationsand development
2. TIMELINE & ROLL-OUT STRATEGY
specific training activity is foreseen for theCentral PPO on the new functionality of theirCJI Backend system
In case a usercommunity demandsthe use of the portal
BE‐Evidence
Activities dans BE‐Evidence
Task 2.1 National analysis on legal, semantic and technical aspects relevant for establishing an e‐CODEX connection
Task 2.2 Developing a detailed plan for implementing and setting up the e‐CODEX components (including a technical scenario)
• Setup of 3 e‐Codex environments on new Justice 24/7 infrastructure (Debian, Tomcat, Oracle DB)
• DEV (development) : single node• ACC (acceptance) : two nodes in High Availability mode• PRD (production) : two nodes in High Availability mode
• Developing a generic interface on the Justice Enterprise Service Bus as interface between National applications and the e‐Codex stack.
• Integration of the e‐Codex stack in the Justice Logging and auditing infrastructure.
Task 2.3 E‐Codex testing activities
• Create detailed test scenario and scripts for integration testing leveraging the EU Central Testing platform.
• Connection testing with European Central Testing Platform
• Functional testing with European Central Testing Platform
• Connection testing with peer Member State
• Functional testing with peer Member State
Activities dans BE‐Evidence
Task 3.1 National analysis on legal, semantic and technical aspects
• Workshops will be held with the business users at the federal prosecution office to gather legal and user requirements and map the local semantic and business process requirements with the standard EU interface exposed by the e‐Codex/e‐Evidence solution.
Task 3.2.Developing a detailed plan for setting up the e‐Evidence components
• This will include the definition of the system architecture (redundance, security, etc) as well as the definition of the required application configuration to be implemented in step 3.4
Task 3.3 Testing activities
• Create and execute test scenarios and scripts, using the central testing platform
Task 3.4 Roll out, and configuration and administration of the e‐Evidence RI
• Bring the e‐Evidence installation onto the production environment, configure and administer the application with required settings (user management, access management , forms etc…)
FormationTask 4.1 Define necessary material for communication and marketing to the users
• This task will propose a communication plan which will present what needs to be communicated, why, to whom, the means that will be used to reach our target population and the communication frequency.
Task 4.2 Creation of the material
• A training plan will be provided in order to highlight userswho will need to be trained.
• The option retained for training support is that of web‐based, self‐service training material that will be created by the SPF Justice training unit using material provided by the project team. This will ensure that training requirements can be met in a more flexible manner
Task 4.3 Organize meetings with each of the prosecution offices for them to know the system.
Roadmap
Starting Date : 01/06/2019E‐Codex Testing from : 01/10/2019E‐Codex Rollout : 31/01/2020E‐Evidence RI Testing from : 01/12/2019E‐Evidence RI Rollout : 31/04/2020Training : Q2/2020Closing date : 30/11/2020
e‐EvidenceImplementation in
Latvia
MoJ & CA2019
1) Legal and TechnicalAnalysis of currentsituation – draft laws ifnecessary
2) Technical Implementation– instalation of e‐CODEX and e‐Evidence system
3) Acceptance testing and Training of 150 practitioners + video guide
Mainactivities ofProject
Go‐LIVE
Before summer break 2020
E‐Evidence project ‐ Finland
e‐Evidence expert meeting, Brussels16.09.2019
Objectives ofthe e‐Evidence project
• The creation of the e‐CODEX technical platform (connector and gateway)
• The installation of the e‐Evidence Reference Implementation
• Follow‐up project to be started in the autumn 2019• Taking of Evidence / Service of Documents• Financial Penalties• European Arrest Warrant• transfer of the iSupport data exchange to the same platform
Timeline ofthe e‐Evidence project
• Finalising the e‐CODEX technical platform 9‐10/2019• The installation of the e‐Evidence Reference Implementation 11‐12/2019
Expected go live of exchanges• December 2019 ‐ January 2020
PTe-Evidence
Meeting on e-Evidence Digital Exchange System
September 16,2019
Prosecutor General’sOffice
| PT e-Evidence -OBJECTIVES
Is a project that aimsto:
- Connect Portuguese competent authorities to the European e-Evidence Exchange System,
enabling to exchange EIO /MLA with European judges and prosecutors through features
incorporated into theSIC-MP, thePublicProsecutor's casemanagementsystem.
- Connect forensic experts from the Judicial Police (PJ) with the PGO system for securely
exchangingEIO /MLAevidence electronically.
- Provide the PGO system with storage capacity specifically dedicated to securely keeping EIO
/MLA digital evidenceavailable.
This project is support under CEF Telecom programme and involve 4 entities (from Portugal):1. PGO –Prosecutor General’s Office / Coordinator of theproject2. PJ –Portuguese Criminal Police3. PDM&FC –IT company4. Linkare –IT company
Budget: €479.674,00Grant (75%): €359.755,00
| PT e-Evidence - Main ACTIVITIES and MILESTONES
Start:15/11/2019
End: 12/11/2021
| PT e-Evidence -Timeline
1. EXEC and E2E projects ends
2. Access Pointe-CODEX
3. Reference ImplementationPortal
NOV21
Adaptation of SIC-MP
Connect PJ toSIC-MP
Training
go-live EIOexchange nationalsystem
backend
NOV19 PT e-EvidenceProject
2019 2020 2021
First phaseSIC-MP
Thanks for your attention
EVIDENCE2E-CODEX: LINKING EVIDENCE INTO E-CODEX FOR EIO AND MLA PROCEDURES
IN EUROPE
Maria Angela Biasiotti, Fabrizio TurchiIGSG-CNR
Brussels 16 September 2019
EVIDENCE2e-CODEX Goals
63
Pre-piloting the EVIDENCE proposal and achievements together and with e-CODEX for the specific purposes of allowing the secure and trusted exchange of digital evidence among EU MS in the EIO and MLA context
EVIDENCE2e-Codex project |e-Evidence WP Meeting | Brussels, 16th of September 2019
Partner Country
P1. CNR ItalyP2. RUG NetherlandsP3. CETIC BelgiumP4. ELF NetherlandsP5. LIF BulgariaP6. INTERPOL FranceP7. K&I ItalyP8. MoJ-NL NetherlandsP9. MoJ-DE Germany
Partner Country
P10. MoJ-IT ItalyP11. LIBRe BulgariaP12. BMJ-AT AustriaP13. MoJ-FR FranceP14. MoJ-PT PortugalP15. UNI-THESS
Greece
P16. UOM MaltaP17. UNIL SwitzerlandP18. UNI-WIE AustriaP19. CEHJ FranceP20. MoJ-ES
P21. HCCH The Hague Conference on Private International Law NL 64
EVIDENCE2e-CODEX Partners
EVIDENCE2e-Codex project |e-Evidence WP Meeting | Brussels, 16th of September 2019
1. Analyze Legal issues dealing with the implementation of EIO in MSs (highlighting obstacles and barriers still in place) including data protection implications (WP2)
2. Developing a formal language and a tailored made Application (EESP) for the exchange of electronic evidence by ICTS under EIO. (WP3)
Providing stakeholders with ‘ready for use’ information on EIO, E.E. and e-CODEX and Cross fertilization among different stakeholders (WP4)
65EVIDENCE2e-Codex project |e-Evidence WP Meeting | Brussels, 16th of September 2019
EVIDENCE2e-CODEX Main activities
supports the UCO/CASE language, standard for the representation of the Evidence Package meta data
Is a web application for managing the Evidence Package (EP)
Final aim is to prepare the EP and facilitate its exchange through the Reference Implementation and e-Codex.
66
EVIDENCE2e-CODEX Evidence Exchange Standard Package (EESP) application
EVIDENCE2e-Codex project |e-Evidence WP Meeting | Brussels, 16th of September 2019
Thank you!
For more information:www.evidence2e-codex.eu
EXEC ‐ Electronic Xchange of e‐Evidences with e‐CODEX
e‐Evidence Expert Group16 September 2019Brussels
This project was funded by the European Union’s Justice Programme (2014‐2020).
EXEC ObjectivesSetup of the
• Gateway
• Connector
• e‐Evidence Reference Implementation (created by the European Commission)
in order to
enable the participating Member States to exchange European InvestigationOrders (EIO) and related e‐Evidence fully electronically through the e‐Evidence Reference Implementation provided by the European Commissionor existing directly connected national back end solutions.
EXEC
21 EXEC Partners
EXEC
Supreme Judicial Council BulgariaMINISTRY OF JUSTICE OF THE CZECH REPUBLIC Czech RepublicJUSTIZMINISTERIUM DES LANDES NORDRHEIN‐WESTFALEN GermanyARISTOTELIO PANEPISTIMIO THESSALONIKIS GreeceMinistry of Justice GreeceMinisterio de la justicia SpainMINISTERE DE LA JUSTICE FranceMINISTARSTVO PRAVOSUDA CroatiaCONSIGLIO NAZIONALE DELLE RICERCHE ItalyMINISTERO DELLA GIUSTIZIA ItalyLietuvos Respublikos generaline prokuratura LithuaniaMinistère de la Justice LuxembourgRIJKSUNIVERSITEIT GRONINGEN NetherlandsMINISTERIE VAN VEILIGHEID EN JUSTITIE NetherlandsBundesministerium für Verfassung, Reform, Deregulierung und Justiz AustriaMinistério da Justiça PortugalZENTRALE STELLE FÜR INFORMATIONSTECHNIK IM SICHERHEITSBEREICH Germany Associated PartnerCHAMBRE EUROPÉENNE DES HUISSIERS DE JUSTICE EuropeCOURT ADMINISTRATION OF LATVIA Latvia Associated PartnerBAYERISCHES STAATSMINISTERIUM DER JUSTIZ Germany Associated PartnerMINISTRY OF JUSTICE AND PUBLIC ORDER OF THE REPUBLIC OF CYPRUS Cyprus Associated Partner
Timeplan
EXEC
Current State of Play 1/2
• WP 2: Identify Legal and Technical Obstacles• Feasibility Report is done. Results and actions will be
discussed in a workshop on 25/26 September 2019, Florence
• WP 3: Setup of Access Points• Workshops incl. training material are done• All Access Points are setup and at least ready for testing
EXEC
Current State of Play 2/2
• WP 4: Testing• Test strategy and test plan done• Testing in progress, see next slide
• WP 5: Rollout of the solution• Rollout plan in progress. Results and actions will be discussed
in a workshop on 2 October 2019, Vienna• Final event: 21/22 January 2020, Brussels – together with
EVIDENCE2e‐CODEX and the EC ‐> Save the date!
EXEC
EXEC ‐ State of Play Partners
Member State Country ISO Code
Domibus Gatewayset up
Domibus Connectorset up
RI PoCsetup
Crossborder Exchange with CTP successful
CrossborderExchange
with other MS successful
Comment
Austria AT DONE DONE DONE DONE DONE EXEC Partner
Bulgaria BG DONE DONE DONE DONE DONE EXEC Partner
Croatia HR DONE DONE DONE DONE ONGOING EXEC Partner
Cyprus CY DONE EXEC Associate Partner
Czech Republic CZ DONE DONE DONE DONE DONE EXEC Partner
France FR DONE DONE DONE ONGOING EXEC Partner
Germany DE DONE DONE DONE DONE DONE EXEC Partner
Greece GR DONE DONE DONE ONGOING EXEC Partner
Italy IT DONE DONE DONE DONE ONGOING EXEC Partner
Latvia LV EXEC Associate Partner
Lithuania LT DONE DONE DONE ONGOING EXEC Partner
Luxembourg LU DONE DONE DONE DONE ONGOING EXEC Partner
Netherlands NL DONE (axway) DONE n/a ONGOING EXEC Partner
Portugal PT DONE DONE DONE ONGOING EXEC Partner
Spain ES DONE DONE DONE DONE DONE EXEC Partner
Lessons Learned so far
• Firewall configuration• ‐> Test early!
• Certificate handling• ‐> Certificate issuance by CEF?
• Close communication essential• Frequent telephone conferences.
EXEC
Next steps
• Switch to 2‐way SSL• Install RI v0.1 ‐> used for tests of e‐CODEX installation• Obtain certificates (CEF PKI‐Service?)• Sign Circle of Trust Agreement• Planning of technical & organisational rollout
• CEF‐TC‐2019‐2 Call – 14 November 2019• Project proposal for national integration of RI• Project proposal for delivering data to Criminal Court DB• Interest in EXEC 2 for MS not yet connected ?
EXEC
Thank you very much for your participation!
• Sli.do #[email protected]
eEDES RI 1.1
• Judicial authorities (JA) from MS only (in 1. phase);
• secure platform/infrastructure (portal using a 2-factors
authentication);
• to send securely (encrypted) a fully electronic EIO/MLA or
signed/scanned documents to another JA in another MS with
possibility to reply with attachments;
eEDES RI 1.1
• Possibility to forward requests to another competent authority in the
same executing MS;
• transfer of electronic evidence via the same secure channel;
• Interface and forms in all EU official languages;
• Clear and user-friendly dashboard;
eEDES RI 1.1• Court Database (CDB) as support to identify and verify the competent
issuing and executing authorities; automatically filled in in the
corresponding section;
• all communication and exchanges linked to given cases accessible from one
place in the portal;
• tracking of all exchanged messages with timestamp and delivery status;
• printable for the file if needed;
eEDES RI 1.1• tooltips to help to fill in the EIO/MLA forms;
• overview of cases and related requests;
• clear status indication of actions related to a case including
overdue task;
• different search functions (such as by case number, date, MS, etc.)
9/30/2019
83
CDB Criminal
European Commission(Secure Hosting Service)
Germany:- competent authorities- rules for determining
competence
Sweden:- competent authorities- rules for determining
competence
…
Secure access (HTTPS)
Court Database
Designatedauthority(ies)
(France)
Designatedauthority(ies)
(Czech Republic)
Designatedauthority(ies)
(Sweden)
Secure access (HTTPS)
Secure access (HTTPS)
CDB Criminal
European Commission(Secure Hosting Service)
Germany:- competent authorities- rules for determining
competence
Sweden:- competent authorities- rules for determining
competence
…
Secure access (HTTPS)
Designatedauthority(ies)
(France)
Designatedauthority(ies)
(Czech Republic)
Designatedauthority(ies)
(Sweden)
Secure access (HTTPS)
Secure access (HTTPS)
Court Database
CDB Criminal
European Commission(Secure Hosting Service)
Germany:- competent authorities- rules for determining
competence
Sweden:- competent authorities- rules for determining
competence
…
Secure access (HTTPS)
Designatedauthority(ies)
(France)
Designatedauthority(ies)
(Czech Republic)
Designatedauthority(ies)
(Sweden)
Secure access (HTTPS)
Secure access (HTTPS)
Court Database