SKA Systems Engineering: from PDR to Construction

  • Published on
    11-Jun-2015

  • View
    197

  • Download
    5

DESCRIPTION

In a project of the complexity of the 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.

Transcript

1. SKA Systems Engineering:from PDR to ConstructionSpain SKA Day, October 23rd, Granada 2. Who am I? What do we (SKAO SEs) do? When does all this take place? To CDR, and Beyond Accomplishments & Ongoing Activities And Industry? ConclusionsSpain SKA Day, October 23rd, GranadaTalk Outline 3. Who am I?Spain SKA Day, October 23rd, Granada 4. Systems Engineer for the SDP/TM elements Former VIA-SKA Project Manager VLT Archive Applied Scientist, later ALMAScience Archive Front-/Back-endDeveloper at ESO Ph.D. in Radio Astronomical data archivesand Virtual Observatory Software Analyst/ManagerSpain SKA Day, October 23rd, GranadaWho am I? 5. 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 aparticular element design changes keep it that waySpain SKA Day, October 23rd, GranadaWho am I? 6. SKAOffice(RevN) -JCG.vsd2014-04-14Director-General(Phil Diamond)Deputy Director-General andHead of Project(Alistair McPherson)EngineeringProject ManagerProject Officer Industry LiaisonOfficer(Phil Crosby)In-Kind ContributionHead of Admin andLegal(Colin Greenwood)Finance Manager(Helen MacDonald)HR Manager(Andrew Taylor)IT Manager(Paul Furness)Deputy ITManager(tbc)Executive Officer(Sarah-Jane Pritchard)Dpty Comms. &Outreach Manager(Mathieu Isidro)Director of PolicyDevelopment(Simon Berry)EngineeringProject ManagerDishes(Mark Harman)SaDT(Philip Gibbs)EngineeringProject ManagerCSP and LFAA(Kobus Cloete)System EngineerVerificationSystem EngineerRAM and ILS(Cornelius Taljaard)System EngineerAnalysisSystem EngineerModellingSystem EngineerDishes(Andrea Cremonini)System EngineerLFAA(Maria Labate)System EngineerSaDT(Rodrigo Olguin)System EngineerCSP(Marco Caiazzo)System EngineerSDP/Telescope Mgr(Juande Santander)ConfigurationManager(Susan Nel)EngineeringProject ManagerSite andInfrastructure(Martin Austin)Architect(Tim Cornwell)Deputy Architect(Peter Dewdney)Domain SpecialistSaDT andSynchronisation andTiming(Roshene McCool)Domain SpecialistSignal Processing(Wallace Turner)Domain SpecialistRF/Dish(Gie Han Tan)Project Scientist(Jimi Green)Project Scientist(Tyler Bourke)Project Scientist(Jeff Wagg)AdminAssistant(Donna Parkinson)Domain SpecialistAAandPAF(Mark Waterson)Chief SystemEngineer(Tim Stevenson)Communications Outreach Manager(William Garnier)IT Assistant(Nathan Cunningham)Head of PolicyDevelopment(WANG Qiming)SpectrumManagerPower Engineer(Adriaan Schutte)Office Managerand PA to D-G(Greta Collins)Science Director(Robert Braun)Project ControllerDomain SpecialistOperationsEngineeringProject ManagerSDP and TelescopeManager(Miles Deegan)AIV WorkPackage Manager(Peter Hekman)Receptionist(Anne Curran)0.5FTEReceptionist(Val Gresley-Jones)0.5FTEDomain SpecialistComputing 7. What do we do?Spain SKA Day, October 23rd, Granada 8. Systems EngineeringPrimerSpain SKA Day, October 23rd, Granada 9. Systems Engineering Primer 10. Systems Engineering PrimerScience WGsAG groupSE group 11. Systems Engineering Primer 12. Systems Engineering PrimerSE groupAG groupConsortia 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. When does all thistake place?Spain SKA Day, October 23rd, Granada 21. The SKA1 timelineSpain SKA Day, October 23rd, Granada 22. The SKA1 timelineKEY:/Blue/=/SKA1/science//engineering;/orange/=/policy;/green/=/SKA2;/milestones*in*italics*=/proposals/under/discussionDesign/consortia/startHigh/level/designRebaselining/submissions/(RBS)Preliminary/Design/Review/(elements)Board/RBS/approval 3K5/Mar/15Construction*Readiness*Review*(1*dish*line9up)Key/Doc/Set//ProspectusAgreements/in/Key/Doc/Set/signedFormal/negotiationsRatification/of/Agreements Organisation/has/minimum/no./Members/with/Agreements/ratified2014 2015 2016 2017 2018 2019 2020 2021 2022 2023Detailed/designPrototype/systems/deployedCritical/Design/ReviewSKA1/construction/approvedProcurementSKA1/constructionSKA1/early/scienceSKA2/concept/developmentSKA2/detailed/designSKA2/procurementSKA2/construction/starts15K22/Sep/141/Nov/13PreKconstruction/Stage/1PreKconstruction/Stage/2Production*Readiness*Review*(4*dish*array)New/SKA/Organisation/in/placeAndrea/Casson,/SKAO/Project/Controller,/Sept/2014System/PDRIntegration/testing/on/siteAdvanced/Instrumentation/Prog. 23. Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb MarSpain SKA Day, October 23rd, GranadaThe SKA1 timelineIssue%Baseline%DesignScience%Assessment%WorkshopsProposal%FeedbackLevel%1%Requirements%FeedbackScience%ConferenceEngineering%MeetingLevel%0%RequirementsBrief%SEACEngineering%Change%ProposalsDesigns%%Costs SKAO%ReviewTechnical%Advice(working%groups)SEACBoardConsortium%Design%Activities2013 20152014PDRScienceReview%PanelScienceReview%Panel 24. !!!!!!Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb MarSpain SKA Day, October 23rd, GranadaThe SKA1 timelineIssue%Baseline%DesignScience%Assessment%WorkshopsProposal%FeedbackLevel%1%Requirements%FeedbackScience%ConferenceEngineering%MeetingLevel%0%RequirementsBrief%SEACEngineering%Change%ProposalsDesigns%%Costs SKAO%ReviewTechnical%Advice(working%groups)SEACBoardConsortium%Design%Activities2013 20152014PDRScienceReview%PanelScienceReview%Panel!! !!!! !!!!!!!!(43)!! 25. The SKA1 timelineIssue%Baseline%DesignScience%Assessment%WorkshopsProposal%FeedbackBrief%SEACLevel%1%Requirements%FeedbackScience%ConferenceEngineering%MeetingLevel%0%RequirementsBrief%SEACEngineering%Change%ProposalsDesigns%%Costs SKAO%ReviewTechnical%Advice(working%groups)SEACBoardConsortium%Design%ActivitiesLevel%0%RequirementsPDRJun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar2013 20152014PDRScienceReview%PanelScienceReview%PanelLevel%1%Requirements%FeedbackEngineering%MeetingEngineering%Change%ProposalsDesigns%%Costs SKAO%ReviewTechnical%Advice(working%groups)SEACBoardConsortium%Design%Activities2015Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar 26. PDR panels and process Formed by External Reviewers, AGrepresentative, 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 OARbefore PDR review Face-to-face for outstanding actions, 1-2 days 27. Element overall design report. Specific design reports for allsecond tier subsystems (theElement being the first tier), includingmanufacturing/procurementapproach, transport, installation,verification, support Finite element models (if needed). Software architecture models anduse cases. Parametric models. Analysis reports: Finite elementmodelling (including all mechanicaland thermal load cases), thermalanalysis, fluid dynamics, RFI/EMCanalysis, safety analysis, hazardanalysis Cost analysis (development,construction, verification,commissioningsteady 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 theconstruction of the Element. Draft technical specifications forthe construction of the Element.PDR documentation 28. PDR documentation (in parallel) Interface Control Documents (ICDs) Owned by the SKAO, developedbetween the Consortia Technology Readiness Level Assessment Controlled through Risk Register rightnow 29. Spain SKA Day, October 23rd, GranadaMeantime 30. RebaseliningSKA1Spain SKA Day, October 23rd, Granada 31. Cost cap approved for SKA1 Construction:650 M Need to re-align design with costs (CAPEXand OPEX), and science priorities Processed owned by Architecture GroupAssisted by Systems Engineering Group Transformational science is a top priority Big ECP for changing baseline designSpain SKA Day, October 23rd, GranadaRebaselining SKA1 32. The new baseline design will be the newstable basis for Stage 2 design. PDR to be done on pre=rebaseliningsubmissionsPotential PDR if significant changesneeded to design Work from PDR to CDR based on newbaseline.Spain SKA Day, October 23rd, GranadaRebaselining SKA1 33. To CDR and BeyondSpain SKA Day, October 23rd, Granada 34. CDR panels and process Most likely, same as for PDR: formed byExternal Reviewers, AG representative, SErepresentative, PM, Observers 35. Complete documentation forElement procurement: SoW, specs,drawingsICDs. Specific design reports for allsubsystems, including transport,integrationverification. All finite element models. Software architecture models use cases Software libraries required todemonstrate compliance Software configuration informationfor demonstration of compliance. Parametric models used for designoptimization. Analysis reports: similar to PDR one,with opsconstruction/assembly. Integrated Logistics (RAMS/FMECA)report End-to-end detailed cost breakdown. Construction plan, withacceptance test plan andprocedures. Operations (including maintenance) plan Logistics requirements forconstruction, training Configuration items list Schedule for construction. Detailed risk register.CDR documentation 36. SKA Board to approve SKA1 construction. Later comes Tender and Procurement: Rules being defined right now (see Phils talk) Cannot assume same consortia willundertake packages or package structurewill remain the same Later Construction, Commissioning, Early ScienceSpain SKA Day, October 23rd, GranadaBeyond CDR Solid CDRcrucial! 37. The SKA1 timelineKEY:/Blue/=/SKA1/science//engineering;/orange/=/policy;/green/=/SKA2;/milestones*in*italics*=/proposals/under/discussionDesign/consortia/startHigh/level/designRebaselining/submissions/(RBS)Preliminary/Design/Review/(elements)Board/RBS/approval 3K5/Mar/15Construction*Readiness*Review*(1*dish*line9up)Key/Doc/Set//ProspectusAgreements/in/Key/Doc/Set/signedFormal/negotiationsRatification/of/Agreements Organisation/has/minimum/no./Members/with/Agreements/ratified2014 2015 2016 2017 2018 2019 2020 2021 2022 2023Detailed/designPrototype/systems/deployedCritical/Design/ReviewSKA1/construction/approvedProcurementSKA1/constructionSKA1/early/scienceSKA2/concept/developmentSKA2/detailed/designSKA2/procurementSKA2/construction/starts15K22/Sep/141/Nov/13PreKconstruction/Stage/1PreKconstruction/Stage/2Production*Readiness*Review*(4*dish*array)New/SKA/Organisation/in/placeAndrea/Casson,/SKAO/Project/Controller,/Sept/2014System/PDRIntegration/testing/on/siteAdvanced/Instrumentation/Prog. 38. Accomplishments Ongoing ActivitiesSpain SKA Day, October 23rd, Granada 39. SKA Engineering Meeting 2014 40. Element Progress Great technical progress seen in the last year Parametrics models, SysML diagrams,Product Trees, Interface Control Documentsprogressing nicely across consortia Better understanding of key architectural issues Pre-PDR submissions clarified afterEngineering MeetingNot talking aboutbuilding the SKA,but building the SKA! 41. Telescope Architecture Teams One for SKA1-Low, one for SKA1-Mid/Survey Focused on technicalarchitecturalhotspots Calibration feedback SDP location Time referencedefinitions Other hotspots as identified with consortia 42. Year in the Life of SKA1 Uses Science Prioritization Use Cases Drives models for SDP sizing Power consumption Telescope scheduling Used to bring insight into feasible ways tooperate the telescope 43. Operations Concept Document Further specialization of the ConOps Work started by NRAO contractors Will provide SKAO with Operations Modelby end 2014 Will help filling in missing details that canimpact design 44. And Industry?Spain SKA Day, October 23rd, Granada 45. And Industry? Varied industry involvement: Unpaid Consultants (Roadmaps, Trends) Paid Contractors (SE, PM, at this stage) Remember: design work cannot bepredicated on single-vendor solutions Industry engagement with consortia done byconsortia themselves SKAO can help get people in touch 46. And Industry? Standards-based approach well regarded Model-Based System Engineering (SysML)currently standard in SKAO, and manyconsortia Keep in touch!Phil Crosby,Industry Liaison 47. Spain SKA Day, October 23rd, GranadaConclusions 48. Conclusions Lots to do before Procurement! Timeline is king, and we mean to keep it that way Progress, dont dwell on things We are here to help consortia help us SKA1 must be transformational for science Industry should be considering potentialapplications now, to be able to be involved laterSKA means the industrialization of Radio Astronomy 49. Conclusions Lots to do before Procurement! Timeline is king, and we mean to keep it that way Progress, dont dwell on things We are here to help consortia help us SKA1 must be transformational for science Industry should be considering potentialapplications now, to be able to be involved laterWe will be needing industry, in a big way 50. Thanks for yourgood work!Spain SKA Day, October 23rd, Granada 51. Questions?Juande Santander-Velaj.santander-vela@skatelescope.org

Recommended

View more >