By default, ANSYS Workbench does not retain design points after they are solved. It saves the calculated data only for the current design point. For other design points, only the parameter values are saved. If you want to work with a design point other than current design point, you can:
Additionally, you can export design point parameter values to a CSV file, which you can then use in other programs for further processing.
In some cases, you might want to switch back and forth between multiple designs within the same project. ANSYS Workbench enables you to select one or more design points and retain their calculated data within the project. Data is always retained for the current design point.
To retain design point data:
In the design points table, select the Retained check box for each of the desired design points.
Generate retained design point data by updating the design points.
Once design point data has been retained:
You can verify that the data has been retained and see the availability and state of the retained data. For more information, see Reviewing the Retained Data Column.
You can view multiple designs by setting different design points as current. For more information, see Setting a Different Design Point as Current.
You can verify that data has been retained by viewing the icon in the Retained Data column for each design point. This icon indicates the availability, validity, and state of the retained data for the design point.
Different kinds of changes to the project have different impacts on retained data. Changes to the parameter values for the design point cause the retained data to become out-of-date but still valid. Non-parametric changes cause the retained data for non-active design points to become invalid.
Note: During a local design point update, only the design point being updated is active. When no update is in progress, only the current design point is active.
The state of the design point and the validity of its retained data do not necessarily match. It is possible for a design point to be up-to-date while its retained data is invalid or vice versa.
When used in the Retained Data column, icons have slightly different meanings than they do elsewhere in Workbench. The following table describes the meaning of each icon within the context of retained design point data.
| Icon | State/Validity | Description |
|---|---|---|
| Valid and up-to-date | The design point has valid retained data that is up-to-date. The retained data is available to be exported. |
| Valid but out-of-date | The design point has valid retained data, but the retained data is out-of-date because of a change to the design point's parameter values. The retained data is available to be exported. |
| Invalid or non-existing | The design point either does not have retained data or previously retained data has been invalidated by a non-parametric change. The retained data is not available to be exported. |
Each state is illustrated in the image below, as follows:
DP0 (Current) has retained data that is valid and up-to-date. The current design point always has valid retained data and the Retain check box is disabled.
DP1 has valid retained data that is current and up-to-date.
DP2 either does not have retained data or has retained data that is invalid.
DP3 has retained data that is valid but out-of-date.

Once multiple design points have retained data, you can switch back and forth between these multiple designs within the project. To view the design associated with a given design point, you set it as the current design point. Only design points with retained data can be set to current, and only one design point can be set to current at a time.
To set a design point as the current design point:
In the design points table, right-click a design point that has retained data.
From the context menu, select .
The design point becomes the current design point for the project. In the Name column, (Current) displays after the name of the current design point. Setting a design point as current does not automatically update it.
Note: In a project that includes a Microsoft Office Excel system and uses retained design points, switching to a different up-to-date design point via the menu option automatically updates the Excel system, which can be time-consuming if the spreadsheet contains macros or extensive calculations.
To work with the calculated data for a design point other than the current design point, you can export the design point to a separate project. A new project is created for each design point that is exported.
When you export a design point, if the design point has already been exported, the existing exported files are overwritten.
To export design points:
In the design points table, select the desired design points.
Right-click the points.
Select .
The projects resulting from the export are fully independent projects named
projectname_dpn.wbpj.
They are located as siblings in the same directory as the main project. The
content of the new project depends on the state of the design point's retained
data at the time of the export:
If valid retained data is available for an exported design point, the retained data is used to create the new project. This retained data can be either up-to-date or out-of-date.
If no valid retained data is available for an exported design point, the project exported is an out-of-date project based on the current design point with the parameter values for this design point applied. No valid retained data exists if the design point is either not selected to retain data or is selected but retained data is not yet generated or has became invalid. You are asked to confirm before the export of such a design point is performed. When you open the exported project, it is out-of-date and requires an update to solve for the exported design point.
After an export, you must save the parent project before you can export design points again.
If a design point fails to export, the files for this design point remain in the project_files\dpn directory until you delete them manually or attempt to update the design point again.
Note: Be aware that DesignXplorer data is not a part of design points and is not exported. DesignXplorer is a consumer of design points but does not define design points. Consequently, it is not involved when a design point is updated, or by extension, exported.
From the design points table, you can export the design point parameter values to a CSV (Comma-Separated Values) file, which you can then use with other software tools for further processing. This file is created in an "extended" file format. In addition to supporting standard CSV formatting, it supports several Workbench-specific formatting conventions.
To export design point parameter values to a CSV file:
In the design points table, right-click a cell.
Select Export Table Data as CSV.
A file similar to the following is generated:
# # 10/1/2012 10:38:01 AM # The parameters defined in the project are: # P1 - WB_B [mm], P2 - WB_D [mm], P3 - WB_L [mm], P4 - WB_P [N], P5 - WB_E [MPa], # P10 - WB_SIG [MPa], P8 - WB_DIS [mm], P9 - WB_BUCK [N] # # The following header line defines the name of the columns by reference to the parameters. Name, P1, P2, P3, P4, P5, P10, P8, P9 DP 0, 2, 5, 100, 1000, 200000, 12000, 80, 1028.91145833333 DP 1, 3, 5, 150, 1000, 200000, , , DP 2, 5, 5, 20, 1000, 200000, , ,
The values are always exported in units as defined in ANSYS Workbench.
Values are separated by commas.
The optional header line indicates the name of each column.
Each line is an independent record made of fields separated by commas.
The format is not dependent on the locale, which means that the real number 12 and 345 one-thousandths is always written
as 12.345, regardless of the regional settings of
the computer.
If a line starts with a "#" character, it is considered a comment line rather than a header or data line and is ignored.
The header line is mandatory. It is the line where each parameter is identified by its ID (P1, P2, ..., Pn) to describe each column. The IDs of the parameters in header line match the IDs of the parameters in the project.
The first column is used to indicate a name for each row.
A file can contain several blocks of data, with the beginning of each block being determined by a new header line.