Keep the views your project needs.
Create, organize and return to useful project views. Give your team a consistent starting point for recurring reviews and communication.
Recurring model reviews need a shared starting point: the relevant area, discipline and model context for the discussion.
Saved project views are an application workflow within the xeoVision framework, using xeokit SDK for visualization. Organize useful perspectives around the topics your team needs to revisit, and return to them when the review continues.
Combine a federated model view with object filtering to focus the conversation. Agree how saved views fit the project’s review process; a saved view provides model context, not an approval record or a replacement for your issue-management system.
How it works
- 01 Set up a view around the topic you want to discuss.
- 02 Save and organize it within the project.
- 03 Return to the relevant view when the conversation continues.
What does a saved project view contain?
The model context a review needs to start from: the models that are loaded, the selection and the viewpoint. It is an application workflow built on xeokit SDK, so the view is kept alongside the project rather than in a separate tool.
Is a saved view an approval record?
No. A saved view records model context, not a decision. It is not an approval record and it does not replace an issue-management or quality-assurance system; those stay separate, and can be connected through integration work if your process needs it.
Why keep views instead of rebuilding them each time?
Because a recurring review that starts from a different state each time spends its first minutes re-establishing context. A saved view gives everyone the same starting point, so the discussion begins with the question rather than with the navigation.
