COMMISSION IMPLEMENTING DECISION (EU) 2022/2520
of 20 December 2022
on the specific arrangements for the handover and takeover process of the e-CODEX system
(Text with EEA relevance)
Article 1
Article 2
Article 3
Article 4
ANNEX
Specific arrangements for the handover and takeover process of the e-CODEX system
1.
INTRODUCTION
2.
MAIN MILESTONES
3.
HANDOVER AND TAKEOVER ACTIVITIES
|
Component |
Artefacts |
Handover Support |
|||||||||||||||||||
Items to develop & operate |
Configuration Management Tool – CMT |
Source Code Configuration Database and pModes Documentation Database dump at the initial and final handover stages. |
Documentation Masterclass "CMT" Development and maintenance, installation, configuration, operation and troubleshooting |
|||||||||||||||||||
Central Testing Platform – CTP |
Source Code Documentation Database dump at the initial and final handover stages. |
Documentation Masterclass "CTP" Development and maintenance, installation, configuration, operation and troubleshooting |
||||||||||||||||||||
Repository Server (currently: Nexus) |
Repositories |
Masterclass "development and infrastructure" |
||||||||||||||||||||
Integration Server (currently: Jenkins) |
Integration Items |
|||||||||||||||||||||
Source Code Repository (currently: Gitblit) |
Source Code |
|||||||||||||||||||||
e-CODEX Website |
e-CODEX Website Contents |
Masterclass "e-CODEX Overview" |
||||||||||||||||||||
Items to develop & deliver |
e-CODEX Architecture |
e-CODEX Website Documentation |
Documentation Masterclass "e-CODEX Overview" |
|||||||||||||||||||
Connector Suite |
For each component (Connector, Client, Plugin, Security Library, Utilities, etc.): Source Code Documentation |
Documentation Masterclass "Connector" |
||||||||||||||||||||
Use Case Schemas:
|
Schemas Business Process Model EU e-Justice Core Vocabulary (Access to be granted via the tool “Metadata Workbench”) |
Documentation Masterclass "Schemas" |
||||||||||||||||||||
Other Items |
e-CODEX Tickets |
All tickets including all statuses (for knowledge management purposes) |
Masterclass "Connector" Database dump with all data |
|||||||||||||||||||
e-CODEX Connector Suite Roadmap |
e-CODEX Website |
Masterclass "Connector" |
||||||||||||||||||||
e-CODEX Security Requirements |
Document |
Masterclass "Connector" |
4.
ACTIVITIES
(a)
Training Activities
Title |
Content of the module |
Doc type |
Training Materials Module 1: Masterclass e-CODEX overview |
During this first Masterclass the participants will get a general overview of what e-CODEX entails, including an overview of the basic e-CODEX architecture, the general e-CODEX principles and a short historical overview of how e-CODEX came to be. This module is mainly based on theoretical facts. |
PPT presentation & e-CODEX Syllabus materials |
Training Materials Module 2: Masterclass connector |
During this Masterclass the participants will receive an in-depth explanation on the Connector Suite and its different products/components, including the relation with the gateway. This module consists of a theoretical part, a hands-on training and optional shadowing session(s), including installation, troubleshooting and technical support. |
PPT presentation & e-CODEX Syllabus materials |
Training Materials Module 3: Masterclass Schemas |
During this Masterclass the participants will get familiar with the data schemas developed by the entity managing the e-CODEX system. The focus will also lie on the Metadata Workbench in which the EU e-Justice Core Vocabulary is being administered and to the technique of business process modelling. This module consists of a theoretical part, a hands-on training and optional shadowing sessions(s). |
PPT presentation & e-CODEX Syllabus materials |
Training Materials Module 4: Masterclass CMT |
During this Masterclass the participants will get acquainted with the features and processes of the Configuration Management Tool. The CMT is an online tool to manage the collection of participant data and the distribution of e-CODEX configuration files. This module consists of a theoretical part, a hands-on training and optional shadowing sessions(s). |
PPT presentation & e-CODEX Syllabus materials |
Training Materials Module 5: Masterclass CTP |
During this Masterclass the participants will get familiar with the features and processes of the Central Testing Platform and the testing strategy. The CTP provides a full e-CODEX test environment and a web interface for sending and receiving customisable test messages. This module consists of a theoretical part, a hands-on training and optional shadowing sessions(s). |
PPT presentation & e-CODEX Syllabus materials |
Training Materials Module 6: Masterclass development and infrastructure |
During this Masterclass the participants will further discuss development and infrastructural topics, such as repository server management. This module consists of a theoretical part, a hands-on training and optional shadowing sessions(s). |
PPT presentation & e-CODEX Syllabus materials |
Training Materials Module 7: Debugging masterclass |
During this masterclass the participants will learn about the detection and correction of the potential e-CODEX system bugs and problem resolution, including resolution of support requests. This module consists of a theoretical part, a hands-on training and optional shadowing sessions(s). |
PPT presentation & e-CODEX Syllabus materials |
(b)
Transparency of the handover and takeover process
(c)
Responsibility of eu-LISA and the entity managing the e-CODEX system during the handover and takeover process
5.
CRITERIA FOR A SUCCESSFUL HANDOVER PROCESS
|
Criteria |
Monitoring indicator |
Means of verification |
Deadline |
||||||
1 |
Knowledge transfer of the different components of the e-CODEX system |
All the training sessions held. |
Registration forms completed and training materials delivered to eu-LISA |
By 1 July 2023 |
||||||
2 |
Transfer of all components of the e-CODEX system |
All assets delivered and complete |
Express acknowledgement by eu-LISA |
By 1 July 2023 |
||||||
3 |
Technical stability of the e-CODEX system (all components) |
The 2 latest versions produced by the entity managing the e-CODEX system. |
A stable version of the e-CODEX system, meaning a package that can be deployed in production and that ensures the integrity of all the exchanges taking place on this version. |
By 31 December 2022 |
||||||
4 |
Allocation of sufficient resources within eu-LISA |
The composition of the e-CODEX team (including the technicians to be trained) communicated by eu-LISA to the Commission and the entity managing the e-CODEX system. |
eu-LISA notification to the Commission and the entity managing the e-CODEX system |
By 1 January 2023 |
||||||
5 |
Transfer of intellectual property and usage rights |
The handover of the e-CODEX system and the supporting software products, documentation and other assets listed in the Annex to Regulation (EU) 2022/850 carried out with all intellectual property rights and usage rights. |
|
By the date of joint request by the entity managing the e-CODEX system and eu-LISA to the Commission to declare the successful completion of the handover and takeover process |
||||||
6 |
Resolution of all support requests received by the entity managing the e-CODEX system before eu-LISA takes over the responsibility for the e-CODEX system |
All support requests received by the entity managing the e-CODEX system before eu-LISA takes over the responsibility for it closed or the agreement to take them over acknowledged by eu-LISA |
|
By the date of joint request by the entity managing the e-CODEX system and eu-LISA to the Commission to declare the successful completion of the handover and takeover process |
||||||
7 |
Agreement between the entity managing the e-CODEX system and eu-LISA regarding the successful completion of the handover and takeover process |
Agreement between the entity managing the e-CODEX system and eu-LISA regarding the fulfilment of the criteria for a successful handover process and for the successful completion of that process |
Joint request by the entity managing the e-CODEX system and eu-LISA to the Commission to declare the successful completion of the handover and takeover process |
Between 1 July and 31 December 2023 |
6.
CRITERIA FOR A SUCCESSFUL TAKEOVER PROCESS
Impact level |
Effect on service |
1 |
Service cannot be carried out |
2 |
Corresponding service(s) cannot be performed properly and problem cannot be circumvented. |
3 |
Minor impact on corresponding service(s). |
|
Criterion |
Monitoring indicator |
Means of verification |
Deadline |
||||||||||
1 |
Knowledge transfer of the different components of the e-CODEX system |
eu-LISA participated in all the training sessions that have taken place |
eu-LISA acknowledgement |
By 1 July 2023 |
||||||||||
2 |
Transfer of all components of the e-CODEX system |
All sources are received and the documents are fully completed |
eu-LISA acknowledgement |
By 1 July 2023 |
||||||||||
3 |
Allocation of sufficient resources within eu-LISA |
|
eu-LISA acknowledgement |
By 1 January 2023 |
||||||||||
4 |
Establishment of the e-CODEX Advisory Group |
Establishment of the Advisory Group and meetings during the handover and takeover process held at least every second month, pursuant to Article 12 of Regulation (EU) 2022/850 |
|
Regarding item 1: by 28 February 2023; Regarding item 2: by 30 June 2023. |
||||||||||
5 |
Establishment of the e-CODEX Programme Management Board |
Establishment of the e-CODEX Programme Management Board and meetings during the handover and takeover pursuant to Article 13 of Regulation (EU) 2022/850 |
|
Regarding item 1: by 1 January 2023; Regarding item 2: by 30 June 2023 |
||||||||||
6 |
Transfer of Data |
The transfer of all relevant data including but not limited to, tickets, user credentials, etc. are transferred to eu-LISA either in the form of a database dump or any other format agreed upon between entity managing the e-CODEX system and eu-LISA. |
eu-LISA acknowledgement |
By 1 July 2023 |
||||||||||
7 |
Transfer of the History of all issues |
In the form of a database dump or any other format agreed upon between entity managing the e-CODEX system and eu-LISA. |
eu-LISA acknowledgement |
By 1 July 2023 |
||||||||||
8 |
Transfer of unresolved issues |
In the form of a database dump or any other format agreed upon between entity managing the e-CODEX system and eu-LISA. |
eu-LISA acknowledgement |
By the date of joint request by the entity managing the e-CODEX system and eu-LISA to the Commission to declare the successful completion of the handover and takeover process |
||||||||||
9 |
Transfer of user management, including end-users (access to CMT, CTP…) |
In the form of a database dump or any other format agreed upon between entity managing the e-CODEX system and eu-LISA. |
Credentials communicated, imported in eu-LISA infrastructure and access to the different components is verified by some end-users. |
By 1 July 2023 |
||||||||||
10 |
Takeover of the helpdesk activities:
|
Process is understood and working procedures in place for the takeover team to carry on their daily tasks. |
Ticketing tool available, accessible and all tickets have been transferred to eu-LISA tool (functional mailbox if it exists, support templates, support knowledge base etc.). |
By the date of joint request by the entity managing the e-CODEX system and eu-LISA to the Commission to declare the successful completion of the handover and takeover process |
||||||||||
11 |
Application access credentials |
Transfer of user lists and relevant credentials to eu-LISA taking into account security measures and recommendations for this type of data. |
Users have received their credentials and connection information. |
By 1 July 2023 |
||||||||||
12 |
Takeover of the deployment activities |
Backlog, planning and any relevant documentation or related Requests for Change (RfCs) or tickets; |
Deployment activities are clearly identified and open ones planned for completion |
By 1 July 2023 |
||||||||||
13 |
Takeover of the development activities |
Backlog, planning and any relevant documentation or related RfCs or tickets; |
Development activities are clearly identified and open ones planned for completion |
By 1 July 2023 |
||||||||||
14 |
Takeover of the testing activities |
Backlog, planning and any relevant documentation or related RfCs or tickets; |
Testing activities are clearly identified and open ones planned for completion |
By 1 July 2023 |
||||||||||
15 |
Takeover of the Change and Release Management activities |
Backlog, planning and any relevant RfCs or documentation; |
All open RfCs and release plan are taken over and integrated in the overall project plan |
By 1 July 2023 |
||||||||||
16 |
Availability of the infrastructure and infrastructure management |
All infrastructure requirements received and implemented. All e-CODEX identified assets available and provided to eu-LISA. |
All components are available to all stakeholders as needed. For the development infrastructure, eu-LISA to confirm the setup and the operation. |
By 1 July 2023 |
||||||||||
17 |
Security Management |
All security requirements and recommendation communicated and implemented by eu-LISA. |
The following documentation is to be made available:
eu-LISA should confirm their implementation. |
By 1 July 2023 |
||||||||||
18 |
Communication Plan |
A communication plan needs to be established in order to inform all users and stakeholders about the upcoming change in the service providers and about the new communication channels and procedures. |
Notifications received from eu-LISA by all users and stakeholder before the end of the handover/takeover period to inform them about the new working procedures: credentials, URLs, websites, ticketing tool… |
By 1 July 2023 |
||||||||||
19 |
Final alignment of data |
Final provision of the gap in the assets provided to eu-LISA at the beginning of the handover/takeover process. |
|
On 1 July 2023 |
||||||||||
20 |
Agreement between the entity managing the e-CODEX system and eu-LISA regarding the successful completion of the handover and takeover process |
Agreement between the entity managing the e-CODEX system and eu-LISA regarding the fulfilment of the criteria for a successful handover process and for the successful completion of that process |
Joint request by the entity managing the e-CODEX system and eu-LISA to the Commission to declare the successful completion of the handover and takeover process |
Between 1 July and 31 December 2023 |
7.
INTELLECTUAL PROPERTY RIGHTS OR USAGE RIGHTS
8.
TIMELINE
|
Component |
Handover Support |
Duration (indication) |
Sequence |
Items to develop & operate |
Configuration Management Tool – CMT |
Documentation Masterclass "CMT" |
2 days |
4th |
Central Testing Platform – CTP |
Documentation Masterclass "CTP" |
2 days |
5th |
|
Repository Server (currently: Nexus) |
Masterclass "development and infrastructure" |
2 days |
6th |
|
Integration Server (currently: Jenkins) |
||||
Source Code Repository (currently: Gitblit) |
||||
Items to develop & deliver |
e-CODEX Architecture |
Documentation Masterclass "e-CODEX Overview" |
4 days |
1st |
Connector Suite |
Documentation Masterclass "Connector" |
20 days |
2nd |
|
Use Case Schemas |
Documentation Masterclass "Schemas" |
10 days |
3rd |
9.
STRUCTURE OF THE HANDOVER REPORT TO BE PROVIDED BY THE ENTITY MANAGING THE e-CODEX SYSTEM
10.
STRUCTURE OF THE TAKEOVER REPORT TO BE PROVIDED BY eu-LISA
APPENDIX
COMMON HANDOVER DOCUMENT STRUCTURE
Document change log
Edition |
Issue Date |
|
Modified paragraphs |
Modifications |
|
|
|
|
|
1.
REFERENCE AND APPLICABLE DOCUMENTS
1.1.
Reference documents
ID |
Title |
Reference |
Version |
|
|
|
|
1.2.
Applicable documents
ID |
Title |
Reference |
Version |
|
|
|
|
2.
TERMINOLOGY
2.1.
Abbreviations and acronyms
Abbreviation Or Acronym |
Meaning |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
3.
INTRODUCTION
3.1.
Purpose of the Document
3.2.
Target Audience
4.
ASSUMPTIONS AND RISKS
4.1.
Assumptions and Prerequisites
4.2.
Risks
Risk |
Risk Owner |
Mitigation |
|
|
|
5.
HANDOVER AND TAKEOVER APPROACH
5.1.
Kick-Off meeting
5.2.
Synchronisation meetings
5.3.
Handover Plan
5.4.
Initial Handover of assets
5.4.1.
Applications
5.4.2.
Documentation
5.4.3.
Procedures
5.4.4.
Backlog (RfC, Tickets, Issues, etc.…)
6.
FINAL HANDOVER OF ASSETS
6.1.
Applications
6.2.
Documentation
6.3.
Procedures
6.4.
Backlog (RfC, Tickets, Issues, etc.)
7.
KNOWLEDGE TRANSFER
8.
HANDOVER CONTACT DETAILS
9.
TAKEOVER CONTACT DETAILS
10.
INFRASTRUCTURE NEEDS AT EU-LISA
10.1. Applications
10.2. Hardware/System Requirements
10.3. COTS (commercial off-the-shelf)
11.
SECURITY REQUIREMENTS
12.
WORKSHOP SCHEDULE
12.1.
General workshop about all services
[Date |
Add Date |
Duration |
Add Duration |
Location |
Add Location |
Audience |
All |
Scope |
Introduction and functional overview of all applications and services of e-CODEX.] |
12.2.
Helpdesk and Operations Workshops
[Date |
Add Date |
Duration |
Add Duration |
Location |
Add Location |
Audience |
Helpdesk Team |
Scope |
Support, incident handling, reporting, notifications, security management…] |
12.3.
Installation and Testing Workshops
12.3.1.
Installations
[Date |
Add Date |
Duration |
Add Duration |
Location |
Add Location |
Audience |
Technical team |
Scope |
installations of releases and patches] |
12.3.2.
Testing
[Date |
Add Date |
Duration |
Add Duration |
Location |
Add Location |
Audience |
Testing team |
Scope |
testing of all applications] |
12.3.3.
Workshops on other topics
[Date |
Add Date |
Duration |
Add Duration |
Location |
Add Location |
Audience |
Ad-Hoc |
Scope |
All remaining items] |
12.3.4.
Q&A and Shadowing Workshops
[Date |
Add Date |
Duration |
Add Duration |
Location |
Add Location |
Audience |
Ad-Hoc |
Scope |
Depending on the topic in scope] |