Upper Limit of MMC Position Issue

[[Sa...]]

I am trying to figure out how to save calculated bonus tolerances, to apply them on a per-sample basis.

Our system right now updates the Upper Limit with each new sample. Which then sets the characteristic attribute across the entire inspection plan. I want to differentiate the Upper Limit and the Calculated Upper Limit as it applies to each specific sample.

 

Most Recent Sample StandardProtocol Printout:

The bonus tolerance for our most recent sample was calculated as 0.3111. This value is then instantly saved as the K2111 Characteristic Attribute, overwriting past values.

 

Calculated Bonus Tolerance Saved in Planner:

With each sample, the Upper Limit is overwritten.

 

 

Samples with Mismatched Upper Limit:

When we pull the data through our multi-piece report later, it only uses the most recent sample's Upper Limit, since that is how Upper Limit is saved. Which is inaccurately calculating conditional formatting rules highlighting outages.

Upper Limit Callout - ${Qdb.Characteristic(2111)}

I am trying to pick brains to see if anyone has a solution to save each calculated bonus tolerance as its own independent variable, on a per sample basis.

Something that takes a snapshot of the Upper Limit after each sample and saves it as a measurement attribute of the sample.

 

Any tips/tricks would be greatly appreciated.

 

Thanks! 

 

 

 

[[Pi...]]

If you are using PiWeb reporting - I'm not sure is it possible - You may try to use PCM/Calculated characteristics and play with that.

If you have PiWeb SBS/Enterprise you can try to make calculated characteristics on server and test this.

On top of that you might try to create pure custom report that suits your needs.