View Source

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 check	Data delay check	Data completeness check	Data quality check	Data recovery option
	Centre	Data acquisition method	Data transfer check	Data delay check	Data completeness check	Data quality check	Exists?	Time limit?
1	BoM (ammc)	ecpds (ftp)
2	DMI (ekmi)	ecpds (ftp)
3	DWD (edzw)	ecpds (https)
4	ECCC (cwao)	ecpds (http)
5	ECMWF (ecmf)	MARS	N/A	YES	YES	YES	YES	NO
6	FNMOC (fnmo)
7	JMA (rjtd)	ecpds (push)	YES
8	KMA (rksl)	ecpds (push)
9	LOPS (lops)	ecpds (ftp)	YES	YES	YES	NO	YES	1DAY
10	METEOAM (cnmc)	ecpds (pull from ecgb)
11	METNO (enmi)	ecpds (push)					YES
12	METFR (lfpw)	ecpds (push)
13	NCEP (kwbc)	ecpds (ftp)	YES	YES	YES		YES	NO
14	NIWA (niwa)	ecpds (sftp)
15	NZMS (nzkl)	ecpds (ftps)	YES	YES	NO	NO	YES	NO
16	PRTOS (lemm)	ecpds (push)	YES	YES	YES	YES
17	SHNSM (sabm)	ecpds (ftp)					NO
18	UKMO (egrr)	ecpds (push)	YES	YES	YES	NO	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

Year	2018	2019				2020
Quarter	Q4	Q1	Q2	Q3	Q4	Q1	Q2	Q3	Q4
created	12	9	15	7	6	9	12	12
updated	12	10	18	10	7	11	15	18
closed	8	9	16	7	4	8	10	11

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)

The below incident list is restricted to user group "ecmwf" only.