1. 2008-12-02 | Slide 1 E-PRTR data flows in a Shared Environmental Information System 2008-12-02 Norbert Pfaffinger IT Business Analysis Federal Environment Agency Austria

2. 2008-12-02 | Slide 2 Contents 1.Overview of Data Flows in the National PRTR Application 2.Overview of Interoperability efforts taken i

3. 2008-12-02 | Slide 3 PRTR data flows within AT Just 1 National Web Application (no interfaces to subsidiary data sources, though interfaces to sibling national applications) Operators of PRTR relevant facilities log in to enter data via GUI Regional and national authorities log in to validate data National PRTR register embedded within the “EDM” (Electronic Data Management for the Environmental Sector; run by the Ministry)

4. 2008-12-02 | Slide 4 Master data registryforpersonsandinstallationseRAS EDM PORTAL eCERTIFICATE eHW- TRANSPORT eCOMPOST eMASS- BALANCE eINCINERATIO N eLANDFILL ePERMITS eEoL- VEHICLES eWEEE ePRTR eSHIPMENT Single sign on access to apps Applications AT Application Landscape for PRTR: Embedding within EDM

5. 2008-12-02 | Slide 5 “EZG“ “HFKW“ “EMREG-OG“ ePRTR “Strahlenregister“ Portal edm.gv.at Data harmonization Master Data Reg. eRAS Overall architecture eReporting Helpdesk eIncineration eWEEE eHW-Transport eBatteries ePackaging eEoL-Vehicles eShipment eMass-Balance eLandfill ePermits eCertificateeCompost Embedding within EDM: AT Task Chart

6. 2008-12-02 | Slide 6 Emission Certificate PRTR AT PRTR Application Interfaces Master data registry (parties, installations, …) Reference List Register Waste Mass Balance 12 3 4 12&: Real time access to data (not copied) 3: Option to use data from other reports (copied) 4 : XML export for EU reporting. Parameters approx the same, time frames the same as with collected data Commercial Register 5 5 : Daily update from Austrian Commercial Register Automated update query upload (XML, FTP, copied)

7. 2008-12-02 | Slide 7 General Interoperability Principles the AT PRTR Register “inherits” from the EDM Use of a common master data register, for parties, facilities, installations, etc. Use of GS1 GLNs for the identification of anything registered in the master data register  next slides Use of a common reference list register (for lists of countries, pollutants, types of waste, etc.)  next slides Data models built according to UN/CEFACT methodology using components from the UN/CEFACT Core Component Library (CCL) (some EDM related data models handed in for standardisation, esp. for Transboundary Movements of Waste – Basel Convention – EUDIN project)  next slides

8. 2008-12-02 | Slide 8 Identification of Master Data Objects via GS1 GLN What are GLNs? GS1 (“Global Standards”) is a standardisation organisation with worldwide relevance, active in the field of electronic data exchange “Global Location Numbers” (“GLNs”) are a GS1 standard: A common identification for physical locations and legal entities Allow for Interoperability, they allow to re-identify objects that are administrated in different places - they prevent the need to assign objects from different sources to each other manually or by heuristic algorithms Are the basis for the Global Trade Item Numbers (GTINs) – known from barcodes Integrate neatly with UN/CEFACT standards  next slides Master data registry (parties, installations, …) How do GLNs get used in the Austrian EDM / PRTR? Readily assigned GLNs (GLNs previously requested from GS1) can be used as IDs for parties, facilities, installations, etc. Automatic assignment of new GLNs when registering objects: Automatically assigned GLNs are restricted for the use within the EDM

9. 2008-12-02 | Slide 9 Reference List Register Common reference list register for the various EDM apps No redundancy, any number of languages supported

10. 2008-12-02 | Slide 10 Reference List Register: Historisation Transparent changes / history Transparency on what’s valid for any given point of time Consolidated view of all entries, old & new Individual view of entries valid during a given period of time

11. 2008-12-02 | Slide 11 Reference List Register: Consolidated View of a List

12. 2008-12-02 | Slide 12 Data models: Approach to Interoperability ABCD Standard: Library of semantic components Message models assembled from library components

13. 2008-12-02 | Slide 13 Standards for Interoperability: Status Quo Worldwide Standard: Library of semantic components UN/CEFACT Core Component Library (CCL) United Nations Centre for Trade Facilitation and Electronic Business Initial publication in 2006 Since then bi-annual update (extension)

14. 2008-12-02 | Slide 14 UN/CEFACT Data Modelling Methodology Context-IndependentContext-Specific Syntax- Independent Syntax- Specific Core ComponentsBusiness Information Entities Message Format Specification (such as XML Schema Definition) Message Structure 12 3 4 12& published in Core Component Library 3 currently not published 4 published separately (XSDs, EDIFACT)

15. 2008-12-02 | Slide 15 UN/CEFACT Core Component Library Example Components UN/CEFACT Core Component Library (CCL) Basing a new message model, such as for the Environmental Sector, on the CCL: Typically many components from the CCL can be reused Typically some new components will have to be defined Example Components:

16. 2008-12-02 | Slide 16 VolumeMeasure MassMeasure Quantity Description Name TypeCode ID Goods UN/CEFACT Data Modelling Methodology How CCs and BIEs relate Two main principles: 1.„pick what you need“ (other way to see it: „discard what you do not need“) 1.„qualify“ NetMassMeasure GrossMassMeasure ID Goods MassMeasure ID Goods Core Component (CC) Business Information Entity (BIE)

17. 2008-12-02 | Slide 17 UN/CEFACT CCL Most commonly used Components NameDescription PeriodA period of time PartyA person or organisation LocationCoordinates, etc. AddressStreet name, building number, country, etc. CostMonetary amount, etc. Document CommunicationTelephone, Fax, E-Mail, Website Address, etc. OrganizationOrganisation Contact Country

18. 2008-12-02 | Slide 18 AT PRTR Summary National register / central system Reporting by facility operators Data distribution: So far to EU E-PRTR only Detail of data collected: Similar to detail of data reported, except for data taken from other reports (waste mass balance, etc.) Time frames for collecting: The same as for reporting (annual) Technical: Web Application, GUI, real time master data and reference data access encapsulated via Java API (internally using JDBC), use of data from other reports via Webservices (SOAP) Integrated into single window approach for Environmental Sector – “EDM” Interoperability an objective that has been taken much care of (data structures – UN/CEFACT, IDs - GLNs, reference lists, etc.)

19. 2008-12-02 | Slide 19 E-PRTR data flows in a Shared Environmental Information System i norbert.pfaffinger@umweltbundesamt.at Thank you! Comments and questions are welcome:

20. 2008-12-02 | Slide 20 (Online) Forms and/or Electronic data exchange interfaces 1. Domain Model 2. Harmonised Model 3. Database model Appendix Slide: Data Modelling: Process & Results Not visible to users Visible to users Main result: UML class diagram in domain terminology Main result: UML class diagram composed of reusable components Main results: Typically XML Schema plus Interface Specification Document (PDF)

21. 2008-12-02 | Slide 21