OK, thanks for making sure I didn't go off in the wrong direction--
well, because you want to display these comparison values on a
dashboard, we're going to have to use a measure or a KPI, even though
these value really are member properties rather than a "real" measures
or KPIs.
There are several parts to this:
1) Add two properties to your station class to contain the data. (Or
put it in another class that is one-to-one with your station class.)
You have two cutoff points, so maybe call these properties
LowestAveragePerformance and HighestAveragePerformance.
You said before that users need to edit these values. You could create
a Zen page for that or any other user interface. DeepSee won't care
where the data comes from.
2) In the Architect, BI-enable the station class and create two
measures, one based on each of these properties. As I commented
before, these measures make sense ONLY when used at the station level;
they are meaningless when aggregated across stations, so we won't use
them that way.
Now that we have the raw ingredients...
I don't know exactly how you want to use the data in a dashboard, but
here's a possible scenario:
3) In the Analyzer, create a string-valued measure or a computation
(as needed) called Performance Rating. The definition uses this logic:
$SELECT
(performance<LowestAveragePerformance:"Poor",performance<HighestAveragePerformance:"Average",:"Good")
or something like that.
Or create a numeric measure or computation that equals either 1, 2, or
3. Display this in your pivot table and attach an alert to it.
If it's a measure, you can create a KPI based on it and attach display
rules to that KPI. Use this KPI only when displaying one station at a
time (e.g., one station on the dashboard or one station per row in a
pivot table).