Read in Recommended support checks about practises used at ECMWF which could be of help. Some examples and source codes are also available there.

Support checks (on provider's end)

Organisation

Data acquisition method

Data transfer checkData delay check

Data completeness check

Data quality checkData recovery option
Exists?Time limit?
BoM (ammc)

sftp

YESYESYESNOYESNO
CMA (babj)

ftp







CPTEC (sbsj)http





DWD (edzw)sftp





ECCC (cwao)sftp (ssh key)YESYES



ECMWF (ecmf)MARS retrievalN/AYESYESYESYESNO
IMD (vabb)

ftp

YESYESYESNOYESNO
JMA (rjtd)http





KMA (rksl)push (dedicated line via ECPDS)YES (?)NOYESNO

Meteo-France (lfpw)ftp





UKMO (egrr)copy from ecgb





NCEP (kwbc)

ftp







NCMRWF (dems)

ftp

YESYESYESNOYESNO
  • Data acquisition  method: If not specified  the data retrieval method is pull by  ECMWF's acquisition system ECPDS from the provider's location
  • Data transfer check: Is the data transfer checked to avoid any technical issues on the way from provider's location to ECMWF's premises? Was the data delivered bit identical?
  • Data delay check: Is the potential delay of  data availability checked on the provider's side?
  • Data completeness check: Is the data content (number of expected fields; reference field list etc) checked on the provider's side?
  • Data quality check: Is there any data quality control to avoid e.g. unrealistic parameter values due to interpolation or any other kind of error either scientific or technical?
  • Not simple packing? The data should be packed using GRIB simple packing for faster processing by users (HW packing is used to archive the data)

  • Data recovery option:  Is it possible to recover any missing/corrupted data when needed?
    • If yes, is there any time limit when the data can be rescued? If yes, specify number of days within which the recovery action must happen.

Statistics

Support incidents

Number of operational incidents since May 2018

Year

2018

2019

2020

2021

2022

2023

QuarterQ2Q3Q4Q1Q2Q3Q4sumQ1Q2Q3Q4sumQ1Q2Q3Q4sumQ1Q2Q3Q4sumQ1Q2Q3Q4sum

created

318231522161670121431278415252219812322122178

11

18

10



updated31929192617218426193539119313229271192528132995

19

27

19



closed21223192414147118172128842525222294211811858

14

22

12



  • Number of updated incidents includes the newly created or closed ones
  • Updated or closed incidents may refer to those from previous quarters
  • Stats do not include  system change tickets (=non-incidents)

System changes

Number of operational system updates since 2019

Year

2019

2020

202120222023*
created/updated481332*5

*impacted by migration to Bologna

**until 9/2023