MACC User Interface Achievements

1. MACC / MACC-II User InterfaceThomas Holzer-Popp and the O-INT / INT partnersDLR-DFDthomas.holzer-popp@dlr.de

2. MACCUser InterfaceAchievements

3. MACC User Interface Achievements • two cycles documenting requirements • downstream services, end users • reviewed by users, response from MACC services on implementation • active user involvement • User Advisory Board, user sessions, user questionnaire on MACC web • Service Level Agreement templates • 18 agreements • each MACC service line has at least one active user collaboration • test cases set up and run • using output from R-ENS, EMIS, D-SAT, G-AER • Assess down-scaling in Mediterranean and to city level • demonstrate health applications • test case report • valuable show cases, feedback for service improvement

4. User interaction in MACC (1) User requirements feeding into service specifications • Objective: understand user needs and prepare for specifiations • Preparation + online distribution of user questionaire – 2 revisions • Collect requirements from downstream services and end users • Analysis of questionnaires and open user sessions • Iteration with users • Contribute to Service Portfolio Specifications • Integrate user requirements per service line + assure tracability • Short service specifications as part of SLAs • Analysis of implementation status / comments • Requirements not fully comprehensive / build on IG analysis

5. User requirements + feedback • Categories • Technical (30) • Parameters, resolution, delivery time • Coverage (Iceland, most of Turkey: not Russian Federation) • Format, quicklooks, documentation, updates • Validation, uncertainty • Meteorological forecasts (restricted) • Data policy (3) • Data access conditions manual on web (in completion) • Contact per service (in preparation, through SLAs) • Data access (7) • ftp, fast / dynamic access, hotline • Feedback on implementation for each requirement (v2)

6. User interaction in MACC (2) Overall user interaction • Objective: assure project level active user involvement • User Advisory Board (UAB) • Supported by loose local / urban group • Two open meetings at assemblies • Dedicated user sessions during MACC assemblies • Present user needs to service providers in plenary • Inform users on services in MACC • Reports on user meetings and UAB

7. UAB feedback • Overall statements • MACC provides highly promising integrated model based results • Use of MACC products require scientific expertise • Regional / downstream concept needs clarification • Communication needs improvements to achieve wider acceptance • Policy support needs faster response, longer time series, finer scales • MACC needs to work in operational way • Policy requirements need further refinement -> EIONET • Blockage by limited resources for using MACC output -> FAIRMODE • Specific recommendations • Add uncertainties (emissions) • Use EUMETCAST for faster NRT dissemination

8. User interaction in MACC (3) Service Level Agreements • Objective: define bi-lateral provider – user twins for service evaluation • Approach for agreements • SLA templates, other agreements (MoU, LoA) where appropriate • Start with PROMOTE follow-up then, extend to all services • Status of bi-lateral agreements • 9 signed, 3 other agreements, 6 agreements in preparation • 1 transfered to PASODOBLE • User presentations / feedback during MACC conference sessions • PASODOBLE prepared feedback note for use of R-ENS

9. SLA content • Partners • Named provider(s) and user • Signed on director level • Technical contact persons to conduct work • Major principles • Specific MACC service(s) and user application • Provider commitment to provide data and respond to user feedback • User commitment to use and provide feedback on them • Short product specification (parameters, period, format, …) • Minimal legal terms (no exchange of funds, liability/warranty) • Template may be adopted specifically for each SLA or other agreement

10. Agreements - status

11. Agreements per service line

12. PASODOBLE 1st feedback note • First issue focused on using R-ENS as boundary conditions for nesting • Use of MACC R-ENS as boundary conditions implemented succesfully • Technical evaluation • R-ENS dataset availability has significantly improved • For all user requirements larger R-ENS area and forecast period needed • Above 4km G-RG can be used as boundary conditions • Limited experiments to assess need for additional variables in R-ENS • Depends on chemical scheme, region, season • Highest benefit shown if adding O2, Na (coarse and fine), part. SO4, ethene, PAN, HNO3, isoprene • Benefit expected with more vertical levels / not shown yet • PASODOBLE develops OGC interface for access to MACC products • will be continued in MACC-II from M18

13. MACC users (1) • Downstream services linking to finer scales / specific use • No SLA, but exchange of letters / joint meeting, joint staff • PASODOBLE: air quality • ENDORSE: renewable energies • EEA / EIONET / national environmental agencies • Collaboration, meetings • Dedicated POLICY sub project • European users • EMEP, (DG-ENV) • Regional environmental agencies • Issues of scale and understanding „core/downstream“ concept

14. MACC users (2) • Commercial users • ObsAIRve as test case (SLA in preparation) • Solar energy: GeoModel • International science users • CAMS, GURME, AMQEII, WMO, SPARC • National wheather services • Users registered at MACC web portal • ~500 from 44 countries (23 non EU) • (were ~50-100 at MACC start)

15. MACC test cases • Inter-core processing chain test cases • 3 parts of Mediterranean basin • Assess specifics in each environmental regime for R-ENS • Core-downstream test cases • Nesting R-ENS to city level • Post-processing of D-SAT + R-ENS PM2.5 data • Health test cases • Meningitis-dust / Sahel – WMO-SDS using G-AER and D-SAT • COPD forecasts for patients with R-ENS NO2 • Health warnings and GIS exposure assessments with R-ENS

16. Conclusions / downscaling (1) • Mediterranean regions NO2, SO2, O3, PM10 – ~ 5 km) • Catalonia • Po-valley • Greece • Findings • Mediterranean needs specific care • MACC R-ENS driven regional models show finer detail • Several over-estimations of O3 peaks (local emissions or circulation?) • R-ENS as boundary conditions shows improved scoring (few stations) • More species / levels expected to improve scoring • Sensitivity tests (switch off VOCs, PM10, NH3) decrease PM10, O3 • Separate tests are needed per variable • Need for 2 forecasts per day

17. Example nested O3 overestimation

18. Conclusions / downscaling (2) • City forecasts • Denmark NOx, O3 street level • Romania CO, SO2, NO2 0.02 deg) • Findings • interim 1 downscaling step needed from MACC R-ENS • forecasts work generally well as with individual models used so far • However, few cases of complete failure occured (specific chemistry?) • Thus more species, levels are needed – but not yet specified which • 2007 MACC /TNO emissions improve NO2 forecast

19. Conclusions / health • PM10 (daily mean) is most relevant • MACC ensemble product is capable to show episodes but with under-estimated peaks and some time lag • Model uncertainties are regarded less important than other confounding factors • Use of MACC ensemble product for health applications requires adjustment for higher resolution • Underlying correlation statistics on regions • Additional local modelling added on MACC background • Urbanization correction factors from in-situ/model analysis • With such adjustment use of MACC for epidemiological applications was shown (forecasting, warning, exposure estimation / time activity) • Sahel MACC dust forecasts useful for analysis of environmental factors leading to outbreaks of meningococis and possibly for seasonal prediction

20. Example: PM10 urban exposure

21. Met Office forecaster Met Office Forecaster National Health Service Network Health Forecasts Call logs Medixine administrator Monitoring Patient name and tel no , changes to Medixine software patient status on NHS Server Doctor practice Patient Telephone numbers responses Automated telephone call Patient responses interactive voice response system Person with COPD Example: COPD warning for Exeter

22. MACC User Interface Conclusions • Understanding + meeting user requirements needs • Patience, dedication, an iterative process • Dedicated pilot users / twinning pairs • Pilot users / show cases need initial co-funding • Increasing uptake by users depends on • Long-term sustainability of services • Clear communication of services (ensemble – uncertainty) • Clear conditions for services (commercial, meteorological forecasts) • Moving from research project to operational framework • Users need • Products with high and documented quality • Easy access to data and documentation

23. Some MACC use examples SolarGIS solar radiation database missing extreme values

24. MACC-IIUser InterfacePlans

25. User Interface transition to MACC-II • Continue coordination of user interaction • User requirements, project user interaction • Service Level Agreements continuing from MACC + additional SLAs • Core service evaluation (external user feedback) • Support service specifications • Discontinue test cases • Link some of them as external users via SLAs • Show cases must come from external users • Strengthen user interaction • Add focus on communiation, training • more comprehensive and systematic approach to user interaction • Adding technical user interface

26. MACC II services with their data interfaces metadata specifications responses responses direct access INT_1 User requirements INT_2 Metadata Web services INT_3 Project communications INT_4 Project training specifications enquiries enquiries enquiries requirements web services MACC II users INT structure

27. INT_1 User interaction • Coordinate interaction with users (2 cycles) • Aiming at growing user base • Aiming at more comprehensive coverage of main user communities • 1.1 user requirements • integrate feedback to helpdesk • Increased emphasis on data access needs • 1.2 Active user dialogue • User workshops, User Advisory Board • User feedback summary reports / show case documentation • 1.3 Service Level Agreements / similar arrangements • Assess possibilities for simplifying signature process • 1.4 Support translating user requirements into service specifications • Structure user requirements and assure traceability

28. INT_2 Technical user interface • Assure best product availability in support of a growing user base • Harmonized metadata • harmonized definition, creation, catalogue (harvesting) • INSPIRE/WIS compatible data search • 2.1 Global metadata interface • 2.2 European metadata interface • Web services for inter-operable access • Cooperation with service sub projects (responsible for data services) • Allow distributed nodes for data access • Allow different access modes • from M18 / building on PASODOBLE „interface to core products“

29. INT_3 Project communication • Coordinate project communications • 3.1 review / improve communication channels • 3.2 Coordinate web portal • Add new catalogue to web portal • Harmonize structure • Directly link, documentation, validation and use case information • 3.3 user querries • Helpdesk integrating distributed user contacts • FAQ pages • Querries summary report, assure response to user needs • 3.4 external representation • Project communication officer • Press releases, newsletter • Communication strategy

30. INT_4 Training • Provide user focused training • 4.1 Training sessions • Only at clear demand • Annual training report • 4.2 eTraining material • For capacity building / training users • Content provided by all sub projects • Summer school • „Atmospheric chemistry monitoring and forecasting“ • End of June 2013 • Lectures on background of scientific MACC • Student work with MACC products • Aim to attract student but also professional participants

31. Thanks to all User Interface partners … responsible for overall user interaction: CERC, EAA, DLR … responsible for test cases - leaving at end of MACC: MFR, AEMET, ARPA-ER, ISAC-CNR, AUTH, DMI, NMA, CGS CHMI, UWS, ICSTM, UKMO … for new tasks (ECMWF, UPMC, FZJ) Thanks to all MACC sub projects for close collaboration!