Sorry, this was in a table, but the format was changed when posted. The term to be added is first and the "example" is in the parentheses:

Active      "Demand Response Active"
Demand      "Chiller Demand Limit"
Enable      "Demand Response Enable"
Limit       "Chiller Demand Limit"
Maximum     "Primary Chilled Water Pump Speed Maximum"
Minimum     "Primary Chilled Water Pump Speed Minimum"
Position    "Cooling Valve Position"
Primary     "Primary Chilled Water Pump Speed Maximum"
Pump        "Primary Chilled Water Pump Speed Maximum"
Response    "Demand Response Active"
Run         "Primary Chilled Water Pump Run"
Secondary   "Secondary Chilled Water Pump Speed Maximum"
Speed       "Primary Chilled Water Pump Speed Maximum"
Stage       "Demand Response Stage"
Static      "AHU Supply Static Pressure"
Supply      "AHU Supply Static Pressure"

Kevin... Does run mean, the actual command? Meaning, start stop?

Jason...could be a run command or a run (or running) status.

The use of run is tricky. I know in our work I've longed for the ability to differentiate between an enable tag and a run tag on a cmd point.

It's one of those tricky areas and can be different depending on how a system is programmed.

As I see it there are at least the following cases in this area:

• enable mean the equip can run if told to by another command, but won't necessarily run
• run can mean the actual command to start/run an equip, or it could be the same as enable if the equip makes up it's own mind when it should run
• run can also be applied to the status feedback from an equip to communicate it the equipment is running
• status can also be applied to the previous point

So I'm not sure how we cover off these different use/cases for these tags, maybe we could include them in the spec but leave their use up to the discretion of the integrator. Not sure.....

There may even be more that I haven't worked out here.