Gary, As noted this behavior has been part of the system for at least 12 years. Probably goes all the way back to Version 1.
Violation of license agreement? Not going to go there. However I will say other vendors require a license for any one that logs in. We were evaluating Mercury ITG a few years ago and even the Customer required a license to view the request. The cost of those licenses were on the same level as a floating license. I mentioned the AR System and floating licenses and the sales rep said 50% discount on the license costs and we weren't even near a purchasing decision. Misi has a good system for how to allocate fixed and floating. I gave a presentation a couple of years ago at User World in San Francisco on the same thing. I only looked at who is making modifications during peak hours. Didn't get in to nitty gritty concerning submitter and assignee permissions for the person making the modification. Just assigning fixed licenses based on modifications during peak hours. ------Original Message------ From: Opela, Gary L CTR USAF AFMC 72 CS/SCBAH To: Arslist ReplyTo: Arslist Subject: Re: floating licenses Sent: Dec 17, 2008 9:13 AM Yeah, but this is a ridiculous assertion, and its ridiculousness is proven by my statistics. For instance, I have one user that, in the last 17 days, has Modified 298 of his own tickets, but only 2 of other people's tickets, so you can look, there are probably 298 times he has search, and would have consumed a license, whenever he didn't need to. I have another person, who in the last 17 days, has modified 243 of his own tickets, and 0 other people's tickets. This guy is not a candidate for a read-only license, because he has the propensity to need to modify someone else's ticket, he just hasn't had to yet this month. I have a ton other people that have modified over 100 of their own tickets, and little to none of other people's tickets. This is going to cause me to consume far more licenses than I need, and in my opinion, is in violation of the license agreement, although that's not my call, and I'm not a legal-speak person. I'm just a lay man that understands the license policy to simply state that a write license is only required when you modify someone else's ticket, but if I have 25 floating licenses, and 25 people run a search at the same time, consuming those 25 licenses, and then within five minutes, person number 26 tries to modify someone else's ticket, he won't be able to. Gary -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Shellman, David Sent: Wednesday, December 17, 2008 8:08 AM To: arslist@ARSLIST.ORG Subject: Re: floating licenses Gary, Many of us have been saying that for a long time. It's a floating write license. Searching shouldn't have anything to do with the assignment of the floating license. I have heard Doug Mueller say that the assumption is that if you execute a search, you will be making a modification soon. Therefore the licenses are assigned with a search if they are available. Dave ------------------------- dave.shell...@tycoelectronics.com (Wireless) ----- Original Message ----- From: Action Request System discussion list(ARSList) <arslist@ARSLIST.ORG> To: arslist@ARSLIST.ORG <arslist@ARSLIST.ORG> Sent: Wed Dec 17 08:48:14 2008 Subject: Re: floating licenses Dave, thanks for responding. I understand how licenses work, I just do not think that a float license should be assigned until such case that one is needed; it messes up how many licenses are actually needing to be used at one time. > As defined, "When a search, modify, or submit is performed, AR System checks for an available Floating Write license token. Why should it? A write license is not required at this point unless/until a modify of another person's ticket is occurring, with submitter mode locked. If it is consuming a license prior to this point, basically any time the user uses the system, then I'm using more licenses than I should be. That means that if I have 100 users that might modify 5 other people's tickets per month, but 200 of their own, then I most likely will be running out of licenses every day. I should be able to have 25 licenses for 100 users if they each only modify five tickets per month, because they each only require a write license for those five modifications. I wrote filters that track the different submit/mod own/mod other each time someone performs one, and it increments a counter in another table so that I know exactly how many licenses I need. We currently have everyone on fixed licenses, but I think that is a waste. Thanks, Gary Opela, Jr. -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Easter, David Sent: Tuesday, December 16, 2008 7:15 PM To: arslist@ARSLIST.ORG Subject: Re: floating licenses ** > In the mid-tier, it's 15 minutes The floating license time-out on the Mid-tier can be no less than one hour currently. > Basically, if the user is just submitting, modifying their own, and querying, will remedy go ahead and assign a ticket[sic]? As defined, "When a search, modify, or submit is performed, AR System checks for an available Floating Write license token. If a token is available, the user is granted write access to requests. If no tokens are available, the user is notified and continues to use the Read license until a token becomes available." (Concepts Guide - AR System 7.1.00 - Page 57) -David J. Easter Sr. Product Manager, Solution ------Original Message Truncated------ Dave ------------------------- dave.shell...@tycoelectronics.com (Wireless)
