CLONE - Review TM - INFRA interfaces with BMS to capture how alarms and events should be propagated and defined in the light of operational requirements

This enabler is continuation of SP-956.

At this stage we are receiving inputs from CSIRO and SARAO operations teams that inform updates to the ICDs, and possibly BMS specifications.

• Updating of ICDs will continue in first few sprints of PI8 (aiming to have first draft updates ready by mid September 2020).
• ICD update after review and assistance with creation of an ECP (aiming for mid October 2020).

Refer to TM-BMS preparation and roll-out (an Operations interaction view).

Original SP-956 description

After the operations review of engineering and operational scenarios, a number of gaps have been highlighted in the interfaces between TM and the building management system (BMS).

This work has highest priority because INFRA contracts will be among the first to be issued and locking the implementation of the BMS to a predefined set of parameters without a clear mechanism to allow change and refinement is potentially a high risk.

After a dedicated workshop https://confluence.skatelescope.org/display/SE/2020-05-19+-+Architecture+CoP+Meeting+focused+on+TM-BMS+interfaces it is understood that all Process Values are available to TM via the BACnet and the OPC-UA interfaces.

From that workshop some key actions resulted:

To be implemented by a SAFe team:

In particular we still need to investigate how the BMS behaves regarding Alarms and Events, how can these be made available to the operator? TM will be used to forward attribute values to the EDA, but there is no description of Alarms and Events in the current interfaces.

It is decided that in the MID case an investigation will occur to understand how this is currently handled in MeerKAT, while for the LOW telescope further investigation will proceed based on the design doucumentation.

To be implemented by the Operations team:

In addition it is noted that operations will need time, experience and cycles of usage in order to reach stability in the definitions of parameters that TM shall collect from the BMS, thus some flexibility is required:

• generate a classification of devices and related attributes to be monitored. This will be attached to the BMS specs. this is a forum activity.
• refine what BMS LOGs is: Process Values, Alarms and Events.

The ICD updates shall take into account the results of the ECP-200007 (TRKECP-22 , PIM-22 and PIM-33) and include the associated documentation updates.

Document updates to be delivered in the Solution Intent space here:

https://confluence.skatelescope.org/display/SWSI/TM-BMS+ICDs