<div class="section-container active-section" sc-info-ref="1">
<div section-index="1" class="card-wrapper card-1">
<h2>Introduction to the Common Services</h2>
<p>The Common Services support the exchange of evidences between <b>evidence providers</b> and <b>evidence
requesters</b>. These services are composed of three independent modules that have access to all information
required to enable evidence exchange.</p>
<p>The three modules aim to answer the following questions:</p>
<ul>
<li>Evidence broker - What evidence to request?</li>
<li>Data Service Directory - Who to send the evidence request to?</li>
<li>Semantic repository - Which semantic agreement should I respect?</li>
</ul>
<h4 class="mg-24b">Watch the video explaining the Common services</h4>
<div class="video-wrapper mg-24b">
<iframe src="https://europa.eu/webtools/crs/iframe/?oriurl=https%3A%2F%2Fwww.youtube.com%2fembed%2fEySvW5fzO6k" frameborder="0"></iframe>
</div>
<p>The first part of the guidelines introduces you to the Common Services and the Common Services Administration Tool.
The following part then provides you with guidance on how to input your data as complete your tasks in the Common
Services Administration Tool in the role of evidence provider.</p>
<div class="visual-wrapper">
<div class="visual-container">
<img src="https://ec.europa.eu/digital-building-blocks/sites/download/attachments/713528669/Infographic_Common%20Services.png?api=v2"
alt="" />
</div>
</div>
<p>You can read more about the Common Services by clicking on the link to the relevant Technical Design Documents
below:</p>
<p><a class="btn primary" target="_blank" href="https://ec.europa.eu/digital-building-blocks/sites/display/TDD/"><span>Evidence Broker</span><span class="sr-only">(opens in a new tab)</span><span class="ico-external"></span></a></p>
<p><a class="btn primary" target="_blank" href="https://ec.europa.eu/digital-building-blocks/sites/display/TDD/"><span>Data Service Directory</span><span class="sr-only">(opens in a new tab)</span><span class="ico-external"></span></a></p>
<p><a class="btn primary" target="_blank" href="https://ec.europa.eu/digital-building-blocks/sites/display/TDD/"><span>Semantic Repository</span><span class="sr-only">(opens in a new tab)</span><span class="ico-external"></span></a></p>
</div>
<div section-index="2" class="card-wrapper card-2">
<h2>What is the Common Services Administration Tool?</h2>
<p>The Common Services Administration Tool is the user interface to the Common Services. You will be able to manage
your Member State procedures, procedural requirements, evidence types, evidence providers and data services
through the application.</p>
<p>You can access the production version of the tool here:</p>
<p><a class="btn primary" target="_blank" href="https://cs.oots.tech.ec.europa.eu/home"><span>Common Services Administration Tool</span><span class="sr-only">(opens in a new tab)</span><span class="ico-external"></span></a></p>
</div>
<div section-index="3" class="card-wrapper card-3">
<h2>Who needs access to the tool?</h2>
<p>You will need access to the Common Services Administration Tool if you are:</p>
<ul>
<li><b>User manager (SDG national coordinator)</b> go through an identity checking process so they can
manage access to the Common Services Administration Tool for users in their respective Member State</li>
<li><b>MS member(s)</b> of the evidence mapping subgroup support competent authorities in the evidence
mapping process and help them access the tools and locate online resources</li>
<li><b>Competent authorities</b> responsible for requesting evidence in online procedures</li>
<li><b>Competent authorities</b> responsible for providing evidence in online procedures (responding to
evidence requests)</li>
<li><b>Technical architect</b> who can provide input on the more technical data required in the Common
Services</li>
</ul>
<div class="section-more">
<div class="note-wrapper">
<div class="icon-wrapper">Note</div>
<p class="note-txt">Access to the Common Services Administration Tool is granted by the National Coordinator of each Member
State. If you have any issues related to your access, or would like to request access to the tool,
please contact your SDG National Coordinator.</p>
</div>
</div>
</div>
<div section-index="4" class="card-wrapper card-4">
<h2>What user roles are in the tool?</h2>
<p>There are four main user roles in the Common Services:</p>
<ul>
<li><b>MS Editors (EB/DSD)</b> are representatives of an organisation authorised to manage EB/DSD data on
its behalf. Editors can manage data in Draft status and request reviews of data by the Administrators.
</li>
<li><b>MS Administrators (EB/DSD)</b> have the same permissions as editors but can also publish, archive and
delete data.</p>
<li><b>Observers</b> have read-only privileges. </li>
<li><b>User Managers</b> are responsible for assigning roles. MS User Managers are responsible for the
management of OOTS users in their Member States. The EC User Manager is responsible for the management
of OOTS users.</li>
</ul>
<div class="section-more">
<div class="note-wrapper">
<div class="icon-wrapper">Note</div>
<p class="note-txt">If you have questions or need support related to your user role in the Common Services, you
can contact your national coordinator who will be able to provide you with access via the user management
application. You can find the detailed guidance for this procedure on the OOTS Service Desk:
<a class="link-cta tertiary forward"
href="https://ec.europa.eu/digital-building-blocks/sites/display/OOTS/Service+Desk"
target="_blank"><span>Common Services Admin UI access management procedure</span></a>
</p>
</div>
</div>
</div>
<div section-index="5" class="card-wrapper card-5">
<h2>What do the statuses of the assets mean?</h2>
<p>Each asset in the Common Services Administration Tool can be saved as one of the four main statuses. The status
of an asset may impact what actions you can take. An asset at any given time can be in one of the four main
statuses:</p>
<div class="section-more">
<div class="note-wrapper">
<div class="icon-wrapper">Note</div>
<p class="note-txt">Assets include Member State procedures, evidence types and evidence providers that have
been input into the Common Services.</p>
</div>
</div>
<ul>
<li><b>Draft</b> means it is not published and depending on the role (MS Editor/ MS Administrator) can be
submitted for review/published/edited/deleted/linked with other entities.</li>
<li><b>In review</b> means it is frozen for reviewing purposes and depending on the role (MS Editor/ MS
Administrator ) can be published/ set back to draft.</li>
<li><b>Published</b> means the asset it is published and can be set back to draft/ archived.</li>
<li><b>Archived</b> means that the asset is inactive and can be set back to draft/ deleted.</li>
</ul>
</div>
</div>
<div class="section-container" sc-info-ref="2">
<div section-index="6" class="card-wrapper card-6">
<h2>What do I need to do in the Common Services as an evidence provider?</h2>
<p>This section covers the tasks that evidence providers may perform in the Common Services Administration Tool.</p>
<p>First, before completing any tasks in the tool, evidence providers should:</p>
<p>1) Understand two key concepts:</p>
<ul>
<li><b>Evidence Types</b>: a category of structured or unstructured evidence with a common purpose or
content.</li>
<li><b>Evidence Providers</b>: a Competent Authority that lawfully issues evidence falling within scope of
Article 14(2) of Regulation (EU) 2018/1724.</li>
</ul>
<div class="section-more">
<div class="note-wrapper">
<div class="icon-wrapper">Note</div>
<p class="note-txt">Member States should try and identify evidence types and evidence providers for every procedural
requirement listed in the Common Services. If a citizen or business tries
to complete a procedure in another country and no evidence type has been defined for the procedural
requirement in your Member State, they will not be able to retrieve the evidence through the OOTS.</p>
</div>
</div>
<p>2) Determine if they need to connect to the OOTS by following the checklist provided in the next section "Do I
need to connect as an evidence provider to the OOTS?"</p>
</div>
<div section-index="7" class="card-wrapper card-7">
<h2>Checklist: Do I need to connect as an evidence provider to the OOTS?</h2>
<p>Article 14(2) of the SDGR provides the legal basis for connecting as an evidence provider to the OOTS: Where
competent authorities lawfully issue, in their own Member State and in an electronic format that allows
automated exchange, evidence that is relevant for the online procedures referred to in paragraph 1, they shall
also make such evidence available to requesting competent authorities from other Member States in an electronic
format that allows automated exchange.</p>
<p>If you do need to connect to the OOTS as an evidence provider, you will need to follow the steps below:</p>
<div class="visual-wrapper">
<div class="visual-container">
<img src="https://ec.europa.eu/digital-building-blocks/sites/download/attachments/713528669/Connect%20to%20OOTS%20as%20evidence%20provider_horisontal.png?api=v2"
alt="" />
</div>
</div>
</div>
<div section-index="8" class="card-wrapper card-8" id="create-your-evidence-type">
<h2>Create your evidence type</h2>
<p>Evidence types may be exchanged as either structured or un-structured evidences. In OOTS, structured evidence is
(in digital format) based on a data model that is machine-readable. Non-structured evidence is considered as
evidence stored in a document format, like PDF, and is human readable. Evidence itself must be issued in one of
three formats:</p>
<ul>
<li>Evidence that is in a human readable format (e.g., PDF);</li>
<li>Structured evidence that complies with an OOTS data model relevant for the evidence type; or</li>
<li>Structured evidence that does not comply with an OOTS data model must be accompanied by a human-readable
version of the evidence (e.g., a PDF) to ensure the receiving competent authority can read the evidence.
</li>
</ul>
<div class="step-label">Step 1: General Information of the evidence type</div>
<div class="step-content">
<ul>
<li>Adding the general information of your evidence type in English helps to facilitate understanding amongst
the Member States using the Common Services Administration Tool.</li>
<li>Describe the evidence type and refer to any legal frameworks that govern the definition of that evidence
type.</li>
<li>Adding the general information of your evidence type in other <b>most relevant</b> languages is important
because it enables the
evidence type to be displayed in the right language to citizens and businesses using the OOTS.</li>
</ul>
</div>
<div class="step-label">Step 2: Select the jurisdiction of your evidence type</div>
<div class="step-content">
<ul>
<li>Evidence types may be the same across the whole country, a birth certificate for example.</li>
<li>
<bullet>Evidence types may also be specific to a region or even a municipality.
</li>
<li>Different jurisdictions may use different evidence types.</li>
<li>Different regions may map different evidence types to the same procedural requirement.</li>
<li>In situations where different regions provide different evidence types, the user will have to choose between
the jurisdictions to identify the right evidence type to request.</li>
</ul>
</div>
<div class="step-label">Step 3: Save your evidence type</div>
<div class="step-content">
<p>Editors can:</p>
<ul class="ul-sec">
<li>Save evidence types as a draft</li>
<li>Submit the evidence type for review by an administrator</li>
</ul>
<p>Administrators can:</p>
<ul class="ul-sec">
<li>Save the evidence type as a draft</li>
<li>Submit the evidence type for review by an administrator</li>
<li>Publish the evidence type</li>
</ul>
</div>
<div class="section-more">
<div class="note-wrapper">
<div class="icon-wrapper">Note</div>
<div class="note-txt">
<p>Member States are encouraged to add the evidence types in English language and in few characters as possible,
providing enough information to determine what the file is: [Document Name], e.g. Birth Certificate.</p>
<p>Please also note that it is unnecessary to differentiate the document name per Member States. If for example the
official document name is "
Birth Certificate", it can be used as an evidence type for all the Member States.</p>
<p>What to avoid:</p>
<ul>
<li>Adding Member State initials (e.g., "Birth Certificate_AT");</li>
<li>Identifying the evidence as "proof" (e.g., "Proof of Birth"), which is already part of the requirements
(being Proof of Birth, Proof of Marriage, etc.)</li>
</ul>
<p>Once the evidence type is correctly added, requirements should be linked to it.</p>
</div>
</div>
</div>
</div>
<div section-index="9" class="card-wrapper card-9" id="link-your-evidence-type-to-a-requirement">
<h2>Link your evidence type to a requirement</h2>
<div class="step-label">Step 1: Select a procedural requirement that you would like to link an evidence type to</div>
<div class="step-content">
<ul>
<li>Check the description of the requirement that you would like to link an evidence type to, before performing
the linking.</li>
<li>Ensure the evidence type can meet all the minimum information described in the procedural requirement so the
requesting competent authority has
all the information they need to process the procedure on behalf of the user.</li>
<li>It is OK for your evidence type to contain more information than what is requested.</li>
</ul>
</div>
<div class="step-label">Step 2: Add the evidence to an evidence type list</div>
<div class="section-more">
<div class="note-wrapper">
<div class="icon-wrapper">Note</div>
<p class="note-txt">Requirements are linked to <b>evidence type lists</b>, <u>not</u> directly to evidence
types.</p>
</div>
</div>
<ul>
<li>Provide a name of your evidence type list that helps it to be easily distinguishable from the other lists.
</li>
<li>Evidence type lists may contain one or more evidence types. You can combine different evidence types in a
list if it is necessary to meet all the minimum information in the relevant procedural requirement.</li>
<li>You can also create more than one evidence type list and map it to the same procedural requirement. For
example, proof of university diploma could be linked to three different evidence type lists. One for
Bachelor, one for Masters and one for PhD diplomas.</li>
</ul>
<div class="step-label">Step 3: Confirm</div>
<div class="step-content">
<ul>
<li>Now you have successfully linked your evidence type to a requirement, you can view the linking by clicking
on the "Evidence type(s) linked" tab.</li>
<li>Once published, your evidence type will be live in the OOTS. If you don’t publish your evidence type and a
portal requests the evidence type for your country for a requirement, the user will receive a message that
the evidence type is not defined, and they won’t be able to proceed. Only published evidence types appear in
queries to the Common Services.</li>
<li>For the whole evidence type to be published, it must be linked to a published evidence provider in order to
be exchanged via the OOTS.</li>
<li>Once published, the evidence type metadata becomes publicly accessible in the Semantic Repository. The
Semantic Repository URIs contain <b>machine-readable information (XML, JSON)</b> about the asset metadata,
including name, description, identifier, publisher, and available languages.</li>
</ul>
</div>
</div>
<div section-index="10" class="card-wrapper card-10" id="create-your-evidence-provider">
<h2>Create your evidence provider</h2>
<div class="step-label">Step 1: General information</div>
<div class="step-content">
<ul>
<li>Provide the legal name of the evidence provider.</li>
<li>Provide a description to help end-users to select between providers.</li>
<li>The identifier scheme is up to each Member State to decide.</li>
<li>The identifier value specifically identifies the evidence provider in your Member State and allows your
access point to route the evidence request message to the right provider.</li>
<li>The Access service refers to the national eDelivery access point the evidence provider is connected to.
</li>
<li>Adding the official address of the evidence provider to make it easier for end users to verify the
authority.</li>
<li>Add the name of your evidence provider in relevant languages so that it can be displayed in the right
language for end users when they use the OOTS.</li>
</ul>
</div>
<div class="step-label">Step 2: Define jurisdictions</div>
<div class="step-content">
<ul>
<li>You may have multiple evidence providers that provide the same evidence type in your country.</li>
<li>For example, university diplomas may be held in education databases specific to region in country.</li>
<li>To ensure the user can help the system identify the right evidence provider, define the jurisdiction for
your evidence providers.</li>
</ul>
</div>
<div class="step-label">Step 3: Save your evidence provider</div>
<div class="step-content">
<p>Editors can:</p>
<ul class="ul-sec">
<li>Save evidence providers as a draft.</li>
<li>Submit the evidence providers for review by an administrator.</li>
</ul>
<p>Administrators can:</p>
<ul class="ul-sec">
<li>Save evidence providers as a draft.</li>
<li>Submit the evidence providers for review by an administrator.</li>
<li>Publish evidence providers.</li>
</ul>
</div>
</div>
<div section-index="11" class="card-wrapper card-10" id="link-your-evidence-provider-to-an-evidence-type">
<h2>Link your evidence provider to an evidence type</h2>
<div class="step-label">Step 1: Select evidence provider and evidence type</div>
<div class="step-content">
<ul>
<li>Select the evidence provider that you want to link to an evidence type</li>
<li>Select the evidence type that you want to link the evidence provider to</li>
</ul>
</div>
<div class="step-label">Step 2: Define metadata</div>
<div class="step-content">
<ul>
<li>Metadata is the information that links an evidence type to an evidence provider.</li>
<li>This metadata may be different for the same evidence type. For example, one university may provide
university diplomas in one format (PDF) and the other may provide the same evidence in a different
format (XML and PDF).</li>
<li>If multiple providers provide the same evidence type with the same values for the metadata, you can
reuse existing metadata.</li>
<li>The minimum level of assurance refers to the minimum level of assurance of the eID that users need to
have to authenticate to request evidence from the evidence provider.</li>
<li>Art 15.2 (e) of the Implementing Regulation states that "where structured evidence does not comply with
the OOTS data model relevant for the evidence type concerned, a human-readable version of the evidence."
</li>
<li>If you want to add a distribution format like XML, you will need to add a PDF distribution too. In
future data models for all structured evidences will be included in the semantic repository.</li>
<li>If the jurisdiction level is not national. You can add a jurisdiction context. For example, you may need
to tell users to select the municipality where they were born to get their birth certificate, rather
than selecting the municipality where they live now.</li>
</ul>
</div>
<div class="step-label">Step 3: Confirm</div>
<div class="step-content">
<ul>
<li>When your evidence provider and your evidence type are published, you are ready to exchange evidence
through the OOTS.</li>
</ul>
</div>
</div>
</div>
<div class="scroll-to-top">
<button><svg xmlns="http://www.w3.org/2000/svg" width="16" height="16" viewBox="0 0 16 16" fill="none">
<path
d="M15.1002 8.525C14.9502 8.675 14.7709 8.75 14.5622 8.75C14.3542 8.75 14.1752 8.68333 14.0252 8.55L8.7502 3.25V14.875C8.7502 15.075 8.6792 15.25 8.5372 15.4C8.39586 15.55 8.21686 15.625 8.0002 15.625C7.78353 15.625 7.6042 15.55 7.4622 15.4C7.32086 15.25 7.2502 15.075 7.2502 14.875L7.2502 3.25L1.9752 8.55C1.8252 8.68333 1.6462 8.75 1.4382 8.75C1.22953 8.75 1.0502 8.675 0.900196 8.525C0.766862 8.375 0.700195 8.2 0.700195 8C0.700195 7.8 0.766862 7.625 0.900196 7.475L7.3752 1.025C7.45853 0.924999 7.5542 0.854 7.6622 0.812C7.77086 0.770667 7.88353 0.75 8.0002 0.75C8.11686 0.75 8.2292 0.770667 8.3372 0.812C8.44586 0.854 8.54186 0.924999 8.6252 1.025L15.1002 7.475C15.2335 7.625 15.3002 7.8 15.3002 8C15.3002 8.2 15.2335 8.375 15.1002 8.525Z"
fill="white" />
</svg>
</button>
</div> |