White Paper. LAMUM Usage Reports Tutorial (8.1)

Transcription

1 1 LAMUM Usage Reports Tutorial (8.1) White Paper LAMUM can generate hundreds of different Usage Reports. Some are Current Checkout Status reports and some are Historical Usage reports. Analyzing usage and trying to determine what, if any changes need to be made in your license inventory is like solving a puzzle. Each report is a piece of the puzzle. Each report will tell you something different. But once the pieces are in place the puzzle is solved. The purpose of this white paper is to describe the various reports and try to explain how they can be interpreted. It will be up to you to determine which reports are meaningful, and when you want them created.

2 Index 2 Current Checkout Overview Current Checkout Details by Tool (Tag) Current Realtime information Current Gas Gauge Display Borrowed Licenses report History: History/Graph by Tool (Tag) User Details by Tool (Tag) Group Details by Tool (Tag) Heatmap of Checkouts by Tool (Tag) Heatmap of Denials by Tool Concurrency by Tool (Tag) Denials by Tool (Tag) Denials by User Zero usage by Tool (Tag) Averages report Combined Feature report Multiple Feature report Zero usage report (all Tools) Comprehensive Zero-usage Report Comprehensive Checkout Details Denials Overview (all Tools) Users Overview User Details (by User ID) Group Details (by Group) User Activity Export

3 3 3 ways to create Usage Reports Let s first look at the 3 ways Usage reports can be created in LAMUM: 1) Interactive method- Any Current Status or Historical Report can be created interactively. You only need to log into LAMUM go to the Usage Tab and navigate through the various reports, picking and choosing to find the one you like. From there you can: a. If a Graph- save, copy, print, ..as a.jpg image b. If a Table- export it to Excel 2) On-demand method- Any Current Status or Historical Report can be created through its associated URL. So you can create the report (view) you like, using the :8182 portal, and then save that URL as a Favorite in your browser. Of course you will want to give the Favorite a User-friendly name. This will not work using the :8181 portal. 3) Batch Report method- any Historical usage graph or table can be automatically generated Weekly, Monthly, Quarterly, by saving the associated :8182 URL as a Batch Report. Setting up a report for auto-batch creation is relatively simple: create the report you want in the :8182 portal, using 7 days for Weekly, 30 days for Monthly, etc. From the drop down next to the Submit button, select Create Batch Report. That will take you to the Batch Report setup page. Give the report a User-friendly name, and decide how you want it delivered- to a Folder, or ed. If Folder you need to put in the path to that Folder. If you need to put in the address of the recipient. There is a complete tutorial on Batch Reports at the TeamEDA website: 6.pdf Note on Table Reports: 1. Every Table Report column can be sorted by clicking on the column Headeronce for ascending, once for descending. 2. Every Table Report can be filtered to show only desired rows. There are 2 ways to filter: a. General filter box (above Table)- type in a few characters of the desired information. Remove characters to clear filter. b. Column filter boxes- click Toggle Column Filters. That will bring up boxes underneath each column header. You will be able to type in (or select) the desired information to filter on.

4 Current Status Reports 4 Let s take a look at a few reports showing current license checkout information. How current depends on your Data Collection Interval (Usage/Admin). If it is set to 15 minutes, current is within the last 15 minutes. If it is set to 5 minutes, current is within the last 5 minutes, etc. Note on Data Collection Interval setting: One might think the more frequent the better but that is not necessarily true. There are other factors: database growth, # daemons, network traffic, application checkout times, - A database will grow 3x faster if you set a 5 minutes cron, vs. 15 minutes cron. Beyond 10GB database the reports will generate slower, so keeping the database under that as long as you can, is important. Auto-truncation for database will be available in 7.2. As a rule of thumb- 50 daemons, 500 Users, 10 minute cron interval will be about 1 GB per month. - # daemons- the lmstat usually takes about 3 seconds per daemon. If you have 20 daemons that means it takes about a minute to complete a lmstat cron run. - Network traffic might be a factor is LAMUM is doing an lmstat every 5 minutes and you have 20 or more daemons. Are there other applications or activities on the network that could slow down the cron process? - If your applications are checked out on average 15 or more minutes, a 15 minutes cron should be more than adequate. If the applications are only checked out for only a few minutes at a time, then a shorter Data Collection Interval might make sense. It is possible to pick up the shorter checkouts in the Comprehensive Checkout Report. So let s look at some Current Checkout status reports. Click on the Current Tab:

5 5 Notice from the Current Tab drop down, that you can click on Overview or any particular Tool/Tag. Click on Overview: Current Checkout Overview report This is a comprehensive overview of every Tool (feature) currently checked out, color coded by % of capacity. This report shows the Feature name, Tag name, Capacity, and # of licenses currently checked out. The Usage Percentage is simply actual/capacity. The colors and percentage can be modified by clicking Edit color thresholds. The AutoRefresh button (off/on) lets you toggle whether the table is updated every 30 seconds or not. If you want to have this page open all time, on a separate display (or large screen mounted on the wall), you will want this page refreshed constantly. Current Checkout Details by Tool (Tag) report If you want to see a list of Users who have this Tool (feature) currently checked out, click on the Feature name, then click on Current Usage Details. Here is the view of Current Usage Details for a specific Tool/feature:

6 6 This report shows the individual Users who currently have a license checked out, Tag, Feature, Licenses held, Capacity, Total checked out, Total currently, User Machine ID, time of checkout and Total Time in Use. Total Time in Use is probably the most important piece of data. Is someone deliberately holding a license? Did someone forget to check the license back in? If it is checked out no one else can use it. You can sort the Table from longest checkout to shortest checkout. Just click on the Total Time in User column header twice. Note the number of lines in the Table just above the Table on the left side. Note that you can change the number of lines per display page (10, 20, 30, ), and that you can cycle forward or backward through the pages. If you want information about a specific User, click on the User name/id. If you are linked to Active Directory (Usage/Admin/ Mail & Active Directory Setup ), you will get an AD window with the User s information:

7 7 This will allow you to know who and where the User is, their name, organization, location, phone number and address. The address is linked to your Outlook so you may click on it and it will allow you to directly create an . Current Realtime information The last important Current report is the Realtime info (Usage/Home). Next to a specific Tool Name, click on Realtime in the Info column. This brings up a page: This shows the Tag Name, port@host, status (green or red), lmgrd version (if FlexLM) and 2 options: - Listing/Expiration dates

8 - Details 8 The Listing/Expiration dates window provides a list of all features at this port@host, # of licenses, days to expiration and actual expiration date. This is the licenses key information, and may or may not agree with you contract renewal date. Note: Realtime info is only available for FlexLM, and other port@host based license managers, where feature detail and expiration data is available. Current Gas Gauges Display There is also a way to view Current Checkout status as gas gauges. This will make it even easier to monitor current checkouts!

9 9 You can view all features currently in use or you can select, from the Current Overview table the specific features you want to see as gas gauges, by checking the boxes next to the feature in the Current Overview table, then click show as gas gauge at the bottom of the Current Overview table. If you are viewing the gas gauge display using the :8181 port, auto-scaling is disabled and the gas gauge matrix is fixed. If you are viewing the gas gauge display using the :8182 port, the gauge matrix will auto-scale depending on your screen resolution and screen size. The gas gauges are set to update automatically every 5 minutes, however current checkouts are based on the most recent lmstat. Gas gauge display is practical if you keep a display, or browser Tab, open all the time. You may also consider the Command Center concept to display this on a big (65 ) display on the wall. (See the Command Center white paper at under Resources) Borrowed Licenses report It is useful to know when licenses are Borrowed and for how long. This report (table) shows all Current Checkout Detail by User by Tool, and if borrowed, how long it has been borrowed.

10 Historical Reports Overview 10 There are literally hundreds of ways to look at historical usage data: - By Tag (port@host) - By Tool/Feature - By User - By Group - By various time periods: 7 days, 30 days, 90 days, 180 days, 365 days, or any customer time period with a specified begin and end date. Tag is a User-friendly way of saying port@host. There are 7 primary Reports (columns): History, User Details, Group Details, Heatmap, Concurrency, Denials, and Zero Usage. You need to select a Tool (row) and scroll right to the desired report. It is going to be either a Graph or a Table. Then you will need to select the Feature you desire. In addition, you can combine the same feature from multiple license servers onto one report (Combined Feature Report), or you can plot multiple features from the same port@host onto the same graph (Multiple Feature Report), Average usage reports, Zero usage reports, or Denials reports, etc. Note: all reports are by Tag, Tool then Feature. Usage is always shown by Feature. Some reports are displayed as Graphs, some are displayed as Tables. As previously mentioned, Graphs are.jpg images, and Tables can be exported to Excel. Usage reports can be created from either the :8181 or :8182 portals. The biggest differences are: - :8181 requires log-in (User name/password), provides access to all asset/vendor information and the Usage reports. - :8182 does not require log-in, provides access to Usage reports, but does not allow access to Asset or Vendor information, or certain Usage Tabs (Admin, Groups, Alerts, and Parsers). Note: it is recommended that a Favorite link to :8181/lam (License Asset Manager) and :8182/lammonitor (Usage Monitor) be set in your browser. So let s begin by looking at the most commonly used historical reports, presented on the Usage/Home page: History, User Details, Group Details, Heatmap, Concurrency, and Denials, and Zero Usage by Tool Name. To create a report for a given Tool Name, simply go the desired Tool and scroll over to the desired Report, or go to the column and scroll down to the desired Tool. Click on either Graph or Table.

11 11 History/Graph report by Tag Select the Tool row you want, scroll over to the History column and click Graph. You will then be promoted to select the Feature you want to show usage for. The default is for 7-days. You can change the time period if you like and click Submit. The History/Graph is actually a Full Graph of usage + 2 pie charts. It is possible to create graphs of multiple time periods in one session, i.e. 7-day report and 30-day report at same time. The Full Graph shows actual usage during the time period. This is a very common and useful Usage report. The x-axis is time period (dates). The y-axis is # of licenses in use. The light blue (turquoise) area is the actual usage. There is a dotted orange line that reflects the number of licenses you own (capacity). Actual usage will never go above this line, but you will be able to easily see how many times you hit maximum capacity during this time period. The blue line is the Average usage, which will be more meaningful over longer time periods, where the Average line is also a Trend line. There is an option for showing just the Average line, or just the actual usage,

12 Since this is a graph it is also a.jpg image. You can place your cursor inside the graph, right mouse click and copy, save, print, the image of desired. Also in the History/Graph report are 2 pie charts: 12 The left pie chart is your Top 10 Users for this tool and time period, in terms of Duration, or total length of checkout time. If you have an apparent Power User you might to consider a node-locked license, or a cheap LAN license. To have a Power User dominating a WAN-Global licenses can be very expensive. The right pie chart is your Top 10 Users for this tool and time period, in terms of total # of checkouts. These are considered graphs so they are also.jpg images which you can copy, save,.. User Details report by Tag If you need to see usage of a specific Tool/feature by User, pick the Tool, scroll over to User Details and click Table. The default is for 7-days. You can change the time period if you like and click Submit. Only one time period is allowed.

13 13 This report shows a list of all Users of the selected Tool/Feature in the time period specified. The rows can be sorted by clicking on any column heading. Clicking on Total Usage twice will sort the list by longest User time to shortest User time. This is a useful way of determining who is or is not using the Tool/feature. Assuming you have set up LAMUM to connect to your Active Directory (Usage/Admin/Mail & Active Directory Setup), you can click on User name and see the AD information for that User. The address will hyperlink to your Outlook if you want to send an . Again, you can filter the list by using the General filter box at the top, or use the Column filters. To reset to No Filters just empty the filter box. Note the number of lines in the Table just above the Table on the left side. Note that you can change the number of lines per display page (10, 20, 30, ), and that you can cycle forward or backward through the pages. You will also notice a drop-down next to the Submit button. You have 3 options with Tables: Display, Export to Excel, or Create Batch Report. Display is the default. If you want to dump the Table in Excel, click Export to Excel, then Submit. This might be useful if you need to chargeback usage of a Tool/feature by User, or if you want to do something else with the data. If you want to have this report automatically created Weekly, or Monthly,, click Create Batch Report, then Submit. This will take you to the Batch Report setup page. You will need to create a Report Name, choose Frequency (7 day= Weekly, 30 days= Monthly,.), choose Delivery Type (Folder or ). If Folder, enter path to folder. If , enter address for receipt. Only one address is allowed. If you want a group of people to get the report, create an Alias for the group. This report is useful if you need to account for usage by Individual User.

14 14 Group Details report by Tag A Group is a select number of Users appearing under a user created Group name (Project, Site, Manager,..). If you need to see usage of a specific Tool/feature by Group, pick the Tool, scroll over to Group Details and click Table. Group creation, Group Maintenance, are discussed in other TeamEDA tutorials. This Table shows Total usage of the selected Tool/feature (NX13100N) for the specified time period by Group. In this example the report is showing usage of NX13100N by 10 different Groups. The Table shows Group name, Total usage time, Total # of checkouts,.. Again the report can be sorted or filtered like any Table can. You can also Export to Excel, which will be useful if you need to chargeback usage of a Tool/feature by Group, or Create Batch Report. This report is useful if you need to account for usage by Group (Project, Site, Manager name,.) Heatmap of Checkouts Report by Tag This is a very interesting view of checkout activity over a 7 day (Sunday-Saturday), 24- hour week, color coded to show high intensity usage areas. To create this report, go the Tool row, scroll over to Heatmap column, and click Graph. Of course you will then need to select a feature. Again, the default is 7 days but you can see it for any time period. The x-axis is time of day in hourly intervals. The y-axis is day of week, Sunday-Saturday. There are 168 cells. Checkouts are recorded in appropriate cells, and color coded based on cell totals. A smoothing algorithm make it more pleasing to look at.

15 15 Here is a graph showing the checkouts, by day and time, from 12/29/13 to 1/25/14, a onemonth report, for Solidworks. If a month long report, it is totaling all checkouts over the one-month period, by day of week and time of day. This report might be more useful if you just select 7 days, which would show you checkout activity for say last week. The Tool/feature, Tag name, time period covered, and time zone (of the LAMUM server) are displayed in the header. The legend on the right is highest total checkouts (dark red) to lowest total checkouts (dark blue, usually 0), during this time period. You can see the vast majority of checkouts are occurring Monday-Wednesday between 11am-4pm. This says nothing about your capacity, or whether you are getting Denials. This is just showing where most checkout activity is occurring. In the blue and yellow areas there is not much usage. If there were going to be Denials, they would most likely occur in the very dark red areas. Licenses should always be available in the blue and yellow areas. Again this is a graph, a.jpg image you can use it elsewhere. This report is useful to evaluate patterns of usage (checkouts) over a week s period. It shows you when licenses are most intensely used. It shows you when licenses are not used. If someone complains that they can t get a license, show them this report. Chances are they can find a day/time when licenses are available.

16 Concurrency Report by Tag 16 This report is one of the most important pieces of the puzzle. For floating (concurrent-use) licenses it s the one report that gives you a true sense of what usage is at each level of possible concurrent usage, from 1 to x, where x is the number of seats (licenses) you own. Concurrent usage is an important factor when trying to determine the number of licenses you need. There are 2 Concurrency reports: a 24x7 Concurrent usage report and a Monday-Friday 8am-5pm Concurrent usage report. You pay for the Licenses to be used 24x7, but that is seldom the case. It is important to note that the time period selected is local time, where the LAMUM server is located. Let s look at the 24x7 report first: The header shows the Tool/feature, Tag, time period, and total # of licenses available. The 24x7 Concurrency report shows % of time at each level of possible concurrent use level. In this example we own 15 licenses (seats), the X-axis. The vertical bars are purple in the 24x7 graph. Note that Zero use values are not shown. In this example there is concurrent usage at every level.

17 17 The Y-axis is % of time at each level of possible concurrency. The % values add up to 100%. Why is this important? You pay for your licenses on a 24x7 use basis. This report shows you what percentage of time you are actually using what you are paying for! Looking at this you might say we only need 3 or 4 licenses. No true. In this example, 24x7 time period, 1 license only was used 34.6% of the time. 2 licenses concurrently used was 50.4% of the time. 85% of time 2 or less licenses were used, etc. This graph is useful if you have Users all over the world. Let s look at the same information but only M-F, 8-5: Notice that the picture changes. The green vertical bars indicate it is M-F, 8-5. Looking at it this way implies you need at least 15 licenses, maybe more. There is a 14.5% probability of a denial in this time period. 5% probability is a good level to have, not too many not

18 too few. Notice also that the header says Workweek: Mon Fri, If all your Users are local, and your licenses are LAN, the M-F, 8-5 should be more than adequate. Again, these are all graphs, so also a.jpg image. Denial Report by Tag One of the most overstated reports is the Denial report. Most companies are concerned that if there are Denials, then Engineers are unproductive, and they need to go buy more licenses. In truth, some level of Denials is OK. If you never have Denials, maybe you have too many licenses. If you have too many Denials, then maybe you do need more licenses. Probably a few Denials are OK. More importantly the Concurrency reports will tell you the % of time you are at maximum or near max. capacity. It is probably more useful to decide what is an acceptable level of maximum capacity concurrency- 10%? 5%? 2%? We recommend a level of 5% is acceptable First let s explain what a Denial is, what causes Denials, and how Denials should be interpreted. A Denial occurs in FlexLM when a User attempts to obtain a license to use for an application but all available licenses are already checked out, or, for some other reason, a license is not accessible. Like books in a library, you buy 10 books (licenses) and put them in the library. FlexLM daemon allows books (licenses) to be checked out up the limit of what you bought (capacity). In FlexLM, a denial is recorded in the Flex Debug Log with an error code, if the Engineer is unable to secure a license, for whatever reason. There may be several reasons why the denial occurred- User not authorized, Authorized server not available, Licensed number of Users already reached, We are really only interested in the last one- no licenses (seats) available. The number of Denials could be modest, occasional, or extreme. We are looking for modest and occasional Denials. Extreme Denials are usually due to a creative Engineer who writes a script to check for license availability, and if none is available, keep checking every 5-10 seconds, etc. This could record hundreds if not thousands of denials. These are considered false Denials. It is also possible to have the same tool on 2 or 3 (or several) license servers around the world. An engineer might go to the first server and try to get a license. If none available, it records a Denial. The engineer goes to a 2 nd server, none available, records a Denial, 3 rd server, until he gets a license. 2+ false Denials have been recorded. Denials do tell part of the story. If you are seeing a lot of legitimate Denials, you truly may need more licenses. LAMUM does show the Denial error code (with explanation) so you can eliminate false Denials. Moreover, LAMUM will consolidate Denials by User by hour, so the clever engineer won t impact the analysis, by creating hundreds, if not thousands of spurias Denials.

19 To look at Denials for a specific Tool/feature, go to the Denials column and down to the desired Tool/feature, click Table. 19 The default Table is for 365 days, showing # of Denials by month. You can then drill down into a specific month, then drill down into a specific week, and finally drill down into a specific day. The Denial report by day will give you the most data: name of the User that was denied (and yes the same User could be shown several times!), date, time, feature, Tool, Tag, Client (machine ID), error code, and error code description. You can sort, filter, or export the Table as needed. If you only want to see error code related to Licensed number of users already reached just filter on that error code. Note the number of lines in the Table just above the Table on the left side. Note that you can change the number of lines per display page (10, 20, 30, ), and that you can cycle forward or backward through the pages.

20 20 Again, if you see the same User ID appearing a lot, you can always find out who they are by clicking on their User ID, which will bring up the AD information. This Table can also be exported to Excel. Zero Usage Reports by Tag This report by Tool (in 7.1) is useful to see features in a specific Tool that have NOT been used in a given time frame. Again, go the Zero Usage column, scroll down to the desired Tool name and click Table. (See the Zero Usage reports below for more information.) The Zero Usage report does take a while to generate. Please be patient!

21 History Tab Reports 21 There are a few additional reports available from the History Tab: Averages, Combined Features, Multiple Features, Zero usage, and Comprehensive Checkouts. Averages Report

22 22 Knowing Total Use for every feature used in a given time period, Average Usage time per checkout, and Average number of Users for any given time period is really important. The above is the Averages Report Table, with default of 7 days. It lists every feature used in the specified time period by Feature name, Tag name, Capacity (how many licenses you own), Total usage for this time period, Average usage time per checkout, Average number of Users, and number of times at Max capacity, and Average use color-coded by % of capacity, based on a 24x7 week, or M-F 8-5. Accordingly, it could be a long report! Note the number of lines in the Table just above the Table on the left side. Note that you can change the number of lines per display page (10, 20, 30, ), and that you can cycle forward or backward through the pages. Note also that you can sort on any column heading, or filter as in any Table to reduce the data to what you need. Note that you can Export to Excel or Create Batch Report. This report is useful to see Average use, rather than Maximum use. Perhaps you should plan according to average use rather than worst-case max use. Trends and forecasts might me more realistic based on Averages, i.e. do you see Average use increasing or decreasing over time? Note: Averages report can be created for 24x7 or M-F 8-5 time periods. Combined Feature Report This report is useful only if you have the same Tool name running on multiple license servers. For example, if you have Matlab running on a license server in Boston, and on a license server in Pune (India), and in Tokyo (Japan), then this report will allow you to plot all 3 instances of Matlab usage on the same graph, each in a different color, plus see the combined total of all 3 plotted in black. This report is useful if you want to see all Matlab usage together on the same graph. It may help you decide if you need to move licenses from one server to another server, or whether you can reduce total Matlab licenses.

23 23 Again, you can do this for any time frame, and it is also a.jpg image. The colors in the graph can be changed. Multiple Feature Report This report allows you to plot multiple features (up to 6) for a specific Tool/Tag, on the same graph. It is useful if you need to see related feature use for a given Tool/Tag. It would not be useful if the features are unrelated. Again, this is multiple features, at same port@host (Tag). To create such a report simply click History/Multiple Features. LAMUM will bring up a list of all your Tools (Tag) available. Pick the one you want. A table will appear with all the features at that Tool/Tag. Check the boxes of the features you want to see plotted together, pick a time period, click Submit. Again, only up to 6 features. Too much data/lines will just make the graph unreadable. Note: in 7.1 you will be able to change the colors for the lines.

24 24 It s a graph, also a.jpg image. The colors in the graph can be changed. Comprehensive Zero Usage Report Knowing what Tool/Features are being used is one thing, but knowing what Features are not being used is equally as important. Why pay for features not being used? Do engineers need training on using those features? This report will list all features from every Tool (Tag) that have had no use in the specified time period. The Comprehensive Zero usage Report shows Zero usage across all Tags. This can be a long report so it is best created as a Batch report.

25 25 Since it s a Table, it can be exported to Excel, Create Batch Report,. Note the number of lines in the Table just above the Table on the left side. Note that you can change the number of lines per display page (10, 20, 30, ), and that you can cycle forward or backward through the pages. Of course you can sort or filter as needed. Remember- you can create Zero Usage by specific Tag on the Usage/Home page, or Zero Usage for all features, all Tags with this Usage/History/Comprehensive Zero Usage Report. As a table, you can sort on column header, or filter using the general filter box or the Column specific filter boxes. And of courst the entire table can be exported to Excel. Comprehensive Checkout Details Report For FlexLM licenses, all the above Usage Reports are based on data collected according to the lmstat Cron interval you set- typically 10 or 15 minutes. It is possible with certain applications that a checkout and checkin could occur in between lmstats, and could be missed. We call these short checkouts. Some companies really don t care about those short checkouts. Some companies want to see all checkouts, even if a checkout/checkin occur in under 1 minute. This report allows you to generate a report on all checkouts, regardless of checkout/checkin time. However, in FlexLM the only place where these short checkouts are recorded is in the Flex Debug Log. Therefore, the Comprehensive Checkout Detail report is dependent on a special Flex Debug Log parser, under Usage/Parsers/ FLEX Comprehensive Checkout Parser Setup. This parser collects the data periodically (Daily, every 2 days,.) usually in the middle of the night. Once the parser is set up properly, and you have a green light on Parse Now command, you will have data to create this report. This report may take a long time to generate, so it might be better as a Batch Report.

26 26 To create a Comprehensive Checkout Details Report, go to Usage/History/Comprehensive Checkout Details, pick the Tool(Tag)/port@host you want, a time period, and click Submit. The report is a Table, showing User name, Machine name, Feature name, Date, Total # of checkouts, Total # seconds checked out. Again, it s a Table which can be sorted, filtered, exported to Excel, or you can Create a Batch Report. Denials Tab Reports Denials Overview This Table report, under the Usage/Denials Tab, will provide an overview of all Denials for every Tool/Tag available, for any specified time period. Default is 365 days.

27 27 The report shows # Denials, Feature name, Tool name, Tag name. Details allows you to drill down to see more detailed Denials information for a given Tool/Tag. As a Table you can sort, filter, export to Excel, or Create Batch Report. Denials by User Report If you wish to see Denials by User, simply select the User name from the drop down and pick a time period. The following table report will show you Denials for that User in that time period.

28 Denials Heatmap Report 28 Similar to the Checkout Heatmap, the Denials Heatmap is a graph showing the day and time of denials for a specific Tool and time period, on a 24x7 basis. Users Tab Reports Users Overview Report This report shows the number of unique User ID s in a specified time period. The actual number of unique engineers that day is on top of the orange columns. Note the high water mark for that period.

29 29 The LAMUM license key is tied to this information. LAMUM pricing is based on a maximum level of Unique Daily Users. You want to be sure your high water mark stays below your authorized User level. You can see what that is by going to Usage/Admin/About License. If you exceed your license Daily User limit, LAMUM give you a License Viloation message, and will not allow you access to the reports until either midnight (where it resets to 0 ), or you get a new licenes key from TeamEDA with a higher limit. This report is also useful in that it helps you see the number of engineers using your engineering tools, on a daily basis. Over longer periods you ll see if the engineering team is growing or shrinking. It s a graph, so also a.jpg image. User Details Report This Table report shows all Tool/Feature usage for a specified User. It is useful if you need to chargeback or account for a User, and you need see what tools he/she used for how long, etc. It can also be used by the User s Manager to determine if the Engineer is using the right tools, frequency of use, etc. It could be part of a Performance review. To create the report, go to Usage/Users/ User Details, pick the User name/id from the drop down list, pick a time period, and click Submit.

30 30 The report shows the User ID, Feature name, Tag name, Checkout date/time, Total usage. As a Table it can be sorted, filtered, exported to Excel, or Create Batch Report. Note the number of lines in the Table just above the Table on the left side. Note that you can change the number of lines per display page (10, 20, 30, ), and that you can cycle forward or backward through the pages. Note: this report shows all usage for a specified User Name/ID. The User Details report on the Usage/Home page shows all Users for a specified Tool/Tag. Groups Tab Reports Group Details Report This report is similar to the User Details Report except it provides details on usage by Group. A Group is a preselected number of Users. It may be a Project Team, a Manager name, a Site, a Lab, etc. Groups are created under the Groups Tab/Group Maintenance. It s simple: create a Group Name, select Edit and add User ID s that belong to that Group. Click Update. You can also define Groups off-line in an Excel spreadsheet, using the template provided in the Usage/Groups/Group Batch Import & Export, to the right under HERE. There is a separaate Tutorial/App Note for Setting up and maintaining Groups on the To create a Group Details report, go to Usage/Groups/Group Details. Pick a Group from the drop down, select a time period, click Submit. It will most likely be a large Table. Note the number of lines in the Table just above the Table on the left side. Note that you can

31 31 change the number of lines per display page (10, 20, 30, ), and that you can cycle forward or backward through the pages. Of course you can sort or filter as needed. Again, this is useful if you need to see usage by Group (Project, Manager, Site, etc) for chargeback or other accounting purposes. It s a Table so you can sort, filter, export to Excel, or Create Batch Report. Note: this report shows all usage for a specified Group. The Group Details report on the Usage/Home page shows all Groups using a specified Tool/Tag. Users Activity Export Report The final report we will cover is the Users Actvity Export report, which is a comprehensive dump of all User activity for a specified Tool and time period. It is only available as a Excel spreadsheet. The resulting Excel spreadsheet could be very large, but once in Excel you can sort, filter, extract whatever information you like. To create the report go to Usage/Batch/Users Activity Export. Select a Tool and time period, and then click Export to Excel. You ll have to do this for every Tool you want. There is no way to select multiple Tools.

32 32 The resulting Excel spreadsheet will show: Feature, Product, Tag, Date, Time, Usage Seconds, User, Port, Machine Name, Host This concludes the Usage Reports Tutorial for LAMUM (October 2016). As more reports are made added, an updated version of this Tutorial will be made available. Contact TeamEDA for questions: