PDR.04 Interface Requirements. Context... SE. Revision: 01. Author. F. Graser, B. Opperman. Document Classification.. Unrestricted Status..

Transcription

1 PDR.04 Interface Requirements Document number SKA-TEL-SDP Context.... SE Revision 01 Author. F. Graser, B. Opperman Release Date Document Classification.. Status.. Draft Name Ferdl Graser Signature & Date: Designation Affiliation SDP Systems Engineer Signature: SKA-Science Data Processor Ferdl Graser Ferdl Graser (Feb 9, 2015) Release Date: Page 1 of 40

2 Name Designation Affiliation Paul Alexander SDP Lead University of Cambridge Signature & Date: Signature: Paul Alexander Paul Alexander (Feb 9, 2015) Version Date of Issue Prepared by Comments 0.1 ORGANISATION DETAILS Name Science Data Processor Consortium Release Date: Page 2 of 40

3 Table of Contents Table of Contents... Error! Bookmark not defined. List of Figures... 4 List of Tables... 4 Introduction... 5 References... 6 Applicable Documents... 6 Reference Documents Interface Register External Interfaces Internal Interfaces Interface Requirements External Interfaces...13 Release Date: Page 3 of 40

4 List of Figures Figure 1. Diagram illustrating the context of SDP with regard to other Elements (subsystems) Figure 2: Diagram illustrating L4 Internal faces of Top Level SDP components List of Tables Table 1. External SDP interfaces Table 2. SDP L4 internal interfaces Release Date: Page 4 of 40

5 Introduction In Systems Engineering an interface can be identified as any point where a system and something, or someone, meet. The interface point may include other systems, internal hardware, circuitry, external peripherals, networks, system users, etc. These interfaces are described in an Interface Document (ICD) which defines and controls the interfaces of the system and thereby bound its requirements. In the context of the SKA1 s Science Data Processor (SDP) this ICD describes all possible and potential external and internal inputs and outputs to and from the SDP and (other) relevant subsystems and elements. The external Level 3 (L3) interfaces between SDP and other subsystems, i.e., SaDT, CSP, TM, INFRA, are illustrated in Figure 1. This ICD also describes the internal SDP Level 4 (L4) interfaces between the Hardware, Software, Data Layer, Data Delivery, Monitor and, Pipeline elements (Figure 2) which comprise the SDP. These interfaces are described in more detail in the following paragraphs. Release Date: Page 5 of 40

6 References Applicable Documents The following documents are applicable to the extent stated herein. In the event of conflict between the contents of the applicable documents and this document, the applicable documents shall take precedence. Reference Number AD[01] AD[02] AD[03] AD[04] AD[05] Reference SKA-TEL.SDP.SE-TEL.CSP.SE-ICD-001 SKA-TEL.SDP.SE-TEL.TM.SE-ICD-001 SKA-TEL.SDP.SE-TEL.INFRA.SE-ICD-001 SKA-TEL.SDP.SE-TEL.INFRA.SE-ICD-001 SKA-TEL.SADT.SE-TEL.SDP.SE-ICD-001 Reference Documents The following documents are referenced in this document. In the event of conflict between the contents of the referenced documents and this document, this document shall take precedence. There are no reference documents for this document. Release Date: Page 6 of 40

7 1 Interface Register 1.1 External Interfaces The SDP s L3 external interfaces are summarised in Figure 1 and detailed in Table 1. These interfaces are owned by SKAO. Figure 1. Diagram illustrating the context of SDP with regard to other Elements (sub-systems). Release Date: Page 7 of 40

8 Table 1. External SDP interfaces. Connection I.S1L.SDP_CSP.001 SKA1-Low SDP_CSP Visibility Data Interface I.S1M.SDP_CSP.002 SKA1-Mid SDP_CSP Pulsar Search Data Interface I.S1M.SDP_CSP.003 SKA1-Mid SDP_CSP Pulsar Timing Data Interface I.S1S.SDP_CSP.001 SKA1-Survey SDP_CSP Visibility Data Interface connects to CSP Central Signal Processor CSP Central Signal Processor CSP Central Signal Processor CSP Central Signal Processor I.S1L.SDP_INFRA-AUS.001 SKA1- Low SDP_INFRA-AUS Local Infrastructure Interface I.S1S.SDP_INFRA-AUS.001 SKA1- Survey SDP_INFRA-AUS Local Infrastructure Interface LINFA-AUS Local Infrastructure Australia LINFA-AUS Local Infrastructure Australia I.S1S.SDP_INFRA-SA.001 SKA1-Mid SDP_INFRA-SA Local Infrastructure Interface LINFA-SA Local Infrastructure South Africa I.S1L.SADT_SDP.001.VIS CSP- SDP_VIS to SDP_SKA1_LOW I.S1L.SADT_SDP.004 SDP to SADT.To_External_SKA1_LOW I.S1L.SADT_SDP.010 TM_NETWORK to SDP_SKA1_LOW I.S1M.SADT_SDP.003.PSS (CSP- SDP_PSS to SDP_SKA1_MID) Pulsar Survey Search I.S1M.SADT_SDP.003.PST (CSP- SDP_PST to SDP_SKA1_MID ) Pulsar timing I.S1M.SADT_SDP.003.VIS CSP- SaDT Signal and Data Transport SaDT Signal and Data Transport SaDT Signal and Data Transport SaDT Signal and Data Transport SaDT Signal and Data Transport Release Date: Page 8 of 40

9 SDP_VIS to SDP_SKA1_MID I.S1M.SADT_SDP.009 SAT to SDP_SKA1_MID I.S1M.SADT_SDP.012 TM_NETWORK to SDP_SKA1_MID I.S1S.SADT_S5 SDP to SADT to _External_SKA1_SURVEY I.S1S.SADT_SDP.002.VIS CSP- SDP_VIS to SDP_SKA1_SURVEY I.S1S.SADT_SDP.011 TM_NETWORK to SDP_SKA1_SURVEY SaDT Signal and Data Transport SaDT Signal and Data Transport SaDT Signal and Data Transport SaDT Signal and Data Transport SaDT Signal and Data Transport SaDT Signal and Data Transport I.S1L.SDP_TM.001 SKA1-Low SDP_TM and Monitoring Interface I.S1L.SDP_TM.002 SKA1-Low SDP_TM Telescope State Information Interface I.S1M.SDP_TM.002 SKA1-Mid SDP_TM Telescope State Information Interface I.S1S.SDP_TM.001 SKA1-Survey SDP_TM and Monitoring Interface I.S1S.SDP_TM.002 SKA1-Survey SDP_TM Telescope State Information Interface TM Telescope Manager TM Telescope Manager TM Telescope Manager TM Telescope Manager TM Telescope Manager Release Date: Page 9 of 40

10 1.2 Internal Interfaces All the SDP L4 internal interfaces are summarised in Figure 2 and detailed in Table 2. These interfaces are owned by SDP. Figure 2: Diagram illustrating L4 Internal faces of Top Level SDP components. Release Date: Page 10 of 40

11 Table 2. SDP L4 internal interfaces. Connection SDP.C1_C2.001 OS to hardware SDP.C1_C2.002 Hardware sensors SDP.C1_C2.003 Out of Band Management to OS. (indirect support to LMC) SDP.C2_C3.001 Container interface (OS packages required etc...) connects to C.1 Hardware Compute Platform C.2 Software Compute Platform C.1 Hardware Compute Platform C.2 Software Compute Platform C.1 Hardware Compute Platform C.2 Software Compute Platform C.2 Software Compute Platform C.3 Data Layer SDP.C2_C3.002 Storage Interface SDP.C2_C3.003 Middleware interface (messaging, notifications, etc...) C.2 Software Compute Platform C.3 Data Layer C.2 Software Compute Platform C.3 Data Layer SDP.C3_C4.001 Additional services provided by Pipeline wrapper supplied by Data Layer (essentially through Data Objects like visibilities, weights, flags etc.). SDP.C3_C4.002 Interface at the level of a Data Object. C.3 Data Layer C.4 Pipeline Components C.3 Data Layer C.4 Pipeline Components SDP.C3_C5.001 Interface at the level of a Data Product (collection of DOs) SDP.C3_C5.002 Make replication request on DP SDP.C3_C5.003 Meta information on DP (locality, size, creation date, owner, SB, etc...) SDP.C3_C5.004 Notification on availability of new DP SDP.C3_C5.005 Open question on resource availability (does it come from LMC / Data Layer) C.3 Data Layer C.5 Data Delivery Platform C.3 Data Layer C.5 Data Delivery Platform C.3 Data Layer C.5 Data Delivery Platform C.3 Data Layer C.5 Data Delivery Platform C.3 Data Layer C.5 Data Delivery Platform Release Date: Page 11 of 40

12 SDP.C3_C5.006 Replicate catalogue to DDL C.3 Data Layer C.5 Data Delivery Platform SDP.C6_C1.001 LMC hardware control C.1 Hardware Compute Platform C.6 Local Monitoring and SDP.C6_C2.001 Out of Band Management to LMC SDP.C6_C2.002 Monitor OS to LMC SDP.C6_C2.003 OS to LMC C.2 Software Compute Platform C.6 Local Monitoring and C.2 Software Compute Platform C.6 Local Monitoring and C.2 Software Compute Platform C.6 Local Monitoring and SDP.C6_C3.001 Monitor metrics, power etc to LMC SDP.C6_C3.002 metrics, power etc to LMC SDP.C6_C3.003 Data Flow Manager to Data Layer Interface C.3 Data Layer C.6 Local Monitoring and C.3 Data Layer C.6 Local Monitoring and C.3 Data Layer C.6 Local Monitoring and SDP.C6_C4.001 Pipeline metrics to LMC SDP.C6_C4.002 Pipeline to Local Telescope Model interfacepl open question C.4 Pipeline Components C.6 Local Monitoring and C.4 Pipeline Components C.6 Local Monitoring and SDP.C6_C5.001 General specification of LMC guidelines - monitoring, power control etc.. SDP.C6_C5.002 Single document with specialisation where appropriate (e.g. DFM to DL and Pipeline metrics) SDP.C6_C5.003 Authentication Interface (to be finalised) C.5 Data Delivery Platform C.6 Local Monitoring and C.5 Data Delivery Platform C.6 Local Monitoring and C.5 Data Delivery Platform C.6 Local Monitoring and Release Date: Page 12 of 40

13 2 Interface Requirements 2.1 External Interfaces SDP Interface requirements and associated Verification methods are presented in Table 3. Note that verification methods for interface requirements from the SaDT element are not shown here as the requirements are led by SaDT and are not available to SDP at this time. Table 3. SDP interface requirements and verification methods. Requirement Description verified by SDP_REQ_INT-1 Interface Management Selfdescription- SDP SKA1 Low Survey Mid. Monitor and SDP_REQ_INT-2 Interface Management Structure of Reporting- SDP SKA1 Low Survey Mid. Monitor and SDP_REQ_INT-3 Interface Management Configure interface- SDP SKA1 Low Survey Mid. Monitor and SDP_REQ_INT-4 Interface Management Alarm and event filtering- SDP SKA1 Low Survey Mid. Monitor and SDP_REQ_INT-5 Configure SDP parameters- SDP SKA1 Low Survey Mid. Monitor and SDP_REQ_INT-6 Safety Locally failsafe- SDP SKA1 Low Survey Mid. Monitor and The SDP shall provide a self-description on request from the TM. Through selfdescription the SDP provides information that describes the content of the interface, including a set of valid commands, parameters, monitoring points, alarms and events. SDP shall report information in a hierarchical structure, including a product breakdown structure and a capability structure. The TM shall be able to request the SDP to configure the level of reporting of monitoring points, alarms, events and logs. The SDP shall filter alarms and events to prevent the reporting of alarms for items that are not fitted or that are under maintenance. The TM shall configure the SDP parameters as required for the observation. The SDP shall be designed to be locally failsafe and not be dependent on any external inputs from TM for safety. Release Date: Page 13 of 40

14 SDP_REQ_INT-7 Monitoring. Report external state model- SDP SKA1 Low Survey Mid. Monitor and SDP_REQ_INT-8 Monitoring.. Report internal states- SDP SKA1 Low Survey Mid. Monitor and SDP_REQ_INT-9 Monitoring. Report alarms- SDP SKA1 Low Survey Mid. Monitor and SDP_REQ_INT-10 Monitoring. Report specific alarm information- SDP SKA1 Low Survey Mid. Monitor and SDP_REQ_INT-11 Monitoring. Log reporting- SDP SKA1 Low Survey Mid. Monitor and SDP_REQ_INT-12 Monitoring. Log level- SDP SKA1 Low Survey Mid. Monitor and SDP_REQ_INT-13 Monitoring. Drill-down capability- SDP SKA1 Low Survey Mid. Monitor and SDP_REQ_INT-14 Monitoring. Drill-down activation- SDP SKA1 Low Survey Mid. Monitor and SDP_REQ_INT-15 Monitoring. Report failures- SDP SKA1 Low Survey Mid. Monitor and The SDP shall report the SDP element external state to TM. The SDP shall report the internal states of sub-elements to TM. The SDP shall report alarms for conditions and failures that: a) pose hazards to equipment, data or personnel b) reduce the effectiveness of SDP to perform its prime functions or provide capabilities. The SDP shall provide the following alarmrelated data to the TM: a) Time of detection: Accuracy of TBD milliseconds with a resolution of TBD milliseconds b) Severity of the Event: Categorised by at least 3 levels of comparison c) Description of the event that caused the alarm The SDP shall report log messages to TM. The TM shall control the level at which log messages are reported. The SDP shall make provision for an extensive set of "drill-down" monitoring points in the SDP to enable a capability for fault diagnostics. The activation of the drill-down capability is TBD. The SDP shall report detected failures, and identification of the source of the failure in the SDP product breakdown structure, based on the FMECA analysis. Where applicable, faulty Line Replaceable Units (LRUs) shall be identified. Release Date: Page 14 of 40

15 SDP_REQ_INT-16 Monitoring. Failure prediction- SDP SKA1 Low Survey Mid. Monitor and SDP_REQ_INT-17 Monitoring. Capability reporting- SDP SKA1 Low Survey Mid. Monitor and SDP_REQ_INT-18 Monitoring. Resource Overview- SDP SKA1 Low Survey Mid. Monitor and SDP_REQ_INT-19 Monitoring. Current Capability availability- SDP SKA1 Low Survey Mid. Monitor and SDP_REQ_INT-20 Monitoring. Event reporting - SDP SKA1 Low Survey Mid. Monitor and SDP_REQ_INT-21 Engineering Interface- SDP SKA1 Low Survey Mid. Monitor and SDP_REQ_INT-22 Lifecycle Management. Remote updates- SDP SKA1 Low Survey Mid. Monitor and SDP_REQ_INT-23 Lifecycle Management. Facilitate remote updates- SDP SKA1 Low Survey Mid. Monitor and The SDP shall report monitoring points that are required for preventive maintenance, as identified in the FMECA analysis. The SDP, when requested by the TM to commit/engage a capability, shall report the availability of that capability as either: a) Not available b) Available, with degraded performance c) Available with full performance The SDP shall present a high-level overview of SDP resource availability. The SDP shall report on all capabilities available to the telescope. The SDP shall report the following events to TM: a) Processing progress: SDP shall report on "Processing Started", "Processing Completed" and "Processing Success/Fail" events to TM to indicate the progress of a capability. b) Mode/Frequency change: SDP shall report on the successful/failed mode or observational frequency band change requested by the TM. c) VO event: SDP shall report on the creation of a VO event. The TM shall provide a "tunnelling" capability to access engineering interfaces of sub-elements remotely. The SDP shall enable patching and upgrade of software and firmware remotely. The TM shall provide "tunnelling" capability to facilitate remote software and firmware upgrades. Release Date: Page 15 of 40

16 SDP_REQ_INT-24 Lifecycle Management. Report version information - SDP SKA1 Low Survey Mid. Monitor and SDP_REQ_INT-25 Data Transport. Maximum data rate- SDP SKA1 Low Survey Mid. Monitor and SDP_REQ_INT-26 Protocol. Communications protocol- SDP SKA1 Low Survey Mid. Monitor and SDP_REQ_INT-27 Data Identification. Exclusions- SDP SKA1 Low Survey Mid. Telescope State Information SDP_REQ_INT-28 Data Identification. Critical information- SDP SKA1 Low Survey Mid. Telescope State Information SDP_REQ_INT-29 Data Identification. Non-critical information- SDP SKA1 Low Survey Mid. Telescope State Information SDP_REQ_INT-30 Data Transport. Maximum data rate- SDP SKA1 Low Survey Mid. Telescope State Information SDP_REQ_INT-31 Protocol. Communications protocol- SDP SKA1 Low Survey Mid. Telescope State Information SDP_REQ_INT-32 Visibility Organisation- SDP SKA1 Low, Survey and Mid. Visibility Data The SDP shall report version information of all software and firmware. The maximum data rate for the transfer of control and monitoring data to facilitate the SDP_TM interface is TBD. The communications protocol for this interface is defined in Section 5 of this document. The TM shall ensure that all Telescope State Information contained in the Telescope Model will be available for transmission to the SDP in one of the categories defined below. The TM shall send and the SDP shall receive Telescope State Information as detailed in Appendix X within TBD seconds of the TM receiving such state information. These information points are classified as critical for the purposes of this document. The TM shall send and the SDP shall receive Telescope State Information other than that detailed in Appendix X within TBD seconds of the TM receiving such state information. These information points are classified as non-critical for the purposes of this document. The maximum data rate for the transfer of control and monitoring data to facilitate the SDP_TM interface is TBD. The communications protocol for this interface is defined in Section 5 of this document. See for information on data organisation. Release Date: Page 16 of 40

17 SDP_REQ_INT-33 Visibility Coverage- SDP SKA1 Low, Survey and Mid. Visibility Data SDP_REQ_INT-34 Visibility Transport- SDP SKA1 Low, Survey and Mid. Visibility Data For a given set of frequency channels the CSP shall produce all possible crosscorrelations and auto-correlations. The CSP shall produce visibility data using UDP/IP on IEEE Ethernet frames. SDP_REQ_INT-35 Visibility MTU- SDP SKA1 Low, Survey and Mid. Visibility Data SDP_REQ_INT-36 Visibility Format- SDP SKA1 Low, Survey and Mid. Visibility Data SDP_REQ_INT-37 Visibility Communications protocol- SDP SKA1 Low, Survey and Mid. Visibility Data SDP_REQ_INT-38 Visibility Routing- SDP SKA1 Low, Survey and Mid. Visibility Data SDP_REQ_INT-39 Visibility Multiple streams- SDP SKA1 Low, Survey and Mid. Visibility Data SDP_REQ_INT-40 Visibility SKA-1 Low Data Rate- SDP SKA1 Low, Survey and Mid. Visibility Data SDP_REQ_INT-41 Visibility SKA-1 Survey Data Rate- SDP SKA1 Low, Survey and Mid. Visibility Data SDP_REQ_INT-42 Visibility SKA-1 Mid Data Rate- SDP SKA1 Low, Survey and Mid. Visibility Data SDP_REQ_INT-43 Visibility Meta-data- SDP SKA1 Low, Survey and Mid. Visibility Data The UDP MTU shall be as large as possible, whilst still maintaining transmission compatibility with COTS networking equipment. See for information on data format. SPEAD [AD1] with visibility specific payload format. The communications protocol for this interface is further defined in Section 5 of this document. Subsets of the visibility data hierarchy shall be routable to specific IP and port combinations. Subsets are still TBD. The CSP, when producing multiple streams of visibility data, will provide sufficient control and meta-data to allow each stream to be independently received by the SDP. The CSP-Low shall send and the SDP-Low shall receive visibility data at a maximum rate of Tbps (TBC). The CSP-Survey shall send and the SDP- Survey shall receive visibility data at a maximum rate of Tbps (TBC). The CSP-Mid shall send and the SDP-Mid shall receive visibility data at a maximum rate of Tbps (TBC). The CSP shall provide sufficient meta-data with the visibility data to allow the receiver to fully decode any encapsulation without additional information. Specifically this will include the ability to convert timestamp information into an absolute time standard (UTC, TBD). VR-2 Verification by Analysis Release Date: Page 17 of 40

18 SDP_REQ_INT-44 Visibility Antenna Labelling- SDP SKA1 Low, Survey and Mid. Visibility Data SDP_REQ_INT-45 Visibility Timestamps- SDP SKA1 Low, Survey and Mid. Visibility Data SDP_REQ_INT-46 Visibility Channel / Baseline ID- SDP SKA1 Low, Survey and Mid. Visibility Data SDP_REQ_INT-47 Visibility Channel / Baseline Count- SDP SKA1 Low, Survey and Mid. Visibility Data SDP_REQ_INT-48 Visibility Schedule Block ID- SDP SKA1 Low, Survey and Mid. Visibility Data SDP_REQ_INT-49 Visibility Hardware ID- SDP SKA1 Low, Survey and Mid. Visibility Data SDP_REQ_INT-50 Visibility Time Centroid- SDP SKA1 Low, Survey and Mid. Visibility Data SDP_REQ_INT-51 Visibility Complex Visibility- SDP SKA1 Low, Survey and Mid. Visibility Data Metadata included with visibility data will include labels of antennas forming the visibility in the format as used by TM. The order of antenna labels forming the visibility shall be according to the sign convention of the SKA telescope. 64-bit integer UTC timestamp epoch of the last sample that was integrated (i.e. whether flagged/not correlated, or not). 32 bits is 1 second count since UTC epoch; 32 bits is fraction of a 1 second, providing ~0.25 ns timestamp resolution. As a minimum each integration time (60ms) needs to be uniquely identified. Nanosecond timestamp resolution is needed for pulsar phase binning use cases. Channel ID, baseline ID and beam ID (Survey only) once per integration time. 26- bit baseline polarisation ID (to allow for 10e4 stations in SKA2) and a 22-bit channel ID for Low and Mid. 22-bit baseline ID (to allow for ~3k stations in SKA2), a 20-bit channel ID, and a 6-bit beam ID for Survey. Provides offset into channel / baseline visibility array for this particular heap. Provides counts for the two dimensions of the channel / baseline visibility array. When used in conjunction with the ID, uniquely identifies the portion of the overall array in this heap. 26 bits for the baseline count and 22 bits for the channel count. A 64-bit schedule block ID used to uniquely associate correlator data with a particular observation. This ID will be provided to the CSP by TM. Actual bit length is TBD pending decision from TM. Hardware source ID, 24-bit. This indicates the hardware source of the data for testing/troubleshooting/back tracing to a hardware fault. Time centroid index (TCI), as 8-bit integer (TBD). Is the unit-less calculated centroid of the integration interval. Complex visibility, two 32-bit single-precision floating point numbers already data valid normalized. Release Date: Page 18 of 40

19 SDP_REQ_INT-52 Visibility Flagging Fraction- SDP SKA1 Low, Survey and Mid. Visibility Data SDP_REQ_INT-53 Visibility Normalisation- SDP SKA1 Low, Survey and Mid. Visibility Data SDP_REQ_INT-54 Visibility Delay Tracking- SDP SKA1 Low, Survey and Mid. Visibility Data SDP_REQ_INT-55 Visibility Doppler Tracking- SDP SKA1 Low, Survey and Mid. Visibility Data SDP_REQ_INT-56 Pulsar Search Transport- SDP SKA1 Mid. Pulsar Search Data SDP_REQ_INT-57 Pulsar Search Format- SDP SKA1 Mid. Pulsar Search Data SDP_REQ_INT-58 Pulsar Search Communications protocol- SDP SKA1 Mid. Pulsar Search Data SDP_REQ_INT-59 Pulsar Search SKA-1 Mid Data Rate- SDP SKA1 Mid. Pulsar Search Data SDP_REQ_INT-60 Pulsar Search Meta-data- SDP SKA1 Mid. Pulsar Search Data SDP_REQ_INT-61 Pulsar Search Candidates- SDP SKA1 Mid. Pulsar Search Data SDP_REQ_INT-62 Pulsar Timing Transport- SDP SKA1 Mid. Pulsar Timing Data 8-bit (TBD) integer indicating the fraction of data (FD) that was correlated. Encode the square root of FD in 8 bits. Reserve 1 bit of the FD for a hardware fault flag The CSP shall not perform Van Vleck, or any other normalization corrections, on the visibility data. The CSP shall apply delay tracking and fringe stopping corrections to each channel, as supplied by the TM, to all visibility data sent to the SDP. The CSP shall apply Doppler tracking corrections, as supplied by the TM, to all visibility data sent to the SDP The CSP shall produce pulsar search data using TCP/IP on IEEE Ethernet frames. The format for pulsar search candidates is TBD. Unidirectional high-level message passing protocol running on TCP/IP.5 The CSP-Mid shall send and the SDP-Mid shall receive pulsar search data at a maximum rate of 10 Gbps. The CSP-Mid shall send and the SDP-Mid shall receive transient or single pulse search data at a maximum data rate of 4 Gbps. The CSP shall provide sufficient meta-data with the pulsar search data to allow the receiver to fully decode any encapsulation without additional information. List of pulsar search candidates in TBD format. The CSP shall produce pulsar timing data using TCP/IP on IEEE Ethernet frames. Release Date: Page 19 of 40

20 SDP_REQ_INT-63 Pulsar Timing Format- SDP SKA1 Mid. Pulsar Timing Data SDP_REQ_INT-64 Pulsar Timing Communications protocol- SDP SKA1 Mid. Pulsar Timing Data SDP_REQ_INT-65 Pulsar Timing SKA-1 Mid Data Rate- SDP SKA1 Mid. Pulsar Timing Data SDP_REQ_INT-66 Pulsar Timing Meta-data- SDP SKA1 Mid. Pulsar Timing Data SDP_REQ_INT-67 Pulsar Timing Communications protocol- SDP SKA1 Mid. Pulsar Timing Data SDP_REQ_INT-68 Pulsar Timing SKA-1 Mid Data Rate- SDP SKA1 Mid. Pulsar Timing Data SDP_REQ_INT-69 Pulsar Timing Meta-data- SDP SKA1 Mid. Pulsar Timing Data SDP_REQ_INT-70 Rack size- SDP Compute SKA1 Common Mechanical SDP_REQ_INT-71 Rack standard- SDP Compute SKA1 Common Mechanical SDP_REQ_INT-72 Service area- SDP Compute SKA1 Common Mechanical 1. The format for the pulsar timing data is defined as PSRFITS file format. Individual files are 10s dumps Each file is max 68 MB per beam per dump File transfer between CSP and SDP using rsync (TBC). The CSP-Mid shall send and the SDP-Mid shall receive pulsar timing data at a maximum rate of 9.4 Gbps (this data rate is for the payload data only and does not include overhead for the file format, protocol, etc.) The CSP shall provide sufficient meta-data with the pulsar timing data to allow the receiver to fully decode any encapsulation without additional information. File transfer between CSP and SDP using rsync (TBC). The CSP-Mid shall send and the SDP-Mid shall receive pulsar timing data at a maximum rate of 9.4 Gbps (this data rate is for the payload data only and does not include overhead for the file format, protocol, etc.) The CSP shall provide sufficient meta-data with the pulsar timing data to allow the receiver to fully decode any encapsulation without additional information. The racks referred to hereafter shall be of size 1200mm D x 600mm W x 2100mm H. The racks of equipment provided by the SDP for installation in the allocated space provided by INFRA shall meet the IEC standard TBC in terms of mechanical interfaces and size. Additional aisle space in front of racks of 1200mm will be provided by INFRA for each rack of SDP equipment to allow for doors, cabling and operator access. VR-4 Verification by Inspection VR-4 Verification by Inspection VR-4 Verification by Inspection Release Date: Page 20 of 40

21 SDP_REQ_INT-73 Floor loading- SDP Compute SKA1 Common Mechanical SDP_REQ_INT-74 Connection- SDP Compute SKA1 Common Mechanical SDP_REQ_INT-75 Temperature- SDP Compute SKA1 Common Mechanical SDP_REQ_INT-76 Capacity- SDP Compute SKA1 Common Mechanical SDP_REQ_INT-77 Environment- SDP Compute SKA1 Common Mechanical SDP_REQ_INT-78 Additional load- SDP Compute SKA1 Common Mechanical SDP_REQ_INT-79 Data centre power efficiency- SDP Compute SKA1 Common Mechanical SDP_REQ_INT-80 Per rack power consumption- SDP Compute SKA1 Common Mechanical SDP_REQ_INT-81 Nominal voltage- SDP Compute SKA1 Common Mechanical SDP_REQ_INT-82 Level variation- SDP Compute SKA1 Common Mechanical SDP_REQ_INT-83 Nominal level- SDP Compute SKA1 Common Mechanical SDP_REQ_INT-84 Harmonic distortion- SDP Compute SKA1 Common Mechanical Equipment provided by the SDP for installation in the allocated space provided by INFRA shall have a maximum floor loading of 2000 kg per square metre TBC. INFRA will provide a fluid interface to each SDP rack that conforms to the TBD standard. INFRA shall ensure that the temperature of the cooling fluid at the point of ingress to the SDP rack is no more than 22 degrees Celsius TBC. The SDP shall ensure that the SDP rack presents no more than 50 kw TBC of heat load to the cooling medium. INFRA shall ensure that the ambient environment of the SDP equipment is no more than 25 degrees Celsius TBC. The SDP shall ensure that the SDP equipment inserts no more than TBD kw of additional load into the INFRA environment. The data centre housing SDP equipment shall have a PUE no greater than The SDP equipment will be limited to a maximum of 50 kw per rack. INFRA shall provide a power supply with a nominal voltage of 230V AC. INFRA shall provide a power supply with a variation of no more than TBD % from the steady state level. INFRA shall provide a power supply with a steady state voltage equal to the specified nominal voltage +10/-6% TBC. INFRA shall provide a power supply with total harmonic distortion less than TBD %. VR-4 Verification by Inspection VR-2 Verification by Analysis Release Date: Page 21 of 40

22 SDP_REQ_INT-85 Frequency variation- SDP Compute SKA1 Common Mechanical INFRA shall provide a power supply with power supply frequency of 50Hz +/-TBD %. SDP_REQ_INT-86 led shutdown under UPS- SDP Compute SKA1 Common Mechanical SDP_REQ_INT-87 Redundancy- SDP Compute SKA1 Common Mechanical SDP_REQ_INT-88 Scope- SDP Compute SKA1 Common Mechanical SDP_REQ_INT-89 Logging- SDP Compute SKA1 Common Mechanical SDP_REQ_INT-90 Configuration- SDP Compute SKA1 Common Mechanical SDP_REQ_INT-91 Ease of Use- SDP Compute SKA1 Common Mechanical SDP_REQ_INT-92 Authentication- SDP Compute SKA1 Common Mechanical SDP_REQ_INT-93 Space allocation- SDP Compute SKA1 Mid Mechanical SDP_REQ_INT-94 Cable trays- SDP Compute SKA1 Mid Mechanical SDP_REQ_INT-95 Overall power consumption- SDP Compute SKA1 Mid Electrical INFRA shall provide uninterruptable power at a TBD level for a duration of TBD to the SDP in the event of a major power supply failure. Each rack shall be supplied by two independent power feeds. An access control system provided by INFRA shall prevent unauthorised access to all SDP equipment. The access control system provided by INFRA shall ensure that all access attempts to the SDP equipment are logged. The access control system provided by INFRA shall have the ability to provide temporary access for contractors and maintainers as authorised by the SDP. The access control system provided by INFRA shall not impact on staff activities once inside the secure area. The access control system provided by INFRA shall use authentication media that is revocable and replaceable. INFRA-SA shall provide sufficient floor space for the installation of 100 racks TBC. INFRA-SA shall supply and install cable trays sufficient to cover the following requirements [width, mass loading, above/below are TBD]. The SDP equipment will be limited to an overall power limit of 3.2MW. VR-2 Verification by Analysis VR-4 Verification by Inspection VR-2 Verification by Analysis VR-4 Verification by Inspection VR-2 Verification by Analysis Release Date: Page 22 of 40

23 SDP_REQ_INT-96 Medium- SDP Compute SKA1 Mid Fire SDP_REQ_INT-97 Warning- SDP Compute SKA1 Mid Fire SDP_REQ_INT-98 Space allocation- SDP Compute SKA1 Low Mechanical SDP_REQ_INT-99 Cable trays- SDP Compute SKA1 Low Mechanical SDP_REQ_INT-100 Overall power consumption- SDP Compute SKA1 Low Electrical SDP_REQ_INT-101 Medium- SDP Compute SKA1 Low Fire SDP_REQ_INT-102 Warning- SDP Compute SKA1 Low Fire SDP_REQ_INT-103 Space allocation- SDP Compute SKA1 Survey Mechanical SDP_REQ_INT-104 Cable trays- SDP Compute SKA1 Survey Mechanical SDP_REQ_INT-105 Overall power consumption- SDP Compute SKA1 Survey Electrical SDP_REQ_INT-106 Medium- SDP Compute SKA1 Survey Fire The fire control system provided by INFRA- SA shall use a medium that complies to the following South African standards (TBD) in order to ensure that unnecessary damage is not caused to SDP equipment in the case of a fire suppression event. The fire control system provided by INFRA- SA shall provide visual and audible warnings prior to the activation of the fire suppression system to allow evacuation of personnel from the environment. INFRA-AUS shall provide sufficient floor space for the installation of 25 racks TBC. INFRA-AUS shall supply and install cable trays sufficient to cover the following requirements [width, mass loading, above/below are TBD]. The SDP equipment will be limited to an overall power limit of 0.75 MW TBC. The fire control system provided by INFRA- AUS shall use a medium that complies to the following Australian standards (TBD) in order to ensure that unnecessary damage is not caused to SDP equipment in the case of a fire suppression event. The fire control system provided by INFRA- AUS shall provide visual and audible warnings prior to the activation of the fire suppression system to allow evacuation of personnel from the environment. INFRA-AUS shall provide sufficient floor space for the installation of 75 racks TBC. INFRA-AUS shall supply and install cable trays sufficient to cover the following requirements [width, mass loading, above/below are TBD]. The SDP equipment will be limited to an overall power limit of 2.0 MW TBC. The fire control system provided by INFRA- AUS shall use a medium that complies to the following Australian standards (TBD) in VR-4 Verification by Inspection VR-2 Verification by Analysis VR-2 Verification by Analysis VR-4 Verification by Inspection VR-2 Verification by Analysis VR-2 Verification by Analysis VR-4 Verification by Inspection Release Date: Page 23 of 40

24 SDP_REQ_INT-107 Warning- SDP Compute SKA1 Survey Fire SDP_REQ_INT-108 Rack size- SDP Archive SKA1 Common Mechanical SDP_REQ_INT-109 Rack standard- SDP Archive SKA1 Common Mechanical SDP_REQ_INT-110 Service area- SDP Archive SKA1 Common Mechanical SDP_REQ_INT-111 Floor loading- SDP Archive SKA1 Common Mechanical SDP_REQ_INT-112 Environment- SDP Archive SKA1 Common Thermal SDP_REQ_INT-113 Humidity- SDP Archive SKA1 Common Thermal SDP_REQ_INT-114 Data centre power efficiency- SDP Archive SKA1 Common Electrical SDP_REQ_INT-115 Per rack power consumption- SDP Archive SKA1 Common Electrical SDP_REQ_INT-116 Nominal voltage- SDP Archive SKA1 Common Electrical SDP_REQ_INT-117 Level variation- SDP Archive SKA1 Common Electrical order to ensure that unnecessary damage is not caused to SDP equipment in the case of a fire suppression event. The fire control system provided by INFRA- AUS shall provide visual and audible warnings prior to the activation of the fire suppression system to allow evacuation of personnel from the environment. The racks referred to hereafter shall be of size 1200mm D x 600mm W x 2100mm H. The racks of archive equipment provided by the SDP for installation in the allocated space provided by INFRA shall meet the IEC standard TBC in terms of mechanical interfaces and size. Additional aisle space in front of racks of 1200mm will be provided by INFRA for each rack of SDP archive equipment to allow for doors, cabling and operator access. Equipment provided by the SDP for installation in the allocated space provided by INFRA shall have a maximum floor loading of 2000 kg per square metre TBC. INFRA shall ensure that the ambient environment of the SDP equipment is no more than 25 degrees Celsius TBC. INFRA shall ensure that the ambient environment of the SDP equipment is in the range 20% to 80% humidity non-concensing. The data centre housing SDP equipment shall have a PUE no greater than The SDP equipment will be limited to a maximum of 20 kw per rack. INFRA shall provide a power supply with a nominal voltage of 230V AC. INFRA shall provide a power supply with a variation of no more than TBD % from the steady state level. VR-4 Verification by Inspection VR-4 Verification by Inspection VR-4 Verification by Inspection VR-2 Verification by Analysis VR-2 Verification by Analysis Release Date: Page 24 of 40

25 SDP_REQ_INT-118 Nominal level- SDP Archive SKA1 Common Electrical SDP_REQ_INT-119 Harmonic distortion- SDP Archive SKA1 Common Electrical SDP_REQ_INT-120 Frequency variation- SDP Archive SKA1 Common Electrical SDP_REQ_INT-121 led shutdown under UPS- SDP Archive SKA1 Common Electrical SDP_REQ_INT-122 Redundancy- SDP Archive SKA1 Common Electrical SDP_REQ_INT-123 Logging- SDP Archive SKA1 Common Access SDP_REQ_INT-124 Configuration- SDP Archive SKA1 Common Access SDP_REQ_INT-125 Ease of Use- SDP Archive SKA1 Common Access SDP_REQ_INT-126 Authentication- SDP Archive SKA1 Common Access SDP_REQ_INT-127 Space allocation- SDP Archive SKA1 Mid Mechanical SDP_REQ_INT-128 Cable trays- SDP Archive SKA1 Mid Mechanical SDP_REQ_INT-129 Total heat load- SDP Archive SKA1 Mid Thermal INFRA shall provide a power supply with a variation of no more than TBD % from the steady state level. INFRA shall provide a power supply with total harmonic distortion less than TBD %. INFRA shall provide a power supply with power supply frequency of 50Hz +/I TBD %. INFRA shall provide uninterruptable power at a TBD level for a duration of TBD to the SDP in the event of a major power supply failure. Each rack shall be supplied by two independent power feeds. The access control system provided by INFRA shall ensure that all access attempts to the SDP equipment are logged. The access control system provided by INFRA shall have the ability to provide temporary access for contractors and maintainers as authorised by the SDP. The access control system provided by INFRA shall not impact on staff activities once inside the secure area. The access control system provided by INFRA shall use authentication media that is revocable and replaceable. INFRA-SA shall provide sufficient floor space for the installation of TBD archive racks. INFRA-SA shall supply and install cable trays sufficient to cover the following requirements [width, mass loading, above/below are TBD]. The SDP shall ensure that the SDP archive equipment inserts no more than TBD kw of total load into the INFRA environment. VR-4 Verification by Inspection VR-4 Verification by Inspection VR-4 Verification by Inspection Release Date: Page 25 of 40

26 SDP_REQ_INT-130 Overall power consumption- SDP Archive SKA1 Mid Electrical SDP_REQ_INT-131 Medium- SDP Archive SKA1 Mid Fire SDP_REQ_INT-132 Warning- SDP Archive SKA1 Mid Fire SDP_REQ_INT-133 Space allocation- SDP Archive SKA1 Low Mechanical SDP_REQ_INT-134 Cable trays- SDP Archive SKA1 Low Mechanical SDP_REQ_INT-135 Total heat load- SDP Archive SKA1 Low Thermal SDP_REQ_INT-136 Overall power consumption- SDP Archive SKA1 Low Electrical SDP_REQ_INT-137 Medium- SDP Archive SKA1 Low Fire SDP_REQ_INT-138 Warning- SDP Archive SKA1 Low Fire SDP_REQ_INT-139 Space allocation- SDP Archive SKA1 Survey Mechanical SDP_REQ_INT-140 Cable trays- SDP Archive SKA1 Survey Mechanical The SDP archive equipment will be limited to an overall power limit of TBD kw. The fire control system provided by INFRA- SA shall use a medium that complies to the following South African standards (TBD) in order to ensure that unnecessary damage is not caused to SDP archive equipment in the case of a fire suppression event. The fire control system provided by INFRA- SA shall provide visual and audible warnings prior to the activation of the fire suppression system to allow evacuation of personnel from the environment. INFRA-AUS shall provide sufficient floor space for the installation of TBD archive racks. INFRA-AUS shall supply and install cable trays sufficient to cover the following requirements [width, mass loading, above/below are TBD]. The SDP shall ensure that the SDP archive equipment inserts no more than TBD kw of total load into the INFRA environment. The SDP equipment will be limited to an overall power limit of TBD kw. The fire control system provided by INFRA- AUS shall use a medium that complies to the following Australian standards (TBD) in order to ensure that unnecessary damage is not caused to SDP equipment in the case of a fire suppression event. The fire control system provided by INFRA- AUS shall provide visual and audible warnings prior to the activation of the fire suppression system to allow evacuation of personnel from the environment. INFRA-AUS shall provide sufficient floor space for the installation of TBD archive racks. INFRA-AUS shall supply and install cable trays sufficient to cover the following requirements [width, mass loading, above/below are TBD]. VR-4 Verification by Inspection VR-2 Verification by Analysis VR-2 Verification by Analysis VR-4 Verification by Inspection VR-2 Verification by Analysis VR-2 Verification by Analysis Release Date: Page 26 of 40

27 SDP_REQ_INT-141 Total heat load- SDP Archive SKA1 Survey Thermal SDP_REQ_INT-142 Overall power consumption- SDP Archive SKA1 Survey Electrical SDP_REQ_INT-143 Medium- SDP Archive SKA1 Survey Fire SDP_REQ_INT-144 Warning- SDP Archive SKA1 Survey Fire SDP_REQ_INT-145 Visibility Wire data rate- SDP SKA1 Low Data SDP_REQ_INT-146 Visibility Data Link and Framing-SDP SKA1 Low Data SDP_REQ_INT-147 Visibility SADT-SDP end point -SDP SKA1 Low Data SDP_REQ_INT-148 Visibility Individual link capacity-sdp SKA1 Low Data SDP_REQ_INT-149 Visibility Data traffic profile- SDP SKA1 Low Data SDP_REQ_INT-150 Visibility Flow control -SDP SKA1 Low Data SDP_REQ_INT-151 Visibility Data buffering- SDP SKA1 Low Data The SDP shall ensure that the SDP archive equipment inserts no more than TBD kw of total load into the INFRA environment. The SDP archive equipment will be limited to an overall power limit of TBD kw. The fire control system provided by INFRA- AUS shall use a medium that complies to the following Australian standards (TBD) in order to ensure that unnecessary damage is not caused to SDP equipment in the case of a fire suppression event. The fire control system provided by INFRA- AUS shall provide visual and audible warnings prior to the activation of the fire suppression system to allow evacuation of personnel from the environment bit/s (64 bits/visibility) [RD8] (TBC) Ethernet supporting Jumbo frames Demarcation at SDP switch 100Gbit/s Continuous unidirectional data flow from CSP to SDP No flow control to be provided by SADT. None required Release Date: Page 27 of 40

28 SDP_REQ_INT-152 Visibility Transport latency- SDP SKA1 Low Data SDP_REQ_INT-153 Visibility Packet loss-sdp SKA1 Low Data SDP_REQ_INT-154 Visibility Packet out of order-sdp SKA1 Low Data SDP_REQ_INT-155 Visibility Protocol support- SDP SKA1 Low Data SDP_REQ_INT-156 Visibility Pluggable Modules-SDP SKA1 Low Data SDP_REQ_INT-157 Visibility Type of connection between SADT and SDP- SDP SKA1 Low Electrooptical SDP_REQ_INT-158 Visibility Number of connections-sdp SKA1 Low Electro-optical SDP_REQ_INT-159 Visibility Power for pluggable module-sdp SKA1 Low Electrical SDP_REQ_INT-160 Visibility Power Source- SDP SKA1 Low Electrical SDP_REQ_INT-161 Visibility Optical modules- SDP SKA1 Low Mechanical SDP_REQ_INT-162 Visibility Cabling -SDP SKA1 Low Mechanical No special requirements Minimal better than 10-6 suggested None Ethernet/IP/UDP/ Application Header /science data The pluggable modules shall meet 4x25G electrical I/O CAUI-4 IEEE P802.3bm 100 Gigabit Ethernet pluggable modules see document CSP-SDP Data Transmission, Concept Design, Equipment and Architecture [RD6]. Note: The packet flow is presented as a 100Gigabit stream out of the pluggable module. SDP is responsible for the Ethernet switching required to deliver the flows to the SDP receiving equipment. Number of 100GE connections 592 TBC DC power for the pluggable units taken from the Ethernet switch.caui-4 IEEE P802.3bm Power Watts (TBD) Mains or 48v DC power for the transponder units. TBD Receptor housings on the SDP equipment shall fit with pluggable modulescfp4.. Physical space shall be available for the cables or fibres required for client and line side connections. Release Date: Page 28 of 40

29 SDP_REQ_INT-163 Visibility Rack space-sdp SKA1 Low Mechanical SDP_REQ_INT-164 Visibility Number of transponder units-sdp SKA1 Low Mechanical SDP_REQ_INT-165 Visibility Transponder management-sdp SKA1 Low Monitor and SDP_REQ_INT-166 Visibility Traffic management user interface- SDP SKA1 Low Monitor and SDP_REQ_INT-167 Visibility Physical layer monitoring across interface- SDP SKA1 Low Monitor and SDP_REQ_INT-168 Visibility Built in self-test data integrity and performance margin-sdp SKA1 Low Monitor and SDP_REQ_INT-169 Visibility Interoperability between elements following upgrade-sdp SKA1 Low Operational SDP_REQ_INT-170 Visibility Interoperability between elements following upgrade-sdp SKA1 Low Operational SDP_REQ_INT-171 Visibility System integration plan compliance-sdp SKA1 Low Operational SDP_REQ_INT-172 Visibility Precursor constraints-sdp SKA1 Low Operational Standard 19 inch rack space conforming to IEC or ETS will be required from SDP for SADT transponder equipment. The amount of rack space per SADT transponder unit is 10 U TBC. Expected number of rack SADT transponder units TBC. The SADT transponders shall have a Network Management System capable of controlling and monitoring the line and client side interfaces. All traffic management functionality provided by SADT equipment shall have an end user controllable terminal interface provided by SADT e.g. Network manager/craft terminal PC SADT shall provide method to monitor OSI layer 1 statistics inside its interface boundary and collect statistics from end element packetisers and transceiver modules (DOM) via TM and the SADT network manager In non-observation mode the SADT equipment shall self-generate and receive PRBS data streams, or interface to external test equipment, for the purpose of performance margin testing and maintenance of SADT links Interoperability between end element equipment and internal interfaces shall be maintained during system build upgrades using strict version control Interoperability between end element equipment and internal interfaces shall be maintained during system build upgrades using strict version control SADT equipment shall operate according to a system-wide (multi-element) integration test plan owned by the SKAO TBD SADT equipment interfaces and constraints due to the precursor telescopes on site shall be provided system-wide by the SKAO and AIV consortium - TBD Release Date: Page 29 of 40

30 SDP_REQ_INT-173 Visibility Wire data rate- SDP SKA1 Survey Data SDP_REQ_INT-174 Visibility Data Link and Framing-SDP SKA1 Survey Data SDP_REQ_INT-175 Visibility SADT-SDP end point -SDP SKA1 Survey Data SDP_REQ_INT-176 Visibility Individual link capacity-sdp SKA1 Survey Data SDP_REQ_INT-177 Visibility Data traffic profile- SDP SKA1 Survey Data SDP_REQ_INT-178 Visibility Flow control -SDP SKA1 Survey Data SDP_REQ_INT-179 Visibility Data buffering- SDP SKA1 Survey Data SDP_REQ_INT-180 Visibility Transport latency- SDP SKA1 Survey Data SDP_REQ_INT-181 Visibility Packet loss-sdp SKA1 Survey Data SDP_REQ_INT-182 Visibility Packet out of order-sdp SKA1 Survey Data SDP_REQ_INT-183 Visibility Protocol support- SDP SKA1 Survey Data SDP_REQ_INT-184 Visibility Pluggable Tbps (64 bits/visibility) [RD8] (TBC) Ethernet supporting Jumbo frames Demarcation at SDP switch 100Gbit/s Continuous unidirectional data flow from CSP to SDP No flow control to be provided by SADT. None required No special requirements Minimal better than 10-6 suggested None Ethernet/IP/UDP/ Application Header /science data The pluggable modules shall meet 4x25G electrical I/O CAUI-4 IEEE P802.3bm Release Date: Page 30 of 40

31 Modules-SDP SKA1 Survey Electro-optical SDP_REQ_INT-185 Visibility Type of connection between SADT and SDP- SDP SKA1 Survey Electrooptical SDP_REQ_INT-186 Visibility Number of connections-sdp SKA1 Survey Electro-optical SDP_REQ_INT-187 Visibility Power for pluggable module-sdp SKA1 Survey Electrical SDP_REQ_INT-188 Visibility Power Source- SDP SKA1 Survey Electrical SDP_REQ_INT-189 Visibility Optical modules- SDP SKA1 Survey Mechanical SDP_REQ_INT-190 Visibility Cabling -SDP SKA1 Survey Mechanical SDP_REQ_INT-191 Visibility Rack space-sdp SKA1 Survey Mechanical SDP_REQ_INT-192 Visibility Number of transponder units-sdp SKA1 Survey Mechanical SDP_REQ_INT-193 Visibility Transponder management-sdp SKA1 Survey Monitor and SDP_REQ_INT-194 Visibility Traffic management user interface- SDP SKA1 Survey Monitor and 100 Gigabit Ethernet using CFP4 modules see document CSP-SDP Data Transmission, Concept Design, Equipment and Architecture [RD06]. Note: The packet flow is presented as a 100Gigabit stream out of the pluggable module. SDP is responsible for the Ethernet switching required to deliver the flows to the SDP receiving equipment. Number of 100GE connections 371 DC power for the pluggable units taken from the Ethernet switch.caui-4 IEEE P802.3bm Power Watts (TBD) Mains or 48v DC power for the transponder units. TBD Receptor housings on the SDP equipment shall fit with pluggable modulescfp4. Physical space shall be available for the cables or fibres required for client and line side connections. Standard 19 inch rack space conforming to IEC or ETS will be required from SDP for SADT transponder equipment. The amount of rack space per SADT transponder unit is 10 U TBC. Expected number of rack SADT transponder units ~ TBC. The SADT transponders shall have a Network Management System capable of controlling and monitoring the line and client side interfaces. All traffic management functionality provided by SADT equipment shall have an end user controllable terminal interface provided by SADT e.g. Network manager/craft terminal PC Release Date: Page 31 of 40

32 SDP_REQ_INT-195 Visibility Physical layer monitoring across interface- SDP SKA1 Survey Monitor and SDP_REQ_INT-196 Visibility Built in self-test data integrity and performance margin-sdp SKA1 Survey Monitor and SDP_REQ_INT-197 Visibility Interoperability between elements following upgrade-sdp SKA1 Survey Operational SDP_REQ_INT-198 Visibility Interoperability between elements following upgrade-sdp SKA1 Survey Operational SDP_REQ_INT-199 Visibility System integration plan compliance-sdp SKA1 Survey Operational SDP_REQ_INT-200 Visibility Precursor constraints-sdp SKA1 Survey Operational SDP_REQ_INT-201 Visibility Wire data rate- SDP SKA1 Mid Data SDP_REQ_INT-202 Visibility Data Link and Framing-SDP SKA1 Mid Data SDP_REQ_INT-203 Visibility SADT-SDP end point -SDP SKA1 Mid Data SDP_REQ_INT-204 Visibility Individual link capacity-sdp SKA1 Mid Data SADT shall provide method to monitor OSI layer 1 statistics inside its interface boundary and collect statistics from end element packetisers and transceiver modules (DOM) via TM and the SADT network manager In non-observation mode the SADT equipment shall self-generate and receive PRBS data streams, or interface to external test equipment, for the purpose of performance margin testing and maintenance of SADT links Interoperability between end element equipment and internal interfaces shall be maintained during system build upgrades using strict version control Interoperability between end element equipment and internal interfaces shall be maintained during system build upgrades using strict version control SADT equipment shall operate according to a system-wide (multi-element) integration test plan owned by the SKAO TBD SADT equipment interfaces and constraints due to the precursor telescopes on site shall be provided system-wide by the SKAO and AIV consortium - TBD Tbps (64 bits/visibility) [RD8] (TBC) Ethernet supporting Jumbo frames Demarcation at SDP switch 100Gbit/s Release Date: Page 32 of 40

33 SDP_REQ_INT-205 Visibility Data traffic profile- SDP SKA1 Mid Data SDP_REQ_INT-206 Visibility Flow control -SDP SKA1 Mid Data SDP_REQ_INT-207 Visibility Data buffering- SDP SKA1 Mid Data SDP_REQ_INT-208 Visibility Transport latency- SDP SKA1 Mid Data SDP_REQ_INT-209 Visibility Packet loss-sdp SKA1 Mid Data SDP_REQ_INT-210 Visibility Packet out of order-sdp SKA1 Mid Data SDP_REQ_INT-211 Visibility Protocol support- SDP SKA1 Mid Data SDP_REQ_INT-212 Visibility Pluggable Modules-SDP SKA1 Mid Data SDP_REQ_INT-213 Visibility Type of connection between SADT and SDP- SDP SKA1 Mid Electrooptical SDP_REQ_INT-214 Visibility Number of connections-sdp SKA1 Mid Electro-optical SDP_REQ_INT-215 Visibility Power for pluggable module-sdp SKA1 Mid Electrical Continuous unidirectional data flow from CSP to SDP No flow control to be provided by SADT. None required No special requirements Minimal better than 10-6 suggested None Ethernet/IP/UDP/ Application Header /science data The pluggable modules shall meet 4x25G electrical I/O CAUI-4 IEEE P802.3bm 100 Gigabit Ethernet pluggable modules see document CSP-SDP Data Transmission, Concept Design, Equipment and Architecture [RD6]. Note: The packet flow is presented as a 100Gigabit stream out of the pluggable module. SDP is responsible for the Ethernet switching required to deliver the flows to the SDP receiving equipment. Number of 100GE connections 273 DC power for the pluggable units taken from the Ethernet switch.caui-4 IEEE P802.3bm Power Watts (TBD) Release Date: Page 33 of 40

34 SDP_REQ_INT-216 Visibility Power Source- SDP SKA1 Mid Electrical SDP_REQ_INT-217 Visibility Optical modules- SDP SKA1 Mid Mechanical SDP_REQ_INT-218 Visibility Cabling -SDP SKA1 Mid Mechanical SDP_REQ_INT-219 Visibility Rack space-sdp SKA1 Mid Mechanical SDP_REQ_INT-220 Visibility Number of transponder units-sdp SKA1 Mid Mechanical SDP_REQ_INT-221 Visibility Transponder management-sdp SKA1 Mid Monitor and SDP_REQ_INT-222 Visibility Traffic management user interface- SDP SKA1 Mid Monitor and SDP_REQ_INT-223 Visibility Physical layer monitoring across interface- SDP SKA1 Mid Monitor and SDP_REQ_INT-224 Visibility Built in self-test data integrity and performance margin-sdp SKA1 Mid Monitor and SDP_REQ_INT-225 Visibility Interoperability between elements following upgrade-sdp SKA1 Mid Operational Mains or 48v DC power for the transponder units. TBD Receptor housings on the SDP equipment shall fit with pluggable modulescfp4.. Physical space shall be available for the cables or fibres required for client and line side connections. Standard 19 inch rack space conforming to IEC or ETS will be required from SDP for SADT transponder equipment. The amount of rack space per SADT transponder unit is 10 U TBC. Expected number of rack SADT transponder units TBC. The SADT transponders shall have a Network Management System capable of controlling and monitoring the line and client side interfaces. All traffic management functionality provided by SADT equipment shall have an end user controllable terminal interface provided by SADT e.g. Network manager/craft terminal PC SADT shall provide method to monitor OSI layer 1 statistics inside its interface boundary and collect statistics from end element packetisers and transceiver modules (DOM) via TM and the SADT network manager In non-observation mode the SADT equipment shall self-generate and receive PRBS data streams, or interface to external test equipment, for the purpose of performance margin testing and maintenance of SADT links Interoperability between end element equipment and internal interfaces shall be maintained during system build upgrades using strict version control Release Date: Page 34 of 40

35 SDP_REQ_INT-226 Visibility Interoperability between elements following upgrade-sdp SKA1 Mid Operational SDP_REQ_INT-227 Visibility System integration plan compliance-sdp SKA1 Mid Operational SDP_REQ_INT-228 Visibility Precursor constraints-sdp SKA1 Mid Operational SDP_REQ_INT-229 Pulsar Search Wire data rate-sdp SKA1 Mid Data SDP_REQ_INT-230 Pulsar Search Data Link and Framing-SDP SKA1 Mid Data SDP_REQ_INT-231 Pulsar Search SADT-SDP end point -SDP SKA1 Mid Data SDP_REQ_INT-232 Pulsar Search Individual link capacity-sdp SKA1 Mid Data SDP_REQ_INT-233 Pulsar Search Data traffic profile- SDP SKA1 Mid Data SDP_REQ_INT-234 Pulsar Search Flow control -SDP SKA1 Mid Data SDP_REQ_INT-235 Pulsar Search Data buffering-sdp SKA1 Mid Data SDP_REQ_INT-236 Pulsar Search Transport latency- SDP SKA1 Mid Data SDP_REQ_INT-237 Pulsar Search Packet loss-sdp SKA1 Mid Data Interoperability between end element equipment and internal interfaces shall be maintained during system build upgrades using strict version control SADT equipment shall operate according to a system-wide (multi-element) integration test plan owned by the SKAO -TBD SADT equipment interfaces and constraints due to the precursor telescopes on site shall be provided system-wide by the SKAO and AIV consortium - TBD Tbit/s TBC [RD10] Ethernet supporting Jumbo frames Demarcation at SDP switch 10 Gbit/s Continuous unidirectional data flow from CSP to SDP. Note the TCP transport uses bidirectional traffic but any feedback for the Pulsar computation goes via TM. No flow control to be provided by SADT. None required No special requirements Minimal better than 10-6 suggested Release Date: Page 35 of 40

36 SDP_REQ_INT-238 Pulsar Search Packet out of order- SDP SKA1 Mid Data SDP_REQ_INT-239 Pulsar Search Protocol support- SDP SKA1 Mid Data SDP_REQ_INT-240 Pulsar Search Pluggable Modules- SDP SKA1 Mid Electrooptical SDP_REQ_INT-241 Pulsar Search Type of connection between SADT and SDP- SDP SKA1 Mid Electrooptical SDP_REQ_INT-242 Pulsar Search Number of connections-sdp SKA1 Mid Electro-optical SDP_REQ_INT-243 Pulsar Search Power for pluggable module-sdp SKA1 Mid Electrical SDP_REQ_INT-244 Pulsar Search Power Source-SDP SKA1 Mid Electrical SDP_REQ_INT-245 Pulsar Search Optical modules- SDP SKA1 Mid Mechanical SDP_REQ_INT-246 Pulsar Search Cabling -SDP SKA1 Mid Mechanical SDP_REQ_INT-247 Pulsar Search Rack space-sdp SKA1 Mid Mechanical SDP_REQ_INT-248 Pulsar Search Number of transponder units-sdp SKA1 Mid Mechanical None Ethernet/IP/TCP/ Application Header /science data The pluggable modules shall meet 4x25G electrical I/O CAUI-4 IEEE P802.3bm 10 Gigabit Ethernet pluggable modules see document CSP-SDP Data Transmission, Concept Design, Equipment and Architecture [RD06]. Note: The packet flow is presented as a 100Gigabit stream out of the pluggable module. SDP is responsible for the Ethernet switching required to deliver the flows to the SDP receiving equipment. Number of 10 GE connections 23 DC power for the pluggable units taken from the Ethernet switch.caui-4 IEEE P802.3bm Power Watts (TBD) Mains or 48v DC power for the transponder units. TBD Receptor housings on the SDP equipment shall fit with pluggable modulescfp4. Physical space shall be available for the cables or fibres required for client and line side connections. Standard 19 inch rack space conforming to IEC or ETS will be required from SDP for SADT transponder equipment. The amount of rack space per SADT transponder unit is 10 U TBC. Expected number of rack SADT transponder units 1 shared with PST. TBC. Release Date: Page 36 of 40

37 SDP_REQ_INT-249 Pulsar Search Transponder management-sdp SKA1 Mid Monitor and SDP_REQ_INT-250 Pulsar Search Traffic management user interface-sdp SKA1 Mid Monitor and SDP_REQ_INT-251 Pulsar Search Physical layer monitoring across interface- SDP SKA1 Mid Monitor and SDP_REQ_INT-252 Pulsar Search Built in self-test data integrity and performance margin-sdp SKA1 Mid Monitor and SDP_REQ_INT-253 Pulsar Search Interoperability between elements following upgrade-sdp SKA1 Mid Operational SDP_REQ_INT-254 Pulsar Search Interoperability between elements following upgrade-sdp SKA1 Mid Operational SDP_REQ_INT-255 Pulsar Search System integration plan compliance-sdp SKA1 Mid Operational SDP_REQ_INT-256 Pulsar Search Precursor constraints-sdp SKA1 Mid Operational SDP_REQ_INT-257 Pulsar Timing Wire data rate-sdp SKA1 Mid Data SDP_REQ_INT-258 Pulsar Timing Data Link and Framing-SDP SKA1 Mid Data SDP_REQ_INT-259 Pulsar Timing SADT-SDP end The SADT transponders shall have a Network Management System capable of controlling and monitoring the line and client side interfaces. All traffic management functionality provided by SADT equipment shall have an end user controllable terminal interface provided by SADT e.g. Network manager/craft terminal PC SADT shall provide method to monitor OSI layer 1 statistics inside its interface boundary and collect statistics from end element packetisers and transceiver modules (DOM) via TM and the SADT network manager In non-observation mode the SADT equipment shall self-generate and receive PRBS data streams, or interface to external test equipment, for the purpose of performance margin testing and maintenance of SADT links Interoperability between end element equipment and internal interfaces shall be maintained during system build upgrades using strict version control Interoperability between end element equipment and internal interfaces shall be maintained during system build upgrades using strict version control SADT equipment shall operate according to a system-wide (multi-element) integration test plan owned by the SKAO -TBD SADT equipment interfaces and constraints due to the precursor telescopes on site shall be provided system-wide by the SKAO and AIV consortium - TBD Tbit/s TBC Ethernet supporting Jumbo frames Demarcation at SDP switch Release Date: Page 37 of 40

38 point -SDP SKA1 Mid Data SDP_REQ_INT-260 Pulsar Timing Individual link capacity-sdp SKA1 Mid Data SDP_REQ_INT-261 Pulsar Timing Data traffic profile- SDP SKA1 Mid Data SDP_REQ_INT-262 Pulsar Timing Flow control -SDP SKA1 Mid Data SDP_REQ_INT-263 Pulsar Timing Data buffering-sdp SKA1 Mid Data SDP_REQ_INT-264 Pulsar Timing Transport latency- SDP SKA1 Mid Data SDP_REQ_INT-265 Pulsar Timing Packet loss-sdp SKA1 Mid Data SDP_REQ_INT-266 Pulsar Timing Packet out of order- SDP SKA1 Mid Data SDP_REQ_INT-267 Pulsar Timing Protocol support- SDP SKA1 Mid Data SDP_REQ_INT-268 Pulsar Timing Pluggable Modules- SDP SKA1 Mid Electrical SDP_REQ_INT-269 Pulsar Timing Type of connection between SADT and SDP- SDP SKA1 Mid Electrooptical SDP_REQ_INT-270 Pulsar Timing Number of connections-sdp SKA1 Mid Electro-optical 10 Gbit/s Continuous unidirectional data flow from CSP to SDP. Note the TCP transport uses bidirectional traffic but any feedback for the Pulsar computation goes via TM No flow control to be provided by SADT. None required No special requirements Minimal better than 10-6 suggested None Ethernet/IP/TCP/ Application Header /science data The pluggable modules shall meet 4x25G electrical I/O CAUI-4 IEEE P802.3bm 10 Gigabit Ethernet pluggable modules see document CSP-SDP Data Transmission, Concept Design, Equipment and Architecture [RD06]. Note: The packet flow is presented as a 100Gigabit stream out of the pluggable module. SDP is responsible for the Ethernet switching required to deliver the flows to the SDP receiving equipment. Number of 10 GE connections 1 Release Date: Page 38 of 40

39 SDP_REQ_INT-271 Pulsar Timing Power for pluggable module-sdp SKA1 Mid Electrical SDP_REQ_INT-272 Pulsar Timing Power Source-SDP SKA1 Mid Electrical SDP_REQ_INT-273 Pulsar Timing Optical modules- SDP SKA1 Mid Mechanical SDP_REQ_INT-274 Pulsar Timing Cabling -SDP SKA1 Mid Mechanical SDP_REQ_INT-275 Pulsar Timing Rack space-sdp SKA1 Mid Mechanical SDP_REQ_INT-276 Pulsar Timing Number of transponder units-sdp SKA1 Mid Mechanical SDP_REQ_INT-277 Pulsar Timing Transponder management-sdp SKA1 Mid Monitor and SDP_REQ_INT-278 Pulsar Timing Traffic management user interface-sdp SKA1 Mid Monitor and SDP_REQ_INT-279 Pulsar Timing Physical layer monitoring across interface- SDP SKA1 Mid Monitor and SDP_REQ_INT-280 Pulsar Timing Built in self-test data integrity and performance margin-sdp SKA1 Mid Monitor and SDP_REQ_INT-281 Pulsar Timing Interoperability between elements following upgrade-sdp SKA1 Mid Operational DC power for the pluggable units taken from the Ethernet switch.caui-4 IEEE P802.3bm Power Watts (TBD) Mains or 48v DC power for the transponder units. TBD Receptor housings on the SDP equipment shall fit with pluggable modulescfp4. Physical space shall be available for the cables or fibres required for client and line side connections. Standard 19 inch rack space conforming to IEC or ETS will be required from SDP for SADT transponder equipment. The amount of rack space per SADT transponder unit is 10 U TBC. Expected number of rack SADT transponder units 1 shared with PSS TBC. The SADT transponders shall have a Network Management System capable of controlling and monitoring the line and client side interfaces All traffic management functionality provided by SADT equipment shall have an end user controllable terminal interface provided by SADT e.g. Network manager/craft terminal PC SADT shall provide method to monitor OSI layer 1 statistics inside its interface boundary and collect statistics from end element packetisers and transceiver modules (DOM) via TM and the SADT network manager In non-observation mode the SADT equipment shall self-generate and receive PRBS data streams, or interface to external test equipment, for the purpose of Interoperability between end element equipment and internal interfaces shall be maintained during system build upgrades using strict version control Release Date: Page 39 of 40

40 SDP_REQ_INT-282 Pulsar Timing Interoperability between elements following upgrade-sdp SKA1 Mid Operational SDP_REQ_INT-283 Pulsar Timing System integration plan compliance-sdp SKA1 Mid Operational SDP_REQ_INT-284 Pulsar Timing Precursor constraints-sdp SKA1 Mid Operational Interoperability between end element equipment and internal interfaces shall be maintained during system build upgrades using strict version control SADT equipment shall operate according to a system-wide (multi-element) integration test plan owned by the SKAO - TBD. SADT equipment interfaces and constraints due to the precursor telescopes on site shall be provided system-wide by the SKAO and AIV consortium - TBD Release Date: Page 40 of 40

41 PDR04InterfaceRequirements (4) EchoSign Document History February 09, 2015 Created: February 09, 2015 By: Status: Transaction ID: Verity Allan SIGNED XJEHDWA5R48XN63 PDR04InterfaceRequirements (4) History Document created by Verity Allan February 09, :17 PM GMT - IP address: Document ed to Ferdl Graser (ferdl@scs-space.com) for signature February 09, :18 PM GMT Document viewed by Ferdl Graser (ferdl@scs-space.com) February 09, :20 PM GMT - IP address: Document e-signed by Ferdl Graser (ferdl@scs-space.com) Signature Date: February 09, :21 PM GMT - Time Source: server - IP address: Document ed to Paul Alexander (pa@mrao.cam.ac.uk) for signature February 09, :21 PM GMT Document viewed by Paul Alexander (pa@mrao.cam.ac.uk) February 09, :46 PM GMT - IP address: Document e-signed by Paul Alexander (pa@mrao.cam.ac.uk) Signature Date: February 09, :47 PM GMT - Time Source: server - IP address: Signed document ed to Ferdl Graser (ferdl@scs-space.com), Paul Alexander (pa@mrao.cam.ac.uk) and Verity Allan (vla22@mrao.cam.ac.uk) February 09, :47 PM GMT