From SKA to SKAO: Early progress in SKA project construction.

From SKA to SKAO
Early Progress in the
SKA Project Construction
Juande Santander-Vela,
Head of Software Product Management
ICALEPCS’21 (October 2021)

SKA Status Update
Juande Santander-Vela
SKA SW Systems Engineer
4 Years Ago!

Slide /
The SKA Project and SKA telescopes
4

Studying HI to Enable SKA Science
Cosmic Dawn
(First Stars and Galaxies)
Galaxy Evolution
(Normal Galaxies z~2-3)
Cosmology
(Dark Energy, Large Scale Structure)
Cosmic Magnetism
(Origin, Evolution)
Cradle of Life
(Planets, Molecules, SETI)
Testing General Relativity
(Strong Regime, Gravitational Waves)
Exploration of the Unknown
Broadest range of
science of any
facility, worldwide

SKAO and SKA Telescopes
6
SKA Phase 2: 2500 dishes across Africa; 1,000,000 antennas across Australia
SKA-Low: 131,072 antennas spread across 65km SKA-Mid: 197 15m dishes spread across 150km.
Incorporates South Africa’s MeerKAT
•A global collaboration of 16 countries which will build and operate the next-generation radio
astronomy observatory
•Will be supported by a global network of SKA Regional Centres providing access to SKAO data
•7-8 year construction schedule. Cost ~€2B (2020 euros) for first 10 years
Slide /

Largest collecting area of
any radio array in the world

419,000m2
SKA1 LOW
Australia
~130,000 antennas
~130,000 antennas
HIGH
FREQUENCIES
~200 dishes
~200 dishes
33,000m2
SKA1 MID
South Africa
66 dishes
6,500m2
ALMA
Atacama Large Millimeter/
submillimeter Array, Chile
100m dish
7
,800m2
Effelsberg
Germany
MID
FREQUENCIES
ARRAYS SINGLE DISHES
71,000m2
500m dish
FAST
Five Hundred Meter Aperture
Spherical Telescope, China
27 dishes
13,200m2
JVLA
Karl G. Jansky Very Large Array, USA
52,000m2
LOFAR
Low Frequency Array for Radio
astronomy, Netherlands
34,000 antennas
At 110 MHz
30 dishes
48,000m2
GMRT
Giant Metrewave Radio Telescope, India
100m dish
7
,800m2
GBT
Green Bank Telescope, USA
76m dish
4,500m2
Lovell
UK
LOW
FREQUENCIES
The Square Kilometre Array (SKA) will be the world's largest radio telescope,
revolutionising our understanding of the Universe. The SKA will be built in
two phases - SKA1 and SKA2 - starting in 2018, with SKA1 representing a
fraction of the full SKA. SKA1 will include two instruments - SKA1 MID and
SKA1 LOW - observing the Universe at different frequencies.
A telescope's capacity to receive faint signals - called sensitivity - depends on its
collecting area, the bigger the better. But just like you can't compare radio
telescopes and optical telescopes, comparison only works between telescopes
working in similar frequencies, hence the different categories above.
The collecting area is just one aspect of a telescope’s capability though. Arrays
like the SKA have an advantage over single dish telescopes: by being spread over
long distances, they simulate a virtual dish the size of that distance and so can
see smaller details in the sky, this is called resolution.
42,000m2
Arecibo
Puerto Rico
305m dish
64 dishes
9,000m2
MeerKAT
South Africa
36 dishes
4,000m2
ASKAP
Australian SKA Pathfinder, Australia
2048 antennas
2,500m2
MWA
Murchison Widefield Array, Australia
64m dish
3,200m2
Parkes
Australia
Photo:
C
S
I
R
O
/
J
o
h
n
S
a
r
k
i
s
s
i
a
n
64m dish
3,200m2
SRT
Sardinia Radio
Telescope, Italy
P
h
o
t
o
:
R
o
b
e
r
t
o
M
u
r
a
7,000m2
300m x 35m
antenna
NRT
Nancay Radio Telescope, France
P
h
o
t
o
:
S
t
ation de radioastronomie de Nancay
NON-STEERABLE
30m dish
700m2
IRAM 30m
Spain
12 dishes
2,
100m2
IRAM NOEMA
Northern Extended
Millimeter Array, France
C
r
e
d
i
t
:
S
K
A
O
r
g
a
n
i
s
a
t
i
o
n
Photo: SK
A
Credit: SKA
Organi
s
a
t
i
o
n
Photo: CS
I
R
O
A
T
N
F
P
h
o
t
o
:
N
R
A
O
/
A
U
I
P
h
o
t
o
:
S
K
A
S
o
u
t
h
A
f
r
i
c
a
Photo: Top-Foto, A
s
s
e
n
Photo
:
N
C
R
A
-
T
I
F
R
P
hoto: JBCA, Uni of Manchest
e
r
Ph
o
t
o
:
M
P
I
f
R
/
N
.
J
u
n
k
e
s
Phot
o
:
N
R
A
O
/
A
U
I
Pho
t
o
:
A
L
M
A
(
E
S
O
/
N
A
O
J
/
N
R
A
O
)
,
C
.
P
a
d
i
l
l
a
Photo: H. Schweiker/WIYN
and
N
O
A
O
/
A
U
R
A
/
N
S
F
Credit: NAOC
P
h
o
t
o
:
©
2
0
1
7
I
R
A
M
Cloud
P
h
o
t
o
:
I
R
A
M
,
a
i
r
l
i
b
r
eprod

Slide /
SKA-Mid Site,
Karoo, South Africa
SKA-Low Site, Murchison,
Western Australia
SKA Global HQ,
Jodrell Bank, UK
SKA Partners – includes Members of
the SKA Organisation – precursor to the
SKAO –, current SKAO Member States*,
and SKAO Observers (as of June 2021)
African Partner Countries
* *
* * * *
*
SKAO and SKA Project World Map
8

Slide /
From SKA to SKAO and
Start of Construction
9

SKA Project Timeline
Distributed nature and very resilient
staff have help us a lot against
COVID-19 schedule impacts!

Slide /
Documentation Submitted to
Council for Approval
•SKA Observatory Establishment & Delivery Plan
•Details staffing and costs for the SKA
Observatory own delivery and supporting
functions: Business enabling functions,
Observatory operations, Observatory
development, and Construction support.
•SKA Phase 1 Construction Proposal
•Describes the science requirements for the
project; what the scope of the project is; how
the project will be executed, monitored, and
controlled; wider benefits of the project to
society; and a guide to the detailed project
documentation, reference information, and its
organisation
14

Recommendation
The Director-General recommends that the SKA Observatory Council approves
the commencement of the Construction of SKA-1 as described in the Technical Document
and in accordance with the Construction Proposal (Project Execution Plan documents
Revision 2) and the Staged Delivery Plan (Project Execution Plan documents Revision 3)
and supported by the Observatory Establishment and Delivery Plan, recognising that
the robust financial approvals, risk management and change management processes
already in place will ensure that the financial commitments and deliverables of the Project
remain clear and within the bounds of good governance.
www.skao.int
We recognise and acknowledge the
Indigenous peoples and cultures that have
traditionally lived on the lands on which
our facilities are located. T₀ in July 1st 2021!
Approved!
~30 years to this moment!

Slide /
Role of Software in the SKA Project
16

Receivers / Dish
Receivers / Dish
Receivers / Dish
Receivers / Dish
x 197
Central Signal Processor
(Correlator/Beam Former/
PSS/PST)
Science Data Processor
(Real Time Ingest, Real-Time and
Oﬄine Calibration, Oﬄine Data
Reduction)
Field Nodes
(256 antennas)
Field Nodes
(256 antennas)
Field Nodes
(256 antennas)
Field Nodes
(256 antennas)
x 512
PSS/PST)
Reduction)
150 km baselines
65 km baselines
~2 Pb/s → ~7 Tb/s ~5 Tb/s
~50 PFLOPS
~100 Gb/s
(300 PB/year)
~9 Tb/s ~5 Tb/s
~100 Gb/s
(300 PB/year)
SKA
Regional
Centre
Supercomputers
SKA
Regional
Centre
Supercomputers
SKA
Regional
Centre
Supercomputers
~50 PFLOPS
~130 PFLOPS
~130 PFLOPS
SKA Telescopes SKA Regional Centres
SKA1 Mid
SKA1 Low
Real-Time Calibration
Slide /
Software and the SKA
17

Receivers / Dish
Receivers / Dish
Receivers / Dish
Receivers / Dish
x 197
PSS/PST)
Reduction)
Field Nodes
(256 antennas)
Field Nodes
(256 antennas)
Field Nodes
(256 antennas)
Field Nodes
(256 antennas)
x 512
PSS/PST)
Reduction)
150 km baselines
65 km baselines
~2 Pb/s → ~7 Tb/s ~5 Tb/s
~50 PFLOPS
~100 Gb/s
(300 PB/year)
~9 Tb/s ~5 Tb/s
~100 Gb/s
(300 PB/year)
~50 PFLOPS
~130 PFLOPS
~130 PFLOPS
SKA Telescopes SKA
SKA1 Mid
SKA1 Low

cessor
ormer/
Reduction)
~5 Tb/s
~100 Gb/s
(300 PB/year)
SKA
Regional
Centre
Supercomputers
SKA
Regional
Centre
Supercomputers
S ~130 PFLOPS
escopes SKA Regional Centres

cessor
ormer/
Reduction)
~5 Tb/s
~100 Gb/s
(300 PB/year)
SKA
Regional
Centre
Supercomputers
SKA
Regional
Centre
Supercomputers
S ~130 PFLOPS
escopes SKA Regional Centres
Plus all control software!
And all digital signal
processing firmware

Slide /
The progress so far…
Current Status
21

•Work with teams started in August 2018
• Currently executing PI12!
•From one train to three trains:
• Data Processing
• Observation Management & Controls (Correlators)
• Services (Platform, Networks, System)
Scaling Agile Teams: SKA and SAFe
22
Slide /

Telescope Delivery Teams
Priorities driven by
TDTs; alignment
through PIs
Software deployed
and integrated at
product level

M
o
n
d
a
y
M
o
n
d
a
y
M
o
n
d
a
y
M
o
n
d
a
y
M
o
n
d
a
y
M
o
n
d
a
y
M
o
n
d
a
y
M
o
n
d
a
y
M
o
n
d
a
y
M
o
n
d
a
y
M
o
n
d
a
y
M
o
n
d
a
y
M
o
n
d
a
y
M
o
n
d
a
y
M
o
n
d
a
y
M
o
n
d
a
y
Solution Sync — Every Fortnight
Program Backlog Refinement — Every Week
PO Sync — Weekly
Scrum of Scrums — Weekly
Program I&A and
other prep.
(3 half days)
PI Planning (4-5 days)
Final Program Backlog Refinement:
Just in time for the Product Group
to prioritise Features for the PI.
Overall Project Synchronisation via Pre- and Post-PI Planning — Every PI
Defect Triage - Daily
Sprint
Planning
Sprint
Review
Sprint M.1
Sprint
Planning
Sprint
Review
Sprint M.2
Sprint
Planning
Sprint
Review
Sprint M.3
Sprint
Planning
Sprint
Review
Sprint M.4
Sprint
Planning
Sprint
Review
Sprint M.5
Sprint
Planning
Sprint
Review
IP Sprint M
Sprint
Planning
Sprint
Review
IP Sprint M
Team Standups - Daily
Telescope Delivery Teams - Agile Cadence
TDTs now doing PI planning
based on the Agile software
experience!

Performance Milestones
Integration Milestones
2027
2026
2025
2024
2023
2022
2021
9 10 11 12 13 15
14 16 17 18 19 20 22
21 23 24 25 26 28
27 29 30 31 32 34
33 35 36
Array Assembly (AA) 0.5
Array Assembly (AA) 1 Array Assembly (AA) 2 Array Assembly (AA) 3 Array Assembly (AA) 4
LOW PSI
P6
AA2 scale SDP for all
performance critical
steps (~AA2 data and
array size)
P7
performance critical steps
(~AA3 data and array size)
SAFe operational
SW AA1 release
First SAFe AA0.5
operational SW
release
P11
SAFe operational
SW AA3 release
P12
P10
P1
First integration of
software in a PSI
System (PSI LOW)
MID: ~Dec 24
LOW: ~Sep 24
MID: ~Jan 26
LOW: ~Oct 25
MID: ~Oct 26
LOW: ~Sep 25
MID: ~Jul 27
LOW: ~Jul 27
SAFe operational
SW AA2 release
S
W
S
o
l
u
t
i
o
n
TBC
Steady state
construction
capacity:
20% Solution
Enablers
50%
ART/Solution
Features
30% Other
capacity
P8
MID PSI
TBC
Key Business feature set Enabler feature set
Business, Enabler, and
Program milestones
P2
Functionally
complete MVP for
PSI Mid and Low
SAFe operational
SW AA4 release
First integration
in PSI Mid
SKAMPI Development
for PSI Mid and Low
SKAMPI
Development for
AA05
Support for SKAMPI PSI Integration Events
Support for
SKAMPI
System ITF
Integration
Support for SKAMPI AA05 Integration,
Testing and Commissioning
SKAMPI Development for AA1
Architectural Runway to AA05 Architectural Runway to AA1
IM1
First OMC and SDP
hardware on PSI Mid
Support for SKAMPI AA1
Integration, Testing and
Commissioning
Commissioning
Support for SKAMPI
AA3 Int., Testing &
Commissioning
Commissioning
SKAMPI
Development for
AA3
SKAMPI
Development for
AA4
Architectural Runway to AA2
Architectural
Runway to AA3
Architectural
Runway to AA4
IM2
First Dish Controller or
Emulator in PSI Mid
IM3
First OMC, CSP LMC, PSS, PST,
NSDN, SAT, SPFRx, Dish LMC
hardware on System ITF
IM4
First MID CBF
Hardware on
System ITF
IM5
Start of System ITF
Veriﬁcation Events
IM6
Start of AA05
Integration Events
IM7
End of AA05 System
SKA1 Mid
Milestones
SKA1 Low
Milestones
T0 C0
P2 P3 P9
P5
IL1
AAVS moved to
external
shelter
IL2
MCCS running
on AAVS
platform
IL3
MCCS operating
AAVS data
capture
Hot-season
tests
IL4 IL6
AAVS3 station
deployment
IL7
MCCS
operating
3 stations
IL8
3-station
interferometry
Hot-season
tests
IL9
AA0.5 Station
Deployment
IL10
Milestones
coming from
MCCS Roadmap.
Probably need
review.
Milestones
coming Mid
CI Flow
Diagrams
Milestones
coming the needs
to have proper
scaling of the
SAFe Operational
Software.
IL5
Beam Pattern
Testing
P4
Start small scale SDP
scaling (~3-5 nodes)
SKA Roadmap

Performance Milestones
Integration Milestones
2024
2023
2022
2021
9 10 11 12 13 15
14 16 17 18 19 20 22
21 23 24 25 26
Array Assembly (AA) 0.5
Array Assembly (AA) 1
LOW PSI
P6
performance critical
steps (~AA2 data and
array size)
P7
performance critical st
(~AA4 data and array si
SAFe operational
SW AA1 release
First SAFe AA0.5
operational SW
release
P1
First integration of
software in a PSI
System (PSI LOW)
MID: ~Dec 24
LOW: ~Sep 24
S
W
S
o
l
u
t
i
TBC
Steady state
construction
capacity:
20% Solution
Enablers
50%
ART/Solution
Features
30% Other
capacity
P8
MID PSI
TBC
P2
Functionally
complete MVP for
PSI Mid and Low
First integration
in PSI Mid
IM1
First OMC and SDP
hardware on PSI Mid
IM2
Emulator in PSI Mid
IM3
First OMC, CSP LMC, PSS, PST,
NSDN, SAT, SPFRx, Dish LMC
IM4
First MID CBF
Hardware on
System ITF
IM5
Start of System ITF
IM6
Start of AA05
Integration Events
IM7
End of AA05 System
SKA1 Mid
Milestones
SKA1 Low
Milestones
T0 C0
P2 P3 P9
P5
IL1
AAVS moved to
external
shelter
IL2
MCCS running
on AAVS
platform
IL3
MCCS operating
AAVS data
capture
Hot-season
tests
IL4 IL6
AAVS3 station
deployment
IL7
MCCS
operating
3 stations
IL8
3-station
interferometry
Hot-season
tests
IL9
AA0.5 Station
Deployment
IL10
Milestones
coming from
MCCS Roadmap.
Probably need
review.
Milestones
coming Mid
CI Flow
Diagrams
Milestones
coming the needs
to have proper
scaling of the
SAFe Operational
Software.
IL5
Beam Pattern
Testing
P4
Start small scale SDP
scaling (~3-5 nodes)

2027
2026
2025
2024
2023
17 18 19 20 22
21 23 24 25 26 28
27 29 30 31 32 34
33 35 36
mbly (AA) 0.5
Array Assembly (AA) 1 Array Assembly (AA) 2 Array Assembly (AA) 3 Array Assembly (AA) 4
P6
le SDP for all
ance critical
AA2 data and
ay size)
P7
SAFe operational
SW AA1 release
P11
SAFe operational
SW AA3 release
P12
P10
MID: ~Dec 24
LOW: ~Sep 24
MID: ~Jan 26
LOW: ~Oct 25
MID: ~Oct 26
LOW: ~Sep 25
MID: ~Jul 27
LOW: ~Jul 27
SAFe operational
SW AA2 release
C
P8
SAFe operational
SW AA4 release
CBF
on
TF
IM5
Start of System ITF
IM6
Start of AA05
Integration Events
IM7
End of AA05 System
P9
n
metry
Hot-season
tests
IL9
AA0.5 Station
Deployment
IL10
Still a few knock-on
effects on hardware-
access related activities

S
o
l
u
t
i
o
n
Key Business feature set Enabler feature set
Business, Enabler, and
Program milestones
SKAMPI Development
for PSI Mid and Low
SKAMPI
Development for
AA05
Support for SKAMPI PSI Integration Events
Support for
SKAMPI
System ITF
Integration
Support for SKAMPI AA05 Integration,
Testing and Commissioning
Architectural Runway to AA05 Architectural Runway to AA1
IM1
hardware on PSI Mid
Support for S
Integration, T
Commis
SKAMPI Developme
Architectural Runway to AA
IM2
Emulator in PSI Mid
IM3
IM4
First MID CBF
Hardware on
System ITF
IM5
IM6
Start of AA05
Integration Events
IM7
SKA1 Mid
Milestones
SKA1 Low
Milestones IL1
AAVS moved to
external
shelter
IL2
MCCS running
on AAVS
platform
IL3
MCCS operating
AAVS data
capture
Hot-season
tests
IL4 IL6
AAVS3 station
deployment
IL7
MCCS
operating
3 stations
IL8
3-station
interferometry
Hot-season
tests
IL9
AA0.5 Station
Deployment
IL10
Milestones
coming from
MCCS Roadmap.
Probably need
review.
Milestones
coming Mid
CI Flow
Diagrams
IL5
Beam Pattern
Testing

r SKAMPI AA05 Integration,
g and Commissioning
for AA1
Commissioning
Commissioning
Support for SKAMPI
AA3 Int., Testing &
Commissioning
Commissioning
SKAMPI
Development for
AA3
SKAMPI
Development for
AA4
Architectural Runway to AA2
Architectural
Runway to AA3
Architectural
Runway to AA4
nts
IM7
n
t

Slide /
Prototyping System Integration: SKAMPI
•SKAMPI: SKA MVP Prototype Integration
•Sometimes referred to as SKA MVP Product Integration!
‣ Points to the idea that we want to productise it, so that it becomes
easy to manage
•Mixture of technologies
•TANGO for control
•OCI Containers/Kubernetes/Helm for deployment
•Gitlab CI/CD for testing
•Mostly Python, with a bit of C/C++ for some devices/software
32

SKA1 Control Hierarchies
SKA1-Low SKA1-Mid

Legend
Human-Machine Interfaces
Monitoring & Control Interfaces (TANGO)
Signal Chain
SKAMPI
Component
Hardware
Element
Emulated
Component
Signal UI
OET
Dish Master
CSP Master
CBF Master
CBF
Mid
CBF Mid
Emulator
SDP Master
SDP
TMC
Dish
Receiver
User
Signal
Displays
CLI
Jupyter
Notebook
WebJive
EDA
Grafana
Logstash/
Kibana
Archive Events
Logging
Database Connection
Slide /
34

Slide /
35
«pod» pb-[...]-[...]
«namespace» sdp
«app» sdp-prototype
«etcd-cluster»
sdp-prototype-etcd
«pod» sdp-etcd
«pod» etcd-operator
«pod» sdp-prototype-tangods
sdp-master
sdp-subarray-1
«pod»
sdp-prototype-processing-controller
sdp-prototype
manages
«pod»
sdp-prototype-helm-deploy
helm-deploy
sdp-prototype-etcd-nodeport
etcd
etcd-operator
cbf-master
fsp01
fsp02
fsp03
midcbf-cbf-proto <pod>
cbf-proto <app>
fsp04
cbfsubarray01
vcc001
vcc002
vcc003
vcc004
csp-master
midcsplmc-proto <pod>
csp-proto <app>
cspsubarray01
oet
oet-jupyter
jupyter-oet <pod>
jupyter-oet
jupyter-{hostname}
dishmaster1
dishmaster3
dishmaster4
centralnode
tmcprototype-tmc-proto <pod>
tmc-proto <app>
dishleafnode1
dishleafnode2
dishleafnode3
cspsubarrayleafnode1
dishmaster2
dishleafnode4
cspmasterleafnode
subarraynode1
sdpsubarrayleafnode1
sdpmasterleafnode
Key
< p o d >
<container>
services
<etcd cluster>
Grouping based on labels (E.g
<app>, <release> etc)
Call relationship (change during runtime: allocate resources)
Call relationship (change during runtime: configure scan)
Call relationship (fixed during runtime)
Service Interface Point
Service Interface
connected to external
ingress point
«etcd»
sdp-subarray-2
«etcd»
«app» pb-[...]
«pod»
workflow
«etcd»
«app» pb-[...]-[...]
«pod»
execution engine
«etcd»
«etcd»
SDP configuration dependency (implicitly through etcd)
Text
Central Node i/f
Subarray Node i/f
CSP Master Leaf Node i/f
SDP Subarray Leaf Node i/f
CSP Subarray Leaf Node i/f
SDP Master Leaf Node i/f
Dish Leaf Node i/f Dish Master i/f
CspMaster i/f
CspSubarray i/f
CspMaster mid proto i/f
CspSubarray mid proto i/f

oet
oet-jupyter
jupyter-oet <pod>
jupyter-oet
jupyter-{hostname}
dishmaster1
dishmaster3
dishmaster4
centralnode
tmcprototype-tmc-proto <pod>
tmc-proto <app>
dishleafnode1
dishleafnode2
dishleafnode3
cspsubarrayleafnode1
dishmaster2
dishleafnode4
cspmasterleafnode
subarraynode1
sdpsubarrayleafnode1
sdpmasterleafnode
Key
< p o d >
<container>
services
<etcd cluster>
Grouping based on labels (E.g
<app>, <release> etc)
Call relationship (change during runtime: configure scan)
Call relationship (fixed during runtime)
Service Interface Point
Service Interface
ingress point
«etcd»
Central Node i/f
Subarray Node i/f
CSP Master Leaf Node i/f
SDP Master Leaf Node i/f
Dish Leaf Node i/f Dish Master i/f

«pod» pb-[...]-[...]
«namespace» sdp
«app» sdp-prototype
«etcd-cluster»
sdp-prototype-etcd
«pod» sdp-etcd
«pod» etcd-operator
«pod» sdp-prototype-tangods
sdp-master
sdp-subarray-1
«pod»
sdp-prototype-processing-controller
sdp-prototype
manages
«pod»
sdp-prototype-helm-deploy
helm-deploy
sdp-prototype-etcd-nodeport
etcd
etcd-operator
cbf-master
fsp01
fsp02
fsp03
midcbf-cbf-proto <pod>
cbf-proto <app>
fsp04
cbfsubarray01
vcc001
vcc002
vcc003
vcc004
csp-master
midcsplmc-proto <pod>
csp-proto <app>
cspsubarray01
cspsubarrayleafnode1 sdpsubarrayleafnode1
Call relationship (change during runtime: configure scan) Service Interface
ingress point
«etcd»
sdp-subarray-2
«etcd»
«app» pb-[...]
«pod»
workflow
«etcd»
«app» pb-[...]-[...]
«pod»
execution engine
«etcd»
«etcd»
CspMaster i/f
CspSubarray i/f
CspMaster mid proto i/f
CspSubarray mid proto i/f

Slide /
Challenges
•Using TANGO in a very event-oriented way
•Finding some edge cases around the event mechanism
‣ Requires sustained effort directly on TANGO
•Containerisation and orchestration challenges
•TANGO Device Server granularity
•Helm chart granularity
•Native TANGO support?
•Computing scaling challenges
•Mostly coming from current granularity overhead
•Team scaling challenges
•Need to have even better alignment on what needs to be done, and how it needs to be done
•Identifying suitable rules for contribution and release management
39
Just hired Thomas
Juerges: 50% on
TANGO
Finding about this
now, working on fixes
on time!
We joined the
TANGO collaboration
in 2017!

Slide /
Next Steps
•Keep aligning the Construction Proposal’s Integrated Product
Schedule (hardware oriented) with the Software Roadmap
(functionality oriented)
•Finish contracting to move from bridging to construction funding
•Provide appropriate level of effort to the System and Platform
teams
‣ Setting up the contracting framework should help with this
•Keep improving our TANGO base
•Keep iterating on SKAMPI → SKAO Telescope Software
41

Slide /
Interesting talks and posters relevant to the SKA project around
ICALEPCS’21
Related Contributions
42

Slide /
SKA at ICALEPCS’21
43
Code Speaker Organisation Title
MOAL03 Juande Santander-Vela SKAO
From SKA to SKAO: Early Progress in the SKA Project
Construction
TUBL02 Samuel Twum SARAO
Implementing an Event Tracing Solution With Consistently
Formatted Logs for the SKA Telescope Control System
TUBR02 Sonja Vrcic SKAO Design Patterns for the SKA Control System
TUBL04 Matteo Di Carlo
INAF/
OAAB Teramo
Continuous Integration-Continuous Delivery (CI-CD)
Practices at SKA

Slide /
SKA-related at ICALEPCS’21
44
MOAR03 Thomas Juerges ASTRON/SKAO LOFAR2.0: Station Control Upgrade
FRAR01 Mikel Eguiraun MAX IV Taranta, the No-Code Web Dashboard in Production
MOPV046 Thijs Snijder ASTRON Tango Controls Device Attribute extension in Python3

Slide /
TANGO-related at ICALEPCS’21
45
TUBL03 Piotr Pawel Goryl S2Innovation Tango Controls RFCs
FRAR01 Mikel Eguiraun MAX IV Taranta, the No-Code Web Dashboard in Production
MOPV025 Jean-Luc Pons ESRF
TangoGraphQL: A GraphQL binding for Tango control
system Web-based applications
MOPV034 Michal Liszcz et al.
S2Innovation/
ESRF/MAX IV
Migration of Tango Controls Source Code Repositories
MOPV046 Thijs Snijder ASTRON Tango Controls Device Attribute extension in Python3

Thank you!
Questions?
www.skao.int
our facilities are located.

Thanks to the SKA SAFe Solution Team,
SKAO TDTs, our developers, and the
TANGO Collaboration
In the memory of my father-in-law, Demetrio
Sababa
www.skao.int
our facilities are located.

From SKA to SKAO: Early progress in SKA project construction.

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to From SKA to SKAO: Early progress in SKA project construction.

Similar to From SKA to SKAO: Early progress in SKA project construction. (20)

More from Joint ALMA Observatory

More from Joint ALMA Observatory (18)

Recently uploaded

Recently uploaded (20)

From SKA to SKAO: Early progress in SKA project construction.