半導体・EDA

Engineering software asset management for feature-based EDA licensing in semiconductor environments

利用状況の評価を依頼する

Metering happens at the feature level, not the seat level, so a tool that pulls a dozen features on launch is counted the way it actually behaves. Where an estate spans interactive workstations, regional design centers and batch jobs on the compute farm, each is metered where it runs and the results reconcile into one view.

Feature-based and token-based licensing is the normal operating condition in semiconductor rather than the exception, alongside cryptic vendor feature names, reserved seats that never return to the pool, borrowed licenses that linger after the work stops, and peak demand that a monthly average hides. Those are the conditions that make an EDA estate the least accurately measured line in the software budget, and the reason seat-count reporting doesn’t survive contact with it.

01

One launch is a dozen feature checkouts

An EDA session does not take out a license. The tool starts, pulls a set of features off the server, and pulls more as the engineer opens each option. What the engineer calls one seat arrives in your reporting as a stack of separate checkouts under names nobody outside the vendor can read.

Level 1 captures that record as the license manager writes it. Feature Mapping folds the raw feature names belonging to one product into a single logical line, and Feature Labeling renames the cryptic strings into something a department head can read. Without both, a feature-level report is technically accurate and practically useless.

02

Tokens don’t divide into seats

Many EDA and simulation products draw on a shared token pool where each feature costs a different number of tokens. A concurrent seat count tells you nothing about a pool like that. Level 1 tracks token consumption per feature, which is the only unit the pool is actually spent in.
Reserved and lingering licenses distort the same picture from the other direction. A reserved seat is allocated to a named user or machine and does not return to the pool without administrator intervention, so it reads as in use whether or not anyone is at the desk. A lingering seat stays checked out for a period after the engineer stops. Both are captured as their own data types rather than folded into a utilization percentage that quietly overstates demand.
Denial Reports close the loop: who was refused which feature, and when. That is the number that settles whether a pool is short of capacity or badly distributed, and it is the number engineering managers argue about without.

03

Three design centers, three peaks, one pool

A pool shared across time zones looks healthy on a monthly average and saturates at 10am local in each of them. The monthly number is the one that reaches the budget meeting. The 10am number is the one that stops an engineer working.

Where a network path exists, Open iT sends collected data from each local environment to a centralized server, which gives one consolidated view across sites without asking any site to change how it runs. Deployment is on-premises, cloud or hybrid, including Azure SQL Server and Azure Analysis Services, so the platform follows whatever your IT strategy already is.

Line chart of monthly license use from January to December. Actual peak use stays between about 88 and 120, topping out in October, while available licenses sit near 155 and the forecast near 152, leaving a gap of roughly 30 or more idle licenses at the peak.

04

The gap between what you own and what anyone used

IT owns the asset. The engineering disciplines own the demand. Nobody owns the evidence, and what arrives on the SAM manager’s desk is usually a guesswork. 
At Chiyoda Philippines once metering was in place, one month of one application produced three numbers that had never been in the same room. 155 seats available. 152 forecast by the disciplines. 120 in use at the busiest moment. The disciplines were not wildly wrong. They were confidently wrong by 32 seats, and confidently wrong is the expensive kind.

Aviogroup, an aerospace propulsion manufacturer running 13 license servers across sites in Italy, Poland, the Netherlands and French Guiana, measured one pool for a full year and found 64 seats available against a peak of 46. Two industries, two continents, years apart, and close to a quarter of each pool sitting idle at the busiest moment on record.

ソフトウェア でサポートされているエンジニアリング関連のロゴ一覧:Ansys、Nastran、LS-DYNA、Abaqus、SolidWorks、Simulia、Altair、MATLAB、およびGreen Hillsソフトウェア 。

05

6,000+ applications. 90 license managers.

LicenseAnalyzer™ meters more than 6,000 engineering and specialty applications across 88 natively supported license managers. For a semiconductor estate that includes Altium in four deployment forms, Green Hills Software, TASKING TLM, Parasoft, SlickEdit and SciTools across the embedded and verification toolchain, MATLAB and MathLM for modelling, Altair and ANSYS for signal integrity and thermal work, Moldex3D for package moulding, and OpenText Exceed TurboX where engineers reach the Linux farm remotely. CodeMeter, Sentinel HASP and Sentinel RMS cover the dongle-protected specialty tools every design house keeps a handful of.

Coverage follows the license manager rather than the vendor logo. Anything served by FlexNet, RLM, LM-X or DSLS is metered the same way, which is what most front-end EDA sits on whichever name is on the invoice.

アプリケーションの対応一覧と計測の詳細についてはこちらをご覧ください

06

Cost traced to the project that spent it

LicensePlanner™ maps usage against financial, contract and organizational data. Cost Centers group consumption by department, project, location or business unit. Chargeback and showback allocate cost to whoever consumed it, in a form a project manager or an auditor can follow, and project-based allocation handles the case where a tape-out draws on capacity funded by three different budgets.

License Cost Simulation runs the scenario before you commit: reduce seats by twenty percent, move to a token model, consolidate two agreements. LicensePredictor™ projects usage eighteen months out. Both exist so the renewal conversation starts from a modelled position rather than last year’s number plus a margin.

07

買収が行われるたびに、すでに支払っているライセンス料を二重に支払うことになる

Consolidation is how this industry grows, and every acquisition arrives with duplicate agreements, overlapping entitlements and another set of license servers nobody has mapped.

Open iT brings the acquired license servers into the same console as yours. SSAD, Open iT’s cloud-hosted normalized software catalog, matches and standardizes publisher and title data so the same product bought twice under two different names stops looking like two products. LicensePlanner holds the vendor and contract detail for both estates and consolidates estimated, budgeted and actual spend, which is how the overlap becomes visible before you renew both agreements.

The usual outcome is that the acquired teams run on reclaimed capacity instead of new purchases.

08

すでに稼働しているスタックに組み込むことができます

Open iT feeds your existing stack rather than replacing it.

For ServiceNow, the Open iT LicenseAnalyzer Store App and the on-premises ServiceNow Adapter surface engineering usage data inside ServiceNow alongside its own entitlement records, producing an Engineering License Overview dashboard and flagging over-licensed and underutilized software. SSAD normalization is what makes that matching accurate rather than approximate.

Reporting runs through a native Power BI connector and report templates, including dashboards for named user usage, token usage and seat reassignment recommendations. Azure SQL and Azure Analysis Services are supported where a cloud Analysis Server suits your estate.

08

Audit-ready whenever you need it

Level 1 keeps a usage audit trail for compliance and historical review, with configurable retention and access logs that include source IP. Denial Reports capture who was denied, why and when. CLIMS records every license-management event as a timestamped, process-level audit trail.

Data Anonymization transforms user, host and application names while keeping the usage data reliable, which is what makes an extract reviewable by finance, by a vendor, or by anyone else with no business seeing which engineer ran which job. Single sign-on runs through Microsoft Entra ID with SAML 2.0, or Okta. Role-based access separates administrators holding full management rights from reporting users with read-only access, so a console login cannot change a configuration by accident.

09

Audit-ready whenever you need it

Level 1 keeps a usage audit trail for compliance and historical review, with configurable retention and access logs that include source IP. Denial Reports capture who was denied, why and when. CLIMS records every license-management event as a timestamped, process-level audit trail.

Data Anonymization transforms user, host and application names while keeping the usage data reliable, which is what makes an extract reviewable by finance, by a vendor, or by anyone else with no business seeing which engineer ran which job. Single sign-on runs through Microsoft Entra ID with SAML 2.0, or Okta. Role-based access separates administrators holding full management rights from reporting users with read-only access, so a console login cannot change a configuration by accident.

09

Start with the pool, not the vendor

Bring us the constraint rather than the requirement. Which license managers you run, which pools are token-based, where the design centers are, and which applications matter enough that an engineer waiting on one costs you schedule. The architecture gets built around those answers.

Start with a Level 1 usage assessment. It meters one renewal cycle across your license servers and shows the gap between the capacity you own and the capacity anyone worked in. The first useful output is not a saving. It is one table, three columns, for one application, for one month: bought, forecast, actually used.

Book a 30-minute call. We’ll ask which license managers you run and when your next renewal lands. Nothing to install, nothing to prepare.

Metering engineering software since 1999 · 6,000+ applications · 90+ license managers natively supported

Request a Usage Assessment

09

よくある質問

Can Open iT measure Cadence, Synopsys or Siemens EDA tools?

Coverage follows the license manager, not the vendor. If the tool is served by FlexNet, RLM, LM-X or DSLS, Open iT meters it, including denial data. Tell us which managers you run and we'll confirm against your estate.

What is the difference between a license being checked out and a license being used?

A checkout is recorded when the application starts and released when it closes. Everything in between counts as consumption, including the hours a tool sat open behind a browser. True Active Usage separates the two by measuring activity inside the application.

Will engineers see this as surveillance?

Idle detection is threshold-based and non-punitive, and suspend preserves the session rather than closing it. The license returns to the pool. The work stays on the screen.

Does this replace our IT asset management platform?

No. Open iT measures the engineering license estate. Entitlements, purchase orders and allocation workflows stay in your SAM platform, and the two join through the ServiceNow integration.

実装にはどのくらい時間がかかりますか?

Plan for an evaluation and a rollout rather than an install. Timelines move with the size of the estate and the number of license manager types in play.

さらに詳しく探る

ワークフロー分野別に探す

地下

Petrel、tNavigator、RMS、DUG Insight、Zetaware — 地下探査ソリューションの全ラインナップ。

貯留層工学

tNavigator、PetEx、RMS — シミュレーションによる座席配置の最適化およびレベル2~3のデータ収集。

石油工学

Petroleum Experts Suite(PROSPER、GAP、MBAL)、PIPESIM — 坑井ライフサイクルにおけるライセンス管理。

掘削・坑井工学

ハリバートン・スイート(StressCheck、WellCat)、WellPlan、COMPASS — ハリバートンによる60万ドルのコスト削減。

下流工程/プロセス工学

AVEVA、SmartPlant (SPLM)、Honeywell ULM、AspenTech — トークンモデル最適化。

電力・送電網

ETAP、NEPLAN、PSCAD — 電力系統解析ライセンスの管理。

海底・海洋

OrcaFlex、構造解析ツール — オフショア向けライセンス管理。

鉱業

Leapfrog、Vulcan、Datamine、Deswik、Rocscience、FLAC3D:探査から生産に至るまでのライセンス管理。

再生可能エネルギー

WindPRO、WAsP、PVsyst、Homer Energy — 対応アプリの拡充に伴い、順次提供開始予定です。

トップに戻る

話をしよう

Open iT 、貴社のビジネスにどのようなメリットがあるかをご紹介します。
ご注意:
このフォームを送信することにより、Open iT からの追加の連絡を受け取ることに同意したものとみなされます。 お客様の情報は、当社のプライバシーに関する通知に従って処理されます。