The Review Editor: Overview

How to navigate the Review Editor and make most use of its features

Written by Breno Glennon
Updated over a week ago

Navigating the Review Editor interface

The Review Editor is your point of call when a new model iteration is supplied.

It allows users to:

  • (Re)View 3D models/variants - drafts and final outcomes - in 3D and AR

  • Leave feedback and comments - generic or specific to an area of the model in 3D

  • Understand model performance based on the use cases selected

  • Approve and upload final models into PLATTAR

Let's cover the user interface and the various interaction features in detail:

Brief & Model Information

At the top of the Review Editor screen, you see important model information displayed, including a dropdown which defaults to the latest version of the model available in PIPELINE and enables to you to go back anre/view previous versions if needed. From here, you can also access the original brief for easy reference to both the Requester and the 3D modeler.

Please note that if you select a previous version of a model, all resolved and unresolved comments that were raised whilst feedback rounds occurred will be displayed in the messaging system on the right-hand side panel.

Review Editor (The 3D review panel)

On the left of your screen is the 3D review panel. We will cover the workings and all its features in a separate article.

Model Performance

PIPELINE features an inbuilt model performance assessment that captures, assesses, and ranks a model's performance attributes across anumber of metrics. This presents the requester and creator with an overall model performance score and suggestions on how to optimise performance and/or alerts on how to improve model performance for the target use case. Model Performance is displayed by default, but will be replaced with other relevant information when the user chooses the upload feature.

These alerts and suggestions are displayed at the bottom of model attributes and their corresponding values. These are generally directed towards the 3D modeler and should be incorporated and/or resolved in future model uploads for this job.

That said, it is good practise for Requester and/or Quality Control to keep an eye on these alerts to ensure improvement suggestions are implemented where feasible.

Review Complete

Once the Requester/QA has completed the review (ie. all model feedback has been captured via comment and annotations (see All Features Explained), the Requester/QA must confirm feedback to the modeler is complete by selecting the "Review Complete" button. The modeler will receive notification of the status change and will commence reviewing and incorporating feedback in the next round of modelling. Our modelling team will use the Commenting System if modelers need further clarification on feedback/comments provided.

Model Approval

The process of Model Upload > Requester Feedback > Model iteration repeats until:

  1. the QA/Requester is satisfied with the final outcome OR

  2. the maximum amount of model iterations (generally a max. of two rounds) is reached and the latest model version is uploaded and considered final unless additional agreements are put into place between the Requester and the PLATTAR Team.

Once the model has reached a 'Final' stage described above, QA and Requesters can approve the 3D content via the 'Approve Model' button found on the right of the interface.

NOTE: If Quality Control (QA) is part of the folder/project, QA needs to approve the final model outcome (=Solution) first. This will then trigger a notification for the Requester to perform a last review/check and give final approval as the model owner.

Brief/Job Complete

Once the Requester approves the model, the brief/project is considered complete and the final version of the model is ready for export to PLATTAR (more information found on 'Upload Content to Plattar'). Once approved, the stage column will be marked as ‘Complete’ under the 'My Briefs' view.

Let's explain all features available to the reviewer in the Review Editor!

Did this answer your question?