# Official Journal C 288/2022

| | ISSN 1977-091X |
| --- | --- |
| Official Journal
  of the European Union | C 288 |
| | |
| English edition | Information and Notices | Volume 6529 July 2022 |

ISSN 1977-091X

Official Journal

of the European Union

C 288

English edition

Information and Notices

Volume 6529 July 2022

---

| Contents | page |
| --- | --- |
| | II   Information |
| | INFORMATION FROM EUROPEAN UNION INSTITUTIONS, BODIES, OFFICES AND AGENCIES |
| | European Commission |
| 2022/C 288/01 | Communication from the Commission concerning Council Regulation (Euratom) No 1493/93 on shipments of radioactive substances between Member States | 1 |
| 2022/C 288/02 | Commission notice on guidelines with regard to the procedure for accreditation, approval and authorisation of independent operators to access vehicle security features laid down in Annex X to Regulation (EU) 2018/858 | 7 |
| 2022/C 288/03 | Non-opposition to a notified concentration (Case M.10624 – ENEL / INTESA / JV) (
  1
  ) | 33 |

Contents

page

II   Information

INFORMATION FROM EUROPEAN UNION INSTITUTIONS, BODIES, OFFICES AND AGENCIES

European Commission

2022/C 288/01

Communication from the Commission concerning Council Regulation (Euratom) No 1493/93 on shipments of radioactive substances between Member States

1

2022/C 288/02

Commission notice on guidelines with regard to the procedure for accreditation, approval and authorisation of independent operators to access vehicle security features laid down in Annex X to Regulation (EU) 2018/858

7

2022/C 288/03

Non-opposition to a notified concentration (Case M.10624 – ENEL / INTESA / JV) (
  1
  )

1

33

---

| | IV   Notices |
| --- | --- |
| | NOTICES FROM EUROPEAN UNION INSTITUTIONS, BODIES, OFFICES AND AGENCIES |
| | European Commission |
| 2022/C 288/04 | Euro exchange rates — 28 July 2022 | 34 |
| | European Data Protection Supervisor |
| 2022/C 288/05 | Summary of the Opinion of the European Data Protection Supervisor on the Proposal for a Regulation of the European Parliament and of the Council on the financial rules applicable to the general budget of the Union
  (The full text of this Opinion can be found in English, French and German on the EDPS website https://edps.europa.eu) | 35 |

IV   Notices

NOTICES FROM EUROPEAN UNION INSTITUTIONS, BODIES, OFFICES AND AGENCIES

European Commission

2022/C 288/04

Euro exchange rates — 28 July 2022

34

European Data Protection Supervisor

2022/C 288/05

Summary of the Opinion of the European Data Protection Supervisor on the Proposal for a Regulation of the European Parliament and of the Council on the financial rules applicable to the general budget of the Union
  (The full text of this Opinion can be found in English, French and German on the EDPS website https://edps.europa.eu)

(The full text of this Opinion can be found in English, French and German on the EDPS website https://edps.europa.eu)

35

---

| | V   Announcements |
| --- | --- |
| | OTHER ACTS |
| | European Commission |
| 2022/C 288/06 | Publication of a communication of approval of a standard amendment to the product specification for a name in the wine sector referred to in Article 17(2) and (3) of Commission Delegated Regulation (EU) 2019/33 | 38 |
| 2022/C 288/07 | Publication of a communication of approval of a standard amendment to the product specification for a name in the wine sector as referred to in Article 17(2) and (3) of Commission Delegated Regulation (EU) 2019/33 | 43 |
| 2022/C 288/08 | Publication of an application for registration of a name pursuant to Article 50(2)(a) of Regulation (EU) No 1151/2012 of the European Parliament and of the Council on quality schemes for agricultural products and foodstuffs | 46 |

V   Announcements

OTHER ACTS

European Commission

2022/C 288/06

Publication of a communication of approval of a standard amendment to the product specification for a name in the wine sector referred to in Article 17(2) and (3) of Commission Delegated Regulation (EU) 2019/33

38

2022/C 288/07

Publication of a communication of approval of a standard amendment to the product specification for a name in the wine sector as referred to in Article 17(2) and (3) of Commission Delegated Regulation (EU) 2019/33

43

2022/C 288/08

Publication of an application for registration of a name pursuant to Article 50(2)(a) of Regulation (EU) No 1151/2012 of the European Parliament and of the Council on quality schemes for agricultural products and foodstuffs

46

---

| | |
| --- | --- |
| | (1)   Text with EEA relevance. |

---

(1)   Text with EEA relevance.

1

| EN | |
| --- | --- |

EN

---

II Information

INFORMATION FROM EUROPEAN UNION INSTITUTIONS, BODIES, OFFICES AND AGENCIES

European Commission

| 29.7.2022 | EN | Official Journal of the European Union | C 288/1 |
| --- | --- | --- | --- |

29.7.2022

EN

Official Journal of the European Union

C 288/1

---

Communication from the Commission concerning Council Regulation (Euratom) No 1493/93 on shipments of radioactive substances between Member States

(2022/C 288/01)

Pursuant to Article 8 of Council Regulation (Euratom) No 1493/93, the Member States are required to forward to the Commission the name(s) and the address(es) of the competent authorities as defined in Article 2 and all necessary information for rapidly communicating with such authorities.

Member States are required to notify the Commission of any changes to such data.

The Commission is required to communicate this information and any changes to it, to all competent authorities in the Community and publish it in the Official Journal of the European Union.

The present Communication from the Commission replaces Commission Communication 2015/C 290/01 concerning Council Regulation (Euratom) No 1493/93 on shipments of radioactive substances between Member States (OJ C 290, 4.9.2015, p. 1).

A list of competent authorities in the Member States and all necessary information for communicating rapidly with them are given below.

Competent authorities referred to in Council Regulation (Euratom) No 1493/93 on shipments of radioactive substances between Member States

Austria

| Zentrales Strahlenquellenregister |
| --- |
| Bundesministerium für Klimaschutz, Umwelt, Energie, Mobilität, Innovation und Technologie |
| Abteilung V/8 – Strahlenschutz |
| Untere Donaustraße 11 |
| 1020 Wien |

Zentrales Strahlenquellenregister

Bundesministerium für Klimaschutz, Umwelt, Energie, Mobilität, Innovation und Technologie

Abteilung V/8 – Strahlenschutz

Untere Donaustraße 11

1020 Wien

Tel. +43 171100-614406

Email: strahlenregister@bmk.gv.at

Belgium

| Federal Agency for Nuclear Control (FANC) |
| --- |
| Security & Transport Department |
| Import & Transport Office |
| Rue Ravensteinstraat 36 |
| 1000 Brussels |

Federal Agency for Nuclear Control (FANC)

Security & Transport Department

Import & Transport Office

Rue Ravensteinstraat 36

1000 Brussels

Tel. +32 22892181

Email: transport@fanc.fgov.be

Internet: www.fanc.fgov.be

Bulgaria

| Nuclear Regulatory Agency |
| --- |
| Blvd. ‘Shipchenski Prohod’ 69 |
| 1574 Sofia |

Nuclear Regulatory Agency

Blvd. ‘Shipchenski Prohod’ 69

1574 Sofia

Tel. +359 29406801

Fax +359 29406919

+359 29406889

Email: mail@bnra.bg

Internet: www.bnra.bg

Croatia

| Ministry of the Interior |
| --- |
| Civil Protection Directorate |
| Sector for Radiological and Nuclear Safety |

Ministry of the Interior

Civil Protection Directorate

Sector for Radiological and Nuclear Safety

Fax +385 13788599

Email: sector.rns@civilna-zastita.hr

Internet: https://civilna-zastita.gov.hr/podrucja-djelovanja/83

Cyprus

| Radiation Inspection and Control Service |
| --- |
| Department of Labour Inspection |
| Ministry of Labour, Welfare and Social Insurance |
| Apellis Street 12 |
| 1080 Nicosia |

Radiation Inspection and Control Service

Department of Labour Inspection

Ministry of Labour, Welfare and Social Insurance

Apellis Street 12

1080 Nicosia

Tel. +357 22405623

Fax +357 22663788

Email: info@dli.mlsi.gov.cy

Internet: www.mlsi.gov.cy/dli

Czech Republic

| State Office for Nuclear Safety |
| --- |
| Register and Exposure Assessment Division |
| Senovážné náměstí 9 |
| 110 00 Praha 1 |

State Office for Nuclear Safety

Register and Exposure Assessment Division

Senovážné náměstí 9

110 00 Praha 1

Tel. +420 221624255

Fax +420 221624817

Email: jan.vinklar@sujb.cz

Internet: www.sujb.cz

Denmark

Danish Health Authority

| Radiation Protection |
| --- |
| Knapholm 7 |
| 2730 Herlev |

Radiation Protection

Knapholm 7

2730 Herlev

Tel. +45 44543454

Fax +45 72227417

Email: sis@sis.dk

Internet: www.sis.dk

Estonia

| Environmental Board |
| --- |
| Climate and Radiation Department |
| Kopli 76 |
| 10416 Tallinn |

Environmental Board

Climate and Radiation Department

Kopli 76

10416 Tallinn

Tel. +372 6625999

Fax +372 6807427

Email: info@keskkonnaamet.ee

Internet: www.keskkonnaamet.ee

Finland

| Radiation and Nuclear Safety Authority (STUK) |
| --- |
| P.O. Box 14 |
| FI-00881 Helsinki |

Radiation and Nuclear Safety Authority (STUK)

P.O. Box 14

FI-00881 Helsinki

Tel. +358 9759881

Fax +358 975988500

Email: stuk@stuk.fi

Internet: www.stuk.fi

France

| Institut de Radioprotection et de Sûreté Nucléaire (IRSN) |
| --- |
| Boîte postale 17 |
| 31 avenue de la Division Leclerc |
| BP 17 |
| 92260 Fontenay-aux-Roses |

Institut de Radioprotection et de Sûreté Nucléaire (IRSN)

Boîte postale 17

31 avenue de la Division Leclerc

BP 17

92260 Fontenay-aux-Roses

Tel. +331 58357754

Fax +331 58359536

Email: inventaire@irsn.fr

Internet: www.irsn.fr

Germany

| Bundesamt für Wirtschaft und Ausfuhrkontrolle (BAFA) |
| --- |
| Frankfurter Straße 29-35 |
| 65760 Eschborn |

Bundesamt für Wirtschaft und Ausfuhrkontrolle (BAFA)

Frankfurter Straße 29-35

65760 Eschborn

Tel. +49 61969080

Fax +49 6196908800

Email: radionuklide@bafa.bund.de

Internet: www.bafa.de

Greece

| Greek Atomic Energy Commission (EEAE) |
| --- |
| Patriarchou Grigoriou and |
| Neapoleos, P.O. Box 60092 |
| Ag. Paraskevi |
| 153 10 Attica |

Greek Atomic Energy Commission (EEAE)

Patriarchou Grigoriou and

Neapoleos, P.O. Box 60092

Ag. Paraskevi

153 10 Attica

Τel. +30 2106506803

Email: chairman@eeae.gr

Internet: www.eeae.gr

Hungary

| Hungarian Atomic Energy Authority |
| --- |
| PO Box 676 |
| Budapest 114 |
| 1539 |

Hungarian Atomic Energy Authority

PO Box 676

Budapest 114

1539

Tel. +36 14364800

Fax +36 14364804

Email: haea@haea.gov.hu

Internet: www.oah.hu

Ireland

| Radiation Protection Regulation Team |
| --- |
| Office of Environmental Enforcement |
| Environmental Protection Agency |
| McCumiskey House |
| Richview |
| Clonskeagh Road |
| Dublin 14 |
| D14 YR62 |

Radiation Protection Regulation Team

Office of Environmental Enforcement

Environmental Protection Agency

McCumiskey House

Richview

Clonskeagh Road

Dublin 14

D14 YR62

Tel. +353 12680100

Fax +353 12680199

Email: RadRegulatory@epa.ie

Internet: www.epa.ie

Italy

| Italian National Institute for Environmental Protection and Research (ISPRA) |
| --- |
| Department for Nuclear, Technological and Industrial Risk |
| Via Vitaliano Brancati 48 |
| 00144 Roma |

Italian National Institute for Environmental Protection and Research (ISPRA)

Department for Nuclear, Technological and Industrial Risk

Via Vitaliano Brancati 48

00144 Roma

Tel. +39 0650072009

+39 0650072851

Fax +39 0650072941

Email: protocollo.ispra@ispra.legalmail.it

Internet: www.isprambiente.gov.it

| Ministero dello Sviluppo Economico |
| --- |
| Direzione Generale per il Mercato Elettrico, |
| le Rinnovabili e l’Efficienza Energetica, il Nucleare |
| Divisione V – Impieghi pacifici dell’energia nucleare, ricerca e gestione di materiali e rifiuti nucleari |
| Via Molise 6 |
| 00187 Roma |

Ministero dello Sviluppo Economico

Direzione Generale per il Mercato Elettrico,

le Rinnovabili e l’Efficienza Energetica, il Nucleare

Divisione V – Impieghi pacifici dell’energia nucleare, ricerca e gestione di materiali e rifiuti nucleari

Via Molise 6

00187 Roma

Tel. +39 0647052531

+39 0647052639

Fax +39 0647053980

Email: dgmereen.segreteria@mise.gov.it

Internet: www.mise.gov.it

Latvia

| Radiation Safety Centre of |
| --- |
| State Environmental Service of Latvia |
| Rupniecibas Street 23 |
| Riga, LV-1045 |

Radiation Safety Centre of

State Environmental Service of Latvia

Rupniecibas Street 23

Riga, LV-1045

Tel. +371 67084306

Email: pasts@vvd.gov.lv

Internet: www.vvd.gov.lv

Lithuania

| Radiation Protection Centre |
| --- |
| Kalvarijų st. 153 |
| LT-08352 Vilnius |

Radiation Protection Centre

Kalvarijų st. 153

LT-08352 Vilnius

Tel. +370 52361936

Fax +370 52763633

Email: rsc@rsc.lt

Internet: www.rsc.lt

Luxembourg

| Directeur de la Santé |
| --- |
| Division de la Radioprotection |
| Villa Louvigny |
| Allée Marconi |
| L-2120 Luxembourg |

Directeur de la Santé

Division de la Radioprotection

Villa Louvigny

Allée Marconi

L-2120 Luxembourg

Tel. +352 24785670

Fax +352 467522

Email: secretariat.radioprotection@ms.etat.lu

Malta

| Radiation Protection Board |
| --- |
| OHSA Building |
| 17, Triq Edgar Ferro |
| Pietà |
| PTA 3153 |

Radiation Protection Board

OHSA Building

17, Triq Edgar Ferro

Pietà

PTA 3153

Tel. +356 21247677

Fax +356 21232909

Email: ohsa.rpb@gov.mt

The Netherlands

| Authority for Nuclear Safety and Radiation Protection (ANVS) |
| --- |
| Koningskade 4 |
| 2596 AA Den Haag |
| PO Box 16001 |
| 2500 BA Den Haag |

Authority for Nuclear Safety and Radiation Protection (ANVS)

Koningskade 4

2596 AA Den Haag

PO Box 16001

2500 BA Den Haag

Tel. +31 (0) 884890500

Email: postbus.transportinfo@anvs.nl

Internet: www.anvs.nl

Poland

| National Atomic Energy Agency of the Republic of Poland |
| --- |
| Radiation Protection Department |
| Bonifraterska 17 st. |
| 00-203 Warsaw |

National Atomic Energy Agency of the Republic of Poland

Radiation Protection Department

Bonifraterska 17 st.

00-203 Warsaw

Tel. +48 225562800

Fax +48 226213786

Email: secretariat.dor@paa.gov.pl

Internet: www.gov.pl/paa

Portugal

| Agência Portuguesa do Ambiente |
| --- |
| Rua da Murgueira 9 |
| Zambujal - Alfragide |
| 2610-124 Amadora |

Agência Portuguesa do Ambiente

Rua da Murgueira 9

Zambujal - Alfragide

2610-124 Amadora

Tel. +351 214728200

Tel. +351 214728232

Email: geral@apambiente.pt

radiacao@apambiente.pt

Internet: www.apambiente.pt

Romania

| National Commission for Nuclear Activities Control (CNCAN) |
| --- |
| Blvd. Libertatii nr. 14, sector 5 |
| 050706 București |

National Commission for Nuclear Activities Control (CNCAN)

Blvd. Libertatii nr. 14, sector 5

050706 București

Tel. +40 213160572

Fax +40 213173887

Email: office@cncan.ro

Internet: www.cncan.ro

Slovak Republic

| Public Health Authority of the Slovak Republic |
| --- |
| Trnavská cesta 52 |
| 826 45 Bratislava |

Public Health Authority of the Slovak Republic

Trnavská cesta 52

826 45 Bratislava

Tel. +421 249284253

+421 249284111

Fax +421 244372619

Email: uvzsr@uvzsr.sk

podatelna@uvzsr.sk

Internet: www.uvzsr.sk

Slovenia

For radioactive sources in medical and veterinary sectors:

| Ministry of Health |
| --- |
| Slovenian Radiation Protection Administration |
| Ajdovščina 4 |
| SI-1000 Ljubljana |

Ministry of Health

Slovenian Radiation Protection Administration

Ajdovščina 4

SI-1000 Ljubljana

Tel. +386 14788709

Fax +386 14788715

Email: gp-ursvs.mz@gov.si

Internet: www.uvps.gov.si/en/

For radioactive sources in other sectors (industry, research):

| Ministry of the Environment and Spatial Planning |
| --- |
| Slovenian Nuclear Safety Administration |
| Litostrojska cesta 54 |
| SI-1000 Ljubljana |

Ministry of the Environment and Spatial Planning

Slovenian Nuclear Safety Administration

Litostrojska cesta 54

SI-1000 Ljubljana

Tel. +386 14721100

Fax +386 14721199

Email: gp.ursjv@gov.si

Internet: www.ursjv.gov.si/en/

Spain

National contact point

| Consejo de Seguridad Nuclear |
| --- |
| C/ Pedro Justo Dorado Dellmans, 11 |
| 28040 Madrid |
| Madrid |

Consejo de Seguridad Nuclear

C/ Pedro Justo Dorado Dellmans, 11

28040 Madrid

Madrid

Tel. +34 913460100

Fax +34 913460588

Javier Zarzuela

Email: jzj@csn.es

Regarding shipments of radioactive substances to nuclear facilities, to first category radioactive facilities or to second and third category radioactive facilities located in the regions of Andalucía, Castilla-La Mancha and Melilla:

| Dirección General de Política Energética y Minas |
| --- |
| Paseo de la Castellana, 160 |
| 28071 Madrid |
| Madrid |

Dirección General de Política Energética y Minas

Paseo de la Castellana, 160

28071 Madrid

Madrid

Tel. +34 913497418

Fax +34 913497529

Email: Bzn-sgenergianuclear@miteco.es

Regarding shipments of radioactive substances to second and third category radioactive facilities located in the following regions:

| COMUNIDAD AUTÓNOMA DE ASTURIAS |
| --- |
| Dirección General de Industria |
| Plaza de España, 1, 3.a planta |
| 33007 Oviedo |
| Asturias |

COMUNIDAD AUTÓNOMA DE ASTURIAS

Dirección General de Industria

Plaza de España, 1, 3.a planta

33007 Oviedo

Asturias

Tel. +34 985106676

Fax +34 985106675

| COMUNIDAD AUTÓNOMA DE ARAGÓN |
| --- |
| Departamento de Industria, Competitividad y Desarrollo Empresarial |
| Dirección general de Energía y Minas |
| Servició de Gestión Energética |
| Paseo de María Agustín, 36 |
| 50004 Zaragoza |
| Zaragoza |

COMUNIDAD AUTÓNOMA DE ARAGÓN

Departamento de Industria, Competitividad y Desarrollo Empresarial

Dirección general de Energía y Minas

Servició de Gestión Energética

Paseo de María Agustín, 36

50004 Zaragoza

Zaragoza

Tel. +34 976714747

Fax +34 976715360

Email: gestionenergetica@aragon.es

| COMUNIDAD AUTÓNOMA DE ILLES BALEARS |
| --- |
| Consejería de Transición Energética, Sectores Productivos y Memoria Democrática |
| Dirección General de Política Industrial |
| Servicio de Actividades Radiactivas |
| C/ del Bastió d’en Sanoguera, 2 |
| 07002 Palma |
| Illes Balears |

COMUNIDAD AUTÓNOMA DE ILLES BALEARS

Consejería de Transición Energética, Sectores Productivos y Memoria Democrática

Dirección General de Política Industrial

Servicio de Actividades Radiactivas

C/ del Bastió d’en Sanoguera, 2

07002 Palma

Illes Balears

Tel. +34 971176570

+34 971177000 + 63550

Fax +34 971176828

Email: rx@caib.es

| COMUNIDAD AUTÓNOMA DE CANARIAS |
| --- |
| Consejería de Turismo, Industria y Comercio |
| Dirección General de Industria |
| Avda. Francisco La Roche, 35, Edificio Usos Múltiples I, 7a planta |
| 38071 Santa Cruz de Tenerife |
| Santa Cruz de Tenerife |

COMUNIDAD AUTÓNOMA DE CANARIAS

Consejería de Turismo, Industria y Comercio

Dirección General de Industria

Avda. Francisco La Roche, 35, Edificio Usos Múltiples I, 7a planta

38071 Santa Cruz de Tenerife

Santa Cruz de Tenerife

Tel. +34 928899400 (Ext. 89288)

+34 922475000 (Ext. 25216)

Fax +34 922475354

| COMUNIDAD AUTÓNOMA DE CANTABRIA |
| --- |
| Consejería de Innovación, Industria, Transporte y Comercio |
| Dirección General de Industria, Energía y Minas |
| C/ Albert Einstein, 2 |
| 39011 Santander |
| Cantabria |

COMUNIDAD AUTÓNOMA DE CANTABRIA

Consejería de Innovación, Industria, Transporte y Comercio

Dirección General de Industria, Energía y Minas

C/ Albert Einstein, 2

39011 Santander

Cantabria

Tel. +34 942200044

Fax +34 942200030

| COMUNIDAD AUTÓNOMA DE CASTILLA Y LEÓN |
| --- |
| Consejería de Empleo e Industria |
| Dirección General de Industria |
| C/ Jacinto Benavente, 2, pta. 2a, ala norte |
| 47195 Arroyo de la Encomienda |
| Valladolid |

COMUNIDAD AUTÓNOMA DE CASTILLA Y LEÓN

Consejería de Empleo e Industria

Dirección General de Industria

C/ Jacinto Benavente, 2, pta. 2a, ala norte

47195 Arroyo de la Encomienda

Valladolid

Tel. +34 983324288

Fax +34 983411410

Tel. +34 9833242291

| COMUNIDAD AUTÓNOMA DE CATALUÑA |
| --- |
| Departamento de Empresa y Trabajo |
| Dirección General de Energía, Seguridad Industrial y Seguridad Minera |
| Servicio de Coordinación de Actividades Radioactivas |
| C/ Foc, 57, edificio A |
| 08038 Barcelona |
| Barcelona |

COMUNIDAD AUTÓNOMA DE CATALUÑA

Departamento de Empresa y Trabajo

Dirección General de Energía, Seguridad Industrial y Seguridad Minera

Servicio de Coordinación de Actividades Radioactivas

C/ Foc, 57, edificio A

08038 Barcelona

Barcelona

Tel. +34 933226633

Fax +34 934393996

Email: scar@gencat.cat

| COMUNIDAD AUTÓNOMA DE EXTREMADURA |
| --- |
| Consejería para la Transición Ecológica y Sostenibilidad |
| Dirección General de Industria, Energía y Minas |
| Paseo de Roma, s/n |
| 06800 Mérida |
| Badajoz |

COMUNIDAD AUTÓNOMA DE EXTREMADURA

Consejería para la Transición Ecológica y Sostenibilidad

Dirección General de Industria, Energía y Minas

Paseo de Roma, s/n

06800 Mérida

Badajoz

Tel. +34 924012115

Fax +34 924005601

Email: jose.narvaez@juntaex.es

| COMUNIDAD AUTÓNOMA DE GALICIA |
| --- |
| Vicepresidencia Segunda y Consejería de Economía, Empresa e Innovación |
| Dirección General de Planificación Energética y Recursos Naturales |
| Edificio administrativo San Caetano, s/n, bloque 5, puerta 4.a |
| 15781 Santiago de Compostela |
| A Coruña |

COMUNIDAD AUTÓNOMA DE GALICIA

Vicepresidencia Segunda y Consejería de Economía, Empresa e Innovación

Dirección General de Planificación Energética y Recursos Naturales

Edificio administrativo San Caetano, s/n, bloque 5, puerta 4.a

15781 Santiago de Compostela

A Coruña

Tel. +34 981545587

Fax +34 981957192

| COMUNIDAD AUTÓNOMA DE LA RIOJA |
| --- |
| Consejería de Desarrollo Autonómico Secretaría General Técnica |
| Servicio de Industria y Comercio |
| C/ Marqués de la Ensenada, 13-15 (entrada por c/ Albia de Castro) |
| 26071 Logroño |
| La Rioja |

COMUNIDAD AUTÓNOMA DE LA RIOJA

Consejería de Desarrollo Autonómico Secretaría General Técnica

Servicio de Industria y Comercio

C/ Marqués de la Ensenada, 13-15 (entrada por c/ Albia de Castro)

26071 Logroño

La Rioja

Tel. +34 941291710 / 941291711

Fax +34 941291206

Email: dg.itic@larioja.org

| COMUNIDAD AUTÓNOMA DE MADRID |
| --- |
| Consejería de Economía, Empleo y Competitividad |
| Dirección General de Industria, Energía y Minas |
| Ramírez de Prado, 5 bis, 2.a planta |
| 28045 Madrid |
| Madrid |

COMUNIDAD AUTÓNOMA DE MADRID

Consejería de Economía, Empleo y Competitividad

Dirección General de Industria, Energía y Minas

Ramírez de Prado, 5 bis, 2.a planta

28045 Madrid

Madrid

Tel. +34 914206498

Fax +34 915802194

| COMUNIDAD AUTÓNOMA DE MURCIA |
| --- |
| Consejería de Empresa, Empleo, Universidades y Portavocía |
| Dirección General de Energía y Actividad Industrial y Minera |
| C/ Nuevas Tecnologías, s/n |
| 30205 Murcia |
| Murcia |

COMUNIDAD AUTÓNOMA DE MURCIA

Consejería de Empresa, Empleo, Universidades y Portavocía

Dirección General de Energía y Actividad Industrial y Minera

C/ Nuevas Tecnologías, s/n

30205 Murcia

Murcia

Tel. +34 968362002

Fax +34 968362003

| COMUNIDAD AUTÓNOMA DE NAVARRA |
| --- |
| Departamento de Desarrollo Económico y Empresarial |
| Dirección General de Industria, Energía y Proyectos Estratégicos S3 |
| Servicio de Ordenación Industrial, Infraestructuras Energéticas y Minas |
| Parque Tomas Caballero, 1 |
| 31005 Pamplona |
| Navarra |

COMUNIDAD AUTÓNOMA DE NAVARRA

Departamento de Desarrollo Económico y Empresarial

Dirección General de Industria, Energía y Proyectos Estratégicos S3

Servicio de Ordenación Industrial, Infraestructuras Energéticas y Minas

Parque Tomas Caballero, 1

31005 Pamplona

Navarra

Tel. +34 848424499

Fax +34 848426468

Email: mlesdelg@navarra.es

| COMUNIDAD AUTÓNOMA DE PAÍS VASCO |
| --- |
| Departamento de Desarrollo Económico, Sostenibilidad y Medio Ambiente |
| Viceconsejería de Industria |
| Dirección de Proyectos Estratégicos y Administración Industrial |
| C/ Donostia-San Sebastián, 1 |
| 01010 Vitoria-Gasteiz |
| Araba/Álava |

COMUNIDAD AUTÓNOMA DE PAÍS VASCO

Departamento de Desarrollo Económico, Sostenibilidad y Medio Ambiente

Viceconsejería de Industria

Dirección de Proyectos Estratégicos y Administración Industrial

C/ Donostia-San Sebastián, 1

01010 Vitoria-Gasteiz

Araba/Álava

Tel. +34 945019696

+34 945019935

Fax +34 945019978

José Miguel Muñoz San Martín

Email: josemi-munoz@euskadi.eus

| COMUNIDAD AUTÓNOMA DE COMUNITAT VALENCIANA |
| --- |
| Consejería de Economía Sostenible, Sectores Productivos, Comercio y Trabajo |
| Dirección General de Industria, Energía y Minas |
| C/ de la Democracia, 77, Ciudad Administrativa 9 de octubre, Torre 2 |
| 46018 València |
| València/Valencia |

COMUNIDAD AUTÓNOMA DE COMUNITAT VALENCIANA

Consejería de Economía Sostenible, Sectores Productivos, Comercio y Trabajo

Dirección General de Industria, Energía y Minas

C/ de la Democracia, 77, Ciudad Administrativa 9 de octubre, Torre 2

46018 València

València/Valencia

Tel. +34 961209576

Fax +34 961209564

| CIUDAD AUTÓNOMA DE CEUTA |
| --- |
| Consejería de Sanidad, Consumo y Gobernación |
| Servicio de Consumo |
| Plaza de África, 1, acceso C, 1.o A |
| 51001 Ceuta |
| Ceuta |

CIUDAD AUTÓNOMA DE CEUTA

Consejería de Sanidad, Consumo y Gobernación

Servicio de Consumo

Plaza de África, 1, acceso C, 1.o A

51001 Ceuta

Ceuta

Tel. +34 956511658

+34 9956515627

+34 956528129

Fax +34 956515988

Sweden

| Strålsäkerhetsmyndigheten |
| --- |
| SE-171 16 Stockholm |

Strålsäkerhetsmyndigheten

SE-171 16 Stockholm

Tel. +46 87994000

Fax +46 87994010

Email: registrator@ssm.se

Internet: www.ssm.se

---

| 29.7.2022 | EN | Official Journal of the European Union | C 288/7 |
| --- | --- | --- | --- |

29.7.2022

EN

Official Journal of the European Union

C 288/7

---

Commission notice on guidelines with regard to the procedure for accreditation, approval and authorisation of independent operators to access vehicle security features laid down in Annex X to Regulation (EU) 2018/858

(2022/C 288/02)

Commission Delegated Regulation (EU) 2021/1244 (1) amends Annex X to Regulation (EU) 2018/858 (2) and notably adds a new Appendix that lays down the procedure for the approval and authorisation of independent operators (IO) to access vehicle security features.

The legal obligations of the procedure regarding the role and responsibilities of the bodies involved in the approval and authorisation of independent operators and their employees to be granted access to security-related vehicle repair and maintenance information are laid down in Regulation (EU) 2018/858, Annex X, Appendix 3. In accordance with point 6.3 of Annex X functional requirements on the application of the procedure are provided in support of the legal obligations through examples and use cases in the Annex to this Commission Notice.

---

(1)  Commission Delegated Regulation (EU) 2021/1244 of 20 May 2021 amending Annex X to Regulation (EU) 2018/858 of the European Parliament and of the Council as regards the standardised access to vehicle on-board diagnostics information and repair and maintenance information, and the requirements and procedures for access to vehicle security information (OJ L 272, 30.7.2021, p. 16).

(2)  Regulation (EU) 2018/858 of the European Parliament and of the Council of 30 May 2018 on the approval and market surveillance of motor vehicles and their trailers, and of systems, components and separate technical units intended for such vehicles, amending Regulations (EC) No 715/2007 and (EC) No 595/2009 and repealing Directive 2007/46/EC (OJ L 151, 14.6.2018, p. 1).

---

ANNEX

Functional requirements: use cases

USE CASE SERMI 1. Requests for changes to the accreditation process and monitoring the implementation across Member States:

| Actor | ‘Forum for Access to Security-Related Vehicle RMI’ or ‘SERMI’ members and the Commission |
| --- | --- |
| Goal | Actors may make a request to change the scheme. |
| Use Case Input | A request for changing the scheme to receive security-related Repair and Maintenance Information (RMI) |
| Use Case Output | Updated scheme to receive security-related RMI where appropriate |
| Description | SERMI handles requests for scheme changes. Its members evaluate and update the scheme. SERMI advises the Commission on requests for changes to the accreditation process |

Actor

‘Forum for Access to Security-Related Vehicle RMI’ or ‘SERMI’ members and the Commission

Goal

Actors may make a request to change the scheme.

Use Case Input

A request for changing the scheme to receive security-related Repair and Maintenance Information (RMI)

Use Case Output

Updated scheme to receive security-related RMI where appropriate

Description

SERMI handles requests for scheme changes. Its members evaluate and update the scheme. SERMI advises the Commission on requests for changes to the accreditation process

USE CASE SERMI 2. Selection of trust center(s)

| Actor | Trust Center (TC) |
| --- | --- |
| Goal | To designate a TC. |
| Use Case Input | TC’s application to SERMI which assesses whether the TC fulfills all functional and technical requirements. |
| Use Case Output | Accepted or rejected TC application.
  Updated selected TC list. |
| Description | SERMI processes requests from TCs applying for selection according to the criteria in point 4.1.2. of Appendix 3 of Annex X to Regulation (EU) 2018/858, SERMI creates and updates the selected TC list. The Commission is notified. |

Actor

Trust Center (TC)

Goal

To designate a TC.

Use Case Input

TC’s application to SERMI which assesses whether the TC fulfills all functional and technical requirements.

Use Case Output

Accepted or rejected TC application.

Updated selected TC list.

Description

SERMI processes requests from TCs applying for selection according to the criteria in point 4.1.2. of Appendix 3 of Annex X to Regulation (EU) 2018/858, SERMI creates and updates the selected TC list. The Commission is notified.

USE CASE SERMI 3. Setting out the implementation guide for interaction between the entities involved

| Actor | SERMI and Commission |
| --- | --- |
| Goal | Use of the implementation guide by vehicle manufacturers and TC to achieve correct implementation of the required communication standards Online Certificate Status Protocol (OCSP) and Simple Object Access Protocol (SOAP). |
| Use Case Input | Information and known standards. |
| Use Case Output | Implementation guide providing all required information for the communication interfaces. |
| Description | SERMI provides input to the Commission on the possibility to create and maintain the implementation considering enhancing security requirements and improving technologies over time. |

Actor

SERMI and Commission

Goal

Use of the implementation guide by vehicle manufacturers and TC to achieve correct implementation of the required communication standards Online Certificate Status Protocol (OCSP) and Simple Object Access Protocol (SOAP).

Use Case Input

Information and known standards.

Use Case Output

Implementation guide providing all required information for the communication interfaces.

Description

SERMI provides input to the Commission on the possibility to create and maintain the implementation considering enhancing security requirements and improving technologies over time.

USE CASE NAB 1. Accreditation of a Conformity Assessment Body

| Actor | Conformity Assessment Body (CAB) |
| --- | --- |
| Goal | Accredited CAB. |
| Use Case Input | Application form provided by a CAB to be processed by the National Accredidation Body (NAB). |
| Use Case Output | CAB is either accredited or not accredited.
  NAB accreditation report of CAB. |
| Description | Accreditation form provided by the NAB for completion by a CAB.
  The accreditation form is completed by the organisation applying to be a CAB.
  The NAB assesses that the organisation fulfills all requirements specified.
  The accreditation is to ensure that the CAB is assessed for compliance with the standard ‘Conformity assessment – Requirements for the operation of various types of bodies performing inspection’ (ISO/IEC 17020:2012) as inspection body type A.
  The CAB requests accreditation in accordance with Article 7 of Regulation (EC) No 765/2008. |

Actor

Conformity Assessment Body (CAB)

Goal

Accredited CAB.

Use Case Input

Application form provided by a CAB to be processed by the National Accredidation Body (NAB).

Use Case Output

CAB is either accredited or not accredited.

NAB accreditation report of CAB.

Description

Accreditation form provided by the NAB for completion by a CAB.

The accreditation form is completed by the organisation applying to be a CAB.

The NAB assesses that the organisation fulfills all requirements specified.

The accreditation is to ensure that the CAB is assessed for compliance with the standard ‘Conformity assessment – Requirements for the operation of various types of bodies performing inspection’ (ISO/IEC 17020:2012) as inspection body type A.

The CAB requests accreditation in accordance with Article 7 of Regulation (EC) No 765/2008.

USE CASE NAB 2. Processing of complaints against CABs

In accordance with Article 9(4) of Regulation (EC) No 765/2008, National accreditation bodies put in place the necessary procedures to deal with complaints against the conformity assessment bodies they have accredited.

The repsonsibilities of the NAB include:

| (a) | decide on the admissibility of the complaint, |
| --- | --- |

(a)

decide on the admissibility of the complaint,

| (b) | ensure that a complaint concerning an accredited CAB is first addressed by the CAB |
| --- | --- |

(b)

ensure that a complaint concerning an accredited CAB is first addressed by the CAB

| (c) | take appropriate corrective measures within a reasonable timeframe where necessary, |
| --- | --- |

(c)

take appropriate corrective measures within a reasonable timeframe where necessary,

| (d) | record all complaints and actions taken, and |
| --- | --- |

(d)

record all complaints and actions taken, and

| (e) | respond to the complainant. |
| --- | --- |

(e)

respond to the complainant.

During the complaint process through the NAB, all existing Independent Operator (IO) approvals, all employee authorisations, inspection certificates and corrective measures that have been issued by this CAB remain valid.

In case the NAB decides to withdraw the CAB accreditation all IO approvals and related approval inspection certificates and all employee authorisations inspection certificates that have been issued by this CAB ceases to be valid. The CAB subsequently informs the approved IO of that decision. The NAB informs SERMI and the Commission of that decision.

| Actor | IO, TC, vehicle manufacturer, relevant authorities. |
| --- | --- |
| Goal | To deal with complaints. |
| Use Case Input | Complaint against a CAB. |
| Use Case Output | Resolution of a complaint against a CAB. |
| Description | Complaints are resolved at local level between the CAB and the complainant. Complaints that are not resolved at the local level may be referred to the NAB for further consideration in accordance with Article 9(4) of Regulation (EC) No 765/2008. |

Actor

IO, TC, vehicle manufacturer, relevant authorities.

Goal

To deal with complaints.

Use Case Input

Complaint against a CAB.

Use Case Output

Resolution of a complaint against a CAB.

Description

Complaints are resolved at local level between the CAB and the complainant. Complaints that are not resolved at the local level may be referred to the NAB for further consideration in accordance with Article 9(4) of Regulation (EC) No 765/2008.

USE CASE NAB 3. NAB listing of accredited CABs

| Actor | NAB |
| --- | --- |
| Goal | NAB maintaining an updated list of all accredited CABs. |
| Use Case Input | Accredited CABs. |
| Use Case Output | A country-specific list of accredited CABs |
| Description | NAB creates, maintains and publishes a country-specific list of all accredited CABs. |

Actor

NAB

Goal

NAB maintaining an updated list of all accredited CABs.

Use Case Input

Accredited CABs.

Use Case Output

A country-specific list of accredited CABs

Description

NAB creates, maintains and publishes a country-specific list of all accredited CABs.

USE CASE CAB 1. CAB setting up of a business relationship with Trust Center

| Actor | CAB |
| --- | --- |
| Goal | CAB sets up a contractual agreement with a selected TC published in the SERMI selected TC list. |
| Use Case Input | Contract between the CAB and a selected TC chosen from the list of accepted TCs published by SERMI (see USE CASE SE2). |
| Use Case Output | A signed contract between CAB and TC is issued. |
| Description | CAB contracts a business relationship with one selected TC according to the published SERMI list in order to:






  a) | Create digital certificates and authorisation records. |

Actor

CAB

Goal

CAB sets up a contractual agreement with a selected TC published in the SERMI selected TC list.

Use Case Input

Contract between the CAB and a selected TC chosen from the list of accepted TCs published by SERMI (see USE CASE SE2).

Use Case Output

A signed contract between CAB and TC is issued.

Description

CAB contracts a business relationship with one selected TC according to the published SERMI list in order to:

a)

Create digital certificates and authorisation records.

| b) | Maintain approval and authorisation status (send out ‘new’ certificates if necessary). |
| --- | --- |

b)

Maintain approval and authorisation status (send out ‘new’ certificates if necessary).

| c) | Send the digital certificate and the PIN letter to be forwarded to the IO employee by the CAB. |
| --- | --- |

c)

Send the digital certificate and the PIN letter to be forwarded to the IO employee by the CAB.

A CAB sets up only one contractual agreement with one TC.

USE CASE CAB 2. CAB inspects IO for approval

| Actor | IO |
| --- | --- |
| Goal | Approval of IO, so that an IO can name employee(s) for authorisation to be given to access to security-related RMI. |
| Use Case Input | Completed application form as required by the CAB. The application form contains the criteria listed in point 4.3.3. of Appendix 3 of Annex X to Regulation (EU) 2018/858 |
| Use Case Output | Paper certificate with the IO approval inspection result. |
| Description | IO sends the application form and all necessary documents to the CAB by auditable means.
  CAB verifies the documents and checks if the IO has already been inspected by another CAB.
  If the criteria for IO approval (point 4.3.3 of Appendix 3 of Annex X to Regulation (EU) 2018/858) are met the CAB sends the paper approval inspection certificate to the IO.
  The CAB notifies by auditable means the other CABs in the respective country if the IO does not pass the CAB inspection.
  CAB verifies that the data provided by the IO is consistent throughout the process.
  Every IO employee of an IO who becomes authorised for access to security information is registered at the same CAB and TC.
  Every approved IO can be subject to unannounced random on-site inspections. This will occur once during the IO’s approval validity period. |

Actor

IO

Goal

Approval of IO, so that an IO can name employee(s) for authorisation to be given to access to security-related RMI.

Use Case Input

Completed application form as required by the CAB. The application form contains the criteria listed in point 4.3.3. of Appendix 3 of Annex X to Regulation (EU) 2018/858

Use Case Output

Paper certificate with the IO approval inspection result.

Description

IO sends the application form and all necessary documents to the CAB by auditable means.

CAB verifies the documents and checks if the IO has already been inspected by another CAB.

If the criteria for IO approval (point 4.3.3 of Appendix 3 of Annex X to Regulation (EU) 2018/858) are met the CAB sends the paper approval inspection certificate to the IO.

The CAB notifies by auditable means the other CABs in the respective country if the IO does not pass the CAB inspection.

CAB verifies that the data provided by the IO is consistent throughout the process.

Every IO employee of an IO who becomes authorised for access to security information is registered at the same CAB and TC.

Every approved IO can be subject to unannounced random on-site inspections. This will occur once during the IO’s approval validity period.

USE CASE CAB 3. CAB inspections on-site

| Actor | CAB |
| --- | --- |
| Goal | Minimum of one random and unannounced on-site inspection of every approved IO during the validity period and an IO requested on-site inspection in the last six months of the validity period to ensure that the information given during the application is correct and that the procedural requirements are implemented and practiced in daily operations as stated by the IO in the application for approval. The inspection carried out in the last 6 months will also be used to determine the renewal of an IO approval. On the basis of a complaint against an approved IO or an authorised IO employee, determines whether an on-site inspection is required. |
| Use Case Input | Unannounced visit to IO premises.
  Visit to IO premises on IO request in the last 6 months of the IO approval validity
  On the basis of a complaint. |
| Use Case Output | IO approval is confirmed or revoked.
  In case the IO approval is revoked, the IO employee authorisations are revoked and the TC is instructed to revoke the corresponding digital certificates.
  IO approval is renewed (USE CASE CAB 4). |
| Description | CAB visits the IO and carries out an on-site inspection by verifying compliance with the criteria in point 4.3.3 of Appendix 3 of Annex X to Regulation (EU) 2018/858.
  CAB may request the assistance of market surveillance authorities from the Member State they are established for the purposes of an on-site inspection.
  According to the findings during the inspection the IO approval is confirmed or revoked. The CAB allows the IO to correct minor deficiencies following the negative result of an on-site inspection in accordance point 4.3.1. of Appendix 3 of Annex X to Regulation (EU) 2018/858.
  A final negative inspection result has for consequence the revocation of the IO approval, the IO employee authorisations and the IO employee digital certificates by the TC. |

Actor

CAB

Goal

Minimum of one random and unannounced on-site inspection of every approved IO during the validity period and an IO requested on-site inspection in the last six months of the validity period to ensure that the information given during the application is correct and that the procedural requirements are implemented and practiced in daily operations as stated by the IO in the application for approval. The inspection carried out in the last 6 months will also be used to determine the renewal of an IO approval. On the basis of a complaint against an approved IO or an authorised IO employee, determines whether an on-site inspection is required.

Use Case Input

Unannounced visit to IO premises.

Visit to IO premises on IO request in the last 6 months of the IO approval validity

On the basis of a complaint.

Use Case Output

IO approval is confirmed or revoked.

In case the IO approval is revoked, the IO employee authorisations are revoked and the TC is instructed to revoke the corresponding digital certificates.

IO approval is renewed (USE CASE CAB 4).

Description

CAB visits the IO and carries out an on-site inspection by verifying compliance with the criteria in point 4.3.3 of Appendix 3 of Annex X to Regulation (EU) 2018/858.

CAB may request the assistance of market surveillance authorities from the Member State they are established for the purposes of an on-site inspection.

According to the findings during the inspection the IO approval is confirmed or revoked. The CAB allows the IO to correct minor deficiencies following the negative result of an on-site inspection in accordance point 4.3.1. of Appendix 3 of Annex X to Regulation (EU) 2018/858.

A final negative inspection result has for consequence the revocation of the IO approval, the IO employee authorisations and the IO employee digital certificates by the TC.

USE CASE CAB 4. CAB inspects IO for approval’s renewal

| Actor | IO |
| --- | --- |
| Goal | Renewal of IO approval. |
| Use Case Input | Completed application as required by the CAB. The application form contains the criteria listed in point 4.3.2. of Appendix 3 of Annex X to Regulation (EU) 2018/858. Positive result of an IO requested on-site inspection by the CAB in the 6 months prior to the approval expiration deadline. |
| Use Case Output | Paper certificate with the inspection result for renewal of an IO approval.
  Expiration of IO approval, IO employee authorisation and revocation of the digital certificates in case of a negative inspection result or of a denial of the renewal request. |
| Description | After a time period of 60 months the approval is to be renewed.
  Prior to expiry of the approval the IO is notified by the CAB of the pending expiry. This period of notification is of six months before the approval ends.
  IO requests an on-site inspection by the CAB.
  The CAB performs the on-site inspection. If the inspection result is negative the CAB revokes the IO approval and the IO employee authorisation(s). The CAB instructs the TC to revoke the IO employee certificate(s).
  IO sends all documents by auditable means to the CAB two months before the approval expires.
  CAB verifies the documents and checks if the IO has already been approved or rejected by another CAB.
  CAB verifies compliance with the concept of legitimate business activity set out in the second paragraph of point 6.3. of Annex X to Regulation (EU) 2018/858. CAB may be assisted by the market surveillance authority from the Member State it is established.
  If the criteria for IO approval (see point 4.3.3 of Appendix 3 of Annex X to Regulation (EU) 2018/858) are met the CAB sends the approval inspection paper certificate to the IO.
  The CAB notifies by auditable means, the other CABs in the respective country if the IO does not pass the CAB inspection.
  CAB verifies that the data provided by the IO is consistent throughout the process. Every employee of an IO who becomes authorised for access to security information following the authorisation inspection described in use case CA6 is registered at the same CAB and TC. |

Actor

IO

Goal

Renewal of IO approval.

Use Case Input

Completed application as required by the CAB. The application form contains the criteria listed in point 4.3.2. of Appendix 3 of Annex X to Regulation (EU) 2018/858. Positive result of an IO requested on-site inspection by the CAB in the 6 months prior to the approval expiration deadline.

Use Case Output

Paper certificate with the inspection result for renewal of an IO approval.

Expiration of IO approval, IO employee authorisation and revocation of the digital certificates in case of a negative inspection result or of a denial of the renewal request.

Description

After a time period of 60 months the approval is to be renewed.

Prior to expiry of the approval the IO is notified by the CAB of the pending expiry. This period of notification is of six months before the approval ends.

IO requests an on-site inspection by the CAB.

The CAB performs the on-site inspection. If the inspection result is negative the CAB revokes the IO approval and the IO employee authorisation(s). The CAB instructs the TC to revoke the IO employee certificate(s).

IO sends all documents by auditable means to the CAB two months before the approval expires.

CAB verifies the documents and checks if the IO has already been approved or rejected by another CAB.

CAB verifies compliance with the concept of legitimate business activity set out in the second paragraph of point 6.3. of Annex X to Regulation (EU) 2018/858. CAB may be assisted by the market surveillance authority from the Member State it is established.

If the criteria for IO approval (see point 4.3.3 of Appendix 3 of Annex X to Regulation (EU) 2018/858) are met the CAB sends the approval inspection paper certificate to the IO.

The CAB notifies by auditable means, the other CABs in the respective country if the IO does not pass the CAB inspection.

CAB verifies that the data provided by the IO is consistent throughout the process. Every employee of an IO who becomes authorised for access to security information following the authorisation inspection described in use case CA6 is registered at the same CAB and TC.

USE CASE CAB 5.CAB handling of IO data

| Actor | IO |
| --- | --- |
| Goal | IO data to be corrected. |
| Use Case Input | IO requests the respective CAB to amend the IO data.
  IO provides appropriate justification for this amendment and submits it to the CAB. |
| Use Case Output | Updated IO data. |
| Description | IO sends all necessary documents to the CAB by auditable means.
  CAB checks the documents. If the CAB determines that the request is justified, the data is amended and the CAB issues the modified paper certificate to the IO. |

Actor

IO

Goal

IO data to be corrected.

Use Case Input

IO requests the respective CAB to amend the IO data.

IO provides appropriate justification for this amendment and submits it to the CAB.

Use Case Output

Updated IO data.

Description

IO sends all necessary documents to the CAB by auditable means.

CAB checks the documents. If the CAB determines that the request is justified, the data is amended and the CAB issues the modified paper certificate to the IO.

USE CASE CAB 6. CAB inspects IO employee for authorisation

| Actor | IO employee |
| --- | --- |
| Goal | Authorisation of an IO employee(s). |
| Use Case Input | Completed inspection application form as required by the CAB. The application form complies with the criteria listed in point 4.3.4. of Appendix 3 of Annex X to Regulation (EU) 2018/858 |
| Use Case Output | Inspection result sent by CAB to TC in order fot the TC to:






  (1) | issue an electronic certificate for the IO employee, |

Actor

IO employee

Goal

Authorisation of an IO employee(s).

Use Case Input

Completed inspection application form as required by the CAB. The application form complies with the criteria listed in point 4.3.4. of Appendix 3 of Annex X to Regulation (EU) 2018/858

Use Case Output

Inspection result sent by CAB to TC in order fot the TC to:

(1)

issue an electronic certificate for the IO employee,

| (2) | create the IO employee’s authorisation record in the database. |
| --- | --- |

(2)

create the IO employee’s authorisation record in the database.

Description

The IO employee sends the application and all necessary documents to the CAB by auditable means.

The CAB checks whether the IO employee had made a previous demand that had been rejected by the CAB itself or any other CAB at Union level.

The CAB checks the documents.

If the criteria for IO employee authorisation (see point 4.3.4. of Appendix 3 of Annex X to Regulation (EU) 2018/858 ) are met the CAB informs the TC in order to issue an electronic certificate (use case TC1).

Every IO employee seeks authorisation with the CAB that its IO is registered with the CAB.

Verification of the accuracy and completeness of information submitted by the IO on behalf of its employees is covered by ISO 17020:2012 clause 7.1.6

USE CASE CAB 7. Pseudonymisation of Personal Data in CAB

| Actor | CAB |
| --- | --- |
| Goal | Pseudonymisation of the personal data from IO employee(s). |
| Use Case Input | First name, last name of the IO employee. |
| Use Case Output | IO employee unique identifier to be used as in the digital certificate. |
| Description | First name, last name of the IO employee is transferred to an IO employee unique identifier that will be used throughout the process for access to security relevant RMI.
  The use case ensures that the processing of personal data complies with EU-rules on the protection of fundamental rights and freedoms of individuals, as provided in Regulation (EU) 2016/679 and Directive 2002/58/EC. |

Actor

CAB

Goal

Pseudonymisation of the personal data from IO employee(s).

Use Case Input

First name, last name of the IO employee.

Use Case Output

IO employee unique identifier to be used as in the digital certificate.

Description

First name, last name of the IO employee is transferred to an IO employee unique identifier that will be used throughout the process for access to security relevant RMI.

The use case ensures that the processing of personal data complies with EU-rules on the protection of fundamental rights and freedoms of individuals, as provided in Regulation (EU) 2016/679 and Directive 2002/58/EC.

USE CASE CAB 8. CAB informs TC in order to issue a digital certificate

| Actor | CAB |
| --- | --- |
| Goal | To provide the IO employee with a digital certificate. |
| Use Case Input | CAB inspection result to TC for an authorised employee. |
| Use Case Output | Secure token with a digital certificate and a separate PIN for the IO employee sent to CAB.
  The IO employee receives the PIN associated with the digital certificate forwarded by the CAB by auditable means. |
| Description | The CAB sends all necessary data to the TC so that the TC can produce the digital certificate, the secure token and the PIN. |

Actor

CAB

Goal

To provide the IO employee with a digital certificate.

Use Case Input

CAB inspection result to TC for an authorised employee.

Use Case Output

Secure token with a digital certificate and a separate PIN for the IO employee sent to CAB.

The IO employee receives the PIN associated with the digital certificate forwarded by the CAB by auditable means.

Description

The CAB sends all necessary data to the TC so that the TC can produce the digital certificate, the secure token and the PIN.

USE CASE CAB 9. CAB inspection of an IO employee for authorisation renewal

| Actor | IO employee |
| --- | --- |
| Goal | Renewal of an employee authorisation |
| Use Case Input | Completed inspection application form as required by the CAB. The application form contains the criteria listed in point 4.3.4. of Appendix 3 of Annex X to Regulation (EU) 2018/858 |
| Use Case Output | Renewal inspection result of an IO employee authorisation. |
| Description | The CAB informs the IO of the date expiry of the employees’ authorisation, 6 months prior to the actual date of the expiration of the authorisation.
  IO employee sends all documents by auditable means to the CAB 2 months before the authorisation expires.
  The authorisation inspection process described in USE CASE CAB 6 is carried out. |

Actor

IO employee

Goal

Renewal of an employee authorisation

Use Case Input

Completed inspection application form as required by the CAB. The application form contains the criteria listed in point 4.3.4. of Appendix 3 of Annex X to Regulation (EU) 2018/858

Use Case Output

Renewal inspection result of an IO employee authorisation.

Description

The CAB informs the IO of the date expiry of the employees’ authorisation, 6 months prior to the actual date of the expiration of the authorisation.

IO employee sends all documents by auditable means to the CAB 2 months before the authorisation expires.

The authorisation inspection process described in USE CASE CAB 6 is carried out.

USE CASE CAB 10. CABs handling of employee’s data

| Actor | IO employee |
| --- | --- |
| Goal | The IO employee data is correct. |
| Use Case Input | Request to the respective CAB to update the IO employee data.
  The appropriate form is completed and signed by the IO employee prior to submission to the CAB. |
| Use Case Output | Updated IO employee data. |
| Description | IO employee sends all necessary documents to the CAB by auditable means.
  The CAB checks the documents.
  If the update request affects the data stored in the digital certificate, the CAB informs the TC in order to issue a new digital certificate (USE CASE TC 1). |

Actor

IO employee

Goal

The IO employee data is correct.

Use Case Input

Request to the respective CAB to update the IO employee data.

The appropriate form is completed and signed by the IO employee prior to submission to the CAB.

Use Case Output

Updated IO employee data.

Description

IO employee sends all necessary documents to the CAB by auditable means.

The CAB checks the documents.

If the update request affects the data stored in the digital certificate, the CAB informs the TC in order to issue a new digital certificate (USE CASE TC 1).

USE CASE CAB 11. CAB procedure for complaint process

| Actor | CAB |
| --- | --- |
| Goal | The CAB has a documented process to receive, evaluate and make decisions on complaints; this process complies with the respective national laws. |
| Use Case Input | Regulations, standards and SERMI scheme. |
| Use Case Output | Documented process for complaints. |
| Description | The CAB develops and documents a process for handling complaints. Complaints are resolved at local level between the CAB and the complainant.
  Parties wishing to make representation with regard to a perceived scheme issue should be able to contact the respective CAB with all necessary information.
  CAB puts in place the necessary procedures and ressources to carry out an on-site inspection where it determines that is appropriate to assess a complaint.
  Complaints that are not resolved at the local level may be referred to the NAB for further consideration in accordance with Article 9(4) of Regulation (EC) No 765/2008. |

Actor

CAB

Goal

The CAB has a documented process to receive, evaluate and make decisions on complaints; this process complies with the respective national laws.

Use Case Input

Regulations, standards and SERMI scheme.

Use Case Output

Documented process for complaints.

Description

The CAB develops and documents a process for handling complaints. Complaints are resolved at local level between the CAB and the complainant.

Parties wishing to make representation with regard to a perceived scheme issue should be able to contact the respective CAB with all necessary information.

CAB puts in place the necessary procedures and ressources to carry out an on-site inspection where it determines that is appropriate to assess a complaint.

Complaints that are not resolved at the local level may be referred to the NAB for further consideration in accordance with Article 9(4) of Regulation (EC) No 765/2008.

USE CASE CAB 12. CAB processes a complaint concerning an IO approval

| Actor | Vehicle manufacturer, TC, relevant authority |
| --- | --- |
| Goal | CAB processes complaints regarding an IO approval.
  IO approval is revoked or confirmed following the process outcome.
  Approval database is kept up to date. |
| Use Case Input | Complaint with the required information according to the process in USE CASE CAB 11. |
| Use Case Output | Rejection of the complaint.
  Or
  Decision to revoke an IO approval as result of a complaint process:






  1) | IO approval revocation documented and IO approval classified as revoked in the approval database. |

Actor

Vehicle manufacturer, TC, relevant authority

Goal

CAB processes complaints regarding an IO approval.

IO approval is revoked or confirmed following the process outcome.

Approval database is kept up to date.

Use Case Input

Complaint with the required information according to the process in USE CASE CAB 11.

Use Case Output

Rejection of the complaint.

Or

Decision to revoke an IO approval as result of a complaint process:

1)

IO approval revocation documented and IO approval classified as revoked in the approval database.

| 2) | IO employee authorisations revoked. |
| --- | --- |

2)

IO employee authorisations revoked.

Description

The CAB investigates the complaint by notably assessing whether the IO has remained compliant with the criteria of point 4.3.3. of Appendix 3 of Annex X to Regulation (EU) 2018/858 and with the concept of legitimate business activity set out in the second paragraph of point 6.3. of Annex X to Regulation (EU) 2018/858. CAB may be assisted by the market surveillance authority from the Member State where it is established.

If the reasons for the complaint cannot not be confirmed the complaint is rejected.

CAB determines whether an on-site inspection is required. The CAB notably assesses whether the IO has remained compliant with the above points.

In case the reasons are confirmed the IO approval is revoked.

In the event of a revocation the CAB:

| 1) | informs the IO that the approval is revoked, |
| --- | --- |

1)

informs the IO that the approval is revoked,

| 2) | informs the respective TC in order to immediately document the approval as revoked and to revoke all digital certificates and authorisations from the IO employees of the respective IO, |
| --- | --- |

2)

informs the respective TC in order to immediately document the approval as revoked and to revoke all digital certificates and authorisations from the IO employees of the respective IO,

| 3) | inform all CABs in its Member State about the revocation. |
| --- | --- |

3)

inform all CABs in its Member State about the revocation.

USE CASE CAB 13. CAB processes a complaint concerning an IO employee’s authorisation

| Actor | Vehicle manufacturer, IO, TC, relevant authority |
| --- | --- |
| Goal | CAB processes complaints regarding an IO employee’s authorisation.
  IO employee’s authorisation is revoked or confirmed by the TC following the process outcome.
  Digital certificate revocation list and authorisation database is updated. |
| Use Case Input | Complaint with the required information according to the process in USE CASE CA11. |
| Use Case Output | Rejection of the complaint.
  Or
  Information of the TC in order to revoke IO employee authorisation after a complaint process:






  1) | IO employee’s digital certificate registered as invalid. |

Actor

Vehicle manufacturer, IO, TC, relevant authority

Goal

CAB processes complaints regarding an IO employee’s authorisation.

IO employee’s authorisation is revoked or confirmed by the TC following the process outcome.

Digital certificate revocation list and authorisation database is updated.

Use Case Input

Complaint with the required information according to the process in USE CASE CA11.

Use Case Output

Rejection of the complaint.

Or

Information of the TC in order to revoke IO employee authorisation after a complaint process:

1)

IO employee’s digital certificate registered as invalid.

| 2) | IO employee’s authorisation status updated as invalid. |
| --- | --- |

2)

IO employee’s authorisation status updated as invalid.

Description

The CAB investigates the complaint. The CAB notably assesses whether the IO employee still meets the criteria of point 4.3.4 of Appendix 3 of Annex X to Regulation (EU) 2018/858 or has participated in activities that would not be compliant with the concept of legitimate business activity set out in the second paragraph of point 6.3. of Annex X to Regulation (EU) 2018/858.

CAB determines whether an on-site inspection is required. CAB may be assisted by the market surveillance authority from the Member State it is established.

If the reasons for the complaint cannot not be confirmed the complaint is rejected.

In case the reasons are confirmed the IO employee authorisation is revoked.

CAB informs the respective TC in order to immediately revoke the employee’s digital certificate and the employee’s authorisation.

The CAB informs the IO about the IO employee revocation.

USE CASE CAB 14. CAB provision of statistics

| Actor | CAB |
| --- | --- |
| Goal | CAB monitors approvals and authorisations. |
| Use Case Input | Result of approval, authorisations and on-site inspections. |
| Use Case Output | CAB provides a report on a quarterly basis in the first year of CAB activity and then annually to SERMI and the Commission (to be published on SERMI website) |
| Description | CAB analyses the results of the approval/authorisation inspection process and provides a report with:






  — | Number of investigations. |

Actor

CAB

Goal

CAB monitors approvals and authorisations.

Use Case Input

Result of approval, authorisations and on-site inspections.

Use Case Output

CAB provides a report on a quarterly basis in the first year of CAB activity and then annually to SERMI and the Commission (to be published on SERMI website)

Description

CAB analyses the results of the approval/authorisation inspection process and provides a report with:

—

Number of investigations.

| — | Quotient: approvals/applications |
| --- | --- |

—

Quotient: approvals/applications

| — | Quotient: authorisations/applications |
| --- | --- |

—

Quotient: authorisations/applications

| — | Most common (3 where applicable) reasons for refusing approval |
| --- | --- |

—

Most common (3 where applicable) reasons for refusing approval

| — | Most common (3 where applicable) reasons for refusing authorisation |
| --- | --- |

—

Most common (3 where applicable) reasons for refusing authorisation

| — | Number and outcome of on-site inspections in the reporting period |
| --- | --- |

—

Number and outcome of on-site inspections in the reporting period

| — | Most common (3 where applicable) reasons for IO approval revocation |
| --- | --- |

—

Most common (3 where applicable) reasons for IO approval revocation

| — | Additionally, the SERMI in cooperation with the Commission can add other Key Performance Indicators (KPI) |
| --- | --- |

—

Additionally, the SERMI in cooperation with the Commission can add other Key Performance Indicators (KPI)

USE CASE IO 1. IO requests for approval

| Actor | IO |
| --- | --- |
| Goal | The IO meets all requirements set out in Appendix 3 of Annex X to Regulation (EU) 2018/858 in order to work with security-related RMI. |
| Use Case Input | All necessary documents and application form (as provided by the CAB) in auditable format. |
| Use Case Output | Approval of IO
  or
  non approval of IO. |
| Description | IO uses the NAB website to obtain a list of accredited CAB.
  The IO contacts the respective CAB.
  The IO receives the application form from the CAB.
  The IO fills in the application form and sends the application form and all necessary documents to the CAB by auditable means.
  When the CAB has inspected the IO the CAB records the approval inspection result in its database in order for the CAB to be able to check in the future whether an IO application has been previously inspected.
  Every employee of an IO is registered at the same CAB.
  Non approval of the IO will be notified by the CAB to all other CABs within their respective NAB’s jurisdiction. |

Actor

IO

Goal

The IO meets all requirements set out in Appendix 3 of Annex X to Regulation (EU) 2018/858 in order to work with security-related RMI.

Use Case Input

All necessary documents and application form (as provided by the CAB) in auditable format.

Use Case Output

Approval of IO

or

non approval of IO.

Description

IO uses the NAB website to obtain a list of accredited CAB.

The IO contacts the respective CAB.

The IO receives the application form from the CAB.

The IO fills in the application form and sends the application form and all necessary documents to the CAB by auditable means.

When the CAB has inspected the IO the CAB records the approval inspection result in its database in order for the CAB to be able to check in the future whether an IO application has been previously inspected.

Every employee of an IO is registered at the same CAB.

Non approval of the IO will be notified by the CAB to all other CABs within their respective NAB’s jurisdiction.

USE CASE IO 2. IO registration at the vehicle manufacturer

(see EN/ISO 18541-1:2014, use case 1.1)

USE CASE IO 3. IO business ceases to trade

| Actor | IO |
| --- | --- |
| Goal | Approval database is updated by CAB. |
| Use Case Input | The Information about the IO and its cessation of trade
  or IO informs the CAB about discontinuance of business. |
| Use Case Output | An update of the approval database, together with the revocation of all related certificates and authorisations issued to the employees of that IO. |
| Description | The CAB receives information about the IO trade cessation.
  The CAB informs the TC in order to revoke all certificates and authorisations issued to the employees of that IO. |

Actor

IO

Goal

Approval database is updated by CAB.

Use Case Input

The Information about the IO and its cessation of trade

or IO informs the CAB about discontinuance of business.

Use Case Output

An update of the approval database, together with the revocation of all related certificates and authorisations issued to the employees of that IO.

Description

The CAB receives information about the IO trade cessation.

The CAB informs the TC in order to revoke all certificates and authorisations issued to the employees of that IO.

USE CASE IO 4. Parts ordering

| Actor | IO |
| --- | --- |
| Goal | Supply an ordered part to the IO. |
| Use Case Input | Authentication of IO employee.
  Security-related parts order. |
| Use Case Output | Security-related part. |
| Description | Vehicle manufacturer offers security-related parts ordering facility to authorised IO employees.
  Manufacturers offers an online ordering facility for security-related parts using the digital certificate to confirm the identity of the person requiring the part. Alternatively, they may require security-related parts to be obtained from authorised dealers where currently established authentication procedures are in place.
  Security parts are delivered by vehicle manufacturers or their agents/authorised dealers in a timely manner to the IOs. |

Actor

IO

Goal

Supply an ordered part to the IO.

Use Case Input

Authentication of IO employee.

Security-related parts order.

Use Case Output

Security-related part.

Description

Vehicle manufacturer offers security-related parts ordering facility to authorised IO employees.

Manufacturers offers an online ordering facility for security-related parts using the digital certificate to confirm the identity of the person requiring the part. Alternatively, they may require security-related parts to be obtained from authorised dealers where currently established authentication procedures are in place.

Security parts are delivered by vehicle manufacturers or their agents/authorised dealers in a timely manner to the IOs.

USE CASE IO 5. IO receives secure token

| Actor | CAB |
| --- | --- |
| Goal | IO receives a secure token with a digital certificate. |
| Use Case Input | Secure token with a digital certificate forwarded by CAB. |
| Use Case Output | Secure token with a digital certificate received by IO. |
| Description | The IO receives an electronic certificate from TC.
  The IO delivers the electronic certificate to the respective IO employee (see USE CASE EM 6). |

Actor

CAB

Goal

IO receives a secure token with a digital certificate.

Use Case Input

Secure token with a digital certificate forwarded by CAB.

Use Case Output

Secure token with a digital certificate received by IO.

Description

The IO receives an electronic certificate from TC.

The IO delivers the electronic certificate to the respective IO employee (see USE CASE EM 6).

USE CASE IO 6. IO record keeping requirements

| Actor | IO |
| --- | --- |
| Goal | Auditable record of transactions kept by the IO. |
| Use Case Input | Documents/Information provided by the repair order. |
| Use Case Output | Audit trail and details of the repair job. |
| Description | The IO stores data that could be required in the event of an audit.
  Before issuing a repair order, the IO makes sure that the following information is gathered:






  1) | Identification of the customer |

Actor

IO

Goal

Auditable record of transactions kept by the IO.

Use Case Input

Documents/Information provided by the repair order.

Use Case Output

Audit trail and details of the repair job.

Description

The IO stores data that could be required in the event of an audit.

Before issuing a repair order, the IO makes sure that the following information is gathered:

1)

Identification of the customer

| 2) | Identification of the vehicle (Vehicle in place) |
| --- | --- |

2)

Identification of the vehicle (Vehicle in place)

| 3) | Proof of the authority of the customer to request the work to the vehicle. |
| --- | --- |

3)

Proof of the authority of the customer to request the work to the vehicle.

USE CASE IO 7. Cessation of employment of an IO employee at an IO

| Actor | IO |
| --- | --- |
| Goal | Approval/Authorisation data at the CAB is kept up-to-date |
| Use Case Input | Information about end of contract with IO employee |
| Use Case Output | Updated authorisation data base and request to TC to revoke the respective digital certificate. |
| Description | The IO informs the CAB about the change of employment within three working days.
  The CAB informs the TC in order to update the authorisation data base and to revoke the respective digital certificate.
  The IO is informed of these changes. |

Actor

IO

Goal

Approval/Authorisation data at the CAB is kept up-to-date

Use Case Input

Information about end of contract with IO employee

Use Case Output

Updated authorisation data base and request to TC to revoke the respective digital certificate.

Description

The IO informs the CAB about the change of employment within three working days.

The CAB informs the TC in order to update the authorisation data base and to revoke the respective digital certificate.

The IO is informed of these changes.

USE CASE IO 8. Procedural requirements for security-related operations

1.   General behaviour

Only IO employees of the approved IO, who have been successfully authorised and are in possession of an authorisation inspection certificate and a valid electronic certificate issued by the corresponding trust center, will have access security-related RMI.

The IO employee is responsible for the correct use of the Certificate and PIN.

The IOs and their employees follow the procedures to deal with the end user device (PC, Laptop, etc.) as specified in ISO 18541-2:2014

2.   Procedure to conduct a security-related operation

If an employee carries out a security related software update or needs other security related repair and maintenance information for a vehicle operation, the procedure described in point 3 to 5 and shown in the below figure 1 is followed.

Figure 1

Basic outline of the procedure to conduct a security-related operation

Image 1

3.   Customer verification

The IO employee verifies the identification of the customer that has brought in the vehicle.

Possible sources of identification: Identity card, passport, driver’s licence, roadside member card.

The IO is responsible for recording the identity information.

The information provided in figure 2 may be used for this process.

Figure 2

Field reference for customer inspection from the vehicle registration certificate

| Vehicle registration documents |
| --- |
| Data (Part I) | Field (Part I) |
| Surname(s) or business name | C.1.1 |
| Other name(s) or initial(s) (where appropriate) | C.1.2 |
| Address in the Member State of registration on the date of issue of the document | C.1.3 |
| Data (Part II) | Field (Part II) |
| Surname(s) or business name | C.3.1 and C.6.1 |
| Other name(s) or initial(s) (where appropriate) | C.3.2 and C.6.2 |
| Address in the Member State of registration on the date of issue of the document | C.3.3 and C.6.3 |

Vehicle registration documents

Data (Part I)

Field (Part I)

Surname(s) or business name

C.1.1

Other name(s) or initial(s) (where appropriate)

C.1.2

Address in the Member State of registration on the date of issue of the document

C.1.3

Data (Part II)

Field (Part II)

Surname(s) or business name

C.3.1 and C.6.1

Other name(s) or initial(s) (where appropriate)

C.3.2 and C.6.2

Address in the Member State of registration on the date of issue of the document

C.3.3 and C.6.3

Where possible, the IO employee notes the following data:

| (1) | Name and surname of the customer. |
| --- | --- |

(1)

Name and surname of the customer.

| (2) | Identity card/passport number and/or number of the roadside member card. |
| --- | --- |

(2)

Identity card/passport number and/or number of the roadside member card.

| (3) | Fleet management or rental car company name. |
| --- | --- |

(3)

Fleet management or rental car company name.

| (4) | Contact name of the respective company. |
| --- | --- |

(4)

Contact name of the respective company.

| (5) | Address of the respective company. |
| --- | --- |

(5)

Address of the respective company.

| (6) | Telephone number of the respective company. |
| --- | --- |

(6)

Telephone number of the respective company.

| (7) | Driver’s company identification. |
| --- | --- |

(7)

Driver’s company identification.

This additional information is requested in the circumstances where the customer will not have vehicle registration documents

| (8) | Fleet management. |
| --- | --- |

(8)

Fleet management.

| (9) | Rental Cars. |
| --- | --- |

(9)

Rental Cars.

| (10) | Loan. |
| --- | --- |

(10)

Loan.

4.   Vehicle verification

The IO employee makes sure that the vehicle identification number (VIN) of the vehicle is the same as the Vehicle Identification Number (VIN) on the registration documents (see figure 3).

Figure 3

Community codes from the registration documents for the vehicle inspection

| Vehicle registration documents |
| --- |
| Data (Part I) | Field (Part I) |
| Vehicle identification number | E |

Vehicle registration documents

Data (Part I)

Field (Part I)

Vehicle identification number

E

5.   Issue the repair order

The next step is to issue the repair order by using a dealer management system. The repair order contains at least the data from figure 4 and the data used to identify the customer and their authority.

Figure 4

Community codes from the registration documents for issuing a repair order

| Vehicle registration documents |
| --- |
| Data | Field |
| Registration number | A |
| Make | D.1 |
| Type, variant, version | D.2 |

Vehicle registration documents

Data

Field

Registration number

A

Make

D.1

Type, variant, version

D.2

The current value of the odometer and the reason for the repair is noted and the repair order needs to be signed by the customer (owner and/or the person who brings the vehicle to the IO). Figure 5 describes the procedure for IO and employee.

Signed repair orders are kept for a minimum of 5 years by the IO.

Figure 5

Procedural requirements for IO

Image 2

USE CASE EM 1. IO employee requests authorisation

| Actor | IO employee |
| --- | --- |
| Goal | IO employee receives authorisation to work with security-related RMI. |
| Use Case Input | IO employee meets all requirements specified in the Appendix.
  IO employee fills in the application form from the CAB. |
| Use Case Output | Authorisation of an IO employee, so that the IO employee can receive the digital certificate to access security-related RMI. |
| Description | The IO employee receives the application form from the CAB if the IO has requested the authorisation of the respective employee.
  The IO employee completes the application form and sends the application form and all necessary documents to the CAB by auditable means.
  The CAB issues an authorisation inspection certificate to the IO employee and communicates the positive inspection result to the TC in order to create an authorisation record and to issue a digital certificate for this IO employee.
  The CAB also keeps trace of the IO employee rejection if the inspection is not successful. |

Actor

IO employee

Goal

IO employee receives authorisation to work with security-related RMI.

Use Case Input

IO employee meets all requirements specified in the Appendix.

IO employee fills in the application form from the CAB.

Use Case Output

Authorisation of an IO employee, so that the IO employee can receive the digital certificate to access security-related RMI.

Description

The IO employee receives the application form from the CAB if the IO has requested the authorisation of the respective employee.

The IO employee completes the application form and sends the application form and all necessary documents to the CAB by auditable means.

The CAB issues an authorisation inspection certificate to the IO employee and communicates the positive inspection result to the TC in order to create an authorisation record and to issue a digital certificate for this IO employee.

The CAB also keeps trace of the IO employee rejection if the inspection is not successful.

USE CASE EM 2. IO employee registration at a vehicle manufacturer

(see EN/ISO 18541-1:2014 use case 1.2)

| Actor | IO or IO employee |
| --- | --- |
| Goal | To register IO employee for use of the vehicle manufacturer RMI system as defined by the IO. |
| Use Case Input | - Request from the IO to register a new IO employee. User id and password of the IO are necessary.
  - An IO employee’s request, indicating that they are associated with an IO, and are requesting confirmation from the IO legal representative to complete registration |
| Use Case Output | IO’s employee registered as an authorised user in the VM RMI system. |
| Description | The vehicle manufacturer requests the IO to confirm the validity of the IO data.
  The vehicle manufacturer accepts IO’s employee as a user and informs the user accordingly.
  The vehicle manufacturer RMI system asks the user to choose a User ID and either assigns an initial password to the user or allows them to enter one that satisfies the vehicle manufacturer’s password security requirements.
  The vehicle manufacturer may charge a reasonable registration fee to the IO. |

Actor

IO or IO employee

Goal

To register IO employee for use of the vehicle manufacturer RMI system as defined by the IO.

Use Case Input

- Request from the IO to register a new IO employee. User id and password of the IO are necessary.

- An IO employee’s request, indicating that they are associated with an IO, and are requesting confirmation from the IO legal representative to complete registration

Use Case Output

IO’s employee registered as an authorised user in the VM RMI system.

Description

The vehicle manufacturer requests the IO to confirm the validity of the IO data.

The vehicle manufacturer accepts IO’s employee as a user and informs the user accordingly.

The vehicle manufacturer RMI system asks the user to choose a User ID and either assigns an initial password to the user or allows them to enter one that satisfies the vehicle manufacturer’s password security requirements.

The vehicle manufacturer may charge a reasonable registration fee to the IO.

USE CASE EM 3. Employee access to security-related RMI

(see EN/ISO 18541:2014 all parts)

USE CASE EM 4. Receipt of the PIN from the CAB

| Actor | CAB |
| --- | --- |
| Goal | Supply to the IO employee the PIN letter for the secure token with the digital certificate. |
| Use Case Input | PIN from TC. |
| Use Case Output | PIN letter delivered to IO employee. |
| Description | The CAB prepares a PIN letter with the PIN supplied by the TC for this identity and sends it to the IO employee home address by auditable means. |

Actor

CAB

Goal

Supply to the IO employee the PIN letter for the secure token with the digital certificate.

Use Case Input

PIN from TC.

Use Case Output

PIN letter delivered to IO employee.

Description

The CAB prepares a PIN letter with the PIN supplied by the TC for this identity and sends it to the IO employee home address by auditable means.

USE CASE EM 5. IO employee receives the digital certificate from IO

| Actor | IO, IO employee |
| --- | --- |
| Goal | Supply the electronic certificate to the IO employee. |
| Use Case Input | Electronic certificate. |
| Use Case Output | IO employee receives the electronic certificate from IO. |
| Description | The IO employee receives the electronic certificate from the IO with the corresponding identity. |

Actor

IO, IO employee

Goal

Supply the electronic certificate to the IO employee.

Use Case Input

Electronic certificate.

Use Case Output

IO employee receives the electronic certificate from IO.

Description

The IO employee receives the electronic certificate from the IO with the corresponding identity.

USE CASE TC 1. Trust Center creates and delivers certificate

| Actor | CAB |
| --- | --- |
| Goal | CAB receives certificates and PIN for distribution to IO employees |
| Use Case Input | Request for creation of a digital certificate. |
| Use Case Output | Digital certificate and PIN. |
| Description | The CAB contacts the TC (see USE CASE CAB 11 for procedure).
  The TC creates the digital certificate and provides it to the CAB for distribution to the IO employee by using the following procedure:






  (1) | TC sends the personalised digital certificate to the CAB by auditable means. |

Actor

CAB

Goal

CAB receives certificates and PIN for distribution to IO employees

Use Case Input

Request for creation of a digital certificate.

Use Case Output

Digital certificate and PIN.

Description

The CAB contacts the TC (see USE CASE CAB 11 for procedure).

The TC creates the digital certificate and provides it to the CAB for distribution to the IO employee by using the following procedure:

(1)

TC sends the personalised digital certificate to the CAB by auditable means.

| (2) | The pin code is sent by auditable means to the CAB separately to the digital certificate |
| --- | --- |

(2)

The pin code is sent by auditable means to the CAB separately to the digital certificate

USE CASE TC 2. Trust Center assesses digital certificate’s validity

| Actor | Vehicle manufacturer |
| --- | --- |
| Goal | Validation of the status of a digital certificate. |
| Use Case Input | Digital certificate serial number. |
| Use Case Output | Status supplied by TC is the following: | 0 → Suspended |

Actor

Vehicle manufacturer

Goal

Validation of the status of a digital certificate.

Use Case Input

Digital certificate serial number.

Use Case Output

Status supplied by TC is the following:

0 → Suspended

| | 1 → Ok |
| --- | --- |

1 → Ok

| | 2 → Revoked |
| --- | --- |

2 → Revoked

| | 3 → Unknown |
| --- | --- |

3 → Unknown

Description

Vehicle manufacturer asks the TC for the status of employees’ digital certificate for authentication using the communication defined in OCSP standard. The TC responds to the OCSP-responder status.

The TC maintains for this purpose a revocation database according to the OCSP standard.

USE CASE TC 3. Trust Center provision of IO employee authorisation status

| Actor | Vehicle manufacturer |
| --- | --- |
| Goal | Validation of authorisation status using SOAP/RESTful API. |
| Use Case Input | Digital certificate serial number and attributes. |
| Use Case Output | Status replied by TC is the following: | Validity |

Actor

Vehicle manufacturer

Goal

Validation of authorisation status using SOAP/RESTful API.

Use Case Input

Digital certificate serial number and attributes.

Use Case Output

Status replied by TC is the following:

Validity

| | IOEUID |
| --- | --- |

IOEUID

| | IOUID |
| --- | --- |

IOUID

| | CABUID |
| --- | --- |

CABUID

Description

Vehicle manufacturer asks for IO employees’ authorisation status.

TC responds to the authorisation status.

USE CASE TC 4. Trust Center suspension of issued certificates

| Actor | Vehicle manufacturer, IO, CAB, relevant authority |
| --- | --- |
| Goal | Digital certificate suspension to prevent future misuse by a certificate owner in case of a detected misuse. |
| Use Case Input | Triggered by an employee of the actor with a serial number or by other means to identify the certificate. |
| Use Case Output | Suspension of certificate, status OCSP updated.
  TC sends information to the CAB.
  Information to IO employee as to the reason for the digital certificate suspension. |
| Description | Appropriate employee of the respective participant. This employee of a CAB sends a message to the TC by auditable means.
  The message contains:






  — | Letterhead of the respective participant. |

Actor

Vehicle manufacturer, IO, CAB, relevant authority

Goal

Digital certificate suspension to prevent future misuse by a certificate owner in case of a detected misuse.

Use Case Input

Triggered by an employee of the actor with a serial number or by other means to identify the certificate.

Use Case Output

Suspension of certificate, status OCSP updated.

TC sends information to the CAB.

Information to IO employee as to the reason for the digital certificate suspension.

Description

Appropriate employee of the respective participant. This employee of a CAB sends a message to the TC by auditable means.

The message contains:

—

Letterhead of the respective participant.

| — | Serial number or other means to identify the certificate. |
| --- | --- |

—

Serial number or other means to identify the certificate.

| — | Transaction number from the respective participant, if necessary. |
| --- | --- |

—

Transaction number from the respective participant, if necessary.

The suspension processes immediately upon receipt of the suspension request.

The TC inspects the origin of the message:

| — | TC suspends the digital certificate (updated OCSP). |
| --- | --- |

—

TC suspends the digital certificate (updated OCSP).

| — | TC informs the CAB about the suspension to initiate the complaint process in written or electronic form. |
| --- | --- |

—

TC informs the CAB about the suspension to initiate the complaint process in written or electronic form.

USE CASE TC 5. Trust Center suspension of an approval of an IO

| Actor | Vehicle manufacturer, CAB, relevant authority |
| --- | --- |
| Goal | Suspension of the authorisation of all employees for a specific IO (plus all authorisations belonging to that IO) to prevent future misuses by the employees of an IO in case of detected misuses. |
| Use Case Input | Requested by employee representative of an authenticated actor (i.e. with an appropriate certificate) e.g. an employee of a CAB who is responsible for the suspension with the IO unique identifier or other means to identify the IO. |
| Use Case Output | Suspended authorisation(s) updated
  TC sends information to the CAB |
| Description | Authenticated employee of the respective actor sends a message to the TC by auditable means.
  The message contains:






  — | Letterhead of the respective participant. |

Actor

Vehicle manufacturer, CAB, relevant authority

Goal

Suspension of the authorisation of all employees for a specific IO (plus all authorisations belonging to that IO) to prevent future misuses by the employees of an IO in case of detected misuses.

Use Case Input

Requested by employee representative of an authenticated actor (i.e. with an appropriate certificate) e.g. an employee of a CAB who is responsible for the suspension with the IO unique identifier or other means to identify the IO.

Use Case Output

Suspended authorisation(s) updated

TC sends information to the CAB

Description

Authenticated employee of the respective actor sends a message to the TC by auditable means.

The message contains:

—

Letterhead of the respective participant.

| — | IO unique identifier or other means to identify the IO. |
| --- | --- |

—

IO unique identifier or other means to identify the IO.

| — | Transaction number from the respective participant, if necessary. |
| --- | --- |

—

Transaction number from the respective participant, if necessary.

| — | Reason of suspension. |
| --- | --- |

—

Reason of suspension.

The suspension is processed upon receipt of the suspension request.

The TC verifies the origin of the message.

TC suspends all authorisations belonging to the IO.

The TC informs the CAB about the suspension to initiate the complaint process in written or electronic form.

USE CASE TC 6. Trust Centers suspends IO employee’s authorisation

| Actor | Vehicle manufacturer, IO, CAB, relevant authorities |
| --- | --- |
| Goal | Suspension of authorisation of an IO employee to prevent future misuses in case of a detected misuse. |
| Use Case Input | Requested by a representative of an authenticated participant. |
| Use Case Output | Suspension of authorisation, updated authorisation database.
  Suspension notification to the CAB.
  Information to IO employee on the reason for the authorisation suspension. |
| Description | Authenticated employee of the respective participant e.g. an employee of a CAB who is responsible for the suspension sends information to the TC (using a common method).
  The information contains:






  — | Letterhead of the respective participant. |

Actor

Vehicle manufacturer, IO, CAB, relevant authorities

Goal

Suspension of authorisation of an IO employee to prevent future misuses in case of a detected misuse.

Use Case Input

Requested by a representative of an authenticated participant.

Use Case Output

Suspension of authorisation, updated authorisation database.

Suspension notification to the CAB.

Information to IO employee on the reason for the authorisation suspension.

Description

Authenticated employee of the respective participant e.g. an employee of a CAB who is responsible for the suspension sends information to the TC (using a common method).

The information contains:

—

Letterhead of the respective participant.

| — | IO unique identifier. |
| --- | --- |

—

IO unique identifier.

| — | IO employee unique identifier. |
| --- | --- |

—

IO employee unique identifier.

| — | Transaction number from the respective actor, if necessary. |
| --- | --- |

—

Transaction number from the respective actor, if necessary.

| — | Reason of suspension. |
| --- | --- |

—

Reason of suspension.

The suspension is processed upon receipt of the suspension request.

The TC verifies the origin of the information.

TC suspends an authorisation belonging to an employee.

TC informs the CAB about the suspension to initiate the complaint process in written or electronic form.

USE CASE TC 7. Trust Centers revokes IO approval

| Actor | CAB |
| --- | --- |
| Goal | Approval data base is kept up to date. |
| Use Case Input | CAB notifies the decision to revoke the IO approval. |
| Use Case Output | IO approval classified as revoked in database. |
| Description | The TC will update the approval data base after receipt of the CAB notification of the decision to revoke a particular IO. The IO approval is classified as revoked.
  The digital certificates and the authorisations of all IO employees of this IO are classified as revoked in the corresponding data bases. |

Actor

CAB

Goal

Approval data base is kept up to date.

Use Case Input

CAB notifies the decision to revoke the IO approval.

Use Case Output

IO approval classified as revoked in database.

Description

The TC will update the approval data base after receipt of the CAB notification of the decision to revoke a particular IO. The IO approval is classified as revoked.

The digital certificates and the authorisations of all IO employees of this IO are classified as revoked in the corresponding data bases.

USE CASE TC 8. Trust Centers revokes IO employee’s authorisation

| Actor | CAB |
| --- | --- |
| Goal | Digital certificate and authorisation data bases are kept up to date. |
| Use Case Input | CAB notifies the decision to revoke the IO authorisation. |
| Use Case Output | IO’s employee digital certificate is classified as revoked.
  IO employee’s authorisation is classified as revoked. |
| Description | The TC will update the digital certificate and the authorisation data bases after receipt of the CAB notification of the decision to revoke a particular IO employee.
  The digital certificate and the authorisation of the IO employees of this IO are classified as revoked in the corresponding data bases. |

Actor

CAB

Goal

Digital certificate and authorisation data bases are kept up to date.

Use Case Input

CAB notifies the decision to revoke the IO authorisation.

Use Case Output

IO’s employee digital certificate is classified as revoked.

IO employee’s authorisation is classified as revoked.

Description

The TC will update the digital certificate and the authorisation data bases after receipt of the CAB notification of the decision to revoke a particular IO employee.

The digital certificate and the authorisation of the IO employees of this IO are classified as revoked in the corresponding data bases.

USE CASE TC 9. Trust Center provides an environment to test the readiness of a certificate and the TC provided Multi Factor Authentication method

| Actor | IO employee |
| --- | --- |
| Goal | Confirmation to the IO employee that the electronic certificate works. |
| Use Case Input | IO employee electronic certificate + PIN and Multi Factor Authentication on client device(s). |
| Use Case Output | Test ok / not ok.
  Message with failure details in case of not ok. |
| Description | The employee connects to the website of the TC.
  The IO employee logs on to the TC test website with his electronic certificate.
  The IO employee sees result of test (ok/not ok.)
  The TC logs actions for further support process (e.g. vehicle manufacturer). |

Actor

IO employee

Goal

Confirmation to the IO employee that the electronic certificate works.

Use Case Input

IO employee electronic certificate + PIN and Multi Factor Authentication on client device(s).

Use Case Output

Test ok / not ok.

Message with failure details in case of not ok.

Description

The employee connects to the website of the TC.

The IO employee logs on to the TC test website with his electronic certificate.

The IO employee sees result of test (ok/not ok.)

The TC logs actions for further support process (e.g. vehicle manufacturer).

USE CASE TC 10. TC provides an interface regarding the specifications of use case CA1

| Actor | TC |
| --- | --- |
| Goal | TC support of standard communication interface between TC and CAB (web service). |
| Use Case Input | Information and known standards to develop a communication interface (web service). |
| Use Case Output | Communication interface between TC and CAB. |
| Description | The TC develops and runs a standard communication interface for the CAB. The CAB uses this standard communication interface. It may be used for ordering the digital certificate. |

Actor

TC

Goal

TC support of standard communication interface between TC and CAB (web service).

Use Case Input

Information and known standards to develop a communication interface (web service).

Use Case Output

Communication interface between TC and CAB.

Description

The TC develops and runs a standard communication interface for the CAB. The CAB uses this standard communication interface. It may be used for ordering the digital certificate.

USE CASE TC 11. TC provides test users with test certificates to validate the communication (OCSP & SOAP/RESTful API)

| Actor | Vehicle manufacturer |
| --- | --- |
| Goal | The functional communication between a vehicle manufacturer and a TC. |
| Use Case Input | Request to the TC interface. |
| Use Case Output | Test data: test users, test certificates, test authorisation database content. |
| Description | Vehicle manufacturer requests for test data in all appropriate languages for all appropriate markets.
  The TC sends information (test users/test certificates) which covers all possible testing outcomes to the vehicle manufacturer. |

Actor

Vehicle manufacturer

Goal

The functional communication between a vehicle manufacturer and a TC.

Use Case Input

Request to the TC interface.

Use Case Output

Test data: test users, test certificates, test authorisation database content.

Description

Vehicle manufacturer requests for test data in all appropriate languages for all appropriate markets.

The TC sends information (test users/test certificates) which covers all possible testing outcomes to the vehicle manufacturer.

USE CASE VM 1. Investigation of an IO approval

| Actor | Vehicle manufacturer (VM) |
| --- | --- |
| Goal | To investigate if an existing approval should remain valid. |
| Use Case Input | Vehicle manufacturer notices possible abuse/indication of abuse. |
| Use Case Output | The possible abuse or indication of abuse is confirmed or rejected. |
| Description | In case of non-compliance with the criteria of point 4.3.3 of Appendix 3 of Annex X to Regulation (EU) 2018/858 or with the concept of legitimate business activity set out in the second paragraph of point 6.3. of Annex X to Regulation (EU) 2018/858, the vehicle manufacturer reports this non-compliance of an IO to the CAB.
  The vehicle manufacturer starts the complaint process by informing the respective CAB.
  The vehicle manufacturer is free to notify the relevant authorities, if applicable. |

Actor

Vehicle manufacturer (VM)

Goal

To investigate if an existing approval should remain valid.

Use Case Input

Vehicle manufacturer notices possible abuse/indication of abuse.

Use Case Output

The possible abuse or indication of abuse is confirmed or rejected.

Description

In case of non-compliance with the criteria of point 4.3.3 of Appendix 3 of Annex X to Regulation (EU) 2018/858 or with the concept of legitimate business activity set out in the second paragraph of point 6.3. of Annex X to Regulation (EU) 2018/858, the vehicle manufacturer reports this non-compliance of an IO to the CAB.

The vehicle manufacturer starts the complaint process by informing the respective CAB.

The vehicle manufacturer is free to notify the relevant authorities, if applicable.

USE CASE VM 2. Investigation of an IO employee authorisation

| Actor | Vehicle manufacturer |
| --- | --- |
| Goal | To investigate if existing authorisation should remain valid. |
| Use Case Input | Vehicle manufacturer notices possible abuse/indication of abuse. |
| Use Case Output | The possible abuse or indication of abuse is confirmed or rejected. |
| Description | In case of non-compliance with the criteria of point 4.3.3 of Appendix 3 of Annex X to Regulation (EU) 2018/858 or with the concept of legitimate business activity set out in the second paragraph of point 6.3. of Annex X to Regulation (EU) 2018/858, the vehicle manufacturer reports these indications of abuse to the CAB. The vehicle manufacturer may where necessary block the IO employee internally.
  The vehicle manufacturer starts the complaint process by informing the respective CAB.
  The vehicle manufacturer is free to notify the relevant authorities. |

Actor

Vehicle manufacturer

Goal

To investigate if existing authorisation should remain valid.

Use Case Input

Vehicle manufacturer notices possible abuse/indication of abuse.

Use Case Output

The possible abuse or indication of abuse is confirmed or rejected.

Description

In case of non-compliance with the criteria of point 4.3.3 of Appendix 3 of Annex X to Regulation (EU) 2018/858 or with the concept of legitimate business activity set out in the second paragraph of point 6.3. of Annex X to Regulation (EU) 2018/858, the vehicle manufacturer reports these indications of abuse to the CAB. The vehicle manufacturer may where necessary block the IO employee internally.

The vehicle manufacturer starts the complaint process by informing the respective CAB.

The vehicle manufacturer is free to notify the relevant authorities.

USE CASE VM 3. Vehicle manufacturer blocks IO's access

| Actor | Vehicle manufacturer, CAB |
| --- | --- |
| Goal | IO (and subsequently all connected IO employees) is denied access to security-related information. |
| Use Case Input | Vehicle manufacturer registers IO non-compliance regarding the terms and conditions. |
| Use Case Output | Access to security information blocked for the IO (and all the IO employees). |
| Description | Following its investigation, the CAB has determined that the approval should be revoked The vehicle manufacturer can subsequently block the IO access internally. The vehicle manufacturer blocks the access to security information for that IO. |

Actor

Vehicle manufacturer, CAB

Goal

IO (and subsequently all connected IO employees) is denied access to security-related information.

Use Case Input

Vehicle manufacturer registers IO non-compliance regarding the terms and conditions.

Use Case Output

Access to security information blocked for the IO (and all the IO employees).

Description

Following its investigation, the CAB has determined that the approval should be revoked The vehicle manufacturer can subsequently block the IO access internally. The vehicle manufacturer blocks the access to security information for that IO.

USE CASE VM 4. Vehicle manufacturer blocks IO employee's access

| Actor | vehicle manufacturer, CAB |
| --- | --- |
| Goal | Vehicle manufacturers have the opportunity to block an IO employee from access to security-related RMI. |
| Use Case Input | Vehicle manufacturer registers reason to block IO employee. |
| Use Case Output | Access to security information blocked for the IO employee. |
| Description | Following its investigation, the CAB has determined that the approval should be revoked. The vehicle manufacturer can subsequently block the employee access internally.
  The vehicle manufacturer blocks the access to security information for that IO employee. |

Actor

vehicle manufacturer, CAB

Goal

Vehicle manufacturers have the opportunity to block an IO employee from access to security-related RMI.

Use Case Input

Vehicle manufacturer registers reason to block IO employee.

Use Case Output

Access to security information blocked for the IO employee.

Description

Following its investigation, the CAB has determined that the approval should be revoked. The vehicle manufacturer can subsequently block the employee access internally.

The vehicle manufacturer blocks the access to security information for that IO employee.

USE CASE VM 5. Vehicle manufacturer inspections authorisation status of IO employee

| Actor | Vehicle manufacturer |
| --- | --- |
| Goal | Vehicle manufacturer verifies the authorisation status when the employee uses the certificate for authentication to access security-related RMI. |
| Use Case Input | Content information of the employee electronic certificate. |
| Use Case Output | Authorisation status |
| Description | The vehicle manufacturer verifies the validity of the certificate (TC, OCSP.)
  The vehicle manufacturer verifies if the employee is blocked (vehicle manufacturer internal).
  The vehicle manufacturer verifies the validity of the employee authorisation:






  — | The vehicle manufacturer contacts the TC by using the content information of the employee electronic certificate. |

Actor

Vehicle manufacturer

Goal

Vehicle manufacturer verifies the authorisation status when the employee uses the certificate for authentication to access security-related RMI.

Use Case Input

Content information of the employee electronic certificate.

Use Case Output

Authorisation status

Description

The vehicle manufacturer verifies the validity of the certificate (TC, OCSP.)

The vehicle manufacturer verifies if the employee is blocked (vehicle manufacturer internal).

The vehicle manufacturer verifies the validity of the employee authorisation:

—

The vehicle manufacturer contacts the TC by using the content information of the employee electronic certificate.

| — | The TC replies with the current authentication status. |
| --- | --- |

—

The TC replies with the current authentication status.

USE CASE VM 6. Download of implementation guide from SERMI website by vehicle manufacturer (currently OCSP & SOAP/RESTful API)

| Actor | Vehicle manufacturer |
| --- | --- |
| Goal | Compliant inspection IO employee granted an authorisation electronic certificate and authorisation inspection certificate. |
| Use Case Input | Request for implementation guide. |
| Use Case Output | Downloaded implementation guide. |
| Description | Download of implementation guide from the SERMI website. The vehicle manufacturer inspects the IO employee electronic certificate and authorisation by using the implementation guide (OCSP, SOAP/RESTful API). |

Actor

Vehicle manufacturer

Goal

Compliant inspection IO employee granted an authorisation electronic certificate and authorisation inspection certificate.

Use Case Input

Request for implementation guide.

Use Case Output

Downloaded implementation guide.

Description

Download of implementation guide from the SERMI website. The vehicle manufacturer inspects the IO employee electronic certificate and authorisation by using the implementation guide (OCSP, SOAP/RESTful API).

USE CASE VM 7. Vehicle manufacturer supplies information to local authorities

| Actor | Vehicle manufacturer |
| --- | --- |
| Goal | Supplying information to relevant authority. |
| Use Case Input | Customer contacts local authorities.
  Inquiry by relevant authorities via manual process (no additional IT service required). |
| Use Case Output | Information about the vehicle (e.g. history of actions performed on a specific VIN). |
| Description | Customer reports an offence punishable by national laws. Gives VIN or transaction information.
  The competent authority contacts the specific vehicle manufacturer with an inquiry regarding a specific VIN.
  In the case of a stolen vehicle, if the vehicle is recovered the relevant authority informs the vehicle manufacturer and the status of the vehicle is restored to normal (audit trail contains information about event). |

Actor

Vehicle manufacturer

Goal

Supplying information to relevant authority.

Use Case Input

Customer contacts local authorities.

Inquiry by relevant authorities via manual process (no additional IT service required).

Use Case Output

Information about the vehicle (e.g. history of actions performed on a specific VIN).

Description

Customer reports an offence punishable by national laws. Gives VIN or transaction information.

The competent authority contacts the specific vehicle manufacturer with an inquiry regarding a specific VIN.

In the case of a stolen vehicle, if the vehicle is recovered the relevant authority informs the vehicle manufacturer and the status of the vehicle is restored to normal (audit trail contains information about event).

USE CASE. Technical requirements

1.1.   Secure communication requirements

Any digital communication or transfer of identification, approval and authorization data among CAB, TC and VM is done by secure means i.e. using https-ssl/tls and mutual authentication based on X.509 certificates.

1.2.   Data management description

In the SERMI-scheme only the CAB is collecting and using personal information: The following diagram describes a minimal set of attributes that are to be stored in each entity information system in order to be able to implement defined processes and use cases.

Figure 6

Example of data storage as per ISO 18541-1 Use Case Cluster 1

| CAB | TC | Vehicle manufacturer |
| --- | --- | --- |
| The CAB shall collect and use for the approval inspection of the IO legal representative the data described in chapter 6.3.3 and for the authorization inspection of the IO employees the data described in chapter 6.3.5
  The CAB sends the following data by using the web service:






  — | IOEUID |

CAB

TC

Vehicle manufacturer

The CAB shall collect and use for the approval inspection of the IO legal representative the data described in chapter 6.3.3 and for the authorization inspection of the IO employees the data described in chapter 6.3.5

The CAB sends the following data by using the web service:

—

IOEUID

| — | IOUID |
| --- | --- |

—

IOUID

| — | Activation password |
| --- | --- |

—

Activation password

The TC receives from the CAB the following data:

| — | IOEUID |
| --- | --- |

—

IOEUID

| — | IOUID |
| --- | --- |

—

IOUID

| — | Activation password |
| --- | --- |

—

Activation password

Additionally the TC generates and uses the following data:

| — | CABUID |
| --- | --- |

—

CABUID

| — | Serial number of the electronic certificate |
| --- | --- |

—

Serial number of the electronic certificate

| — | Validity of the electronic certificate |
| --- | --- |

—

Validity of the electronic certificate

| — | Authorization status |
| --- | --- |

—

Authorization status

The VM generates and uses the following data:

| — | Data according ISO 18541-1 use case cluster 1 |
| --- | --- |

—

Data according ISO 18541-1 use case cluster 1

| — | Username and password associated to an IOEUID |
| --- | --- |

—

Username and password associated to an IOEUID

| — | IOEUID |
| --- | --- |

—

IOEUID

| — | IOUID |
| --- | --- |

—

IOUID

| — | CABUID |
| --- | --- |

—

CABUID

| — | Serial number of the electronic certificate |
| --- | --- |

—

Serial number of the electronic certificate

Attribute description

| 1) | IO employee unique identifier (IOEUID):
  The string generated by the CAB that strictly identifies the IO employee. |
| --- | --- |

1)

IO employee unique identifier (IOEUID):

The string generated by the CAB that strictly identifies the IO employee.

| 2) | IO unique identifier (IOUID):
  The value generated by the CAB that strictly identifies the IO as a legal entity. |
| --- | --- |

2)

IO unique identifier (IOUID):

The value generated by the CAB that strictly identifies the IO as a legal entity.

| 3) | CAB unique identifier (UID):
  The value generated by the Trust Center that strictly identifies the CAB. |
| --- | --- |

3)

CAB unique identifier (UID):

The value generated by the Trust Center that strictly identifies the CAB.

| 4) | Serial Number:
  Contains the X509 certificate serial number, which is unique for each certificate and automatically generated during the certificate issuance. |
| --- | --- |

4)

Serial Number:

Contains the X509 certificate serial number, which is unique for each certificate and automatically generated during the certificate issuance.

Authorization X / Status Authorization X:

Describe the authorization(s) and the corresponding status for a user.

1.3.   Certificate design

The x509.V3-certificate standard (RFC 5280 and ISO 9594-8.2017) define a list of common fields and values that are to be filled in an electronic certificate.

The digital certificate is to fulfill the security requirements of the BSI (http://www.bsi.de) regarding to key length and cryptography algorithms. The point in time to apply the BSI requirements must be established by the Forum Secure RMI.

When connecting to a server using a digital certificate, the server checks a standard field named ‘Subject DN’ allowing it to do a link with the identity of the IO in the internal VM system.

The following figure demonstrates an excerpt of content fields, required for identification by a VM system. The complete x509.V3-certificate structure defined in the RFC 5280 is not depicted here.

Figure 7

Content fields of the electronic certificate

| Field | Value | Comments |
| --- | --- | --- |
| Serial Number | XXX | Certificate serial number. |
| Issuer | XXX | Friendly name of the TC. |
| Validity | X years (From/To date) | Certificate lifetime from the certificate issuance to its end of validity. |
| Subject DN | IOEUID=<UserUniqueIdentifier>,
  IOUID=<IOUniqueIdentifier>,
  CABUID=<CABUniqueIdentifier>, | Information checked by the VM system after authentication step for identifying the user. |
| Subject Public Key Info | RSA encryption 4 096 bits | Algorithm and value of the public key contained in the certificate. |
| Authority Info Access | http://XXX | OCSP server location which will be defined by the TC. |

Field

Value

Comments

Serial Number

XXX

Certificate serial number.

Issuer

XXX

Friendly name of the TC.

Validity

X years (From/To date)

Certificate lifetime from the certificate issuance to its end of validity.

Subject DN

IOEUID=<UserUniqueIdentifier>,

IOUID=<IOUniqueIdentifier>,

CABUID=<CABUniqueIdentifier>,

Information checked by the VM system after authentication step for identifying the user.

Subject Public Key Info

RSA encryption 4 096 bits

Algorithm and value of the public key contained in the certificate.

Authority Info Access

http://XXX

OCSP server location which will be defined by the TC.

Validity

Validity period as defined in this scheme. Each electronic certificate is valid for a maximum period of 60 months. This period cannot be longer than the remaining validity period of the employing IO approval.

Subject Distinguished Name (DN)

| 1) | IOEUID:
  Contains a value generated by the CAB which represents the IO employee identity. This value is unique to an authorised user: if a user requests a new electronic certificate from the same CAB or another CAB (after a renewal or a revocation), he/she has is associated to the same UID.
  The IOEUID is built as follows: < ISO-3166-1-COUNTRY-CODE OF THE LOCATION OF THE CAB/NAME OF THE CAB/CHARACTER ALPHANUMERIC CODE>
  Example: BE/CAB-CERT/1234567890A
  This value has a maximum of 64bits. |
| --- | --- |

1)

IOEUID:

Contains a value generated by the CAB which represents the IO employee identity. This value is unique to an authorised user: if a user requests a new electronic certificate from the same CAB or another CAB (after a renewal or a revocation), he/she has is associated to the same UID.

The IOEUID is built as follows: < ISO-3166-1-COUNTRY-CODE OF THE LOCATION OF THE CAB/NAME OF THE CAB/CHARACTER ALPHANUMERIC CODE>

Example: BE/CAB-CERT/1234567890A

This value has a maximum of 64bits.

| 2) | IOUID:
  Contains a value generated by the CAB which represents the IO legal name, the address and the VAT number.
  EXAMPLE: <IO LEGALNAME: JOHNS_GARAGE/ADDRESS:MAINSTREET1BRUSSELS12345/VAT:BE12345678910 |
| --- | --- |

2)

IOUID:

Contains a value generated by the CAB which represents the IO legal name, the address and the VAT number.

EXAMPLE: <IO LEGALNAME: JOHNS_GARAGE/ADDRESS:MAINSTREET1BRUSSELS12345/VAT:BE12345678910

| 3) | CABUID:
  Contains a value generated by the TC which is unique to an accredited CAB. This value has a maximum of 64bits.
  The CAB has the responsibility to manage unique identifiers for users. The TC has the responsibility to manage unique identifiers IO’s legal entities and CAB. |
| --- | --- |

3)

CABUID:

Contains a value generated by the TC which is unique to an accredited CAB. This value has a maximum of 64bits.

The CAB has the responsibility to manage unique identifiers for users. The TC has the responsibility to manage unique identifiers IO’s legal entities and CAB.

Subject Public Key Info

Defines the algorithm and length of the public key contained in the electronic certificate. To ensure enough confidence in the strength of the algorithm, a key length of 4 096 bits shall be used.

Authority Info Access

The Trust Center is to provide an OCSP access to the certificate revocation list in order to provide an automatic access to the revocation status of the certificate. The OCSP service is provided 24/7 days.

1.4.   Authorisation check Web Service based on SOAP/RESTful API

The VM system is able to check the authorization status of the user requesting access to security information.

This check provides a standard SOAP XML service/RESTful APIbased on HTTPS protocol. Access to this service requires authentication by an electronic certificate. Request at the TC server is based on the following information:

Figure 8

Input data

| Input data |
| --- |
| Field | Value | Comments |
| IO Employee Unique Identifier (IOEUID) | <UserUniqueIdentifier> | |
| IO Unique Identifier (IOUID) | <IOUniqueIdentifier> | |
| Authorization ID | <AuthorizationUniqueIdentifier> | |

Input data

Field

Value

Comments

IO Employee Unique Identifier (IOEUID)

<UserUniqueIdentifier>

IO Unique Identifier (IOUID)

<IOUniqueIdentifier>

Authorization ID

<AuthorizationUniqueIdentifier>

Figure 9

Output data user information details retrieval during registration based on SOAP/RESTful API

| Output data |
| --- |
| Field | Value | Comments |
| User Status | | 0 → Suspended |

Output data

Field

Value

Comments

User Status

0 → Suspended

| | 1 → Ok |
| --- | --- |

1 → Ok

| | 2 → Revoked |
| --- | --- |

2 → Revoked

| | 3 → Unknown |
| --- | --- |

3 → Unknown

IO employee Unique Identifier

<UserUniqueIdentifier>

This check provides a standard SOAP XML service/RESTful API based on HTTPS protocol. A VM specific electronic certificate is required to authenticate access to this service.

---

| 29.7.2022 | EN | Official Journal of the European Union | C 288/33 |
| --- | --- | --- | --- |

29.7.2022

EN

Official Journal of the European Union

C 288/33

---

Non-opposition to a notified concentration

(Case M.10624 – ENEL / INTESA / JV)

(Text with EEA relevance)

(2022/C 288/03)

On 17 June 2022, the Commission decided not to oppose the above notified concentration and to declare it compatible with the internal market. This decision is based on Article 6(1)(b) of Council Regulation (EC) No 139/2004 (1). The full text of the decision is available only in Italian language and will be made public after it is cleared of any business secrets it may contain. It will be available:

| — | in the merger section of the ‘Competition policy’ website of the Commission (http://ec.europa.eu/competition/mergers/cases/). This website provides various facilities to help locate individual merger decisions, including company, case number, date and sectoral indexes, |
| --- | --- |

—

in the merger section of the ‘Competition policy’ website of the Commission (http://ec.europa.eu/competition/mergers/cases/). This website provides various facilities to help locate individual merger decisions, including company, case number, date and sectoral indexes,

| — | in electronic form on the EUR-Lex website (http://eur-lex.europa.eu/homepage.html?locale=en) under document number 32022M10624. EUR-Lex is the online point of access to European Union law. |
| --- | --- |

—

in electronic form on the EUR-Lex website (http://eur-lex.europa.eu/homepage.html?locale=en) under document number 32022M10624. EUR-Lex is the online point of access to European Union law.

---

(1)  OJ L 24, 29.1.2004, p. 1.

---

IV Notices

NOTICES FROM EUROPEAN UNION INSTITUTIONS, BODIES, OFFICES AND AGENCIES

European Commission

| 29.7.2022 | EN | Official Journal of the European Union | C 288/34 |
| --- | --- | --- | --- |

29.7.2022

EN

Official Journal of the European Union

C 288/34

---

Euro exchange rates (1)

28 July 2022

(2022/C 288/04)

1 euro =

| | Currency | Exchange rate |
| --- | --- | --- |
| USD | US dollar | 1,0122 |
| JPY | Japanese yen | 137,26 |
| DKK | Danish krone | 7,4442 |
| GBP | Pound sterling | 0,83586 |
| SEK | Swedish krona | 10,4490 |
| CHF | Swiss franc | 0,9745 |
| ISK | Iceland króna | 138,70 |
| NOK | Norwegian krone | 9,8983 |
| BGN | Bulgarian lev | 1,9558 |
| CZK | Czech koruna | 24,609 |
| HUF | Hungarian forint | 407,30 |
| PLN | Polish zloty | 4,7908 |
| RON | Romanian leu | 4,9342 |
| TRY | Turkish lira | 18,1417 |
| AUD | Australian dollar | 1,4535 |
| CAD | Canadian dollar | 1,2986 |
| HKD | Hong Kong dollar | 7,9456 |
| NZD | New Zealand dollar | 1,6172 |
| SGD | Singapore dollar | 1,4009 |
| KRW | South Korean won | 1 320,45 |
| ZAR | South African rand | 17,0011 |
| CNY | Chinese yuan renminbi | 6,8325 |
| HRK | Croatian kuna | 7,5200 |
| IDR | Indonesian rupiah | 15 107,59 |
| MYR | Malaysian ringgit | 4,5071 |
| PHP | Philippine peso | 56,592 |
| RUB | Russian rouble | |
| THB | Thai baht | 37,097 |
| BRL | Brazilian real | 5,3300 |
| MXN | Mexican peso | 20,6760 |
| INR | Indian rupee | 80,6535 |

Currency

Exchange rate

USD

US dollar

1,0122

JPY

Japanese yen

137,26

DKK

Danish krone

7,4442

GBP

Pound sterling

0,83586

SEK

Swedish krona

10,4490

CHF

Swiss franc

0,9745

ISK

Iceland króna

138,70

NOK

Norwegian krone

9,8983

BGN

Bulgarian lev

1,9558

CZK

Czech koruna

24,609

HUF

Hungarian forint

407,30

PLN

Polish zloty

4,7908

RON

Romanian leu

4,9342

TRY

Turkish lira

18,1417

AUD

Australian dollar

1,4535

CAD

Canadian dollar

1,2986

HKD

Hong Kong dollar

7,9456

NZD

New Zealand dollar

1,6172

SGD

Singapore dollar

1,4009

KRW

South Korean won

1 320,45

ZAR

South African rand

17,0011

CNY

Chinese yuan renminbi

6,8325

HRK

Croatian kuna

7,5200

IDR

Indonesian rupiah

15 107,59

MYR

Malaysian ringgit

4,5071

PHP

Philippine peso

56,592

RUB

Russian rouble

THB

Thai baht

37,097

BRL

Brazilian real

5,3300

MXN

Mexican peso

20,6760

INR

Indian rupee

80,6535

---

(1)  Source: reference exchange rate published by the ECB.

---

European Data Protection Supervisor

| 29.7.2022 | EN | Official Journal of the European Union | C 288/35 |
| --- | --- | --- | --- |

29.7.2022

EN

Official Journal of the European Union

C 288/35

---

Summary of the Opinion of the European Data Protection Supervisor on the Proposal for a Regulation of the European Parliament and of the Council on the financial rules applicable to the general budget of the Union

(2022/C 288/05)

(The full text of this Opinion can be found in English, French and German on the EDPS website https://edps.europa.eu)

On 16 May 2022, the European Commission issued a Proposal for a Regulation of the European Parliament and of the Council on the financial rules applicable to the general budget of the Union, amending the Financial Regulation. The EDPS notes that the Proposal aims to improve the quality and interoperability of data on recipients of Union funding and on those ultimately benefitting, directly or indirectly, from Union funding in order to effectively prevent, detect, investigate and correct frauds or remedy irregularities.

The EDPS fully supports the goals of the Proposal, including the increased use of digitalisation to better protect EU financial interests and to combat fraud and other irregularities. While processing of personal data may be necessary to achieve this goal, it is incumbent upon the EU legislator to ensure that any interference with the right to data protection remain limited to what is strictly necessary and proportionate to the objectives pursued.

The EDPS welcomes that the Proposal aims to establish the categories of data that will be processed in order to achieve the Proposal’s objectives. The EDPS understands, however, that the process of data-mining and risk-scoring will not be limited to the data explicitly identified by the Proposal and that those data would be compared with data from other sources. The EDPS considers it necessary to explicitly identify all the categories of personal data to be processed, as well as the sources of those data. Appropriate safeguards to ensure the quality and accuracy of those data should also be put in place, particularly in circumstances where those other data would be collected from third parties.

The EDPS observes that no additional information in the Proposal is provided as regards to the IT system itself. Therefore, he recommends clarifying the type of the IT system to be used, in particular whether the Commission plans to base the system on the already existing IT system ‘Arachne’ or to create a completely new IT system. Regardless of the use of existing structures, the EDPS would like to remind that appropriate safeguards need to be established and introduced in the architecture of this IT system, in line with the general data protection rules applicable to the processing of personal data. This should be well reflected upon in the design and development phase of the IT system, in line with the requirement of data protection by design.

The EDPS also strongly recommends the co-legislator to clearly define the maximum duration for which personal data referred to may be stored and made available in the single integrated IT system for data-mining and risk-scoring provided by the Commission.

Regarding publication of relevant information concerning all recipients of funds financed from the EU budget, the EDPS positively notes the efforts to made to balance the principle of transparency against the interference with the right of the recipients concerned to respect for their private life in general and to the protection of their personal data by exempting recipients from publication of their personal data if certain conditions would be met (threshold in terms of the amount of aid received, nature of the measure, risks for the rights and freedoms etc.).

1.   INTRODUCTION

| 1. | On 16 May 2022, the European Commission issued a Proposal for a Regulation of the European Parliament and of the Council on the financial rules applicable to the general budget of the Union (recast) (‘the Proposal’), amending the Financial Regulation (1). |
| --- | --- |

1.

| 2. | The objective of the Proposal is to align the Financial Regulation with the 2021-2027 Multiannual Financial Framework (MFF) package, to maintain a ‘single rule book’ governing the expenditure of the Union, meaning that all general financial rules are included in the Financial Regulation. In addition, the Proposal includes targeted improvements and simplifications which have been identified since the entry into force of the 2018 Financial Regulation. The Proposal also aims to increase the use of digitalisation to better protect EU financial interests, to better contribute to the achievement of the EU policy objectives and to achieve additional simplification for recipients of Union funds (2). |
| --- | --- |

2.

| 3. | The present EDPS Opinion is issued in response to a consultation by the European Commission of 16 May 2022, pursuant to Article 42(1) of EUDPR (3). The EDPS welcomes the reference to this consultation in Recital 257 of the Proposal. In this regard, the EDPS also positively notes that he had been informally consulted pursuant to recital 60 EUDPR. |
| --- | --- |

3.

5.   CONCLUSIONS

| 26. | In light of the above, the EDPS makes the following recommendations:






  (1) | to clarify the role of all entities that would be using and accessing any personal data processed by the single integrated IT system for data-mining and risk-scoring. |
| --- | --- | --- |

26.

(1)

to clarify the role of all entities that would be using and accessing any personal data processed by the single integrated IT system for data-mining and risk-scoring.

| (2) | to clarify the type of the IT system to be used, in particular whether the Commission plans to base the system on the already existing IT system ‘Arachne’ or to create a completely new IT system. |
| --- | --- |

(2)

to clarify the type of the IT system to be used, in particular whether the Commission plans to base the system on the already existing IT system ‘Arachne’ or to create a completely new IT system.

| (3) | to explicitly identify all the categories of data concerned, i.e. which data will be processed/brought into connection with the identification data mentioned in Article 36 paragraph 6 of the Proposal, as well as the sources of those data. |
| --- | --- |

(3)

to explicitly identify all the categories of data concerned, i.e. which data will be processed/brought into connection with the identification data mentioned in Article 36 paragraph 6 of the Proposal, as well as the sources of those data.

| (4) | introduce appropriate safeguards to ensure the quality and accuracy of data, particularly in case those other data would be collected from third parties. |
| --- | --- |

(4)

introduce appropriate safeguards to ensure the quality and accuracy of data, particularly in case those other data would be collected from third parties.

| (5) | regardless of whether the Commission intends to make use of existing structures, to include in the Proposal itself a high level description of the IT tool, including data protection roles and responsibilities and relevant applicable safeguards. |
| --- | --- |

(5)

regardless of whether the Commission intends to make use of existing structures, to include in the Proposal itself a high level description of the IT tool, including data protection roles and responsibilities and relevant applicable safeguards.

| (6) | to apply additional safeguards for the non-published types of data. For instance, pseudonymisation of data should be considered. |
| --- | --- |

(6)

to apply additional safeguards for the non-published types of data. For instance, pseudonymisation of data should be considered.

| (7) | to clarify whether electronic recording and storage of data would be done within the IT system for data-mining and risk-scoring or the IT system would only have access to data stored elsewhere. |
| --- | --- |

(7)

to clarify whether electronic recording and storage of data would be done within the IT system for data-mining and risk-scoring or the IT system would only have access to data stored elsewhere.

| (8) | to clearly define the maximum duration for which the data referred to in Article 36 of the Proposal may be stored and made available in the single integrated IT system for data-mining and risk-scoring provided by the Commission. |
| --- | --- |

(8)

to clearly define the maximum duration for which the data referred to in Article 36 of the Proposal may be stored and made available in the single integrated IT system for data-mining and risk-scoring provided by the Commission.

Brussels, 7 July 2022.

Wojciech Rafał WIEWIÓROWSKI

---

(1)  Regulation (EU, Euratom) 2018/1046 of the European Parliament and of the Council of 18 July 2018 on the financial rules applicable to the general budget of the Union, amending Regulations (EU) No 1296/2013, (EU) No 1301/2013, (EU) No 1303/2013, (EU) No 1304/2013, (EU) No 1309/2013, (EU) No 1316/2013, (EU) No 223/2014, (EU) No 283/2014, and Decision No 541/2014/EU and repealing Regulation (EU, Euratom) No 966/2012 (OJ L 193, 30.7.2018, p. 1).

1

(2)  See COM(2022) 223 final, p. 1.

2

(3)  Regulation (EU) 2018/1725 of the European Parliament and of the Council of 23 October 2018 on the protection of natural persons with regard to the processing of personal data by the Union institutions, bodies, offices and agencies and on the free movement of such data, and repealing Regulation (EC) No 45/2001 and Decision No 1247/2002/EC (OJ L 295, 21.11.2018, p. 39).

3

---

V Announcements

OTHER ACTS

European Commission

| 29.7.2022 | EN | Official Journal of the European Union | C 288/38 |
| --- | --- | --- | --- |

29.7.2022

EN

Official Journal of the European Union

C 288/38

---

Publication of a communication of approval of a standard amendment to the product specification for a name in the wine sector referred to in Article 17(2) and (3) of Commission Delegated Regulation (EU) 2019/33

(2022/C 288/06)

This communication is published in accordance with Article 17(5) of Commission Delegated Regulation (EU) 2019/33 (1).

COMMUNICATION OF STANDARD AMENDMENT MODIFYING THE SINGLE DOCUMENT

‘Verdicchio dei Castelli di Jesi’

PDO-IT-A0482-AM04

Date of communication: 6.5.2022

DESCRIPTION OF AND REASONS FOR THE APPROVED AMENDMENT

1.   Packaging — containers and capacity

Description: For the packaging of ‘Verdicchio dei Castelli di Jesi’ wine, alternative containers may be used of a material other than glass, consisting of a wine skin of polyethylene or polyester multi-layered plastic enclosed in a box made of cardboard or any other rigid material, which must not be less than the minimum capacity laid down by national and EU legislation.

Reasons: The option has been added to package ‘Verdicchio dei Castelli di Jesi’ wine in containers other than glass, as this is what producers want following careful technical and commercial assessments.

This amendment concerns Article 8 of the product specification and section 9 of the single document.

2.   Reference to the inspection body - change of address

Description: The address of Valoritalia società per la certificazione delle qualità e delle produzioni vitivinicole italiane S.r.l. has been changed from Via Piave 24, 00187 Rome to Via Venti Settembre 98/G, 00187 Rome.

Reasons: The registered office of the ‘Verdicchio dei Castelli di Jesi’ inspection body has been transferred.

This amendment concerns Article 10 of the product specification but does not concern the single document.

SINGLE DOCUMENT

1.   Name of product

Verdicchio dei Castelli di Jesi

2.   Geographical indication type

PDO – Protected Designation of Origin

3.   Categories of grapevine product

| 1. | Wine |
| --- | --- |

1.

Wine

| 5. | Quality sparkling wine |
| --- | --- |

5.

Quality sparkling wine

4.   Description of the wine(s)

1.   Verdicchio dei Castelli di Jesi

CONCISE TEXTUAL DESCRIPTION

‘Verdicchio dei Castelli di Jesi’ PDO wines are pale straw yellow in colour. They have a delicate, distinctive aroma of almond. In terms of flavour, they are harmonious and dry with a pleasant, bitter aftertaste.

| General analytical characteristics |
| --- |
| Maximum total alcoholic strength (in % volume) | |
| Minimum actual alcoholic strength (in % volume) | |
| Minimum total acidity | 4,50 grams per litre expressed as tartaric acid |
| Maximum volatile acidity (in milliequivalents per litre) | |
| Maximum total sulphur dioxide (in milligrams per litre) | |

General analytical characteristics

Maximum total alcoholic strength (in % volume)

Minimum actual alcoholic strength (in % volume)

Minimum total acidity

4,50 grams per litre expressed as tartaric acid

Maximum volatile acidity (in milliequivalents per litre)

Maximum total sulphur dioxide (in milligrams per litre)

2.   Verdicchio dei Castelli di Jesi Classico

CONCISE TEXTUAL DESCRIPTION

‘Verdicchio dei Castelli di Jesi’ PDO Classico wines are pale straw yellow in colour. They have a delicate, distinctive aroma. In terms of flavour, they are dry and harmonious with a pleasant, bitter aftertaste.

| General analytical characteristics |
| --- |
| Maximum total alcoholic strength (in % volume) | |
| Minimum actual alcoholic strength (in % volume) | |
| Minimum total acidity | 4,50 grams per litre expressed as tartaric acid |
| Maximum volatile acidity (in milliequivalents per litre) | |
| Maximum total sulphur dioxide (in milligrams per litre) | |

General analytical characteristics

Maximum total alcoholic strength (in % volume)

Minimum actual alcoholic strength (in % volume)

Minimum total acidity

4,50 grams per litre expressed as tartaric acid

Maximum volatile acidity (in milliequivalents per litre)

Maximum total sulphur dioxide (in milligrams per litre)

3.   Verdicchio dei Castelli di Jesi Classico Superiore

CONCISE TEXTUAL DESCRIPTION

‘Verdicchio dei Castelli di Jesi’ PDO Classico wines are pale straw yellow in colour. They have a delicate, distinctive aroma. In terms of flavour, they are dry and harmonious with a pleasant, bitter aftertaste.

| General analytical characteristics |
| --- |
| Maximum total alcoholic strength (in % volume) | |
| Minimum actual alcoholic strength (in % volume) | |
| Minimum total acidity | 4,50 grams per litre expressed as tartaric acid |
| Maximum volatile acidity (in milliequivalents per litre) | |
| Maximum total sulphur dioxide (in milligrams per litre) | |

General analytical characteristics

Maximum total alcoholic strength (in % volume)

Minimum actual alcoholic strength (in % volume)

Minimum total acidity

4,50 grams per litre expressed as tartaric acid

Maximum volatile acidity (in milliequivalents per litre)

Maximum total sulphur dioxide (in milligrams per litre)

4.   Verdicchio dei Castelli di Jesi Passito

CONCISE TEXTUAL DESCRIPTION

In terms of colour, ‘Verdicchio dei Castelli di Jesi’ PDO Passito wines range from intense straw yellow to amber. They have a distinctive, intense aroma. In terms of flavour, they are medium-sweet to sweet, harmonious, velvety and distinctive.

| General analytical characteristics |
| --- |
| Maximum total alcoholic strength (in % volume) | |
| Minimum actual alcoholic strength (in % volume) | |
| Minimum total acidity | 4,00 grams per litre expressed as tartaric acid |
| Maximum volatile acidity (in milliequivalents per litre) | 25 |
| Maximum total sulphur dioxide (in milligrams per litre) | |

General analytical characteristics

Maximum total alcoholic strength (in % volume)

Minimum actual alcoholic strength (in % volume)

Minimum total acidity

4,00 grams per litre expressed as tartaric acid

Maximum volatile acidity (in milliequivalents per litre)

25

Maximum total sulphur dioxide (in milligrams per litre)

5.   Verdicchio dei Castelli di Jesi Spumante

CONCISE TEXTUAL DESCRIPTION

‘Verdicchio dei Castelli di Jesi’ PDO Spumante wines have fine, persistent bubbles. In terms of colour, they are straw yellow of varying intensity, sometimes with hints of pale green. The aroma is delicate and distinctive, fine, generous and complex. In terms of flavour, they range from extra-brut to dry, sapid, fresh, fine and harmonious.

| General analytical characteristics |
| --- |
| Maximum total alcoholic strength (in % volume) | |
| Minimum actual alcoholic strength (in % volume) | |
| Minimum total acidity | 4,50 grams per litre expressed as tartaric acid |
| Maximum volatile acidity (in milliequivalents per litre) | |
| Maximum total sulphur dioxide (in milligrams per litre) | |

General analytical characteristics

Maximum total alcoholic strength (in % volume)

Minimum actual alcoholic strength (in % volume)

Minimum total acidity

4,50 grams per litre expressed as tartaric acid

Maximum volatile acidity (in milliequivalents per litre)

Maximum total sulphur dioxide (in milligrams per litre)

5.   Wine-making practices

5.1.   Specific oenological practices

—

5.2.   Maximum yields

| 1. | Verdicchio dei Castelli di Jesi
  14 000 kilograms of grapes per hectare |
| --- | --- |

1.

Verdicchio dei Castelli di Jesi

14 000 kilograms of grapes per hectare

| 2. | Verdicchio dei Castelli di Jesi Classico

  14 000 kilograms of grapes per hectare |
| --- | --- |

2.

Verdicchio dei Castelli di Jesi Classico

14 000 kilograms of grapes per hectare

| 3. | Verdicchio dei Castelli di Jesi Classico Superiore

  11 000 kilograms of grapes per hectare |
| --- | --- |

3.

Verdicchio dei Castelli di Jesi Classico Superiore

11 000 kilograms of grapes per hectare

| 4. | Verdicchio dei Castelli di Jesi Passito

  14 000 kilograms of grapes per hectare |
| --- | --- |

4.

Verdicchio dei Castelli di Jesi Passito

14 000 kilograms of grapes per hectare

6.   Demarcated geographical area

The production area for ‘Verdicchio dei Castelli di Jesi’ PDO wines is located in the provinces of Ancona and Macerata.

The identified area comprises part of the geographical basin of the River Esino and spans territory belonging to 22 inland municipalities in Ancona province and 2 inland municipalities in Macerata province.

7.   Wine grape varieties

Verdicchio Bianco B. - Verdicchio

8.   Description of the link(s)

Verdicchio dei Castelli di Jesi

There is a centuries-old tradition of vine cultivation and wine production in the territory where ‘Verdicchio dei Castelli di Jesi’ PDO wines are produced. There is also an age-old tradition of producing sparkling wines, which is well documented, and of producing Passito wines [from raisined grapes].

Over the centuries, human factors have resulted in Verdicchio vines being chosen as the variety for cultivation in the area. They have also had an impact on the vine training methods and oenological practices employed.

The interplay between natural (relief, climate and soil) and human factors is what gives ‘Verdicchio dei Castelli di Jesi’ PDO wines their uniquely distinctive qualitative and organoleptic characteristics that cannot be achieved elsewhere.

9.   Essential further conditions (packaging, labelling, other requirements)

Information on the vintage year

Legal framework:

EU legislation

Type of further condition:

Additional provisions relating to labelling

Description of the condition:

The year of the vintage must be indicated on the labels of ‘Verdicchio dei Castelli di Jesi’, ‘Verdicchio dei Castelli di Jesi’Classico, ‘Verdicchio dei Castelli di Jesi’Classico Superiore, ‘Verdicchio dei Castelli di Jesi’Passito, ‘Verdicchio dei Castelli di Jesi’Spumante Riserva PDO wines.

Packaging, bottling and ban on certain closure systems

Legal framework:

EU legislation

Type of further condition:

Additional provisions relating to labelling

Description of the condition:

For the packaging of ‘Verdicchio dei Castelli di Jesi’ type wines, alternative containers may also be used of a material other than glass, consisting of a wine skin of polyethylene or polyester multi-layered plastic enclosed in a box made of cardboard or any other rigid material, which must not be less than the minimum capacity laid down by national and EU legislation.

‘Verdicchio dei Castelli di Jesi’Classico type wine must be released for consumption only in glass containers with a capacity not exceeding 5 litres.

‘Verdicchio dei Castelli di Jesi’Classico Superiore type wine must be released for consumption only in glass containers with a capacity not exceeding 3 litres. For these types of wine, the use of tear-off closures and crown caps is prohibited.

Link to the product specification

https://www.politicheagricole.it/flex/cm/pages/ServeBLOB.php/L/IT/IDPagina/18115

---

(1)  OJ L 9, 11.1.2019, p. 2.

---

| 29.7.2022 | EN | Official Journal of the European Union | C 288/43 |
| --- | --- | --- | --- |

29.7.2022

EN

Official Journal of the European Union

C 288/43

---

Publication of a communication of approval of a standard amendment to the product specification for a name in the wine sector as referred to in Article 17(2) and (3) of Commission Delegated Regulation (EU) 2019/33

(2022/C 288/07)

This communication is published in accordance with Article 17(5) of Commission Delegated Regulation (EU) 2019/33 (1).

COMMUNICATION OF STANDARD AMENDMENT MODIFYING THE SINGLE DOCUMENT

‘Rosso Cònero’

PDO-IT-A0428-AM03

Date of communication: 6 May 2022

DESCRIPTION OF AND REASONS FOR THE APPROVED AMENDMENT

1.   Packaging – containers and capacity

Description: For the packaging of Rosso Cònero wine, alternative containers may be used of a material other than glass, consisting of a wine skin of polyethylene or polyester multi-layered plastic enclosed in a box made of cardboard or any other rigid material, which must not be less than the minimum capacity laid down by national and EU legislation.

Reasons: The option has been added to package Rosso Cònero wine in containers other than glass, as this is what producers want following careful technical and commercial assessments.

This amendment concerns Article 8 of the product specification and section 9 of the single document.

2.   References to the control body – change of address

Description: The address of Valoritalia società per la certificazione delle qualità e delle produzioni vitivinicole italiane S.r.l. has been changed from Via Piave 24, 00187 Rome to Via Venti Settembre 98/G, 00187 Rome.

Reasons: The registered office of the Rosso Cònero control body has been transferred.

This amendment concerns Article 10 of the product specification but does not concern the single document.

SINGLE DOCUMENT

1.   Name of product

Rosso Cònero

2.   Geographical indication type

PDO – Protected Designation of Origin

3.   Categories of grapevine product

| 1. | Wine |
| --- | --- |

1.

Wine

4.   Description of the wine(s)

Rosso Cònero

CONCISE TEXTUAL DESCRIPTION

Rosso Cònero PDO wines are ruby red in colour and pleasant and vinous on the nose. They are full-bodied with a flavourful, harmonious and dry taste.

| General analytical characteristics |
| --- |
| Maximum total alcoholic strength (in % volume) | |
| Minimum actual alcoholic strength (in % volume) | |
| Minimum total acidity | 4,50 grams per litre expressed as tartaric acid |
| Maximum volatile acidity (in milliequivalents per litre) | |
| Maximum total sulphur dioxide (in milligrams per litre) | |

General analytical characteristics

Maximum total alcoholic strength (in % volume)

Minimum actual alcoholic strength (in % volume)

Minimum total acidity

4,50 grams per litre expressed as tartaric acid

Maximum volatile acidity (in milliequivalents per litre)

Maximum total sulphur dioxide (in milligrams per litre)

5.   Wine-making practices

5.1.   Specific oenological practices

—

5.2.   Maximum yields

1.   Rosso Cònero

13 000 kilograms of grapes per hectare

6.   Demarcated geographical area

The production area of Rosso Cònero wine comprises the whole of the municipalities of Ancona, Offagna, Camerano, Sirolo and Numana, and part of the municipalities of Castelfidardo and Osimo, all of which are in the province of Ancona.

7.   Wine grape varieties

Montepulciano N.

8.   Description of the link(s)

Rosso Cònero

The influence of human factors in the production area of Rosso Cònero wine has been crucial to the choice of grape varieties to be grown, the development of vine cultivation techniques and oenological practices, and there are signs of viticulture and oenology dating back to the 10th century BC.

These factors interact with the very distinctive and unique natural features of the area, which are mainly characterised by the presence of Monte Cònero. Here, the Montepulciano variety has found its ideal growing area, making ‘Rosso Cònero’ PDO wines unique and impossible to reproduce elsewhere.

9.   Essential further conditions (packaging, labelling, other requirements)

Indication of the year of production of the grapes

Legal framework:

EU legislation

Type of further condition:

Additional provisions relating to labelling

Description of the condition:

The year of production of the grapes must be indicated on the labelling of ‘Rosso Cònero’ PDO wines.

Packaging and closure systems

Legal framework:

EU legislation

Type of further condition:

Additional provisions relating to labelling

Description of the condition:

All closure systems permitted under EU and national legislation are allowed for Rosso Cònero PDO wine.

Furthermore, as regards the packaging, alternative containers may be used of a material other than glass, consisting of a wine skin of polyethylene or polyester multi-layered plastic enclosed in a box made of cardboard or any other rigid material, which must not be less than the minimum capacity laid down by national and EU legislation.

Link to the product specification

https://www.politicheagricole.it/flex/cm/pages/ServeBLOB.php/L/IT/IDPagina/18114

---

(1)  OJ L 9, 11.1.2019, p. 2.

---

| 29.7.2022 | EN | Official Journal of the European Union | C 288/46 |
| --- | --- | --- | --- |

29.7.2022

EN

Official Journal of the European Union

C 288/46

---

Publication of an application for registration of a name pursuant to Article 50(2)(a) of Regulation (EU) No 1151/2012 of the European Parliament and of the Council on quality schemes for agricultural products and foodstuffs

(2022/C 288/08)

This publication confers the right to oppose the application pursuant to Article 51 of Regulation (EU) No 1151/2012 of the European Parliament and of the Council (1) within three months from the date of this publication.

SINGLE DOCUMENT

’Meso istarskog goveda – boškarina / Meso istrskega goveda – boškarina'

EU No: PDO-HR+SI-2655 – 19.1.2021

PDO (X) PGI ( )

1.   Name(s) [of PDO or PGI]

’Meso istarskog goveda – boškarina / Meso istrskega goveda – boškarina’

2.   Member State or Third Country

| | Republic of Croatia |
| --- | --- |

Republic of Croatia

| | Republic of Slovenia |
| --- | --- |

Republic of Slovenia

3.   Description of the agricultural product or foodstuff

3.1.   Type of product

Class 1.1 Fresh meat (and offal)

3.2.   Description of the product to which the name in (1) applies

‘Meso istarskog goveda – boškarina / Meso istrskega goveda – boškarina’ is a fresh meat that undergoes controlled maturation for at least 15 days. The meat is obtained from a native breed known as Istrian cattle (‘istarsko govedo / istrsko govedo’), which are born in the geographical area defined in point 4 and subject to a standard procedure for slaughter and processing of the carcass.

‘Meso istarskog goveda – boškarina / Meso istrskega goveda – boškarina’ is placed on the market as a fresh or frozen product.

‘Meso istarskog goveda – boškarina / Meso istrskega goveda – boškarina’ is a light pink to dark red colour, with a moderate intramuscular fat content (marbling), aromatic, with a pleasant odour, a full, characteristic taste of beef, tender and succulent, and suited as such for use in a variety of meat dishes.

Depending on their age and weight category, carcasses of the Istrian cattle breed must have the following characteristics:

| — | bull and heifer calves slaughtered at 8 to 12 months of age – their dressed half-carcasses weigh 100 kg to 250 kg; their meat is a light pink colour, tender, succulent, mildly aromatic, with moderate marbling; the subcutaneous fatty tissue is a white colour; |
| --- | --- |

—

bull and heifer calves slaughtered at 8 to 12 months of age – their dressed half-carcasses weigh 100 kg to 250 kg; their meat is a light pink colour, tender, succulent, mildly aromatic, with moderate marbling; the subcutaneous fatty tissue is a white colour;

| — | heifers slaughtered at over 12 months of age – their dressed half-carcasses weigh 180 kg to 320 kg; their meat is a pink colour, tender, succulent, mildly aromatic, with moderate marbling; the subcutaneous fatty tissue is a white colour; |
| --- | --- |

—

heifers slaughtered at over 12 months of age – their dressed half-carcasses weigh 180 kg to 320 kg; their meat is a pink colour, tender, succulent, mildly aromatic, with moderate marbling; the subcutaneous fatty tissue is a white colour;

| — | young bulls (males slaughtered at 12 to 24 months of age) – their dressed half-carcasses weigh 200 kg to 400 kg; their meat is a pink to intense red colour, tender, succulent, mildly aromatic and marbled; the subcutaneous fatty tissue is white- to slightly yellow-coloured; |
| --- | --- |

—

young bulls (males slaughtered at 12 to 24 months of age) – their dressed half-carcasses weigh 200 kg to 400 kg; their meat is a pink to intense red colour, tender, succulent, mildly aromatic and marbled; the subcutaneous fatty tissue is white- to slightly yellow-coloured;

| — | cows (females slaughtered at over 24 months of age) – their dressed half-carcasses weigh more than 220 kg; their meat is a pink to purple-red colour, succulent, aromatic and marbled; the subcutaneous fatty tissue is a slight to intense yellow colour; |
| --- | --- |

—

cows (females slaughtered at over 24 months of age) – their dressed half-carcasses weigh more than 220 kg; their meat is a pink to purple-red colour, succulent, aromatic and marbled; the subcutaneous fatty tissue is a slight to intense yellow colour;

| — | bulls (males slaughtered at over 24 months of age) – their dressed half-carcasses weigh more than 280 kg; their meat is a pink to purple-red colour, succulent and aromatic; the subcutaneous fatty tissue is a slight to intense yellow colour; |
| --- | --- |

—

bulls (males slaughtered at over 24 months of age) – their dressed half-carcasses weigh more than 280 kg; their meat is a pink to purple-red colour, succulent and aromatic; the subcutaneous fatty tissue is a slight to intense yellow colour;

| — | steer (castrated males slaughtered at over 24 months of age) – their dressed half-carcasses weigh more than 350 kg; their meat is a red to dark red colour, aromatic and marbled; the subcutaneous fatty tissue is an intense yellow colour. |
| --- | --- |

—

steer (castrated males slaughtered at over 24 months of age) – their dressed half-carcasses weigh more than 350 kg; their meat is a red to dark red colour, aromatic and marbled; the subcutaneous fatty tissue is an intense yellow colour.

Carcasses of the Istrian cattle breed are classified using the EUROP grid system. As regards conformation, the carcasses must belong to class E, U, R or O, and as regards degree of fat cover, to class 2, 3 or 4.

The pH value, as measured in the dorsal muscle (musculus longissimus dorsi) at the earliest 24 hours after slaughter and cooling of the half-carcass, must be less than or equal to 5,8.

3.3.   Feed (for products of animal origin only) and raw materials (for processed products only)

Calves for fattening are weaned at the earliest at 4 months of age. Before fattening begins, hay and pasture are gradually introduced into their feed, alongside milk.

The primary feed for cattle over 8 months of age is coarse fodder (pasture, hay), which should, in principle, be produced in the geographical area defined in point 4.

It is permitted to add concentrate feed (cereals) for a maximum of 20 % of the total daily ration (expressed as a share of the weight of dry matter contained in the concentrate feed). The concentrate feed may be procured outside the geographical area defined in point 4.

Where there is insufficient coarse fodder available due to bad weather, the cattle may feed on hay and haylage produced outside the defined geographical area, but only for a maximum of 15 % of the total annual amount of coarse fodder expressed in dry matter.

The total proportion of all fodder (coarse fodder, concentrate feed) produced outside the defined geographical area on which the cattle may feed during any given year may be up to 28 %, expressed in dry matter. Since it is sourced from outside the defined geographical area only in exceptional circumstances, the use of such fodder in such limited amounts does not have a major effect on the properties of the product described in point 3.2.

It is not permitted to use milk replacers or ready-made concentrate-feed mixes that contain food industry by-products when feeding the cattle. It is also forbidden to use silage in feeding.

The use of haylage grass and a clover/grass mixture in feeding is permitted for a maximum of 40 % of the daily ration expressed in dry matter.

3.4.   Specific steps in production that must take place in the identified geographical area

All stages of production of ‘Meso istarskog goveda – boškarina’ / ‘Meso istrskega goveda – boškarina’, from calving, through slaughter of the cattle, primary processing and butchering, to the maturing of the meat, must take place within the geographical area referred to in point 4.

3.5.   Specific rules concerning slicing, grating, packaging, etc. of the product the registered name refers to

After the maturing process is complete, ‘Meso istarskog goveda – boškarina / Meso istrskega goveda – boškarina’ may be quick-frozen or placed on the market as a fresh product. The meat must be vacuum-packed before being frozen.

If the meat was matured in half- or quarter-carcasses, the carcasses must be butchered according to the standard cuts in the slaughter industry before being frozen or placed on the market.

The fresh meat may be placed on the market unpacked, vacuum-packed or in modified-atmosphere packaging. The frozen meat may be placed on the market vacuum-packed only.

3.6.   Specific rules concerning labelling of the product the registered name refers to

Where ‘Meso istarskog goveda – boškarina / Meso istrskega goveda – boškarina’ is sold to the final consumer unpacked in a retail outlet, the inscription ‘Meso istarskog goveda – boškarina / Meso istrskega goveda – boškarina’ and the common symbol of ‘Meso istarskog goveda – boškarina / Meso istrskega goveda – boškarina’ (see illustration below) must be displayed clearly. The common symbol on the inscription must be no smaller than 7 x 7 cm.

Where ‘Meso istarskog goveda – boškarina / Meso istrskega goveda – boškarina’ is placed on the market in packaged form, each packaging must contain the inscription ‘Meso istarskog goveda – boškarina / Meso istrskega goveda – boškarina’ and the common symbol of ‘Meso istarskog goveda – boškarina’ / ‘Meso istrskega goveda – boškarina’. The inscription ‘Meso istarskog goveda – boškarina / Meso istrskega goveda – boškarina’ must stand out more clearly than any other inscription by using larger lettering. The common symbol on the packaging must be no smaller than 2,5 x 2,5 cm.

In addition to the information laid down in the regulations in force on the labelling of beef, the packaging or inscription (in the case of unpacked meat) must also contain the date of slaughter, the category of cattle referred to in the specification and the inscription ‘Matured meat’.

Image 3

Illustration of common symbol

There are two versions of the common symbol of ‘Meso istarskog goveda – boškarina’ / ‘Meso istrskega goveda – boškarina’, which correspond to the two versions (Croatian and Slovenian) of the product name.

The common symbol is generally used in the multi-coloured variant. If the multi-coloured variant of the common symbol is not possible, the single-colour variant may be used, in black or one of the primary colours that make up the multi-coloured symbol.

4.   Concise definition of the geographical area

‘Meso istarskog goveda – boškarina / Meso istrskega goveda – boškarina’ is produced in the territory of the Istrian peninsula, the Kvarner archipelago, the Karst and Čičarija plateaus, and the Podgrad valley including the southern slopes of the Brkini hills.

In Croatia, production may take place in the territory of the following towns and municipalities: Buje, Buzet, Labin, Novigrad, Pazin, Poreč, Pula, Rovinj, Umag, Vodnjan, Bale, Barban, Brtonigla, Cerovlje, Fažana, Funtana, Gračišće, Grožnjan, Kanfanar, Karojba, Kaštelir-Labinci, Kršan, Lanišće, Ližnjan, Lupoglav, Marčana, Medulin, Motovun, Oprtalj, Pićan, Raša, Sveta Nedjelja, Sveti Lovreč, Sveti Petar u Šumi, Svetvinčenat, Tar-Vabriga, Tinjan, Višnjan, Vižinada, Vrsar, Žminj, Mošćenička Draga, Lovran, Opatija, Matulji and Kastav, Cres, Mali Lošinj, Krk, Baška, Dobrinj, Malinska-Dubašnica, Omišalj, Punat and Vrbnik.

In Slovenia, production may take place in the territory of the following municipalities: Piran, Izola, Koper, Ankaran, Hrpelje-Kozina, Ilirska Bistrica, Sežana, Komen and Divača.

5.   Link with the geographical area

The diversity and complexity of the geological and geomorphological structure of the production area of ‘Meso istarskog goveda - boškarina’ / ‘Meso istrskega goveda – boškarina’ led to the development of a variety of soil types. The climate of the geographical area as a whole is Mediterranean, changing gradually inland and towards the north of the peninsula, where it becomes moderate continental. The variety of topography, soil and climate and the interaction between them have resulted in a rich and diverse vegetation cover. Dinaric, Alpine and Mediterranean flora are all found here, with evergreen forests of holm oak and scrub, and deciduous forests of downy oak, hornbeam and beech. Woodland covers a third of the land, while much of the area consists of pastureland and scrubland that are home to over 300 plant varieties.

To this day, the native breed of Istrian cattle originating from the geographical area is reared in the traditional way. In the past, the cattle were reared using a highly extensive farming system. Feeding was based on pasture, and to a lesser extent meadow hay, lucerne, wheat and barley straw, corn stalks and litter. Depending on the vegetation cover and climate conditions of the breeding area, the cattle were grazed for 6 to 9 months of the year, or in some places all year round. In many parts of the production area, especially those where karst predominates, there was meagre pastureland available, forcing the free-grazing cattle to venture beyond those pastures in search of food. In the summer months, when the pastureland was already dry, the cattle were driven into the woodland, where there was not enough pasture and they were mostly forced to graze on the leaves of trees such as holm oak, manna ash, acacia, mulberry, cornelian cherry, Oriental hornbeam, strawberry-tree, holly, myrtle and wild olive, or would resort to evergreen flora if need be. It was this very same farming and feeding method that led many owners to call their herd ‘Boškarin’ (after boška = woodland, high scrub), which is used as a synonym for the Istrian cattle breed.

The present-day method for farming Istrian cattle differs only slightly from the traditional method. Although Istrian cattle are no longer used as draught animals, they all have regular access to pastureland, scrubland and woodland, and are mostly fed the traditional way.

In the past, Istrian cattle were not systematically fattened for meat production. An exception was fattening for the needs of the army, as recalled in a document from 1631 that refers to cattle farming on the island of Unije. In the late 19th century, the meat of Istrian cattle was sold in the towns and cities, especially Pula and Trieste.

To preserve the genetic material and prevent the breed from becoming extinct, the late 1980s saw the launch of a campaign to revive the breeding of Istrian cattle, which has focused on exploiting the gastronomic value of the specific characteristics of ‘Meso istarskog goveda – boškarina / Meso istrskega goveda – boškarina’ and its systematic promotion as a gourmet delicacy. Due to their lower total weight, slow natural growth and poorer yields, and the overall quality of their meat, Istrian cattle have very limited potential for beef production, and the breed is therefore farmed almost exclusively in the area described in point 4. Outside the geographical area, cattle are bred more intensively, which has a negative effect on the organoleptic characteristics of the meat, making it fattier and less aromatic.

The link between ‘Meso istarskog goveda – boškarina / Meso istrskega goveda – boškarina’ and the production area dates far back, to a time when an archaic form of cattle considered to be the ancestor of Istrian cattle, Bos primigenius, was farmed on the Istrian peninsula. Genetic research indicates that Istrian cattle belong to a separate genetic group, which is reflected in the characteristic conformation of the carcass compared with other meat breeds. The carcass of Istrian cattle is characterised by a relatively strong chest and small hind legs. It has a moderate muscle and fat content, and the yield of certain age categories is lower than other European meat breeds of cattle. The characteristics of the carcass also directly affect those of the meat.

One specific characteristic of ‘Meso istarskog goveda – boškarina / Meso istrskega goveda – boškarina’ is that it is tougher than the meat of other breeds, which is the result of the higher collagen content of the muscle tissue. The amount of collagen in the muscles is a hereditary factor, and there is more of it in Istrian cattle, as it was a draught breed that needed strength and developed muscle tissue that contained particularly sturdy collagen. Tough meat requires longer heat treatment, which breaks down the collagen and ultimately gives the meat its succulence and fullness of flavour. To reduce its toughness and strengthen and develop its specific aromas, the meat undergoes a process of maturation after slaughter, in which the collagen fibres are broken down and some of the amino acids are released.

One of the properties of ‘Meso istarskog goveda – boškarina / Meso istrskega goveda – boškarina’ is its lower degree of marbling, as a result of the moderate proportion of intramuscular fat, the moderate intensity of fattening and the low proportion of high-energy fodder in the ration. The intense yellow colour of the adipose tissue of the older cattle is the result of the fat composition, in other words the food eaten by the animal. Scientific studies have shown that the ratio of saturated to unsaturated fatty acids in the fatty acid composition of the meat lipids of Istrian cattle favours saturated fatty acids (approximately 60:40 %), which helps make the meat less prone to autoxidation when stored for a lengthy period. This property is particularly important for preserving the quality of the meat at the maturation stage. Subjecting the fresh meat of Istrian cattle to maturation stimulates proteolytic processes in the meat, which accentuate its organoleptic properties (softness, succulence, texture, odour, and the full aroma of the matured meat) and enhance its gastronomic potential.

The specific characteristics of Istrian cattle and of the meat they produce have been developed first and foremost by the cattle farmers of Istria, who, throughout history, have extensively farmed the breed and used it as draught animals. Thanks to centuries of selection, Istrian cattle have fully adapted to the climate and other ecological conditions in which they live, particularly the scarcity of food. Unlike highly productive commercial dairy or meat breeds, which need high-energy fodder, Istrian cattle can feed, in the absence of pastureland, by grazing on the shoots and leaves of numerous species of woody plants.

Since the relevant research to date has established a clear link between the botanical profile of the feed and the organoleptic and aromatic characteristics of the meat, it is fair to say that the geographical area has a significant, direct effect on the qualitative (nutritional and organoleptic) characteristics of ‘Meso istarskog goveda – boškarina / Meso istrskega goveda – boškarina’

Reference to publication of the specification

https://poljoprivreda.gov.hr/UserDocsImages/dokumenti/hrana/proizvodi_u_postupku_zastite-zoi-zozp-zts/Specifikacija_meso_istarskog_goveda_boskarin.pdf

https://www.gov.si/assets/ministrstva/MKGP/PODROCJA/HRANA/SHEME-KAKOVOSTI/SPECIFIKACIJE-EVROPSKA-KOMISIJA/Boskarin.pdf

---

(1)  OJ L 343, 14.12.2012, p. 1.

---