Model update handling

Follow instructions in Model update handling

Support checks (on provider's end)

• Data acquisition  method: Acquisition method is pull (via ECPDS/FTP) 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 packing: only if differs from the required  single packing
  

  ---

• 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 August 2018

• 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

*impacted by the changes related to migration to Bologna