Estimate, Freeze, and Run a Data Center FactSim Study
Use this workflow after the data center scenario, baseline, CAD resource, and Model Asset are ready. FactSim keeps the estimated work, frozen inputs, execution stages, result identity, and review evidence connected to the same scenario.
Module availability and execution limits depend on the active tenant profile.
Prerequisites
| Requirement | Check |
|---|---|
| Scenario and baseline | The engineering question, baseline, changed scenario, and comparison criteria are reviewed. |
| Versioned resources | CAD, Model Asset, component geometry, and baseline resources have stable versions and checksums. |
| Execution profile | The tenant has an admitted FactSim profile, available capacity, and an accepted cost or runtime limit. |
| Permissions | The operator has the required view, manage, run, audit, and report permissions for the intended steps. |
| Review ownership | The engineering reviewer and report owner are assigned before submission. |
Permissions
| Task | Permission |
|---|---|
| View configuration, bindings, and runs | dcops.factsim.view |
| Estimate and freeze inputs | dcops.factsim.manage |
| Submit or cancel a run | dcops.factsim.run |
| Reconcile execution evidence | dcops.factsim.audit |
| Render and publish a report | dcops.factsim.report |
Run workflow
Estimate the run
- Open Data Center Operations > Engineering Validation > Scenario Lab.
- Select the scenario.
- Select a CAD resource version.
- Select the scenario baseline.
- Select the matching Model Asset version.
- Choose Estimate.
- Review the estimated cell count, runtime, cost, currency, and expiry time.
An estimate is tied to the selected resource versions and execution profile. Re-estimate after changing geometry, the baseline, the Model Asset, or an expired estimate.
Freeze the inputs
Choose Freeze inputs after the estimate and engineering assumptions have been reviewed. The frozen binding records:
- baseline resource and checksum;
- CAD resource and version checksum;
- Model Asset and version checksum;
- component geometry set;
- execution profile and runtime contract;
- estimate and binding checksums.
Frozen inputs remain immutable for that run. Create a new binding when an input or execution profile changes.
Submit and monitor
Choose Submit run after the binding is frozen. The progress view follows four stages:
| Stage | Meaning |
|---|---|
| CAD preparation | Validates and prepares the selected geometry for execution |
| Thermal-fluid run | Executes the admitted solver profile |
| Audit gate | Checks result identity, required evidence, and completion state |
| Report render | Builds the governed result package after reviewer action |
You may leave the page while a long-running job is active and return to the same run record. Use Cancel run when the scenario is no longer needed. GPU time already consumed by the run cannot be recovered.
Recover from a problem
| Message or state | Response |
|---|---|
| Estimate expired | Run the estimate again and review the new values |
| Version has no checksum | Select or create a resource version with a completed checksum |
| Tenant slots are in use | Wait for an active run to finish or cancel an unnecessary run |
| CAD preparation failed | Review geometry, domain size, supported formats, and cell estimate |
| Thermal-fluid run failed | Review inputs and limits, then retry or prepare a smaller scenario |
| Audit gate failed | Review result evidence and input identity before submitting again |
| State appears stale | Use Reconcile when authorized, then review the latest stage evidence |
Expected output
A completed execution reaches Ready for report with a result reference, checksum, stage evidence, and the frozen input identity. Continue with Review and Publish Data Center Simulation Evidence.