When a Workbench project is saved or uploaded to an EKM repository, it is saved as an archive file (.wbpz), and a Workbench project report is automatically generated. To view the project report, simply click on the .wbpz file in the file list window. The Workbench Project Report is displayed as HTML by default in the file list window. The following figure shows a sample Workbench project report. The navigation pane on the left contains a table of contents that makes it easy to navigate through the report. To hide or show the navigation pane, click the icon in the top left corner of the pane. Additional report actions are also available in the report view, and are described below.
When you view a Workbench Project Report, a navigation pane
is displayed to the left of the report. This pane contains a table
of contents that provides an overview of the sections in the report.
You can click on a section in the table of contents to instantly jump
to that section. You can hide the navigation pane from view by clicking
in the top left corner of the pane.
You can then redisplay the navigation pane at any time by clicking
in the top left corner of the report
window.
Two actions are displayed in the top-right corner of the report window: Copy Report and Download Report.
The Copy Report feature enables you to save a copy of the report
in another location in EKM. If you click the Copy Report icon
, the report is copied to the clipboard. You can
then navigate to the folder to which you want to copy the report and
select > .
The report with have the name of the parent CAE file with a Simulation Details Report suffix.
The Download Report feature enables you to save the report as
an Excel, Word, PDF or XML file on your local computer. To use this
feature, click the Download Report icon
and then select either Excel, PDF, XML, or Word Document from the menu. Depending on your browser
settings, you may be prompted to specify a save location for the file
or to open the file upon download. If your browser is set to download
files automatically, the report is instantly downloaded in the selected
format to the default download location specified in your browser
settings. A link to the file may be displayed on a download bar or
in a download window for easy access. For example, if you are running
on Google Chrome, a download bar is displayed at the bottom of the EKM window:

The Workbench project report is divided into sections, and the title of each section is displayed in a table of contents in the navigation pane. Section titles may include Summary, Project Schematic View, Files, Design Points, and Outline of All Parameters. The report may also contain additional subsections, depending on the setup, solution, and results in the Workbench project. Some examples are shown below when Design Exploration is set up.
The Summary table contains project properties.
These include Project, Date, Time, Product Version, and Last Saved Version. These properties
can be used as search criteria to retrieve the project.
The Project Schematic View contains an image of the Workbench-exported project schematic. A sample is shown below.

A project schematic is made up of all the systems defined for the project. Each system has individual cells that show the project flow. Each cell has an application or Workbench workspace associated with it. Some cells are associated with data-integrated applications such as Fluent or Mechanical APDL applications. Some cells represent Engineering Data or Parameters. In some cases, multiple cells in a system will be associated with the same application. A visual indication of a cell's state (for example, attention required, up to date) is presented as an icon on the right side of each cell. Refer to Understanding Cell States in the ANSYS Workbench User's Guide for details.
The Files table is the Workbench-exported list of all files included in the project. A sample is shown below.

The Design Points table contains the Workbench-exported list of Design Points for the project. A sample is shown below. Refer to Using Six Sigma Analysis in the Design Exploration User’s Guide for more details on using Six Sigma Analysis.

The Outline of All Parameters table contains the Workbench-exported list of all parameters associated with the project. Note that only the current design point (DP0) is included. A sample is shown below.

Parameters Correlation is provided when Design Exploration is set up and describes the selected input parameters and their variation range, the chosen Correlation type, and the generated Correlation Matrix and charts. A sample is shown below. Refer to Using Six Sigma Analysis in the Design Exploration User’s Guide for more details on Parameters Correlation.

Response Surface is provided when Design Exploration is set up and describes the selected type of meta-model, including its properties, the obtained quality, and the generated Response Points and charts. A sample is shown below. Refer to Using Response Surfaces in the Design Exploration User’s Guide for more details on Response Surface.

Goal Driven Optimization is provided when Design Exploration is set up and describes the chosen Optimization type and the generated candidates and charts. A sample is shown below. Refer to Using Goal Driven Optimization in the Design Exploration User’s Guide for more details.

Six Sigma Analysis is provided when Design Exploration is set up and describes the selected input parameters and their variation range, the chosen Design of Experiments type, and the generated Matrix of Experiments. A sample is shown below. Refer to Using Six Sigma Analysis in the Design Exploration User’s Guide for more details on using Six Sigma Analysis.

The Appendix is provided when Design Exploration is set up and contains tables and other information that is referenced in other parts of the report. A sample is shown below.

The last section of a Workbench project report contains details for each system that is defined for the Workbench project. For each system, it provides details for all CAE model files that are referenced by cells contained within the system. Content can include a model image, geometry data, mesh data, boundary conditions, and so on. The figure below shows some of the details of a sample FLUENT system.
