access:internet_key_vision
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
access:internet_key_vision [2011/01/25 00:44] mikeclapp |
access:internet_key_vision [2012/10/10 16:18] (current) |
||
|---|---|---|---|
| Line 121: | Line 121: | ||
| These are questions we need to ask sales/marketing in order to give the correct answer for billing. These are billing reports and I can imagine that we'll need several versions including details and summaries. | These are questions we need to ask sales/marketing in order to give the correct answer for billing. These are billing reports and I can imagine that we'll need several versions including details and summaries. | ||
| - | {{:rental_report.png?220x238}} | + | |
| + | **Monthly Report by Company** | ||
| + | |||
| + | {{rental_report.png?440x476}} | ||
| Line 127: | Line 130: | ||
| Total Usage Summary | Total Usage Summary | ||
| - | Report per company | ||
| == Company Hours by Key == | == Company Hours by Key == | ||
| - | {{:keynumberreport.png?332x321}} | + | {{keynumberreport.png?332x321}} |
| == Company Hours by User == | == Company Hours by User == | ||
| This is the existing report. What's not shown that could be is which key a user used to accumulate those hours. We don't have that capability with the Solo Server. | This is the existing report. What's not shown that could be is which key a user used to accumulate those hours. We don't have that capability with the Solo Server. | ||
| - | {{:keysbyuser.png?344x353}} | + | {{keysbyuser.png?344x353}} |
| Line 142: | Line 144: | ||
| The point of this report is to see where users are failing to get keys and identify who's running their keys to capacity. It'd done with a lot of inference that a failure on checking a key out is because someone has a key. If it's possible, a better way may be to measure utilization. If a key is checked out all the time it might represent just one user that never checks it in. It doesn't tell us much in that case. A more interesting one to us for marketing is when their are multiple users and the percentage of checkout time vs. the day. It would probably use the 8 hours out of every 24 as a baseline of full utilization. This is an area that we should think about in an effort to understand usage better. | The point of this report is to see where users are failing to get keys and identify who's running their keys to capacity. It'd done with a lot of inference that a failure on checking a key out is because someone has a key. If it's possible, a better way may be to measure utilization. If a key is checked out all the time it might represent just one user that never checks it in. It doesn't tell us much in that case. A more interesting one to us for marketing is when their are multiple users and the percentage of checkout time vs. the day. It would probably use the 8 hours out of every 24 as a baseline of full utilization. This is an area that we should think about in an effort to understand usage better. | ||
| - | {{:keyavailabilityreport.png?331x298}} | + | {{keyavailabilityreport.png?331x298}} |
| === Logging === | === Logging === | ||
| Line 180: | Line 182: | ||
| **Existing Application Screen** Includes Hasp Support which we have no plans for on this server. | **Existing Application Screen** Includes Hasp Support which we have no plans for on this server. | ||
| - | {{:keymakeruserservice.png?504x370}} | + | {{keymakeruserservice.png?504x370}} |
| **Functions** | **Functions** | ||
| Line 190: | Line 192: | ||
| * Kills keys (dum-dum te-dum dum dum da dum da dum) | * Kills keys (dum-dum te-dum dum dum da dum da dum) | ||
| * Prints billing reports | * Prints billing reports | ||
| + | * Transfers keys to different companies/branches | ||
| + | * Updates company names to reflect database changes (name changes) | ||
| Line 198: | Line 202: | ||
| **Existing Application Screen** This supports HASP keys as well and will probably be simplified for Internet Keys | **Existing Application Screen** This supports HASP keys as well and will probably be simplified for Internet Keys | ||
| - | {{:keymakerbuild.png?504x370}} | + | {{keymakerbuild.png?504x370}} |
| **Functions** | **Functions** | ||
| Line 233: | Line 237: | ||
| This is unchanged from current desktop apps. | This is unchanged from current desktop apps. | ||
| - | {{:dtlogin.png|}} | + | {{dtlogin.png|}} |
| == Keys Available == | == Keys Available == | ||
| Line 244: | Line 248: | ||
| - | {{:dtavailable2.png|}} | + | {{dtavailable2.png|}} |
| Line 250: | Line 254: | ||
| This is a new admin screen for assigning users to key. It's accessed by selecting a key and pressing the User button. It displays all the users for a company, sorted first by users with the key enable, and alphabetically on the user login. This means it's easy for an admin to see who's on a key at the top of the list but find users that aren't enabled more easily in list below. | This is a new admin screen for assigning users to key. It's accessed by selecting a key and pressing the User button. It displays all the users for a company, sorted first by users with the key enable, and alphabetically on the user login. This means it's easy for an admin to see who's on a key at the top of the list but find users that aren't enabled more easily in list below. | ||
| - | {{:dtuserkey.png|}} | + | {{dtuserkey1.png|}} |
| == Keys in Use == | == Keys in Use == | ||
| - | {{:dtinuse.png|}} | + | {{dtinuse.png|}} |
| == User Admin == | == User Admin == | ||
| - | {{:dtuseradmin.png|}} | + | {{dtuseradmin1.png|}} |
| - | {{:dtuseradminmenu.png|}} | + | {{dtuseradminmenu1.png|}} |
access/internet_key_vision.1295916264.txt.gz · Last modified: 2012/10/10 16:18 (external edit)
Page Tools
