Download pdf - SKA Systems Engineering: from PDR to Construction

SKA Systems Engineering: from PDR to Construction

Spain SKA Day, October 23rd, Granada


• Who am I?• What do we (SKAO SEs) do?• When does all this take place?• To CDR, and Beyond…• Accomplishments & Ongoing Activities • And Industry?• Conclusions

Talk Outline


Who am I?


• Systems Engineer for the SDP/TM elements• Former VIA-SKA Project Manager• VLT Archive Applied Scientist, later ALMA

Science Archive Front-/Back-end Developer at ESO

• Ph.D. in Radio Astronomical data archives and Virtual Observatory

• Software Analyst/Manager

Who am I?


• Systems Engineer for the SDP/TM elements• We are guardians to ensure that the SKA:

• is buildable • operates as intended• as a system, is not dominated by a

particular element• design changes keep it that way

Who am I?

SKAOffice(RevN) -JCG.vsd

2014-04-14

Deputy Director-General and

Head of Project(Alistair McPherson)

Director-General(Phil Diamond)

Project Officer Industry LiaisonOfficer

(Phil Crosby)In-Kind Contribution

Head of Admin and Legal

(Colin Greenwood)

Finance Manager(Helen MacDonald)

HR Manager(Andrew Taylor)

IT Manager(Paul Furness)

Deputy IT Manager

(tbc)

Executive Officer(Sarah-Jane Pritchard)

Dpty Comms. & Outreach Manager

(Mathieu Isidro)

Director of Policy Development

(Simon Berry)

Engineering Project Manager

Dishes(Mark Harman)


CSP and LFAA(Kobus Cloete)


SaDT(Philip Gibbs)

System EngineerVerification

System EngineerRAM and ILS

(Cornelius Taljaard)

System EngineerDishes

(Andrea Cremonini)

System EngineerLFAA

(Maria Labate)

System EngineerCSP

(Marco Caiazzo)

System EngineerSaDT

(Rodrigo Olguin)

System EngineerSDP/Telescope Mgr

(Juande Santander)

System EngineerAnalysis

System EngineerModelling

Configuration Manager(Susan Nel)


Site and Infrastructure(Martin Austin)

Architect(Tim Cornwell)

Deputy Architect(Peter Dewdney)

Domain SpecialistSignal Processing

(Wallace Turner)

Domain SpecialistSaDT and

Synchronisation and Timing

(Roshene McCool)

Domain SpecialistRF/Dish

(Gie Han Tan)

Project Scientist(Jimi Green)

Project Scientist(Tyler Bourke)

Project Scientist(Jeff Wagg)

Admin Assistant

(Donna Parkinson)

Domain SpecialistAA�and�PAF

(Mark Waterson)

Chief System Engineer

(Tim Stevenson)

Communications& Outreach Manager

(William Garnier)

IT Assistant(Nathan Cunningham)

Head of Policy Development

(WANG Qiming)

Spectrum Manager

Power Engineer(Adriaan Schutte)

Office Manager and PA to D-G

(Greta Collins)

Science Director(Robert Braun)

Project Controller

Domain Specialist Operations

AIV Work Package Manager

(Peter Hekman)

Engineering Project ManagerSDP and Telescope

Manager(Miles Deegan)

Receptionist(Val Gresley-Jones)

0.5FTE

Receptionist(Anne Curran)

0.5FTE

Domain Specialist Computing


What do we do?


Systems Engineering Primer



Science WGs AG group SE group


Systems Engineering PrimerSE group AG group

Consortia




Systems Engineering Primer: Docs





When does all this take place?


The SKA1 timeline

20162015 2017 2018 2019 2020 2021 2022 20232014

High/level/design

Rebaselining/submissions/(RBS)

Preliminary/Design/Review/(elements)

Detailed/design

Prototype/systems/deployed

Critical/Design/Review

SKA1/construction/approvedProcurement

SKA1/early/science

SKA1/construction

SKA2/detailed/design

Design/consortia/start

SKA2/procurementSKA2/construction/starts

SKA2/concept/development

Board/RBS/approval 3K5/Mar/15

15K22/Sep/14

1/Nov/13

PreKconstruction/Stage/1


Production*Readiness*Review*(4*dish*array)

Construction*Readiness*Review*(1*dish*line9up)

New/SKA/Organisation/in/place

Key/Doc/Set/&/Prospectus

Formal/negotiations

Ratification/of/Agreements Organisation/has/minimum/no./Members/with/Agreements/ratified

Agreements/in/Key/Doc/Set/signed

Andrea/Casson,/SKAO/Project/Controller,/Sept/2014

System/PDR

Integration/testing/on/site

Advanced/Instrumentation/Prog.

KEY:/Blue/=/SKA1/science/&/engineering;/orange/=/policy;/green/=/SKA2;/milestones*in*italics*=/proposals/under/discussion

The SKA1 timeline


The SKA1 timeline

Issue%Baseline%Design

Science%Assessment%Workshops

Proposal%Feedback

Level%1%Requirements%Feedback

Science%Conference

Engineering%Meeting

Engineering%Change%Proposals

Designs%&%Costs

SKAO%Review

Technical%Advice(working%groups)

SEAC

Board

Consortium%Design%Activities

Level%0%Requirements

Brief%SEAC

2013 2015Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar

2014

PDR

ScienceReview%Panel

ScienceReview%Panel



Proposal%Feedback


Science%Conference

Engineering%Meeting


Designs%&%Costs

SKAO%Review


SEAC

Board



Brief%SEAC


2014

PDR

ScienceReview%Panel

ScienceReview%Panel


The SKA1 timeline



Proposal%Feedback


Science%Conference

Engineering%Meeting


Designs%&%Costs

SKAO%Review


SEAC

Board



Brief%SEAC


2014

PDR

ScienceReview%Panel

ScienceReview%Panel

!! !!

!! !!

!!!!

!!(43)

!!

!!

!!

!!



Proposal%Feedback


Science%Conference

Engineering%Meeting


Designs%&%Costs

SKAO%Review


SEAC

Board



Brief%SEAC


2014

PDR

ScienceReview%Panel

ScienceReview%Panel

The SKA1 timeline



Proposal%Feedback


Science%Conference

Engineering%Meeting


Designs%&%Costs

SKAO%Review


SEAC

Board



Brief%SEAC


2014

PDR

ScienceReview%Panel

ScienceReview%Panel



Proposal%Feedback


Science%Conference

Engineering%Meeting


Designs%&%Costs

SKAO%Review


SEAC

Board



Brief%SEAC


2014

PDR

ScienceReview%Panel

ScienceReview%Panel

• Formed by External Reviewers, AG representative, SE representative, PM, Observers

• Chaired by a selected External Reviewer• SKAO Project Manager acts as Secretary

• SKAO personnel contributes to OAR• Consortia respond to Consolidated OAR

before PDR review• Face-to-face for outstanding actions, 1-2 days

PDR panels and process

• Element overall design report. • Specific design reports for all

second tier subsystems (the Element being the first tier), including manufacturing/procurement approach, transport, installation, verification, support…

• Finite element models (if needed).• Software architecture models and

use cases.• Parametric models.• Analysis reports: Finite element

modelling (including all mechanical and thermal load cases), thermal analysis, fluid dynamics, RFI/EMC analysis, safety analysis, hazard analysis…

• Cost analysis (development, construction, verification, commissioning & steady state ops).

• Preliminary construction plans. • Configuration items list.• Compliance matrix.• Preliminary maintenance plan.• Preliminary verification plan.• Schedule estimate for construction.• High level risk register.• Draft Statement of work for the

construction of the Element.• Draft technical specifications for

the construction of the Element.

PDR documentation

• Interface Control Documents (ICDs)• Owned by the SKAO, developed

between the Consortia• Technology Readiness Level Assessment

• Controlled through Risk Register right now

PDR documentation (in parallel)


Meantime…


Rebaselining SKA1


• Cost cap approved for SKA1 Construction:650 M€

• Need to re-align design with costs (CAPEX and OPEX), and science priorities

• Processed owned by Architecture Group ➡Assisted by Systems Engineering Group

• Transformational science is a top priority• Big ECP for changing baseline design

Rebaselining SKA1


• The new baseline design will be the new stable basis for Stage 2 design.

• PDR to be done on pre=rebaselining submissions➡Potential ∆PDR if significant changes

needed to design• Work from PDR to CDR based on new

baseline.

Rebaselining SKA1


To CDR and Beyond

• Most likely, same as for PDR: formed by External Reviewers, AG representative, SE representative, PM, Observers

CDR panels and process

• Complete documentation for Element procurement: SoW, specs, drawings & ICDs.

• Specific design reports for all subsystems, including transport, integration & verification.

• All finite element models. • Software architecture models &

use cases • Software libraries required to

demonstrate compliance • Software configuration information

for demonstration of compliance. • Parametric models used for design

optimization.

• Analysis reports: similar to PDR one, with ops & construction/assembly.

• Integrated Logistics (RAMS/FMECA) report

• End-to-end detailed cost breakdown.• Construction plan, with

acceptance test plan and procedures.

• Operations (including maintenance) plan • Logistics requirements for

construction, training• Configuration items list• Schedule for construction.• Detailed risk register.

CDR documentation


• SKA Board to approve SKA1 construction.• Later comes Tender and Procurement:

• Rules being defined right now (see Phil’s talk)• Cannot assume same consortia will

undertake packages… or package structure will remain the same

• Later Construction, Commissioning, Early Science…

Beyond CDR… Solid CDR

crucial!

20162015 2017 2018 2019 2020 2021 2022 20232014

High/level/design

Rebaselining/submissions/(RBS)

Preliminary/Design/Review/(elements)

Detailed/design

Prototype/systems/deployed

Critical/Design/Review

SKA1/construction/approvedProcurement

SKA1/early/science

SKA1/construction

SKA2/detailed/design

Design/consortia/start

SKA2/procurementSKA2/construction/starts

SKA2/concept/development

Board/RBS/approval 3K5/Mar/15

15K22/Sep/14

1/Nov/13



Production*Readiness*Review*(4*dish*array)

Construction*Readiness*Review*(1*dish*line9up)

New/SKA/Organisation/in/place

Key/Doc/Set/&/Prospectus

Formal/negotiations

Ratification/of/Agreements Organisation/has/minimum/no./Members/with/Agreements/ratified

Agreements/in/Key/Doc/Set/signed

Andrea/Casson,/SKAO/Project/Controller,/Sept/2014

System/PDR

Integration/testing/on/site

Advanced/Instrumentation/Prog.

KEY:/Blue/=/SKA1/science/&/engineering;/orange/=/policy;/green/=/SKA2;/milestones*in*italics*=/proposals/under/discussion

The SKA1 timeline


Accomplishments & Ongoing Activities

SKA Engineering Meeting 2014

• Great technical progress seen in the last year• Parametrics models, SysML diagrams,

Product Trees, Interface Control Documents… progressing nicely across consortia

• Better understanding of key architectural issues• Pre-PDR submissions clarified after

Engineering Meeting

Element Progress

Not talking about

building the SKA,

but building the SKA!

• One for SKA1-Low, one for SKA1-Mid/Survey• Focused on technical & architectural

hotspots• Calibration feedback• SDP location• Time reference & definitions• Other hotspots as identified with consortia

Telescope Architecture Teams

• Uses Science Prioritization Use Cases• Drives models for

• SDP sizing• Power consumption• Telescope scheduling

• Used to bring insight into feasible ways to operate the telescope

Year in the Life of SKA1

• Further specialization of the ConOps• Work started by NRAO contractors

• Will provide SKAO with Operations Model by end 2014

• Will help filling in missing details that can impact design

Operations Concept Document


And Industry?

• Varied industry involvement:• Unpaid Consultants (Roadmaps, Trends)• Paid Contractors (SE, PM, at this stage)

• Remember: design work cannot be predicated on single-vendor solutions

• Industry engagement with consortia done by consortia themselves• SKAO can help get people in touch

And Industry?

• Standards-based approach well regarded• Model-Based System Engineering (SysML)

currently standard in SKAO, and many consortia

• Keep in touch!

And Industry?

Phil Crosby,

Industry Liaison


Conclusions

• Lots to do before Procurement!• Timeline is king, and we mean to keep it that way• Progress, don’t dwell on things• We are here to help consortia help us

• SKA1 must be transformational for science• Industry should be considering potential

applications now, to be able to be involved later

Conclusions

SKA means the industrialization of Radio Astronomy

• Lots to do before Procurement!• Timeline is king, and we mean to keep it that way• Progress, don’t dwell on things• We are here to help consortia help us

• SKA1 must be transformational for science• Industry should be considering potential

applications now, to be able to be involved later

Conclusions

We will be needing industry, in a big way


Thanks for yourgood work!

Questions?Juande Santander-Vela

[email protected]