Introduction:

Many customers run multiple Teamcenter-SPDM solutions across the enterprise, mixing multiple instances, multiple ISV vendors, and hybrid cloud/on-prem implementations. This fragmentation reduces the customer’s ability to uniformly access data. Consolidating Teamcenter-SPDM on Azure can speed the shift to one consistent, harmonized PLM experience, enterprise wide. 

What is Teamcenter Simulation?

Teamcenter Simulation integrates simulation data, processes, and results into the broader PLM (Product Lifecycle Management) environment. Instead of engineers running simulations in silos on local drives, it provides:

• A single source of truth for CAD, simulation models, inputs, and results.
• Traceability across design, analysis, and manufacturing.
• Support for multi-CAD, multi-CAE tools (e.g., NX Nastran, ANSYS, Abaqus, Star-CCM+).
• Primary benefit Teamcenter Simulation SPDM gives you full traceability from source to solution. SPDM is a single source of truth where CAE analysis of a product design testing is related to a corresponding item in original CAD. This relationship of CAD and SIM data is a key to determine which CAD revision is captured in a particular CAE analysis.

Architecture:

Siemens Teamcenter SPDM baseline architecture has two major blocks of architectures which are connected.

1. Teamcenter PLM core deployment
2.  StarCCM deployed on HPC Cyclecloud Slurm Workspace

1. Teamcenter PLM Core Deployment:

It has four distributed tiers (client, web, enterprise, and resource) in a single availability zone. Each tier aligns to function and communication flows between these tiers. All four tiers use their own virtual machines in a single virtual network. The Teamcenter Simulation aka CAE manage is core business functionality of SPDM runs on a central server in the enterprise tier and users access it through a web-based or thick-client interface. You can deploy multiple instances in Dev and Test environments by adding extra virtual machines and storage on virtual networks separate from production virtual networks.

2. StarCCM HPC Cyclecloud slurm cluster architecture:

Siemens StarCCM simulation software will be deployed on Azure Cyclecloud HPC Scheduler node. CAE Analyst fires the simulation jobs from Teamcenter Active workspace or Rich client UI. Azure HPC will then spin up and HPC nodes, these nodes will process the jobs submitted by CAE Analyst based on the runtime parameter. StarCCM will processed complete the simulation iteration and .sim file output will be generated.

Workflow

1. CAE Analysts, SPDM & Teamcenter users access the Teamcenter application via an HTTPS-based endpoint Public URL. Users access the application through two user interfaces: (1) a Rich client and (2) an Active workspace client, CAE engineer/Simulation Analysts  access the Teamcenter through the Teamcenter Simulation client. Teamcenter Simulation client is lightweight thin client runs on users’ desktop.
2. User access will be authenticated via Company’s Azure Entra ID. Azure Entra ID with SAML configuration allows single sign on(SSO) to the Teamcenter application.
3. Azure Firewall & Azure backbone Security component which filter the traffic and threat intelligence feeds directly from Microsoft Cyber Security. Https traffic directed to the Azure Application gateway. The Hub virtual network and Spoke virtual network are peered so they can communicate over the Azure backbone network.
4. Azure Application Gateway routes traffic to the Teamcenter’s web server virtual machines (VMs) in the Web tier.
5. Siemens PLM Teamcenter deployment on Azure.

• For detailed information about Teamcenter Architecture on Azure  refer this url.
• Teamcenter Simulation Client runs on Teamcenter User’s desktop.
• CAE manager is deployed as integral part of the Teamcenter package.

6. Teamcenter Simulation on Azure HPC:

• CAE Engineer executes the following typical workflow with Azure HPC cluster

Step 1: CAD Data & Product Structures

• CAD models (e.g., from NX, CATIA, SolidWorks) are managed in Teamcenter.
• Simulation engineer links simulation models directly to Teamcenter product structures.
• Ensures simulation always uses the latest or correct version of the design.

Step 2: Build Simulation Model (Pre-processing)

• Simulation templates define solver type (FEA, CFD, Multiphysics) and required inputs.
• Engineers use tools like NX CAE, Simcenter 3D, ANSYS, Abaqus, or Star-CCM+ integrated with Teamcenter.
• Meshes, boundary conditions, loads, and materials are associated with the correct design revision.

Step 3: Manage Simulation Data

• All input decks, scripts, and models stored in Teamcenter for version control.
• Metadata (e.g., load case, solver settings) captured for searchability & re-use.
• Supports process automation: simulation workflows can be pre-configured for repeatable tasks.

Step 4: Run Simulation Jobs (Enhanced with Azure CycleCloud Benefits)

• Jobs submitted to local HPC clusters or cloud HPC (Azure CycleCloud,) directly from Teamcenter.
• Teamcenter stores solver logs, job status, and output files.
• Following diagram show end to end workflow starts with Teamcenter CAE manager--> StarCCM -->HPC cluster ->Simulation processing Sim file -->Sim file back to Teamcenter
• Teamcenter CAE manager--> StarCCM running on HPC cluster

• Teamcenter generates the job file on the HPC node

• HPC Cluster creating HPC nodes 

• Squeue monitoring on HPC node

• Job monitoring on Teamcenter UI

• Simulation output file generated by Sbatch job

• • • • • • File copied over to Teamcenter shared file location  

                            

            

            Step 5: Post-processing & Results Management

            • Results imported back into Teamcenter: stress plots, temperature distributions, flow fields, etc.
            • Visualization via Simcenter 3D, JT format (lightweight 3D), or web-based viewers.
            • Results tied back to:
            • Design versions
            • Simulation setup
            • Load cases
            • This creates a traceable digital thread from requirements → design → simulation → results.

             

            Step 6: Review, Sign-off, and Collaboration

            • Results shared with design, manufacturing, and management teams in Teamcenter.
            • Review workflows, e-signatures, and approvals integrated into PLM processes.
            • Simulation results influence design changes and product validation reports.

Azure CycleCloud adds several key advantages:

• On-demand scaling: Automatically provisions Azure compute nodes when workloads spike, then scales down when jobs complete to reduce costs.
• HPC Slurm scheduler integration: Supports popular schedulers like Slurm enabling smooth job submission from Teamcenter.
• Multi-VM sizes & GPU support: Allows selecting the right mix of CPU/GPU VMs for different simulation workloads (e.g., CFD, FEA, ML-driven simulations).
• Hybrid flexibility: Combine on-prem HPC with Azure bursting to handle peak demand without over-provisioning local hardware.
• Cost governance: Built-in cost controls, job quotas, and reporting to track simulation expenses.
• Security & compliance: Leverages Azure security, VNet isolation, and role-based access control for simulation data and compute resources.
• Integration with Azure Storage: Simplifies access to input/output files using Azure Blob, Azure NetApp Files, or Lustre for HPC-grade throughput.

Conclusion:

Siemens Teamcenter SPDM, when deployed on Azure HPC CycleCloud Workspaces, delivers a scalable and high-performance simulation data management solution. The integration with Azure CycleCloud enables dynamic provisioning of compute resources, allowing simulation workloads to scale elastically based on demand. This ensures optimal resource utilization and cost efficiency, especially during peak simulation cycles. With support for Slurm scheduling, multi-VM configurations, and GPU acceleration, SPDM on HPC CCWs empowers engineering teams to run complex simulations faster and more reliably. The architecture’s hybrid flexibility—combining on-premises and cloud bursting—further enhances throughput without overcommitting infrastructure, making it a robust foundation for enterprise-wide digital thread and product validation workflows.