Federated ACC Models and Views in Frame and Power BI

Why federated views matter in BIM reporting

Most BIM dashboards are built around a single model. That works for isolated analysis, but it stops short of how many projects are actually coordinated. Teams review architecture, structure, MEP, and specialist packages together in federated views because that is where coordination decisions happen.

If the dashboard only reflects one child model at a time, the reporting layer falls behind the real coordination workflow.

That is why we are releasing a beta workflow for federated views created in Autodesk Construction Cloud Model Coordination. With Frame, teams can now work directly with the same federated views they already build in ACC and bring them into Frame and Power BI without rebuilding that coordination logic somewhere else.

What is new in Frame

With this beta launch, Frame makes ACC federated views usable inside our reporting workflows. Instead of treating federation as an external step, we now support it directly as part of the dashboard experience.

That means your team can:

• Use the federated views prepared in ACC Model Coordination as the basis for analysis.
• Start from templates built specifically for federated model cases.
• Work with issues attached to those federated contexts instead of jumping back and forth between tools.
• Keep reports aligned with coordination activity through ACC Issues webhooks.

The goal is simple: if the team is coordinating in federated views inside ACC, your dashboard should be able to do the same.

Quick walkthrough

Here is a short walkthrough of the federated ACC workflow in Frame, including federated views from Model Coordination, issue location in context, and drill-through to child model detail pages in Power BI.

Why this changes the reporting workflow

Federated coordination is where teams usually answer the questions that matter:

• Which discipline is driving the issue?
• Which child model should be reviewed next?
• Where does the issue sit relative to the full project context?
• What does the team need to inspect in 3D versus in sheets?

Without federated support, dashboards can lose that context fast. Reports may show issue counts or model data, but the actual review still has to happen somewhere else.

By working from the ACC federated view itself, Frame keeps the analytical and visual context tied together. The user is no longer analyzing a simplified copy of the coordination environment. They are working with the same federated setup the BIM team already made in ACC.

Power BI dashboards built for federated models

We also designed our Power BI dashboards so federated workflows stay readable instead of becoming a mess of mixed data.

At the overview level, teams can review the federated context across all loaded models. But when a question requires deeper inspection, the report also makes it possible to drill through each child model.

That matters because federation is useful precisely because it combines models, but real investigation often needs to go back down to the model level.

Inside the report, this means you can:

• Start from the federated view and inspect the project in context.
• Drill through to the Assets Detail page for the specific child model you need to inspect.
• Separate one model’s data without losing the relationship to the federated coordination view.
• Keep a clear path from high-level coordination down to model-specific asset detail.

This gives teams a more practical review path inside Power BI. You can move from a federated coordination question to a model-level inspection step without rebuilding filters every time.

3D viewer and sheets across the federated setup

The viewer experience is also built around that same federated logic.

In the 3D viewer inside the Power BI report, users can see all models participating in the federated setup. This is important for cross-discipline inspection, especially when the issue only makes sense when multiple models are visible together.

At the same time, users can navigate to the 2D sheets corresponding to each model. That makes it easier to move between 3D coordination and the drawing context that teams often still need for review, communication, and sign-off.

This combination helps different stakeholders work the way they need:

• Coordinators can inspect the whole federated environment in 3D.
• Discipline leads can narrow the review to their own child model.
• Project teams can reference the corresponding sheets when a 2D explanation is easier to share.

Supporting issues directly in federated views

Issues are one of the most important reasons to support federated views properly.

On many projects, the issue is not meaningful in isolation. Its location only becomes clear when multiple models are shown together. If the dashboard strips away that federated context, the issue becomes harder to understand and harder to trust.

Frame works directly with the federated view from ACC, so issues can be displayed in the exact location where the team expects to review them. Instead of approximating the issue against a simplified model setup, we keep it anchored to the same federated coordination environment used in ACC Model Coordination.

That improves issue review in several ways:

• The issue can be inspected in the correct spatial context.
• Teams can see nearby systems from other models without manual setup.
• Reviewers spend less time reconstructing the location of the problem.
• Reporting remains aligned with how the issue was originally coordinated.

Keeping reports up to date with ACC Issues webhooks

Reporting around issues only works if the data stays current.

That is why we also support webhooks from ACC Issues, making it easier to keep federated dashboards updated as issue information changes. When teams are creating, updating, or closing issues in ACC, your reporting workflow does not need to fall behind and wait for a manual refresh cycle to catch up.

This is especially useful for:

• Ongoing coordination dashboards reviewed in weekly meetings.
• Management reports that track issue status over time.
• Federated workflows where issue movement needs to be reflected quickly.
• Teams trying to avoid stale reports that no longer match ACC.

In practice, it means your dashboard can remain much closer to the current state of coordination work happening in the CDE.

Where this beta fits best

This new workflow is especially valuable for teams already using ACC Model Coordination as their main review environment and who want their reporting to reflect that same setup.

It fits well when you need:

• Federated model review in Power BI.
• Better visibility into issues across multiple child models.
• Drill-through from federated context to model-specific detail.
• 3D and 2D review paths inside the same dashboard.
• A reporting layer that stays connected to ACC activity.

If your team already spends most of its coordination time inside federated views, this beta is the missing step that makes dashboards much more useful.

Final thought

Federated coordination should not stop at the viewer inside ACC. The same federated logic should flow into the dashboards your team uses to inspect issues, review models, and communicate progress.

With Frame’s beta support for ACC federated views, Power BI reports can now stay much closer to the way teams actually coordinate projects.

If you want to explore related workflows, see our ACC to Power BI integration guide and our custom Power BI viewer overview. If you want to discuss this workflow with your team, contact us.