The Common Services have provisioned multiple environments for different purposes, taking advantage of the cloud infrastructure. The environments are either public-facing, aim to be used by the member states for production use, assessment and testing, or internally used by Dev, QA, UX and Security teams for continuous assessment of the development.

• Production / PROD: A stable public-facing environment, containing the official data of the Common Services.
• Acceptance / ACC: A production mirror environment having the same version as the production environment. It is used by the member states to test safely against the latest stable versions of the specs and features and to experiment with LCM and UI Data Entry without touching the official production data.
• Training / TRAINING: A production mirror environment having the same version as the production environment. It is used by the member states for training the clerks.  Typically used during Accelerator events in the 'training track' (whereas ACC/PROD would typically be used in the 'readiness checks' track).
• Projectathon / PROJ: A "sealed" fully controlled environment from a data perspective, used in the Projectathon instances. It supports the latest stable specs and contains the necessary common services data.
• User Acceptance Testing / UAT: A stable public-facing environment used to evaluate the next version of the services.

This document outlines the readiness indicators that should be checked by a Member State’s Access Point prior to going into production. Please take the time to review these readiness indicators carefully.

Access Point Readiness Indicators

The eDelivery PKI service is an optional service offered by the European Commission. Member States are free to choose any certificate that is conform to the  requirements and recommendations used in eDelivery (as per the OOTS TDDs ). To Member States who would like to use this certificate, the European Commission team offers one, maximum two eDelivery PKI certificates. This service is free of charge.

Read the procedure

Go to the request form

For more info about eDelivery Access Point for National Coordinators, visit the Onboarding Playbook

For more info about eDelivery Access Point for Intermediary Platforms, visit the Onboarding Playbook

This document outlines the readiness indicators for Common Services before going into production.

Common Services Readiness Indicators

The Evidence Mapping Framework is a guideline aimed at providing a basis for relevant stakeholders to participate in the Evidence Mapping process. It summarises the key concepts, introduces the importance of Evidence Mapping, and provides an overview of the Evidence Mapping sub-group's work, including objectives, scope, tasks, methodology, principles, and associated risks. The Framework also highlights some key points for stakeholders to keep in mind and provides answers to frequently asked questions.

Evidence Mapping Framework

The documents below are guidelines for relevant stakeholders participating in the Evidence Requesting and Evidence Providing tasks of the Evidence Mapping process. These guidelines present a summary of key concepts for Intermediary Platforms, Evidence Requesters and Evidence Providers.

Guidance for Evidence Requesters (coming soon)

The main purpose of this tool is to simplify navigating requirements and evidence types by providing the most value to both Evidence Requesters and Evidence Providers. While they have different reasons, they both share an interest in reviewing the list of requirements that have been defined.

For Evidence Requesters, this will help them determine if their requirements already exist or if they need to submit a new one. For Evidence Providers, it serves as a reference to check if any of their evidence types match the requirements.

Go to the Evidence Explorer Tool

For more info about Requirements and Evidence Types, visit the Onboarding Playbook:

Intermediary platform - Introduction to the Common Services

Evidence Requester - Introduction to the Common Services

Evidence Provider - Introduction to the Common Services

To ensure smooth operation of the OOTS infrastructure and applications, Member States need to follow some basic processes that allow for coordination between the components managed by the European Commission and those managed by the Member States. During the onboarding process, the OOTS Support Team will provide National Coordinators (NC) with access to the Technical Dashboard. Once National Coordinators have access, they will need to nominate their Technical Contact Points (TCP) to facilitate communication.

Please find below an explanation of the different functions for the two roles involved in reporting to the Support Team:

National Coordinator (NC)

• Responsible for User Management in the Common Services Admin Tool;
• Responsible for nominating the Technical Contact Points in the Dashboard;
• Can submit the Jira notification of the Procedures requiring dual control.

Technical Contact Point (TCP)

• Responsible for Access Point maintenance and updates (please take a look at the subsection below- "Report to the Support Team");
• Uploads the technical data required for the Procedures to S-CIRCABC;
• Can submit the Jira notification part of the Procedures requiring dual control (please note that S-CIRCABC upload and JIRA ticket must be done by 2 different people - either NC and TCP or 2 TCPs);
• On-call availability in out-of-office hours, available to be contacted via telephone 24/7 in the event of an urgent or critical situation.

You can read the full procedure (Annex IV - Technical Support Dashboard) via the link below, which contains guidelines on the workflows concerning the nomination/ revocation of SpoCs.

Read the procedure

OOTS_technical_dashboard_access_management

Now you have familiarised yourself with the procedure, you can request to nominate/ revoke a Contact Point to the Technical Dashboard by opening a ticket via the service desk.

Go to the request form

Before taking steps to manage your Access Point Governance, you should first on-board onto the Technical Dashboard.

For Access Point Governance, a list of parameters needs to be defined for each Access Point and shared with other Member States to ensure a working interconnection between the countries. This set of parameters has been defined: Deployment configuration data for OOTS

Access Point Governance

The Service Desk page lists all the procedures that you should follow when reporting issues to the Support Team. Your assistance will help maintain the highest level of security and safety.

Go to the Service Desk

When a Member State is impacted in any way, a notification is sent from the Dashboard to all representatives (NC +TCP) from a given Member State. Additionally, if the Member State nominated National Contact Points to be notified via phone, then the Support Team will call these Contact Points in case there is a critical or security incident. 

Competent Authorities, when, at national level, are instructing third parties to process Personal Data for the Exchange of Evidence through the OOTS, should use a Data Processing Agreement for setting out the technical requirements for the Controller and the Processor to follow when processing Personal Data.

OOTS provides a ready-to-use template for the Agreement which can be accessed here by Competent Authorities: