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.
O que o Open iT faz
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.
Tem alguma dúvida? Fale com um especialista em licenciamento.
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.
Como é que isto é calculado
Cada linha corresponde a um cálculo aritmético com base nos seus dados introduzidos e em dois resultados de clientes publicados. Nada aqui é modelado, ponderado ou inferido.
- Despesa anual = número de lugares × custo por lugar.
- Capacidade ociosa = lugares × percentagem de ociosidade. O intervalo padrão de 20 a 40 por cento é o que a Open iT mede em parques de engenharia.
- Referência publicada = despesa anual × 20% e × 20,8%. A Devon Energy reduziu o seu orçamento para software de subsolo em 20% em 11 fornecedores e módulos (openit.com, 2022). Uma grande empresa do setor energético, cujo nome foi anonimizado, reduziu a modelação do subsolo de 12 milhões de dólares para 9,5 milhões de dólares, o que corresponde a 20,8%. Ambos os casos são apresentados como resultados de otimização e aproveitamento.
- Limite máximo de simultaneidade = lugares × (1 menos a percentagem de inatividade). A simultaneidade máxima real é superior à procura média e só pode resultar da regulação do tráfego.
A capacidade ociosa é o limite máximo: cada hora ociosa recuperada, algo que nenhuma propriedade consegue alcançar. O valor de referência é o limite mínimo atingido por duas implementações reais, com uma diferença de apenas um ponto entre si. O seu resultado situa-se entre esses dois valores, e a única forma de o afinar é através da medição.
O que isto não lhe pode dizer
- A sua percentagem real de inatividade. Até que o Nível 2 avalie a atividade do anfitrião, o controlo deslizante representa uma estimativa e é o valor de entrada que determina todo o resultado.
- A sua concorrência máxima real. Doze meses de medição permitem-lhe determinar o pico em relação ao direito por módulo.
- Quais são os lugares recuperáveis. A recuperação automática é executada no FlexLM, LM-X, LUM e RLM. O Petrel no FlexNet é elegível; qualquer outro sistema no seu parque de equipamentos deve ser verificado primeiro.
- Se a opção «suspender» se adequa às vossas operações. A reativação do Petrel demora entre 5 a 15 minutos para um engenheiro, razão pela qual a opção «suspender» é preferível à opção «terminar», mas os limiares ainda têm de ser definidos em conjunto com os vossos responsáveis.
Valores em USD. São utilizados dois resultados de clientes publicados como intervalo de referência. Trata-se dos resultados desses clientes, apresentados como resultados de aproveitamento e otimização, e não constituem uma projeção para o seu parque imobiliário.
Perguntas mais frequentes
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.