1. 1 Operational Scheme and Schedule: Basics §Basic scheme (analysis + forecast) l Global-Modell (GME, global and synoptic-scale) l Lokal Modell (LM, highly resolved mesoscale model) §3 runs per day l 00, 12, 18 UTC l 03, 06, 09, 15, 21 UTC only analysis §Schedule determined by l data cut-off l computational resources l user priority

2. 2 Operational time schedule of DWD-models

3. 3 Boundary values and forecast range §forecast range of LM: 48h §every hour LM gets new boundary data from GME l smooth transition within 8 grid points l continous data assimilation §forecast range of GME l 00, 12 UTC: 174h l 18 UTC: 48h

4. 4 Schedule of GME/LM-runs (relative to starting time) §+2h 06minstart of GME-analysis §+2h 23 minstart of LM-analysis §+2h 30 minstart of GME-forecast §+2h 34 minstart of LM-forecast §+3h 45 min48h-LM-forecast available §+4h 30 min174h-GME-forecast available §Postprocessing- l Graphic-files: 5 min l local forecast parameters: 15 min §Availability of final products about 5 hours after starting time

5. 5 Basic postprocessing §Interpolation between model levels and pressure levels l model level (34m): Typical vertical profiles (depending on stability, e.g) T 2m wind 10m l LM-model-levels 26 and 27 for 850-hPa-level, e.g §Reduction of model surface pressure to mean sea level l base: adiabatic gradient l in the case of mountainous areas (e.g. Greenland) reduced amount of vertical temperature gradient however, often too high surface pressure values

6. 6 Postprocessing (further steps) §Automatic weather interpretation l for all fields and local products: describing model weather output of GME and LM §Generation of graphical and alphanumerical products l general analysis and forecast fields l MPEG-files (TriVis) with animations of cloud development precipication wind temperature l local model output as meteograms and local soundings l local direct model output as alphanumerical information l local output through Kalman, Model Output Statistics and Perfect Prog

7. 7 MAP: Ps/T850, GME (21-11-01, 00 UTC)+48h

8. 8 Trivis (LM, precipitation): 19.12.01, 00 +24h

9. 9 LM-(17-04-01, 00 UTC+48h):Frankfurt/Kassel/Essen

10. 10 Postprocessing (Cross Sections) §Time series of preselected cross-sections of relevant parameters l cloudiness l wind l temperature

11. 11 LM(+30h)-cross-section Frankfurt to Tarbes (4-4-02, 06)

12. 12 Postprocessing (followed-up-models) §Followed-up models (based upon GME-/LM-output) l sea state models water level (e.g. tides) waves l trajectory model pollution (e.g.) l winter road maintenance SWIS (1-D-model for road surface temperature and road condition) l agro- and biometeorological models fungus disease ultraviolett irradiation l test: 1-D-model for fog and low clouds

13. 13 SWIS-Input-Editor

14. 14 detailed road weather forecast for „Ruhrgebiet“

15. 15 Computer-system: NWP-runs, IBM §distributed memory massively parrallel processors §application units: 1920 l different model areas are related to different processors l communication between these areas is performed l COS4: 448, COS5: 1472 processor units §memory: 1240 GByte §disk capacity: 7562 GByte §peak performance of each processor unit: 2.4 GFlop/s l „beat frequency“: 375 MHz l each „beat“ : e.g. 8 floating point operations (by considering more bits)!

16. 16 Computer-system: data storage, communication (I) §2 IBM p690, each l 32 processors l 128 GB memory l 864 GB disk capacity l tasks (e.g.) developments, tests routine jobs (decoding of observations, production of graphics, etc) data handling §Storage server (e.g., test results) l 3 x 13.5 TByte

17. 17 Computer-system: data storage, communication (II) §data amount l 174h-GME-run: 40 GByte l 48h-LM-run: 5 GByte l totaly NWP-production > 120 Gbyte per day (follow-up models inclusive ) §Archive (SGI O200) l 24 processors l 24 GB memory l 853 GB disc capacity §archiving of data on cassettes (600 TByte)

18. 18 Operational computer system