Upgrade to Pro — share decks privately, control downloads, hide ads and more …

SKA Systems Engineering: From PDR to Construction

SKA Systems Engineering: From PDR to Construction

In a project of the complexity of the Square Kilometre Array (SKA), it is very important to be very observant of the different requirements for the SKA telescopes, and how they are implemented by the different sub-systems. And because the design of the SKA is evolving, the need to assess the impact of design changes, and potential trade-offs, is more relevant than ever. In this talk I will present how the SKA Organisation is leading the Systems Engineering work of the different consortia, and how we are using Model Based Systems Engineering (MBSE) to integrate the design inputs from the sub-systems, and be able to keep a Systems view that ensures that the element designs are sound, and really comply with the stringent requirements posed by the SKA.

D6c83d5d20c63b8e421a7966b04cfedb?s=128

Juande Santander-Vela

October 23, 2014
Tweet

More Decks by Juande Santander-Vela

Other Decks in Technology

Transcript

  1. SKA Systems Engineering: from PDR to Construction Spain SKA Day,

    October 23rd, Granada
  2. 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
  3. Spain SKA Day, October 23rd, Granada Who am I?

  4. Spain SKA Day, October 23rd, Granada • 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?
  5. Spain SKA Day, October 23rd, Granada • 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?
  6. SKAOffice(RevN) - JCG.vsd 2014-04-14 Deputy Director- General and Head of

    Project (Alistair McPherson) Director-General (Phil Diamond) Project Officer Industry Liaison Officer (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) Engineering Project Manager CSP and LFAA (Kobus Cloete) Engineering Project Manager SaDT (Philip Gibbs) System Engineer Verification System Engineer RAM and ILS (Cornelius Taljaard) System Engineer Dishes (Andrea Cremonini) System Engineer LFAA (Maria Labate) System Engineer CSP (Marco Caiazzo) System Engineer SaDT (Rodrigo Olguin) System Engineer SDP/Telescope Mgr (Juande Santander) System Engineer Analysis System Engineer Modelling Configuration Manager (Susan Nel) Engineering Project Manager Site and Infrastructure (Martin Austin) Architect (Tim Cornwell) Deputy Architect (Peter Dewdney) Domain Specialist Signal Processing (Wallace Turner) Domain Specialist SaDT and Synchronisation and Timing (Roshene McCool) Domain Specialist RF/Dish (Gie Han Tan) Project Scientist (Jimi Green) Project Scientist (Tyler Bourke) Project Scientist (Jeff Wagg) Admin Assistant (Donna Parkinson) Domain Specialist AAandPAF (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 Manager SDP and Telescope Manager (Miles Deegan) Receptionist (Val Gresley-Jones) 0.5FTE Receptionist (Anne Curran) 0.5FTE Domain Specialist Computing
  7. Spain SKA Day, October 23rd, Granada What do we do?

  8. Spain SKA Day, October 23rd, Granada Systems Engineering Primer

  9. Systems Engineering Primer

  10. Systems Engineering Primer Science WGs AG group SE group

  11. Systems Engineering Primer

  12. Systems Engineering Primer SE group AG group Consortia

  13. Systems Engineering Primer

  14. Systems Engineering Primer

  15. Systems Engineering Primer

  16. Systems Engineering Primer: Docs

  17. Systems Engineering Primer: Docs

  18. Systems Engineering Primer: Docs

  19. Systems Engineering Primer: Docs

  20. Spain SKA Day, October 23rd, Granada When does all this

    take place?
  21. Spain SKA Day, October 23rd, Granada The SKA1 timeline

  22. 2016 2015 2017 2018 2019 2020 2021 2022 2023 2014

    High/level/design Rebaselining/submissions/(RBS) Preliminary/Design/Review/(elements) Detailed/design Prototype/systems/deployed Critical/Design/Review SKA1/construction/approved Procurement SKA1/early/science SKA1/construction SKA2/detailed/design Design/consortia/start SKA2/procurement SKA2/construction/starts SKA2/concept/development Board/RBS/approval 3K5/Mar/15 15K22/Sep/14 1/Nov/13 PreKconstruction/Stage/1 PreKconstruction/Stage/2 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
  23. Spain SKA Day, October 23rd, Granada 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 2015 Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar 2014 PDR Science Review%Panel Science Review% Panel 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 2015 Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar 2014 PDR Science Review%Panel Science Review% Panel
  24. Spain SKA Day, October 23rd, Granada 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 2015 Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar 2014 PDR Science Review%Panel Science Review% Panel !! !! !! !! !! !! !!(43) !! !! !! !! 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 2015 Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar 2014 PDR Science Review%Panel Science Review% Panel
  25. 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 2015 Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar 2014 PDR Science Review%Panel Science Review% Panel Level%1% Requirements% Feedback Engineering% Meeting Engineering%Change%Proposals Designs%&% Costs SKAO%Review Technical% Advice (working% groups) SEAC Boar Consortium%Design%Activities Level%0% Requirements Brief% SEAC Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar PDR
  26. • 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
  27. • 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
  28. • 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)
  29. Spain SKA Day, October 23rd, Granada Meantime…

  30. Spain SKA Day, October 23rd, Granada Rebaselining SKA1

  31. Spain SKA Day, October 23rd, Granada • 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
  32. Spain SKA Day, October 23rd, Granada • 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
  33. Spain SKA Day, October 23rd, Granada To CDR and Beyond

  34. • Most likely, same as for PDR: formed by External

    Reviewers, AG representative, SE representative, PM, Observers CDR panels and process
  35. • 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
  36. Spain SKA Day, October 23rd, Granada • 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!
  37. 2016 2015 2017 2018 2019 2020 2021 2022 2023 2014

    High/level/design Rebaselining/submissions/(RBS) Preliminary/Design/Review/(elements) Detailed/design Prototype/systems/deployed Critical/Design/Review SKA1/construction/approved Procurement SKA1/early/science SKA1/construction SKA2/detailed/design Design/consortia/start SKA2/procurement SKA2/construction/starts SKA2/concept/development Board/RBS/approval 3K5/Mar/15 15K22/Sep/14 1/Nov/13 PreKconstruction/Stage/1 PreKconstruction/Stage/2 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
  38. Spain SKA Day, October 23rd, Granada Accomplishments & Ongoing Activities

  39. SKA Engineering Meeting 2014

  40. • 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!
  41. • 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
  42. • 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
  43. • 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
  44. Spain SKA Day, October 23rd, Granada And Industry?

  45. • 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?
  46. • 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
  47. Spain SKA Day, October 23rd, Granada Conclusions

  48. • 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
  49. • 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
  50. Spain SKA Day, October 23rd, Granada Thanks for your good

    work!
  51. Questions? Juande Santander-Vela j.santander-vela@skatelescope.org