Documentation text of B.141
State of a battery of an MDS.
The current power source is designated by ./@ActivationState:
- If ./@ActivationState equals "On", the device is running on battery
- If ./@ActivationState equals "Off", the device is in mains operation and currently not able to be run on battery
- If ./@ActivationState equals "StndBy", the device is in mains operation and can be switched to run on battery
- If ./@ActivationState equals "Fail", the battery has a malfunction. Detailed error information SHOULD be communicated by using an ALERT SYSTEM.
Enumerations "Shtdn" and "NotRdy" are undefined for BatteryState.
Requirements split
The B.141 description contains two requirements,
- A should that is explicitly mentioned as SHOULD in the last bullet point of the enumeration
- The enumeration itself is normative text and ought to be phrased as a SHALL level requirement
Hence, the documentation should be split into to requirements.
Activation state override
B.141 overrides the ActivationState semantics and excludes usage of NotRdy and Shtdn.
- Mains supply should not be included here. Instead, the status of the mains supply should be modelled as a metric - or by another means. As of now, the ActivationState depends not only on the activation state of the battery but also on the activation state of the mains. This causes conflicts in cases where multiple batteries are available and only one is being discharged at a time (for which then there is no suitable activation state anymore -> think of two batteries, one is in use and being discharged (On) and the other one is still Off - but not allowed to be Off as this implies running on mains).
- NotRdy may be required during the boot phase of the device when a battery status isn't available yet.
Do we need a new element to model mains power or is it enough to include an attribute in MdsState?
Copied this comment to Revision ticket [#25].
Related
11073-10207 Revision: #25
Done in PR#282.