#415 How to handle MaxTechnical/PhysiologicalParallelAlarms

[Clément Ledoux]

Based on APKP discussion, the following ticket is created (https://github.com/ornet-ev/apkp/issues/89):
BICEPS defines AlertSystemDescriptor/@MaxPhysiologicalParallelAlarms and AlertSystemDescriptor/@MaxTechnicalParallelAlarms, but some devices have an upper limit for the sum of the number of physiological and technical alarm limits, but no separate limit for each kind. E.g. a device which can support up to 4 alarms could set both values to 4, however, a consumer might incorrectly assume that the provider supports a total of 8 alarms.

Therefore, I suggest the addition of an optional apkp:MaxParallelAlarms extension for pm:AlertSystemDescriptor, which includes this number.

The standard should also address whether to set AlertSystemDescriptor/@MaxPhysiologicalParallelAlarms or AlertSystemDescriptor/@MaxTechnicalParallelAlarms. Since APKP-support is optional and not setting them implies unlimited alarms, I think the correct approach is to set all three attributes to the same value.

Another question: Do we need to distinguish between alarms and advisories? Some systems may have an upper bound on alarms, others on alerts.

[David]

2026-05-11: Can potentially be incorporated into revision. As this appears to be another UI hint, it should not be necessary to have it in BICEPS, though.