Automatic Throttles in Teradata 14.0 and 14.10 - comment by joe.ruvolo

Carrie
We have some questions around the throttle rule type definitions of Collective, Individual, Member and Global.  When we first upgraded from v13.10/SLES 10 to v14.10/SLES 11, the TASM rules converted had selected a rule type of 'Collective', and thus with a concurrency limit of 4, we were only getting 4 queries across the entire system at a time; all others were delayed.  We quickly found the issue, and changed the throttle setting to Member, which seemed to resolve the issue.
However, we've recently found that under heavy usage, our throttles don't seem to be working as we expected.  For example, we have a throttle named 'Cognos User', which is set at a Rule Type of Member.  Its Classification is set at Request Source, Include (Profiles: AG_PROFILE, COGNOS_USER_PROFILE), and Query Characteristics set to include only queries using all AMPs.  State settings set the Concurrency to 4, Delay. These 2 profiles define all our Cognos users. 
We've found that we are only getting 4 Cognos queries running concurrently; other cognos queries are getting delayed.  With the above throttle settings, we expected the 'Member' Rule Type to limit to 4 concurrent processes per each member of the group.  But that is not what we are seeing.
Are we not understanding the Rule Type definitions?  The definition of rule type 'Individual' says it creates 1 queue for each object.  'Member' syas it creates 1 queue for each user, which is why we went with Member.
Appreciate any insights you have on the Throttle Rule Type definitions...
Thx!
Joe