In an imported ProcessBook display, I would like to see the same behavior in Coresight and in ProcessBook regarding changing the time context. In short, we want the value displayed to be based on the End Time of the display. We see this in ProcessBook, but not in Coresight.
Let’s say we have a ProcessBook PDI file that has a trend with a default span of 7 days. This PDI is viewed both in ProcessBook and via Coresight.
On that trend we have pi tags that are getting updated frequently. Above the trend we text that displays the address and lat/long of the location of the field device.
The address and lat/long are AF Attributes that are hand entered when they change. Each is a configuration item such that when we check it in and select Create Revision, AF retains the history for these values.
Now let’s consider 3 scenarios and contrast the behavior between PP and Coresight. Let’s say the location of the device changed on Jan 1 at noon.
Situation 1 : View the PDI where both start and stop times are prior to Jan 1.
Behavior in ProcessBook: The previous values for address and lat/long are shown.
Expected behavior.
Behavior in Coresight: The previous values for address and lat/long are shown.
Expected behavior.
Situation 2: View the PDI where the start is Dec 27 and end time is Jan
Behavior in ProcessBook: The new values for address and lat/long are shown.
Expected behavior.
Behavior in Coresight: The previous values for address and lat/long are shown.
UNEXPECTED BEHAVIOR.
Situation 3: View the PDI where the start time is after Jan 1 at noon.
Behavior in ProcessBook: The new values for address and lat/long are shown.
Expected behavior.
Behavior in Coresight: The new values for address and lat/long are shown.
Expected behavior.
Coresight is not behaving like ProcessBook. In PB the values of AF Attributes are the values at the STOP TIME. Coresight is the opposite, showing values at the START TIME.
When people change the time range in PB, the address changes based on the end time; they can scroll back and look at data and know where the unit was. Given we’ve done this for years, my users realize and expect the values to be current at the END TIME of the displayed time range. If you open a trend, the values listed on the right are the values at the END TIME. Thus this is the expected behavior.
We would NOT want the address data to stay the same as we change the time range. Neither would we want it to be the value at the START TIME.
We would want the values to reflect the latest value based on the time range chosen—not the earliest values. I realize when the values change during the time range specified, you have to pick one value to display. I’m asking that you do in Coresight what has become the established norm in other products—display the most recent value of the time range shown.
