Featured

LAMUM vs. In-House Scripts & Tools

For most engineering companies worldwide, the cost of engineering software licenses is the second largest overhead expense they face. Despite the considerable investment spent on these licenses, their management and monitoring is usually done via in-house scripts or tools.

Managing engineering software licenses in-house can cost companies tremendous resources, as well as staff hours and infrastructure that could be allocated to the company’s core functionality. Apart from the opportunity – and financial – cost, these in-house tools often struggle to provide accurate and actionable data that helps companies maximize the efficiency of their licenses. In-house scripts also need to be regularly updated and debugged to ensure their functionality, costing even more staff hours.

You can learn more about LAMUM’s best-in-class functionality, and how it helps the world’s largest engineering firms save 15-25% on their engineering software license costs by contacting our sales team and requesting a demo today!

8 Best Practices for Successful Software License Management

Engineering organizations put different spins on what’s important for managing their software and license usage.  They claim current methods are adequate, yet they fall short and are inefficient. License Asset Manager with Usage Monitoring (LAMUM) focuses on best practices for engineering software license management and monitoring for efficiency.

Centralized Repository for Asset Information

Often overlooked is consolidating asset information. LAMUM features provides this best practice and combined with license usage monitoring and managing for efficiency is the ideal solution to deploy more best practices! Understanding current usage with visibility of historical trends is essential, and best to have asset information ready to reference for renewals, compliance, and audit-readiness.  Information like contacts, POs, invoices, SLAs, and cost can be maintained multiple ways.  That’s the problem!  Many disparate methods like spreadsheets, documents, and hardcopies maintaining this information is impractical.  It’s not easily accessible by all and difficult to find auditable items.

Knowing What You Pay For

is essential and many have a good idea of what they own for software including seats, cost, usage restrictions, and expirations. Count on the all-in-1 solution that has all asset information and attachments combined with the license file data ingested by LAMUM to facilitate reconciliation of what you pay for.

Proactively Prepare for Renewals

Don’t wait for your vendor to contact you.  Get started 45-60 days in advance by refencing LAMUM expiration reports and email alerts.  There’s ample license information and usage trends to properly prepare and determine what you need.  Be proactive and prepared for contract and license renewals!

Prepare for the Budget Cycle

Just as valuable as renewal information is historical usage to analyze trends, peaks, and ultimately determine what you may need for the next budget cycle.  Knowing what you pay for, knowing what you’re using, and knowing what you need for renewals and budgets is critical.  Viewing logs and in-house scripts are no match for data-driven analytics for historical perspective on new product introduction license needs.

Current Checkouts and License Harvesting

Customers say that the usage stat command or GUI is adequate.  Yes, but can they display a single pane of all active tools with details that include checkout duration to sort by long checkouts, ability to send warnings and alerts for long checkouts that may be idle, a hyperlinked username to display LDAP information, and even harvest the license from that long checkout?  Deploy a best practice solution and not the less than adequate method.

Comprehensive Usage Reporting

Viewing a log is not efficient and reporting shouldn’t be an extra option and cost for the engineering software license management solution.  Software license management best practices require features that provide current and historical reports with selectable criteria that can be saved for on-demand or batch reporting to be used in an instant or generated for future software license usage review.  A web-based user interface replaces client installations with URLs to be repurposed as hyperlinks

Alerts and Notifications for License Management

– Reports provide perspective to make decisions for license capacity.  As much as you’d like to be prepared for the unexpected through data analysis, you need reactive and proactive notification.  Alerts help isolate capacity issues to quell user frustration.  Proactive notification of capacity and denials thresholds help to identify license abuse.  Expiration alerts provide ample notice to secure license renewals in time.  Daemon-down alerts enable fast response before impacting productivity on a larger scale.

Cost Savings and ROI with Efficient License Management

Our mantra is “know what you pay for, know what you’re using, know what you need.”  The focus for many is on simply having more than enough licenses to avoid denials and impact on productivity and revenue vs managing for efficiency and cost savings. License administrators view current usage to determine how many licenses are used vs capacity and overlook licenses not used. It’s not surprising to see a huge gap between them.  What a great opportunity for cost savings when I see license capacity of 150 when trends show the most licenses used is 46.  Do the math on cost per license and potential savings to appreciate the ROI for a solution like LAMUM. 

Request a demo today for LAMUM, the TeamEDA engineering software license management system!

FAQs

We’re using many ways to capture our engineering software asset information, but mostly using Microsoft Excel spreadsheets.  Can the information in the spreadsheets be transferred into LAMUM?

License asset information can be entered manually for each specific line item: Vendor, Tool, PO, Server, Daemon, and License which ties each line item together. To transfer data for many assets, CSV templates in the proper format for import are downloadable from LAMUM to populate with the required and optional information to be imported into LAMUM.  Existing Microsoft spreadsheets could be cross-referenced or reformatted in the proper format.  Many assets to be configured for usage monitoring can be imported, too.

What’s the value of LAMUM when our vendors provide a GUI at no extra cost that shows current licenses checked out already?

LAMUM provides much more than current license usage and in much more detail than the vendors.  Consider a single pane to view all current license usage at once and understanding licenses in use vs capacity, as well as the severity or threat of exceeding capacity. Add alerts to that to be proactive in policing long checkout abuse and replenishing the pool of licenses.

How do you correlate compliance and audit-readiness between asset information and license usage?

The license asset information and up to eighteen (18) documents provide necessary compliance and audit-readiness information to reference with your vendor.  Through Active Directory (LDAP) synchronization, LAMUM can capture pertinent information for the usernames checking out licenses relative to location to reference to ensure that engineering groups are adhering to license restrictions.

Can you explain cost savings opportunities and ROI with LAMUM?

With LAMUM cost savings is much more than just reducing the number of licenses needed to save money.  We look at reducing license counts, preventing further spend through efficient usage, consolidating methods to maintain license information and usage, and reducing labor costs for to manage the engineering software license usage and monitoring for efficiency. You’ll save on all fronts and easily absorb the cost of LAMUM within the available software spend cap.

When we run out of licenses for our FlexLM software, we just do lmremove to check licenses back in.  Why is LAMUM better for license harvesting?

LAMUM doesn’t just focus on current usage statistics.  It calculates duration of use for licenses currently checked out to identify long checkouts and potentially long checkout abuse.  For FlexLM, we can REMOVE a license to check it back in, but our best practice is to assess long durations, use long checkout warnings and alerts to change behavior, and using the username’s Active Directory information to identify the email or phone number to attempt to contact the user to check the license back in if idle for another user to use.

Combating License Abuse

Software License Management’s Role Enabling Business Growth

How a management change at your Software Vendor impacts you

The LAMUM NX1.0 Experience

TeamEDA Releases LAMUM NX1.0

Zero-Usage Reports

The biggest challenge for CAD/IT administrators is discovering licenses that are under-utilized or have zero-usage over several months. Running a report that shows a number of licenses that have not been used in the last 365 days, is a clear indication that you may want to negotiate a trade-in or even to stop paying maintenance!

It is certainly important to talk about what is being used, how much, by whom, etc. But it is equally important to look at what is not being used. The Zero Usage report does just that. It shows all features/tools that were not used in a specified period of time.

Managers need to know what is not being used as well as what is.

Managers need to consider the best ways to make decisions about:

  • Cost allocations and overall Engineering expenditure
  • Intelligent use of engineering resources
  • Spending restrictions
  • Resource distribution

Learn more about reports.

Discovering under-utilized or zero-use licenses

Batch Reports for Engineering Licenses

Would you like to receive regular reports (every week, once a month, once a quarter, etc.)? LAMUM will automatically create these for you in the middle of the night, and either send to you via email or deliver to a specific folder.

Setting up a Batch report in LAMUM is very easy:
  • Create the report you want and select the time period you would like to analyze (7 days for Weekly, 30 days for Monthly, etc.).
  • Click Create Batch Report, give the Report a User-friendly name.
  • Choose how you want it delivered: email or specified folder. That’s it!

There is no limit on how many Batch Reports you can set up.

Batch Reports can be:
  • Single reports (graphs or tables)
  • Multiple graphs for single tool
  • Selected Features Usage Graphs by Tag
  • Selected Features Usage Tables by Tag
    • Includes all User Details

(Tag is user-friendly name for port@host)

Feature Usage by Tag – Table/Graph

(A “set” of Graphs or Tables for selected Tools)

Allows you to Create Batch Reports for “ALL” or “Specific features” usage details for a given Tag and Time period.

  • A “set” of graphs for selected tools at a given tag
  • A “set” of tables for selected tools at a given tag
  • Created weekly, monthly, or quarterly, e-mailed or dropped in a folder

(Tag is a user-friendly name for port@host)

Multi-graph View Select

(A “set” of up to 8 Graphs, for same Tool)

The Multi-graph view is a batch report that provides a complete and comprehensive set of usage graphs for each daemon.

It may include a combination of up to 8 graphs, such as:

  • Heatmap (Checkouts)
  • Heatmap (Denials)
  • Top 10 Users (by count or time of checkout)
  • History graph
  • Concurrent use graph (24×7)
  • Concurrent use graph (M-F 8-5)
  • Group Usage
  • Unique Users Graph

These can be individual or combined and scheduled weekly, monthly or however preferred. This routine report is available as a downloadable .pdf that can be easily shared with the team or management.

Mergers, Acquisitions & Staffing Changes: Are You Ready?

Right now is a critical time for many companies to make crucial decisions about acquisitions, mergers and changes in staffing. As organizations are thinking about ways to move forward, it is becoming increasingly important to consider what engineering licenses are needed.

  • How many CAD, EDA, PLM or any other engineering licenses do you currently have?
  • What are the future needs and expectations?
  • How will mergers and acquisitions affect your engineering team?
  • How do you manage the different engineering licenses across the various groups?
  • Did your company need to furlough engineering employees or are you currently in the exciting stage of needing to hire more talent?

With the recent increase of both acquisitions and mergers, it can be a two-fold challenge at times. Corporate companies want to make sure that the companies they are investing have a system to manage all of their engineering licenses for greater visibility and transparency. The smaller companies are trying to learn how to show compliance, learn corporate structures and best ways to enter a new way of working.

In some larger companies, training departments are in charge of ensuring new colleagues are aware of the tools that the teams are using as well as ensuring that the employees are aware of the product suite available to them. They also oversee that these tools are used in compliance. Check out our overview of how LAMUM can be useful across the different job functions.

Ultimately, the training departments need to have a good idea of utilization, especially during the current ongoing pandemic. Managers could really see big savings here.

Helpful Articles