PDR.03 Requirements Analysis - ASTRONbroekema/papers/SDP-PDR/PDR03... · 2015. 7. 27. · Functions...

Document no: SKA-TEL-SDP-0000033 Unrestricted Revision: 01 Author: F. Graser Release date: 2015-02-09 of 128

PDR.03 Requirements Analysis

Document number………………………………………………….…….SKA-TEL-SDP-0000033

Context………………………………………………………………………………..…………….SE

Revision………………………………………………………………………………………….……1

Author………………………………………………………………………………………F. Graser

Release Date……………………………………………………………………………2015-02-09

Document Classification………………………………………………………………Unrestricted

Status……………………………………………………………………………………………Draft


Name Designation Affiliation

P. Alexander SDP lead University of Cambridge

Signature & Date:

Name Designation Affiliation

F. Graser SDP System Engineer SCS Space

Signature & Date:

Version Date of Issue Prepared by Comments

1.0 2015-02-09 F. Graser

ORGANISATION DETAILS

Name Science Data Processor Consortium

Signature:

Email:

Signature:

Email:

Ferdl Graser (Feb 9, 2015)Ferdl Graser

[email protected]

Paul Alexander (Feb 9, 2015)Paul Alexander

[email protected]

https://secure.echosign.com/verifier?tx=XJEEYJP37E5NW7Z

https://secure.echosign.com/verifier?tx=XJEEYJP37E5NW7Z


Table of Contents 1. Introduction .................................................................................................................................... 4

2. System Description ......................................................................................................................... 4

2.1. Product tree ............................................................................................................................ 4

C Science Data Processor .................................................................................................................... 5

C.1 Hardware Compute Platform .................................................................................................... 5

C.2 Software Compute Platform ..................................................................................................... 6

C.3 Data Layer ................................................................................................................................. 7

C.4 Pipeline Components ................................................................................................................ 8

C.5 Data Delivery Platform .............................................................................................................. 9

C.6 Local Monitoring and Control ................................................................................................. 10

2.2. Functional decomposition .................................................................................................... 11

3. Requirements Analysis .................................................................................................................. 13

3.1. SDP Functional Requirements ............................................................................................... 13

F.1 Continuum Imaging ................................................................................................................. 13

F.2 Spectral line Imaging ............................................................................................................... 29

F.3 Ingest Data .............................................................................................................................. 42

F.4 Real-time Calibration............................................................................................................... 50

F.5 Drift Scan Imaging ................................................................................................................... 51

F.6 Science Analysis ....................................................................................................................... 63

F.7 Imaging Transient Search ........................................................................................................ 65

F.8 Non-Imaging Transient Post Processing .................................................................................. 70

F.9 Pulsar Timing Post Processing ................................................................................................. 72

F.10 Pulsar Search Post Processing ............................................................................................... 75

F.11 Update Global Sky Model ...................................................................................................... 80

F.12 Archiving ................................................................................................................................ 80

F.13 Regional Centre Interface ..................................................................................................... 88

F.14 SKA Archive User Interface.................................................................................................... 90

F.15 SDP LMC ................................................................................................................................ 99

F.16 Commissioning .................................................................................................................... 112

3.2. SDP non-functional requirements ...................................................................................... 113

NF.1 Security ............................................................................................................................... 113

NF.2 Equipment & Component Specifications ............................................................................ 113

NF.3 Production & Manufacturing Specifications ....................................................................... 117


NF.4 Operations .......................................................................................................................... 118

NF.5 EMC & RFI ........................................................................................................................... 119

NF.6 Health, Safety & Environment ............................................................................................ 120

NF.7 Maintenance, Test & Support ............................................................................................. 124

NF.8 VLBI ..................................................................................................................................... 127

1. Introduction This document defines the requirements, functions and components that comprise the Science Data

Processor (SDP) element that is responsible for processing output data for the three SKA

Observatory telescopes.

All the information presented in this document is managed by the systems engineering tool

Innoslate (https://www.innoslate.com/) and can be accessed on-line in order to interactively

interrogate the content. Refer to Addendum A for further details.

Also included with this document are the complete functional decomposition diagram and product

tree diagrams in .png format as well as a spreadsheet containing the following:

All requirements

All functions

All components

Functions – requirements matrix (only functional requirements)

Components – functions matrix

2. System Description

2.1. Product tree The physical hierarchy of the SDP system is shown below in text format and a series of diagrams.

These diagrams are taken from the Innoslate tool and are shown separately due to limitations of the

document format.

https://www.innoslate.com/

https://www.innoslate.com/


C Science Data Processor SDP System

C.1 Hardware Compute Platform

All hardware components within the SKA Science Data Processor

C.1.1 Compute Island

The basic replicatable unit of the SKA Science Data Processor

C.1.1.1 Management Compute Island

Dedicated hardware and software to facilitate efficient management of

the compute island hardware

C.1.1.2 Compute Node

Basic replicatable unit of the compute island

C.1.2 Buffer

Hardware to buffer intermediate data to facilitate iterative processing

C.1.3 SDP Infrastructure

Local cooling, rack space and local power distribution. Interfaces with the data

centre infrastructure resources.


C.1.3.1 Racks

The racks to house the science data processor equipment. Includes

integrated water-cooling if applicable.

C.1.4 Hierarchical Storage

Hierarchical storage system for science data

C.1.4.1 Medium Performance Buffer

Part of the Hierarchical storage.

C.1.4.2 Long Term Storage

Long term storage equipment for science products

C.1.5 Interconnect System

The collection of data transport networks within the Science Data processor

C.1.5.1 Low-latency network core switch

hardware to interconnect the internal low-latency networks present

within each compute island

C.1.5.2 Management Network

dedicated network to manage and control the various hardware

resources within the SDP. Connects the management compute island

resources as well.

C.1.5.3 Data Transport Network

The data transport network responsible for the bulk data transport into

and out of the compute islands

C.1.6 Delivery Platform Hardware

Dedicated hardware for data delivery

C.1.7 LMC Hardware

Dedicated hardware for Local Monitoring and control

C.2 Software Compute Platform

The collection of software that is required to effciently utilize and manage the

hardware compute platform. Provides software services to the data layer.

C.2.1 Compute OS software

Operating system(s) running on SDP hardware

C.2.2 Middleware

Software that provides services to other software components beyond those

available from the operating system.


C.2.2.1 Messaging Layer

Software that provides communication services to other software

components

C.2.2.2 Logging system

Software component that handles the generation, collection,

aggregation and analysis of system logs.

C.2.2.3 Platform Management System

Software systems to deploy, maintain and control the hardware in the

Science data processor

C.2.2.4 System Optimisation Tools

Software tools designed to facilitate system optimisation efforts

C.2.3 Hierarchical Storage Management software

Software that automates the movement of data across various storage tiers

C.2.4 Application Development Environment and SDK

The suite of software components that support and facilitate software

development

C.2.5 Scheduler

Software component responsible for hardware allocation and hardware

requirements estimates

C.3 Data Layer

The software system responsible for data persistence, data base and data life-cycle

services as well as the pipeline framework

C.3.1 Data Manager

Distributed software component that deals with the creation, monitoring and

termination of Data Objects.

C.3.1.1 Data Manager interface to Pipeline Components

C.3.2 Data Life Cycle Manager

Software component that implements a rule driven system for data movement,

persistence and release based on hardware parameters and policies.

C.3.3 Science Archive Software

Software component that implements the database and query capabilities

required for users to discover and retrieve released science data products.


C.3.4 Local Database Services

Generic database services for the SDP, including the Science Archive, the

LMC and potentially source catalogues.

C.3.5 Ingest Data from CSP into Data Layer

High speed data interface between the CSP and SDP.

C.4 Pipeline Components

Software components that, once executed one after the other, form a Data Processing

Pipeline

C.4.1 Processing Library

Software Library of processing components and supporting software

C.4.1.1 Non-imaging processing components

Software components for processing of voltage domain time series

data

C.4.1.2 RM Synthesis Component

Software Component for RM Synthesis of Image Cubes

C.4.1.3 Ingest Components

Software Components for the Ingest Pipeline

C.4.1.3.1 Flagging Component

Software Component for Flagging of RFI

C.4.1.3.2 Demixing Component

Software Component for removal of bright sources outside the

FoV

C.4.1.4 Calibration components

Software Components for performing the Calibration on visibility data

C.4.1.5 Source Finding Components

Software Compmentent for Finding Sources from Image Cubes

C.4.1.6 Imaging Components

Software Components for transforming visibility data into image cubes

C.4.1.6.1 Gridding

Software Component for putting visibility data on a regular

grid


C.4.1.6.2 Deconvolution

Software Component for decovolving Image Cubes

C.4.1.6.3 FFT

Software Component for Fast Fourier Transformation

C.4.2 Algorithmic Software

C.4.3 Sky Model Use and Creation

The Sky Model contains the (parameterized) known sky.

C.4.4 QA components

Quality Assurance components.

C.4.4.1 Global Sky Model QA

Quality Assurance of the Sky Model components

C.5 Data Delivery Platform

A software stack whose purpose is to enable users to search for and access data

products. It includes services to tansport data to specified remote sites and to perform

remote visualisation of data products. This will be deployed at SDP sites and be

available to deploy other Regional Centres.

C.5.2 Tiered Data Transfer Service

Service for managing the movement of data objects to specified remote sites

(e.g., Regional Centres)

C.5.2.1 LMC interface for data scheduling & reporting

Interface for LMC to request data movement using the Tiered Data

Transfer Service, reporting back information from the data delivery

services and for these services to be able to access Authn and AuthZ

information

C.5.3 User Portal

Web based platform hosting user tools and services related to the data delivery

subsystem

C.5.3.1 Astronomer/ Telescope Operator/ Public Interfaces

Web GUI and API interfaces to the data delivery subsystems

C.5.4 Data Discovery Service

Service to enable searching for data objects based on information describing

the objects


C.5.4.1 IVOA Models and Services

C.5.5 Data Visualisation Service

Service that enables remote visualisation of data products

C.5.6 Regional Centre Interface

The interface to move data to the Regional Centres

C.6 Local Monitoring and Control

Provides bridge between external monitor and control requirements and internal sub-

elements.

C.6.1 Local Telescope Model

Storage of meta-data relevant to current observation. Wide variety of data is

stored from static configuration information through to components of the

Local Sky Model.

C.6.2 Data Flow Manager (LMC)

Responsible for constructing physically realisable data flow graphs for

deployment into the data layer.

C.6.3 QA monitoring

Aggregates and inteprets lower level QA data arriving from the various

pipelines.

C.6.4 User Interfaces

Visual environment for presenting QA data. Allows user interaction with the

metric calculations.

C.6.5 Master Controller and error handling

Single instance central controller for all instantiated SDP capabilities. Main

point of contact for TM.

C.6.6 Event monitoring and logging

Logging, alarm and event handling services. Includes aggregation and

granular control.

C.6.7 Data Flow Models

Model describing the sequence in which Pipeline Components are to be

executed

C.6.7.1 Non-imaging pipeline

Voltage domain time series processing


C.6.7.1.1 Pulsar Timing Post Processing

Timing of known Pulsars

C.6.7.1.2 Pulsar Search Post Processing

Post-processing of Pulsar Search candidates

C.6.7.1.3 Non-imaging transient post processing

Single Pulse / Fast Transients

C.6.7.2 Continuum Imaging Pipeline

Continuum Imaging Pipeline

C.6.7.3 Fast Imaging (Slow Transients)

Real-time continuum imaging for slow transient detection

C.6.7.4 Ingest Pipeline

Data Reception and pre-processing

C.6.7.5 Science Analysis Pipeline

Science Analysis pipelines

C.6.7.5.1 Postage Stamp Source Detection

Source Finding component

C.6.7.5.2 RM Synthesis

RM-Synthesis pipeline

C.6.7.6 Calibration Pipeline

Calibration pipeline for EoR processing

C.6.7.7 Real-time calibration pipeline

Real-time calibration pipeline for feedback to CSP

C.6.7.8 Spectral Line Imaging Pipeline

Spectral Line Imaging Pipeline

2.2. Functional decomposition The top level functional hierarchy of the SDP system is shown below in a diagram. Further diagrams

of the functional hierarchy are not practical to show in this format and are therefore omitted.

Complete diagrams are available together with this document.


3. Requirements Analysis The functional breakdown presented earlier in the document is used to categorise the functional

requirements.

3.1. SDP Functional Requirements

F.1 Continuum Imaging

To make science-ready images cubes with spectral dimension representing a Taylor

expansion of continuum spectra, and any alternative representations which are found

to be appropriate, or spectral cubes at low spectral resolution

SDP_REQ-278 Local sky model

The SDP shall use a Local Sky Model, derived from a Global Sky Model or previous

Local Sky Model.

SDP_REQ-372 Early science processing capability

The SDP shall support per telescope early science processing rates 10% of those

required for full observing, as described in the SDP construction plan.

SDP_REQ-386 Continuum imaging pipeline

The SDP shall provide a Continuum Imaging pipeline that constructs wide-band

images. Polarisation shall be available if requested or necessary for calibration or

quality assurance.

SDP_REQ-390 Multi-frequency synthesis imaging

The SDP shall construct and make use of frequency-dependent image models over the

entire observed bandwidth.

SDP_REQ-392 Peeling

The continuum pipeline shall enable peeling of bright sources (strength limited by

signal to noise ratio) from the visibility data.

SDP_REQ-467 Perform Imaging Pipeline Automatic QA

The Imaging Pipeline shall perform standardised, automated Quality Assessment of

Images along the axes of astrometry, photometry, radiometry, polarimetry, and

spectrometry.

SDP_REQ-614 Numerical Precision

The scientific quality and usability of SDP outputs shall be no worse than if all of the

relevant processing steps inside the SDP were carried in double precision floating

point arithmetic.

SDP_REQ-619 Combine multiple image cubes

The Continuum Imaging and Spectral line pipeline shall be able to combine multiple

image cubes appropriately.

SKA1-SYS_REQ-2127 Sub-Arraying.

Sub-Arraying. All of the SKA1 telescopes shall be capable of operating independently

with one to sixteen sub-arrays (i.e. collecting area is split and allocated to separate,

concurrently observing programmes).

SKA1-SYS_REQ-2128 Continuum and spectral line imaging mode.

Continuum and spectral line imaging mode. All three SKA1 telescopes shall be

capable of operating in a Continuum and Spectral-line imaging mode concurrently.

SKA1-SYS_REQ-2134 Electromagnetic frequency range.


Electromagnetic frequency range. SKA1_Low shall be able to measure

electromagnetic radiation in a frequency range from 50 MHz to 350 MHz.

SKA1-SYS_REQ-2140 SKA1_Low station diameter

SKA1_Low station diameter . The station diameter will be 35 metres, which is

consistent with being able to provide a single, circularly symmetric, beam of 5

degrees at the half-power points at 100 MHz (centre of the EoR frequency range)

while meeting the sensitivity requirements with 256 antennas per station evenly

distributed in an irregular-random configuration.

SKA1-SYS_REQ-2142 SKA1_Low number of stations.

SKA1_L ow number of stations . The SKA1_Low shall comprise of 1024 stations.

SKA1-SYS_REQ-2147 Instantaneous bandwidth.

Instantaneous bandwidth. The SKA1_Low shall be capable of simultaneously

processing 300 MHz of bandwidth.

SKA1-SYS_REQ-2148 SKA1_Low channelisation

SKA1_Low channelisation. The SKA1_Low channelisation for each sub array shall

provide up to 256,000 linearly spaced frequency channels across the available

frequency range of each band.

SKA1-SYS_REQ-2153 Diameter

Diameter. SKA1 dishes shall have a projected diameter of larger than or equal to 15m

and smaller than 16.5m.

SKA1-SYS_REQ-2165 Polarisation Purity

Polarisation Purity. The IXR shall be better than 15 dB over the whole observing

bandwidth within the HPBW

SKA1-SYS_REQ-2173 MeerKAT array

MeerKAT array. The monitor and control functions of MeerKAT shall be made

available to SKA1_Mid via a Foreign Telescope interface consisting of a Local

Monitor and Control system connected to the SKA1_Mid Telescope Manager.

SKA1-SYS_REQ-2174 Combined SKA1_Mid configuration.

Combined SKA1 Mid Configuration. 42 % of the Combined SKA1_Mid shall be

within a radius of 400 m of the array centre.

SKA1-SYS_REQ-2178 Combined SKA1_Mid configuration

Combined SKA1_Mid configuration. 14 % of the combined SKA1_Mid array shall be

within a radius between 4,000m and 100,000 m of the array centre.

SKA1-SYS_REQ-2185 RF system sampled bandwidth band 1

RF system sampled bandwidth band 1. The instantaneous bandwidth for band 1 will

be 700MHz and shall be sampled to at least 2.0 G samples per second for each

polarisation.



be 810 MHz and shall be sampled to at least 2.0 G sample per second for each

polarisation.


RF system sampled bandwidth band 3 The instantaneous bandwidth for band 3 will be

1,403 MHz and shall be sampled to at least 5.0 G samples per second for each

polarisation.




2,380 MHz and shall be sampled at at least 5.0 G samples per second for each

polarisation.


RF system sampled bandwidth band 5 The SKA_Mid, for band 5, shall digitise two

separate 2.5 GHz bands for each polarisation.

SKA1-SYS_REQ-2195 SKA1_Mid channelisation

SKA1_Mid channelisation. The SKA1_Mid channelisation for each sub array shall

provide up to 256, 000 linearly spaced frequency channels across the sampled

bandwidth of each band.

SKA1-SYS_REQ-2236 SKA1_Survey configuration

SKA1_Survey configuration. 22% of the SKA1_Survey array shall be within a radius

of 4,000 m and 25,000 m of the array centre

SKA1-SYS_REQ-2238 RF system frequency range PAF band 1

RF system frequency range PAF band 1 The SKA1_Survey PAF for band 1 shall have

a frequency range from 350 to 900 MHz for each polarisation.



a frequency range from 0.650 to 1.670 GHz for each polarisation.


RF system frequency range PAF band 3. The SKA1_Survey PAF for band 3 shall

have a frequency range from 1.500 to RF system frequency range PAF band 3 The

SKA1_Survey PAF for band 3 shall have a frequency range from 1.500 to 4.000 GHz

for each polarisation.

SKA1-SYS_REQ-2241 Maximum available bandwidth

Maximum available bandwidth The SKA1_Survey shall have a PAF bandwidth of at

least 500 MHz for each polarisation and beam

SKA1-SYS_REQ-2242 SKA1_Survey digitised bandwidth

SKA1_Survey digitised bandwidth The SKA1_Survey digitised bandwidth for each

PAF shall be greater than 500 MHz for each polarisation.

SKA1-SYS_REQ-2247 SKA1_Survey number of beams.

SKA1_Survey number of beams. The SKA1_Survey shall beam-form the element

signals in each band to provide 36 full bandwidth, dual polarisation beams per

antenna.

SKA1-SYS_REQ-2250 SKA1_Survey channelisation.

SKA1_Survey channelisation. The SKA1_Survey channelisation shall provide 256,

000 linearly spaced frequency channels across the frequency band of each PAF band.

SKA1-SYS_REQ-2252 SKA1_Survey correlator dump period.

SKA1_Survey correlator dump period. The SKA1_Survey correlator shall have a

programmable dump period in the range 3 seconds to 0.3 seconds

SKA1-SYS_REQ-2256 SKA1_Survey imaging dynamic range.

SKA1_Survey imaging dynamic range Ã¢â‚¬â€œ band 1. The SKA1_Survey array

shall have an imaging dynamic range of greater than:band 1: 55dB for a 1000 hour


single-field integrationband 2: 56dB for a 1000 hour single-field integrationband 3:

54dB for a 1000 hour single-field integration.

SKA1-SYS_REQ-2259 SKA1_Survey spectral dynamic range.

SKA1_Survey spectral dynamic range. The spectral dynamic range for SKA1_Survey

shall be better than 30dB between adjacent channels and 60dB globally.

SKA1-SYS_REQ-2262 SKA1_Survey inclusion of ASKAP.

SKA1_Survey inclusion of ASKAP. The SKA1_Survey shall incorporate the 36

ASKAP antennas in both monitor and control and data collection functions.

SKA1-SYS_REQ-2263 SKA1_Survey single array operation.

SKA1_Survey single array operation . SKA1-Survey shall be capable of operating

ASKAP and SKA1 dishes as single array for frequency band 2.

SKA1-SYS_REQ-2266 SKA1_Survey PAF rotation.

SKA1_Survey derotation. SKA1_Survey shall provide PAF rotation capability

sufficient to orient Phased Array Feed beams on a sky coordinate frame independent

of parallactic angle.

SKA1-SYS_REQ-2319 Closed loop calibration.

Closed loop calibration. The telescope calibration shall be solved by comparison of

observed with GSM predictions with a time scale appropriate to the component and

physical effect being calibrated and fed back to the telescope.

SKA1-SYS_REQ-2321 Direction dependent effects.

Direction dependent effects. Self-calibration and image reconstruction algorithms

shall be capable of dealing with direction dependent effects.

SKA1-SYS_REQ-2322 Global sky model.

Global sky model. Calibration and continuum subtraction shall use a Local Sky

Model, derived from a Global Sky Model or previous Local Sky Model.

SKA1-SYS_REQ-2324 Multi-frequency synthesis imaging.

Multi-frequency synthesis imaging . All imaging shall construct and make use of

frequency dependent image models over the entire observed bandwidth.

SKA1-SYS_REQ-2325 Scale sensitive deconvolution

Deconvolution of single channels Scale sensitive two-dimensional (i.e. on the tangent

plane) deconvolution shall be available.

SKA1-SYS_REQ-2328 Solution for pointing errors.

Solution for pointing errors. It shall be possible to solve for and correct time- and

station-dependent pointing errors with accuracy and timescale limited by signal to

noise ratio.

SKA1-SYS_REQ-2330 Peeling.

Peeling. Peeling of bright sources (strength limited by signal to noise ratio) from the

visibility data shall be possible.

SKA1-SYS_REQ-2338 Calibration pipeline.

Calibration pipeline. There shall be a Calibration pipeline that derives current

telescope parameters using a recent observation and a Global Sky Model, either a

known GSM or the most recent GSM.

SKA1-SYS_REQ-2339 Continuum imaging pipeline.


Continuum imaging pipeline. There shall be a Continuum Imaging pipeline that shall

have the goal of constructing noise-limited wide-band images for observations up to

1000h integration time. Polarisation shall be available if requested or necessary for

calibration or quality assurance.

SKA1-SYS_REQ-2340 Continuum imaging data products.

Continuum imaging data products. The Data Products shall include the first n moment

images for multi-frequency synthesis, corresponding residual images (if

deconvolved), sensitivity image and representative PSF image, where n is set by

signal to noise ratio.

SKA1-SYS_REQ-2634 Calibration update rate

Calibration update rate. Calibration measurements shall be necessary at a rate of no

more than 10seconds.

SKA1-SYS_REQ-2724 Aperture Array DDE

Aperture Array DDE . There shall be a direction dependent model for the aperture

array primary beam to be used in calibration and imaging.

SKA1-SYS_REQ-2725 Faraday rotation DDE

Faraday rotation DDE. There shall be a direction dependent Faraday Rotation model

for use in calibration and imaging.

SKA1-SYS_REQ-2726 PAF DDE

PAF DDE. There shall be a direction dependent model for the dish phased array feed

sensitivity pattern to be used in calibration and imaging.

SKA1-SYS_REQ-2727 Dish DDE

Dish DDE. There shall be a direction dependent model for the dish primary beam to

be used in calibration and imaging.

SKA1-SYS_REQ-2729 Calibration and Imaging formalism

Calibration and imaging formalism. The Calibration and Imaging formalism shall be

based upon the Rau framework [14].

SKA1-SYS_REQ-2745 Astrometry performance metric

Astrometric performance metric: The Astrometric performance metric (APM) shall

measure deviation (rms, average offset, and med) of source positions from known

standards.

SKA1-SYS_REQ-2825 SKA1_Mid Absolute flux scale

Absolute flux scale: The absolute flux scale shall be accurate to 5% rms.



SKA1-SYS_REQ-2828 SKA1_Survey Absolute flux scale

Absolute flux scale: The absolute flux scale shall be accurate to 5% rms



SKA1-SYS_REQ-2833 SKA1_Mid inclusion of MeerKAT

SKA1_Mid inclusion of MeerKAT. The SKA1_Mid shall incorporate the 64 antennas

in both monitor and control and data collection functions.

SKA1-SYS_REQ-???? Mosiacking

Waiting for the description from Bojan.


F.1.1 RFI flagging and excision

To flag visibility data that are affected by RFI or instrumental glitches

SDP_REQ-476 Flag RFI

The SDP shall be capable of automatically flagging known and unknown RFI.

SDP_REQ-477 Excise RFI

The SDP shall be capable of automatically excising known and unknown RFI.

SDP_REQ-487 Flag Data

The ingest shall flag data indicated as bad by the Telescope Manager

SDP_REQ-488 Flag Lightning

The ingest pipeline shall flag RFI from lightning.

SDP_REQ-490 Data Quality

The ingest pipeline shall generate metrics (TBD) about the data quality during

flagging.

SDP_REQ-525 Pulsar Timing RFI Mitigation

Pulsar Timing Post Processing shall be capable of identifying and removing

RFI signals from pulsar timing data.

F.1.4.1 Apply t-f flagger

F.1.1.1 Determine spatial filter weights

F.1.1.2 Apply Spatial filter

SDP_REQ-491 Spatial Filtering

The RFI mitigation step shall perform spatial filtering

SDP_REQ-495 Spatial Filter Weights

The Spatial Filtering step will set the weights for spatial filtering

F.1.1.3 Determine RFI detection threshhold

SDP_REQ-478 Detect RFI

The SDP shall be capable of detecting data that is corrupted by RFI.

SDP_REQ-486 Determine RFI Threshold

The RFI detection will determine the RFI detection threshold

SDP_REQ-489 Covariance Matrices

The ingest pipeline shall compute the appropriate types of covariance

matrices needed to improve the robustness of RFI mitigation

F.1.2 Store LSM

F.12.1 Data Layer Management

Manages and executes the logical data flow from CSP to the final

delivery

SDP_REQ-247 Data Layer Management

There shall be a system of software systems that manages the data flow

from the reception of raw data from CSP to the delivery of science

products.

SDP_REQ-251 Concurrency

The data layer manager of each SKA telescope and all sub-arrays shall

be capable of operating concurrently and independently. It shall be

possible to run additional instances of the data layer manager for other


purposes such as: commissioning, maintenance and simulation in

parallel.


Global sky model. Calibration and continuum subtraction shall use a

Local Sky Model, derived from a Global Sky Model or previous Local

Sky Model.

SKA1-SYS_REQ-2348 Role of science processing centres.

Role of science processing centres. The science-processing centre will

convert the output data from the CSP into science data products to be

stored in the science data archive.

F.12.1.1 Data Life Cycle Control

Automation and management of lifecycle states of data objects

SDP_REQ-248 Data Life Cycle Management

There shall be a mechanism that automates the migration of

data items through the various life cycle states starting from the

initial storage. This shall entail the migration of data items

between storage layers and include backup copies until the data

items become obsolete and are deleted.

SDP_REQ-268 Rejuvenation

The lifetime of archived data shall not be limited by the

lifetime of any of the hardware and software components

comprising the archive.

F.12.1.2 Hierarchical Storage Management

Policy driven placement of data objects in tiered storage

system

SDP_REQ-253 Workload Balance

The data layer shall provide a load balancing optimisation of

the data locality based on the specific performance and I/O

work load at runtime.

SDP_REQ-598 Storage Hierarchy

There shall be a mass storage system that automatically moves

data between high-cost and low-cost storage media for

optimised performance

F.12.1.3 Data Layer Services

Services and API interfaces providing middleware functionality

to other SDP elements.

SDP_REQ-599 Data Service Layer

The Data Service Layer ensures that data access shall be

independent of the physical schema of the underlying compute

infrastructure.

F.12.1.4 Monitoring

Access to system monitoring and application performance data


SDP_REQ-266 Status Information

System status information shall be made available in

compliance with the capabilities specified in SKA-

TEL.SDP.SE-TEL.TM.SE-ICD-001.

SDP_REQ-287 Continuous performance monitoring.

Performance monitoring shall be compliant with the

capabilities specified in SKA-TEL.SDP.SE-TEL.TM.SE-ICD-

001.

F.1.3 Forward Estimate

To estimate a trial sky image cube from visibility data

F.1.4 Deconvolution

To deconvolve the data for the interferometer instrumental response by

subtracting a sky model from the visibility data

SDP_REQ-397 Imager

The imaging pipeline shall provide a clean map image, clean beam image,

clean component map image and residual map image (or the equivalent set of

image cubes in the case of spectral line).

SDP_REQ-403 Deconvolution

The deconvolution step shall transform the calibrated visibilities into a clean

map image, clean beam image, clean component map image and residual map

image (or the equivalent set of image cubes in the case of spectral line).

SDP_REQ-447 Major and minor deconvolution cycles

The deconvolution step shall contain a major and a minor cycle

SDP_REQ-504 Scale sensitive deconvolution

The SDP shall provide scale sensitive two-dimensional (i.e. on the tangent

plane) deconvolution.


Deconvolution of single channels Scale sensitive two-dimensional (i.e. on the

tangent plane) deconvolution shall be available.


F.1.4.2 Subtract Component in Image Plane


The deconvolution step shall transform the calibrated visibilities into a

clean map image, clean beam image, clean component map image and

residual map image (or the equivalent set of image cubes in the case of

spectral line).

F.1.4.3 Identify Component





spectral line).

F.1.4.4 iFFT

SDP_REQ-402 Fourier Transform Algorithm


The continuum pipeline shall use a Fourier Transform algorithm to

transform data and weights between the image plane and visibility

plane (and visa versa).

F.1.4.5 De-gridding

SDP_REQ-398 Gridding & de-gridding

The continuum pipeline shall transform ungridded visibilities and

corresponding weights into gridded visibilities and corresponding

weights (and visa versa).

SDP_REQ-399 Anti-aliasing kernel

The gridding convolution kernel shall contain an anti-aliasing term.

SDP_REQ-400 w-kernel

The gridding convolution kernel shall contain a w-term (wide-field

effect).

SDP_REQ-401 A-kernel

The gridding convolution kernel shall contain an A-term representing

the receptor primary beam (direction-dependent effect).

F.1.4.6 Subtract from uv-data

SDP_REQ-396 LSM subtraction

The Continuum pipeline shall subtract the current local sky model

from the averaged visibilities.

F.1.4.7 Gridding









effect).




F.1.4.8 FFT





F.1.4.9 Major Cycle Loop





spectral line).


F.1.5 Initial Calibration (averaged data)

Initial calibration is already done in the ingest pipeline on full resolution data.

This function exists in case initial calibration needs to be done on averaged

data.

SDP_REQ-417 Calibration pipeline.

SDP shall have a Calibration pipeline that derives current telescope parameters

using a recent observation and either a known or the most recent Global Sky

Model.

F.1.6.5 Correct

SDP_REQ-499 Correct

The calibration pipeline shall be able to correct for direction

independent effects.

F.1.6 Calibration

Skip this step the first time its executed. (this is not shown in the diagram to

reduce complexity)


The SDP shall use a Local Sky Model, derived from a Global Sky Model or

previous Local Sky Model.

SDP_REQ-412 SKA1_Survey spectral dynamic range.

The SDP contribution to the spectral dynamic range for SKA1_Survey shall

be better than TBD between adjacent channels and TBD globally.




Model.

SDP_REQ-424 Polarisation purity.

The SKA1_low station beams shall have a polarisation purity at the zenith

better than TBD after calibration.

SDP_REQ-430 Flux scale

The SDP shall preserve the absolute flux scale provided by the global sky

model.

SDP_REQ-437 SKA1_Survey inclusion of ASKAP.

The SDP shall process data from the SKA1_Survey FoV including the 36

ASKAP antennas including both monitor and control and data collection

functions.

SDP_REQ-441 Automated Quality Assessment.

The SDP shall perform standardised, automated Quality Assessment of Images

along the axes of astrometry, photometry, radiometry, polarimetry, and

spectrometry.

SDP_REQ-442 Astrometric performance metric

The SDP Astrometric performance metric (APM) shall measure deviation

(rms, average offset, and med) of source positions from known standards.

SDP_REQ-443 Photometric performance metric


The SDP Photometric performance metric (PPM) shall measure deviation

(rms, average offset, and med) of source fluxes from known standards.

SDP_REQ-444 Radiometric performance metric

The SDP Radiometric performance metric (RPM) shall measure noise

fluctuations (rms, average offset, and med) in an Image..

SDP_REQ-445 Polarimetric performance metric

The SDP Polarimetric performance metric (OPM) shall measure deviation

(rms, average offset, and med) of source polarisations (polarisation degree and

angle) from known standards.

SDP_REQ-446 Spectrometric performance metric

The SDP Spectrometric performance metric (SPM) shall measure deviation

(rms, average offset, and med) of source spectral lines from known standards.

SDP_REQ-466 Perform Calibration Pipeline Automatic QA

The Calibration Pipeline shall perform standardised, automated Quality

Assessment of Images along the axes of astrometry, photometry, radiometry,

polarimetry, and spectrometry.

SDP_REQ-500 Self-calibration loop

The continuum pipeline shall be able to perform self-calibration in order to

achieve noise-limited performance.

SDP_REQ-536 Pulsar Timing Polarisation Calibration

Pulsar Timing Post Processing shall apply polarisation calibration parameters

provided by TM to pulsar timing data

SDP_REQ-553 Pulsar Timing Flux Calibration

Pulsar Timing Post Processing shall apply flux calibration parameters



Continuum and spectral line imaging mode. All three SKA1 telescopes shall

be capable of operating in a Continuum and Spectral-line imaging mode

concurrently.

SKA1-SYS_REQ-2158 Pointing repeatability.

Pointing repeatability. The pointing repeatability shall be better than 10 arc

seconds rms for winds < 7 m/s at night time.

SKA1-SYS_REQ-2159 Pointing repeatability - Low wind / day time

Pointing repeatability . The pointing repeatability shall be better than 17 arc

seconds rms for an average wind speed of < 7 m/s in the day time

SKA1-SYS_REQ-2160 Pointing repeatability - Higher wind


seconds rms for an average wind speed between 7 and 20 m/s


MeerKAT array. The monitor and control functions of MeerKAT shall be

made available to SKA1_Mid via a Foreign Telescope interface consisting of

a Local Monitor and Control system connected to the SKA1_Mid Telescope

Manager.



SKA1_Survey number of beams. The SKA1_Survey shall beam-form the

element signals in each band to provide 36 full bandwidth, dual polarisation

beams per antenna.


SKA1_Survey imaging dynamic range Ã¢â‚¬â€œ band 1. The SKA1_Survey

array shall have an imaging dynamic range of greater than:band 1: 55dB for a

1000 hour single-field integrationband 2: 56dB for a 1000 hour single-field

integrationband 3: 54dB for a 1000 hour single-field integration.


SKA1_Survey inclusion of ASKAP. The SKA1_Survey shall incorporate the

36 ASKAP antennas in both monitor and control and data collection functions.



sufficient to orient Phased Array Feed beams on a sky coordinate frame

independent of parallactic angle.


Closed loop calibration. The telescope calibration shall be solved by

comparison of observed with GSM predictions with a time scale appropriate to

the component and physical effect being calibrated and fed back to the

telescope.


Direction dependent effects. Self-calibration and image reconstruction

algorithms shall be capable of dealing with direction dependent effects.


Global sky model. Calibration and continuum subtraction shall use a Local

Sky Model, derived from a Global Sky Model or previous Local Sky Model.


Multi-frequency synthesis imaging . All imaging shall construct and make use

of frequency dependent image models over the entire observed bandwidth.


Solution for pointing errors. It shall be possible to solve for and correct time-

and station-dependent pointing errors with accuracy and timescale limited by



Peeling. Peeling of bright sources (strength limited by signal to noise ratio)

from the visibility data shall be possible.



telescope parameters using a recent observation and a Global Sky Model,

either a known GSM or the most recent GSM.

SKA1-SYS_REQ-2621 Spectral stability

Spectral stability: The spectral stability, on a time scale of 600 sec.,of the

station beam bandpass, post station calibration and RFI-mitigation, shall be

within 1.3 %, 0.4 %, 0.6 % and 1.1 % at 50 MHz, 100 MHz, 160 MHz, and


220 MHz respectively compared to the full polarization, parameterized beam

model.

SKA1-SYS_REQ-2629 Station beam stability

Station beam stability. The difference between the parameterized station beam

model and the actual station beam shall remain smaller than 1.3 %, 0.4 %, 0.6

% and 1.1 % relative to the main beam peak power, after calibration, at 50

MHz, 100 MHz, 160 MHZ and 220 MHz respectively


Calibration update rate. Calibration measurements shall be necessary at a rate

of no more than 10seconds.

SKA1-SYS_REQ-2635 Real time calibration

Real-time calibration. The LFAA reception system at station level shall

provide on-line instrumental calibration functions with an update rate of 10

minutes


Aperture Array DDE . There shall be a direction dependent model for the

aperture array primary beam to be used in calibration and imaging.


Faraday rotation DDE. There shall be a direction dependent Faraday Rotation

model for use in calibration and imaging.


PAF DDE. There shall be a direction dependent model for the dish phased

array feed sensitivity pattern to be used in calibration and imaging.


Dish DDE. There shall be a direction dependent model for the dish primary

beam to be used in calibration and imaging.


Calibration and imaging formalism. The Calibration and Imaging formalism

shall be based upon the Rau framework [14].

SKA1-SYS_REQ-2824 SKA1_Low Absolute flux scale

Absolute flux scale : The absolute flux scale shall be accurate to 5%









F.1.6.1 Solve

SDP_REQ-498 Fit model parameters

The calibration pipeline shall fit model parameters for the instrumental

and or sky models taking observed and predicted visibilities as input.


F.1.6.2 Predict

SDP_REQ-501 Predict visibilities

The calibration pipeline shall produce visibilities by taking as input the

local sky model and instrument models.

F.1.6.3 Subtract (calibration)

SDP_REQ-497 Subtract (calibration)

The calibration pipeline shall be able to subtract observed and

predicted visibilities from each other.

F.1.6.4 Flag (calibration)

SDP_REQ-503 Flag (calibration)

The calibration pipeline shall be able to flag visibilities on the basis of

calibration solutions.

F.1.6.5 Correct

SDP_REQ-499 Correct



F.1.7 Image Plane Spectral Averaging

SDP_REQ-404 Image plane spectral averaging

The continuum pipeline shall perform cube averaging of frequency channels

post-imaging to avoid smearing effects and accommodate quality assessment.

SDP_REQ-405 Image plane averaging 2

The continuum pipeline shall provide optional re-projection of data.

F.1.8 Specify continuum pipeline

To specify the combinations of processing tasks and their parameters to be

done to produce continuum image cubes

F.1.9 Execute continuum pipeline

To execute processing tasks for continuum imaging

F.1.10 Continuum pipeline buffering

To store intermediate data products (visibilities and grids) during iterative

processing for continuum imaging.

SDP_REQ-618 Tranfer images from archive to buffer

The Data Layer shall be able to transfer image cubes from the science data

archive to the buffer for further processing.



delivery




products.







parallel.




Sky Model.



















system















infrastructure.

F.12.1.4 Monitoring










001.

F.1.11 Continuum pipeline data transport

To transport data between processing tasks of the continuum imaging

pipeline.

SDP_REQ-617 Restore images from archive to buffer

The SDP shall be able to restore image cubes from the science data archive to

the buffer in order to produce image cubes combining multiple cubes from

previously processed data.



delivery




products.






parallel.




Sky Model.




















system















infrastructure.

F.12.1.4 Monitoring









001.

F.1.12 Continuum Source Finding

SDP_REQ-507 Calibration Source Finding

The science analysis pipeline shall find the location of bright sources of

emission for use in the sky model.

F.1.12.1 Fast Point Source Detection

F.2 Spectral line Imaging

To make science-ready image cubes with high or moderate spectral resolution.





SDP_REQ-387 Spectral line emission pipeline

The SDP shall provide a Spectral Line Emission pipeline that constructs channel

cubes of spectral line emission either with continuum emission remaining or with

continuum emission removed.

SDP_REQ-388 Spectral line absorption pipeline

The SDP shall provide a Spectral Line Absorption pipeline that constructs channel

cubes of spectral line absorption with continuum sources removed.

SDP_REQ-467 Perform Imaging Pipeline Automatic QA

The Imaging Pipeline shall perform standardised, automated Quality Assessment of

Images along the axes of astrometry, photometry, radiometry, polarimetry, and

spectrometry.




point arithmetic.











































polarisation.




polarisation.




polarisation.




polarisation.
































antenna.








































Solution for pointing errors. It shall be possible to solve for and correct time- and

station-dependent pointing errors with accuracy and timescale limited by signal to

noise ratio.

SKA1-SYS_REQ-2336 Standard pipeline products.

Standard pipeline products. All pipelines shall include as data products the pipeline

processing log, and Quality Assessment log.

SKA1-SYS_REQ-2341 Spectral line emission pipeline.

Spectral line emission pipeline. There shall be a Spectral Line Emission pipeline that

is optimised for constructing noise-limited (up to 1000h integration) channel cubes of

spectral line emission either with continuum emission remaining or with continuum

emission removed.

SKA1-SYS_REQ-2342 Spectral line emission data products.

Spectral line emission data products. The data products shall include spectral line

cube image, continuum model images, sensitivity image, and representative point

spread function.

SKA1-SYS_REQ-2343 Spectral line absorption pipeline.

Spectral line absorption pipeline. There shall be a Spectral Line Absorption pipeline

that is optimised for constructing noise-limited channel cubes of spectral line

absorption with continuum sources removed.

SKA1-SYS_REQ-2344 Spectral line absorption data products.

Spectral line absorption data products. The data products shall include spectral line

cube image, continuum model images, sensitivity image, and representative point

spread function.


Aperture Array DDE . There shall be a direction dependent model for the aperture

array primary beam to be used in calibration and imaging.





PAF DDE. There shall be a direction dependent model for the dish phased array feed

sensitivity pattern to be used in calibration and imaging.





Calibration and imaging formalism. The Calibration and Imaging formalism shall be

based upon the Rau framework [14].















SKA1-SYS_REQ-???? Mosiacking

Waiting for the description from Bojan.













flagging.




















F.1.2 Store LSM



delivery




products.






parallel.




Sky Model.



















system
















infrastructure.

F.12.1.4 Monitoring









001.



F.1.4 Deconvolution



SDP_REQ-397 Imager























spectral line).






spectral line).

F.1.4.4 iFFT





F.1.4.5 De-gridding









effect).








F.1.4.7 Gridding










effect).




F.1.4.8 FFT










spectral line).

F.2.5 Initial Calibration (high spectral resolution)

To apply correction for known instrumental or atmospheric effect that are

relevant at high spectral resolution

F.2.6 Calibration (high spectral resolution)

To solve for instrumental or atmospheric effects relevant at high spectral

resolution by comparing model and observed data

F.2.7 Spectral Line Source Finding

To estimated a spectral-line model for the sky a residual spectral cube by

image-plane deconvolution

F.2.8 Spectral line pipeline buffering


processing for spectral line imaging.






delivery




products.






parallel.





Sky Model.



















system















infrastructure.

F.12.1.4 Monitoring










001.

F.2.9 Spectral line pipeline data transport

To transport data between processing tasks of the spectral line pipeline.



delivery




products.






parallel.




Sky Model.




















system















infrastructure.

F.12.1.4 Monitoring









001.

F.2.10 Postage Stamp Selection

SDP_REQ-600 Postage Stamp Selection

The spectral line pipelines shall be able to image multiple pre-determined

areas smaller than the full field of view within a single pointing.

F.2.10.1 uv Plane Averaging

SDP_REQ-395 Additional Visibility Averaging

The continuum pipeline shall perform optional additional visibility

averaging to reduce computational load.



F.2.10.2 Phase Rotation

SDP_REQ-448 Phase Rotation

The spectral line pipelines shall rotate the visibility phase centre to a

given direction within the field of view.


F.2.11 Continuum Subtraction

Continuum subtraction on full resolution spectral cubes

SDP_REQ-601 Continuum Subtraction

The spectral line pipelines shall have the ability to remove continuum

structure based on the products of the continuum imaging pipeline.

F.2.12 Specify spectral line pipeline

To specify the combinations of processing tasks and their parameters for

producing spectral line data products

F.2.13 Execute spectral line pipeline

To execute processing tasks for spectral line imaging

F.3 Ingest Data

To receive, store or forward data from CSP (and other sources) and prepares data for

further processing. (This will satisfy requirements for doing EoR).





The SDP shall process data from the SKA1_Survey FoV including the 36 ASKAP

antennas including both monitor and control and data collection functions.




point arithmetic.






Continuum and spectral line imaging mode. All three SKA1 telescopes shall be

capable of operating in a Continuum and Spectral-line imaging mode concurrently.

SKA1-SYS_REQ-2133 Mode transition

Mode transition. The switching time between telescope operating modes shall take

less than 30 seconds (not including antenna slewing time)




















SKA1-SYS_REQ-2150 SKA1_Low correlator Integration rate.

SKA1_Low correlator Integration rate . T he SKA1_Low correlator for each sub array

shall have independently configurable visibility integration periods in the range 6s to

0.6s.




















polarisation.




polarisation.




polarisation.




polarisation.









SKA1-SYS_REQ-2197 SKA1_Mid correlator integration rate.

SKA1_Mid correlation integration period. The SKA1_Mid shall have independently

configurable visibility integration period from a maximum integration time of 0.8s to

a minimum of 0.08s for each subarray.
























antenna.



















SKA1-SYS_REQ-2264 SKA1_Survey sub-arraying.

SKA1_Survey sub-arraying. It shall be possible to split the SKA1_Survey array into

independent operable ASKAP and SKA1 dish sub-arrays.





SKA1-SYS_REQ-2285 Latency of TOO scheduling block initiation.

Latency of TOO scheduling block initiation . Scheduling intervention on TOO

triggers shall be initiated within 1s of receiving the trigger.

SKA1-SYS_REQ-2286 Discard previous scheduling block.

Discard previous scheduling block . At the launching of a TOO Scheduling Block, the

results from any active Scheduling Blocks shall be discarded.


















Role of science processing centres. The science-processing centre will convert the

output data from the CSP into science data products to be stored in the science data

archive.

SKA1-SYS_REQ-2472 RFI flagging

RFI flagging. The SKA1 telescopes shall automatically flag frequency data with a

resolution of one channel and time data to the resolution of the integration unit if the

data is corrupted by RFI.

SKA1-SYS_REQ-2473 RFI excision


RFI excision. The SKA1 Telescopes shall automatically excise data that is corrupted

by RFI.

SKA1-SYS_REQ-2474 RFI masking

RFI masking. The SKA1 Telescopes shall flag data according to a pre-selected RFI

Mask.

SKA1-SYS_REQ-2640 Clipped Data Flagging

Clipped data flagging. Clipped data shall be flagged accordingly within the data

stream .




F.3.1 Integrate in time and frequency

SDP_REQ-502 Ingest Pipeline

The SDP shall have an ingest pipeline to condition the input data.

SDP_REQ-526 Average Input Data In Time

Pulsar Timing Post Processing shall be able to average input data in time using

a weighted sum of sub-integrations with precomputed weights.

F.3.1.1 Send (u,v) data to Calibration function

F.3.1.2 Compress

F.3.1.3 Integrate in time and frequency (base-line dependant)

SDP_REQ-480 Integrate Data

The SDP shall be capable of integrating data in time and/or frequency.

F.3.1.4 Transpose, reorder













flagging.




















F.3.2 Receive and buffer (u,v) data

SDP_REQ-301 SDP ingest data rate

The SDP system shall ingest CSP data at TBD Gbps, while losing less than

TBD% (0.01%?) of the data.

SDP_REQ-470 Receive Data

The SDP shall receive the data packets from CSP in compliance with the CSP-

SDP ICD.

SDP_REQ-496 Set Weight

The Ingest Pipeline shall set the correct data weights

F.3.2.1 Buffer (u,v) data ~0.5s

SDP_REQ-471 Buffer Data

The Ingest Pipeline shall be capable of buffering the input data for the

purpose of receiving and aligning data from the CSP.

F.3.2.2 Receive (u,v) data from CSP



delivery




products.






parallel.




Sky Model.




















system















infrastructure.

F.12.1.4 Monitoring









001.


F.3.3 Handle missing and out of order packets

F.3.3.1 Detect missing packets

SDP_REQ-472 Handle Missing Data

The SDP shall be capable of handling missing data packets coming

from CSP.

SDP_REQ-483 Missing Data

The HandleMissingData step will be able to detect missing data

packets

F.3.3.2 Order (u,v) data over time

SDP_REQ-482 Order UV Data

The ingest pipeline will be able to order (u,v) data over time.

F.3.5 Merge Metadata from TM

F.3.5.1 Input Metadata from TM

SDP_REQ-484 Input Meta Data

The ingest pipeline will be capable of ingesting metadata from the

Telescope Manager.

F.3.5.2 Merge missing packet info with TM metadata

SDP_REQ-473 Merge Meta Data

The SDP shall merge the metadata stream from the Telescope Manager

with the data stream from CSP.

F.3.6 Strong source removal

SDP_REQ-479 Remove Sources

The SDP shall be capable of removing strong sources at high data resolution.

F.3.7 Receive and Apply Initial Calibration (optional)

Optional. Only needed if initial calibration needs to be one on full resolution

data (related to F.5.1 Initial calibration).




Model.

SDP_REQ-615 EoR Calibration Pipeline

The SDP shall provide a calibration pipeline for EoR purposes.

F.3.8 Phase Rotation

F.3.9 Partial gather and transpose

F.3.9.1 transpose data

SDP_REQ-475 Transpose Data

The ingest pipeline shall be capable of transposing data.

F.3.9.2 Combine time, frequency channels, baselines & polarisation

SDP_REQ-474 Gather Data

The ingest shall be capable of gathering data

SDP_REQ-485 Combine Data

The ingest pipeline shall be able to combine data based on time,

frequency channels, baselines and polarisation.


F.3.10 Specify Ingest Pipeline

To specify the combinations of processing tasks and their parameters for

ingesting data.

F.3.11 Execute Ingest Pipeline

To execute processing tasks for ingesting data.

F.4 Real-time Calibration

To calculate calibration parameters in real-time for other elements of the SKA.




point arithmetic.











telescope parameters using a recent observation and a Global Sky Model, either a

known GSM or the most recent GSM.


Calibration update rate. Calibration measurements shall be necessary at a rate of no

more than 10seconds.

F.1.6.2 Predict


The calibration pipeline shall produce visibilities by taking as input the local

sky model and instrument models.

F.1.6.1 Solve


The calibration pipeline shall fit model parameters for the instrumental and or

sky models taking observed and predicted visibilities as input.

F.1.6.5 Correct

SDP_REQ-499 Correct

The calibration pipeline shall be able to correct for direction independent

effects.








The calibration pipeline shall be able to subtract observed and predicted

visibilities from each other.

F.5 Drift Scan Imaging

A technique which involves a continuously changing pointing centre and step-wise

changing phase centres, with the whole field then jointly deconvolved.




point arithmetic.

SKA1-SYS_REQ-???? Drift Scan Imaging

Waiting for the description from Bojan













flagging.




















F.1.2 Store LSM



delivery




products.






parallel.




Sky Model.



















system
















infrastructure.

F.12.1.4 Monitoring









001.



F.1.4 Deconvolution



SDP_REQ-397 Imager























spectral line).






spectral line).

F.1.4.4 iFFT





F.1.4.5 De-gridding









effect).








F.1.4.7 Gridding









effect).





F.1.4.8 FFT










spectral line).

F.1.5 Initial Calibration (averaged data)

Initial calibration is already done in the ingest pipeline on full resolution data.

This function exists in case initial calibration needs to be done on averaged

data.




Model.

F.1.6.5 Correct

SDP_REQ-499 Correct



F.1.6 Calibration

Skip this step the first time its executed. (this is not shown in the diagram to

reduce complexity)


The SDP shall use a Local Sky Model, derived from a Global Sky Model or

previous Local Sky Model.

SDP_REQ-412 SKA1_Survey spectral dynamic range.

The SDP contribution to the spectral dynamic range for SKA1_Survey shall

be better than TBD between adjacent channels and TBD globally.




Model.

SDP_REQ-424 Polarisation purity.

The SKA1_low station beams shall have a polarisation purity at the zenith

better than TBD after calibration.

SDP_REQ-430 Flux scale

The SDP shall preserve the absolute flux scale provided by the global sky

model.



The SDP shall process data from the SKA1_Survey FoV including the 36

ASKAP antennas including both monitor and control and data collection

functions.

SDP_REQ-441 Automated Quality Assessment.

The SDP shall perform standardised, automated Quality Assessment of Images

along the axes of astrometry, photometry, radiometry, polarimetry, and

spectrometry.

SDP_REQ-442 Astrometric performance metric

The SDP Astrometric performance metric (APM) shall measure deviation

(rms, average offset, and med) of source positions from known standards.

SDP_REQ-443 Photometric performance metric

The SDP Photometric performance metric (PPM) shall measure deviation

(rms, average offset, and med) of source fluxes from known standards.

SDP_REQ-444 Radiometric performance metric

The SDP Radiometric performance metric (RPM) shall measure noise

fluctuations (rms, average offset, and med) in an Image..

SDP_REQ-445 Polarimetric performance metric

The SDP Polarimetric performance metric (OPM) shall measure deviation

(rms, average offset, and med) of source polarisations (polarisation degree and

angle) from known standards.

SDP_REQ-446 Spectrometric performance metric

The SDP Spectrometric performance metric (SPM) shall measure deviation

(rms, average offset, and med) of source spectral lines from known standards.

SDP_REQ-466 Perform Calibration Pipeline Automatic QA

The Calibration Pipeline shall perform standardised, automated Quality



SDP_REQ-500 Self-calibration loop

The continuum pipeline shall be able to perform self-calibration in order to

achieve noise-limited performance.

SDP_REQ-536 Pulsar Timing Polarisation Calibration

Pulsar Timing Post Processing shall apply polarisation calibration parameters


SDP_REQ-553 Pulsar Timing Flux Calibration

Pulsar Timing Post Processing shall apply flux calibration parameters





concurrently.

SKA1-SYS_REQ-2158 Pointing repeatability.


seconds rms for winds < 7 m/s at night time.


SKA1-SYS_REQ-2159 Pointing repeatability - Low wind / day time

Pointing repeatability . The pointing repeatability shall be better than 17 arc

seconds rms for an average wind speed of < 7 m/s in the day time

SKA1-SYS_REQ-2160 Pointing repeatability - Higher wind


seconds rms for an average wind speed between 7 and 20 m/s





Manager.


SKA1_Survey number of beams. The SKA1_Survey shall beam-form the

element signals in each band to provide 36 full bandwidth, dual polarisation

beams per antenna.


SKA1_Survey imaging dynamic range Ã¢â‚¬â€œ band 1. The SKA1_Survey

array shall have an imaging dynamic range of greater than:band 1: 55dB for a

1000 hour single-field integrationband 2: 56dB for a 1000 hour single-field

integrationband 3: 54dB for a 1000 hour single-field integration.









Closed loop calibration. The telescope calibration shall be solved by

comparison of observed with GSM predictions with a time scale appropriate to

the component and physical effect being calibrated and fed back to the

telescope.


Direction dependent effects. Self-calibration and image reconstruction

algorithms shall be capable of dealing with direction dependent effects.





Multi-frequency synthesis imaging . All imaging shall construct and make use

of frequency dependent image models over the entire observed bandwidth.


Solution for pointing errors. It shall be possible to solve for and correct time-

and station-dependent pointing errors with accuracy and timescale limited by




Peeling. Peeling of bright sources (strength limited by signal to noise ratio)

from the visibility data shall be possible.



telescope parameters using a recent observation and a Global Sky Model,

either a known GSM or the most recent GSM.

SKA1-SYS_REQ-2621 Spectral stability

Spectral stability: The spectral stability, on a time scale of 600 sec.,of the

station beam bandpass, post station calibration and RFI-mitigation, shall be

within 1.3 %, 0.4 %, 0.6 % and 1.1 % at 50 MHz, 100 MHz, 160 MHz, and

220 MHz respectively compared to the full polarization, parameterized beam

model.

SKA1-SYS_REQ-2629 Station beam stability

Station beam stability. The difference between the parameterized station beam

model and the actual station beam shall remain smaller than 1.3 %, 0.4 %, 0.6

% and 1.1 % relative to the main beam peak power, after calibration, at 50

MHz, 100 MHz, 160 MHZ and 220 MHz respectively


Calibration update rate. Calibration measurements shall be necessary at a rate

of no more than 10seconds.

SKA1-SYS_REQ-2635 Real time calibration

Real-time calibration. The LFAA reception system at station level shall

provide on-line instrumental calibration functions with an update rate of 10

minutes


Aperture Array DDE . There shall be a direction dependent model for the

aperture array primary beam to be used in calibration and imaging.


Faraday rotation DDE. There shall be a direction dependent Faraday Rotation

model for use in calibration and imaging.


PAF DDE. There shall be a direction dependent model for the dish phased

array feed sensitivity pattern to be used in calibration and imaging.


Dish DDE. There shall be a direction dependent model for the dish primary

beam to be used in calibration and imaging.


Calibration and imaging formalism. The Calibration and Imaging formalism

shall be based upon the Rau framework [14].












F.1.6.1 Solve


The calibration pipeline shall fit model parameters for the instrumental

and or sky models taking observed and predicted visibilities as input.

F.1.6.2 Predict


The calibration pipeline shall produce visibilities by taking as input the

local sky model and instrument models.



The calibration pipeline shall be able to subtract observed and

predicted visibilities from each other.





F.1.6.5 Correct

SDP_REQ-499 Correct



F.1.7 Image Plane Spectral Averaging

SDP_REQ-404 Image plane spectral averaging

The continuum pipeline shall perform cube averaging of frequency channels

post-imaging to avoid smearing effects and accommodate quality assessment.



F.1.8 Specify continuum pipeline

To specify the combinations of processing tasks and their parameters to be

done to produce continuum image cubes

F.1.9 Execute continuum pipeline

To execute processing tasks for continuum imaging

F.1.10 Continuum pipeline buffering


processing for continuum imaging.







delivery




products.






parallel.




Sky Model.



















system
















infrastructure.

F.12.1.4 Monitoring









001.

F.1.11 Continuum pipeline data transport

To transport data between processing tasks of the continuum imaging

pipeline.

SDP_REQ-617 Restore images from archive to buffer

The SDP shall be able to restore image cubes from the science data archive to

the buffer in order to produce image cubes combining multiple cubes from

previously processed data.



delivery




products.






parallel.




Sky Model.




















system















infrastructure.

F.12.1.4 Monitoring









001.







F.6 Science Analysis




SDP_REQ-469 Perform Science Analysis Pipeline Automatic QA

The Science Analysis Pipeline shall perform standardised, automated Quality






point arithmetic.





SKA1-SYS_REQ-2333 Continuum source finding.

Continuum source finding. Where appropriate, continuum source finding shall be

conducted on images generated by the Continuum Imaging pipeline. Polarization shall

be fitted if available.

SKA1-SYS_REQ-2334 Spectral line source finding.

Spectral line source finding. Where appropriate, spectral line source finding shall be

conducted on image cube generated by the Spectral Line pipeline.

SKA1-SYS_REQ-2335 Stacking.

Stacking. Where appropriate, spectral line stacking shall be conducted on image cubes

generated by the pipelines using a priori known source lists.

SKA1-SYS_REQ-???? Rotation Measure Synthesis

Placeholder requirement for RM synthesis.

F.6.1 Input Data Conditioning for Science Analysis

Interface to PIP.IMG

SDP_REQ-510 Science Analysis input data conditioning

The science analysis pipeline shall transform the images and cubes received

from the imaging pipelines into a form suitable for source detection and

characterisation.

F.6.1.1 Imaging Cube Gridding

SDP_REQ-520 Image Cube management

The science analysis pipeline shall transform image cubes so that each

frequency channel has consistent spatial scale.


F.6.1.2 Image Processing Cadence

SDP_REQ-521 Image Cadence management

The science analysis pipeline shall combine real time updates of

images to form a composite image for source detection and

characterisation.

F.6.2 Source Analysis

SDP_REQ-514 Source Analysis (TBC)

The science analysis pipeline shall analyse sources...... TBD

F.6.2.1 Rotation Measure Synthesis

F.6.2.2 Spectral Line Profile Determination (delete)

SDP_REQ-515 Spectral Line Profile Determination

The science analysis pipeline shall extract the profile of sources

detected in image cubes.

F.6.2.3 Spectral Index Determination (delete)

SDP_REQ-509 Spectral Index Determination

The science analysis pipeline shall calculate the spectral indices of

detected continuum sources.

F.6.3 Source Finding

To convert the sky model into a data product.

SDP_REQ-511 Continuum Source Finding

The science analysis pipeline shall perform continuum source finding.

F.6.3.1 Point Source Detection

SDP_REQ-518 Point Source Detection

The science analysis pipeline shall locate point sources within images.

F.6.3.2 Spectral Line Source Detection

SDP_REQ-516 Spectral Line Source Detection

The science analysis pipeline shall locate sources of spectral line

emission in image cubes.

F.6.3.3 Extended Source Detection

SDP_REQ-508 Extended Source Detection

The science analysis pipeline shall locate extended sources within

images.

F.6.4 Stacking

SDP_REQ-512 Stacking

The science analysis pipeline shall perform stacking. Details TBD.

F.6.4.1 Continuum Stacking

SDP_REQ-519 Continuum Stacking

The science analysis pipeline shall perform stacking of continuum

sources. Details TBD.

F.6.4.2 H1 Stacking

SDP_REQ-513 H1 Stacking

The science analysis pipeline shall perform stacking of spectral line

sources. Details TBD


F.7 Imaging Transient Search




SDP_REQ-389 Slow transient pipeline

The SDP shall provide a Slow Transient imaging pipeline that shall be capable of

constructing a continuum image after a GSM has been subtracted for every correlator

integration time or slower, searching for transient sources, and producing a time-

ordered catalog.




point arithmetic.





SKA1-SYS_REQ-2131 Transient search mode

Transient search mode . Each of the SKA1 telescopes shall be capable of operating in

a transient search mode TBC







































polarisation.




polarisation.




polarisation.




polarisation.
































antenna.










































SKA1-SYS_REQ-2345 Slow transient pipeline.

Slow transient pipeline. There shall be a Slow Transient imaging pipeline that shall be

capable of constructing a continuum image after a GSM has been subtracted for every

correlator integration time or slower, searching for transient sources, and producing a

time-ordered catalogue.

SKA1-SYS_REQ-2346 Slow transient data products.

Slow transient data products. The data products shall include a catalogue of found

sources, a sensitivity image, and representative PSF image.


















F.7.2 Generate Alert for Transients

To generate an alert that a transient has been observed.

F.1.4 Deconvolution



SDP_REQ-397 Imager























spectral line).






spectral line).

F.1.4.4 iFFT





F.1.4.5 De-gridding









effect).









F.1.4.7 Gridding









effect).




F.1.4.8 FFT










spectral line).






F.8 Non-Imaging Transient Post Processing

SDP_REQ-148 Non-imaging Transient Search Number of Beams

SDP, when in non-imaging transient search mode, shall be capable of performing

post-processing on up to a total of 2222 beams per observation.

SDP_REQ-468 Perform Non-Imaging Pipeline Automatic QA

The Non-Imaging Pipeline shall perform standardised, automated Quality Assessment

of [TBD]

SDP_REQ-532 Non-imaging Transient Post Processing

SDP shall be capable of operating in a non-imaging transient search mode,

concurrently with continuum imaging mode and periodicity search mode

F.8.1 Archive Transient Search Candidates

SDP_REQ-546 Non-imaging Transient Search Output


SDP shall output a single ranked list of non-imaging transient candidates from

each observation

SDP_REQ-562 Non-imaging Transient Search Archive Products

Pulsar Search Post Processing shall archive all non-imaging transient

candidates recieved from CSP.

F.8.2 Merge SPOCLDs from multiple beams

SDP_REQ-554 Identify Multi-beam Candidates (transients)

Pulsar Search Post Processing shall determine how many beams each non-

imaging transient candidate is detected in and add that information to the

candidate data stream.

SDP_REQ-563 Merge Data from Multiple Beams (transients)

Pulsar Search Post Processing shall combine non-imaging transient candidates

from all beams received from CSP.

F.8.3 Generation and extraction of candidate heuristics

SDP_REQ-545 Extract non-imaging transient heuristics

Pulsar Search Post Processing shall generate a set of heuristics that can be

used to assign a probability to each non-imaging transient candidate.

SDP_REQ-559 Extract pulsar search heuristics

Periodicity Search Post Processing shall generate a set of heuristics that can be

used to assign a probability to each pulsar candidate.

F.8.4 Candidate Selection

SDP_REQ-557 Periodicity Search List Products

Pulsar Search Post Processing shall output a single ranked list of pulsar

candidates from each observation with data content described by TBD [SDP

data archive description document]

SDP_REQ-566 Non-imaging Transient List Products


candidates from each observation with data content described by TBD [SDP

data archive description document]

F.8.5 Candidate Classification

SDP_REQ-547 Classify Candidates (pulsars)

Periodicity Search Post Processing shall classify pulsar candidates using a

classifier which achieves TBD values for false positives, false negatives,

accuracy, and ???

SDP_REQ-570 Classify Candidates (transients)

Pulsar Search Post Processing shall classify non-imaging transient candidates

using a classifier which achieves TBD values for false positives, false

negatives, accuracy and ???

F.8.6 Alert Generator

SDP_REQ-537 Response Rate for Pulsar Alerts

Preliminary alerts for pulsar discoveries shall be sent to the TM within 1 hour

of the candidate data having arrived at Pulsar Search Post Processing

SDP_REQ-541 False Alarm Rate for Pulsar Alerts


Pulsar Search Post Processing shall alert the telescope manager of the

discovery of a pulsar with an average false alarm rate of better than (TBD) 1

per day.

SDP_REQ-544 Non-imaging Transient Alerts

SDP shall provide preliminary alerts for the detection of fast transient events

within 10s (TBC) of the data containing that event arriving at SDP.

SDP_REQ-564 Response Rate for Non-imaging Transients

Preliminary alerts for non-imaging transient events shall be sent to the TM

within 10 seconds of the candidate data having arrived at Pulsar Search Post

Processing

SDP_REQ-568 False Alarm Rate for Non-imaging Transients


detection of a non-imaging transient event with an average false alarm rate of

better than (TBD) 1 per day.

F.9 Pulsar Timing Post Processing



of [TBD]





SKA1-SYS_REQ-2130 Pulsar Timing Mode.

Pulsar Timing Mode. The SKA1_mid telescope shall be capable of operating in a

Pulsar timing mode, concurrently with continuum imaging mode.

SKA1-SYS_REQ-2201 Beam-former sub-array support.

Beam-former sub-array support. The SKA1_Mid central beam-former shall be able to

form beams or more beams for one to sixteen sub-arrays independently and

concurrently.

SKA1-SYS_REQ-2207 Number of beams: Pulsar timing.

Number of beams: Pulsar timing. The SKA1_Mid central beam-former for Pulsar

timing shall be capable of forming up to 16 dual polarisation coherent beams in total

across all timing sub-arrays.

SKA1-SYS_REQ-2208 Beamformer S/N ratio: Pulsar timing

Beamforming S/N ratio: Pulsar timing. The SKA1_Mid for Pulsar timing shall have a

Signal to Noise ratio greater or equal to 98% of an ideal analogue beam former.

SKA1-SYS_REQ-2224 Frequency agility.

Frequency agility. The SKA1_Mid system shall, for each timing sub-array, be able to

change from observing in any frequency band, to observing in any other frequency

band in less than or equal to 30 seconds.

SKA1-SYS_REQ-2230 Multiple timings.

Multiple timings. The SKA Phase 1 shall be capable of timing up to 16 pulsars

simultaneously in total across all timing sub arrays .

SKA1-SYS_REQ-2231 Pulsar timing Dispersion Measure


Pulsar timing Dispersion Measure. The SKA1_Mid shall be capable of timing pulsars

with dispersion measures between 0 to 3000 pc cm -3 such that residual dispersive

smearing is less than 500 ns.




SKA1-SYS_REQ-2738 CSP to SDP Interface

CSP to SDP interface . The interface between CSP and SDP shall be compliant with

the SKA-TEL.SDP.SE-TEL.CSP.SE-ICD-001 Interface Control Document

SKA1-SYS_REQ-2830 SKA1_Mid Pulsar phase bin width

SKA1_Mid Pulsar phase bin width. The SKA1_Mid shall be capable of providing

pulsar phase bin widths with a time resolution of better than 10us.

F.9.1 Pulsar Timing ToA Determination

SDP_REQ-529 Pulsar Timing Precision

When provided with a suitable template, signal-to-noise and pulsar

parameters, SDP shall be able to measure the arrival time of a pulse with a

precision of 5ns

SDP_REQ-530 Pulsar Timing ToA Determinination

SDP shall be capable of determining the time-of-arrival of a pulse from pulsar

timing data

SDP_REQ-542 Pulsar Timing Error Estimation

SDP shall be able to estimate the uncertainty in the arrival time of a pulse to

better than 5%

SDP_REQ-543 Pulsar Timing Systematic Error

SDP shall introduce no more than 5ns systematic error in the time-of-arrival

determination.

F.9.2 Pulsar Timing Data Preparation

SDP_REQ-524 Pulsar Timing Input

SDP shall be capable of receiving pulsar timing data in accordance with the

SKA-TEL.SDP.SE-TEL.CSP.SE-ICD-001 Interface Control Document.




SDP_REQ-534 Pulsar Timing Data Preparation

SDP shall be capable of performing data pre-processing on pulsar timing data.

F.9.2.1 Data Receptor (Pulsar Timing)

SDP_REQ-548 Pulsar Timing Input Data Reception

Pulsar Timing Post Processing shall be able to receive at least 16

folded pulsar data streams per observation, from CSP

F.9.2.2 RFI mitigation

F.9.2.3 Calibration

F.9.2.4 Averaging

SDP_REQ-540 Average Input Data In Frequency To Given

Significance


Pulsar Timing Post Processing shall be able to average input data in

time to increase the significance metric of the input data per sub-

integration to a precomputed value

SDP_REQ-549 Dynamic Range When Averaging Pulsar Profiles

Pulsar Timing Post Processing shall use at least 32 bits of precision

when averaging

SDP_REQ-561 Average Input Data In Time To Given Significance


time to increase the significance metric of the input data per sub-band

to a precomputed value

SDP_REQ-569 Average Input Data In Frequency


frequency using a weighted sum of sub-bands with precomputed

weights

F.9.2.5 Archive products generated

F.9.2.6 Data Receptor (Pulsar Search)

SDP_REQ-528 Pulsar Search Data Input Data Reception

Pulsar Search Post Processing shall be able to receive pulsar candidates

and associated data from CSP.

F.9.2.7 Data Receptor (Non-Imaging Transient Search)

SDP_REQ-539 Non-imaging Transient Input

SDP shall be capable of receiving non-imaging transient search data in

accordance with the SKA-TEL.SDP.SE-TEL.CSP.SE-ICD-001

Interface Control Document.

F.9.3 Pulsar Timing Model Fitting




SDP_REQ-565 Pulsar Timing Model Fitting

SDP shall be capable of fitting a pulsar timing model to pulsar times-of-arrival

F.9.3.1 Generate Residual

SDP_REQ-531 Generate Residual Output

Pulsar Timing Post Processing shall output residuals for each profile

from each observed pulsar.

SDP_REQ-551 Generate Residual Precision

Pulsar Timing Post Processing shall be able to compute the difference

(residual) between the measured arrival time of a pulse and that

predicted by a pulsar timing model without increasing the error budget

by more than 1 ns.

F.9.3.2 Append residuals to update model

SDP_REQ-538 Form Covariance Matrix of Residuals

Pulsar Timing Post Processing shall estimate the covariance matrix of

the residuals using a provided model of the noise processes in the

residuals


SDP_REQ-550 Weighting Scheme for Pulsar Timing Model

Fitting

Pulsar Timing Post Processing shall use a covariance matrix to weight

the fit of the pulsar timing model.

SDP_REQ-555 Output of Pulsar Timing Model

Pulsar Timing Post Processing shall output an updated pulsar timing

model for each observed pulsar.

SDP_REQ-556 Update Timing Model

Pulsar Timing Post Processing shall compute an updated pulsar timing

model for each observed pulsar by performing a generalised fit to the

computed residuals, including those extracted from the archive that

have been computed from previous observations.

F.10 Pulsar Search Post Processing

To sieve pulsar candidates to find confirmed pulsars.



of [TBD]





SKA1-SYS_REQ-2129 Pulsar Search Mode.

Pulsar Search Mode . The SKA1_mid telescope shall be capable of operating in a

Pulsar search mode, concurrently with Continuum imaging mode.

SKA1-SYS_REQ-2131 Transient search mode

Transient search mode . Each of the SKA1 telescopes shall be capable of operating in

a transient search mode TBC

SKA1-SYS_REQ-2201 Beam-former sub-array support.

Beam-former sub-array support. The SKA1_Mid central beam-former shall be able to

form beams or more beams for one to sixteen sub-arrays independently and

concurrently.

SKA1-SYS_REQ-2203 Number of beams: Pulsar search

Number of beams: Pulsar search. SKA1_Mid, when performing the Pulsar Search

function, shall simultaneously form up to a total of 2222 beams per observation across

all sub arrays .

SKA1-SYS_REQ-2205 Beamformer S/N pulsar search

Beamformer S/N pulsar search. The SKA1_Mid central beam-forming for each sub

array shall have a Signal to Noise ratio greater or equal to 98% of ideal analogue

beam forming for the same sub array:

SKA1-SYS_REQ-2216 Time resolution

Time resolution. The time resolution of the SKA1_Mid pulsar search processing for

each sub-array shall be equivalent to the temporal smearing due to dispersion at the

observation frequency and bandwidth of the observation with a quantisation of value

in powers of 2 from 50 Ã‚Âµs to 800 us


SKA1-SYS_REQ-2220 Binary search

Binary search. For each Pulsar search sub-array within SKA1_Mid the processing

shall be capable of searching for binary systems with accelerations due to their orbital

motion of up to 350 ms -2 .




SKA1-SYS_REQ-2616 SKA1_Mid Pulsar phase binning

SKA1_Mid Pulsar phase binning. The SKA1_Mid, for each subarray, shall allow for

pulse phase-resolved observations supporting the product of the number of phase bins,

channel and polarisation products up to 1,000,000 (i.e. 4 x 256,000).

SKA1-SYS_REQ-2738 CSP to SDP Interface

CSP to SDP interface . The interface between CSP and SDP shall be compliant with

the SKA-TEL.SDP.SE-TEL.CSP.SE-ICD-001 Interface Control Document




F.9.1 Pulsar Timing ToA Determination

SDP_REQ-529 Pulsar Timing Precision

When provided with a suitable template, signal-to-noise and pulsar

parameters, SDP shall be able to measure the arrival time of a pulse with a

precision of 5ns

SDP_REQ-530 Pulsar Timing ToA Determinination

SDP shall be capable of determining the time-of-arrival of a pulse from pulsar

timing data

SDP_REQ-542 Pulsar Timing Error Estimation

SDP shall be able to estimate the uncertainty in the arrival time of a pulse to

better than 5%

SDP_REQ-543 Pulsar Timing Systematic Error

SDP shall introduce no more than 5ns systematic error in the time-of-arrival

determination.

F.10.1 Periodicity Search Post Processing

SDP_REQ-133 Periodicity Search Post Processing

SDP shall be capable of operating in a periodicity search mode, concurrently

with continuum imaging mode and non-imaging transient search mode.

SDP_REQ-147 Periodicity Search Number of Beams

SDP when in pulsar search mode, shall be capable of performing post-

processing on up to a total of 2222 beams per observation

SDP_REQ-527 Pulsar Search Data Input

SDP shall be capable of receiving pulsar periodicity search data in accordance

with the SKA-TEL.SDP.SE-TEL.CSP.SE-ICD-001 Interface Control

Document.

SDP_REQ-535 Non-imaging Transient Input Data


Pulsar Search Post Processing shall be able to receive non-imaging transient

candidates and associated data from CSP.

SDP_REQ-552 Periodicity Search Alerts

SDP shall provide alerts for the probable discovery of pulsars within a TBD

timeframe of data potentially containing that pulsar arriving at the SDP.

SDP_REQ-558 Periodicity Search Output

SDP shall output a single ranked list of pulsar periodicity candidates from

each observation.

F.8.4 Candidate Selection

SDP_REQ-557 Periodicity Search List Products


candidates from each observation with data content described by TBD

[SDP data archive description document]

SDP_REQ-566 Non-imaging Transient List Products


candidates from each observation with data content described by TBD

[SDP data archive description document]

F.10.1.6 Archive Periodicity Search Candidates

SDP_REQ-567 Periodicity Search Archive Products

Pulsar Search Post Processing shall archive all periodicity search

candidates recieved from CSP.

F.8.6 Alert Generator

SDP_REQ-537 Response Rate for Pulsar Alerts

Preliminary alerts for pulsar discoveries shall be sent to the TM within

1 hour of the candidate data having arrived at Pulsar Search Post

Processing

SDP_REQ-541 False Alarm Rate for Pulsar Alerts


discovery of a pulsar with an average false alarm rate of better than

(TBD) 1 per day.

SDP_REQ-544 Non-imaging Transient Alerts

SDP shall provide preliminary alerts for the detection of fast transient

events within 10s (TBC) of the data containing that event arriving at

SDP.

SDP_REQ-564 Response Rate for Non-imaging Transients

Preliminary alerts for non-imaging transient events shall be sent to the

TM within 10 seconds of the candidate data having arrived at Pulsar

Search Post Processing

SDP_REQ-568 False Alarm Rate for Non-imaging Transients


detection of a non-imaging transient event with an average false alarm

rate of better than (TBD) 1 per day.

F.8.3 Generation and extraction of candidate heuristics

SDP_REQ-545 Extract non-imaging transient heuristics


Pulsar Search Post Processing shall generate a set of heuristics that can

be used to assign a probability to each non-imaging transient

candidate.

SDP_REQ-559 Extract pulsar search heuristics

Periodicity Search Post Processing shall generate a set of heuristics

that can be used to assign a probability to each pulsar candidate.

F.8.5 Candidate Classification

SDP_REQ-547 Classify Candidates (pulsars)

Periodicity Search Post Processing shall classify pulsar candidates

using a classifier which achieves TBD values for false positives, false

negatives, accuracy, and ???

SDP_REQ-570 Classify Candidates (transients)

Pulsar Search Post Processing shall classify non-imaging transient

candidates using a classifier which achieves TBD values for false

positives, false negatives, accuracy and ???

F.10.1.1 Merge OCLDs from multiple beams

SDP_REQ-533 Merge Data from Multiple Beams

Pulsar Search Post Processing shall combine periodicity search

candidates from all beams received from CSP.

SDP_REQ-560 Identify multi-beam candidates

Pulsar Search Post Processing shall determine how many beams each

pulsar candidate is detected in and add that information to the

candidate data stream.

F.9.2 Pulsar Timing Data Preparation

SDP_REQ-524 Pulsar Timing Input

SDP shall be capable of receiving pulsar timing data in accordance with the

SKA-TEL.SDP.SE-TEL.CSP.SE-ICD-001 Interface Control Document.




SDP_REQ-534 Pulsar Timing Data Preparation

SDP shall be capable of performing data pre-processing on pulsar timing data.

F.9.2.1 Data Receptor (Pulsar Timing)

SDP_REQ-548 Pulsar Timing Input Data Reception

Pulsar Timing Post Processing shall be able to receive at least 16

folded pulsar data streams per observation, from CSP

F.9.2.2 RFI mitigation

F.9.2.3 Calibration

F.9.2.4 Averaging

SDP_REQ-540 Average Input Data In Frequency To Given

Significance


time to increase the significance metric of the input data per sub-

integration to a precomputed value


SDP_REQ-549 Dynamic Range When Averaging Pulsar Profiles

Pulsar Timing Post Processing shall use at least 32 bits of precision

when averaging

SDP_REQ-561 Average Input Data In Time To Given Significance


time to increase the significance metric of the input data per sub-band

to a precomputed value

SDP_REQ-569 Average Input Data In Frequency


frequency using a weighted sum of sub-bands with precomputed

weights

F.9.2.5 Archive products generated

F.9.2.6 Data Receptor (Pulsar Search)

SDP_REQ-528 Pulsar Search Data Input Data Reception

Pulsar Search Post Processing shall be able to receive pulsar candidates

and associated data from CSP.

F.9.2.7 Data Receptor (Non-Imaging Transient Search)

SDP_REQ-539 Non-imaging Transient Input

SDP shall be capable of receiving non-imaging transient search data in

accordance with the SKA-TEL.SDP.SE-TEL.CSP.SE-ICD-001

Interface Control Document.

F.9.3 Pulsar Timing Model Fitting




SDP_REQ-565 Pulsar Timing Model Fitting

SDP shall be capable of fitting a pulsar timing model to pulsar times-of-arrival

F.9.3.1 Generate Residual

SDP_REQ-531 Generate Residual Output

Pulsar Timing Post Processing shall output residuals for each profile

from each observed pulsar.

SDP_REQ-551 Generate Residual Precision

Pulsar Timing Post Processing shall be able to compute the difference

(residual) between the measured arrival time of a pulse and that

predicted by a pulsar timing model without increasing the error budget

by more than 1 ns.

F.9.3.2 Append residuals to update model

SDP_REQ-538 Form Covariance Matrix of Residuals

Pulsar Timing Post Processing shall estimate the covariance matrix of

the residuals using a provided model of the noise processes in the

residuals

SDP_REQ-550 Weighting Scheme for Pulsar Timing Model

Fitting

Pulsar Timing Post Processing shall use a covariance matrix to weight

the fit of the pulsar timing model.


SDP_REQ-555 Output of Pulsar Timing Model

Pulsar Timing Post Processing shall output an updated pulsar timing

model for each observed pulsar.

SDP_REQ-556 Update Timing Model

Pulsar Timing Post Processing shall compute an updated pulsar timing

model for each observed pulsar by performing a generalised fit to the

computed residuals, including those extracted from the archive that

have been computed from previous observations.

F.11 Update Global Sky Model

To calculate updates to the global sky model.

SDP_REQ-505 Global Sky Model Update

The continuum pipeline shall update the global sky model based on the current local

sky model.














F.12 Archiving

To archive science ready data products produced by the SKA.

SDP_REQ-271 Data Products

The archive shall support an extensible set of data products resulting from observing

modes and science cases, which include but are not limited to the following types:

Continuum imaging, spectral line emission and absorption, and slow transients. The

term support refers to the capability of ingesting, indexing, performing life cycle

management and redistributing data products based on their type.

SDP_REQ-281 Backup sites

All Science Archives shall have an off-line (e.g. tape) backup stored in a secure

location.

SDP_REQ-282 Backup Archive Retrieval

SDP shall support the retrieval of items from a backup archive to the full Science

Archive within 24 hours.

SDP_REQ-289 Archive lifetime.

The science data archives shall be designed to provide an archived data lifetime of not

less than 50 years from the start of archived observations.


SDP_REQ-290 Secure Archive Environment

The SDP will protect the data archives from security and environmental threats

SDP_REQ-57 Spectrum Archive Metadata

The Archive API shall deliver science archive metadata for TBD data products, that

is, as a minimum, consistent with the IVOA Standard Spectrum Data Model

(SpectrumDM). The SpectrumDM data model may be used to represent spectra, time

series data, segments of spectral energy distributions, and other spectral or temporal

associations.


Role of science processing centres. The science-processing centre will convert the

output data from the CSP into science data products to be stored in the science data

archive.

SKA1-SYS_REQ-2350 Mirror sites.

Mirror sites. All data within Science Archives shall have a secondary copy located

offsite in a secure location.

SKA1-SYS_REQ-2355 Data product provenance.

Data product provenance. An official data product shall have known, documented

provenance, and shall have been produced via SKA observations and processing.

SKA1-SYS_REQ-2358 Third party data products.

Third party data products. Third party data products shall not be admitted to the

archive.

SKA1-SYS_REQ-2360 Science data product archive policy.

Science data product archive policy. There shall be a policy, developed and

administered by Operations, governing which types and sizes of data products will be

retained in the archive and for how long.

SKA1-SYS_REQ-2361 Archive access.

Archive access. A telescope archive will be nominally open for access 24/7/365, with

no more than 24 hrs planned downtime per year. Unplanned downtime shall be

consistent with availability budget.

SKA1-SYS_REQ-2363 Archive lifetime.

Archive lifetime. The science data archives shall be designed to provide an archived

data lifetime of not less than 50 years from the start of archived observations.

SKA1-SYS_REQ-2364 Data migration plan.

Data migration plan. Operations shall maintain at all times and update yearly a current

data migration plan covering the contingency of moving from one archive platform to

another.

SKA1-SYS_REQ-2479 Archive security

Archive security. The observatory shall provide a secure environment for all its data

archives.

SKA1-SYS_REQ-2660 Backup archive retrieval

Backup archive retrieval . Backup archive items shall be retrievable to the full archive

from an alternate source within 24 hours

SKA1-SYS_REQ-2661 Backup archive user access conversion

Backup archive user access conversion. Users shall have access to the data of the

entire archive within one week following an incident.


SKA1-SYS_REQ-2688 Data access rights

Commensal Observing Data access rights. There shall be a documented data access

rights policy for commensal observing for data sets shared across projects.

SKA1-SYS_REQ-2728 Data migration design

Data migration design. The archive design shall support and facilitate migration from

one medium to another.

SKA1-SYS_REQ-2821 Archive

Archive. There shall be an archive for each telescope, located in the Science

Processing Centre, for storing selected science data products for subsequent access by

users according to science data access policy.


Manages and executes the logical data flow from CSP to the final delivery


There shall be a system of software systems that manages the data flow from

the reception of raw data from CSP to the delivery of science products.


The data layer manager of each SKA telescope and all sub-arrays shall be

capable of operating concurrently and independently. It shall be possible to

run additional instances of the data layer manager for other purposes such as:

commissioning, maintenance and simulation in parallel.





Role of science processing centres. The science-processing centre will convert

the output data from the CSP into science data products to be stored in the

science data archive.




There shall be a mechanism that automates the migration of data items

through the various life cycle states starting from the initial storage.

This shall entail the migration of data items between storage layers and

include backup copies until the data items become obsolete and are

deleted.


The lifetime of archived data shall not be limited by the lifetime of any

of the hardware and software components comprising the archive.

F.12.1.1.1 Aggregation

Accumulation of data objects into data products

SDP_REQ-252 Concurrent Workflows

The data layer manager shall concurrently generate data

products for multiple observing programs. It shall also support


a single observing program concurrently generating multiple

data products as well as a mix of both scenarios.

SDP_REQ-255 Tracing Data

It shall be possible to trace each data product in the archive

back to a scheduling block and an observing program.

Reversely, it shall be possible to either search by observing

program or scheduling block and to subsequently retrieve all or

part of the associated archived data. This includes relevant

logging and monitoring information as well as quality

assessment data collected during the observations and the

standard processing.

F.12.1.1.2 Replication of Data Objects

Copies Data Objects to or from an alternate source

SDP_REQ-260 Archive Backup

In case of data loss from the Science Archive it shall be

possible to restore the lost data items. Individual data products

shall be retrievable from a backup copy within 24 hours. The

backup mechanism shall support scheduled, as well as

incremental and full backup options.

SDP_REQ-261 Restoring Archive Operations of a failed

site

There shall be a mechanism to operate the archive from a

backup copy to meet a recovery time limit of 1 week,

independent of the total size of the archive.

SDP_REQ-283 Restore archive access

The SDP shall provide the capability to restore access to the

entire archive within one week following an incident.

F.12.1.1.3 Migration

Migration of data from one storage medium to another.

SDP_REQ-263 Data Migration Design

The data layer manager shall contain a data life cycle

management subsystem which shall incorporate mechanisms

for copying, moving and retiring whole physical volumes or

storage units.





SDP_REQ-269 Storage Technology Transition

A strategy for phasing in new storage technology, e.g. new

media types, and phasing out obsolete storage technology shall

be part of the data migration plan.

F.12.1.1.4 Retirement

Cleanup of expired, temporary data


SDP_REQ-256 Discard Scheduling Block

The system shall provide a mechanism for discarding the

results and associated data artefacts from a given active

scheduling while it is still processed and before the next

scheduling block starts.


Policy driven placement of data objects in tiered storage system


The data layer shall provide a load balancing optimisation of the data

locality based on the specific performance and I/O work load at

runtime.


There shall be a mass storage system that automatically moves data

between high-cost and low-cost storage media for optimised

performance

F.12.1.2.1 Transaction Management

Provision of data object integrity across storage tiers and

lifecycle states

SDP_REQ-383 Data Integrity

The data integrity of the hierarchical storage management

system shall be defined and maintained across the entire data

life-cycle.

F.12.1.2.2 Buffering

short-term storage of data objects


The Data Layer shall be able to transfer image cubes from the

science data archive to the buffer for further processing.

F.12.1.2.3 Data Product Storage

Long term storage of data products

F.12.1.2.4 Database Access

Persisting metadata and state information

SDP_REQ-250 DB Interface

There shall be a database interface providing transparent access

to both the telescope state repository and the persistent storage

database services.


Services and API interfaces providing middleware functionality to

other SDP elements.


The Data Service Layer ensures that data access shall be independent

of the physical schema of the underlying compute infrastructure.


F.12.1.3.1 Special Purpose Functions

Individual data services; for instance, consistent access to sky

models.

SDP_REQ-257 Sky Model Access

The data layer manager shall provide concurrent read access to

the local and global sky model. It shall also provide write

access for the purpose of refining the global sky model and

creating new local sky models.

F.12.1.3.2 Raw Data Reception

Receiving network packages from CSP and instantiating

respective data object.

F.12.1.3.3 Aborting/Resetting

Discard an incompletely processed scheduling block and free

allocated resources

SDP_REQ-256 Discard Scheduling Block

The system shall provide a mechanism for discarding the

results and associated data artefacts from a given active

scheduling while it is still processed and before the next

scheduling block starts.

F.12.1.4 Monitoring



System status information shall be made available in compliance with

the capabilities specified in SKA-TEL.SDP.SE-TEL.TM.SE-ICD-001.


Performance monitoring shall be compliant with the capabilities

specified in SKA-TEL.SDP.SE-TEL.TM.SE-ICD-001.

F.12.1.4.1 Load Measurement

gather application performance data

SDP_REQ-265 Continuous Performance Monitoring

Metrics



001.

F.12.1.4.2 Status Reporting

returns processing status





SDP_REQ-267 Availability Metric


The data layer manager's subsystems shall have a defined

metric for deriving the overall availability of a given runtime

configuration.

F.12.1.4.3 Alerting

generation of alerts under pre-defined conditions

SDP_REQ-384 Notification Event

Data services shall be capable of generating pre-defined

notification events such as alarms.

F.12.2 Product Ingest

Creation of science data product catalogue.

SDP_REQ-276 Data Product Provenance

A SDP data product shall have known, documented provenance, and shall

have been produced via SKA observations and processing.

SDP_REQ-574 Science Data Archive

The SDP shall provide an archive for each telescope, located in the Science

Processing Centre, for storing selected science data products for subsequent

access by users according to science data access policy.

F.12.2.1 Indexing

Generation of archival search index.

SDP_REQ-255 Tracing Data

It shall be possible to trace each data product in the archive back to a

scheduling block and an observing program. Reversely, it shall be

possible to either search by observing program or scheduling block and

to subsequently retrieve all or part of the associated archived data. This

includes relevant logging and monitoring information as well as

quality assessment data collected during the observations and the

standard processing.

SDP_REQ-578 Data Model Compliance

The science archive shall be loaded with TBD standard data model

compliant meta data for the purpose of discovery and characterization

of data products. IVOA data models shall be supported where

applicable

F.12.2.2 Branding/Provenance

Population of archival metadata schema

SDP_REQ-254 Provenance

All data products stored in the Science Archive shall contain

provenance information. Science archive users shall be able to use this

provenance information to unambiguously reference data products in

publications.

F.12.3 Archive Access

science archive data access

SDP_REQ-262 Data Layer Product Distribution


The SDP shall provide an internal interface to allow access to bulk data and

data contained in databases (from the science archive) in order to deliver data

products.

SDP_REQ-275 Remote Processing

It shall be possible to run the SDP software at Partner Facilities. TBC

SDP_REQ-573 Third party data products

The SDP shall not admit third party data products to the science data archive.


The SDP shall provide an archive for each telescope, located in the Science

Processing Centre, for storing selected science data products for subsequent

access by users according to science data access policy.

F.12.3.1 Metadata Service

Access to science archive metadata

SDP_REQ-523 Archive Database Service

The Data Layer shall provide a service to allow access to data

contained in databases in the science archive.

SDP_REQ-577 Decoupling real-time Ops

Access methods to the science data archive shall not impact the

performance of telescope operations such as science data product

ingest.

F.12.3.2 Data Product Service

Access to science data products

SDP_REQ-522 Archive Bulk Data Access Service

The Data Layer shall provide a service to allow access to bulk data

contained in the science archive.

SDP_REQ-576 Data Product Replication

The data layer shall provide an access method to science data products.

SDP_REQ-577 Decoupling real-time Ops

Access methods to the science data archive shall not impact the

performance of telescope operations such as science data product

ingest.

F.12.3.3 Access Control

Policy based access control to science data products

SDP_REQ-264 Access Rules

The Science Data Archive shall provide an operator interface that

allows the creation and subsequent maintenance of access rules based

on user role and product type.

SDP_REQ-270 Archive Security Traceability

Measures for protecting the data layer management system from

unauthorised access shall be documented for security auditing

purposes.

SDP_REQ-274 Single Sign-On

The Archive API shall provide single sign-on capability to science

archive users.


SDP_REQ-286 Levels of access to the archive

Access to the archive shall be either anonymous with correspondingly

limited capabilities or via SKA authentication and authorisation.


The SDP shall provide an archive for each telescope, located in the

Science Processing Centre, for storing selected science data products

for subsequent access by users according to science data access policy.

SDP_REQ-609 Release Status

The Science Data Archive shall have a release status for each data

product and the system shall support scheduled changes to this status

information.

SDP_REQ-610 Consistent Release State

The Science Data Archive shall provide methods for consistently

setting and updating the release status of shared data products in the

context of commensal observing.

SDP_REQ-611 User Roles

The Science Data Archive shall support an extensible list of defined

user roles for the purpose of authorisation.

SDP_REQ-612 Data Product Types

The Science Data Archive shall support an extensible set of data

product types.

SDP_REQ-613 Meta Access

The Science Data Archive shall have the ability to define access to

metadata and data products separately.

F.13 Regional Centre Interface

To provide an interface for data transfer between the SKA Science Data Archive and

Regional Centres.

SKA1-SYS_REQ-2366 Distribution of data products.

Distribution of data products. As limited by resource constraints, it will be possible to

deliver science data products to approved off-site facilities, which may be globally

distributed.

F.13.1 Data distribution policy

SDP_REQ-106 Product distribution

The Archive API shall provide the capability to control archive data product

distribution to a set of pre-determined destinations.

F.13.1.1 Maintain remote products

SDP_REQ-107 Identify distribution destination

The Archive API shall support the identification of a destination for

delivery of science data products.

F.13.1.1.1 Analyse Data

SDP_REQ-114 Analysis output storage

The RCs shall support the Archive API by providing storage

for the output of the science data analysis software.

SDP_REQ-127 RC Product Renewal


Changes in products shall cause the Archive API to trigger

changes to delivered data product copies.

F.13.1.1.2 Delete Remote Products

SDP_REQ-125 Trigger data removal

The Archive API shall trigger the removal of all copies of data

products when a TBD low-quality threshold is reached.

F.13.1.1.3 Update Remote Products

SDP_REQ-126 Trigger data update

The Archive API shall trigger the delivery of an updated data

product to replace all copies when an archive data product is

updated at the SDP.

F.13.2 Bulk Data Transfer

SDP_REQ-262 Data Layer Product Distribution

The SDP shall provide an internal interface to allow access to bulk data and

data contained in databases (from the science archive) in order to deliver data

products.

F.13.2.1 WAN Interface

SDP_REQ-110 RC storage capacity

The RCs shall support the Archive API by providing a minimum of

TBD ?B of storage for archive data.

SDP_REQ-111 RC data transfer rate

The RCs shall support the Archive API by accommodating a data

transfer rate of TBD ?B/s.

SDP_REQ-112 RC storage rate

The RCs shall support the Archive API by providing storage that will

accumulate data at the TBD transfer rate.

SDP_REQ-113 RC analysis execution

The RCs shall support the Archive API by providing the execution of

science data analysis software.

SDP_REQ-114 Analysis output storage

The RCs shall support the Archive API by providing storage for the

output of the science data analysis software.

SDP_REQ-115 Metadata replication

The RCs shall support the Archive API by providing for the replication

of the metadata for the archive data products.

SDP_REQ-116 RC expected downtime

The RCs shall limit expected downtime to 5% (TBC).

SDP_REQ-117 RC unexpected downtime

The RCs shall limit unexpected downtime to 3% (TBC).

SDP_REQ-99 User Credentials Replication

The RCs shall support the Archive API by providing for the replication

of user credentials from the SDP.

F.13.2.2 Receive Data at Regional Centre

SDP_REQ-108 Delivery performance


The Archive API shall provide a transfer rate of TBD ?B/s for delivery

of data products.

SDP_REQ-109 Delivery interruption

The Archive API shall provide the capability to interrupt any or all

data deliveries.

F.13.2.3 Schedule data delivery

SDP_REQ-118 Delivery strategy

The Archive API shall schedule external data delivery.

F.13.2.3.1 Check previous deliveries

SDP_REQ-119 Delivery Count Limit

The Achieve API will limit the number of times failed transfers

are retried.

SDP_REQ-124 Delivery strategy data model

The Archive API shall track delivery strategy information for

data delivery and track which Data products s are transferred to

each RC.

F.13.2.3.2 Check Data Transfer budget

SDP_REQ-121 Data delivery budget

The Archive API data delivery scheduler shall identify capacity

by (TBC): 1 project; 2 user

SDP_REQ-122 High priority delivery

The Archive API shall support a default priority of urgent for

the delivery of the initial copy of a data product.

SDP_REQ-123 Low priority delivery

The Archive API shall deliver additional copies of data

products at the lowest priority.

F.13.2.3.3 Prioritise data for delivery

SDP_REQ-120 Data delivery priority

The Archive API data delivery schedule shall identify priorities

by (TBC): 1 product type; 2 project; 3 user

F.13.2.4 Send data to Regional Centre

F.13.2.5 Log Receiving data

SDP_REQ-98 User access log consistency

A log of user behavior (e.g. access history) will be kept by the

Delivery Platform which will be synchronized across geographically

distributed locations.

F.14 SKA Archive User Interface

To provide an interface for all outside parties to access and query the Science Data

Archive.

SKA1-SYS_REQ-2352 Web interface.

Web interface. The science data archives shall be accessible from the internet via a

standardised web interface.

SKA1-SYS_REQ-2353 Virtual Observatory interface.


Virtual Observatory interface. The science data archives shall be accessible via a set

of recommended IVOA services chosen to allow access to all approved data products.

SKA1-SYS_REQ-2354 Archive API.

Archive API. The science data archives shall publish a user accessible, open API in a

small number of complementary languages such as Python, C++, and Java.

SKA1-SYS_REQ-2361 Archive access.

Archive access. A telescope archive will be nominally open for access 24/7/365, with

no more than 24 hrs planned downtime per year. Unplanned downtime shall be

consistent with availability budget.

SKA1-SYS_REQ-2366 Distribution of data products.

Distribution of data products. As limited by resource constraints, it will be possible to

deliver science data products to approved off-site facilities, which may be globally

distributed.

SKA1-SYS_REQ-2482 Accessibility

Accessibility. It shall be possible to control on a per user basis which SKA1 facilities

and resources (both hardware and software) may be accessed by the user.

SKA1-SYS_REQ-2739 Levels of access to the archive

Levels of access . Access to the archive shall be either anonymous with

correspondingly limited capabilities or via SKA authentication and authorisation.

F.14.1 Authenticate and Authorise

SDP_REQ-274 Single Sign-On

The Archive API shall provide single sign-on capability to science archive

users.

SDP_REQ-571 Access to data and metadata

SDP shall provide authenticated users authorized access to proprietary

metadata and data.

F.14.1.1 Authorise User

SDP_REQ-90 Anonymous delivery

The Archive API shall implement anonymous delivery of TBD public

science archive metadata and data products.

SDP_REQ-94 User Authorisation

The Archive API shall implement authorized access to proprietary

science archive data for delivery.

F.14.1.1.1 Authorise User (Service)

SDP_REQ-277 User Defined Access Control

The SDP Delivery Platform shall provide a mechanism that

considers user-defined groups for authorised access.

SDP_REQ-95 Delivery by Role

The Archive API shall authorize role maintenance, metadata

description, metadata retrieval, and data delivery, by user role.

F.14.1.1.2 Authorise User (Client)

SDP_REQ-89 Federated authentication


The Archive API shall provide an interface to multiple static or

dynamic federated identity management mechanisms for

authenticating user credentials.

SDP_REQ-95 Delivery by Role

The Archive API shall authorize role maintenance, metadata

description, metadata retrieval, and data delivery, by user role.

SDP_REQ-97 Authorisation client

The SDP Delivery Platform shall provide a client that executes

the Archive API authorization facilities.

F.14.1.2 Authenticate User

SDP_REQ-88 User Authentication

The Archive API shall provide a mechanism to recognize

authentication credentials.

F.14.1.2.1 Authenticate User (Client)

SDP_REQ-89 Federated authentication

The Archive API shall provide an interface to multiple static or

dynamic federated identity management mechanisms for

authenticating user credentials.

SDP_REQ-91 Certificate Authentication

The Archive API shall support certificate-based credential

authentication.

F.14.1.2.2 Authenticate User (Service)

SDP_REQ-91 Certificate Authentication

The Archive API shall support certificate-based credential

authentication.

F.14.1.3 Maintain User Credentials

Add and remove users and groups.

SDP_REQ-101 Authentication provider list

The SDP shall support the Archive API by maintaining a reference to

a list of accredited identity providers.

F.14.1.3.1 Maintain User Credentials (Client)

SDP_REQ-100 Authorisation credential client

The SDP Delivery Platform shall provide a client that will

access the credential maintenance service.


The SDP shall support the Archive API by maintaining

classification of users by role.

F.14.1.3.2 Maintain User Credentials (Service)


The SDP shall support the Archive API by maintaining

classification of users by role.

F.14.1.3.3 Associate Identities

SDP_REQ-93 External Credentials


The Archive API shall support the linking of an external

authentication credential with an SKA authentication

credential.

F.14.1.4 Maintain user-defined groups

User maintenance of user-defined groups.

SDP_REQ-277 User Defined Access Control

The SDP Delivery Platform shall provide a mechanism that considers

user-defined groups for authorised access.

SDP_REQ-279 User-defined Group Management

The Delivery Platform will support collaboration by providing user-

defined group management.

F.14.2 Discover Data

SDP_REQ-130 VOEvent Delivery

The Archive API shall deliver archive VO event data (transient events) as

defined by the IVOA Standard for VO Event transport.

SDP_REQ-385 Web Interface

The SDP shall provide access to the science data archives from the internet via

a standardised web interface.

SDP_REQ-54 Archive Metadata

The SDP shall provide science archive metadata for the purpose of data

discovery.

SDP_REQ-55 ObsCore Archive Metadata

The Archive API shall deliver science archive metadata that is, as a minimum,

consistent with the IVOA Standard Observation Data Model Core

Components (ObsCoreDM). The ObsCoreDM defines the core components of

an Observation data model that are necessary to perform data discovery.

SDP_REQ-56 Image Archive Metadata

The Archive API shall deliver science archive metadata for multi-dimensional

data products that is, as a minimum, consistent with the proposed IVOA

Standard Image Data Model (ImageDM). The ImageDM is an ObsCoreDM

extension to describe multi-dimensional data, for handling data cubes.


The Archive API shall deliver science archive metadata for TBD data

products, that is, as a minimum, consistent with the IVOA Standard Spectrum

Data Model (SpectrumDM). The SpectrumDM data model may be used to

represent spectra, time series data, segments of spectral energy distributions,

and other spectral or temporal associations.

SDP_REQ-58 Data Discovery

The SDP shall provide science archive data discovery for the purpose of

delivery.

SDP_REQ-59 TAP Discovery

Science archive data discovery service shall, at a minimum, be searchable by

the IVOA Standard Table Access Protocol (TAP). TAP defines a service

protocol for accessing general table metadata and data. ObsCoreDM defines

the general table metadata.


SDP_REQ-60 SIA Discovery

The Archive API multi-dimensional image science archive data discovery

service shall, at a minimum, be searchable by the IVOA Standard Simple

Image Access (SIA) protocol?SIA-2.x. SIA provides capabilities for the

discovery of and access to detailed metadata for multi-dimensional image

datasets, including 2-D images as well as datacubes of three or more

dimensions.

SDP_REQ-62 Data Description

The SDP shall describe the science data archive metadata attributes and

relationships.

SDP_REQ-87 Archive Data File Formats

The Data Layer shall support the data visualisation by providing science data

products in TBD formats, such as CASA image, HDF5, and FITS file formats.

F.14.2.1 Visualise Query Results

SDP_REQ-73 Metadata Visualisation Client

The SDP Delivery Platform shall deliver science archive metadata for

web client visualisation.

SDP_REQ-74 HTTP Client Metadata Visualisation

The Delivery Platform shall deliver science archive metadata in the

IVOA Standard VOTable format for http client visualisation.The

VOTable format is an XML standard for the interchange of

astronomical data represented as a set of tables.

SDP_REQ-75 HTTP Client Previews

The SDP Delivery Platform shall provide previews (optimized sub-

sampling) of data for http client visualisation.

F.14.2.2 Select Data Products For Transfer

SDP_REQ-68 Delivery Client

The Delivery Platform Public Interface shall provide a client that

executes the Archive API DataLink and AccessData delivery facilities.

The client will execute externally to the SDP.

F.14.2.3 Query Authorised Data

SDP_REQ-66 DataLink Delivery

The Archive API shall deliver archive data products, VO data, and

public and outreach data as defined by the IVOA

Standard DataLink. The DataLink service supports linking of data

discovery metadata to detailed metadata, to the data itself, and to

standard and custom services that perform operations on the data

before delivery. The standard provides options to distinguish between

data products.

F.14.2.4 Filter By Authorisation

SDP_REQ-105 Proprietary data period

The Archive API shall enforce a TBD proprietary data period for

products from the science data archive and VO data, as observed for

one or many proposals.

F.14.2.5 Select Destination

SDP_REQ-107 Identify distribution destination


The Archive API shall support the identification of a destination for

delivery of science data products.

F.14.2.6 Query Authorised Metadata

SDP_REQ-103 Proprietary Period

The Archive API shall enforce a proprietary period for science data

archive and VO data, as observed for one or many proposals.

SDP_REQ-90 Anonymous delivery

The Archive API shall implement anonymous delivery of TBD public

science archive metadata and data products.

F.14.2.6.1 Append Authorisation Parameters to Query

SDP_REQ-104 Proprietary metadata period

The Archive API shall enforce a TBD proprietary metadata

period for products from the science data archive and VO data,

as observed for one or many proposals.

F.14.2.6.2 Query Metadata (Client)

SDP_REQ-61 Client Data Discovery


the Archive API TAP and SIA2.x discovery facilities. The

client will execute local to the user.

SDP_REQ-63 TAP Data Description


the Archive API TAP descriptive facilities to retrieve, as a

minimum, the ObsCoreDM-compliant description of the

science data archive metadata attributes and relationships. The


SDP_REQ-64 SIA Data Description


the Archive API SIA descriptive facilities to retrieve the

ObsCoreDM-compliant description of the science data archive

metadata attributes and relationships and the ImageDM-

compliant detailed metadata. The client will execute local to the

user.

SDP_REQ-77 VOEvent Data Description

The Data Delivery Platform shall provide a client that executes

the science archive VO Event Transport Protocol to retrieve, as

a minimum the Standard Sky Event Reporting Metadata model-

compliant description of the science data archive metadata

attributes and relationships, and the detailed metadata. The


F.14.2.6.3 Query Metadata (Service)

SDP_REQ-59 TAP Discovery

Science archive data discovery service shall, at a minimum, be

searchable by the IVOA Standard Table Access Protocol

(TAP). TAP defines a service protocol for accessing general

table metadata and data. ObsCoreDM defines the general table

metadata.


SDP_REQ-60 SIA Discovery

The Archive API multi-dimensional image science archive data

discovery service shall, at a minimum, be searchable by the

IVOA Standard Simple Image Access (SIA) protocol?SIA-2.x.

SIA provides capabilities for the discovery of and access to

detailed metadata for multi-dimensional image datasets,

including 2-D images as well as datacubes of three or more

dimensions.

SDP_REQ-61 Client Data Discovery


the Archive API TAP and SIA2.x discovery facilities. The


SDP_REQ-77 VOEvent Data Description

The Data Delivery Platform shall provide a client that executes

the science archive VO Event Transport Protocol to retrieve, as

a minimum the Standard Sky Event Reporting Metadata model-

compliant description of the science data archive metadata

attributes and relationships, and the detailed metadata. The


F.14.2.7 Condition metadata

SDP_REQ-55 ObsCore Archive Metadata

The Archive API shall deliver science archive metadata that is, as a

minimum, consistent with the IVOA Standard Observation Data Model

Core Components (ObsCoreDM). The ObsCoreDM defines the core

components of an Observation data model that are necessary to

perform data discovery.


The Archive API shall deliver science archive metadata for multi-

dimensional data products that is, as a minimum, consistent with the

proposed IVOA Standard Image Data Model (ImageDM). The

ImageDM is an ObsCoreDM extension to describe multi-dimensional

data, for handling data cubes.


The Archive API shall deliver science archive metadata for TBD data

products, that is, as a minimum, consistent with the IVOA Standard

Spectrum Data Model (SpectrumDM). The SpectrumDM data model

may be used to represent spectra, time series data, segments of spectral

energy distributions, and other spectral or temporal associations.

SDP_REQ-72 Metadata Conditioning

The SDP data model shall support the Archive API by conditioning

science data product metadata with the named VO standards.

SDP_REQ-92 VOEvent Data Model

The Data Delivery Platform shall deliver science archive metadata for

VO Events that is, as a minimum, consistent with the IVOA Standard

Sky Event Reporting Metadata model. The VOEvent DM is used to

describe transient celestial events.


F.14.3 Request Data Delivery

SDP_REQ-118 Delivery strategy

The Archive API shall schedule external data delivery.

F.14.4 Deliver Data to end user

SDP_REQ-65 Data Delivery

The Archive API shall deliver selected archive data products, VO data, and

public and outreach data according to specified standards to the end user.

F.14.4.1 Transfer Data to End User

SDP_REQ-273 Cut-outs

Support of cut-outs to deliver segments of Data Objects to end users.

SDP_REQ-67 AccessData Delivery

The Archive API shall deliver archive data products, VO data, and

public and outreach data as defined by the proposed IVOA Standard

AccessData in standard formats.

F.13.2.5 Log Receiving data

SDP_REQ-98 User access log consistency

A log of user behavior (e.g. access history) will be kept by the

Delivery Platform which will be synchronized across geographically

distributed locations.

F.14.5 Visualise data

SDP_REQ-131 Supported File Formats

The SDP Delivery Platform data visualization client shall visualize science

archive data in the following file formats:CASA images,HDF5 files, andFITS

files.


The Archive API shall deliver science archive metadata for multi-dimensional

data products that is, as a minimum, consistent with the proposed IVOA

Standard Image Data Model (ImageDM). The ImageDM is an ObsCoreDM

extension to describe multi-dimensional data, for handling data cubes.

SDP_REQ-76 Data Visualisation Client

The SDP Delivery Platform shall deliver science archive data for interactive

remote visualization, accessible through a standard web browser.

SDP_REQ-82 Maintain Visualization Session

The SDP DELIV PI data visualization client shall support the creation,

retrieval, modification, and deletion of visualization sessions.

F.14.5.1 Share Visualisation Session

SDP_REQ-81 Multi-User Viewing

The SDP Delivery Platform data visualization client shall allow

multiple users to interact with the same viewing session

simultaneously.

F.14.5.2 View Data with Core Functionality

SDP_REQ-78 Core viewing functionality

The SDP Delivery Platform data visualization client shall support, as a

minimum, the following viewing features: 1 pan; 2 zoom; 3 colormap

adjustments; 4 celestial coordinate system grid overlays; 5 multiple


image overlays; 6 switching frames; blinking i.e. manual or automatic

switching rapidly between different images, regions or frames.

F.14.5.3 View Data with Core analysis

SDP_REQ-128 Community Analysis

The SDP Delivery Platform data visualization service plug-in system

shall have the ability to execute community-provided code.

SDP_REQ-129 View Large Datasets

The SDP Delivery Platform data visualization shall run at interactive

speeds for large images (e.g. 1 TB TBC).

SDP_REQ-79 Extensible Analysis

The SDP Delivery Platform data visualization client shall provide a

plug-in system that will support the execution of data analysis software

as part of visualization.

SDP_REQ-80 Core Analysis Visualization

The SDP Delivery Platform data visualization client shall display, as a

minimum, analysis plug-ins for: 1 region statistics; 2 histograms; 3

spectrum calculators; 4 moment generators; 5 1D and 2D gaussian

fitting

F.14.5.4 Annotate Archive Data

SDP_REQ-132 Annotations

The SDP Delivery Platform data visualization client shall provide the

ability to create, retrieve, update, and delete annotations on individual

archive data products.

F.14.5.5 Automate Science analysis

SDP_REQ-86 Analysis API

The SDP Delivery Platform data visualization shall provide an API

that supports automation of the generation of analysis plots from

archive data.

F.14.5.6 Produce Science Analysis Products

SDP_REQ-85 Viewer Plot Save

The SDP Delivery Platform data visualization client shall support the

storage and retrieval of plots as high-resolution files generated during a

visualization session.

F.14.5.7 Log Data Access

SDP_REQ-96 Data access logging

The Archive API shall log science data product access by credential.

F.14.5.8 Customise Visualisation Environment

SDP_REQ-572 Display customisations

Maintain display customizations for web visualisation of science

archive metadata and data.

F.14.5.8.1 Customise User Display Defaults

SDP_REQ-83 User Visualization Customization

The SDP Delivery Platform data visualization client shall

support the maintenance of the following information, as a

minimum, for a user: 1 default toolbars; 2 default celestial


coordinate systems; toolbar customizations; plugin-specific

customizations; plot display attributes

F.14.5.8.2 Customise Visualisation Display

SDP_REQ-84 Viewer Customizable Plotting

The SDP Delivery Platform data visualization client shall

support customization options for plot display attributes.

F.15 SDP LMC

Provides local monitor and control functionality to the SDP as a whole. This involves

both the internal management of the SDP and the external interface to the Telescope

Manager.

F.15.1 Control

Provides for all aspects related to the control of the SDP, both externally from

TM and internally towards the SDP.

SDP_REQ-1 Mode handling

The SDP shall provide commands to the TM sufficient to support the various

telescope operating mode.

SDP_REQ-11 Frequency handling

The SDP shall support the transition from one frequency band of operation to

another within 30 seconds (TBD - need feedback on allocation of parent time

allowance).

SDP_REQ-2 Capability Handling

The SDP shall support the concept of capabilities via the LMC.

SDP_REQ-28 Precursor integration

The SDP LMC shall provide a uniform and singular point of control for the

SDP for all components of a particular telescope, including any precursor

infrastructure that may form part of the telescope.

SDP_REQ-285 Accessibility

The SDP shall make use of the central Authentication and Authorisation

facilities provided by the SKA to enable per user access to SDP resources.

SDP_REQ-29 Targets of Opportunity

The SDP shall provide a priority override mechanism to support scheduling

and execution of approved Target of Opportunity (ToO) events.

SDP_REQ-3 Observation Handling

The SDP shall support the concept of observations via the LMC.

SDP_REQ-33 Flagging control

The SDP shall allow the TM to control internal flagging, including the

definition of a pre-selected RFI mask, and other parameters as may be relevant

to particular flagging strategies.

SDP_REQ-50 Invalid input handling

The SDP shall be robust against input errors including invalid state, improper

authorisation, and malformed or malicious commands.

SDP_REQ-51 Engineering Support

The SDP shall provide engineering support functions to the relevant

Engineering Operations centres.


SDP_REQ-52 Failsafe

The SDP shall actively ensure that internal failures do not result in a

hazardous situation to the systems and personnel with which it interfaces.

SDP_REQ-602 Invalid Input Handling - Master Controller

The Master Controller shall be robust against input errors including invalid

state, improper authorisation, and malformed or malicious commands.

SDP_REQ-604 MeerKAT integration

The Master Controller shall provide a uniform and singular point of control for

the SDP for all components of the MeerKAT telescope, including any

precursor infrastructure that may form part of the MeerKAT telescope.

SDP_REQ-605 ASKAP integration

The Master Controller shall provide a uniform and singular point of control for

the SDP for all components of the ASKAP telescope, including any precursor

infrastructure that may form part of the ASKAP telescope.

SDP_REQ-606 Receive observation request

The Master Controller shall receive requests for observations from the

Telescope Manager.

SDP_REQ-607 Flagging control - LMC

The Master Controller shall receive flagging parameters from the Telescope

Manager and instruct the Calibration Pipeline to apply these flagging

parameters.

SDP_REQ-608 Engineering Support - Master Controller

The Master Controller shall provide engineering support functions to the

relevant Engineering Operations centres.

SDP_REQ-7 Observation Control

The SDP shall provide commands to control a previously scheduled

observation.

SKA1-SYS_REQ-2126 Simultaneous operation of telescopes

Simultaneous operation of telescopes. All three telescopes shall be capable of

operating concurrently and independently.




concurrently.

SKA1-SYS_REQ-2129 Pulsar Search Mode.

Pulsar Search Mode . The SKA1_mid telescope shall be capable of operating

in a Pulsar search mode, concurrently with Continuum imaging mode.

SKA1-SYS_REQ-2130 Pulsar Timing Mode.

Pulsar Timing Mode. The SKA1_mid telescope shall be capable of operating

in a Pulsar timing mode, concurrently with continuum imaging mode.

SKA1-SYS_REQ-2133 Mode transition

Mode transition. The switching time between telescope operating modes shall

take less than 30 seconds (not including antenna slewing time)






Manager.

SKA1-SYS_REQ-2224 Frequency agility.

Frequency agility. The SKA1_Mid system shall, for each timing sub-array, be

able to change from observing in any frequency band, to observing in any

other frequency band in less than or equal to 30 seconds.





SKA1_Survey single array operation . SKA1-Survey shall be capable of

operating ASKAP and SKA1 dishes as single array for frequency band 2.





SKA1-SYS_REQ-2282 Central location for data bases

Central location for data bases. External sources of information used by the

Elements shall be cached by Telescope Manager. No sources other than those

cached by TM shall be used.

SKA1-SYS_REQ-2283 Target of opportunity

Target of opportunity. TOO observing shall be via Scheduling Blocks.

SKA1-SYS_REQ-2285 Latency of TOO scheduling block initiation.

Latency of TOO scheduling block initiation . Scheduling intervention on TOO

triggers shall be initiated within 1s of receiving the trigger.

SKA1-SYS_REQ-2286 Discard previous scheduling block.

Discard previous scheduling block . At the launching of a TOO Scheduling

Block, the results from any active Scheduling Blocks shall be discarded.

SKA1-SYS_REQ-2312 Alarm latency.

Alarm latency. Latency from event to alarm shall be no more than 5 seconds.


Standard pipeline products. All pipelines shall include as data products the

pipeline processing log, and Quality Assessment log.

SKA1-SYS_REQ-2355 Data product provenance.

Data product provenance. An official data product shall have known,

documented provenance, and shall have been produced via SKA observations

and processing.

SKA1-SYS_REQ-2357 QA annotation.

QA annotation. The telescope shall facilitate the addition of QA annotations

by Users.

SKA1-SYS_REQ-2474 RFI masking


RFI masking. The SKA1 Telescopes shall flag data according to a pre-selected

RFI Mask.

SKA1-SYS_REQ-2788 Non-propagation of failures

Non-propagation of failures . The equipment shall be designed such that

hardware failures and software errors should not create a hazardous situation

to interfacing systems.


SKA1_Mid inclusion of MeerKAT. The SKA1_Mid shall incorporate the 64

antennas in both monitor and control and data collection functions.

F.15.1.1 Manage LMC Instances

Services to manage and maintain parallel instances of various aspects

of the LMC sub-element, principally to enable sub-array capabilities.

Part of the master controller.

SDP_REQ-25 Independent Operations

LMC functions should be able to operate concurrently and with

performance which is independent of other LMC instances

SDP_REQ-26 Resource sharing

The Master Controller shall ensure that any shared resources between

SDP instances on different telescopes do not compromise the ability of

the instance to act concurrently and independently.


Sub-Arraying. All of the SKA1 telescopes shall be capable of

operating independently with one to sixteen sub-arrays (i.e. collecting

area is split and allocated to separate, concurrently observing

programmes).

SKA1-SYS_REQ-2230 Multiple timings.

Multiple timings. The SKA Phase 1 shall be capable of timing up to 16

pulsars simultaneously in total across all timing sub arrays .

SKA1-SYS_REQ-2264 SKA1_Survey sub-arraying.

SKA1_Survey sub-arraying. It shall be possible to split the

SKA1_Survey array into independent operable ASKAP and SKA1

dish sub-arrays.

F.15.1.2 Manage Data Flow Graphs

Manages the identification, creation and deployment of data flow

graphs.

SDP_REQ-624 Data Flow Graphs

The SDP shall be responsible for the indentifiction, creation and

dissemination of data flow graphs

F.15.1.2.1 Manage Data Flow Models

Curation and provision of the underlying data flow models

from the data flow model store to the data flow manager as

they are needed.

SDP_REQ-625 Data Flow Models


The Master Controller shall provide updated data flow models

to the Data Flow Manager as/when they are needed.

F.15.1.2.2 Component Profiling

Tools to profile pipeline components to assist with decision

making in the graph building process.

SDP_REQ-626 Component Profiles

The SDP shall maintain profiles of pipeline components needed

for the construction of data flow graphs.

F.15.1.2.3 Hardware Resource Availability

Services to interrogate and report on the current availability of

hardware resources needed to construct a physical data flow

graph.

SDP_REQ-627 Hardware availability

The SDP shall determine the availablity of hardware resources

needed for the construction of data flow graphs.

F.15.1.2.4 Construct Physical Data Flow Graph

Build a physical data flow deployment graph based on the

chosen data flow model.

SDP_REQ-628 Create data flow graphs

The SDP shall build physical data flow deployment graphs

based on chosen data flow models.

F.15.1.3 Power Control

Controls all aspects of SDP power management, including bringup

from standby to unconfigured state.

SDP_REQ-629 Power Management

The Master Controller shall control all aspects of SDP power

management

F.15.1.3.1 Read Standby Configuration

Load the standby configuration into the power control system

to allow the transition to the unconfigured state.

SDP_REQ-630 Load standby configuration

The Master Controller shall load the standy configuratuon

scheme into the power control system to allow for the transition

to the unconfigured state.

F.15.1.3.2 Graceful Shutdown

Halt the entire SDP, apart from power on components, in a

graceful fashion. No time guarantee is given.

SDP_REQ-30 Graceful degradation

The SDP shall handle internal hardware and software failures

in a graceful fashion.

SDP_REQ-31 Graceful degradation - evaluation


The Master Controller shall evaluate internal hardware and

software failures as they occur in order to identify possible next

steps, including continuance, degraded operation, and

termination.

SDP_REQ-32 Graceful degradation - reporting

The Master Controller shall report the outcomes of any

automated failure handling to the TM via the logging

mechanism specified in SKA-TEL.SDP.SE-TEL.TM.SE-ICD-

001.

SDP_REQ-620 Graceful Error Recovery

The SDP shall recover gracefully from internal failures in both

hardware and software. Priority is to be placed on preserving

partially processed or buffered data to allow processing to be

restarted if possible.

SDP_REQ-621 Preservation of Intermediate Data Products

The SDP, on entering an error state, shall preserve structurally

valid intermediate data products until commanded to discard

them.

SDP_REQ-622 Inform TM on Availability of Data Products

The SDP, on entering an error state, shall inform the TM on the

state and availability of intermediate data products.

F.15.1.3.3 Emergency Shutdown

Halt the SDP components as fast as is safely possible. No

regard is paid to data integrity (outside of the archive). A time

guarantee may be given.

SDP_REQ-623 Restart Processing after Error

The SDP shall allow the TM to request a restart of a particular

observation based on the availability of intermediate data

products.

SKA1-SYS_REQ-2786 Safety documentation file

Safety documentation file . Elements shall provide procedures

for maintainers to recover from an unplanned shut-down,

including safety checks to be conducted prior to start-up, as

specified in SKA PRODUCT ASSURANCE & SAFETY

PLAN SKA-OFF.PAQA-SKO-QP-001.

F.15.1.4 Sub-element Control

Controls sub-elements within the SDP. Principally these include the

Data Manager, Platform Manager and the Scheduler.

SDP_REQ-375 SDP platform management

The SDP shall provide a dedicated platform management function.

SDP_REQ-376 Platform management interface to LMC

The SDP compute system platform management function shall have an

interface to the SDP LMC system.

SDP_REQ-378 Deployment system


The SDP compute system platform management function shall contain

a deployment service.

SDP_REQ-379 Scheduler

The SDP compute system platform management function shall provide

a scheduler for the compute system resources.

SDP_REQ-380 Scheduler Interface

The SDP compute system scheduler shall have an interface with the

LMC system, and with the pipelines.

SDP_REQ-382 Component system consistency

The SDP compute system deployment system shall ensure all

component systems are in a consistent, verifiable, documented, and

reproducible state at all time.

F.15.1.5 Observation Control

Services related to the setup and management of observations.

SDP_REQ-10 Observation control - status

The Master Controller shall provide a STATUS command which will

report on the status of the specified telescope operating mode.

SDP_REQ-13 Frequency control - switch

The Master Controller shall, on request from TM, switch the center

frequency in use for the current observation within 30 seconds (TBD).

SDP_REQ-17 Scheduling - Compute

The Master Controller shall be able to instruct the Scheduler to

schedule an observation to commence at a particular time with a

particular capability.

SDP_REQ-18 Scheduling - Data Layer

The Master Controller shall be able to instruct the Data Layer, via the

Data Flow Manager, to schedule on observation to commence at a

particular time with a particular capability.

SDP_REQ-19 Scheduling - Delivery

The Master Controller shall be able to instruct the Data Delivery

subsystem to schedule an observation to commence at a particular time

with a particular capability.

SDP_REQ-20 Scheduling - Feedback

The Master Controller shall aggregate scheduling responses from the

Scheduler, the Data Layer and the Data Delivery subsystem in order to

produce a detailed report on the success or failure of the scheduling

request.

SDP_REQ-21 Control - Compute

The Master Controller shall be able to instruct the Scheduler to start,

stop or provide status of a previously scheduled observation.

SDP_REQ-22 Control - Data Layer

The Master Controller shall be able to instruct the Data Layer, via the

Data Flow Manager, to start, stop or provide status of a previously

scheduled observation.


SDP_REQ-23 Control - Delivery

The Master Controller shall be able to instruct the Data Delivery

subsystem to start, stop or provide status of a previously scheduled

observation.

SDP_REQ-24 Control - Feedback

The Master Controller shall aggregate control responses from the

Scheduler, Data Layer and Data Delivery subsystem in order to

produce a detailed report on the success or failure or status information

of a control request.

SDP_REQ-26 Resource sharing

The Master Controller shall ensure that any shared resources between

SDP instances on different telescopes do not compromise the ability of

the instance to act concurrently and independently.

SDP_REQ-27 Observation control - switching

The Master Controller shall be able to switch between previously

scheduled observations within 30 seconds (TBD - based on

performance allocations of SKA-2133).

SDP_REQ-5 Observation scheduling

The SDP shall allow TM to schedule a requested observation.

SDP_REQ-6 Observation scheduling feedback

The Master Controller shall provide an OK/FAIL response with

reasons when a schedule request is issued.

SDP_REQ-8 Observation control - start

The Master Controller shall provide a START command to allow a

scheduled mode of operation to commence.

SDP_REQ-9 Observation control - stop

The Master Controller shall provide a STOP command to allow a

currently executing mode of operation to be terminated permanently.

F.15.1.5.1 Observation Runtime Estimation

Used to estimate the wall clock runtime for a particular

observation. This is used by TM during the observation

planning phase.

SDP_REQ-381 Scheduler input

The SDP compute system scheduler shall get observation mode

input the LMC system and run-time estimates from the

pipelines to produce an estimate of observation processing

time.

F.15.1.5.2 Observation Resource Estimation

Used to estimate the resources required to execute a particular

observation. Used by TM in the observation planning phase.

SDP_REQ-12 Frequency availability

The Master Controller shall, on request from TM, provide a

response as to whether the requested frequency band is

available within 1 second.


SDP_REQ-14 Availability - Compute

The Master Controller shall be able to query the Scheduler in

order to determine the availability of compute resources

(hardware and software) for a specific capability.

SDP_REQ-15 Availability - Data Layer

The Master Controller shall be able to query the Data Layer,

via the Data Flow Manager, in order to determine the

availability of data layer resources (transport, buffer and

archive) for a specific capability.

SDP_REQ-16 Availability - Delivery

The Master Controller shall be able to query the Data Delivery

subsystem in order to determine the availability of delivery

resources for a specific capability.

SDP_REQ-4 Capability availability

The SDP shall on request from the TM provide availability

information for the requested capability.

F.15.1.6 Observation Simulation

Allows simulation of an observation without the presence of the

Telescope Manager. Used in conjunction with the meta data simulator

and a CSP simulator (to be defined) to provide a complete

environment in which to carry out simulated operations.

SDP_REQ-631 Simulate observations

The Master Controller shall allow observations to be simulated

(without the Telescope Manager) in conjunction with a meta-data

simulator and CSP simulator.

F.15.1.7 Receive observation configuration

This is the component that actually receives observation configuration

from the TM.

SDP_REQ-38 Metadata input

The SDP shall query the Telescope Model for all static and dynamic

configuration data that is required prior to and during the execution of

a specific observation.

F.15.1.8 LMC Self Test

Provides self-testing services to allow internal and external users to

test the current state of the overall LMC function (and perhaps the

whole SDP as well).

SDP_REQ-34 Self testing

The SDP shall provide an automated self-test function that will

generate a report on the health of the SDP system as a whole, including

malfunction and out of tolerance operation.

F.15.2 Monitoring

Provides monitoring, logging, alarm, and event handling services for exposure

upwards to the Telescope Manager, and for internal use within the SDP.

SDP_REQ-450 SDP standard pipeline products


The SDP shall include as data products the pipeline processing log, and

Quality Assessment log for all pipelines.

SKA1-SYS_REQ-2280 System status.

System status. The system shall extract information about the current

condition of the system from the science and calibration data streams, and log

this information along with other relevant system and environmental status

information. Based on this information, it shall be possible to monitor, save,

and analyse the technical performance of the system.

SKA1-SYS_REQ-2546 Continuous performance monitoring.

Continuous performance monitoring. Where possible, the system shall be

designed to provide continuous performance monitoring.

F.15.2.1 Monitoring Data Collection

Services to collect, aggregate and store monitoring data from SDP

sub-elements

SDP_REQ-592 Status Monitoring

The SDP shall query status of science and calibration data streams.

F.15.2.2 Central Logging

A central (but likely physically distributed) logging capability that

allows fine-grained control of logging at a variety of levels within each

SDP sub-element.

SDP_REQ-593 Status Logging

The SDP shall log received status information.


Standard pipeline products. All pipelines shall include as data products

the pipeline processing log, and Quality Assessment log.

F.15.2.3 Event Handling

Handles events (and alarms as a special case). Includes collection,

aggregation and dissemination to other parties.

SDP_REQ-632 Event handler

The Master Controller shall initiate an event handler in response to

specific events and/or alarms.

F.15.2.3.1 Handle Alarms

Alarms are special cases of events and will need extra handling

procedures, particular on the notification front.

SDP_REQ-35 Alarms

The SDP shall support the generation of notification events, in

the form of alarms, to the TM based on predefined conditions.

SDP_REQ-36 Alarm timestamps

Alarm time stamps shall be accurate to TBD milliseconds and

with TBD milliseconds resolution.

SDP_REQ-37 Alarm latency

Latency from event to alarm shall be no more than 5 seconds.

SKA1-SYS_REQ-2312 Alarm latency.


Alarm latency. Latency from event to alarm shall be no more

than 5 seconds.

F.15.2.3.2 Event Notification

Function to provide notification services for all event types.

SDP_REQ-594 Status Reporting

The SDP shall use received status information to report on

technical performance.

F.15.2.3.3 Event Aggregation

Function to handle aggregation and suppression of events

based on pre-defined rules.

SDP_REQ-633 Event aggregation

The Master Controller shall aggregate and suppresse events

based on pre-defined rules.

F.15.2.4 Health State

Produces health indications suitable for consumption by the Telescope

Manager. Based on information collected by the monitor, logger and

event frameworks.

SDP_REQ-377 System health monitoring

The SDP compute system platform management function shall collect

and expose system health information to be made available to the

LMC.

F.15.3 Quality Assurance

Provides collection and visualisation of metrics that relate to the quality and

integrity of the science payload at various stages of processing through the

SDP.

SDP_REQ-450 SDP standard pipeline products

The SDP shall include as data products the pipeline processing log, and

Quality Assessment log for all pipelines.


Standard pipeline products. All pipelines shall include as data products the

pipeline processing log, and Quality Assessment log.

SKA1-SYS_REQ-2742 Performance assessment

Performance assessment: Performance assessment shall be based on multi-

valued functions of an observed Image and optionally a template Image.

SKA1-SYS_REQ-2743 Performance goals

Performance Goals: Performance goals shall be based on multi-valued

functions of an observed Image and optionally a template Image.

SKA1-SYS_REQ-2744 Quality assessment

Quality assessment. Quality assessment shall be based on the comparison of a

Performance Assessment and a Performance Goal.

F.15.3.2 QA Visualisation

Visualisation of the various metric used in Quality Assurance.


SDP_REQ-40 Quality assessment interface

The SDP shall provide an interface to allow the quality of the scientific

data to be assessed against a set of predefined criteria.

F.15.3.2.1 Client side rendering

Rendering function used when data is sent directly to the client

and rendered into a viewable graph.

SDP_REQ-41 Performance assessment

The User Interface shall allow the configuration and evaluation

of a performance assessment based on data provided by internal

SDP metrics.

F.15.3.2.2 Server side rendering

Renderer used when the viewable plot / image is produced on

the server side and sent in vector or bitmap form to the client

for direct display.

SDP_REQ-42 Performance goals

The User Interface shall allow the configuration of performance

goals that describe the desired outcome of a particular

performance assessment.

SDP_REQ-43 Quality assessment calculation

The User Interface shall allow the calculation of a quality

assessment based on a comparison of a particular performance

assessment and its associated performance goal.

F.15.3.3 QA Control

Specialist control of the QA visualisation and metric collection

process. For instance, the operator may select only a set of interesting

baselines on which to produce power spectrum plots.

SDP_REQ-595 QA annotations

The SDP shall provide the capability to attach QA-related data to data

output streams.

SKA1-SYS_REQ-2357 QA annotation.

QA annotation. The telescope shall facilitate the addition of QA

annotations by Users.

F.15.4 Local Telescope Model

Provides services to read and write data to the local telescope model.

SDP_REQ-49 Telescope Manager API

The SDP shall support the API specified in SKA-TEL.SDP.SE-TEL.TM.SE-

ICD-001 for all interaction with the TM.

SKA1-SYS_REQ-2645 Telescope Model

Telescope model. A dynamic computational model of the Telescope shall be

used to answer all queries about the state of the Telescope. The telescope

model shall consist of configuration information, numerical models, empirical

parameters, and conventions.


F.15.4.1 Ingest Metadata

Receive metadata from external telescope elements. Typically this will

be a stream of meta-data from the Telescope Manager, but may also

involve reading static configuration entities.

SDP_REQ-38 Metadata input

The SDP shall query the Telescope Model for all static and dynamic

configuration data that is required prior to and during the execution of

a specific observation.

SDP_REQ-597 Component system state information

Component system state information of the SDP compute system shall

be made available as part of the observation meta data.

F.15.4.2 Maintain Telescope Model

Using available data sources, both internal and external, make sure

the local telescope model reflects the current state of the telescope.

SDP_REQ-288 Telescope Model

The SDP shall use a dynamic computational model of the Telescope to

answer all queries about the state of the Telescope. The telescope

model shall consist of configuration information, numerical models,

empirical parameters, and conventions.

F.15.4.2.1 Validate Telescope Model

Check to ascertain the validity of key parts of the model. Useful

in situations where certain metadata must be known prior to a

particular operation commencing.

SDP_REQ-634 Telescope Model-Validation

The Master Controller shall validate key elements of the

telescope model.

F.15.4.2.2 Update Telescope Model

Insert new values into the telescope model, checking for

consistency and validity.

SDP_REQ-635 Telescope Model-Update

The Master Controller shall update key elements of the

telescope model.

F.15.4.3 Serialise Model

Provide a serialised view of the current model, typically used to write

to disk as part of commissioning and set to work activities.

SDP_REQ-636 Telescope Model-Serialise

The Master Controller shall provide a serialised view of the current

telescope model.

F.15.4.4 Simulate Telescope Model

Allows the required meta-data for a simulation observation to be

directly produced within the local telescope model.

SDP_REQ-39 Metadata proxy


The Master Controller shall act as the internal proxy for all SDP

components required telescope meta-data.

F.15.4.5 Handle Transactions

For high update rate use cases, such as the sky model, provide a

transaction capability to allow control of how changes propagate

through the model.

SDP_REQ-637 High update rate -transactions

The Master Controller shall provide a transaction capability for high

update rate use cases to allow control of how changes propogate

through the telescope model.

F.16 Commissioning

To do processing required for commissioning of the SKA system. Needs more

decomposition as the SKA commissioning plan is not yet available.

SDP_REQ-616 Restore visibility data from archive to buffer

The SDP shall be able to restore visibilities from the science data archive to the buffer

in order to process visibilities from previous observations.

SKA1-SYS_REQ-2657 Processing capability

Processing capability. SDP processing per telescope at Early Science shall support

processing rates 10% of that required for Full Observing (decimation being in any or

all of time, frequency, field of view )

F.18.1 Simulation


3.2. SDP non-functional requirements

NF.1 Security

SDP Security requirements,

SDP_REQ-360 Security requirements

The SDP shall include the following list of Security requirements in the SDP

design:SKA1-SYS_REQ-2478 Equipment securitySKA1-SYS_REQ-2479 Archive

securitySKA1-SYS_REQ-2504 Facilities and Equipment Intrusion.SKA1-SYS_REQ-

2793 Personnel security trainingSKA1-SYS_REQ-2822 Information security risk

assessmentSKA1-SYS_REQ-2823 Information security management for inter-

organizational communications

SKA1-SYS_REQ-2478 Equipment security

Equipment security. The observatory shall provide a secure environment for

equipment. This shall include protection of generators, fuel, solar cells and inter-

station assets such as copper cables.

SKA1-SYS_REQ-2479 Archive security

Archive security. The observatory shall provide a secure environment for all its data

archives.

SKA1-SYS_REQ-2504 Facilities and Equipment Intrusion.

Facilities and Equipment Intrusion . Where appropriate, SKA1 equipment facilities

shall be adequately protected against intrusion by insect and "larger" wandering

animals.

SKA1-SYS_REQ-2793 Personnel security training

Personnel security training . All personnel shall receive the security training identified

in the Security Management System necessary for their location. Additional specialist

pre-deployment training shall be given prior to working in remote environments.

SKA1-SYS_REQ-2822 Information security risk assessment

Information security risk assessment . An information security risk assessment shall

be conducted for each element in accordance with ISO/IEC 27005.

SKA1-SYS_REQ-2823 Information security management for inter-

organizational communications

Information security management for inter-organizational communications.

Information transfer between organisations shall be controlled in accordance with

ISO/IEC 27010 as tailored by SKA Organisation Security Policy.

NF.2 Equipment & Component Specifications

SDP equipment and component requirements.

SDP_REQ-361 Equipment and Component requirements

The SDP shall include the following list of Equipment and Component requirements

in the SDP design:SKA1-SYS_REQ-2501 Storage and transport Humidity.SKA1-

SYS_REQ-2502 Condensation.SKA1-SYS_REQ-2503 Pressure.SKA1-SYS_REQ-

2505 Sand and Dust.SKA1-SYS_REQ-2506 Fungus.SKA1-SYS_REQ-2509 Scope of

workmanship standards.SKA1-SYS_REQ-2513 Critical-useful-life

components.SKA1-SYS_REQ-2515 Component selection.SKA1-SYS_REQ-2516

Matching components.SKA1-SYS_REQ-2521 Component derating.SKA1-

SYS_REQ-2525 Fail safe provisions.SKA1-SYS_REQ-2543 Direct fault

indicatorsSKA1-SYS_REQ-2552 Malfunction detection.SKA1-SYS_REQ-2554


Ergonomics.SKA1-SYS_REQ-2572 Material environmental rule compliance.SKA1-

SYS_REQ-2573 Serial number.SKA1-SYS_REQ-2574 Drawing numbers.SKA1-

SYS_REQ-2575 Marking method.SKA1-SYS_REQ-2576 Electronically readable or

scannable IDSKA1-SYS_REQ-2577 Package part number marking.SKA1-

SYS_REQ-2578 Package serial number marking.SKA1-SYS_REQ-2579 Hazard

warning marking.SKA1-SYS_REQ-2580 LRU electrostatic warningsSKA1-

SYS_REQ-2581 Packaging electrostatic warnings.SKA1-SYS_REQ-2583 Cable

identification.SKA1-SYS_REQ-2584 Connector plates. All connector plates shall

carry identification labels for connectorsSKA1-SYS_REQ-2594 Modular

packaging.SKA1-SYS_REQ-2596 Discard at failure items.SKA1-SYS_REQ-2598

Module access.SKA1-SYS_REQ-2599 Component removal.SKA1-SYS_REQ-2600

Secure mounting of modules.SKA1-SYS_REQ-2601 Shock mounting

provision.SKA1-SYS_REQ-2602 Mounting preclusion.SKA1-SYS_REQ-2603

Mounting guides.SKA1-SYS_REQ-2604 Module labelling.SKA1-SYS_REQ-2605

Label robustness.SKA1-SYS_REQ-2606 Disposable item labelling.SKA1-

SYS_REQ-2733 Location of Emergency stop.SKA1-SYS_REQ-2798 Protection of

equipment in stationary use at non-weather protected locationsSKA1-SYS_REQ-2799

Protection of equipment in weather- protected locationsSKA1-SYS_REQ-2800

Transportation of equipmentSKA1-SYS_REQ-2801 Storage of equipment

SKA1-SYS_REQ-2501 Storage and transport Humidity.

Storage and transport Humidity . The storage and transport humidity shall be between

40% and 95%.

SKA1-SYS_REQ-2502 Condensation.

Condensation . Appropriate measures shall be taken to prevent the formation of

condensation on operating electronic components.

SKA1-SYS_REQ-2503 Pressure.

Pressure . Components shipped by air shall be capable of surviving pressures down to

11 kPa (equivalent altitude ~ 50,000 feet).

SKA1-SYS_REQ-2505 Sand and Dust.

Sand and Dust . SKA1 systems shall be adequately protected against sand and dust

ingress.

SKA1-SYS_REQ-2506 Fungus.

Fungus . Equipment shall be protected against fungus growth.

SKA1-SYS_REQ-2509 Scope of workmanship standards.

Scope of workmanship standards. SKA1 dedicated workmanship standards shall

cover all phases of production, assembly and integration, testing, handling, and

include clear requirements for acceptance/rejection criteria.

SKA1-SYS_REQ-2513 Critical-useful-life components.

Critical-useful-life components . Any critical-useful-life components shall be

identified.

SKA1-SYS_REQ-2515 Component selection.

Component selection . Parts and components shall be selected to meet reliability

requirements.

SKA1-SYS_REQ-2516 Matching components.

Matching components . Parts requiring select on test shall be eliminated by deign if

possible.


SKA1-SYS_REQ-2521 Component derating.

Component derating . Safety factors and margins shall be applied in the selection of

modules and components

SKA1-SYS_REQ-2525 Fail safe provisions.

Fail safe provisions . Designs shall implement fail-safe provisions to prevent

secondary failures.

SKA1-SYS_REQ-2543 Direct fault indicators

Direct fault indicators Where possible, direct fault indicators shall be designed in to

equipment.

SKA1-SYS_REQ-2552 Malfunction detection.

Malfunction detection. All equipment malfunction shall be detected at the system

level.

SKA1-SYS_REQ-2554 Ergonomics.

Ergonomics . The ergonomic design shall be compliant with ISO 6385.

SKA1-SYS_REQ-2572 Material environmental rule compliance.

Material environmental rule compliance. All materials used in the SKA1 design shall

be fully compliant to all environmental rules applicable to the SKA1 core and remote

sites.

SKA1-SYS_REQ-2573 Serial number.

Serial number . Each part shall be marked with a unique serial number in an easily

visible location.

SKA1-SYS_REQ-2574 Drawing numbers.

Drawing numbers . Each LRU type shall be identified with a unique drawing number.

SKA1-SYS_REQ-2575 Marking method.

Marking method. Method of marking shall be compatible with the nature of the item,

its environment and its use.

SKA1-SYS_REQ-2576 Electronically readable or scannable ID

Electronically readable or scannable ID. Where possible line replaceable items shall

be marked with an Electronically readable or scannable ID.

SKA1-SYS_REQ-2577 Package part number marking.

Package part number marking . All packaging shall be marked with the part number

of the contents.

SKA1-SYS_REQ-2578 Package serial number marking.

Package serial number marking . All packaging shall be marked with the serial

number of the contents.

SKA1-SYS_REQ-2579 Hazard warning marking.

Hazard warning marking . All items that present a potential hazard shall be labelled in

accordance with BS EN ISO 7010.

SKA1-SYS_REQ-2580 LRU electrostatic warnings

LRU electrostatic warnings All LRUs with electrostatic sensitive components shall be

fitted with ESD warning labels.

SKA1-SYS_REQ-2581 Packaging electrostatic warnings.

Packaging electrostatic warnings. All packaging containing static sensitive contents

shall be marked with ESD warning labels.


SKA1-SYS_REQ-2583 Cable identification.

Cable identification. All cables ends shall carry a unique identifier.

SKA1-SYS_REQ-2584 Connector plates. All connector plates shall carry

identification labels for connectors

Connector plates. All connector plates shall carry identification labels for connectors.

SKA1-SYS_REQ-2594 Modular packaging.

Modular packaging. The packaging of components shall be modular to limit

maintenance to the removal of one module.

SKA1-SYS_REQ-2596 Discard at failure items.

Discard at failure items. Discard at failure items shall be packed at low cost.

SKA1-SYS_REQ-2598 Module access.

Module access . Where applicable, access between modules shall be sufficient to

facilitate hand grasping.

SKA1-SYS_REQ-2599 Component removal.

Component removal . Modules and components shall be mounted such that removal

of any single item will not require the removal of other items (component stacking to

be avoided where possible)

SKA1-SYS_REQ-2600 Secure mounting of modules.

Secure mounting of modules . Modules shall be securely mounted (in compliance

with the shock and vibration requirements) with the minimum number of fasteners.

SKA1-SYS_REQ-2601 Shock mounting provision.

Shock mounting provision . Shock mounting provisions shall be made where

applicable.

SKA1-SYS_REQ-2602 Mounting preclusion.

Mounting preclusion . Provisions for the preclusion of mounting the wrong module

shall be provided (key coding of connectors etc.).

SKA1-SYS_REQ-2603 Mounting guides.

Mounting guides . Mounting guides and location pins shall be provided to facilitate

module mounting.

SKA1-SYS_REQ-2604 Module labelling.

Module labelling . Where possible, labelling of modules shall be on the top or

adjacent in plain sight.

SKA1-SYS_REQ-2605 Label robustness.

Label robustness . Labels shall be permanently affixed and unlikely to come off

during maintenance or as a result of the environment.

SKA1-SYS_REQ-2606 Disposable item labelling.

Disposable LRU labelling . Disposable line replaceable units should be labelled as

such.

SKA1-SYS_REQ-2733 Location of Emergency stop

Location of Emergency stop . Emergency stop switches shall be located in such a way

to minimize the risk of injury. (Verified by Analysis as 'minimisation' is unverifiable

any other way.)

SKA1-SYS_REQ-2798 Protection of equipment in stationary use at non-weather

protected locations


Protection of equipment in stationary use at non-weather protected locations .

Equipment in stationary use at non-weather protected locations shall be protected

against environmental conditions 4K4H/ 4Z1/ 4Z5/ 4Z6/ 4B2/ 4C1/ 4S3/ 4M4 in

accordance with BS EN IEC 60721-3-4. NOTE: 4Z5 refers to the survival, non-

operational mode. The equipment shall be able to operate normally for air movement

up to 11 m/s

SKA1-SYS_REQ-2799 Protection of equipment in weather- protected locations

Protection of equipment in weather-protected locations. Equipment in stationary use

at weather protected locations shall be protected against environmental conditions

3K8H/ 3Z1/ 3Z11/ 3Z12/ 3B3/ 3C1R/ 3S3/ 3M4 in accordance with BS EN IEC

60721-3-3.

SKA1-SYS_REQ-2800 Transportation of equipment

Transportation of equipment . Equipment shall be designed to withstand

transportation from an engineering depot to a station exposed to environmental

conditions 2K5H/2B3/2C1/2S3/2M3 as detailed in BS EN IEC 60721-3-2. NOTE: It

may be assumed that the equipment will be transported in the original packaging that

it was delivered to the engineering depot.

SKA1-SYS_REQ-2801 Storage of equipment

Storage of equipment. Designs shall identify any requirements for equipment to be

stored in environmental conditions less severe than 1K11/1B3/1C1/1S3/1M3 as

specified inBS EN IEC 60721-3-1. Note: It may be assumed that equipment will be

stored in its original packaging.

NF.3 Production & Manufacturing Specifications

SDP production and manufacturing requirements.

SDP_REQ-363 Production and Manufacturing requirements

The SDP shall include the following list of Production and Manufacturing

requirements in the SDP design:SKA1-SYS_REQ-2559 Design for economic

production.SKA1-SYS_REQ-2560 Design definition.SKA1-SYS_REQ-2561

Manufacturing facilities.SKA1-SYS_REQ-2562 Standard manufacturing tools.SKA1-

SYS_REQ-2566 Materials list.SKA1-SYS_REQ-2567 Hazardous Materials

list.SKA1-SYS_REQ-2568 Parts list.SKA1-SYS_REQ-2569 Process list.SKA1-

SYS_REQ-2570 Parts availability.SKA1-SYS_REQ-2571 Long lead time items.

SKA1-SYS_REQ-2559 Design for economic production.

Design for economic production . All designs for the SKA shall be designed for

economic production. This is required to ensure that the SKA is buildable for a

reasonable cost (Con Ops Section 1.2)

SKA1-SYS_REQ-2560 Design definition.

Design definition . Design definition shall be in sufficient detail to allow one or more

manufacturers to produce the same item within identified tolerances.

SKA1-SYS_REQ-2561 Manufacturing facilities.

Manufacturing facilities . Where possible, currently existing facilities shall be used

for manufacturing.

SKA1-SYS_REQ-2562 Standard manufacturing tools.

Standard manufacturing tools . Where possible, standard manufacturing tools shall be

used.


SKA1-SYS_REQ-2566 Materials list.

Materials list. Each sub-system supplier shall provide a Materials list for all items

intended for use within SKA1.

SKA1-SYS_REQ-2567 Hazardous Materials list.

Hazardous Materials list. Each Element supplier shall provide a list of hazardous

materials used for all items intended for use in the SKA1 detailing suggested handling

precautions, disposal instructions and contra-indications.

SKA1-SYS_REQ-2568 Parts list.

Parts list. Each Element supplier shall provide a parts list for all items intended for use

in the SKA1.

SKA1-SYS_REQ-2569 Process list.

P rocess list. Each element supplier shall provide a process list for all items intended

for use in the SKA1.

SKA1-SYS_REQ-2570 Parts availability.

Parts availability. The estimated availability of the parts shall be compatible with the

final system's life cycle.

SKA1-SYS_REQ-2571 Long lead time items.

Long lead time items . Long lead time items shall be identified to the project

management.

NF.4 Operations

SDP operational requirements.

SDP_REQ-241 SDP to INFRA interface

The interface between the SDP and INFRA shall be compliant with the

SKA.TEL.SDP.SE-SKA.TEL.INFRA.SE-ICD-001 Interface Control Document.

SDP_REQ-242 SaDT interface

The interface between SADT and SDP shall be compliant with the SKA-

TEL.SADT.SE-TEL.SDP.SE-ICD-001 Interface Control Document.

SDP_REQ-358 Operational requirements

The SDP shall include the following list of Operational requirements in the SDP

design: SKA1-SYS_REQ-2118 South African Science Processing Centre SKA1-

SYS_REQ-2123 Australian Science Processing Centre SKA1-SYS_REQ-2116 South

African Engineering Operations Centre SKA1-SYS_REQ-2121 Australian

Engineering Operations Centre SKA1-SYS_REQ-2425 SADT to SDP interface.

SKA1-SYS_REQ-2431 SDP to TM interface. SKA1-SYS_REQ-2432 SDP to INFRA

interface. SKA1-SYS_REQ-2433 Design for SKA2 Extensibility SKA1-SYS_REQ-

2650 Seismic resilience SKA1-SYS_REQ-2716 Telescope availability SKA1-

SYS_REQ-2827 System Availability SKA1-SYS_REQ-2834 SKA1_Mid-MeerKAT

infrastructure reuse SKA1-SYS_REQ-???? SDP Power Cap

SKA1-SYS_REQ-2116 South African Engineering Operations Centre

South African Engineering Operations Centre. The South African Engineering

Operations Centre shall be located at Klerefontein.

SKA1-SYS_REQ-2118 South African Science Processing Centre

South African Science Processing Centre. The South African Science Processing

centre shall be located in Cape Town


SKA1-SYS_REQ-2121 Australian Engineering Operations Centre

Australian Engineering Operations Centre The Australian Engineering Operations

Centre shall be in in Geraldton.

SKA1-SYS_REQ-2123 Australian Science Processing Centre

Australian Science processing centre The Australian Science Processing Centre shall

make use of floor space, power, cooling, and other infrastructure at the Pawsey centre

in Perth.

SKA1-SYS_REQ-2425 SADT to SDP interface.

SADT to SDP interface . The interface between SADT and SDP shall be compliant

with the SKA-TEL.SADT.SE-TEL.SDP.SE-ICD-001 Interface Control Document.

SKA1-SYS_REQ-2431 SDP to TM interface.

SDP to TM interface . The interface between SDP and TM shall be compliant with the

SKA-TEL.SDP.SE-TEL.TM.SE-ICD-001 Interface Control Document.

SKA1-SYS_REQ-2432 SDP to INFRA interface.

SDP to INFRA interface . The interface between SDP and Infra shall be compliant

with the SKA.TEL.SDP.SE-TEL.INFRA.SE-ICD-001 Interface Control Document.

SKA1-SYS_REQ-2433 Design for SKA2 Extensibility

Design for Extensibility .Design trade studies for SKA1 shall include scenarios where

design features are included which will allow Increases in the number of receptors for

SKA2 over SKA1 by a factor of 10 whilst re-using more than 90% of SKA1 hardware

The introduction of AIP technologies at SKA2 scales whilst re-using more than 90%

of SKA1 hardware Such trade studies shall yield the incremental cost of such

scenarios over those which do not include such design features.

SKA1-SYS_REQ-2650 Seismic resilience

Seismic resilience. SKA1 structures and equipment shall survive and be fully

operational after a seismic event of magnitude up to Richter 3.8. Note: Seismic event

includes underground collapses in addition to earthquakes.

SKA1-SYS_REQ-2716 Telescope availability

Average annual availability. Each SKA1 telescope shall have an operational

availability of 95%

SKA1-SYS_REQ-2827 System Availability

System Availability . System designs shall meet the system availability allocations

specified in SKA-OFF.SE.ARC-SKAO-RAM-001.

SKA1-SYS_REQ-2834 SKA1_Mid-MeerKAT infrastructure reuse

SKA1_Mid-MeerKAT infrastructure reuse. Where economically practicable, the

existing MeerKAT infrastructure will be reused

SKA1-SYS_REQ-???? SDP Power Cap

Missing L1 requirement for SDP power cap.

NF.5 EMC & RFI

SDP EMC and RFI requirements.

SDP_REQ-359 EMC and RFI requirements

The SDP shall include the following list of EMC and RFI requirements in the SDP

design:SKA1-SYS_REQ-2462 Electromagnetic RadiationSKA1-SYS_REQ-2463

Self-induced RFISKA1-SYS_REQ-2464 Electromagnetic Compatibility


StandardsSKA1-SYS_REQ-2465 Electricity network Electromagnetic

CompatibilitySKA1-SYS_REQ-2466 EMC compatibility marking.SKA1-SYS_REQ-

2467 Electromagnetic susceptibility.

SKA1-SYS_REQ-2462 Electromagnetic Radiation

Electromagnetic Radiation. Any component of the observatory shall not emit

electromagnetic radiation, in any of the stated frequency intervals for broad band and

narrow band cases, that exceeds the SKA RFI/EMI Threshold Levels[4]

SKA1-SYS_REQ-2463 Self-induced RFI

Self-induced RFI. The SKA1 Telescope shall generate less self-induced RFI, within

the Telescope's operating frequency bands, than the SKA RFI/EMI Protection Levels,

for both broad band and narrow band cases, as specified in the "RFI/EMI Protection

and Threshold Levels for the SKA" document. The SKA RFI/EMI Protection Levels

are defined at the respective receiver input, and measured at the respective Telescope

time series output.

SKA1-SYS_REQ-2464 Electromagnetic Compatibility Standards

Electromagnetic Compatibility Standards. The SKA1 Telescopes shall be compliant

with one or more of the following standards for emissions and one or more for

susceptibility/immunity:*BS EN 61000-6-2. Electromagnetic compatibility (EMC).

Generic standards. Immunity standard for industrial environments.*BS EN 61000-6-4

AMD2. Electromagnetic compatibility (EMC). Part 6-4. Generic standards. Emission

standard for industrial environments.*BS CISPR 14-1. Electromagnetic compatibility.

Requirements for household appliances, electric tools and similar apparatus. Part 1.

Emission.*MIL-STD-464C

SKA1-SYS_REQ-2465 Electricity network Electromagnetic Compatibility

Electricity network Electromagnetic Compatibility. The SKA1 telescopes shall follow

the TBD code of practice for the application of Electromagnetic Compatibility (EMC)

standards and guidelines in electricity utility networks.

SKA1-SYS_REQ-2466 EMC compatibility marking.

EMC compatibility marking. All "off-the-shelf" equipment shall possess as a

minimum the host country EMC marking.

SKA1-SYS_REQ-2467 Electromagnetic susceptibility.

Electromagnetic susceptibility. The observatory shall not be susceptible to terrestrial

electromagnetic radiation at any frequency that significantly interferes with its normal

operation.

NF.6 Health, Safety & Environment

SDP health, safety and environmental requirements.

SDP_REQ-357 Health, Safety and Environmental requirements

The SDP shall include the following list of Health, Safety and Environmental

requirements in the SDP design:SKA1-SYS_REQ-2435 Hazard analysis.SKA1-

SYS_REQ-2436 Safety incident recovery planSKA1-SYS_REQ-2437 Design for

hazard elimination.SKA1-SYS_REQ-2438 Fail safe design.SKA1-SYS_REQ-2439

Emergency stop.SKA1-SYS_REQ-2443 Protection from high voltages.SKA1-

SYS_REQ-2444 Safety grounding and bonding.SKA1-SYS_REQ-2445 Electrical

circuit interlocks.SKA1-SYS_REQ-2446 Electrical safetySKA1-SYS_REQ-2448

Stand-off and handles.SKA1-SYS_REQ-2447 Sharp metal edges.SKA1-SYS_REQ-

2449 Construction Safety Plan.SKA1-SYS_REQ-2450 Safety information for


useSKA1-SYS_REQ-2451 Safety training.SKA1-SYS_REQ-2452 Protective

clothing.SKA1-SYS_REQ-2454 Fire fighting equipment.SKA1-SYS_REQ-2455

Noise level dosage.SKA1-SYS_REQ-2456 Transient noise level.SKA1-SYS_REQ-

2457 Illumination.SKA1-SYS_REQ-2458 Clean airSKA1-SYS_REQ-2460

Occupational health legislation and regulations.SKA1-SYS_REQ-2481 Emergency

communicationSKA1-SYS_REQ-2483 Environment protection plan.SKA1-

SYS_REQ-2484 Environmental legislation and regulations.SKA1-SYS_REQ-2491

Safety.SKA1-SYS_REQ-2500 Operating Humidity.SKA1-SYS_REQ-2790

Environmental Impact AssessmentSKA1-SYS_REQ-2795 Travel safetySKA1-

SYS_REQ-2818 Marking of machinery - safetySKA1-SYS_REQ-2819 Safety of

machinery risk assessmentSKA1-SYS_REQ-2820 Safety of equipment with rated

voltage not exceeding 600V

SKA1-SYS_REQ-2435 Hazard analysis.

Hazard analysis . A hazard analysis shall be performed at the system and element

level in accordance with BS IEC 61882 and, where applicable, shall include a FMEA

in accordance with EN 60812.

SKA1-SYS_REQ-2436 Safety incident recovery plan

Safety incident recovery plan. A safety incident recovery plan shall be produced in

accordance with SKA PRODUCT ASSURANCE & SAFETY PLAN SKA-

OFF.PAQA-SKO-QP-001.

SKA1-SYS_REQ-2437 Design for hazard elimination.

Design for hazard elimination. Designs shall demonstrate the elimination, or

mitigation to a risk level practically achievable, of all hazards by means of a

subsystem hazard analysis (SSHA) report as described in EN 14738 and tailored by

SKA Product Assurance and Safety Plan SKA-OFF.PAQA-SKO-QP-001.

SKA1-SYS_REQ-2438 Fail safe design.

Fail safe design. Components and Equipment shall be designed to be locally fail-safe

and not rely on external safety devices or measures to operate safely.

SKA1-SYS_REQ-2439 Emergency stop.

Emergency stop . The SKA1 Elements shall have emergency stop switches or brakes

for all electro-mechanical or mechanical systems that have been identified by safety

analyses (required under SKA1-SYS_REQ-2435) to pose a hazard.

SKA1-SYS_REQ-2443 Protection from high voltages.

Protection from high voltages. High voltage cages or enclosures shall be used to

protect personnel from inadvertent access to high voltages in accordance with

AS/NZS3000 (Australia) and SANS10142 (South Africa).

SKA1-SYS_REQ-2444 Safety grounding and bonding.

Safety grounding and bonding . External conductive parts shall be grounded in

compliance to:South Africa:National Building Regulations and Building Standards

Act, 1977Occupational Health and Safety act, 1993SANS 10313Australia:AS/NZ

3000,AS/NZ 1768

SKA1-SYS_REQ-2445 Electrical circuit interlocks.

Electrical circuit interlocks . Electrical circuit inter-locks shall be provided to prevent

personnel coming into contact with hazards that cannot otherwise be eliminated from

design.

SKA1-SYS_REQ-2446 Electrical safety


Electrical safety . Electrical risks and hazards shall be controlled in accordance with

local, State and national legislation and Codes of Practice.NOTE: In South Africa,

SANS 10142-1 and SANS 10142-2 shall apply.NOTE: In Australia, in addition to

legislation, the following Codes of Practice shall be applied:AS/NZ 3000Safe Work

Australia 'Managing Electrical Risks at the Workplace';Western Australia Director of

Energy Safety 'Safe Low Voltage Work Practices by Electricians'

SKA1-SYS_REQ-2447 Sharp metal edges.

Sharp metal edges . If they cannot be eliminated from design, sharp edges, access

openings and corners shall be protected with covers or coatings where feasible.

SKA1-SYS_REQ-2448 Stand-off and handles.

Stand-off and handles . Stand-offs and handles shall be used to protect system

components from damage during shop maintenance.

SKA1-SYS_REQ-2449 Construction Safety Plan.

Construction and AIV Safety Plan. A comprehensive safety plan, tailored to

construction and AIV activities, shall be established and implemented before the

construction starts at the observatory site.

SKA1-SYS_REQ-2450 Safety information for use

Safety information for use. Where risks remain despite inherently safe design

measures, safeguarding and the adoption ofcomplementary protective measures, the

residual risks shall be identified in the information for use in accordance with BS EN

ISO 12100 (section 6).The information for use shall include, but not be limited to, the

following:Ã¢Å½Â¯ operating procedures for the use of the machinery consistent with

the expected ability of personnel who use the machinery or other persons who can be

exposed to the hazards associated with the machinery;Ã¢Å½Â¯ the recommended

safe working practices for the use of the machinery and the related training

requirements adequately described;Ã¢Å½Â¯ sufficient information, including

warning of residual risks for the different phases of the life of the

machinery;Ã¢Å½Â¯ the description of any recommended personal protective

equipment, including detail as to its need as well as to training needed for its

use.Information for use shall not be a substitute for the correct application of

inherently safe design measures, safeguarding or complementary protective measures.

SKA1-SYS_REQ-2451 Safety training.

S afety training . All personnel shall be provided with appropriate Health and Safety

training in compliance with local regulations.

SKA1-SYS_REQ-2452 Protective clothing.

Protective clothing. Protective Clothing for areas where environments detrimental to

human safety shall be worn.

SKA1-SYS_REQ-2454 Fire fighting equipment.

Fire fighting equipment . Fire fighting equipment shall be made available at all SKA

premises and facilities.

SKA1-SYS_REQ-2455 Noise level dosage.

Noise level dosage. Personnel shall not be exposed to noise level dosages exceeding

local health and safety guideline levels. The maximum noise levels shall not exceed

an 8-hour average exposure of 85 decibels as specified in the Australian National

Standard for Occupational Noise NOHSC: 1007(2000) and South African Noise-

Induce Hearing Loss Regulations (No R.307 2003) of the Occupational Health and


Safety Act, 1993 (Act No 85 of 1993). The desirable maximum noise level is 75

decibels. Note: The National Code of Practice for Noise Management and Protection

of Hearing at Work [NOHSC:2009(2004)] provides practical guidance on how

NOHSC:1007(2000) can be achieved.

SKA1-SYS_REQ-2456 Transient noise level.

Transient noise level. Noise levels exceeding 85dB shall be controlled or mitigated in

accordance with NOHSC National Standard for Occupational Noise [NOHSC: 1007].

SKA1-SYS_REQ-2457 Illumination.

Illumination. Personnel shall be provided with a working illumination level which is

compliant with local and national regulations including the current issue of SANS

10114-1 in South Africa and the AS/NZS 1680 series in Australia.

SKA1-SYS_REQ-2458 Clean air

Clean air. Personnel shall be provided with air quality at least compliant with the

current issue of SANS 10400-O (South Africa - The application of National Building

SKA1-SYS_REQ-2460 Occupational health legislation and regulations.

Occupational health legislation and regulations. The observatory shall comply with all

applicable local, State and national occupational health regulations and standards in

force at the time. Regulations include, but are not limited to:South

Africa:Occupational Health and Safety Act, 1993, and all its

regulations.Australia:Commonwealth Occupational Health and Safety Act 1991;OHS

(Safety Arrangements) Regulations 1991;OHS (Safety Standards) Regulations

1994;OHS Codes of Practice 2008.Western Australia:Occupational Safety and Health

Act 1984;Harmonised OHS legislation (as enacted).

SKA1-SYS_REQ-2481 Emergency communication

Emergency communication. The observatory shall provide an independent system to

communicate with outside locations in emergencies.

SKA1-SYS_REQ-2483 Environment protection plan.

Environment protection plan . An Environmental protection plan shall be developed

and maintained. This shall include the management of Environmental Impact

Assessments (EIA) in accordance with SA NEMA, WA EPA and Commonwealth

EPBC.

SKA1-SYS_REQ-2484 Environmental legislation and regulations.

Environmental legislation and regulations. The observatory shall be compliant with

all local, State and national environmental protection legislation and

regulations.NOTE: Legislation takes precedence over project/contract documentation

and requirements. Omission of a law from this requirement does not affect its

enforceability. Legislation is also subject to amendment and so the Environmental

Laws identified during the Request for Information (copied below) may be modified

by the Hosting Agreements and subsequent Acts and Amendments.Legislation and

regulations identified during the response to Request for Information include:South

Africa:National Environmental Management Act, 1998 ("NEMA");National Water

Act, 1998;National Environmental Management: Air Quality Act, 2004;National

Environmental Management Waste Act, 2008;National Environment Management:

Biodiversity Act, 2004;National Heritage Resources Act, 1999.*Australia:The

Commonwealth Environment Protection and Biodiversity Conservation (EPBC) Act

1999.The Western Australian Environmental Protection Act 1986The Western

Australian Land Administration Act 1997In addition, approvals will be required under


the Western Australia Mining Act 1978, Heritage of Western Australia Act 1990, the

Western Australian Aboriginal Heritage Act 1972 and the MRO Indigenous Land Use

Agreement 2009.* Other South African environmental statutes include the

Environment Conservation Act, 1989, various air pollution statutes, the National

Heritage Resources Act, 1999, the Hazardous Substances Act, 1973, the Health Act,

1977, the Nuclear Energy Act, 1999, the National Nuclear Regulatory Act, 1999, the

National Environmental Management: Protected Areas Act, 2003, the Fertilisers,

Farm Feeds, Agricultural Remedies and Stock Remedies Act, 1947, the Marine

Living Resources Act, 1998, and the National Environmental Management: Integrated

Coastal Management Act, 2008.

SKA1-SYS_REQ-2491 Safety.

Safety. SKA1 equipment and buildings shall be designed and built in compliance with

national and State regulations including AS 1170.4 (Importance level 3, design life 50

years) and SANS 10160-4 for earthquakes of magnitude up to Richter 3.8.

SKA1-SYS_REQ-2500 Operating Humidity.

Operating Humidity . The operating humidity shall be between 40% and 60%

SKA1-SYS_REQ-2790 Environmental Impact Assessment

Environmental Impact Assessment . The Observatory shall undertake an

Environmental Impact Assessment (EIA) in accordance with the local and national

environmental legislation. NOTE: the EIA shall be undertaken in accordance with:

South Africa - the National Environmental Management Act (NEMA); Australia -

Western Australian EPA and Commonwealth EPBC.

SKA1-SYS_REQ-2795 Travel safety

Travel safety. Personnel shall adhere to local safety procedures for travelling in

remote areas. NOTE: Safety procedures should include the training and equipment

required, such as driving instruction, vehicles appropriate for the environment and

radio equipment.

SKA1-SYS_REQ-2818 Marking of machinery - safety

Marking of machinery - safety. In accordance with ISO 61310_2, machinery shall

bear all markings which are necessary ? for its unambiguous identification; ? for its

safe use; and supplementary information shall be given, as appropriate: ? permanently

on the machinery; ? in accompanying documents such as instruction handbooks; ? on

the packaging

SKA1-SYS_REQ-2819 Safety of machinery risk assessment

Safety of machinery risk assessment . A risk assessment shall be conducted for each

item of machinery in accordance with BS EN ISO 12100.

SKA1-SYS_REQ-2820 Safety of equipment with rated voltage not exceeding

600V

Safety of equipment with rated voltage not exceeding 600V . Equipment shall comply

with the safety requirements of BS EN IEC 60950. NOTE: This includes electric

shock, energy related hazards, fire, heat related hazards, mechanical hazards, radiation

and chemical hazards.

NF.7 Maintenance, Test & Support

SDP maintenance, test and support requirements.

SDP_REQ-362 Maintenance, Test and Support requirements


The SDP shall include the following list of Maintenance, Test and Support

requirements in the SDP design:SKA1-SYS_REQ-2512 Best practice.SKA1-

SYS_REQ-2517 Known failure rate parts.SKA1-SYS_REQ-2518 High failure rate

parts.SKA1-SYS_REQ-2519 Reliability testing.SKA1-SYS_REQ-2520 Spares and

repair parts testing.SKA1-SYS_REQ-2522 Shelf life and wear out

characteristics.SKA1-SYS_REQ-2523 Special procurement components.SKA1-

SYS_REQ-2526 Maintainability budgetsSKA1-SYS_REQ-2527 Test and Repair

InstructionsSKA1-SYS_REQ-2528 Level of maintenanceSKA1-SYS_REQ-2529

Maintenance test and support equipmentSKA1-SYS_REQ-2538 Test and support

equipmentSKA1-SYS_REQ-2539 Test and support equipment standardisationSKA1-

SYS_REQ-2540 Test and support equipment lifecycle costs.SKA1-SYS_REQ-2541

Test equipment reliabilitySKA1-SYS_REQ-2542 TrainingSKA1-SYS_REQ-2544

Self-test.SKA1-SYS_REQ-2552 Malfunction detection.SKA1-SYS_REQ-2556

Access tools.SKA1-SYS_REQ-2595 Maintenance provisions.SKA1-SYS_REQ-2597

Plug-in modules.SKA1-SYS_REQ-2711 Component obsolescence planSKA1-

SYS_REQ-2718 Availability budgetsSKA1-SYS_REQ-2722 Availability, reliability,

and maintenance plansSKA1-SYS_REQ-2802 Design for maintainabilitySKA1-

SYS_REQ-2806 Product AssuranceSKA1-SYS_REQ-2816 Design for testability

SKA1-SYS_REQ-2512 Best practice.

Best practice . Best available methods for reducing adverse effects of operational and

maintenance environments on critical components shall be adopted.

SKA1-SYS_REQ-2517 Known failure rate parts.

Known f ailure rate parts. The failure rate of parts shall be known (e.g. through

analysis or modelling) before inclusion in SKA design.

SKA1-SYS_REQ-2518 High failure rate parts.

High failure rate parts. Parts with excessive failure rates shall be identified.

SKA1-SYS_REQ-2519 Reliability testing.

Reliability testing . A testing and evaluation master plan shall be generated for high-

risk reliability components.

SKA1-SYS_REQ-2520 Spares and repair parts testing.

Spares and repair parts testing . Critical spare and repair line replaceable units shall be

tested before deployment.

SKA1-SYS_REQ-2522 Shelf life and wear out characteristics.

Shelf life and wear out characteristics . The shelf life and wear out characteristics of

all components and parts shall be known before inclusion in SKA designs.

SKA1-SYS_REQ-2523 Special procurement components.

Special procurement components . Critical parts requiring special procurement

methods, testing and handling provisions shall be identified.

SKA1-SYS_REQ-2526 Maintainability budgets

Maintainability budgets. Maintainability budgets shall be allocated at the system

decomposition level, and shall be consistent with the system level requirements for

reliability and maintainability of the system.

SKA1-SYS_REQ-2527 Test and Repair Instructions

Test and Repair Instructions. Where end user repair is applicable Test and Repair

Instructions shall be delivered with all equipment.


SKA1-SYS_REQ-2528 Level of maintenance

Level of maintenance. The level of maintenance shall be identified for each repairable

item.

SKA1-SYS_REQ-2529 Maintenance test and support equipment

Maintenance test and support equipment. Equipment required for test and support

shall be identified for each repairable item.

SKA1-SYS_REQ-2538 Test and support equipment

Test and support equipment Test and support equipment shall be identified for each

level of maintenance.

SKA1-SYS_REQ-2539 Test and support equipment standardisation

Test and support equipment standardisation. Any test equipment not included in the

standard test equipment list required for the integration, commissioning and

maintenance of equipment shall be declared.

SKA1-SYS_REQ-2540 Test and support equipment lifecycle costs.

Test and support equipment lifecycle costs. Life cycle costs shall be generated for all

test and support equipment.

SKA1-SYS_REQ-2541 Test equipment reliability

Test equipment reliability Test equipment reliability shall be sufficient to meet the

maintainability requirements.

SKA1-SYS_REQ-2542 Training

T raining A plan detailing the training required for maintenance, calibration and repair

shall be generated.

SKA1-SYS_REQ-2544 Self-test.

Self-test . Self-Test capability such that all faults can be identified down to LRU level

shall be provided.

SKA1-SYS_REQ-2552 Malfunction detection.

Malfunction detection. All equipment malfunction shall be detected at the system

level.

SKA1-SYS_REQ-2556 Access tools.

Access tools . Access requiring tools shall be minimised.

SKA1-SYS_REQ-2595 Maintenance provisions.

Maintenance provisions. Repairable items shall be designed to include maintenance

provisions such as test points, accessibility, and plug-in components.

SKA1-SYS_REQ-2597 Plug-in modules.

Plug-in modules. The design shall implement plug-in modules to the maximum extent

possible.

SKA1-SYS_REQ-2711 Component obsolescence plan

Component obsolescence plan. There shall be a plan for the management of

component obsolescence.

SKA1-SYS_REQ-2718 Availability budgets

Availability budgets. Availability budgets shall be allocated at the system

decomposition level, and shall be consistent with the system level requirements for

reliability and maintainability of the system.

SKA1-SYS_REQ-2722 Availability, reliability, and maintenance plans


Availability, reliability, and maintenance plans . There shall be an availability,

reliability and maintenance plan for each SKA1 telescope.

SKA1-SYS_REQ-2802 Design for maintainability

Design for maintainability . Designs shall incorporate maintainability studies and

analysis in accordance with BS EN IEC 60706-2 with emphasis on minimising the

need for maintainers on sites. This activity should incorporate best practice such as

described by B.S. Blanchard & W.J. Fabrycky 'Systems Engineering and Analysis',

Pearson 2011.

SKA1-SYS_REQ-2806 Product Assurance

Product Assurance . Product Assurance shall be managed following a process

modelled on the SKA Product Assurance & Safety Plan SKA-OFF.PAQA-SKO-QP-

001

SKA1-SYS_REQ-2816 Design for testability

Design for testability. Designs shall include an assessment of testability in accordance

with BS EN IEC 60706-5

NF.8 VLBI

SDP VLBI requirements. VLBI requirements are categorised as non-functional as

SDP is not involved in VLBI processing.

SKA1-SYS_REQ-2838 VLBI data sources

VLBI data sources. The SKA1_Mid and SKA1_Survey telescopes shall be data

sources for VLBI data acquisition system. The interface between the telescopes

SAK1_Mid and SkA1_Survey and the external VLBI data acquisition system shall be

compliant with the ICD SKA-TEL-SKO-0000116

SKA1-SYS_REQ-2838 Provision of equipment for recording

Provision of equipment for recording . Provision of equipment for recording or

capturing VLBI data is outside the scope of SKA1

SKA1-SYS_REQ-2840 VLBI equipment and eVLBI connectivity

VLBI equipment and eVLBI connectivity. VLBI equipment and eVLBI connectivity

beyond the interface boundary described in the ICD SKA-TEL-SKO-0000116 is

outside the scope of supply of the SKA1 project.

SKA1-SYS_REQ-2844 VLBI Processing

VLBI Processing . VLBI processing, with the exception of beam-forming and SKA1

imaging in support of VLBI. is outside the scope of the SKA1

SKA1-SYS_REQ-2847 SKA1_Mid VLBI store the time-dependent antenna

weights

SKA1_Mid VLBI store the time-dependent antenna weights. SKA1_Mid shall be able

to store the time-dependent antenna weights used for each tied-array beam sum

SKA1-SYS_REQ-2851 SKA1_Mid VLBI relative sensitivity and coherence losses

SKA1_Mid VLBI relative sensitivity and coherence losses. The SKA1_Mid

beamformer shall be able to weight the antenna inputs into the tied-array sums based

on relative sensitivity and coherence losses.

SKA1-SYS_REQ-2855 SKA1_Mid VLBI spectral resolution

SKA1_Mid VLBI spectral resolution. SKA1_Mid shall be able to generate VLBI

beams with a spectral resolutions different from the spectral resolution used for

imaging within the same VLBI sub-array


SKA1-SYS_REQ-2857 SKA1_Mid VLBI imaging and beamforming

SKA1_Mid VLBI imaging and beamforming SKA1_Mid shall be able to

simultaneously generate imaging data using all antennas in a VLBI sub-array, as well

as generating the VLBI beams.

SKA1-SYS_REQ-2859 SKA1_Mid VLBI spectral line and time domain

observation

SKA1_Mid VLBI spectral line and time domain observation SKA1_Mid shall be able

to generate VLBI beams optimised for either spectral line observations (to mitigate

spectral leakage) or time domain observations (to mitigate time smearing)

SKA1-SYS_REQ-2862 SKA1_Survey VLBI store the time-dependent antenna

weight

SKA1_Survey VLBI store the time-dependent antenna weight. SKA1_Survey shall be

able to store the time-dependent antenna weights used for each tied-array beam sum.

SKA1-SYS_REQ-2863 SKA1_Survey VLBI timestamp accuracy

SKA1_Survey VLBI timestamp accuracy. SKA1_Survey shall be able to generate

data from the VLBI beams with samples traceable to a timestamp with an accuracy of

1 nsec or better.

SKA1-SYS_REQ-2866 SKA1_Survey VLBI relative sensitivity and coherence

SKA1_Survey VLBI relative sensitivity and coherence. The SKA1_Survey

beamformer shall be able to weight the antenna inputs into the tied-array sums based

on relative sensitivity and coherence losses.

SKA1-SYS_REQ-2870 SKA1_Survey VLBI spectral resolution

SKA1_Survey VLBI spectral resolution. SKA1_Survey shall be able to generate

VLBI beams with a spectral resolutions different from the spectral resolution used for

imaging within the same VLBI sub-array

SKA1-SYS_REQ-2872 SKA1_Survey VLBI imaging and beamforming

SKA1_Survey VLBI imaging and beamforming. SKA1_Survey shall be able to

simultaneously generate imaging data using all antennas in a VLBI sub-array, as well

as generating the VLBI beams.

SKA1-SYS_REQ-2873 SKA1_Survey VLBI spectral line and time domain

observation

SKA1_Survey VLBI spectral line and time domain observation. SKA1_Survey shall

be able to generate VLBI beams optimised for either spectral line observations (to

mitigate spectral leakage) or time domain observations (to mitigate time smearing).

PDR03EchoSign Document History February 09, 2015

Created: February 09, 2015

By: Verity Allan ([email protected])

Status: SIGNED

Transaction ID: XJEEYJP37E5NW7Z

“PDR03” HistoryDocument created by Verity Allan ([email protected])February 09, 2015 - 3:04 PM GMT - IP address: 131.111.185.15

Document emailed to Ferdl Graser ([email protected]) for signatureFebruary 09, 2015 - 3:05 PM GMT

Document viewed by Ferdl Graser ([email protected])February 09, 2015 - 3:06 PM GMT - IP address: 105.184.40.35

Document e-signed by Ferdl Graser ([email protected])Signature Date: February 09, 2015 - 3:06 PM GMT - Time Source: server - IP address: 105.184.40.35

Document emailed to Paul Alexander ([email protected]) for signatureFebruary 09, 2015 - 3:06 PM GMT

Document viewed by Paul Alexander ([email protected])February 09, 2015 - 6:44 PM GMT - IP address: 131.111.185.15

Document e-signed by Paul Alexander ([email protected])Signature Date: February 09, 2015 - 6:44 PM GMT - Time Source: server - IP address: 131.111.185.15

Signed document emailed to Ferdl Graser ([email protected]), Paul Alexander ([email protected])and Verity Allan ([email protected])February 09, 2015 - 6:44 PM GMT

PDR.03 Requirements Analysis - ASTRONbroekema/papers/SDP-PDR/PDR03... · 2015. 7. 27. · Functions...

Documents

Transcript of PDR.03 Requirements Analysis - ASTRONbroekema/papers/SDP-PDR/PDR03... · 2015. 7. 27. · Functions...