SKA1 LFAA SPS SUB-ELEMENT REQUIREMENTS SPECIFICATIONska-sdp.org/sites/default/files/attachments/ska-tel-lfaa-0600028-01... · Web viewMsWord Word 2016 SKA-TEL-LFAA-0600028 MCCS

Name Designation Affiliation Signature

Authored by:

M. Waterson AA Domain Specialist SKAO

Date:

Owned by:

M. Waterson AA Domain Specialist SKAO

Date:

Approved by:

P. Gibbs Engineering Project

Manager

SKAODate:

Released by:

Jan Geralt Bij De Vaate

Consortium Lead AADC

Date:

MCCS REQUIREMENTS SPECIFICATION

Document number......................................................................SKA-TEL-LFAA-0600028Context.......................................................................................................................SPERevision........................................................................................................................01Author...............................M. Waterson, A. Magro. A. DeMarco, W. Turner, D. HaydenDate...............................................................................................................2018-10-31Document Classification............................................................FOR PROJECT USE ONLY Status.................................................................................................................Released

DOCUMENT HISTORYRevision Date Of Issue Engineering Change

NumberComments

A 2018-06-04 - Draft Template version released within consortium

01 2018-10-31 Released for CDR

DOCUMENT SOFTWAREPackage Version Filename

Wordprocessor MsWord Word 2016 document.doc

Block diagrams

Other

ORGANISATION DETAILSName Aperture Array Design and Construction Consortium

Registered Address ASTRONOude Hoogeveensedijk 47991 PD DwingelooThe Netherlands+31 (0)521 595100

Fax. +31 (0)521 595101Website www.skatelescope.org/lfaa/

CopyrightDocument owner Aperture Array Design and Construction Consortium

This document is written for internal use in the SKA project

Document No.:Revision:Date:

SKA-TEL-LFAA-0600028012018-10-31

FOR PROJECT USE ONLYAuthor: M. Waterson et al.

Page 2 of 52

TABLE OF CONTENTS

1 INTRODUCTION................................................................................................101.1 Purpose of Document..........................................................................................................10

1.1.1 Approach......................................................................................................................101.1.2 Verb Convention..........................................................................................................10

1.2 Scope of Document..............................................................................................................111.2.1 Identification................................................................................................................111.2.2 Intended Use of Document..........................................................................................11

1.3 Co-authors...........................................................................................................................111.4 MCCS Description, Context and Deployment.......................................................................12

1.4.1 MCCS Overview............................................................................................................121.4.2 External Interfaces.......................................................................................................121.4.3 Functional Breakdown.................................................................................................12

1.5 MCCS Operational Modes....................................................................................................13

2 APPLICABLE AND REFERENCED DOCUMENTS.....................................................162.1 Applicable documents.........................................................................................................162.2 Reference documents..........................................................................................................172.3 Reference Standards............................................................................................................18

3 MCCS ASSUMPTIONS.................................................................................19

4 MCCS REQUIREMENTS................................................................................204.1 Functional Requirements.....................................................................................................20

4.1.1 Signal Processing..........................................................................................................204.1.2 Synchronisation and Timing.........................................................................................214.1.3 Calibration....................................................................................................................224.1.4 Beam Forming and Pointing.........................................................................................234.1.5 Transient Capture........................................................................................................254.1.6 Observation Configuration...........................................................................................264.1.7 Monitoring and Control...............................................................................................274.1.8 Fault testing.................................................................................................................31

4.1.8.1 Off-line Diagnostic Tests...........................................................................................31

4.1.8.2 On-line Diagnostic Tests...........................................................................................32

4.1.9 Configuration Management.........................................................................................334.2 Internal interfaces................................................................................................................33

4.2.1 External interfaces.......................................................................................................344.2.1.1 To external...............................................................................................................34

4.3 Non-Functional Requirements.............................................................................................364.3.1 External interfaces.......................................................................................................36

4.3.1.1 LFAA to INFRA..........................................................................................................36

4.3.1.2 Electrical Interface...................................................................................................38

4.3.2 Software and Firmware Standards...............................................................................434.3.3 Occupational Health and Safety...................................................................................43

4.3.3.1 Fail Safe Design........................................................................................................43

4.3.3.2 Mechanical Safety....................................................................................................44


SKA-TEL-LFAA-0600028012018-10-31


Page 3 of 52

4.3.3.3 Electrical Safety........................................................................................................45

4.3.3.4 Equipment Safety.....................................................................................................45

4.3.3.5 Equipment Marking.................................................................................................46

4.3.4 Environmental Protection............................................................................................474.3.5 EMI and EMC................................................................................................................47

4.3.5.1 Electrical Network Electromagnetic Compatibility...................................................48

4.3.6 Availability, Maintainability and Reliability..................................................................484.3.6.1 Availability................................................................................................................48

4.3.6.2 Maintainability.........................................................................................................48

4.3.6.3 Design for Maintainability........................................................................................49

4.3.7 Equipment Environment..............................................................................................504.3.8 Equipment Configuration Identification.......................................................................51


SKA-TEL-LFAA-0600028012018-10-31


Page 4 of 52

LIST OF FIGURESFigure 1-1: MCCS Operational States...................................................................................................15

LIST OF TABLESTable 1-1: MCCS Sub-element states and modes................................................................................13


SKA-TEL-LFAA-0600028012018-10-31


Page 5 of 52

LIST OF ACRONYMS AND ABBREVIATIONS

AA Aperture ArrayAAVS Aperture Array Verification SystemAD Applicable DocumentADC Analog to Digital converterAIV Assembly Integration and VerificationAPI Application programming interfaceAPIU Antenna Power Interface UnitARP Address Resolution ProtocolASIC Application Specific Integrated CircuitASKAP Australian Square Kilometre Array PathfinderAUS AustraliaAZ AzimuthBLU Bow-tie low-frequency ultra-wideband antennaBOM Bill of MaterialsBOOTP Bootstrap ProtocolCAD Computer Aided DesignCBF Correlator and BeamformerCDR Critical Design ReviewCI Configuration ItemCIN Configuration Item NumberCIRA Curtin Institute of Radio AstronomyCLK ClockCMB Cabinet Management BoardCOTS Commercial Off The ShelfCPF Central Processing FacilityCPLD Complex Programmable Logic DeviceCSIRO Commonwealth Scientific and Industrial Research OrgCSM Cameo System ModellerCSP Central Signal ProcessingCWDM Coarse Wavelength Division MultiplexingDAQ Data AcquisitionDDBH Digital Data Back HaulDDE Direction dependent effectsDDR Double data rateDSP Digital Signal ProcessingECP Engineering Change ProposalEL ElevationEM ElectromagneticEMI Electro Magnetic InterferenceENOB Equivalent number of bitsEoR Epoch of Re-ionisationFCA Fibre Cable AssemblyFEM Front End Module


SKA-TEL-LFAA-0600028012018-10-31


Page 6 of 52

FN Field NodeFNDH Field Node Distribution HubFO Fibre OpticFoV Field of ViewFPGA Field Programmable Gate ArrayFQDN Fully Qualified Domain NameFS Field StationFTE Full time equivalentFTP File Transfer ProtocolGSM Global Sky ModelGP Ground PlaneHPBW Half Power Beam WidthHW HardwareICD Interface Control DocumentICMP Internet Control Message ProtocolILS Integrated Logistics SupportIP Internet ProtocolIXR Intrinsic Cross-polarisation RatioINAF Italian National Institute for AstrophysicsINAU Infrastructure AustraliaINFRA AUS Infrastructure AustraliaIPPs Integrated Pulse ProfilesISO International Organisation for StandardisationIT Information TechnologyL2 Level 2L3 Level 3LFAA Low Frequency Aperture ArrayLINFRA Local InfrastructureLMC Local monitoring and ControlLNA Low Noise AmplifierLOFAR Low Frequency Aperture ArrayLRU Line Replaceable UnitLSM Local Sky ModelLVDS Low Voltage Differential SignallingM&C Monitor and ControlMCCS Monitor, Control and Calibration Sub-systemMRO Murchison Radio-astronomy ObservatoryMWA Murchison Widefield arrayNF Noise FigureNRE Non-recurring engineeringNPV Net present valueNSDN Non-Science Data NetworkNTP Network Time ProtocolPaSD Power and Signal Distribution SystemPB Programme BlockPBS Product Breakdown StructurePCB Printed Circuit Board


SKA-TEL-LFAA-0600028012018-10-31


Page 7 of 52

PDF Portable Document FormatPDR Preliminary Design ReviewPI Principal InvestigatorPLL Phase Locked LoopPML Power Maturity LevelPPS Pulse Per SecondPREADU Pre-Analogue to Digital UnitPSS Pulsar Search EnginePST Pulsar Timing EnginePV PhotovoltaicRAL Rutherford Appleton LaboratoryRAM Reliability and MaintenanceRD Reference DocumentRF Radio FrequencyRFI Radio Frequency InterferenceRFoF Radio Frequency signal over FibreRMS Root mean squareRPF Remote Processing FacilityS/N Signal to noiseSaDT Signal and Data TransportSAT.STFR.FRQ Synchronisation and Timing, Time and Freq DistributionSB Schedule BlockSciOps Science OperationsSDP Signal Data ProcessingSE Systems EngineerSELV Safety Extra Low VoltageSFDR Spurious Free Dynamic RangeSKA Square Kilometre ArraySKA1 SKA Phase 1SKA-LOW SKA low frequency part of the full telescopeSKAO SKA OfficeSLD Single Line DiagramSLL Side Lobe LevelSNMP Simple Network Management ProtocolSNR Signal-to-noise ratioSOW Statement of WorkSPEAD Streaming Protocol for Streaming Astronomical DataSPS Signal Processing Sub-systemSRMB Sub-rack Management BoardSSH Secure Socket ShellSW SoftwareTB Transient bufferTBC To Be ConfirmedTBD To Be DoneTBS To Be SuppliedTCP-IP Transmission Control Protocol – Internet ProtocolTEL SKA1 Telescope


SKA-TEL-LFAA-0600028012018-10-31


Page 8 of 52

TelMod Telescope ModelTFTP Trivial File Transfer ProtocolTM Telescope ManagerTPM Tile Processing ModuleTRL Technology Readiness LevelUCP Uniboard Control ProtocolUDP User Datagram ProtocolUPS Uninterrupted Power SupplyVHDL VHSIC Hardware Description LanguageVO Virtual ObservatoryVTY Virtual TeletypeWBS Work Breakdown Structure WDM Wavelength Division MultiplexingWP Work Package


SKA-TEL-LFAA-0600028012018-10-31


Page 9 of 52

1 Introduction

1.1 Purpose of Document

1.1.1 Approach

This document resides within a requirements capture tool (Jama Contour) and for each requirement statement includes relational links back to the Level 2 Requirements [AD22].This document is a living document that will converge on the requirements for the MCCS Sub-element. The convergence process is an iterative one between the SKA Office and the consortia involved with the Element design work.

At present, some requirement statements have no traceability link available back to the Level 2 Requirements. In these cases MCSS Level 2 Requirement Assumptions have been created as parent requirements. These assumptions are in a section that follows the requirements in this document. These assumptions must at some point be confirmed as valid, or revised if not.Each requirement identified within this document has a unique four digit identifier preceded by the prefix “SKA1-LFAA-MCSS_REQ-“. The identifier is generated by the requirements capture tool. It provides a useful reference tag and indicates where in the system hierarchy the requirement resides.Each requirement identifies the type of verification method.

The latest issued document takes precedence over the contents of the requirements capture tool. However, an issued Level 3 Requirement document represents a requirements capture tool baseline. The data-base baseline identifier is referenced in the document history.

Amendments to the document will be via change control. If accepted, amendments will be via the requirements capture tool. Re-issue of this document will require a new baseline and export from the requirements tool and subsequent submission and approval via the Document Management System.

1.1.2 Verb Convention

“Shall” is used whenever a statement expresses a convention that is binding. The verbs “should” and “may” express non-mandatory provisions. “Will” is used to express a declaration of purpose on the part of the design activity.


SKA-TEL-LFAA-0600028012018-10-31


Page 10 of 52

1.2 Scope of Document

1.2.1 Identification

The LFAA_MCCS Sub-element is assumed to include all of the associated equipment, facilities, material, software, hardware, policy, technical documentation, services, and personnel required for its operation. This requirement specification does not cover policy, technical documentation, services, or personnel required for its operation.This document covers the LFAA_MCCS aspects of the SKA1 Low Telescope and as such specifies the following product:

LFAA_MCCS TBD-000000

1.2.2 Intended Use of Document

This specification:1. Forms part of the SKA LFAA systems engineering baseline, as defined in the SKA1 LFAA SEMP

[TBD].2. Defines functional, performance, interface, environmental, physical, safety, logistic support,

regulatory (legal) and special design requirements which are an input to the engineering and development of the item.

3. Is the specification against which the LFAA_MCCS Sub-element will be sold-off (proven to be compliant to requirements).

4. Identifies the methods that will be used to verify that these requirements have been met when the item is submitted for acceptance.

This document is expected to be used by the LFAA Element and LFAA_MCCS Sub-element Engineering Team and the SKAO System Engineering Teams. This document will also be used as part of the Construction Procurement Package.

1.3 Co-authors

Name InstituteAndrea De MarcoAlessio Magro University of MaltaDaniel Hayden SKAOWallace Turner SKAOMark Waterson SKAO


SKA-TEL-LFAA-0600028012018-10-31


Page 11 of 52

1.4 MCCS Description, Context and Deployment

1.4.1 MCCS Overview

The context of the LFAA_MCCS Sub-element is captured within the SKA1 LFAA Architectural Design Document [RD1].

1.4.2 External Interfaces

The external interfaces to the LFAA_MCCS are covered in the applicable Interface Control Documents and are further elaborated in the SKA1 LFAA Architectural Design Document [RD1].

1.4.3 Functional Breakdown

MCCS performs the following basic functions: Create and manage observations, where an observation consists of one subarray containing

multiple stations, which in turn can be composed of multiple sub-stations Perform calibration and pointing coefficient calculation for running observations Manage TPMs, including downloading firmware, initialising and synchronising the boards

and firmware, and update required coefficients and configurations throughout the lifetime of an observation

Provide a transient buffer such that, when triggered by TM, buffered station beams can be forwarded to SDP

Expose maintenance functionality for fault finding, mitigation and correction Monitor and control TPMs, antennas and other hardware and software components, and

provide a reporting mechanism for generating reports Provide a logging mechanism and store logs for a period of time, where said logs should be

query-able to external parties Raise alarms and events to inform internal and external entities of state and other changes

of LFAA components Routinely perform status and diagnostic checks Provide an inventory database where labelled hardware components and cables are stored,

to be able to easily localise issues within the CPF Interact with external entities, including TM, SDP, CSP, operators, engineers and hardware

and software deployers


SKA-TEL-LFAA-0600028012018-10-31


Page 12 of 52

1.5 MCCS Operational Modes

The definition of the terms “States” and “Modes” is very diverse in the SE and software communities and it is generally accepted that States and Modes can be used interchangeably, and that there is no clearly defined difference. The strict definition of States and Modes is therefore considered to be not important in this document, and the terms are used quite loosely.However, they are generally used in the following sense:

Modes: refer to sets of behaviour or functionality that are needed to control an item. States: refer to sets of characteristics that are needed for reporting of an item’s condition.

MCCS implementation of states and modes is aligned with the document “SKA1 Control System Guidelines” [RD4].

Table 1-1: MCCS Sub-element states and modesAttribute Range Description and comments adminMode Set by an outside authority (operations via TM).

(read-write) ONLINE The tile can be used for scientific observing.

MAINTENANCE

The tile is not to be used for scientific observing but can be used for testing and commissioning. The LFAA is not aware of the higher observation goals and does not enforce this restriction; the LFAA executes commands received from TM. However, some test modes may be available only when the tile is set to MAINTENANCE mode.

OFFLINE The tile is not to be used at all; when adminMode=OFFLINE, the operational state=DISABLE.

NOT-FITTED Set by operations to suppress alarm generation.

opState(read-only)

LFAA rolls-up the operational state of all components used by the tile and reports the overall operational state for the tile.

OFF The tile is powered off

INIT The tile has been switched on and is initialising (TANGO device does a of POST test to check that device is operating properly)

STANDBY The Tile is in low power mode (I don’t know if low power mode has been formally specified for the Tile yet)

ON Tile is on (ready to be configured, or in observation)

DISABLE

The tile is administratively disabled (adminMode=OFFLINE, NOT_FITTED, or RESERVE); basic monitor and control functionality is available, but beam-forming capabilities are not available.

ALARMThe Quality Factor for at least one attribute is outside the pre-defined ALARM limits. Some or all functionality may not be available

FAULTAn unrecoverable fault has been detected. The tile is not available for use; maintainer/operator intervention is required .

UNKNOWN The tile is unresponsive, e.g., due to loss of communication


SKA-TEL-LFAA-0600028012018-10-31


Page 13 of 52

Attribute Range Description and comments

healthState(read-only)

OKDEGRADEDFAILED

The LFAA rolls-up attribute quality factors, states, and other indicators for all components used by the tile and reports the overall tile healthState.

obsState (read-only)

The server Observing State indicates status related to scan configuration and execution.

IDLE The tile is not processing input data and is not generating output products.

CONFIGURING Transient state entered when a command to re-configure the tile is received. The tile leaves this state when re-configuration is completed.

READY The tile enters READY when (re-)configuration has been completed; scan configuration is complete; the tile is ready to generate output data products. The parameters that require updates during the scan are being updated.

SCANNING The tile is generating tile beam output products. PAUSED When the command ‘pause scan’ is received, the tile

transitions to obsState=PAUSED, but tile beams continue to be produced and sent to the Station. The tile configuration remains as-is. The command ‘resume scan’ causes the tile to transition to SCANNING.

ABORTED The tile transitions to this state when a command ‘abort scan’ is received. In this state re-configuration, and any other on-going processing functions are stopped.

FAULT An unrecoverable error that requires operator intervention has been detected.


SKA-TEL-LFAA-0600028012018-10-31


Page 14 of 52

Figure 1-1: MCCS Operational States


SKA-TEL-LFAA-0600028012018-10-31


Page 15 of 52

2 Applicable and Referenced Documents

2.1 Applicable documents

The following documents are applicable to the extent stated herein. In the event of conflict between the contents of the applicable documents and this document, the applicable documents shall take precedence.

Ref ID Title Document Number Issue

[AD1] SKA Phase 1 System (Level 1) requirements specification

SKA-TEL-SKO-0000008 11

[AD2] SKA LOW Telescope Functional Architecture 100-0000000-001 02[AD3] LFAA Architecture Design Document SKA-TEL-LFAA-0200028 01[AD4] LFAA – CSP Interface Control Document 100-000000-004 03[AD5] LFAA – INAU Interface Control Document 100-000000-003 03[AD6] SaDT – LFAA Interface Control Document 100-000000-026 04[AD7] TM – LFAA Interface Control Document 100-000000-028 02[AD8] SKA1-Low Configuration Coordinates Set –

Complete Set SKA-TEL-SKO-0000422 03

[AD9] SKA EMI & EMC Standards and Procedures SKA-TEL-SKO-0000202 03[AD10] Deleted [AD11] SKA1 Low SDP – LFAA Interface Control Document 100-000000-033 01[AD12] Environmental Conditions for the SKA1 Low Site in

Australia 100-000000-009 01

[AD13] SKA1 System Baseline Design SKA-TEL-SKO-0000002 03[AD14] SKA Project Safety Management Plan SKA-TEL-SKO-0000740 01[AD15] Deleted [AD16] SKA1 Power Budget SKA-TEL-SKO-0000035 05[AD17] LFAA Internal Interface Control Document SKA-TEL-LFAA-0200030 01[AD18] SKA1 Low Configuration Constraints and

Performance Analysis SKA-TEL-SKO-0000557 01

[AD19] SKA RAM Allocation SKA-TEL-SKO-0000102 03[AD20] SKA1 Power Quality Standard Specification SKA-TEL-SKO-00000293 03[AD21] LFAA Field Station Layout Coordinates SKA-TEL-LFAA-0200052 01[AD22] LFAA Requirements Specification SKA-TEL-LFAA-0200026 01


SKA-TEL-LFAA-0600028012018-10-31


Page 16 of 52

2.2 Reference documents

The following documents are referenced in this document. In the event of conflict between the contents of the referenced documents and this document, this document shall take precedence. Ref ID Title Document Number Issue[RD1] SKA Operational Modes and Health Monitoring SKA-TEL-SKO-0000267 B[RD2] SKA Control System Guidelines (CS_Guidelines) SKA-TEL-SKO-0000656 01[RD3] SKA1 Operational Concept Document SKA-TEL-SKO-0000307 02[RD4] Deleted [RD7] EMI Protection and Threshold Levels for the SKA SKA.TEL.OFF.PAQA.RFI-SK0-TN-

001F

[RD8] Deleted [RD10] SKA Support Concept SKA-TEL-SKO-0000103 01[RD11] SKA Integrated Logistic Support Plan (ILSP) SKA-TEL-SKO-0000104 01[RD12] SKA1-Low Bandshape Requirements 100-000000-030 A[RD13] Beamformer and Calibration Report - SKA1-Low SKA-TEL-SKO-0000777 01[RD14] L1 and L2 stability requirements for SKA-Low SKA-TEL-LFAA-0200011 B[RD15] SKA1 Error Budgets SKA-TEL-SKO-0000641 01[RD16] SKA System budget - Low sensitivity budget SKA-TEL-SKO-0000823 B[RD17] SKA1 System budget - Brightness dynamic range SKA-TEL-SKO-0000677 A[RD18] RFI Characterisation and SKA1 signal chain design

considerationsSKA-TEL-SKO-0000492 01

[RD19] SKA System budget - Low spectral performance budget

SKA-TEL-SKO-0000636 01

[RD20] SKA System budget - Low System timing budget SKA-TEL-SKO-0000637 03[RD21] SKA1 Low Transient Buffer – Analysis,

Requirements, Budgets and ImplementationSKA-TEL-SKO-0000984 01

[RD22] Low Spatial and Spectral Beam Stability Budget SKA-TEL-SKO-0000XXX F[RD23] Field Node Detailed Design Document SKA-TEL-LFAA-0200038 01[RD24] SPS Detailed Design Document SKA-TEL-LFAA-0500035 01[RD25] MCCS Detailed Design Document SKA-TEL-LFAA-0600051 01[RD26] LFAA AIV Plan SKA-TEL-LFAA-0000022 01[RD27] LFAA Traceability and Compliance Matrix SKA-TEL-LFAA-0200048 01[RD28] Field Node Requirement Specification SKA-TEL-LFAA-0200036 01[RD29] SPS Requirement Specification SKA-TEL-LFAA-0500034 01[RD30] MCCS Requirement Specification SKA-TEL-LFAA-0600028 01


SKA-TEL-LFAA-0600028012018-10-31


Page 17 of 52

2.3 Reference Standards

The following standards are referenced in this document. In the event of conflict between the contents of the referenced documents and this document, this document shall take precedence.

Ref ID Title[RS1] Deleted[RS2] Deleted[RS3] Occupational Health and Safety (Commonwealth Employment) Act 1991[RS4] Safety of machinery - Functional safety of safety-related electrical, electronic and

programmable electronic control systems IEC 61508[RS5] Safety of machinery. Electrical equipment of machines general requirements IEC EN 60204-

1[RS6] Low voltage switchgear and controller gear IEC EN 60947-5-5[RS7] Safety of machinery. Safety-related parts of control systems general principles for design

ISO 13849-1[RS8] Generic Requirements for Network Equipment in the Outside Plant (OSP) GR-3108-Core

Issue 3[RS9] Equipment Engineering Environmental conditions and environmental tests for

telecommunications equipment Part 1-2: Classification of environmental conditions Transportation ETS 300 019-1-2

[RS10] Safety of machinery -- General principles for design -- Risk assessment and risk reduction ISO 1200-2 clause 5

[RS11] Fundamental SKA Software & Hardware Description Language Standards SKA-TEL-SKO-0000661 Rev 2

[RS12] Equipment Engineering Environmental conditions and environmental tests for telecommunications equipment Part 1-2: Classification of environmental conditions Transportation ETS 300 019-1-2


SKA-TEL-LFAA-0600028012018-10-31


Page 18 of 52

3 MCCS AssumptionsThe following table contains the list of MCCS Assumptions. Assumptions are created for each instance of a MCCS requirement which is not derived from an LFAA requirement but whose existence is necessary.

ID Name DescriptionSKA1-MCCS_ASS-5

Configuring reporting interface

When TM requests the LFAA LMC to configure the monitoring of points, alarms, events, the level of reporting shall comply with the information logs

SKA1-MCCS_ASS-9

Calibration synchronization

Calibration coefficients for a frequency channel shall be applied to every antenna in a station at the same time

SKA1-MCCS_ASS-10

Pointing synchronization

Pointing coefficients for a station beam shall be applied to every antenna in a station at the same time

SKA1-MCCS_ASS-11

Pointing control coordinates

TM sends individual Sky Coordinate Sets with an update rate of not more than 10 Hz to the LFAA LMC per station beamforming instance

SKA1-MCCS_ASS-17

Firmware loading

LMC shall be capable of downloading firmware to TPM flash and loading firmware

SKA1-MCCS_ASS-19

Data acquisition Control data from TPM shall be received by LFAA software and dumped to disk, or processed where required

SKA1-MCCS_ASS-20

Correlation LFAA shall correlate channelized data from all antennas in a station and generate cross-correlation matrices to be used for calibration

SKA1-MCCS_ASS-22

Bandpass flattening

LFAA must calculate coefficients to flatten the bandpass to within 1.5dB. Coefficient updates should happen periodically

SKA1-MCCS_ASS-23

Hardware usage Where applicable, LMC shall monitor hardware usage and report appropriate statistics (applicable to servers and switches)

SKA1-MCCS_ASS-25

Network configuration

LFAA shall be responsible for defining it's internal networking infrastructure, subnet and IP assignment, traffic balancing and so on

SKA1-MCCS_ASS-29

Software versioning

It shall be possible to instruct the LFAA to use a specific version for a software component and firmware bitfile

SKA1-MCCS_ASS-30

Software updates

When software component updates are available, LFAA shall deploy this updates to the running system with minimal disruption to running observation (avoid restarts where possible)

SKA1-MCCS_ASS-31

Web-based interface

A web-based interface to be used locally and remotely shall be provided by LFAA

SKA1-MCCS_ASS-32

Engineering interface

A command-line (tunneling) interface to be used locally and remotely shall be provided by LFAA

SKA1-MCCS_ASS-33

Remote power-up and power down

LFAA shall implement remote power up and power down functionality. Power-up should be staged across the CPF to avoid overloading the power generators


SKA-TEL-LFAA-0600028012018-10-31


Page 19 of 52

https://skaoffice.jamacloud.com/perspective.req?projectId=254&docId=766723






























4 MCCS Requirements

4.1 Functional Requirements

4.1.1 Signal Processing

SKA1-LFAA_MCCS_REQ-126

RFI flaggingWhen commanded by TM, MCCS shall accept a list of frequency channels, amplitude levels and integration periods for which the packets of the station-beam data "RFI flagged" state shall be set, and transmit this to the SPS (TPMs). Two special cases shall be permitted: If the level threshold is set to a value of 0 (TBC) the beam data packet shall always be flagged regardless of level. If the level is set to (maximum word value, TBC), RFI flagging shall be disabled for this channel/beam.

Parent SKA1-LFAA-172, SKA1-LFAA-204Verification FT Cycle


Spectral channelsMCCS shall independently control and calibrate a fixed number of frequency channels conforming to the SPS coarse channelization filter design parameters as described in the LFAA internal ICD [AD17].

Parent SKA1-LFAA-192, SKA1-LFAA-204Verification FT Cycle and Analysis


Instantaneous bandwidthThe MCCS shall provide resources sufficient to permit control, monitor and calibration processing of no less than 300 MHz of aggregate bandwidth per polarisation. The desired bandwidth, specified by TM as sets of discrete coarse channels individually allocated to beams, shall be processed continually for the duration of the given observation period or until commanded to stop.

Parent SKA1-LFAA-123Verification FT Cycle and Demonstration


Channelisation frequency channel amplitude responseMCCS shall, in a format conforming to the LFAA-CSP ICD [AD4], make available via TM the correction coefficients applied to coarse channel levels to normalize their amplitude response.

Parent SKA1-LFAA-141, SKA1-LFAA-44Verification FT Cycle and Demonstration


SKA-TEL-LFAA-0600028012018-10-31


Page 20 of 52














Clipped data flaggingMCCS shall supply a value to SPS representing the boundary of acceptable saturation (SPS shall flag pre-channelised samples that exceed this value).


4.1.2 Synchronisation and Timing


Network Time Protocol (NTP)All MCCS client devices and applications that require synchronised telescope network time shall comply with the Network Time Protocol version 4 standard, RFC 5905



Provision of NTP servicesMCCS shall provide a local NTP service referenced to the SaDT system-level time service for use by all devices physically connected to the LFAA data and management networks.

Parent SKA1-LFAA-102Verification FT Cycle


Synchronous Time StampingMCCS shall command SPS in each station to synchronize the internal time stamping to a 1PPS signal transition.

Parent SKA1-LFAA-137, SKA1-LFAA-204Verification FT Cycle and Demonstration


Pointing synchronization MCCS shall compute and transmit pointing delay and delay-rate coefficients for all station beams in a sub-array to the TPMs involved in advance of a triggering action which will cause the parameters to be applied simultaneously to all antennas in the station/sub-stations.

Parent SKA1-LFAA-167Verification FT Cycle, Demonstration and Analysis


Calibration synchronization MCCS shall compute and transmit calibration coefficients per frequency channel for all station beams in a sub-array to the TPMs involved in advance of a triggering action which will cause the parameters to be applied simultaneously to all antennas in the station/sub-stations.

Parent SKA1-LFAA-50Verification


SKA-TEL-LFAA-0600028012018-10-31


Page 21 of 52



















4.1.3 Calibration


Real time calibrationMCCS shall implement on-line station beam calibration such that all active coarse frequency channels are calibrated at least once every 10 minutes.



Global sky modelThe MCCS shall use a Local Sky Model in order to generate calibration coefficients. This model shall be updated using a subset of the Global Sky Model pulled from SDP, according to the SDP-LFAA ICD [AD15].



Correlation MCCS shall correlate channelized data from all antennas in a station/sub-station and generate cross-correlation matrices to be used for calibration.

Parent SKA1-LFAA-50Verification Demonstration, Analysis and FT Cycle


Calibration accuracyMCCS shall implement calibration calculations according to a TBD algorithm to correct per-antenna amplitude and phase response at each frequency channel with an update rate of less than 600 seconds according to algorithm and accuracy conforming to (TBD) calibration error budget.



Polarisation correctionThe calibration coefficients calculated and forwarded to SPS by MCCS should also compensate for polarization for each antenna (x-y pair) and frequency channel.

Parent SKA1-LFAA-110, SKA1-LFAA-204, SKA1-LFAA-50Verification Demonstration and FT Cycle


Bandpass flattening Calibration coefficients calculated by MCCS should also flatten the bandpass to within 1.5dB.

Parent SKA1-LFAA-50Verification Demonstration, Analysis and FT Cycle


SKA-TEL-LFAA-0600028012018-10-31


Page 22 of 52




















Aperture Array DDEThe MCCS shall have direction dependent models for the beams of each station (or sub-station) with an accuracy of 1% of peak gain in the beam center in amplitude and 0.01 radians in phase at the half-power points to be used for calibration and imaging.



Calibration transferThe beam model shall be well enough known and stable to permit transfer of calibration seamlessly between beams and pointing directions such that the change in calibration due to the telescope (as compared to the environment or the source) shall be less than 0.7% in amplitude and 0.07 radians in phase.



Normalisation of station gainsMCCS shall match station beam power as a function of frequency across stations within a margin of TBD %.

Parent SKA1-LFAA-105Verification FT Cycle and Analysis


Glass Box CalibrationMCCS shall store and when commanded, shall provide the necessary information to TM such that TM can reconstruct or restore calibration and pointing coefficients.


4.1.4 Beam Forming and Pointing


Beam pointing modelMCCS shall implement a model which translates from topocentric Az, El (Sky Coordinate set supplied by TM) to the delay and delay rate per antenna required to steer the beam.This model must include any known imperfections in the geometry of the station (e.g. orientation) and any other effects that can be reproducibly corrected in software. Parameters of the model will be stored by and downloaded from TM, but the calculation happens in MCCS.

Parent SKA1-LFAA-167Verification Demonstration and FT Cycle


SKA-TEL-LFAA-0600028012018-10-31


Page 23 of 52

















Beam pointing accuracyMCCS will command delay and delay rates for individual antennas to SPS with an accuracy of better than 1.70 ps and a rate sufficient for a linear approximation to be valid.

Parent SKA1-LFAA-135, SKA1-LFAA-204Verification Demonstration and FT Cycle


Beam pointing angle rangeMCCS shall accept commands to steer and form beams at all possible azimuth and elevation angles.



Beam pointing control coordinates MCCS shall receive individual Sky Coordinate Sets from TM, per station beamforming instance, with an update rate of not more than 10 Hz, in accordance with the TM to LFAA ICD [AD7] .



Multiple beam capabilityMCCS shall control and monitor up to 8 beams (dual polarization) from each station within a sub-array, which can be independently pointed.

Parent SKA1-LFAA-134Verification Demonstration


Multiple beam widthsMCCS shall control and monitor beams that have different frequency and channel selections independent of each other (where independence allows identical, overlapping or non-overlapping). The independence allows each of one of the beams to have a non-contiguous bandwidth.



SKA-TEL-LFAA-0600028012018-10-31


Page 24 of 52
















4.1.5 Transient Capture


Transient buffer sizeMCCS, when configured, shall store digitized beamformed voltage data, with 2-bit or better sampling, for at least 150 MHz of continuous or non-continuous frequency range within the observed frequency range, in both polarizations, from a configurable subset up to all of the station/sub-station beams, covering at least 900 seconds.



Transient buffer transfer to SDPWhen commanded by TM, MCCS shall transfer transient buffer data to SDP via SADT with a data rate of 80Gb/sec (in accordance with the SDP to LFAA ICD [AD15]), independently for each sub-array, and according to the configuration set by TM (in accordance with the TM to LFAA ICD [AD7]).



Transient capture consecutive triggersMCCS shall restart buffering beam data into the transient buffer at most 45 minutes after the last trigger received from TM.



Transient capture: TM to LFAA latencyMCCS shall have a latency of no more than 1 second from the time it receives a command to dump the transient buffer from TM until the time it starts transmitting the buffered data to SDP.



Transient buffer configurationAs configured by TM, the MCCS shall in turn configure the SPS to send station beams for buffering to MCCS by specifying:- frequency window (per TPM) (continuous or not)- 8-bit or re-sampling to 2 or 4-bit- number and identification of station/sub-station beams



SKA-TEL-LFAA-0600028012018-10-31


Page 25 of 52

















Pause sending of transient dataMCCS shall command SPS to pause sending beam data if MCCS is not able to buffer it (e.g. while the buffer is frozen during read-out), and thereafter command SPS to resume, in accordance with the LFAA Internal ICD [AD17].

Parent SKA1-LFAA-186, SKA1-LFAA-204Verification

4.1.6 Observation Configuration


Maximum number of stationsMCCS shall provide configuration, control and monitoring of up to 512 stations (each consisting of 256 dual polarised antenna signal chains).

Parent SKA1-LFAA-108, SKA1-LFAA-115, SKA1-LFAA-103Verification FT Cycle


Mode transitionThe MCCS shall complete all internal reconfiguration to support any observing mode changes in less than 30 seconds, assuming that the system is already initialised (a full calibration cycle has been performed).



Subarraying MCCS, when commanded, shall assign station resources as independent groups (sub-arrays) that can be configured and operated independently of each other as described in the TM-LFAA ICD [AD7].



Subarray membershipAny LFAA beam shall be assigned independently to one sub-array at a time.



Subarray granularityMCCS shall support sub-arrays containing an integer number of stations between 0 (none) and all (512).


SKA1- Subarray independenceDocument No.:Revision:Date:

SKA-TEL-LFAA-0600028012018-10-31


Page 26 of 52




















LFAA_MCCS_REQ-23

MCCS shall configure, monitor and control each sub-array independently of, and concurrently with all others.



Subarray scheduling block set-up timeOn receiving a subarray configuration request from TM, MCCS shall configure LFAA resources to be ready for an observation in less than a TBD subset of 30 seconds.



Software & Firmware ManagementMCCS shall provide the capability to store, manage and transmit software, OS, and firmware images to SPS components as commanded, to support configuration, maintenance and upgrade of these subsystems.

Parent SKA1-LFAA-205, SKA1-LFAA-204, SKA1-LFAA-68Verification Demonstration and FT Cycle


Configuring reporting interface When TM requests the MCCS to configure the monitoring of points, alarms, and events, the level of reporting shall comply with the information logs.



Support for sub-stationsWhen configuring an observation, MCCS shall accept from TM, and transfer to SPS, for each beam, a per-antenna gain map (256x2) which is used to set the weight (amplitude gain coefficient) of antennas which contribute to a beam. Support for sub-stations is achieved by setting weights for antennas which do not contribute to the beam to zero.


4.1.7 Monitoring and Control


Monitoring and controlThe control and monitoring structure of MCCS shall be in accordance with the guidelines as defined in the SKA1 Control System Guidelines [RD2].

Parent SKA1-LFAA-205Verification Demonstration and Analysis


SKA-TEL-LFAA-0600028012018-10-31


Page 27 of 52



















Per-antenna average RF powerMCCS shall be capable of reading, from the SPS, the RMS value for each antenna.

Parent SKA1-LFAA-198, SKA1-LFAA-204, SKA1-LFAA-50Verification FT Cycle


Hardware usage MCCS shall monitor hardware usage and report appropriate statistics of all servers and switches within LFAA.



Monitor and report operational state MCCS shall monitor its operational state and make available the information upon request in line with the software standard [ TBD ref].



Network M&CMCCS shall provide monitoring and control functions for LFAA network components, consistent with system-level network policies [TBD]. This includes subnet and IP assignment, traffic balancing, status/health reporting, and beamformed data stream through appropriate packet statistics.



Data acquisition Control data from TPM shall be retrieved by MCCS software and dumped to disk, or processed where required.



Subarray station failure flaggingWhen performing observations, MCCS shall detect and report to TM failed stations immediately after detection of the failure.

Parent SKA1-LFAA-161Verification Demonstration and FT Cycle.


SKA-TEL-LFAA-0600028012018-10-31


Page 28 of 52




















Failure and health reportingThe MCCS shall identify all failures and report the health status of the following LRUs to the Telescope Manager (TM):

PyramidAntenna Power Interface Unit

Antenna Power Supply Module

Tile Processing Module

32-Port 40GBE Data switch

PPS/10Mhz Clock Distribution Unit

Rack Power Supply Unit

Rack Cooling System

Data Switch Rack Interconnect

MCCS Rack Assembly Data Switch

MCCS Servers

MCCS Rack Cooling System

Parent SKA1-LFAA-198Verification Demonstration and FT Cycle.


Equipment shutdown on failure MCCS shall autonomously detect and shut-down affected equipment in accordance with the LFAA to INFRA ICD [AD5], when any of the following conditions occur:

1. an over-current condition occurs in a rack;2. an over-temperature condition occurs in an LRU.

Parent SKA1-LFAA-82Verification FT Cycle & Analysis


Alarm latencyLatency from the time that MCCS detects that a measurement has crossed an alarm set-point until it reports this alarm to TM shall be no more than 0.2 seconds.



SKA-TEL-LFAA-0600028012018-10-31


Page 29 of 52











Low power mode - MCCSMCCS hardware components, except for start-up and safety-critical components (ie. Head/Ghost server and networking components), shall support a Low-Power mode which reduces their power consumption to less than 5% of nominal operating power. MCCS hardware components shall continue to communicate with the start-up and safety-critical components while in Low Power Mode.



Low power mode - LFAA componentsMCCS shall provide control and monitoring of LFAA components supporting Low-Power Mode and initiate transition to or from this state when commanded by TM.



Low power mode on power applicationOn start-up, MCCS shall enter the Low-Power mode mode until commanded by TM to transition to a specific state or mode.



Remote power-up and power down MCCS shall implement remote power up and power down functionality. As commanded by TM, power-up should be staged across the CPF to avoid overloading the power generators.

Parent SKA1-MCCS_ASS-33Verification FT Cycle


Fail safe stateMCCS equipment that would otherwise present a safety hazard when subjected to an unplanned loss of main electrical power or main control function, shall enter a designated fail safe state.



Fail safe warningsWhere transitioning to a designated fail safe state represents a hazard, components of the MCCS shall issue continued warnings for the duration of the transition.



SKA-TEL-LFAA-0600028012018-10-31


Page 30 of 52




















Fail safe recoveryOnce a transition to a designated fail-safe state is triggered, the MCCS shall complete the transition and remain in the designated fail-safe state until commanded otherwise.



User access control MCCS shall provide hardware and communication access to any authenticated user. Note: this means that user authentication for access to MCCS is provided by MCCS with TM owning the user database.


4.1.8 Fault testing

4.1.8.1 Off-line Diagnostic Tests


MCCS off-line built-in self-test capability When commanded and with the MCCS Administrative Mode set to OFFLINE, MCCS shall perform diagnostic tests to detect and isolate LRU and sub-element level faults.

Parent SKA1-LFAA-198Verification Analysis


MCCS off-line fault detection performance When commanded and the MCCS Administrative Mode set to OFFLINE, MCCS built-in diagnostic self-test capability shall detect and report TBD% of all critical sub-element failures. Note: A Critical Failure is a failure that would prevent MCCS being "Operationally Capable".



MCCS off-line fault isolation performance When commanded and with the MCCS Administrative Mode set to OFFLINE, MCCS shall isolate TBD% of all failures down to a LRU level.Note: The MCCS maintainer functions as part of the fault isolation mechanism by removing and replacing suspect LRUs.



SKA-TEL-LFAA-0600028012018-10-31


Page 31 of 52

















MCCS off-line communications fault detection When commanded and with the MCCS Administrative Mode set to OFFLINE, MCCS shall detect and report TBD% of sub-element LRU to LRU and LRU to external interface communication path faults.



MCCS off-line memory and calculation fault detection When commanded and with the MCCS Administrative Modes set to OFFLINE, MCCS shall detect and report the following faults:

1. Stuck or incorrect memory cells, whether a direct fault or manifested as such,

2. Calculation faults that may lead to incorrect data products, whether a direct fault or manifested as such.

Parent SKA1-LFAA-198Verification Analysis and FT Cycle

4.1.8.2 On-line Diagnostic Tests


MCCS on-line built-in self-test capability While the MCCS Administrative Mode is set to ONLINE or MAINTENANCE, MCCS shall perform diagnostic tests to detect and isolate LRU and sub-element faults.



MCCS on-line fault detection performanceWhile the MCCS Administrative Mode is set to ONLINE or MAINTENANCE, MCCS shall detect and report TBD% of all Critical Failures. Note: A Critical Failure is a failure that would prevent the MCCS of being "Operationally Capable".



MCCS on-line fault isolation performance While the MCCS Administrative Mode is set to ONLINE or MAINTENANCE, the MCCS shall isolate more than TBD% of all failures down to a LRU level.Note: MCCS maintainer implements part of the fault isolation capability by removing and replacing suspected LRUs to isolate the faulty LRU.



SKA-TEL-LFAA-0600028012018-10-31


Page 32 of 52

















MCCS on-line communications fault detection While the MCCS Administrative Mode is set to ONLINE or MAINTENANCE, MCCS shall detect all utilized sub-element LRU to LRU and LRU to external LRU communication path faults with a detection probability of at least TBD%.


4.1.9 Configuration Management


Local databaseThe MCCS shall maintain a database of identification parameters for all hardware entities which is synchronized with a Global Configuration database. The information shall include IDs and physical location coordinates (to be used for pointing calculations) of Field Nodes and their constituent antennas as well as connection-path mapping and other information needed for maintenance.

Parent SKA1-LFAA-120, SKA1-LFAA-121, SKA1-LFAA-119, SKA1-LFAA-167Verification Inspection


Software versioning It shall be possible to instruct LFAA products to use a specific version for a software component and firmware bitfile.



Software updates - disruption to observationWhen software component updates are available, MCCS shall deploy these updates to the running system with minimal disruption to running observation (avoid restarts where possible).


4.2 Internal interfaces


MCCS to Field NodeThe interface between MCCS and Field Node shall be compliant with the interface definitions listed in the LFAA Internal Interface Control Document, document number [AD17].

Parent SKA1-LFAA-204Verification Inspection


SKA-TEL-LFAA-0600028012018-10-31


Page 33 of 52

















MCCS to SPSThe interface between MCCS and SPS shall be compliant with the interface definitions listed in the LFAA Internal Interface Control Document, document number [AD17].


4.2.1 External interfaces

4.2.1.1 To external


Engineering interface A command-line (tunneling) interface to be used locally and remotely shall be provided by MCCS.

Parent SKA1-MCCS_ASS-32Verification Inspection


Web-based interface A web-based interface to be used locally and remotely shall be provided by MCCS.

Parent SKA1-MCCS_ASS-31Verification Inspection


SADT to LFAA interfaceMCCS shall be compliant with the interface definitions listed in the SADT to LFAA Interface Control Document, document number 100-000000-026 [AD6], for the following sub-interfaces:- I.S1L.SADT_LFAA.007- I.S1L.SADT_LFAA.009



TM to LFAA interfaceMCCS shall be compliant with the interface definitions listed in the TM to LFAA Interface Control Document, document number 100-000000-028 [AD7].



SKA-TEL-LFAA-0600028012018-10-31


Page 34 of 52

















SDP to LFAA interfaceMCCS shall be compliant with the interface definitions listed in the SDP to LFAA Interface Control Document, document number 100-000000-033 [AD11], for the following sub-interfaces:- I.S1L.SDP_LFAA.001- I.S1L.SDP_LFAA.002



SKA-TEL-LFAA-0600028012018-10-31


Page 35 of 52




4.3 Non-Functional Requirements

4.3.1 External interfaces

4.3.1.1 LFAA to INFRA


LFAA to Infra interfaceMCCS shall be compliant with the interface definitions listed in the LFAA to INFRA AUS Interface Control Document, document number 100-000000-003 [AD5], for the following sub-interfaces:- I.S1L.LFAA_INFRA-AUS.005- I.S1L.LFAA_INFRA-AUS.008- I.S1L.LFAA_INFRA-AUS.009



MCCS deployment locationMCCS shall be located in the Central Processing Facility in accordance with the latest approved version of the LFAA to INFRA ICD [AD5].


4.3.1.1.1 Environmental and Safety


MCCS occupational health and safetyMCCS equipment and operations shall comply with all applicable Australian Occupational Health and Safety legislation and regulations in accordance with the LFAA to INFRA ICD [AD5].

Parent SKA1-LFAA-87Verification Inspection and Analysis


MCCS safety certificationMCCS rack and LRU equipment shall be safety certified to AS/NZS 60950.11:2015 or equivalent in accordance with the LFAA to INFRA ICD [AD5].



SKA-TEL-LFAA-0600028012018-10-31


Page 36 of 52














[Useful] LFAA.MCCS environmental certification MCCS rack and LRU equipment shall be RoHS 2 (2011/65/EU) certified in accordance with the LFAA to INFRA ICD [AD5].



MCCS rack side-to-side stability MCCS racks shall be attached to adjacent racks in the same row to provide lateral stability in accordance with the LFAA to INFRA ICD [AD5].



MCCS rack forward-backward stability MCCS racks shall have a Centre Of Gravity (CofG) that is less than 50% of the rack height in the upward direction in accordance with the LFAA to INFRA ICD [AD5].



[Useful] LFAA.MCCS acoustic noise emission[Useful] MCCS acoustic noise emission sound pressure level shall be in accordance with the LFAA to INFRA ICD [AD5].


4.3.1.1.2 Mechanical Interface


MCCS rack size MCCS shall use racks with dimensions of less than or equal to 800mm wide x 1200mm deep x < 2000mm floor to top of cabinet in accordance with the LFAA to INFRA ICD [AD5].



MCCS rack weightThe mass of fully populated MCCS racks shall not exceed 620 kg in accordance with the LFAA to INFRA ICD [AD5].



MCCS rack count The MCCS rack count shall not exceed 4 in the CPF in accordance with the LFAA to INFRA ICD [AD5].


SKA-TEL-LFAA-0600028012018-10-31


Page 37 of 52























4.3.1.2 Electrical Interface


MCCS power qualityMCCS shall operate in compliance with the SKA1 Power Quality Standard Specification [AD20] in accordance with the LFAA to INFRA Interface Control Document [AD5].



MCCS phase load balancing The MCCS electrical load shall be balanced such that the difference in currents between any two of the three phases will nominally be less than 5% and not exceed 10% for periods greater than 2 minutes when the sub-element is fully powered in accordance with the LFAA to INFRA ICD [AD5].



MCCS power factorMCCS rack equipment shall have a power factor in accordance with the LFAA to INFRA ICD [AD5].



MCCS average power consumptionMCCS average power consumption shall not exceed 44 kW in accordance with the LFAA to INFRA ICD [AD5].



MCCS power draw rate of changeMCCS power draw rate of change shall be less than 20% of the maximum power draw averaged over a one second interval (TBC) during startup and mode transitions in accordance with the LFAA to INFRA ICD [AD5].



SKA-TEL-LFAA-0600028012018-10-31


Page 38 of 52

















MCCS harmonic current limitsMCCS equipment connected to the CPF electrical network shall be compliant with the IEEE 519-1992 part 11.5 standard or equivalent for Harmonic Current Limits under standard test conditions and setups in accordance with the LFAA to INFRA ICD [AD5].



MCCS rack power interface Each LFAA.MCCS rack shall connect to two INFRA Element CPF electrical power outlets via two 3 phase power cables (length >=2 meters) that have IEC 60309 (6H) 3P+N+PE 32A RED Cable Mount Plugs (Part Number: 888-231-NS).



MCCS rack peak power drawMCCS racks shall have a peak power draw of less than 34 kW (TBD) +20% for a maximum duration of 50 ms in accordance with the LFAA to INFRA ICD [AD5].



MCCS rack short circuit current survivability MCCS rack electrical protection circuitry shall have a Interrupt Rating (IR) and Short-Circuit Current Rating of not less than TBD kA in accordance with the LFAA to INFRA ICD [AD5].



MCCS rack safety earth connection MCCS racks shall have a safety earth connection point with a connection resistance of less than 0.1 Ohm as per the LFAA to INFRA ICD [AD5].



MCCS inrush currentThe LFAA.MCCS shall have an inrush current of less than three times the average current draw at the point of connection at any point of time, and should reach the steady state current value within one second after switch on.



SKA-TEL-LFAA-0600028012018-10-31


Page 39 of 52




















MCCS phase operability (voltage)The LFAA.SPS shall be operable with supplied voltage phase with a variation of up to 2% of the nominal voltage and 3% during unusual network and load configurations.



MCCS operable frequencyThe LFAA.MCCS shall be operable inside the following frequency deviation:

1. From Grid supply + 2% (49Hz to 51Hz)2. From Generating plant supply + 5% (47.5 to 52.5 Hz)



MCCS magnitude of supply voltage (steady state)The MCCS shall operate with supply voltage within + 10% (360V - 440V)



MCCS supply voltage transientsThe LFAA.MCCS shall be withstand the transient limits defined in IEC 62040-3 dynamic output performance classification 3


4.3.1.2.1 Electromagnetic Interface

4.3.1.2.1.1 Emissions


MCCS harmonic current emissionsMCCS equipment connected to the CPF electrical network shall be compliant with the IEC 61000-3-2 standard or equivalent for Harmonic Current Emissions under standard test conditions and setups in accordance with the LFAA to INFRA ICD [AD5].

Parent SKA1-LFAA-51, SKA1-LFAA-53Verification Inspection


SKA-TEL-LFAA-0600028012018-10-31


Page 40 of 52

















MCCS voltage fluctuations and flicker emissionsMCCS equipment connected to the CPF electrical network shall be compliant with the IEC 61000-3-3 standard or equivalent for Voltage Fluctuations and Flicker Emissions under standard test conditions and setups in accordance with the LFAA to INFRA ICD [AD5].



MCCS number of electromagnetic radiators MCCS shall contain at most 500 LRUs that radiate EMI at levels up to CISPR 22/32 or equivalent standard in the SKA Low telescope frequency range.Note: Rack level LRUs must be configured as per the LFAA design during radiated emissions certification. In other words, rack level LRUs must be populated with all components that contribute radiated emissions. If some components aren't present during certification, these components must be separately certified and be accounted for in the emitter count as specified above.

Parent SKA1-LFAA-51, SKA1-LFAA-53Verification Inspection and Analysis

4.3.1.2.1.2 Immunity


MCCS ESD immunity MCCS equipment susceptible to ESD shall be compliant with the IEC 61000-4-2 standard or equivalent standard for ESD immunity under standard test conditions and setups in accordance with the LFAA to INFRA ICD [AD5].



MCCS radiated, radio-frequency, electromagnetic field immunityMCCS equipment connected to the CPF electrical network shall be compliant with the IEC 61000-4-3 standard or equivalent for radiated, radio-frequency, electromagnetic field immunity under standard test conditions and setups in accordance with the LFAA to INFRA ICD [AD5].



SKA-TEL-LFAA-0600028012018-10-31


Page 41 of 52














MCCS electrical fast transient/burst immunity MCCS equipment connected to the CPF electrical network shall be compliant with the IEC 61000-4-4 standard or equivalent for electrical fast transient/burst immunity under standard test conditions and setups in accordance with the LFAA to INFRA ICD [AD5].



MCCS surge immunity MCCS equipment connected to the CPF electrical network shall be compliant with the IEC 61000-4-5 standard or equivalent for Surge immunity under standard test conditions and setups in accordance with the LFAA to INFRA ICD [AD5].



MCCS immunity to conducted disturbances induced by radio-frequency fields MCCS equipment connected to the CPF electrical network shall be compliant with the IEC 61000-4-6 standard or equivalent for immunity to conducted disturbances, induced by radio-frequency fields under standard test conditions and setups in accordance with the LFAA to INFRA ICD [AD5].



MCCS power frequency magnetic field immunityMCCS equipment connected to the CPF electrical network shall be compliant with the IEC 61000-4-8 standard or equivalent for power frequency magnetic field immunity under standard test conditions and setups in accordance with the LFAA to INFRA ICD [AD5].



MCCS voltage dips, short interruptions and voltage variations immunity MCCS LRU equipment connected to the CPF electrical network shall be compliant with the IEC 61000-4-11 standard or equivalent for voltage dips, short interruptions and voltage variations immunity under standard test conditions and setups in accordance with the LFAA to INFRA ICD [AD5].



SKA-TEL-LFAA-0600028012018-10-31


Page 42 of 52
















4.3.1.2.2 Cooling Interface


MCCS rack thermal load The thermal load of MCCS racks shall be less than TBD kW in accordance with the latest approved version of the LFAA to INFRA ICD [AD5].

Parent SKA1-LFAA-175Verification Inspection and analysis

4.3.2 Software and Firmware Standards


MCCS software and firmware qualityMCCS software and hardware description language related deliverables shall comply with the "Fundamental SKA Software and Hardware Description Language Standards" [RS11].


4.3.3 Occupational Health and Safety


MCCS hazard eliminationMCCS shall be safe to the operators, maintainers and own equipment with categorization exceeding the acceptable levels defined in the SKA Project Safety Management Plan [AD14].


4.3.3.1 Fail Safe Design


MCCS fail-safe operationMCCS equipment shall operate in a locally fail-safe manner and not rely on external safety devices or measures to operate safely.



SKA-TEL-LFAA-0600028012018-10-31


Page 43 of 52














MCCS non-propagation of failuresMCCS equipment hardware failures and software errors shall be safe from creating hazardous conditions in interfacing elements and sub-elements.



MCCS fail safe provisionsMCCS shall not exhibit safety hazards in Categories I or II (ISO 45001) following an unplanned loss of main electrical power or main control functions.


4.3.3.2 Mechanical Safety


MCCS protruding obstacles MCCS equipment LRUs and racks shall eliminate or suitably protect obstacles that protrude and that may cause a safety hazard to personnel or equipment.



MCCS sharp edges and corners Exposed MCCS shall have:

corners rounded to a radius not less than 13 millimeters or suitably protected with covers or coatings;

sharp edges rounded to a radius not less than 0.75 millimeters.Parent SKA1-LFAA-79Verification Inspection


MCCS heavy equipment handholds MCCS equipment weighing more than 23 kg shall have lifting provisions to allow team lifting and/or the use of moving equipment.

Parent SKA1-LFAA-79Verification Analysis & Inspection


MCCS heavy equipment lifting arrangement MCCS equipment with a weight of more than 40 kg shall have an integral lifting arrangement to allow mechanical assisted lifting.

Parent SKA1-LFAA-87Verification Analysis & Inspection


SKA-TEL-LFAA-0600028012018-10-31


Page 44 of 52



















4.3.3.3 Electrical Safety


MCCS electrical installation The electrical wiring of all MCCS hardware shall comply with low voltage installation Standards (wiring of premises) AS/NZS 3000:2007, in addition to local, State and national legislation and Codes of Practice.



MCCS electrical circuit interlock The MCCS shall provide electrical circuit inter-locks to prevent personnel coming into contact with hazards that cannot otherwise be eliminated from design.


4.3.3.4 Equipment Safety


MCCS Thermal Overload Protection All LRUs within MCCS shall be equipped with thermal overload protection functionality to automatically power down the LRU when the MCCS operating temperature exceeds the LRU's safe operating temperature.



MCCS safety of equipment MCCS racks and equipment shall comply with IEC 60950-1 Information Technology Equipment - Safety Part 1 General Requirements or equivalent standard.



MCCS power interruption survivability MCCS racks shall survive a main power interruption at any time, without requiring a repair activity to restore it once power is restored.



SKA-TEL-LFAA-0600028012018-10-31


Page 45 of 52
















4.3.3.5 Equipment Marking


MCCS equipment identification and safety markings MCCS equipment shall in accordance with ISO 61310_2 or equivalent bear all markings necessary:

1. for its unambiguous identification;2. for its safe use;

and supplementary information given, as appropriate:1. permanently on the machinery;2. in accompanying documents such as instruction handbooks;3. on the packaging.



MCCS heavy equipment weight warning MCCS LRUs weighing more than 23 kg shall have a Weight Warning label.

Parent SKA1-LFAA-80, SKA1-LFAA-81Verification Analysis & Inspection


MCCS hazard warning marking MCCS equipment that presents a potential hazard shall display a label in accordance with ISO 7010 or equivalent.



MCCS label robustness MCCS labels shall be affixed for at least 50 years or the lifetime of the equipment, whichever is the smaller, and unlikely to come off during maintenance or as a result of the environment.



MCCS LRU electrostatic warning marking MCCS LRU equipment with electrostatic sensitive components shall be fitted with ESD warning labels.



MCCS essential off-the-shelf equipment EMC marking MCCS "off-the-shelf" LRU equipment shall as a minimum be CISPR 22 and 24 Class A or equivalent compliant over the SKA telescope frequency range.



SKA-TEL-LFAA-0600028012018-10-31


Page 46 of 52



















4.3.4 Environmental Protection


MCCS environmental protection regulationsMCCS shall be compliant with all local, State and national environmental protection legislation and regulations.



MCCS recycling and decomposition. MCCS equipment shall be compliant with environmental, ecological, safety, political and social legislation with regard to recycling and decomposition.



MCCS disposable equipment labellingMCCS disposable equipment should be labelled as such.



MCCS restriction of hazardous substances MCCS shall be compliant with the RoHS Directive 2011/65/EU (RoHS 2) or equivalent.

Parent SKA-LFAA-79Verification Analysis

4.3.5 EMI and EMC


MCCS EMI and EMC MCCS equipment shall be compliant with the emission and immunity standards in the SKA EMI/EMC Standards and Procedures [AD9].

Parent SKA1-LFAA-53, SKA1-LFAA-187, SKA1-LFAA-51, SKA1-LFAA-182Verification Test & Analysis


MCCS essential conducted and radiated electromagnetic emissions MCCS LRU equipment that radiate electromagnetic emissions in the SKA1 frequency range and that aren't within a shielded enclosure of a higher level LRU, shall at a minimum be compliant with the IEC 61000-6-4 standard or equivalent for conducted and radiated emissions under standard test conditions and setups in the SKA Low telescope frequency range as specified in the SKA EMI/EMC Standards and Procedures [AD9].

Parent SKA1-LFAA-51, SKA1-LFAA-53Verification Test & Inspection

SKA1- MCCS electromagnetic susceptibility Document No.:Revision:Date:

SKA-TEL-LFAA-0600028012018-10-31


Page 47 of 52




















LFAA_MCCS_REQ-203

MCCS equipment shall be compliant with the IEC 61000-6-2 standard or equivalent for susceptibility to conducted and radiated emissions under standard test conditions and setups.Note: Only LRUs with electrical or electronic components that are susceptible to EMI and that aren't within a shielded enclosure of a higher level LRU need to be checked for compliance.


4.3.5.1 Electrical Network Electromagnetic Compatibility


MCCS electricity network electromagnetic compatibility MCCS equipment shall follow the code of practice for the application of Electromagnetic Compatibility (EMC) standards and guidelines in electricity utility networks [AD9].


4.3.6 Availability, Maintainability and Reliability

4.3.6.1 Availability


MCCS Availability The MCCS shall have an Inherent Availability of more than 99.99%.



MCCS Operationally Capable MCCS shall remain Operationally Capable when any one processing LRU fails.


4.3.6.2 Maintainability


MCCS maintenance hours The MCCS shall require less than 0.25 FETs for corrective and preventative maintenance (O-Level and I-Level).


SKA1- MCCS mean time to repair


SKA-TEL-LFAA-0600028012018-10-31


Page 48 of 52
















LFAA_MCCS_REQ-209

The MCCS shall have a MTTR of less than 1 hour.



MCCS software update and maintenance down time The MCCS shall be designed not to require software and hardware maintenance down time, in excess of 1 hour per year (during steady state operations).


4.3.6.3 Design for Maintainability


MCCS in-system programmability MCCS programmable devices shall be in-system programmable in cases where the safety of personnel and equipment are not affected.

Parent SKA1-LFAA-68Verification Inspection & Analysis


MCCS software updates MCCS equipment shall facilitate major software updates within the LFAA maintenance time allocations.Note: Software maintenance down time (MDT) is defined as the time per year that LFAA is unavailable as result of a LFAA software defect repairs and general software maintenance activities during the telescope operational phase. It's assumed that all major LFAA software defects are removed during construction and the first year of warranty. LFAA software defect repairs and maintenance that don't require LFAA down-time are excluded from MDT.



MCCS maintenance provisionsMCCS repairable items shall have maintenance provisions such as test points, accessibility, and plug-in components.



MCCS LRU removal MCCS LRUs shall be mounted such that removal of any single LRU does not require the removal of other LRUs.


SKA1-LFAA_MCCS_REQ-

MCCS mounting preclusion MCCS shall include provisions, where cost-effective, to preclude incorrect


SKA-TEL-LFAA-0600028012018-10-31


Page 49 of 52




















225 assembly to eliminate the possibility of equipment damage or mis-operation.Parent SKA1_LFAA-70Verification Inspection


MCCS stand-offs and handles MCCS shall provide equipment handles and stand-offs to facilitate the installation and handling and to mitigate damage of the equipment during out-of-system repair.



MCCS mounting guides Where applicable, MCCS shall provide mounting guides and location pins on equipment to facilitate maintenance.



MCCS module labelling MCCS labelling of modules shall be in a conspicuous location, such that it is readable when the module is removed or installed in its intended operating environment, when such labeling doesn't impede functionality and/or performance.


4.3.7 Equipment Environment


MCCS Storage of Equipment MCCS equipment, while in its storage packaging, shall withstand, and shall operate to specification as defined herein after exposure to, the storage environmental conditions as defined in “Class 1.1: Weather protected, partly temperature-controlled storage locations” of the ETSI EN 300 019-1-1 standard and defined in BS EN IEC 60721-3-1.

1. Climatic Conditions 1K32. Biological Conditions 1B23. Chemical conditions 1C24. Dust and Sand conditions 1S25. Shock & Vibration Conditions 1M2



SKA-TEL-LFAA-0600028012018-10-31


Page 50 of 52















MCCS Transportation Environment All components and spares of the MCCS, in their transport packaging, shall be safe from damage while, and shall perform to specification as defined herein, after being transported under conditions as defined in "Class 2.2: careful transportation" of the ETSI EN 300 019-1-2 standard [37] and defined in BS EN IEC 60721-3-2:- Climatic conditions 2K5H- Biological conditions 2B3- Chemical conditions 2C1- Dust and Sand conditions 2S3- Shock & Vibration conditions 2M3



MCCS COTS operating environment The MCCS "off-the-shelf" equipment shall perform to specification as defined herein during operation under the environmental conditions as defined in the ETSI EN 300 019-1-3 standard for "Class 3.6: Telecommunication control room locations" or equivalent.



MCCS Seismic Resilience MCCS shall be designed and built in compliance with national and State regulations including AS 1170.4 (Importance level 3, design life 50 years) for seismic events resulting in a maximum peak ground acceleration of 1 m/s2, and shall survive and be fully operational after such events.

Note: Seismic events include underground collapses in addition to earthquakes.


4.3.8 Equipment Configuration Identification


MCCS serial and part numbers MCCS equipment items identified in the SKA Logistics Analysis and Configuration Item Plan as needing individual characterisation shall be marked with a label displaying a unique Serial Number and Part Number. The label should normally be in an easily visible location but may also include embedded identification for items such as embedded firmware/software.


SKA1- MCCS electronically readable or scannable ID


SKA-TEL-LFAA-0600028012018-10-31


Page 51 of 52














LFAA_MCCS_REQ-235

Where items in the MCCS require labelling, they shall be marked with a unique Electronically readable or scannable ID, such that the method of marking is in accordance with the SKA Logistic Analysis Plan and Configuration Plan. The ID may be serial number or part number or both or in some cases this may not be needed. The nature of the item, its environment and its use will determine the method.

Parent SKA1-LFAA-91, SKA1-LFAA-92Verification Demonstration


MCCS package marking All packaging of items used in MCCS shall be marked to uniquely identify the contents in accordance with the SKA Logistics Analysis Plan. The identification is by part number and serial number.



MCCS cable identification Each MCCS cable end shall carry an identifier that uniquely defines the connector it needs to connect to.



MCCS connector plate identificationAll MCCS connector plates shall carry identification labels for connectors.



SKA-TEL-LFAA-0600028012018-10-31


Page 52 of 52










