How a Mid-Sized Manufacturer Went From "We Think We're Compliant" to "We Know"

This is the story of a company that believed it was fine. It wasn't in serious trouble. It just didn't actually know. That gap, between thinking and knowing, is where most compliance problems live.

The company is a composite, built from patterns that come up again and again in engineering-heavy businesses. We'll call it Halden Components. About 350 employees, two factories, one design center. They make precision parts for the automotive and aerospace industries.

The comfortable assumption

Halden's engineering team used a familiar mix of software. CAD for design, simulation for testing, CAM for manufacturing, PLM for managing it all. Licenses came from several vendors, each with its own license manager.

If you'd asked the IT director, Marcus, whether they were compliant, he'd have said yes. They bought licenses through resellers. The resellers knew their business. Renewals happened on time. Nobody had complained.

Then a peer at another company mentioned an audit that cost them a painful sum. Marcus went home that evening and couldn't shake the question: "Would we actually pass?"

Step one: what do we own?

Marcus started where OpenLM's software license compliance best practices suggest starting: understanding the terms and keeping proper records.

It took longer than he expected. Contracts were spread across procurement folders, old emails, and a reseller portal or two. Some licenses had been bought years ago by people who'd since left. One agreement existed only as a scanned PDF with a coffee ring on page three.

After two weeks, his team had a single list. Every product, quantity, license type, renewal date, and key terms like territory and device rules.

That list alone was worth the effort. It turned up a subscription they were still paying for but nobody used, and a module that had quietly lapsed while engineers kept using it.

Step two: what's installed and running?

Next, they needed to know what was actually out there. Installed software was one part. The license servers themselves were another.

They counted five license servers they knew about. A walk-through of the factory network found a sixth. It sat in a corner of the second factory, set up years ago for a CAM package, and was still serving licenses from an old license file.

Nobody had touched it in years. It had simply kept running.

Step three: what's actually used?

This was the hard part. Each license manager kept its own logs in its own format. Pulling them together by hand would have taken months.

Halden brought in OpenLM, a license management platform focused on engineering software. OpenLM says it supports over 90 license managers, which covered every vendor Halden used. Usage from all six license servers started flowing into one view.

Marcus resisted the urge to act immediately. He let it run for two months to see normal patterns, busy periods, and anything unusual.

What they found

Two months of data told a clear story. Some of it was reassuring. Some of it wasn't.

Reassuring: For most floating licenses, peak concurrent usage stayed comfortably within what Halden owned. The big CAD contract was fine.

Not reassuring: The forgotten CAM license server was serving more seats than Halden's current agreement covered. That was a genuine compliance gap.

Not reassuring: A simulation tool licensed as node-locked had been installed and used on more machines than the agreement allowed. Engineers had copied it across during a busy project.

Mixed: Three contractors who had left months earlier still had working access. They hadn't used it, but they could have.

Costly: Idle sessions inflated peaks on two expensive products. Licenses sat open for hours with no activity.

What they changed

Marcus grouped fixes into two buckets: compliance and cost.

On compliance, they:

1. Shut down the old CAM license server and moved users to the current one.
2. Removed the extra simulation installs and spoke to the vendor about adding the seats they genuinely needed.
3. Removed contractor access and added license steps to the offboarding checklist.

On cost, they:

1. Introduced idle license harvesting on the two expensive products.
2. Dropped the unused subscription at renewal.
3. Right-sized two floating pools based on real peak usage.

They also followed another of OpenLM's recommended practices: training. A short session with engineering leads explained why copying installs or keeping old license servers creates risk. Nobody was blamed. Most engineers simply hadn't known.

The results

Within a quarter, Halden had a clear compliance position it could actually prove. If an audit letter arrived, they could show entitlements, installs, and usage for every major vendor.

The cost side surprised management. The savings from the unused subscription, right-sized pools, and reduced idle time more than covered the cost of the monitoring tool.

Marcus summed it up in a board update: "We weren't doing anything wrong on purpose. We just couldn't see. Now we can."

What made the difference

Looking back, a few things stood out:

• Records first. The entitlement list made everything else possible.
• Look for hidden servers. The biggest risk was something nobody knew existed.
• Watch before acting. Two months of data prevented knee-jerk decisions.
• Fix compliance and cost together. The same data served both.
• Keep it going. Halden now reviews compliance quarterly. It takes a few hours.

If this sounds familiar

You don't need a crisis to start. Begin with the list of what you own, then find out what's installed and used. OpenLM's article on 9 best practices for software license compliance is a good checklist to work through.

The goal isn't perfection on day one. It's moving from "we think" to "we know."

\