Hi John,
Christmas break was wonderful thanks, back to reality with a bump today though
Well for the project I mentioned earlier I ended up building a state of the art monitoring display in ProcessBook; I say state of the art because it can't currently be replicated it in the control system

Anyway...
I can't show you the actual display but I will certainly give you some information on the way I did it, you can pick what best fits for your situation. For me, ProcessBook was a must.
1. The display could be used in two modes - daily (trends show only the situation since midnight by default) and half hourly (show last 16 periods i.e. last 8 hours). All trends show the limits, average and current value of the component. You can toggle between daily/half hourly and because of the strong naming convention for the tags, it was a matter of changing the tags and everything else self adjusted (you can use ERD in the latest ProcessBook). For example, current value PI tag "Emissions.Component", half hourly average "Emissions.Component.Average.HalfHourly" (daily="Emissions.Component.Average.Daily"), halfhourly limit "Emissions.Component.Limit.HalfHourly", daily limit "Emissions.Component.Limit.Daily" etc...hopefully you get the idea. Then you could simply just change all the halfhourly tags for daily and the bar symbols (see next section) alter accordingly.
2. I made heavy use of the Bar symbol so you have a bar as the background that showed: a) The upper range of the measuring instrument b) The limit for the component. Then overlaid was another 2 bar symbols that showed the current value and the average (daily or halfhourly). Playing around with the colours mean you end up with a neat looking bar representation of the data.
3. There were trends along side each bar to act as quick reference points for the past behaviour of the component.
4. I added some additional calculations to give "hints" as to the maximum value for a component for the remainder of the time period to ensure a limit is not breached. This went down very well, in fact we even talked about adding some complex calculations that would predict how other components would behave by adjusting others...
5. When a limit is breached then another set of tags record the number of limits for each average. These are displayed at all times for the current day. Once a limit is breached a report must be filled out (in an Excel built system) and if there are any outstanding reports then the display bugs the operators until a report is completed. Once a report is completed, the outstanding reports PI tags are reset.
There were a few other supporting displays that explained the calculated values and other associated measurements of interest.
With all this in mind, if you were looking to evaluate this approach with performance equations you could do something like:
Current Value PI Tag:
"Emissions.Component"
Daily Average PI Tag:
"Emissions.Component.Average.Daily"
Code:
TagAvg('Emissions.Component','t','*')
Half Hourly Average PI Tag:
"Emissions.Component.Average.HalfHourly"
Code:
TagAvg('Emissions.Component','*' - ((minute('*')*60)+Second('*')) +(if Minute('*') >= 30 then 1800 else 0),'*')
etc
Hope this helps.
Cheers.
Principal Consultant
Real-Time Data Management @ Wipro Technologies