That is not what we are seeing. If you give somebody an "Incident User" license of "Float" type, they don't show up as consuming a "write" license unless they are in the Incident console or when they login their home page is set to the Overview console or Incident console via overview.
So, if you have some folks who just need to do change and very rarely do Incident work, I'd set them up with their home page being the change console. If they don't go over to the Incident console, their "float" license for Incident won't ever change to "write" as near as we can tell. The problem comes in when your entire support staff utilizes the overview console for everything. In version 7.6.04 this presents a problem as all of the users will automatically pull a "write" license for Incident any time they login or refresh the overview console. We are taking 2 approaches. 1. We've written some queries to identify the people from the RRR License optimization output that have consumed an Incident license but have never updated an incident record. This was as simple as pulling all the unique login ID's from the audit log on HPD and the last modified by on the HPD forms and comparing to the RRR output. The net difference are the users who really don't need a "write" license so we will convert them all to Incident Viewer 2. We are in talks with our account manager about what to do with our upcoming renewals and we believe the best bet is to renew at the same amount as last year and then re-evaluate after 9.0 is installed. I'm hopeful that we will find what Doug has said to be true which should result in a significant decrease in the amount of "write" licenses (Float or Fixed) that the RRR License output tells us we need. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
