OPAF are asking questions about the proper use of BadOutOfRange.
Some OPAF members have used BadOutOfRange as a StatusCode for a variable to indicate an instrument is out of range.
I suggested it is more appropriate to use UncertainOverRange and UncertainUnderRange since the instrument is providing a signal (i.e. not bad) but it is out of ranging suggesting something may be wrong.

I also suggested the use of BadOutOfRange isn't intended as variable status code. It is intended to be used as a response code for a request which contains an argument which is out of the expected range.

OPAF have request an official statement regarding the expected usage of these codes.