ACC // Needs a unified Model Viewing user experience

[Chad-Smith]

This idea covers the general lack of design consistency across the Model Viewing experiences in the Files, Design Collaboration, and Model Coordination UIs. Whether it is true or not, it presents to the user as a disorganised development process in which the left is not talking with the right.

These are mostly surface-level items that should be easily addressed for a more unified UX.

The numbers match with the screenshots below.

1. Levels
   1. Found in multiple places on the UI.
   2. Should be on the toolbar, not as a left tab, for the same reason as explained for the Model Browser. And same for Phases.
   3. Has completely different icons.
2. Model Browser
   1. Should be on the toolbar, not as a left tab, as explained in detail in this Idea.
   2. Has completely different icons.
3. Issues
   1. Multiple experiences for Issue creation.
4. Compare
   1. Different emphasis on icons.
5. Lower Toolbar
   1. Why are there different toolbar colours?
   2. Some of the icons are different between UIs.
6. Button Order
   1. There are multiple buttons in different orders on the toolbar.
7. Full Screen
   1. Why does Design Collaboration not have a Full Screen option?

FILES (i.e. DOCUMENT MANAGEMENT)

This covers viewing in Docs, and where the same Files are shown in other modules such as Build.

DESIGN COLLABORATION

MODEL COORDINATION

[allan.stableford]

Another well thought out and clearly explained idea @Chad-Smith. Totally agree with the suggestion. I too have found it frustrating, especially when training others. 

Thanks again for persisting in creating these ideas.

[Chad-Smith]

An addition.

2. Model Browser - Is missing from Design Collaboration.

8. Colour Theming - Is missing from Files and Model Coordination.

[Chad-Smith]

Adding a related Idea.

Model Browser // Consolidate Model Browser + Levels + Phases

[Chad-Smith]

Adding the following additional justification for UI unification.

We know that the DC and MC modules perform different tasks. But the problem is that they perform these different tasks using different model data.

• In DC, the model data is in the Project Model, which represents all elements in that file. You might end up viewing more elements than the author intended.
• In MC, the model data is in a model View, which represents a subset of elements in that file. You might end up missing elements if the author forgot to include them in the view.

This poses a problem to the user who may interpret the model slightly different depending on whether they are viewing in DC or MC.

If the UI was unified, then we should (in theory) be viewing the model with the greatest level of consistency.

It's the use of Published Views that introduces this issue. The issue simply does not exist with legacy file sharing methods where you always received all elements that the author left in the model.