359   Range Min/Max configuration as new range states

Created: 13 Aug 2006

Status: In Force (green)

Part: Part 7-3 (2003)


Page: 55

Clause: 8

Paragraph: Table 48

Category: Issue for edition 2 of this part


There is no way today to trigger a report (log entry) on a dchg when a value reaches the configured value of MAX or MIN limit.

The quality changes in these cases - but in many cases people may not trigger on quality changes at all.


In table 48 (page 55) replace the top "high-high" value by "max" and the bottom "low-low" by "min".

In the range configuration additionally change "max" to "maxlim" and "min" to "minlim" ... to prevent the different uses of the terms "max" and "min".

Discussion Created Status
29 May 07 In Force (green)
Min and max are process limits and therefore no trigger points. If you still want to get informed when you cross the process limit, this can be done by triggering on quality change.

Proposed to not accepted the TISSUE
19 Apr 07 Ballot Period
I think this needs further discussion. The current interpretation is, that a value can not become higher than the max or min value. That is, why the quality changes to questionable when the value leaves the range defined with min and max, assuming, that this serves as a consistency check. So I see no need, why I would like to trigger on something, that can not happen (if it happens, it means a failure that has an impact on the quality). 15 Apr 07 Discussion (red)
suggestion: introduce max and min additionally to high-high and low-low for the range attribute, leave quality questionable for them. 14 Aug 06 Discussion (red)
There are a lot of applications which need two pairs of limit, so we should not use high-high / low-low for other purpose. Further, if people need this indication, but 'forget' to set trigger option qchg, I consider this as a configuration error. Finally, we have a range attribute. This is send on dchg trigger, and could also show that the value is above max or below min. 14 Aug 06 Discussion (red)


Privacy | Contact | Disclaimer

Tissue DB v.