EU Registry Data model - Documentation · The structure of the document follows a standard representation of a data model. The second section provides an overview of the data model

EU Registry Data model - Documentation

Document Service Data

Type of Document: Deliverable

Reference: 2016-01-25_EU Registry Data Model - documentation.docx

Version: 4.0 Status: Final

Created by: Anestis Trypitsidis

Distribution: DG-ENV, EEA, Epsilon S.A, Agilis SA

Contract Full Title: Service Contract for the development of electronic reporting tools for the industrial

emissions directive 2010/75/EU (reporting period 2013 – 2016)

Contract Number: Contract No. 07.0201/2015/712963/SER/ENV.C.3

For Internal Use Only

Reviewed by:

Approved by:

Document History

Version Author Date Comments

1.0 AT 25/1/2016 Initial version of the document

2.0 AT 08/02/2016 Revised version based on feedback and comment received by DGENV

and EEA

3.0 RJ - DM 12/2/2016 New feedback from DGENV/EEA

4.0 AT 12/2/2016 Minor changes

5.0 RJ 20/02/2016 Minor editorial changes

TABLE OF CONTENTS

TABLE OF FIGURES..................................................................................................................................................... 5

TABLES ........................................................................................................................................................................... 5

1 INTRODUCTION ................................................................................................................................................... 6

2 OVERVIEW ............................................................................................................................................................ 7

3 EU REGISTRY – APPLICATION SCHEMA ...................................................................................................... 8

3.1 DESCRIPTION .................................................................................................................................................................... 8

3.2 EU REGISTRY – CLASS DIAGRAM .................................................................................................................................. 9

3.3 EU REGISTRY DATA TYPES - (LOGICAL DIAGRAM) .................................................................................................. 11

3.4 EU REGISTRY CODE LISTS (LOGICAL DIAGRAM) ...................................................................................................... 12

4 FEATURE CATALOGUE ................................................................................................................................... 12

4.1 FEATURE CATALOGUE METADATA .............................................................................................................................. 12

4.1.1 Types defined in the feature catalogue ........................................................................................................... 13

4.1.2 Feature Types .............................................................................................................................................................. 14

4.1.2.1 Spatial Object types ................................................................................................................................................................................... 14

4.1.2.1.1 ProductionSite ..................................................................................................................................................................................... 14

4.1.2.1.2 ProductionFacility .............................................................................................................................................................................. 16

4.1.2.1.3 ProductionInstallation ..................................................................................................................................................................... 18

4.1.2.1.4 LCP ............................................................................................................................................................................................................. 20

4.1.2.2 Object types .................................................................................................................................................................................................. 22

4.1.2.2.1 ReportData ............................................................................................................................................................................................. 22

4.1.2.2.2 Activity ..................................................................................................................................................................................................... 22

4.1.3 Data Types .................................................................................................................................................................... 23

4.1.3.1 Contact ............................................................................................................................................................................................................ 23

4.1.3.2 Date ................................................................................................................................................................................................................... 24

4.1.3.3 Measure .......................................................................................................................................................................................................... 24

4.1.3.4 AddressRepresentation .......................................................................................................................................................................... 25

4.1.3.5 Confidentiality ............................................................................................................................................................................................. 26

4.1.3.6 InspectionsPerYear ................................................................................................................................................................................... 26

4.1.3.7 OwnershipPartType ................................................................................................................................................................................. 27

4.1.3.8 PermitValue .................................................................................................................................................................................................. 27

4.1.3.9 StatusType ..................................................................................................................................................................................................... 28

4.1.3.10 RelatedParty ........................................................................................................................................................................................... 28

4.1.4 Code lists ........................................................................................................................................................................ 29

4.1.4.1 ActivityCodeValue ..................................................................................................................................................................................... 29

4.1.4.1.1 NACECodeValue .................................................................................................................................................................................. 29

4.1.4.1.2 IEDActivities ......................................................................................................................................................................................... 30

4.1.4.1.3 E-PRTRCodeValue .............................................................................................................................................................................. 30

4.1.4.2 RiverBasinDistrictValue ......................................................................................................................................................................... 30

4.1.4.3 DerogationValue ......................................................................................................................................................................................... 30

4.1.4.4 CountryCode ................................................................................................................................................................................................. 31

4.1.4.5 Reasoning ...................................................................................................................................................................................................... 31

4.1.4.6 CoordinateSystemValue ......................................................................................................................................................................... 32

4.1.4.7 NUTSLevelValue ......................................................................................................................................................................................... 32

4.1.4.8 CompetentAuthorityTypeValue .......................................................................................................................................................... 32

4.1.4.9 ConditionOfFacilityValue ....................................................................................................................................................................... 32

4.1.4.10 RelevantChaptersValue ..................................................................................................................................................................... 32

4.1.4.11 OwnershipTypeValue ......................................................................................................................................................................... 33

TABLE OF ACRONYMS ............................................................................................................................................ 33

LIST OF TERMS - SUMMARY OF STEREOTYPES ............................................................................................. 35

Table of Figures FIGURE 1: EU REGISTRY CLASS DIAGRAM .......................................................................................................................................................... 10 FIGURE 2: EU REGISTRY - DATA TYPES .............................................................................................................................................................. 11 FIGURE 3: EU REGISTRY – CODE LISTS ............................................................................................................................................................... 12

Tables TABLE 1: FEATURE CATALOGUE ........................................................................................................................................................................... 14

Development of electronic reporting tools for the

industrial emissions directive 2010/75/EU

January 25, 2016 Page: 6/35

1 Introduction

The main purpose of this data model is to enable, structure and centralise the electronic reporting

required according to Decision 2012/795/EU, under Article 72 of Directive 2010/75/EU on Industrial

Emissions (IED) and under Regulation (EC) No 166/2006 establishing a European Pollutant Release

and Transfer Register (E-PRTR).

As a result of the activities carried out within the scope of Task 1 – Detailed work plan approved

methodology and data specifications, this deliverable provides the data model to be used for EU

Registry (module 2 plus other (elements of) EU legislation (i.e. E-PRTR facilities, Large Combustion

Plants (LCPs), and potentially even more elements in the future, that have a connection with the scope

of the contract No. 07.0201/2015/712963/SER/ENV.C.3.

The data model was based on discussions that took place within project meetings and information

provided by the discussion paper (ANNEX I) that was provided by the European Commission -

Directorate-General for Environment (DG ENV) and the European Environment Agency (EEA).

It is important to state that the data model was based on the specific requirements stemming from the

tender specifications, the discussion paper and from the existing reporting requirements. In order to

ensure the highest possible compatibility with the requirements of Directive 2007/2/EC (the INSPIRE

Directive) aimed creating a European Union (EU) spatial data infrastructure. The Directive addresses

34 spatial data themes needed for environmental applications. The theme that is most relevant in this

context is the theme on 'Production and Industrial Facilities' (Annex III). This theme denominates

INSPIRE elements, like i.e. the ProductionSite feature type etc. This denomination was kept in order to

be in line with INSPIRE requirements. In other words the INSPIRE model was used as a reference to

link the current separate INSPIRE Data Specifications (DS) to the thematic data requirements. The

result of that is two1 separate INSPIRE Network Services (NS), each of them providing a different data

subset (INSPIRE core data + thematic data). This approach with creating (a subset) service is best fit

to facilitate for the reporting needs for industrial emissions while at the same time allowing Member

States (MS) to ensure conformance with INSPIRE directive quite easily.

The structure of the document follows a standard representation of a data model. The second section

provides an overview of the data model and comprehensive information about each entity. Then

based on the Enterprise Architect software the application schema will be presented (EU Registry

basic Class Diagram, Data types & CodeLists). The final section contains descriptive information for

every type that is defined within the data model.

1 In contrast the Integrated approach, as used with for example the Environmental reporting obligations for Air Quality Data (AQD), the INSPIRE Data Specifications (DS) are extended and embed the thematic requirements. So there is one INSPIRE Network Service (NS) feeding workflows related to environmental obligations.




2 Overview

The data model comprises features related to reporting obligations according to the IED and the E-

PRTR Regulation. It describes the concept of a centralised EU registry on industrial sites, that is based

on INSPIRE and aims at facilitating further streamlining of the electronic reporting by MS.

According to the discussion paper there are four entities, Installations, Facilities, Plants and Sites.

We distinguish between 'level 1' entities and 'level 2' entities. The main differentiating feature

between them is that 'Level 1' entities interconnect the underlying ‘level 2’ entities.

The ‘Level 1’ entities are stored/registered in the so called 'EU registry' and link different ‘level 2’

entities through their (common) administrative data through their communalities.

Their main communality is that activities are operated on a ‘site’ = ”geographical location of the

facility” (E-PRTR, INSPIRE):

o 'level 2' entities linked based on their geographical location ('operated on a single site")

o simplification: geographical reality presented as unique (X,Y) coordinates, defining

'level 1' entity, encompassing several 'level 2' entities

The underlying ‘Level 2’ entities are the following:

1. ‘Installation’ (IED, E-PRTR) means “a stationary technical unit within which one or more

activities listed in Annex I or in Part 1 of Annex VII [to IED] are carried out, and directly

associated activities on the same site with a technical connection to the activities listed and

which could have an effect on emissions and pollution”

2. ‘Facility’ (E-PRTR) “one or more installations on the same site that are operated by the same

natural or legal person”

3. ‘Plant’ (IED) refers to a “combustion plant” covered by Chapter III of the IED or a “waste (co-)

incineration plant” covered by Chapter IV of the IED

Consequently, all entities are connected through the 'Site entity' which is the 'Level 1 entity'. Each of

the underlying Level 2 entities belong to a Site which already has been defined within the context of

the INSPIRE DS as “Productionsite” feature type. As a consequence, level 2 entities are linked with

level 1 entity and are geographical defined as a simple pair of XY coordinates (point feature)2 . This

point feature will usually be the entrance (the gate) of an industrial site as those are the coordinates

that are usually registered by Member States.

Enterprise Architect software tool was used to create and modify the logical model using UML class

diagrams and to transform them into relevant application schema.

2 It is important to mention, that in contrast to EU Registry data specifications, INSPIRE DS for PF apart from point geometry has also other types.




3 EU Registry – Application schema

3.1 Description

Initially the option to derive EU Registry data mode from the INSPIRE extended data model described

in the Technical Guidelines for PF theme was investigated. In the end, as already stated in previous

section, even if EU Registry data model is based on INSPIRE Production Facility (PF)3, we did not

follow at all links and relationships that were defined. Namely, we discard all entities that are not

foreseen under the current Regulations, for example feature type ProductionBuilding, Production Plot,

ProductionInstallationPart. In contrast we kept all relevant entities that are valid for our case, for

example feature type ProductionSite, ProductionFacility and ProductionInstallation. Additionally,

according to data specifications that were delivered within the terms of reference of this contract, new

feature types have been defined, for example ReportData and Large Combustion Plants (LCP). Below a

description of all feature types is presented including their (inter)relations:

ReportData: represents general information that has to be submitted for each type of entity.

For example it is mandatory, when a MS has to add information about a

site/facility/installation/LCP, to include information about the country (CountryID), the

coordinate reference system that the geographical information will be provided

(CoordinateSystem), the authority responsible for the Registry submission (AuthorityReport)

and the date of last update in the National Systems of the data submitted (Date).

ProductionSite: a level 1 entity that allows establishing links between all level 2 entities.

Feature type is consisting of general information and complex data types such as the

ownership, region (NUTS codes), River basin district, address information, one or more

activities based on NACE code list.

Note: It is important to state that one or many level two entities can belong to the same site

(Level 1),

ProductionFacility: is a level 2 entity according to EPRTR Regulation4 and means “one or

more installations on the same site that are operated by the same natural or legal person”,

ProductionInstallation: is a level 2 entity according to IED Regulation5 and concerns “a

stationary technical unit within which one or more activities listed in Annex I or in Part 1 of

Annex VII (of the IED) are carried out, and any other directly associated activities on the same

site which have a technical connection with the activities listed in those Annexes and which

could have an effect on emissions and pollution”,

LCP: is a level 2 entity and is referring to a “combustion plant6” covered by Chapter III of the

IED7;

3 http://inspire.ec.europa.eu/documents/Data_Specifications/INSPIRE_DataSpecification_PF_v3.0.pdf 4 Article 2(4) of E-PRTR Regulation

5 Article 3(3) of IED and Article 2(3) of E-PRTR Regulation

6 Article 3 (25) of the IED includes the following definition: ‘combustion plant’ means any technical apparatus in which fuels are oxidised in order to use the heat thus generated. 7 Article 3(25), 3(40) and 3(41) of IED

http://inspire.ec.europa.eu/documents/Data_Specifications/INSPIRE_DataSpecification_PF_v3.0.pdf




Activity: refers to the activity performed in each entity according to pre-defined code lists..

Each entity is referenced to a specific code list that is represented in Codelist diagram.

Specifically, for:

o Site8: Definition of NACE Codes

o Facility – EPRTR9: Definition of Annex I activities according to Regulation 166/2006

Annex I.

o Installation & LCP – IED10: All activities listed in Annex I to Directive 2010/75/EU

which are operated in the installation or plant

Note: Fore Installations & LCPs a code list should have to be defined and uploaded into

EEA Data dictionary.

3.2 EU Registry – Class Diagram

8 http://converters.eionet.europa.eu/xmlfile/EPRTR_NaceActivityCode_1.xml 9 http://converters.eionet.europa.eu/xmlfile/EPRTR_AnnexlActivityCode_1.xml 10 http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=OJ:L:2010:334:0017:0119:en:PDF

http://converters.eionet.europa.eu/xmlfile/EPRTR_NaceActivityCode_1.xml

http://converters.eionet.europa.eu/xmlfile/EPRTR_AnnexlActivityCode_1.xml

http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=OJ:L:2010:334:0017:0119:en:PDF



January 25, 2016 Page: 10/35

Figure 1: EU Registry Class Diagram

Section 4.1.3 presents one by one all data types.

class Class Diagram - EU Registry

«featureType»

ProductionFacility

+ Address: AddressRepresentation

+ CompetentAuthority: RelatedParty

+ DateStart: Date

+ inspireIdPRTR: Identifier

+ name: CharacterString

+ NameofParentCompany: NameValue [1..*]

+ PointGeometry: GM_Point

+ riverBasinDistrict: RiverBasinDistrictValue

+ status: StatusType

«voidable»

+ Description: CharacterString

+ NumberOfEmployees: int

+ NumberOfInstallations: int

+ OperatingHours: int

+ ProductionVolume: Measure

«featureType»

ProductionInstallation


+ BaselineReportArticle22: boolean

+ BATArticle15(4): boolean


+ DateStart: Date

+ Inspections: InspectionsPerYear

+ inspireIdIED: Identifier


+ OperatorName: NameValue

+ pointGeometry: GM_Point

+ RelevantChapters: RelevantChaptersValue [0..*]

+ status: StatusType [1..*]

«voidable»

+ espirsid: CharacterString [0..1]

+ etsid: CharacterString [0..1]

«featureType»

LCP


+ DateStart: Date

+ Derogations: DerogationValue [1..*]

+ inspireIdLCP: Identifier


+ Permit: PermitValue

+ status: StatusType [1..*]

«featureType»

ProductionSite

+ Activity: ActivityCodeValue [1..*]


+ geometry: GM_Point

+ inspireId: Identifier


+ ownership: OwnershipPartType [1..*]

+ Region: NUTSLevelValue

+ riverBasinDistrict: RiverBasinDistrictValue

+ status: StatusType

+ WebsiteURL: URL [1..*]

«featureType»

Activity

+ activityCode: ActivityCodeValue [1..*]

+ mainEconomicActivity: Boolean

«voidable»

+ description: CharacterString

«featureType»

ReportData

+ AuthorityReport: RelatedParty

+ CoordinatesSystem: CoordinateSystemValue

+ CountryID: CountryCode

+ Date: Date

1..*

1

1

1..*

+hostedInstallation 1..*

+hostingSite

1

1..*

1

1..*

1

1

1..*

+hostedFacility 1..*

+hostingSite

«voidable»1

1

1..*

+hostedLCP

1..*

+hostingSite

1

1..*

1



January 25, 2016 Page: 11/35

3.3 EU Registry Data Types - (Logical diagram)

Figure 2: EU Registry - Data Types

The above Data types of EU Registry are a simple way to combine general fields/attributes into more

complex one and thus correspond to the UML class diagram.

For instance, according to UML diagram, 3 out of 4 feature types have Address attribute linked to

AddressRepresentation which is a complex data type. It is important to mention that even if

AddressRepresentation is not included in INSPIRE PF data specifications, we have included this data

type based on other INSPIRE themes. We can see that AddressRepresentation is a complex data type

which includes mandatory information such as an Administrative unit that belongs to this feature

type, the ISO2 code of the country which is linked to CountryCode Code list, street number with the

denomination locatorDesignator and street name11.

In addition, in order to cover the reporting needs for EPRTR (ProductionFacility feature type), there is

a specific case where a complex type (CompetentAuthority - RelatedParty) is linked to another

(Contact) data type. Section 4.1.3 presents one by one all data types.

11 According to the E-PRTR each facility needs to be reported together with the complete details of the ‘competent authority’. This is done via a complex field (CompetentAuthority-relatedparty) which has the full detailing of the competent authority.

class Data Types - EU Registry

«dataType»

StatusType

+ statusType: ConditionOfFacilityValue

«voidable»

+ description: CharacterString [0..1]

+ validFrom: Date

+ validTo: Date [0..1]

«dataType»

AddressRepresentation

+ Address: boolean

+ adminUnit: GeographicalName [1..*] {ordered}

+ CountryCode: CountryCode

+ locatorDesignator: CharacterString [0..*] {ordered}

+ postCode: CharacterString [0..1]

+ thoroughfare: GeographicalName [0..*] {ordered}

«voidable»

+ addressArea: GeographicalName [0..*] {ordered}

+ locatorName: GeographicalName [0..*] {ordered}

+ postName: GeographicalName [0..*] {ordered}

«dataType»

RelatedParty

+ contact: Contact [1..*]

+ individualName: PT_FreeText [1..*]

+ organisationName: PT_FreeText [1..*]

+ Type: CompetentAuthorityTypeValue

«voidable»

+ FaxNo: String [0..*]

+ positionName: PT_FreeText [0..1]

+ TelephoneNo: String

«dataType»

Contact

+ electronicMailAddress: CharacterString

«voidable»

+ address: AddressRepresentation [0..1]

+ contactInstructions: PT_FreeText [0..1]

+ hoursOfService: PT_FreeText [0..1]

+ telephoneFacsimile: CharacterString [0..*]

+ telephoneVoice: CharacterString [0..*]

+ website: URL [0..1]

«dataType»

Confidentiality

+ Confidential: boolean

+ Reasoning: Reasoning [0..1]

«dataType»

OwnershipPartType

+ ownershipType: OwnershipTypeValue

+ VATnumber: double [0..*]

«voidable»

+ percent: Percentage

«type»

Date

{root}

+ day: CharacterString [0..1]

+ month: CharacterString [0..1]

+ year: CharacterString [0..1]

«dataType»

InspectionsPerYear

+ NumberOfInspections: CharacterString [1..*]

+ Year: CharacterString [1..*]

«dataType»

PermitValue

+ DateOfGranting: Date

+ DateOfLastUpdate: Date

+ DateOfReconsideration: Date

«voidable»

+ Permit: URL

«dataType»

Measure

{root}

+ value: Number

+ convert(UnitOfMeasure*) : Measure

«dataType»

NameValue

+ Confidentiality: Confidentiality

+ Name: char



January 25, 2016 Page: 12/35

3.4 EU Registry Code Lists (Logical diagram)

Figure 3: EU Registry – Code Lists

All above Code Lists are aligned to specific values defined by Directives12 and taken from existing

INSPIRE code lists (either from PF or other Theme). Section 4.1.4 presents one by one all code lists.

4 Feature catalogue

4.1 Feature catalogue metadata

Application Schema EU Registry data model

12 This means that code lists used in the context of IED Reporting either arise from other policies (e.g. RiverBasinDistrict comes from reporting under the WFD and is as such supported by the EEA data dictionary) or are tailored for this project by being extracted from annexes of industrial emissions legislation (e.g. Annex 1 activities of the IED)

class Code Lists - Modul...

«codeList»

NACECodeValue

tags

extensibil i ty = none

vocabulary = http://converters.eionet.europa.eu/xmlfi le/EPRTR_NaceActivityCode_1.xml

«codeList»

IEDActiv ities

tags


vocabulary = http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=OJ:L:2010:334:0017:0119:en:PDF

«codeList»

E-PRTRCodeValue

tags


vocabulary = http://converters.eionet.europa.eu/xmlfi le/EPRTR_AnnexlActivityCode_1.xml

«codeList»

Activ ityCodeValue

tags

extensibil i ty =

vocabulary =

«codeList»

Reasoning

+ Article4(2)(a)ofDirective2003/4/EC(L41/29)

+ Article4(2)(b)ofDirective2003/4/EC(L41/29)

+ Article4(2)(c)ofDirective2003/4/EC(L41/29)

+ Article4(2)(d)ofDirective2003/4/EC(L41/29)

+ Article4(2)(e)ofDirective2003/4/EC(L41/29)

+ Article4(2)(f)ofDirective2003/4/EC(L41/29)

+ Article4(2)(g)ofDirective2003/4/EC(L41/29)

+ Article4(2)(h)ofDirective2003/4/EC(L41/29)

«codeList»

ConditionOfFacilityValue

+ decommissioned

+ functional

«codeList»

CountryCode

+ AT

+ BE

+ BG

+ CY

+ CZ

+ DE

+ DK

+ EE

+ EL

+ ES

+ FI

+ FR

+ HR

+ HU

+ IE

+ IT

+ LT

+ LU

+ LV

+ MT

+ NL

+ PL

+ PT

+ RO

+ SE

+ SI

+ SK

+ TR

+ UK

«codeList»

Relev antChaptersValue

+ CHAPTER III - SPECIAL PROVISIONS FOR COMBUSTION PLANTS

+ Chapter IV: Special provisions for waste incineration plants and waste co-incineration plant & Annex VI Technical Provisions

+ Chapter V: Special provisions for installations and activities using organic solvents & Annex VII Technical Provisions

- Chapter VI: Special provisions for installations producing titanium dioxide & Annex VIII Technical Provisions

Article 4(2)(a) of Directive 2003/4/EC,

Article 4(2)(b) of Directive 2003/4/EC

«codeList»

CompetentAuthorityTypeValue

+ GrantingofPermits

+ Inspectionsandenforcement

+ Other: boolean

«codeList»

CoordinateSystemValue

+ EPSG:3034/ETRS89-LCC

+ EPSG:4326/WGS84

+ ITRS

«codeList»

DerogationValue

+ Article31–DesulphurisationRate

+ Article32–TransitionalNationalPlan

+ Article33–LimitedLifetimeDerogation

+ Article34–SmallIsolatedSystem

+ Article35–DistrictHeatingPlants

«codeList»

Riv erBasinDistrictValue

tags

asDictionary = TRUE

extensibil i ty = any

vocabulary = http://converters.eionet.europa.eu/xmlfi le/EPRTR_RiverBasinDistrictCode_1.xml

xsdEncodingRule = iso 19136_2007_INSPIRE_Extensions

«codeList»

NUTSLev elValue

tags


obligation = technicalGuidance

vocabulary = http://dd.eionet.europa.eu/vocabulary/common/nuts2010/view

Values: AT, AT1,

AT11, AT111, AT112

«codeList»

OwnershipTypeValue



January 25, 2016 Page: 13/35

Version number 1.0

4.1.1 Types defined in the feature catalogue

Type Package Stereotypes

ReportData ProductionAndIndustrialFacilitiesExtension «featureType»

Site ProductionAndIndustrialFacilitiesExtension «featureType»

ProductionFacility ProductionAndIndustrialFacilitiesExtension «featureType»

ProductionInstallation ProductionAndIndustrialFacilitiesExtension «featureType»

LCP ProductionAndIndustrialFacilitiesExtension «featureType»

Activity ProductionAndIndustrialFacilitiesExtension «featureType»

Contact ProductionAndIndustrialFacilitiesExtension «dataType»

Date ProductionAndIndustrialFacilitiesExtension «dataType»

Measure ProductionAndIndustrialFacilitiesExtension «dataType»

AddressRepresentation ProductionAndIndustrialFacilitiesExtension «dataType»

Confidentiality ProductionAndIndustrialFacilitiesExtension «dataType»

InspectionsPerYear ProductionAndIndustrialFacilitiesExtension «dataType»

OwnershipPartType ProductionAndIndustrialFacilitiesExtension «dataType»

PermitValue ProductionAndIndustrialFacilitiesExtension «dataType»

StatusType ProductionAndIndustrialFacilitiesExtension «dataType»

RelatedParty ProductionAndIndustrialFacilitiesExtension «dataType»

ConditionOfFacilityValue ProductionAndIndustrialFacilitiesExtension «codeList»

CountryCode ProductionAndIndustrialFacilitiesExtension «codeList»



January 25, 2016 Page: 14/35

Type Package Stereotypes

RiverBasinDistrictValue ProductionAndIndustrialFacilitiesExtension «codeList»

ActivityCodeValue ProductionAndIndustrialFacilitiesExtension «codeList»

NACECodeValue ProductionAndIndustrialFacilitiesExtension «codeList»

IEDActivities ProductionAndIndustrialFacilitiesExtension «codeList»

E-PRTRCodeValue ProductionAndIndustrialFacilitiesExtension «codeList»

NUTSLevelValue ProductionAndIndustrialFacilitiesExtension «codeList»

CompetentAuthorityTypeValue ProductionAndIndustrialFacilitiesExtension «codeList»

CoordinateSystemValue ProductionAndIndustrialFacilitiesExtension «codeList»

DerogationValue ProductionAndIndustrialFacilitiesExtension «codeList»

Reasoning ProductionAndIndustrialFacilitiesExtension «codeList»

RelevantChaptersValue ProductionAndIndustrialFacilitiesExtension «codeList»

URL ProductionAndIndustrialFacilitiesExtension «codeList»

Table 1: Feature Catalogue

4.1.2 Feature Types

4.1.2.1 Spatial Object types

4.1.2.1.1 ProductionSite

ProductionSite

Name: ProductionSite

Definition: The distinct geographical location13 where the production facility was, is, or is intended to be

located. This includes all infrastructure, equipment and materials;

E-PRTR Definition: ‘site’ means the geographical location of the facility;

INSPIRE Definition:

A Production Site represents the geographical location of the facility or a piece of land where the

facility was, is, or is intended to be located. The location should be provided with defined

13 The 'distinct geographical location' usually refers to the X-Y coordinates of the 'entrance' of the industrial site.



January 25, 2016 Page: 15/35

geographical boundaries, thus the spatial object type may declare a geometry property as surface,

mapping the extension location for the Site. The geographical boundaries may be on land and in

water, and include above and below surface structures, both natural and man-made

Stereotypes: <<feature Type>>

Attribute Activity

Value type: ActivityCodeValue

Definition: Link to ActivityCodeValue codelist (Section 4.1.4.1) according to

http://dd.eionet.europa.eu/vocabulary/common/nace_r2/view

Multiple possibilities including all activities performed by level 2 entities within the site.

Multiplicity: 1..*

Attribute Address

Value type: AddressRepresentation

Definition: Link to AddressRepresentation complex datatype (Section 4.1.3.4).

Boolean to define whether street exits or not, if yes - Street, street number, town, postal code.

Multiplicity: 1

Attribute geomentry

Value type: GM_Point

Definition: Spatial property of the spatial object with a value that is a vector geometry type from ISO 19107.

This is the geometry property for the Production Site and it is set as a mandated point

location

Multiplicity: 1

Attribute inspireId

Value type: Identifier

Definition: An external object identifier of the spatial object, within the pre-defined boundaries for the format

of the identifier the will be set. DGENV & EEA & Agilis will provide guidance on creating valid

INSPIRE identifiers. An example of a valid InspireId would be a 2-character. ISO2 country code +

5-digit number + (sub)identifier.

INSPIRE NOTE An external object identifier is a unique object identifier published by the

responsible body, which may be used by external applications to reference the spatial object. The

identifier is an identifier of the spatial object, not an identifier of the real-world phenomenon.

Multiplicity: 1

Attribute name

Value type: CharacterString

Definition: This attribute was taken from INSPIRE DS and replaces “NameofSite” attribute.

Definition from INSPIRE: Official denomination or proper or conventional name of the site.

Multiplicity: 1

Attribute ownership

Value type: OwnershipPartType

Definition: Link to OwnershipPartType complex data type (Section 4.1.3.7).

The complex data type define one or more parent company names and VAT number that have

ownership over part or all the site

http://dd.eionet.europa.eu/vocabulary/common/nace_r2/view



January 25, 2016 Page: 16/35

Multiplicity: 1..*

Attribute Region

Value type: NUTSLevelValue

Definition: Link to NUTSLevelValue codelist (Section 4.1.4.7).

This codelist derived from a different theme (Statistical Unit) and contains two-letter codelist for

each country.

Multiplicity: 1

Attribute riverBasinDistrict

Value type: RiverBasinDistrictValue

Definition: Link to RiverBasinDistrictValue codelist (Section 4.1.4.2).

Multiplicity: 1

Attribute status

Value type: StatusType

Definition: Link to StatusType complex data type (Section 4.1.3.9).

This attribute informs whether or not a site is active/closed + if closed, reasoning provided

according to code list (values 'active' or 'closed')+ date + compulsory remarks field

Multiplicity: 1

Attribute WebsiteURL

Value type: URL

Definition: One or more website URLs that refer to activities running on the site

Multiplicity: 1..*

4.1.2.1.2 ProductionFacility

ProductionFacility

Name: ProductionFacility

Definition: One or more stationary technical units, that are operated by the same natural or legal person,

where one or more activities listed in the E-PRTR Regulation Annex I are carried out, and any

other directly associated activities which have a technical connection with the activities carried

out on that site and which could have an effect on emissions and pollution

-- Description --

A production facility groups together a single installation, set of installations or production

processes (stationary or mobile), which can be defined within a single geographical boundary,

organizational unit or production process. A production facility can also be identified as one or

more installations located on the same site that are operated by the same natural or legal person

and in which production activities are being carried out. Such a facility groups potentially the

land, buildings, and equipment used in carrying on an industrial business or other undertaking

or service.


Attribute Address




Multiplicity: 1

Attribute CompetentAuthority

Value type: RelatedParty



January 25, 2016 Page: 17/35

Definition: Link to RelatedParty complex datatype (Section 4.1.3.10).

Complete name, address, phone and mail of the environmental authority responsible for the E-

PRTR report of the concerned facility

Multiplicity: 1

Attribute DateStart

Value type: Date

Definition: Link to Date complex data type (Section 4.1.3.2).

Date where the entities was first granted an operational permit for a comparable activity

Multiplicity: 1

Attribute inspireIdPRTR


Definition: An external object identifier of the spatial object, that will be attributed by the MS, but DGENV &

EEA & Agilis will provide guidance on creating valid INSPIRE identifiers. An example of a valid

InspireId would be a 2-character. ISO2 country code + 5-digit number + PRTR .

INSPIRE NOTE: An external object identifier is a unique object identifier published by the

responsible body, which may be used by external applications to reference the spatial object.

The identifier is an identifier of the spatial object, not an identifier of the real-world

phenomenon.

Multiplicity: 1

Attribute name


Definition: This attribute was taken from INSPIRE DS and replaces “Name of the facility” attribute.

Definition from INSPIRE: Official denomination or proper or conventional name of the site.

Multiplicity: 1

Attribute NameofParentCompany


Definition: This attribute derived from EPRTR Directive.

Multiplicity: 1..*

Attribute PointGeomentry


Definition: Spatial property of the spatial object with a value that is a point geometry type from ISO 19107.

This is the geometry property for the Production facility and it is set as a mandated point

location

Multiplicity: 1

Attribute riverBasinDistrict

Value type: RiverBasinDistrictValue


Multiplicity: 1

Attribute status



January 25, 2016 Page: 18/35




according to code list (values 'active' or 'closed') + date + compulsory remarks field

Multiplicity: 1

<<voidable>> Attribute Description


Definition: An optional attribute according to E-PRTR Regulation

Multiplicity: 1

<<voidable>> Attribute NumberOfEmployees

Value type: int


Multiplicity: 1

<<voidable>> Attribute NumberOfInstallations

Value type: int


Multiplicity: 1

<<voidable>> Attribute OperatingHours

Value type: int


Multiplicity: 1

<<voidable>> Attribute ProductionVolume

Value type: Measure

Definition: Link to Measure complex data type (Section 4.1.3.3).

Multiplicity: 1

4.1.2.1.3 ProductionInstallation

ProductionInstallation

Name: ProductionInstallation

Definition: ‘Installation’ means a stationary technical unit within which one or more activities listed in

Annex I or in Part 1 of Annex VII are carried out, and any other directly associated activities

on the same site which have a technical connection with the activities listed in those

Annexes and which could have an effect on emissions and pollution;


Attribute Address



Boolean to define whether street exits or not, if yes - Street, street number, town, postal

code.

Multiplicity: 1

Attribute BaselineReportArticle22

Value type: boolean

Definition: According to the DS this attribute is just a true/false value, which will be important to later



January 25, 2016 Page: 19/35

QA/QC rules. It actually specifies if the installation complies with the specific article

Multiplicity: 1

Attribute BATArticle 15(4)

Value type: boolean

Definition: According to the DS this attribute is just a true/false value, which will be important to later

QA/QC rules. It actually specifies if the installation complies with the specific article

Multiplicity: 1


Value type: RelatedParty (a sub-attribute of the upper level CompetentAuthorityParty)


Complete name, address, phone and mail of the environmental authority responsible for

the E-PRTR report of the concerned facility

Multiplicity: 1

Attribute DateStart

Value type: Date



Multiplicity: 1

Attribute Inspections

Value type: InspectionsPerYear

Definition: Link to InspectionsPerYear complex data type (Section 4.1.3.6).

Competent authority for inspections and enforcement

Multiplicity: 1

Attribute inspireIdIED


Definition: An external object identifier of the spatial object, that will be defined by the Member States.

DGENV & EEA& Agilis will provide guidance on creating valid INSPIRE identifiers. An

example of a valid InspireId would be a 2-character. ISO2 country code + 5-digit number +

IED.


responsible body, which may be used by external applications to reference the spatial

object. The identifier is an identifier of the spatial object, not an identifier of the real-world

phenomenon.

Multiplicity: 1

Attribute name


Definition: This attribute was taken from INSPIRE DS and replaces “Installation name” attribute.

In a format compatible with the field ‘Name of the facility’ used in the reporting under

Regulation (EC) No 166/2006; if possible.

Definition from INSPIRE: Official denomination or proper or conventional name of the

site.



January 25, 2016 Page: 20/35

Multiplicity: 1

Attribute OperatorName


Definition: In a format compatible with the field ‘Name of parent company’ used in the reporting under

Regulation (EC) No 166/2006, if possible.

Multiplicity: 1

Attribute PointGeomentry


Definition: Spatial property of the spatial object with a value that is a vector geometry type from ISO

19107.

This is the geometry property for the Production installation (IED) and it is set as a

mandated point location

Multiplicity: 1

Attribute RelevantChapters

Value type: RelevantChaptersValue


Indicate which of the Chapters III, IV, V and VI of Directive 2010/75/EU also apply to the

installation (or part thereof).

Multiplicity: 0..*

Attribute status




according to code list (values 'active' or 'closed') + date + compulsory remarks field

Multiplicity: 1..*

<<voidable>> Attribute espirsid


Definition: An optional field, where the IED installation is, fully or partly, covered by Directive

2012/18/EU, provide the unique identifier used in the Seveso Plant Information Retrieval

System (SPIRS).

Multiplicity: 0..1

<<voidable>> Attribute etsid


Definition: Where the IED installation is, fully or partly, covered by Directive 2003/87/EC, provide the

unique registry identifier from the EU Transaction Log.

Multiplicity: 0..1

4.1.2.1.4 LCP

LCP

Name: LCP

Definition: Combustion plants with a total rated thermal input is equal to or greater than 50 MW,

irrespective of the type of fuel used






January 25, 2016 Page: 21/35


Attributes define complete name, address, phone and mail of the environmental authority

responsible for the LCP

Multiplicity: 1

Attribute DateStart

Value type: Date



Multiplicity: 1

Attribute Derogations

Value type: DerogationValue

Definition: Link to DerogationValue codelist (Section 4.1.4.3).

Multiple choice of derogations applying according to predefined code list

Multiplicity: 1..*

Attribute inspireIdLCP


Definition: An external object identifier of the spatial object, that will be defined by the Member States.

DGENV & EEA & Agilis will provide guidance on creating valid INSPIRE identifiers. An

example of a valid InspireId would be a 2-character. ISO2 country code + 5-digit number +

LCP.


responsible body, which may be used by external applications to reference the spatial

object. The identifier is an identifier of the spatial object, not an identifier of the real-world

phenomenon.

Multiplicity: 1

Attribute name


Definition: This attribute was taken from INSPIRE DS and replaces “NameOfPlant” attribute.

Definition from INSPIRE: Official denomination or proper or conventional name of the

site.

Multiplicity: 1

Attribute Permit

Value type: PermitValue

Definition: Link to PermitValue complex data type (Section 4.1.3.8)

Attributes allow to provide URL of permit if any, date of first granting, date of last

reconsideration, date of last update

Multiplicity: 1

Attribute status






January 25, 2016 Page: 22/35

according to code list (with values 'active' or 'closed') + date + compulsory remarks field

Multiplicity: 1..*

4.1.2.2 Object types

4.1.2.2.1 ReportData

ReportData

Name: ReportData

Definition: This specific feature type has been isolated as some common attributes have to be reported in

each level 1 and 2 entities (Site, Facility, Installation, LCP)


Attribute AuthorutyReport



Defining name, address, phone, email and website of authority responsible for the Registry

submission.

Multiplicity: 1

Attribute CoordinatesSystem

Value type: CoordinateSystemValue

Definition: Link to CoordinateSystemValue codelist (Section 4.1.4.6).

In this attribute the MS has to report the Coordinate reference system from a predefined

codelist.

Multiplicity: 1

Attribute CountryID

Value type: CountryCode

Definition: Link to CountryCode codelist (Section 4.1.4.4).

According to specific Vocabulary: Strict ISO-3166 country codes

Multiplicity: 1

Attribute Date

Value type: Date


Date of last update in the National Systems of the data submitted

Multiplicity: 1

4.1.2.2.2 Activity

Activity

Name: Activity

Definition: This specific feature type has been isolated as some common attributes have to be reported for

level 2 entities (Facility, Installation, LCP)


Attribute Activity

Value type: ActivityCodeValue

Definition: Link to ActivityCodeValue codelist (Section 4.1.4.1) according to specific directive of each entity.

Classification of the activity according to European legislation.



January 25, 2016 Page: 23/35

Multiple possibilities including all activities performed by level 2 entities within the site.

Multiplicity: 1..*

Attribute mainEconomicActivity

Value type: Boolean

Definition: A true/false value in case, the main/primary activity is reported.

Primary activity in terms of significance and production volume.

Multiplicity: 1

<<voidable>> Attribute description


Definition: Descriptive statement about the activity in line with the declared classification from legislation

Multiplicity: 1

4.1.3 Data Types

4.1.3.1 Contact

Contact

Definition: Communication channels by which it is possible to gain access to someone or something.

Description: -

Stereotypes: <<dataType>>

Attribute electronicMailAddress


Definition: An address of the organisation's or individual's electronic mailbox.

Multiplicity: 1

<<voidable>> Attribute address




Multiplicity: 0..1

<<voidable>> Attribute contactInstructions

Value type: PT_FreeText

Definition: Supplementary instructions on how or when to contact an individual or organisation.

Multiplicity: 0..1

<<voidable>> Attribute hoursOfService


Definition: Periods of time when the organisation or individual can be contacted.

Multiplicity: 0..1

<<voidable>> Attribute telephoneFacsimile


Definition: Number of a facsimile machine of the organisation or individual.

Multiplicity: 0..*

<<voidable>> Attribute telephoneVoice


Definition: Telephone number of the organisation or individual.



January 25, 2016 Page: 24/35

Multiplicity: 0..*

<<voidable>> Attribute website

Value type: URL

Definition: Pages provided on the World Wide Web by the organisation or individual.

Multiplicity: 0..1

4.1.3.2 Date

Date

Definition: Specific date that indicates important information for the reporting entity

Description: This data type derived from INSPIRE relevant data types and include information about a specific

day, month and year


Attribute day


Definition: -

Multiplicity: 0..1

Attribute month


Definition: -

Multiplicity: 0..1

Attribute year


Definition: -

Multiplicity: 0..1

4.1.3.3 Measure

Measure

Definition: An optional data type for the production volume

Description: According to INSPIRE:

The result from performing the act or process of ascertaining the extent, dimensions, or quantity

of some entity.

A measure is always associated to a unit of measure. Ratio measures where the two base measures

are in the same units (often considered unit-less) should be associated to UnitOfMeasure (same

meter/meter for map scale) so that conversions to non-unitless ratios can be accomplished (such

as miles/inch).


Attribute value

Value type: Number

Definition: The numerical value quantifying the extent or size of some quantity, in the units specified by the

associated UnitOfMeasure class.

Multiplicity: 1

Operation convert(UnitOfMeasure*)

Parameters: [inout] target: UnitOfMeasure

Value type: Measure



January 25, 2016 Page: 25/35

Definition: An operation to convert from one unit of measure to another such as feet to meters, or degrees to

radians.

4.1.3.4 AddressRepresentation

AddressRepresentation

Definition: Representation of an address spatial object for use in external application schemas that need

to include the basic, address information in a readable way.

Description: According to INSPIRE:

NOTE 1 The data type includes the all necessary readable address components as well as the

address locator(s), which allows the identification of the address spatial objects, e.g., country,

region, municipality, address area, post code, street name and address number. It also includes

an optional reference to the full address spatial object.

NOTE 2 The datatype could be used in application schemas that wish to include address

information e.g. in a dataset that registers buildings or properties.


Attribute Address

Value type: Boolean

Definition: A true/false value

Multiplicity: 1

Attribute adminUnit

Value type: GeographicalName

Definition: The name or names of a unit of administration where a Member State has and/or exercises

jurisdictional rights, for local, regional and national governance.

Multiplicity: 1..*

Attribute CountryCode

Value type: CountryCode

Definition: Link to CountryCode codelist (Section 4.1.4.4).

According to specific Vocabulary: Strict ISO-3166 country codes

Multiplicity: 1

Attribute CountryCode


Definition: A number or a sequence of characters which allows a user or an application to interpret, parse

and format the locator within the relevant scope. A locator may include more

Multiplicity: 0..1

Attribute PostCode


Definition: A code created and maintained for postal purposes to identify a subdivision of addresses and

postal delivery

Multiplicity: 0..1

Attribute Thoroughfare


Definition: Street name

Multiplicity: 0..*

<<voidable>> Attribute adressArea



January 25, 2016 Page: 26/35


Definition: The name or names of a geographic area or locality that groups a number of addressable

objects for addressing purposes, without being an administrative unit.

Multiplicity: 0..*

<<voidable>> Attribute locatorName


Definition: Proper noun(s) applied to the real world entity identified by the locator.

Multiplicity: 0..*

<<voidable>> Attribute postName


Definition: One or more names created and maintained for postal purposes to identify a subdivision of

addresses and postal delivery points.

Multiplicity: 0..*

4.1.3.5 Confidentiality

Confidentiality

Definition: Define legal interpretation whether or not an entity is confidential or not.

Description: Basically it contains an attribute which justifies the confidentiality


Attribute Confidential

Value type: Boolean

Definition: A true/false value

Multiplicity: 1

Attribute Reasoning

Value type: Reasoning

Definition: Reasoning for confidentiality (that for the time being will only apply to the fields 'name of the

parent company' (E-PRTR) and 'operator name' (IED)

a) Confidentiality of proceedings of public authorities (Article4(2)(a)ofDirective2003/4/EC(L41/29))

b) International relations, public security/national defence (Article4(2)(b)ofDirective2003/4/EC(L41/29) )

c) Course of justice / fair trial (Article4(2)(c)ofDirective2003/4/EC(L41/29)

d) Confidentiality of commercial information (Article4(2)(d)ofDirective2003/4/EC(L41/29)

e) Intellectual property rights (Article4(2)(e)ofDirective2003/4/EC(L41/29)

f) Confidentiality of personal data (Article4(2)(f)ofDirective2003/4/EC(L41/29)

g) Interest of protection of persons supplying information (Article4(2)(g)ofDirective2003/4/EC(L41/29)

Protection of the environment / location of rare species (Article4(2)(h)ofDirective2003/4/EC(L41/29)

Multiplicity: 1

4.1.3.6 InspectionsPerYear

InspectionPerYear

Definition: Define the inspection per year in an Installation IED entity

Description: It contains information about the number of inspections and the reporting year


Attribute NumberOfInspections



January 25, 2016 Page: 27/35


Definition:

Multiplicity: 1..*

Attribute Year


Definition:

Multiplicity: 1..*

4.1.3.7 OwnershipPartType

OwnershipPartType

Definition: Define one or more parent company names and VAT number that have ownership over part or

all the site

Description: Contains information about the type of the ownership, the VAT number and the percentage of

the ownership if it available


Attribute ownershipType

Value type: OwnershipTypeValue

Definition: Link to OwnershiptypeValue codelist (Section 4.1.4.11)

Multiplicity: 1

Attribute VATnumber

Value type: Double

Definition:

Multiplicity: 0..1

<<voidable>> Attribute percent

Value type: Percentage

Definition: Percentage of the ownership

Multiplicity: 1

4.1.3.8 PermitValue

PermitValue

Definition: Define any information concerning the permit

Description: Attributes allow to provide URL of permit if any, date of first granting, date of last

reconsideration, date of last update


Attribute DateofGranting

Value type: Date

Definition: Link to Date complex data type (Section 4.1.3.2)

Multiplicity: 1

Attribute DateOfLastUpdate

Value type: Date


Multiplicity: 1

Attribute DateOfReconsideration

Value type: Date



January 25, 2016 Page: 28/35


Multiplicity: 1

Attribute Permit

Value type: URL

Definition: Pages provided on the World Wide Web by the organisation or individual.

Multiplicity: 1

4.1.3.9 StatusType

StatusType

Definition: The state or condition of a technical component, with regard to the functional and operational

order, in which it is arranged for a limited or extended time period.

Description: It applies equally to the technical unit (facility, installation or installation part), to the production

site, to the parcel and to the production building.


Attribute statusType

Value type: ConfitionOfFacilityValue

Definition: Link to ConfitionOfFacilityValue code list (Section 4.1.4.9)

Multiplicity: 1

<<voidable>> Attribute description


Definition: Descriptive statement about the declared status.

Multiplicity: 0..1

<<voidable>> Attribute validFrom

Value type: Date


Multiplicity: 1

<<voidable>> Attribute validTo

Value type: Date


Multiplicity: 0..1

4.1.3.10 RelatedParty

RelatedParty

Definition: An organisation or a person with a role related to a resource.

Description: A party, typically an individual person, acting as a general point of contact for a resource can be

specified without providing any particular role.


Attribute Contact

Value type: Contact

Definition: Link to Contact data type (Section 4.1.3.1)

Contact information for the related party.

Multiplicity: 1..*

Attribute individualName




January 25, 2016 Page: 29/35

Definition: Contact information for the contact person responsible for managing the object under IED,

under SEVESO, etc.

Multiplicity: 1..*

Attribute organisationName


Definition: Name of the related organisation.

Multiplicity: 1..*

Attribute Type

Value type: CompetentAuthorityTypeValue

Definition: Link to CompetentAuthorityTypeValue codelist (Section 4.1.4.8).

Multiplicity: 1

<<voidable>> Attribute FaxNo

Value type: String

Definition: FAX number

Multiplicity: 0..1

<<voidable>> Attribute positionName


Definition: Position of the party in relation to a resource, such as head of department.

Multiplicity: 0..1

<<voidable>> Attribute TelephoneNo

Value type: String

Definition: telephone number of the Competent Authority or even to the assigned personnel

Multiplicity: 1

4.1.4 Code lists

4.1.4.1 ActivityCodeValue

ActivityCodeValue

Definition: The ActivityCodeValue code list hosts all the potential reference values for the attribute

activityCode in the Activity class.

Description: -

Extensibility: Any

Identifier:

Values: The allowed values for this code list are depending on specific directive of each reported entity.

Classification of the activity according to European legislation.

4.1.4.1.1 NACECodeValue

NACECodeValue

Definition: The NACECodeValue code list hosts a family of reference values for the attribute activityCode in

the Activity class. The list hosts the classification for the activities according to the Council

Regulation 3037/90/EEC.

Description NACE classification has a hierarchical structure founded on different levels embedded in the

activity code. The activity code is accompanied by the activity denomination.

Extensibility: None



January 25, 2016 Page: 30/35

Identifier: http://converters.eionet.europa.eu/xmlfile/EPRTR_NaceActivityCode_1.xml

Values: Allowed values according to NACE Activity Code, publicly available on EIONET portal

4.1.4.1.2 IEDActivities

IEDActivities

Definition: All activities listed in Annex I to Directive 2010/75/EU which are operated in the installation.

Description The threshold values given below generally refer to production capacities or outputs. Where

several activities falling under the same activity description containing a threshold are operated

in the same installation, the capacities of such activities are added together. For waste

management activities, this calculation shall apply at the level of activities 5.1, 5.3(a) and 5.3(b)

Extensibility: None

Identifier: http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=OJ:L:2010:334:0017:0119:en:PDF

Values: Allowed values according to IED Directive, NOTE: this codelist needs to be finalized and

uploaded in EIONET portal

4.1.4.1.3 E-PRTRCodeValue

ActivityCodeValue

Definition: The E-PRTRCodeValue code list hosts a family of reference values for the attribute activityCode

in the Activity class. The list hosts the classification for the activities according to the E-PRTR

register.

Description E-PRTR classification has a hierarchical structure funded on different levels embedded in the

activity code. The activity code is accompanied by the activity denomination.

Extensibility: None

Identifier: http://converters.eionet.europa.eu/xmlfile/EPRTR_AnnexlActivityCode_1.xml

Values: Allowed values according to Annex 1 of EPRTR Directive

4.1.4.2 RiverBasinDistrictValue

RiverBasinDistrictValue

Definition: Code identifiers and/or names assigned to river basin districts.The allowed values for this

code list comprise any values defined by data providers.

Description

Extensibility: Any

Identifier: http://inspire.ec.europa.eu/codeList/RiverBasinDistrictValue

Values: The allowed values for this code list comprise any values defined by data providers.

4.1.4.3 DerogationValue

DerogationValue

Definition: An exemption from or relaxation of legal requirements

Description

Extensibility: Any

Identifier:

Values: The allowed values for this code list comprise any values defined by data providers.

Article 15 – Emerging techniques (for the testing and use of emerging techniques for a total

http://converters.eionet.europa.eu/xmlfile/EPRTR_NaceActivityCode_1.xml

http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=OJ:L:2010:334:0017:0119:en:PDF

http://converters.eionet.europa.eu/xmlfile/EPRTR_AnnexlActivityCode_1.xml

http://inspire.ec.europa.eu/codeList/RiverBasinDistrictValue



January 25, 2016 Page: 31/35

period of time not exceeding 9 months)

Article 30 – Emission limit values (the competent authority may grant a derogation for a

maximum of 6 months from the obligation to comply with the emission limit values)

Article31–DesulphurisationRate (provided for in paragraphs 2 and 3 for sulphur dioxide in

respect of a combustion plant which to this end normally uses low-sulphur fuel, in cases

where the operator is unable to comply with those limit values because of an interruption in

the supply of low-sulphur fuel resulting from a serious shortage

Article32–TransitionalNationalPlan (the article requires 'timely compliance with the

emission limit values from1 July 2020). This means there is a time limit to which this

derogation applies that can be no later then that data.

Article33–LimitedLifetimeDerogation (the plant cannot be operated more than 17 500

operating hours between 1 January 2016and 31 December 2023. After this the derogation

has to become invalid).

Article34–SmallIsolatedSystem (this derogation automatically becomes invalid after 31

December 2019).

Article35–DistrictHeatingPlants (if this derogation is used then indicating the total rated

thermal input becomes mandatory to indicate. That input cannot exceed 200 MW. The

derogation also automatically becomes invalid after 31 December 2022).

4.1.4.4 CountryCode

Countrycode

Definition: Country code as defined in the Interinstitutional style guide published by the Publications

Office of the European Union.

Description -

Extensibility: Any

Identifier: http://publications.europa.eu/code/en/en-5000600.htm

Values: Country and territory codes

4.1.4.5 Reasoning

Reasoning

Definition: This attribute informs about a reasoning codelist for confidentiality of an entity.

Description -

Extensibility: Any

Identifier:

Values: Country code as defined in the Interinstitutional style guide published by the Publications

h) Confidentiality of proceedings of public authorities (Article4(2)(a)ofDirective2003/4/EC(L41/29))

i) International relations, public security/national defence (Article4(2)(b)ofDirective2003/4/EC(L41/29)

)

j) Course of justice / fair trial (Article4(2)(c)ofDirective2003/4/EC(L41/29)

k) Confidentiality of commercial information (Article4(2)(d)ofDirective2003/4/EC(L41/29)

l) Intellectual property rights (Article4(2)(e)ofDirective2003/4/EC(L41/29)

m) Confidentiality of personal data (Article4(2)(f)ofDirective2003/4/EC(L41/29)

n) Interest of protection of persons supplying information (Article4(2)(g)ofDirective2003/4/EC(L41/29)

o) Protection of the environment / location of rare species (Article4(2)(h)ofDirective2003/4/EC(L41/29)

http://publications.europa.eu/code/en/en-5000600.htm



January 25, 2016 Page: 32/35

4.1.4.6 CoordinateSystemValue

CoordinateSystemValue

Definition: The Coordinate reference system is defined for each reported entity.

Description -

Extensibility: Any

Identifier:

Values: Country code as defined in the Interinstitutional style guide published by the Publications

EPSG:3034/ETRS89-LCC

EPSG:4326/WGS84

ITRS

4.1.4.7 NUTSLevelValue

NUTSLevelValue

Definition: The code values for the NUTS levels.

Description -

Extensibility: Any

Identifier: http://dd.eionet.europa.eu/vocabulary/common/nuts2010/view

Values: According to the vocabulary publicly available on EIONET portal

4.1.4.8 CompetentAuthorityTypeValue

CompetentAuthorityTypeValue

Definition: Indicates the type of the competent authority

Description -

Extensibility: Any

Identifier:

Values: According to the IED data specifications. Two types are defined:

GrantingofPermits & Inspectionsandenforcement

4.1.4.9 ConditionOfFacilityValue

ConditionOfFacilityValue

Definition: The status of a facility with regards to its completion and use.

Description -

Extensibility: Any

Identifier:

Values: According to given data specifications, two types are defined:

Functional – as Active

Decommissioned – as Closed

4.1.4.10 RelevantChaptersValue

RelevantChaptersValue

Definition: Other relevant Chapters of Directive 2010/75/EU. Indicate which of the Chapters III, IV, V

and VI of Directive 2010/75/EU also apply to the installation (or part thereof).

Description -

http://dd.eionet.europa.eu/vocabulary/common/nuts2010/view



January 25, 2016 Page: 33/35

Extensibility: Any

Identifier:

Values: The allowed values for this code list comprise any values that also applies to the installation:

CHAPTER III - SPECIAL PROVISIONS FOR COMBUSTION PLANTS

Chapter IV: Special provisions for waste incineration plants and waste co-incineration

plant & Annex VI Technical Provisions

Chapter V: Special provisions for installations and activities using organic solvents &

Annex VII Technical Provisions

Chapter VI: Special provisions for installations producing titanium dioxide & Annex

VIII Technical Provisions

4.1.4.11 OwnershipTypeValue

OwnershipTypeValue

Definition: Type of ownership (the values of the code list 'ownership' needs to be (still) defined)

Description -

Extensibility: Any

Identifier:

Values:

Table of Acronyms

Acronym Description

IED Directive 2010/75/EU on Industrial Emissions

E-PRTR Regulation (EC) No 166/2006 establishing a European Pollutant

Release and Transfer Register

DG ENV Directorate-General for Environment

EEA European Environment Agency

MS Member States

EU European Union

DS Data Specifications

NS Network Services



January 25, 2016 Page: 34/35

PF Production Facility

AQD Air Quality Data

LCP Large Combustion Plant

NUTS Nomenclature of Territorial Units for Statistics

INSPIRE Directive 2007/2/EC establishing an Infrastructure for Spatial

Information in the European Community

RBD River Basin District



January 25, 2016 Page: 35/35

List of Terms - Summary of stereotypes

Stereotype name

Stereotypes are

effectively used to

extend UML model

in a consistent

manner14 or

altering the

meaning, display,

characteristics or

syntax of a basic

UML model

element15.

Use Description

«featureType» Feature-type Represents simply a class of data together with

respective attributes. Other possible denomination of

the word «class» is layer; table; category

«dataType» Structured

data type

Is a set of predefined data values that an attribute has to

have. For example as data type stands the type of the

value that an attribute of a layer can have (e.g. integer,

character, string, boolean).

A data type can be either a simple data type, as

explained above, or a complex one. A complex data type

is when a data type of an attribute is comprised of

multiple data types. A good example based on our case

is the attribute «Address » which is a complex data type

and it includes other data types namely street name,

street number, postal code i.e.

«codeList» Extensible

enumeration

A predefined list from which some specific fields take

values.

14 http://www.agilemodeling.com/style/stereotype.htm 15 http://www.sparxsystems.com/enterprise_architect_user_guide/10/standard_uml_models/stereotypedlg.html

http://www.agilemodeling.com/style/stereotype.htm

http://www.sparxsystems.com/enterprise_architect_user_guide/10/standard_uml_models/stereotypedlg.html

Documents

EU Registry Data model - Documentation · The structure of the document follows a standard representation of a data model. The second section provides an overview of the data model