Medspiration â System Requirements Document - Data User Element

More documents

Recommendations

Info

Medspiration MED-SOC-RS-001_1 System Requirements Document Issue F SR.INT.CTR.0030/I Remote systems (SOC, CMS) shall deliver to the controller the relevant error and operation messages to be centralized in the operation log system. The messages shall be transmitted through ftp. The IFREMER system controller will not have any direct control on remote systems (at SOC or CMS).The only interaction is through the operation and error messages. SR.INT.CTR.0040/I The controller shall deliver to the Medspiration remote systems the error and operation messages related to the dataflow control (retransmission request, acknowledgement). The messages shall be transmitted through ftp. SR.INT.CTR.0050/I Error and operation messages shall be formatted as specified in annex 4 (“Operation and error messages”). SR.INT.CTR.0060/I All systems under IFREMER control shall be able to return to the controller a return status after they have completed their task. 4.2 External 4.2.1 Satellite data providers SR.EXT.ING.0010/I The ingestion module shall query the provider to check the availability of data files from provider according to Table 5-1, Table 5-2 and Table 5-3 SR.EXT.ING.0020/I The ingestion module shall download the available data files from data provider according to the protocol defined in Table 5-1, Table 5-2 and Table 5-3 SR.EXT.ING.0030/I Error message generated by the ingestion module shall be sent to the data provider and the system controller. SR.EXT.ING.0040/I The configuration files (see SR.QLC.0020 and SR.CFD.0370) will be received from GHRSST-PP by email (see SR.CFI.L2P.0010). They will be replaced manually after a coherency check. Comment: Configuration file format is still to be defined. SR.EXT.L2P.0010/I SSES will be provided by the GHRSST (see SR.CFI.L2P.0020) They will include a couple of error statistics (bias and standard deviation) per source and per confidence level value. Comment: The missing value to be used during the initiation phase remain to be defined. © 2004 SOC Page 64 of 193
Medspiration MED-SOC-RS-001_1 System Requirements Document Issue F SR.EXT.SYS.00xx/I The MMR_DSD records shall be sent by email to the GHRSST- PO. SR.EXT.SYS.00xx/I appendix A6 The format of the MMR_DSD record is described in GDS 4.2.2 In situ data provider SR.EXT.MDB.0010/I The MDB records production system shall be interfaced with the CORIOLIS data centre to access the in-situ data. In the frame of MEDSPIRATION, the CORIOLIS data centre will be considered as the only source of in-situ data. However, CORIOLIS is a gateway to GTS data and MEDS data. SR.EXT.MDB.0020/I The in situ data shall be delivered daily by CORIOLIS in netCDF format. This format will be defined in close collaboration with the CORIOLIS team. SR.EXT.MDB.0030/I The data files shall be directly readable through the IFREMER local network (no transmission) since the CORIOLIS data centre is hosted by IFREMER. 4.2.3 GDAC SR.EXT.CTR.0210/I The L2P products shall be delivered to GDAC by ftp push as soon as they have been ingested in the archiving system. The UHR/L4 products shall not be delivered to GDAC since they are regarded as a purely Medspiration product in the SoW. SR.EXT.CTR.0220/I The L2P products shall be delivered to GDAC by IFREMER with respect to the protocol requirements defined for the dataflow control subsystem of the system controller (refer to section 1.4.1). SR.EXT.CTR.0230/I The L2P products shall be formatted as described in annex 1. 4.2.4 GDAC MDB SR.EXT.CTR.0310/I The Medspiration system shall be interfaced with the the GHRSST- © 2004 SOC Page 65 of 193
Page 1 and 2:
Medspiration System Requirements Do
Page 3 and 4:
Page 5 and 6:
Medspiration MED-SOC-RS-001_1 Syste
Page 7 and 8:
Page 9 and 10:
Page 11 and 12:
Page 13 and 14: Medspiration System Requirements Do
Page 15 and 16: Medspiration MED-SOC-RS-001_1 Syste
Page 63: Medspiration System Requirements Do
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Page 193:
show all

Medspiration â System Requirements Document - Data User Element

Create successful ePaper yourself

Delete template?

Save as template?

Medspiration â System Requirements Document - Data User Element