Telescope Manager (TM) has made good progress with respect to the sub-element level Requirements Baseline (RBL). Three out of the four sub-element level RBLs have been formed whereas the last one is in the process. After a delay of a couple of months, we have now submitted a data pack as part of the TM Design Baseline to the SKAO for review. Most of the planned prototyping work has been completed and the report of the outcome of the work has been submitted to the SKAO. We are now focusing on the sub-element level Design Baselines (DBL).
The summary of the work taken up since the last reporting, key events and accomplishments are as follows.
The Prototyping Report was finalised and issued to the SKAO for review in October. The outcome of each prototype has been captured in this report, vis-a-vis the initial objectives. The prototyping activity has been concluded for all except two prototypes: LINFRA and LMC Interface Simulator. No major surprises have revealed so far by the prototypes that indicate major risks in the design. One more version of the Prototyping Report is expected in the first quarter of the next year which will include the outcomes of the remaining prototypes.
Revised TM Cost Estimates
The next round (Version 3) of the TM Revised Cost estimates were prepared and submitted to the SKAO ahead of the IGO meeting in September. Overall there has been a reduction of 5% compared to previous version (from 51.26 to 48.69 MEuros). This reduction was mainly due to a substantial reduction in Level 3 LINFRA (both Software and Hardware) estimates. In addition to the estimating process, this version of the Cost Model undertook an external review of the Version 2 and Version 3 of the Cost Model spreadsheet.
Further design work will likely result in some cost reduction by reducing risk, refine the contingency estimation and a better understanding of the products needed to be developed. This design work is part of the on-going pre-construction activities and will be incorporated in subsequent versions of the Cost Model next being planned early February 2017.
Element Design Baseline (DBL) – M17
After much anticipation, TM Design Baseline has made good progress. After rigorous internal review and addressing over 300 review comments, the main TM Design Report has been updated and circulated to the SKAO for review. The other documents accompanying the TM Design Report as part of the TM DBL, are internal ICDs and the Maintenance Plan. We aim to form the TM DBL by December end. However, this will depend on the availability of SKAO personnel to review the documentation in time.
Sub-Element (ObsMgt, TelMgt, LMC and LINFRA) Requirements Baseline – M18 and M20
ObsMgt, TelMgt and LMC Requirements Baselines have now been formed and that completes the planned major milestone M18 though we achieved it with some delay. The remaining LINFRA Requirements Baseline (M20) is under review currently and the observations from the review are being looked at. We hope to conclude on the process and achieve the milestone M20 in the near future.
SKA Engineering Meeting and TM Face-to-Face (F2F) Meeting in South Africa
All TM sub-elements were well represented at the SKA Engineering Meeting. This meeting provided an opportunity for the inter-consortium and the SKAO interactions on various issues, areas and had fruitful discussions.
This was followed by a two-day TM F2F meeting organised in Pineland at the SKA SA office. Important topics like progress on the TM architecture, costing, evaluation and reuse of precursors and pathfinders, operations, etc. were discussed. As part of the agenda, a MeerKAT Demo was arranged by the SKA SA team and this was followed by a guided tour of the MeerKAT set-up which turned out to be very useful. Apart from this, the stock of the ongoing CDR work was taken and the plans for the future were discussed which resulted in revised dates for the remaining CDR milestones.
TM Board has set up an internal panel to evaluate the work done for the monitor and control systems of the GMRT and MeerKAT facilities, and make a recommendation to the TM Board by January 17, 2017 as to how these efforts can be leveraged for SKA TM.
The GUI Team had interviews with the MeerKAT operators for a couple of days at the SKA SA office in Pinelands following the SKA Engineering Meeting.
TM has now been officially asked by the SKAO to prepare a design for the Authentication and Authorisation (A&A) implementation for the SKA, and this now forms part of the TM work package. A&A Requirement Specification prepared by TM has been submitted to the SKAO as an input to L1 Requirements Rev 10.