service desk

Welcome to the OOTS Service Desk

Find below the different topics on which we can assist you. Once you have submitted your request, the communication will be done via email (from the mail address EC-SERVICENOW@ec.europa.eu) at each step of the processing of your request.

Get in touch with the Support Team

Introduction to the Support Team

Get to know the OOTS Support Team! Find our services, supported areas and availabilities as well as contact details all in one place.

Download Support Team briefing

Contact the Support Team

Reach out to the Support Team with any technical questions or issues you encounter.

Raise a ticket for the Service Desk

Access request

SDG Once Only Collaborative Space

The group's mission is to coordinate the implementation of the Once-Only Technical System and it’s accessible only to Member States representatives and other public entities.

OOTS Projectathon Collaborative Space

This space encourages stakeholder dialogue, idea exchange, promotes the Implementers café series for Projectathon preparation and is exclusively for OOTS implementers.

Implementers’ Space (MS Teams)

Request access MS Teams (only accessible for Projectathon participants).

Technical Dashboard access management

Request to nominate new National Coordinator to the Technical Dashboard, please read the "Procedure page 1".

Request to grant/revoke access from a Technical Contact Point to the Technical Dashboard, please read the "Procedure page 2".

*Read the procedure before initiating the process

Common Services Admin UI access management

This procedure details the access management procedure to the Common Services Admin UI, both for National Coordinators and for Member State Clerks.

Incident reporting

Critical technical incident

Report a critical technical incident such as unexpected downtime occurring either in an EC component or in a Member State Component.

*Read the procedure before initiating the process

Security issue

Report a security issue related either to a Member State implementation or the EC managed Common Services.

*Read the procedure before initiating the process

Vulnerability

Report a vulnerability in any of the OOTS components (on EC or Member State side) that could have an impact on other OOTS components.

*Read the procedure before initiating the process

Access Points

Report a scheduled downtime

Report a scheduled maintenance or downtime in your Access Point, to inform other Member States about the unavailability.

*Read the procedure before initiating the process

Request a PKI certificate

Each Member State can request up to 2 eDelivery PKI certificates for their Access Points.

*Read the procedure before initiating the process

OOTS Component Update

Request to update your Access Point configuration before a change so that continued interconnectivity can be assured.

*Read the procedure before initiating the process

OOTS procedures document repository

TCP nomination/revocation form

Download

Component update request form

Download

Application form for PKI certificate

Download

How to create a CSR

Download

LCM Interface onboarding

Download
               

OOTS FAQ

Find answers to common questions and concerns about Once-Only Technical System.

The procedure portal must identify what to ask for (Evidence Type), and who to ask it from (Evidence Provider).

a) Users can choose to use once only portal (OOP)
Using the Once-Only Technical System is not obligatory - users can still choose to use the Once-Only Technical System or upload the required documents manually.

b) User must input where their evidence is located
The user needs to select the MS where their evidence is issued. If there are multiple evidences required, the user needs to be able to select the provider MS for each evidence.

c) Determining the evidence type
If the portal does not already know what evidence type to request, the procedure portal sends a query to the Evidence Broker. The Evidence Broker allows the Evidence Requester to look up the right evidence type(s) to request from the Evidence Provider.

d) Determining the Evidence Provider
To determine who to send the request for evidence to, the portal sends a query to the Data Service Directory (DSD) with the evidence type (provided by the Evidence Broker) and Member State. The DSD returns the name of the Evidence Provider, the ID of the eDelivery Access point and if defined, any additional attributes required to locate the evidence provider.

e) Selecting the Evidence Provider
In some cases, Member States may need information from the user to determine the right evidence provider. For example, users may be required to input a region or other data to help locate the evidence. These additional attributes will be registered in the DSD. When the portal makes the query to the DSD and the response includes a request for these additional attributes, the procedure portal will request them from the user and use the user’s input to query the DSD again and define the right evidence provider.

If the Data Service Directory returns multiple Evidence Providers for an evidence type the user will be asked to select the relevant Evidence Provider from a list. For example, if university diplomas are stored in each university rather than in a central database, the user will be asked to select the right university to request the evidence from.

Is it also allowed to have decentralized portals, all connected separately to OOTS?
What about costs? What if a Member State does not have sufficient funding to develop a central procedure portal?

It is okay to have separate preview spaces for different evidence providers but of course a single preview space can be implemented. It is true that developing a preview space can be expensive but if you have a shared preview space, you can reduce the implementation costs significantly.  Some work is also ongoing by some Member States to develop a preview space service as an open source reusable component . Once published, it will be found under the Catalogue of reusable services on the OO Hub.

The common services implemented (EB & DSD) may store the meta-data of the evidences types, procedures, requirements.

See more FAQ

  • No labels