Improve quality of ICDs for System-CDR

To finalise by Adoption design review date:

SDP-TM:

I’ve looked at the OARs from the SDP CDR and Pre-CDR and here is a list of the items that need work post SDP CDR close-out:

• for System CDR:
  • Telescope State data items that are exchanged between SDP, TM and other elements, see SDPCDR-250 & SDPPRECDR-379
    • This also includes calibration tables (gain tables) and jones matrices produced by SDP , see SDPPRECDR-210
  • The Telescope configuration (TelMod) data items exchanged between SDP and the Configuration Repository in TM need to be defined and agreed at system level and the mechanism of this part of the interface needs to be clarified. The most important items here are calibration model updates, see SDPPRECDR-400.
  • How TM uses the SDP Resource Model module (library) needs to be discussed and documented. (SDPPRECDR-353)
  • How dependencies between scheduling blocks is going to be dealt with is still not clear and this impacts the scheduling and SBi configuration interface with SDP (SDPPRECDR-388).
  • A conceptual or logical data model for scheduling block configuration is needed. (SDPPRECDR-377 & SDPPRECDR-379).
• post system CDR (during bridging):
  • A minimal set of QA parameters that the system needs from SDP needs to be defined. This is low risk and quite a bit of work has already been done in this area from SDP, but system level input is needed in particular around commissioning. (SDPPRECDR-407)
  • Tango data types may place limitations on QA data produced by SDP, this needs to be discussed and resolved. This is not expected to be an issue, but the OAR is still open, see SDPPRECDR-391.

SDP-LFAA:

• Details of the protocols for I.S1L.SDP_LFAA.001 (GSM interface) have not been developed yet, though SDP is expecting to use standard protocols. Definitions of OSI layers 3-6 are TBD or TBC.
• The data needed from the GSM by LFAA is still TBD. Requirements such as latency, cadence, volumes etc. are also TBD. These details need to wait until the calibration strategy for LFAA is determined.
• For I.S1L.SDP_LFAA.002 (transient buffer interface) there are concerns about using FTP. These need to be resolved and a protocol decided on.
• It should be considered whether I.S1L.SDP_LFAA.002 should also include antenna level data.
• For I.S1L.SDP_LFAA.002 there is a problem that SDP does not have enough storage capacity for the volume of data coming from LFAA. This needs to be resolved, and the outcome included in the ICD.

CSP-TM relates to SP-111 and SP-110. Also See CSP assumption:

VLBI-TM:

for LOW is missing

INFRA-TM:

General presentation:

https://docs.google.com/presentation/d/1ZBx7lltDLKWD-D6qvuSnf5930NU14E7Je5qkLlvUhXU/edit#slide=id.gc6f73a04f_0_0

INFRA-SA: https://drive.google.com/drive/folders/1PKlgNkE62exv0To1HsgkTNcvQjsW61-C

INFRA-AU:https://drive.google.com/drive/folders/127yAPsxYxW-sQrMTPa-Abe5c8Z-3WkY1

SADT-TM

DSH - TM

the level of maturity is variable.