DFS Pro BI Reports

DFS Pro BI turns governed datasets into operational reports. Use it when teams need a repeatable view of data quality, fusion results, maintenance history, facility operations, or AI workflow evidence.

Before you start

Confirm:

• bi.read access to view reports;
• bi.write access to create or edit reports;
• bi.schedule access for report schedules;
• DFS Pro package access when required by the deployment;
• at least one prepared dataset;
• source owner approval for the data shown in the report.

Open BI Reports

Go to the DFS Pro BI area and open the report list.

The report list supports:

• report search;
• status filter;
• folder organization;
• report creation;
• duplicate action;
• publish action;
• archive action;
• delete action where permitted.

Create a report

1. Select Create Report.
2. Enter a report name.
3. Add a description.
4. Choose a folder when folders are used.
5. Save.
6. Open the designer.

Use names that state the operational purpose.

Examples:

• Facility data quality overview
• Work order completion by asset
• Sensor and inspection evidence dashboard
• Energy meter reporting view

Bind a dataset

In the designer:

1. Open dataset binding.
2. Select a dataset.
3. Review available columns.
4. Choose dimensions, metrics, time fields, and filters.
5. Preview the query.
6. Save the binding.

Use validated datasets when the report will be shared outside the implementation team.

Add widgets

Use widgets based on the question the report should answer.

Widget	Use
Table	Review source rows, exceptions, and detailed records.
Bar chart	Compare categories, assets, or sites.
Line chart	Show time trends.
Pie chart	Show distribution for a small category set.
Scatter chart	Compare two numeric values.
Text	Add context, metric definitions, or report notes.
Filter widgets	Let viewers select time range, site, asset, status, or category.

Keep each report focused. Create a separate report when a second audience needs a different decision view.

Configure filters and parameters

Use filters and parameters to make one report reusable across sites, assets, and time ranges.

Common parameters:

• site;
• building;
• asset;
• system;
• time range;
• work-order status;
• quality status.

Preview the report with realistic parameter values before publishing.

Preview and publish

Before publishing:

• confirm dataset binding;
• confirm filters;
• preview every widget;
• review titles and units;
• check row-level detail for sensitive fields;
• record a change summary when making a meaningful update.

Publishing makes the report available to viewers with access.

Use version history

Use report versions when a published report changes.

Review versions before:

• changing dataset binding;
• removing widgets;
• changing filters;
• changing parameter names;
• replacing a report used by operations.

Restore a previous version when a report change breaks an operational workflow.

View and export

In the viewer, users can render the report with selected parameters.

Available export workflows may include:

• widget CSV export;
• report XLSX export;
• report PDF export.

Check the exported file before sending it outside the project team.

Schedule delivery

Use schedules when report output should be delivered on a recurring cadence.

Schedule fields include:

• report;
• schedule name;
• cron expression;
• timezone;
• format;
• recipients;
• enabled status.

After creating a schedule, use Run now to test it and review run history.

Embed a report

Embed tokens can provide a report URL with controlled lifetime and locked parameters.

Use embedding only after confirming:

• viewer scope;
• token lifetime;
• locked parameters;
• revocation process;
• data-sharing approval.

Review active, expired, and revoked tokens for each embedded report.

Troubleshooting

Symptom	Check
Report list is unavailable	bi.read and package access.
Designer is unavailable	bi.write.
Dataset is missing	Dataset BI access, dataset status, and tenant scope.
Widget is empty	Binding, filters, parameters, and source dataset freshness.
Export fails	Report render result, dataset query permissions, and file size.
Schedule fails	Recipients, schedule format, timezone, and schedule run history.

Next step

Use Dataset Lifecycle to keep datasets behind published reports reviewable.