

.png)
NI SP EF HPC Portal
Developed by NI SP as an evolution of NICE EnginFrame, EF HPC Portal is a browser-based engineering access and HPC operations platform that connects engineers, applications, schedulers, data, remote visualization, monitoring and administration in one environment. It provides native integration with Slurm, HPC Gridware, PBS and LSF, pre-configured application templates for Ansys, Star-CCM+, Matlab and OpenFOAM, a WYSIWYG HPC Services editor, job dependencies and reservations, REST and Python automation, data spoolers with SSH/S3 file access and Jupyter integration, GPU and license monitoring, DCV remote desktop integration, enterprise identity management and cloud bursting. EF HPC Portal is the engineering access and HPC operations layer of SimOps, bridging engineering users and the underlying computing environment, while full SimOps transformation also requires organizational processes and complementary enterprise platforms.

The SimOps Team distilled a set of the 20 major best practices drawn from over 230 engineering simulation projects, including three of the "Magnificent Seven", and 160 case studies, over the last 12 years. These best practices are grouped under the three 'Golden-Triangle' lenses of Technology, Process, and People, yet intentionally cross-reference one another, because SimOps only succeeds when the three act in concert. Together with the NI SP team, we compared major features and capabilities of EF HPC Portal with the SimOps best practices. The ratings below express SimOps Best-Practice alignment: how directly and effectively EF HPC Portal's documented capabilities support each best practice. They are not a rating of product maturity.
What EF HPC Portal enables in practice
-
Submit and monitor simulations from a browser through pre-configured application templates, without command-line or scheduler expertise
-
Automate workflows through job dependencies, reservations, VDI hooks, the REST API, the Python efpclient CLI and CI/CD integration
-
Use one portal across Slurm, HPC Gridware, PBS and LSF, and burst to the cloud when local capacity is exhausted
-
See GPU, CPU, wall time, license slots, storage and active sessions in real time and export metrics to StatsD/Grafana
-
Work with data, notebooks, applications and DCV remote visualization in one engineering workspace
-
Administer the platform through RBAC, MFA, Entra ID/LDAP/Active Directory integration, a secure web proxy and browser-based configuration
What EF HPC Portal does not do
While EF HPC Portal provides a broad foundation for engineering access and HPC operations, full SimOps maturity requires integration with complementary capabilities, including:
-
Native version control, branching, review and promotion of workflow definitions (Git/GitOps tooling)
-
PLM/PDM and CAD-triggered simulation integration
-
Enterprise data catalogs, retention policies, archival and lineage
-
Full simulation FinOps with forecasting and chargeback/showback
-
Energy and carbon accounting, and digital-twin or surrogate-model platforms
EF HPC Portal is designed to integrate into this broader ecosystem through its REST API, Python CLI, workflow hooks and CI/CD integration.
Why NI SP EF HPC Portal is SimOps Compliant
In the following, we check the SimOps compliance of NI SP EF HPC Portal. EF HPC Portal is, at its core, an engineering access and HPC operations platform: it focuses on self-service simulation access, workflow automation, scheduler integration, resource and license utilization, hybrid-cloud access and operational visibility. Its most distinctive characteristic is the breadth of the engineering operating environment it brings together: the same portal that gives engineers self-service access also provides scheduling, monitoring, data handling, identity, collaboration and administration. With the capabilities below, EF HPC Portal provides a strong foundation for organizations implementing SimOps, while culture, governance, training and full lifecycle governance are addressed through complementary organizational processes and platforms. EF HPC Portal is best understood as a broad engineering access and HPC operations backbone within a larger SimOps ecosystem rather than a complete, end-to-end SimOps solution.
1. Simulation-Driven Decision Culture
EF HPC Portal lowers the barrier between an engineer and simulation execution. Self-service submission, pre-configured application templates, browser access, in-portal result preview and notifications make simulation easier to start and iterate, and NI SP positions self-service explicitly as a way to increase the frequency and timeliness of engineering simulation. The organizational culture itself remains outside the product.
SimOps Best-Practice Alignment: High
2. Shift-Left Simulation
Application templates, low-friction submission, preview of partial results during runtime and direct access to compute and data reduce the effort of exploratory simulation, supporting more simulations earlier in the design process. Formal product-development processes that institutionalize shift-left are defined by the organization.
SimOps Best-Practice Alignment: High
3. End-to-End Workflow Automation
EF HPC Portal provides multiple direct automation mechanisms: scheduler integration, job dependencies, reservations, VDI pre-submit and closing hooks, the REST API, the Python efpclient CLI, CI/CD integration, automated workload-to-resource matching and automatic release of provisioned resources. This is direct SimOps workflow automation rather than simple job submission.
SimOps Best-Practice Alignment: High
4. Self-Service Simulation Access
Self-service access is a core capability. Engineers submit applications without command-line expertise through pre-configured templates, access files and results in the browser, launch Jupyter notebooks, monitor jobs, receive notifications and open DCV remote desktop sessions, which greatly reduces dependence on specialist scheduler knowledge.
SimOps Best-Practice Alignment: High
5. Hybrid / Cloud HPC Strategy
Scheduler integration, cloud bursting, AWS Workspaces Core integration and browser-based access across distributed environments support a practical hybrid operating model, in which on-premises HPC is extended with cloud capacity when demand exceeds local capacity.
SimOps Best-Practice Alignment: High
6. SimOps Center of Excellence Enablement
The administrative feature set is highly relevant to a SimOps Center of Excellence: centralized web proxy, browser-based configuration, RBAC, enterprise identity integration, non-disruptive upgrades, operational dashboards, notifications and multi-instance administration. Governance, standards, training, vendor management and maturity ownership of a formal CoE remain organizational responsibilities.
SimOps Best-Practice Alignment: High
7. Data Governance and Security
Role-based access, configurable data locations, secure web proxying, MFA and Entra ID, LDAP and Active Directory integration provide centralized access control, and integrated SSH/S3 access supports governed access to distributed data. Enterprise data classification, retention, lineage and regulatory-control frameworks remain complementary.
SimOps Best-Practice Alignment: High
8. Simulation Cost Tracking and Optimization
GPU utilization, cores, wall time, license consumption, filesystem usage, active sessions and active jobs are monitored, and job histories provide evidence for allocation analysis and capacity planning. Dynamic resource allocation and cloud bursting support infrastructure efficiency. A complete simulation FinOps layer with forecasting and chargeback/showback is not part of the portal.
SimOps Best-Practice Alignment: High
9. Cross-Functional Collaboration
RBAC, shared applications and data, collaborative DCV sessions, design reviews, guided walkthroughs and targeted real-time notifications create a strong technical collaboration environment. Recurring management cadences and communities of practice remain organizational practices.
SimOps Best-Practice Alignment: High
10. Version-Controlled Workflows
The REST API and Python CLI support automation pipelines and CI/CD integration, and application templates provide standardized submission definitions. Native version control, branching, review and promotion of workflow definitions are not demonstrated; a Git/GitOps layer can complement the portal where strict release management is required.
SimOps Best-Practice Alignment: Medium
11. End-to-End Data Lifecycle Management
Data spoolers, an integrated file manager, SSH/S3 integration, file preview, user-managed data locations, Jupyter integration and in-portal result access create a strong operational data layer around simulation workflows. Enterprise archival, retention, classification, lineage and governed deletion remain complementary.
SimOps Best-Practice Alignment: High
12. AI/ML and Digital-Twin Enablement
Jupyter integration and scheduler-managed GPU training and inference provide direct support for ML workloads. EF Portal Active Insights, currently in preview, answers questions about jobs, sessions and cluster health and helps with root-cause understanding. Digital-twin management, surrogate-model lifecycle management and active learning are not part of the portal.
SimOps Best-Practice Alignment: High
13. Performance Benchmarking and Tuning
Real-time GPU monitoring, job history, resource consumption, wall time, CPU load, JVM use, license consumption, Grafana/StatsD integration and log analytics provide strong operational telemetry for tuning and capacity decisions. A formal automated benchmark-regression framework across solver versions and hardware is not explicitly provided.
SimOps Best-Practice Alignment: High
14. Continuous Feedback Loops
Dashboards, job history, live logs, notifications, system-event alerts, in-session result preview and a rapid product release cadence create continuous operational feedback. Post-mortems, updated playbooks and structured knowledge sharing remain the responsibility of the adopting organization.
SimOps Best-Practice Alignment: High
15. Onboarding and Upskilling
The intuitive browser interface, self-service submission, application templates, WYSIWYG service editor and preconfigured services remove the command-line barrier and give new users a practical path to their first workload. Formal curricula, competency models, mentoring and certification remain complementary organizational practices.
SimOps Best-Practice Alignment: High
16. User-Experience Monitoring
Live job state, active sessions, real-time operational dashboards, notifications, result previews, GPU and resource metrics and direct access to logs make the user experience operationally visible, so engineers and administrators can react while work is in progress.
SimOps Best-Practice Alignment: High
17. License & Hardware Utilization Optimization
This is one of the platform's strongest contributions. GPU utilization, cores, wall time, license slots, CPU load, storage and active sessions are visible, and dynamic allocation, load balancing, reservations, cloud bursting and automatic resource release align capacity with active workload. Live license utilization helps identify unused allocations and avoid wasted spend.
SimOps Best-Practice Alignment: High
18. PLM / CAD / Pipeline Integration
REST APIs, the Python CLI, workflow hooks and CI/CD integration create strong pathways into broader digital engineering toolchains, and pre-integrated engineering applications strengthen application-level integration. PLM/PDM and CAD-triggered simulation integration are not specifically demonstrated and remain complementary.
SimOps Best-Practice Alignment: High
19. Sustainability Metrics Tracking
Dynamic allocation, idle-resource reduction, on-demand provisioning, workload-aware scheduling and running without virtualization overhead reduce resource consumption, and NI SP links these mechanisms explicitly to sustainable HPC operations. Direct energy-per-simulation measurement, carbon accounting and sustainability dashboards are not provided.
SimOps Best-Practice Alignment: High
20. Support for Maturity Assessment
This best practice asks how a product supports an organization's own SimOps maturity assessment and improvement process. EF HPC Portal supplies much of the operational evidence such an assessment needs: the Operational Dashboard, StatsD/Grafana export, job and operations insights, accounting, and resource and license utilization reporting. The portal does not itself perform the maturity assessment, assign maturity levels or manage the organization's maturity roadmap; those remain management practices.
SimOps Best-Practice Alignment: High

NI SP EF HPC Portal: Workspace and Operational Dashboard
SimOps Best-Practice Alignment Summary
Number | Best Practice | SimOps Best-Practice Alignment |
|---|---|---|
1 | Simulation-Driven Decision Culture | High |
2 | Shift-Left Simulation | High |
3 | End-to-End Workflow Automation | High |
4 | Self-Service Simulation Access | High |
5 | Hybrid / Cloud HPC Strategy | High |
6 | SimOps Center of Excellence Enablement | High |
7 | Data Governance and Security | High |
8 | Simulation Cost Tracking and Optimization | High |
9 | Cross-Functional Collaboration | High |
10 | Version-Controlled Workflows | Medium |
11 | End-to-End Data Lifecycle Management | High |
12 | AI/ML and Digital-Twin Enablement | High |
13 | Performance Benchmarking and Tuning | High |
14 | Continuous Feedback Loops | High |
15 | Onboarding and Upskilling | High |
16 | User-Experience Monitoring | High |
17 | License & Hardware Utilization Optimization | High |
18 | PLM / CAD / Pipeline Integration | High |
19 | Sustainability Metrics Tracking | High |
20 | Support for Maturity Assessment | High |
The analysis above demonstrates the SimOps compliance of NI SP EF HPC Portal. EF HPC Portal reaches High Best-Practice alignment across nineteen of the twenty best practices, with its strongest contributions in workflow automation, self-service HPC access, hybrid-cloud access, user-experience monitoring, and license and hardware utilization. It reaches Medium alignment for version-controlled workflows, where its REST API, Python CLI and application templates make it integration-ready for Git/GitOps tooling but native workflow version control is not provided.
These ratings express SimOps Best-Practice alignment, not product maturity. Several practices, including decision culture, Center of Excellence governance, structured training and maturity management, depend on organizational operating models; EF HPC Portal provides strong technical and operational support for them without replacing the organizational process. NI SP EF HPC Portal is best positioned as a broad Engineering Access and HPC Operations platform that bridges engineering users, workflows, schedulers, data, visualization, monitoring and infrastructure, making it a strong foundation for organizations seeking to industrialize simulation operations.
What customers say (vendor-provided)
"NI SP Professional Services helped us seamlessly integrate our HPC and CAE applications into EF HPC Portal while streamlining data management across our development teams. Their great expertise helped making our workflows more efficient and scalable. Also, the integration of NI SP's EF VDI Portal solution together with DCV has greatly improved remote desktop access to our pre-/post-processing resources, making Engineering teams more productive."
Jean-Yves Noel, HPC Infrastructure Engineer, Electrolux
Customer statement provided by NI SP. It is not independently verified by the SimOps Foundation and does not affect the Best-Practice alignment ratings.
If you are interested in the 25-page extensive analysis report, send your request to info@simops.com.
