Deviations from requirement
During the development of the IAS, we sometimes deviated from the requirement defined in the ALMA memo.
The runningId was thought to recursively build the path of the IASIOs inside the IAS being something like supervisorID@DasuId@ASCEID@AlarmId.
We have found that it is better to associate the type of each item together with its identifier to have better controls at run time.
We introduced the fullrunningId that is an extension of the runningId: the example before becomes something like (supervisorID:SUPERVISOR)@(DasuId:DASU)@(ASCEID:ASCE)@(AlarmId:IASIO).
An alarm can be set or cleared and have 4 priorities: LOW, MEDIUM, HIGH, CRITICAL. When the alarm is created, it has by default priority MEDIUM` that can be changed by the transfer function of the computing element at run time.
Another solution could be that of setting the default priority in the CDB but it would require more time to configure the CDB and/or the development of specific tools to update the default of each alarm.
There are alarms that cannot be shelved. This could be set in the CDB but an easier solution is to assign a priority of CRITICALto the alarms that cannot be hidden. Or, if you prefer, the IAS does not allow to shelve CRITICAL alarms.
