Upload
nickolas-pierce
View
217
Download
0
Tags:
Embed Size (px)
Citation preview
Assembly, Integration & Verification2015 SKA Engineering Meeting
Richard Lord11 November 2015
• About the AIV Consortium• Current Status of Major Milestones
• Roll-Out Planning• Integration & Verification Planning• Product Hand-Over Planning• Test Procedure Planning• MeerKAT Precursor Integration Planning
• Risks
Overview
AIV Consortium Member Organisations
Element Project Manager: Peter Hekman
Element Systems Engineer: David Bolt
Architecture Group: Gie Han Tan
Project Scientist: Tyler Bourke
Operations Planning Group: Antonio Chrysostomou
SKA Office Contacts
# Stage 1: Milestone Description Due Date
1 t0 Nov 2013
2 t0 + 12w Jan 2014
3 Verification Requirements Apr 2014
4 Roll-Out Plan (Draft) Jun 2014
5 Input to Re-Baselining Exercise Sep 2014
6 PDR Submission Nov 2014
7 PDR Closure Feb 2015
Major Milestones - Stage 1
PDR Baseline completed in eB.
Major Milestones - Stage 2
# Stage 2: Milestone Description Due Date1 Kick-off Apr 20152 Telescope Preliminary I&V Plan Jul 20153 SEMP and PMP Alignment Jun 20154 Product Hand-Over Checklist Jul 20155 Updated Cost Model Aug 20156 MeerKAT Precursor ICDs Aug 20157 Telescope Roll-Out Plan (Next Release) Sep 20158 Telescope Test Procedures (Draft) Dec 20159 Precursor Integration Plan and ICDs Mar 2016
10 Telescope Detailed I&V Plan Jun 201611 CDR Data Pack Finalisation (Element CDR) Dec 201612 Telescope AIV Resource Plan Mar 201713 Telescope Test Procedures (Final) Apr 201714 CDR Data Pack Update (for System CDR) May 201715 CDR Submission (for System CDR) Jul 201716 CDR Closure (for System CDR) Oct 2017
• Forms the basis for the delivery of products and planning of integration & verification activities.
• Considers:– Sequencing of implemented functionality– Scale: How many Dishes / Stations deployed and when– Integration of MeerKAT Precursor into SKA1 MID
• Sequential process – early retirement of risks• Achieved by specifying “Array Releases”
Roll-Out Planning
How hard can it be?
“Getting to AR1” Session:• Today (Wednesday):
12h30 – 15h00, Breakout 2 (Merlot)
• Friday:8h30 onwards, Breakout 2 (Merlot)
• Described by:– Date
• When all required products have been installed, i.e. not necessarily integrated into Telescope System
– Number of Dishes / Stations– Array Capability → Determines back-end Element functionality– Key Engineering Goals– Science Capability
• Used by AIV Team and Science Validation Team– Verification of Level-1 (System Level) Requirements– Validation of Science Requirements
Released Array
V-Diagram
Operational Concept Description
Telescope Requirements Specification
Element Requirements Specification
Component Specification
Design & Manufacture
ComponentAIV
ElementAIV
TelescopeAIV
ScienceValidation
Component Verification
Element Verification
System Verification
User Requirements Validation
Time
Design
Verifi
catio
n
Performed withArray Releases
• Multiple ITFs– At Element Level or lower
• All over the world. Rely heavily on simulators/emulators. No AIV involvement.
– At System Level• End-to-End line-up of Level-2 products. Possibly one ITF at each Host Country.
– On Site• Conceptually possible to have an on-site ITF, e.g. in the form of an Engineering Array.
• System-Level ITF used for:– System Level Design Qualification– Verification of interfaces between Level-2 products– Debugging, troubleshooting, development work, etc– Testing of hardware/firmware/software upgrades during Constr. Phase– Knowledge transfer (between contractors, engineers, AIV Team, etc)
• Laboratory Verification Event (LVE)– Verification of end-to-end functionality and performance required for Array Release
1
Integration Test Facility (ITF)
SKA1 MID Roll-Out Plan
Sit
eIn
teg
rati
on
Tes
t F
acili
ty (
ITF
)
LabIntegration Events
Dish Receiver, SaDT,CSP, TM, SDP
T0 + 12 T0 + 24 T0 + 48 T0 + 60T0 + 36
LVE
AR4AR3AR2AR11Dish
2Dishes
4Dishes
LVE2 LVE3 LVE4
DishPRR
Number of SKA1 Dishes deployed
MeerKAT Precursor
Front-End IntegrationINFRA, SaDT, DISH
QualityGate
SKA1 LOW Roll-Out Plan
Sit
eIn
teg
rati
on
Tes
t F
acili
ty (
ITF
)
LabIntegration Events
Station Beamformer and Digitiser, SaDT,CSP, TM, SDP
T0 + 12 T0 + 24 T0 + 48 T0 + 60T0 + 36
LVE
AR4AR3AR2AR11Station
2Stations
4Stations
LVE2 LVE3 LVE4
LFAAPRR
Number of SKA1 Stations deployed
Front-End IntegrationINFRA, SaDT, LFAA
QualityGate
SKA1 MID Dish Roll-Out
T0 T0 + 1 T0 + 2 T0 + 3 T0 + 4Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4
0
50
100
150
200
250
Start Construction SKA1
Start Early Science
End Construction SKA1
MeerKAT Science Programme
Start Full Science
MeerKAT Integration
New SKA1_MID Dishes
MeerKAT Dishes
1st Dish
DishPRR
T0 + 5
421 3LVE
1
Array Releases
2
3
4
= 8 Dishes
= 64 Dishes
= 128 Dishes
= 133 + 64 Dishes
LVE = Lab Verification Event
SKA1 LOW Station Roll-Out
T0 T0 + 1 T0 + 2 T0 + 3 T0 + 4Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4
0
100
200
300
400
500
Start Construction SKA1
Start Early Science
End Construction SKA1
Start Full Science
1st Station
1
Array Releases
2
3
4
= 16 Stations
= 64 Stations
= 256 Stations
= 512 Stations
T0 + 5
4
2
1
3
LVE
= Laboratory Verification
Event
LVE
Software Release ManagementS
ite
Inte
gra
tio
n T
est
Fa
cilit
y (I
TF
)
T0 + 12 T0 + 24 T0 + 48 T0 + 60T0 + 36
LVE
AR4AR3AR2AR1
Arb
itra
ry L
oc
atio
n
Laboratory Integration Environment(Software verified against real hardware and firmware)
Development Environment(Software qualified against simulators)
On-Site Environment(Software acceptance tested with production hardware and firmware)
Software Releases
Software Releases
Issues
No Change-Control Under Change-Control
Issues
Integration & Verification Planning
I&V Plan
Verification Requirements
Roll-Out Plan
Contains:· Integration Events· Verification Events· Resources· ...
· System Requirements
· Hosting Agreements· Telescope Verification Plans· Early-Science Plans· Commissioning Plans· SKAO Input· Consortia Input
1
3
2
· SKAO Input· Consortia Input
I&V Planning
Integration / Verification Event 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20SaDT.NSDNLab ver - DISH, CSP, TM, SDP I.Lab.1 *TM.TELMGMT - DISH.LMC I.Lab.2 * *TM.TELMGMT - SaDT.SAT.LMC I.Lab.3 *DISH Receiver - SaDT.SAT I.Lab.4 *TM.TELMGMT - CSP.LMC I.Lab.5 *SaDT.DDBHLab ver - CSP - DISH I.Lab.6 *DISH Receiver - CSP.CBF I.Lab.7 *TM.TELMGMT - SDP.LMC I.Lab.8 *CSP.CBF-SDP.Data Proc I.Lab.9 *Lab System Line up C&M I.Lab.10 *Lab System Line up Data I.Lab.11 *Lab System 4 input Verification V.Lab.2.1 * *INFRA - DISH I.D1.1 * * *SaDT.NSDN - TM / DISH I.D1.2 *TM.TELMGMT - SaDT.SAT.LMC I.D1.3 *TM.TELMGMT - DISH.LMC I.D1.4 *DISH Receiver - SaDT.SAT I.D1.5 *SaDT.NSDN - TM / CSP I.D1.6 *TM.TELMGMT - CSP.LMC I.D1.7 *SaDT.DDBH - CSP - DISH I.D1.8 *DISH Receiver - CSP.CBF I.D1.9 *2nd DISH Integration to INFRA, SaDT, CSP 2 Dish Integration * *INFRA Handover V.D1.1.1 *SaDT handover V.D1.1.2 *DISH Handover V.D1.1.3 *TM Handover V.D1.1.4 *CSP Handover V.D2.1.5 *Dish C&M V.D1.2.1 * *Freq range, Sensitivity V.D1.2.2 *RFI Detection V.D1.2.3 *Channelisation V.D2.2.1 *Basic Interferometry V.D2.2.2 * *Correlator Products V.D2.2.3 *Displays V.D2.2.4 *EMI / EMC V.D2.3.1 * * *Environmental V.D1.3.1 *4 DISH Integration to INFRA, SaDT, CSP 4 DISH Integration * * *SaDT.NSDN - TM / SDP I.D4.1 *TM.TELMGMT - SDP.LMC I.D4.2 *SaDT CSP-SDPInitial local link I.D4.3 * *CSP.CBF-SDP.Data Processor I.D4.4 *INFRA Handover V.D4.1.1 *SaDT handover V.D4.1.2 *DISH Handover V.D4.1.3 *TM Handover V.D4.1.4 *CSP Handover V.D4.1.5 *SDP Handover V.D4.1.6 *Channelisation V.D4.2.1 * *Basic Interferometry V.D4.2.2 * *Correlation Products V.D4.2.3 *Imaging V.D4.2.4 * *EMI / EMC V.D4.3.1 * *
Months since T0
Laboratory
Early Site, 1-2 Dishes
Site, 4 Dishes
• Integration Events• Verification Events
• Start date• Duration• Resources• Prerequisites
• Each event is a workpackage that can be project-managed
Product Hand-Over Planning
Objectives are to ensure that:• A well-defined development process was followed for the
product.• The product meets its technical specifications,
documented by Qualification Test Results (QTRs) and Acceptance Test Results (ATRs).
• The product can be supported and maintained after hand-over.
• The product is successfully installed on-site.• The logistic support development for the product is in
process.
What level of product integration is required from the AIV Contractor?
Installation, Integration, Verification
ShipmentReadiness
ReviewShip to Site
Responsibility reverts to OEM
Install on SiteIntegrate with
SKA1 Telescope System
System Hand-Over
OperateSKA1 Telescope
System
ProductHand-Over
Review
no
VerifySKA1
Telescope System
Product Hand-Over
no
yes
no
yes yes
Responsibility reverts to OEM
Resolve Issue
ProductHand-Over
Review
noResponsibility
reverts to OEM
ProductHand-Over
Review
noResponsibility
reverts to OEM
yes
yes
AIV Contractor Responsibility
Product Contractor Responsibility Operations Team Responsibility
Test Procedure Planning
Requirements
Verification Requirements
Verification Events
System
Test Procedures
Test Configurations
specified by
verified by
fulfilled at
employs
employs
formed by
Test EquipmentSystems Engineering Tool
MeerKAT Integration Planning
MeerKAT Integration: ECP 150006
• Replace MeerKAT’s Receivers (known as “Digitisers”) with SKA1_MID’s Receivers
• Replace MeerKAT’s TFR distribution to each MeerKAT Dish with SKA1_MID’s STFR distribution
• Does not consider replacement of MeerKAT’s Feeds
Limited space inside SDCL-Band Receiver (“Digitiser”)
25 U rack space
• Roll-Out Plan not yet mandatory for Design Consortia• Support of the System-Level ITF not yet mandatory for
contractors• Late release of software/firmware functionality (TM, CSP,
SDP) during Construction Phase– Knock-on effect on Array Releases – Integration Test Facility would reduce the risk of on-site issues
• Underestimating scale and complexity of MeerKAT Precursor Integration
• Participating organisations not delivering on their contributions on time, or to an acceptable level of quality
• Staff continuity
Risks
Thank You