<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://communities.bentley.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>jwillie's Communities Activities</title><link>https://communities.bentley.com/members/c31a0a6e_2d00_cd53_2d00_4ce0_2d00_b9b9_2d00_2e3637b2eb9a</link><description>Recent activity for people in jwillie's community</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>CALENDAR HOUR TIME-KEEPING IS THE PROBLEM!</title><link>https://communities.bentley.com/communities/other_communities/licensing_cloud_and_web_services/f/forum/101656/calendar-hour-time-keeping-is-the-problem</link><pubDate>Thu, 09 Oct 2014 16:03:44 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:5d21d307-f1af-4111-9090-df5c0c600e43</guid><dc:creator>jwillie</dc:creator><description>&lt;p&gt;As has been posted in other threads, the calendar hour time-keeping method has been giving a lot of people grief.&amp;nbsp; To me it really is the source of all of the overuse issues for companies like mine who are more than willing to pay for a set number of licenses which are not overused during any given moment.&amp;nbsp; Bentley needs to change their calendar hour time-keeping method to instantaneous time-keeping so that however many licenses you own (3 in my case) can be used by however many users want to access it (3-at-a-time in my case).&amp;nbsp; So, if 20 people want to use 1 license in the same calendar hour, they would simply have to use it for an average of 3 minutes each.&amp;nbsp; With an instantaneous time-keeping method in place, there would be no overage!!!&amp;nbsp; What a concept!&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s keep this thread with respect to only the calendar hour issue.&amp;nbsp; Please reply accordingly.&amp;nbsp; CALENDAR HOUR TIME-KEEPING NEEDS TO GO!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>