Medspiration – System Requirements Document - Data User Element

Medspiration
System Requirements Document
MED-SOC-RS-001_1
Issue F
5. PERFORMANCE REQUIREMENTS
5.1 Scenario Definitions
SR.PER.SYS.0010/A The L2P data files shall ideally be delivered within 6 hours after
acquisition. It is recognised this may be not possible depending on the L2 data providers
on which the Medspiration system has no control and thus it is just an ideal target.
SR.PER.SYS.0011/I
L2P must be produced in near real time.
SR.PER.SYS.0015/I A cutoff time (Ω) must be specified after which L2P data are no
longer eligible for inclusion within the analysis. This must take account the time taken to
process L2P data (∆Time L2P ), the time required to perform the analysis (∆T analysis ) itself
and the Maximum desirable output time delay (T output ) using:
Ω =
(Eqn. 2.3.1)
Toutput
− ∆Tanalysis
− ∆TL2P
For example: if T output = 12:00 at T+1, ∆T analysis =4h and, ∆T L2P =2h then Ω= 06:00 at T+1.
This means that L2P SST data for day T can be accepted until day T+1 at 06:00 UTC.
Comment: After this cutoff time data concerning the analysis at day T will be considered
as too late and a message error will be sent.
SR.PER.SYS.0020/A The UHR/L4 data files shall be provided within 12 hours after the
end of the processing window, that is to say before T0 + 36h when processing the (T0 ->
T0 + 24h) UHR/L4 product.
SR.PER.SYS.0030/A The L2P MMR_FR metadata records shall be provided to MMR
within 60 minutes after L2P production.
SR.PER.SYS.0040/A The MDB records shall be delivered within 24 hours after they
are delivered by the in situ data center.
SR.PER.SYS.0050/A The L2P MMR_FR rejected by the MMR shall be less than 2%.
SR.PER.SYS.0060/I
instant
The MMR_DSD describe the availability of data files at any given
SR.PER.SYS.0070/I A too long delay between two data files availability of a same data
© 2004 SOC Page 69 of 193