Table of Contents |
---|
Model update handling
Follow instructions in Model update handling
Support checks (on provider's end)
Info |
---|
Read in Recommended support checks about practises used at ECMWF. Some examples and source codes are also available there. |
Organization | Data acquisition method | Data transfer check | Data delay check | Data completeness check | Data quality check | Data packing | Data recovery option | |
---|---|---|---|---|---|---|---|---|
Exists? | Time limit? | |||||||
BoM (ammc) | ftp | |||||||
CMA (babj) | ftp | |||||||
CNR-ISAC (isac) | http | |||||||
CNRM (lfpw) | ecpds (push) | JPEG2000 | ||||||
ECCC (cwao) | sftp | |||||||
ECMWF (ecmf) | MARS retrieval | N/A | YES | YES | YES | YES | NO | |
HMCR (rums) | ftp | NO | YES | YES | NO | |||
JMA (rjtd) | ftp | |||||||
KMA (rksl) | ecpds (push, dedicated line) | |||||||
NCEP (kwbc) | ftp | YES | YES | YES | NO | |||
UKMO (egrr) | ecpds (push, dedicated line) | 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 August 2018
Year | 2018 | 2019 | 2020 | |||||||
---|---|---|---|---|---|---|---|---|---|---|
Quarter | Q3 | Q4 | Q1 | Q2 | Q3 | Q4 | Q1 | Q2 | Q3 | Q4 |
created | 10 | 11 | 12 | 7 | 10 | 14 | 17 | |||
updated | 10 | 14 | 21 | 8 | 12 | 17 | 22 | |||
closed | 5 | 7 | 21 | 8 | 9 | 11 | 17 |
- 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)
Show If | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
|
Table of Contents |
---|
Model update handling
fFollow instructions in Model update handling
Support checks (on provider's end)
Info |
---|
Read in Recommended support checks about practises used at ECMWF. Some examples and source codes are also available there. |
Organization | Data acquisition method | Data transfer check | Data delay check | Data completeness check | Data quality check | Data recovery option | ||
---|---|---|---|---|---|---|---|---|
Exists? | Time limit? | |||||||
BoM (ammc) | ftp | |||||||
CMA (babj) | ftp | |||||||
CNR-ISAC (isac) | http | |||||||
CNRM (lfpw) | ecpds (push) | |||||||
ECCC (cwao) | sftp | |||||||
ECMWF (ecmf) | MARS retrieval | N/A | YES | YES | YES | YES | NO | |
HMCR (rums) | ftp | NO | YES | YES | NO | |||
JMA (rjtd) | ftp | |||||||
KMA (rksl) | ecpds (push, dedicated line) | |||||||
NCEP (kwbc) | ftp | YES | YES | YES | NO | |||
UKMO (egrr) | ecpds (push, dedicated line) | 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 August 2018
Year | 2018 | 2019 | 2020 | |||||||
---|---|---|---|---|---|---|---|---|---|---|
Quarter | Q3 | Q4 | Q1 | Q2 | Q3 | Q4 | Q1 | Q2 | Q3 | Q4 |
created | 10 | 11 | 12 | 7 | 10 | 14 | ||||
updated | 10 | 14 | 21 | 8 | 12 | 17 | ||||
closed | 5 | 7 | 21 | 8 | 9 | 11 |
- Number of updated incidents includes the newly created or closed ones
- Updated or closed incidents may refer to those from previous quarters
Show If | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
|