Read in Recommended support checks about hopefully helpful practises used at ECMWF which can be shared. Some examples and source codes are also available there.

Support checks (on provider's end)


Centre 

Data acquisition method

Data transfer checkData delay checkData completeness checkData quality check
Data recovery option
Exists?Time limit?
1BoM (ammc)

ecpds (ftp)








2DMI (ekmi) ecpds (ftp)
YESNOYESYES
YES14 DAYS
3DWD (edzw)ecpds (https)






4ECCC (cwao)ecpds (http)NOYESNONO
YES4 DAYS
5ECMWF (ecmf)MARSN/AYESYESYES
YESNO
6FNMOC (fnmo)







7JMA (rjtd)ecpds (push)YES





8KMA (rksl)ecpds (push)






9LOPS (lops)ecpds (ftp) YESYESYESNO
YES1 DAY
10METEOAM (cnmc)ecpds (pull from ecgb)YESNOYESNO
YES3 DAY
11METNO (enmi)ecpds (push)YESYESYESNO
YES
12METFR (lfpw)ecpds (push)YESYESYESNO
YES2 YEARS
13NCEP (kwbc)ecpds (ftp)YESYESYES

YESNO
14NIWA (niwa)ecpds (sftp)






15NZMS (nzkl)ecpds (ftps)YESYESNONO
YES1 MONTH
16PdE (lemm)ecpds (push)YESYESYESYES
NO
17SHNSM (sabm) ecpds (ftp)
YESYESYESYES
YES9 DAYS
18UKMO (egrr) ecpds (push)
YESYESYESNO
NO
  • Data acquisition  method: Acquisition method is pull from the provider's location to ECMWF's premises if not specified
  • 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?
  • 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.

Support incidents

Number of operational incidents since Sep 2018 per quarters

Year201820192020202120222023
QuarterQ4Q1Q2Q3Q4sumQ1Q2Q3Q4sumQ1Q2Q3Q4sumQ1Q2Q3Q4sumQ1Q2Q3Q4sum

created

12915763791212195216181418661711211968

19

14

9

1456
updated12101810745111518256928241728972415242487

30

26

14

2494
closed8916743681011174623211219752110131155

21

20

13

1670

  • 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)