Datastream 7i assigns calibration statuses at the calibration header level and at the test point level. Calibration statuses are assigned based on the data entered for test points on the Calibration tab of the Work orders form (WMJOBS).
The Calibration status is based on the status of all its test points. The calibration fails if one test point fails. The Calibration status passes only when all of the test points pass. Test points are not considered passing if the test point status is set to recalibrate. For all other cases, the Calibration status is incomplete.
Datastream 7i determines the status of an individual test point based on the based on the Device reading for the test point and the specified tolerance for the device. There is an "as found" status and an "as left" status for each test point. The as found status indicates the status of the test point prior to the calibration process. The "as left" status indicates the status of the test point after the calibration test point.
Datastream 7i determines the status of the calibration header whenever a test point is inserted, updated, or deleted. If any one of the test points fails, then the calibration header also fails. A failing test point must be recalibrated until it passes.
The following diagram illustrates how upper and lower limits and tolerance ranges relate to a test point and its status.
There are a number of measurements and standards that can be set for test points on a category and/or an equipment level.
Refer to the following list for an explanation of the different calibration statuses.
Pass (P)—Datastream 7i assigns passing status to the test point if the reading entered for the test point is within the specified tolerance for the test point. No failure occurred, nor was any recalibration required. Within the passing status there are three possible sub-statuses: Pass, fail exists (PF); Pass, recal exists (PR); and Pass (P). Passing status is applied at both the work order header and the test point level.
Fail (F)—Datastream 7i assigns failing status to the test point if the reading entered for the test point is outside of the specified tolerance for the test point. Failing status is applied at both the work order header and the test point level.
Incomplete (I)—Datastream 7i assigns incomplete status if data has not been entered for any one or more of the test points. Incomplete status is applied only at the work order header level.
Not applicable (N/A)—Datastream 7i assigns this status to a test point if you have selected Not applicable for the test point. The status for the test point will always be not applicable, and the test point status does not affect the Calibration status for the calibration header. Not applicable status is applied at only the test point level.
Pass, fail exists (PF)—The PF status is a sub-status of passing status that indicates that the "as found" calibration reading for the test point failed. However, the "as left" reading passed. This status is used for calibration reporting to report more detailed information regarding specific test points for calibration tracking. PF status is applied only at the work order header level.
Pass, recal exists (PR)—The PR status is a sub-status of passing status that indicates that an "as found" or "as left" test point reading reached alert levels before passing. This status is used for calibration reporting to report more detailed information regarding specific test points for calibration tracking. PR status is applied only at the work order header level.
Recalibrate (R)—Datastream 7i assigns this status to a passing status if you have specified a Service % indicating the service/alert limit for the test point and the deviation for the test point is greater than the specified service percentage. The recalibration status does not indicate that the device is out of calibration. The recalibrate status is considered passing, but it indicates that the reading is not as close to the specified tolerances for the test point as is desired. Recalibrate status is applied at only the test point level.
Refer to the following example for further clarification of calibration statuses.