Closed & Restricted Networks
Metering that never calls home.
Open iT installs as a self-contained deployment inside a closed area. Collection, reporting and analysis all run within the boundary, so nothing has to cross it for the system to work.
- Level 1, Level 2, CLIMS and reporting, all inside the enclave
- Data leaves anonymized, on your terms, or not at all
- Connected subnets roll up. Closed areas stay closed.
Your closed areas hold the most expensive engineering software you own and the least data about it.
A tool that meters inside the enclave and analyzes in a cloud service isn’t an air-gapped tool. That surfaces three weeks in, after the architecture review, and it ends the evaluation. So the open side of the estate gets optimized every renewal while the closed side runs on a seat count nobody has tested against usage.
Across engineering estates, 20 to 40 percent of licenses are idle at any given moment. In a closed area that number isn’t a measurement. It’s an assumption, and it has been renewed on for years.
Open iT の機能
1
Run the whole stack inside the boundary.
Four things install in the area and talk only to each other: Level 1 against the license managers, Level 2 on the workstations for True Active Usage, CLIMS as the one console for every server in there, and the reporting and analysis servers behind them. Nothing calls out. Nothing has to cross the boundary for any of it to work.
2
Move data on your terms, or not at all.
Three patterns cover most sites. Fully self-contained, where the area reports from inside itself and nothing leaves. Periodic export, where an anonymized data set goes out for consolidated reporting on the open side. Or a connected roll-up, where a path already exists between an enterprise network and a program subnetwork and collected data is forwarded to a central server. Which one you get is a security-governance decision your team makes during implementation planning, not a product setting.
3
Meter a frozen baseline without unfreezing it.
Metering follows the license manager rather than an application build, so FlexNet, DSLS, LM-X, RLM, Sentinel and CodeMeter estates are covered whatever release sits behind them. Version data is captured in the record, so three programs on three validated baselines of the same tool read as three demand curves. Earlier Open iT releases keep receiving maintenance too: hotfix streams are maintained for 9.17, 9.19 and 10.1 across Core Server, client and CLIMS.
4
Train your people, because we're not allowed to see your data.
In a classified environment we can’t look at your data, which rules out the model where the vendor runs the analysis and hands over a report. So your team is trained to data analysis specialist level, on your system, with your data. They build and interpret the reports, tune parameters, investigate a denial pattern and produce the evidence a renewal needs, without anyone outside the organization seeing a record.
ご質問がありますか？ライセンス担当者に相談してください。
Closed-Area Deployment Checklist
What your security team needs to decide before an implementation plan can be written. Record what is settled, flag what is not, and bring the result to the scoping conversation. Your answers stay in this browser tab until you choose to send them.
decisions made
Your decision record
Decided items are the inputs to an implementation plan. Open items are the agenda for the scoping conversation. Bring us the constraint, not the requirement.
計算方法
各行は、入力データと公表されている2つの顧客成果に基づく算術演算です。ここには、モデル化、重み付け、推論といった処理は一切行われていません。
- 年間支出額 ＝ ライセンス数 × 1ライセンスあたりのコスト。
- 遊休容量＝座席数×遊休率。20～40％という標準的な範囲は、Open iT が各エンジニアリング施設で測定した数値です。
- 公表されたベンチマーク＝年間支出×20％および×20.8％。デボン・エナジーは、11社のベンダーおよびモジュールにわたる地下ソフトウェア の予算を20％削減した（openit.com、2022年）。公表された匿名化された大手エネルギー企業は、地下モデリングの予算を1,200万ドルから950万ドルへと、20.8％削減した。これらはいずれも、コスト削減と最適化の成果として報告されている。
- 同時接続数の上限 = 座席数 × (1 － アイドル率)。実際のピーク時の同時接続数は平均需要を上回りますが、これはメータリングによってのみ生じます。
遊休容量が上限となります。これは、遊休時間を1時間でも削減できれば達成できる数値ですが、どの不動産でも達成できていません。ベンチマークは下限であり、2つの実際の導入事例が、1ポイント以内の差でこの数値に到達しています。貴社の結果はこれら2つの間にあるものであり、その差を縮める唯一の方法は測定を行うことです。
これだけではわからないこと
- 実際のアイドル時の割合です。レベル2でホストのアクティビティが測定されるまでは、このスライダーは仮定値であり、結果全体がこの値によって大きく左右されます。
- 実際のピーク同時接続数です。12か月間の計測データから、モジュールごとの許容値に対するピーク値がわかります。
- どのシートが回収可能か。FlexLM、LM-X、LUM、RLM では自動回収が実行されます。FlexNet 上の Petrel も対象となりますが、それ以外の環境にあるものは、まず確認が必要です。
- サスペンドが自社の運用に適しているかどうか。Petrelの再起動にはエンジニアが5～15分を要するため、サスペンドはターミネートよりも優れていますが、しきい値の設定については引き続きリーダーと協議する必要があります。
金額は米ドル建てです。ベンチマーク範囲として、公表されている2件の顧客実績が用いられています。これらは当該顧客の成果であり、「収穫」および「最適化」の結果として報告されたもので、お客様の資産に関する予測ではありません。
よくある質問
Does Open iT need internet access to work?
No. Every component runs inside the deployment, analysis included. A closed area gets metering, denial reporting and active-versus-inactive analysis on the same terms as your open network, with no connection to anything outside it.
Can we consolidate closed and open reporting?
Only if your security governance allows it. Where a path already exists, collected data is forwarded to a central server. Where it doesn’t, the area reports from inside itself, and anything that does leave is a periodic anonymized export your security team specified.
Can you support us with cleared personnel?
Bring the requirement to the scoping conversation. Where a program needs support staff of a particular nationality or holding a particular clearance, that gets agreed as part of the engagement rather than discovered afterwards.
Do we have to upgrade to stay supported?
No. Earlier releases keep receiving maintenance, with hotfix streams for 9.17, 9.19 and 10.1 across Core Server, client and CLIMS. Accredited environments can’t upgrade on a vendor’s schedule and shouldn’t be asked to.
Bring us the constraint, not the requirement. Which areas are closed, which baselines are frozen, what your personnel rules are, and which applications matter. Then start with a Level 1 usage assessment across one renewal cycle. In a closed area it runs entirely inside the boundary.