1 Integration of the LCP Reporting Into the E-PRTR Scope and Technical specifications December 3rd

Content Scope of the project New system structure and objectives Unify the way of reporting  Data specification and schemas (Task 1 and Task 2) Validation rules  QA\QC rules in FME process (Task 3) Harvesting of data  thematic DB (EPRTR + LCP) – centralised Registry DB (Task 4) Advantages of our technical approach MDB to XML tool Current status Support and assitance 2

3 Scope of the project Integrate the Large Combustion Plants reporting requirements into E-PRTR Reporting System, complying the E-PRTR methodology, that implies: Re-structure the E-PRTR XML Reporting Schema including LCP entities and attributes Update the overall reporting workflow and associated tool in ReportNet validation rules automated feedbacks conversion tools Design of thematic database for E-PRTR and LCP update the scripts to harvest and transfer the XML files into thematic database.

New system structure Analysis of current status: Way of reporting: LCP  Webforms E-PRTR  XML Databases: LCP  None E-PRTR  SQL databases (Master, Public, cms, review) Considerations to take into account: New common plataform Centralised register Thematic DB

Objetives Unify the way of reporting Common XML with all information from E-PRTR and LCP (only with thematic data) Schemas for this new XML Validations rules: Updates in E-PRTR QA\QC rules (without administrative units) Addition of LCP QA\QC rules New procedure to execute QA\QC rules from ReportNet (FME technology) Harvesting of data Design of new thematic database for E-PRTR and LCP New procedures to haverst data from XML file into DB New procedure to convert MDB files into XML

6 Unify the way of reporting Data specificiation and schemas(Task 1 and Task 2) XML definition : UML (without administrative and INSPIRE related units) Schema related to the XML, generated and uploaded to Data Dictionary :

Validation rules – Qa\Qc rules 7 Currently : Off -line tool Disadvantages: Hard maintenance Advantages: Usefull for MS With the centralised register : Remove several validations Include new ones for LCP Generate the executable and install on local workstation (hard maintenance of off-line tool) implies

Qa-Qc rules – new implementation FME solution Feature Manipulation Engine = ETL tools for data transfromations and data translations Development of a FME process for all validations related to thematic data for EPRTR and LCP Simulate the off line tool behaviour for MS New link in ReportNet The MS will receive the result in HTML format

Qa-Qc rules – new implementation 9 Validation result Execute FME process Result in HTML Upload XML Member States Internal process

Harvesting of data 10 Centralising information entails: Adapt E-PRTR database Implement the integration between Thematic data and Register information (previously the centralised register design has to be done) Integrate LCP Thematic data into EPRTR data model (previously the E-PRTR data model has to be designed)

Common platform 11 Centralised Register –Administrative units –INSPIRE relevant elements (identifiers, names, addreses, geographical coordinates, NUTS codes, NACE codes, compentent authorities…) Thematic dataflows –Content-related information Thematic data By ID Centraised Register Final Data Bases

Harvesting of data – new structure 12 Separate the harvesting data in two data workflows: Thematic data into thematic database (by Bilbomatica) Final information into final database (in other project) Bilbomatica Thematic DB Centralised Register Final DB

H arvesting of data – new implementation 13 FME solution Feature Manipulation Engine = ETL tools for data transfromations and data translations Automatic process Get data from CDR Validate information Save information into the Thematic database

Advantages of our technical approach 14 Without off line tools EEA has the environment to developt, run and maintain this kind of process Bilbomatica has experience in this task with other projects Alternative to MDB files FME process to convert mdb file into xml and send the result by

MDB to XML Execute FME process Upload MDB and XML file attached by Member states Internal process

Current status on the project To achive the Unify the way of reporting: Data model designed and accepted (UML) XML reporting Schema for EPRTR and LCP according to the UML, designed and accepted (.xsd) Validations rules E-PRTR qa-qc rules Definition of rules: Defined and accepted Qa\Qc script: Currently implementing LCP qa-qc rules: Definition of rules: Working on them Qa\Qc script: Pending FME process: Pending 16

Current status on the project Harvesting of data Database Model according to the UML: Working on the desing in SQL Server FME process to harves tdata: Pending MDB to XML Access Database Model according to the UML: Working on the desing FME process : Pending 17

Support and assistance After implementation, buf fixing and deployment: Technical team will provide a technical workshop with the EU Member States in order to explain the new system and the new way to work. Guidance for E-PRTR and LCP reporters With MS comments  updates, bug fixing and final deliverable The integration of LCP into E-PRTR will take place in 2018, for LCP & EPRTR data of the

Questions?

THANK YOU