System Requirement Document (SRD) - H-SAF

More documents

Recommendations

Info

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 26/102In this architecture, as detailed in the System Design Document, five main subsystemshave been identified:1. Precipitation Subsystem: in charge of acquiring and pre-processing input data,generating Precipitation (Observation and Assimilation) products, performingquality control processes and activities and disseminating products to end users;2. Soil Moisture Subsystem, in charge of acquiring and pre-processing inputdata, generating Soil Moisture (Observation and Assimilation) products,performing quality control processes and activities and disseminating productsto end users;3. Snow Parameter Subsystem, in charge of acquiring and pre-processing inputdata, generating Snow Parameters (flat/forested, mountainous and merged)products, performing quality control activities and disseminating products to endusers;4. Hydro Validation Subsystem, in charge of providing independent assessmentof the usefulness of H-SAF products in operational hydrology and watermanagement, performing near-real-time acquisition of all products and carryingout hydrological validation activities using available tools and consolidatedmethods and models. It also provides valuable output for cal/val and validationreports used by production subsystems for possible products qualityimprovements;5. Offline Monitoring Subsystem, in charge of acquiring products and validationreports from the other subsystems, storing them in a central online/offlinearchive, disseminating the archived data in OFL to scientific users via U-MARFinterface and performing a monitoring on dissemination results.2.5 General ConstraintsThe availability of envisaged satellite data (current and planned) is a constraint both for thedevelopment and for the operational phase of H-SAF. For this reason it is relevant todepict some details about the situation at the time being (i.e. to be used pre-operationallyand experimentally in development phase). The following table summarises this situationand states, for each data sources, which of the specified access means is the oneconsiderd baseline:Data SourceInterface
H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 27/102Data Source Description Baseline for operationsSEVIRI Meteosat 8LRITNRT via EUMETCastBackupBaselineAMSU-ANOAADirect read-outNRT via EUMETCastBaselineBackupAMSU-B NOAA 17SSM/I DMSP 15SSMIS DMSP 16Direct read-outNRT via EUMETCastNRT via EUMETCastFTP from UKMONRT via EUMETCastFTP from UKMOBaselineBackupBaseline if implementedCurrent baselineBaseline if implementedCurrent baselineMHSMetOpDirect read-outNRT via EUMETCastBaseline if implementedCurrent baselineAMSU-AMetOpDirect read-outNRT via EUMETCastBaseline if implementedCurrent baselineNWP ECMWF Dedicated linkSynopticObservationAuxiliary/AncillaryDataWMO-GOS(various)GTSOFLMHS NOAA 18MVIRI (2) Meteosat 7Direct read-outNRT via EUMETCastU-MARFBaselineBackupAMSR-E (forprecipitation)EOS-AquaFTPATMS (1) NPP NRT via EUMETCast If implementedLIS (1) TRMM FTP and other NASA
Page 1: H-SAFSystem Requirement DocumentDoc
Page 4 and 5: H-SAFSystem Requirement DocumentDoc
Page 10 and 11: H-SAFLIST OF TABLESSystem Requireme
Page 28 and 29: H -SAFSystem Requirement DocumentDo
Page 76 and 77:
H -SAFSystem Requirement DocumentDo
Page 78 and 79:
Page 80 and 81:
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
Page 100 and 101:
Page 102:
show all

System Requirement Document (SRD) - H-SAF

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?