eLearning is available for this topic. Check it out here: HxGN SDx® | Introduction to QA Review Workflow.
When a document is submitted to the system, you are assigned a review task or a consolidation task based on your review plan or the document review matrix. Select the task in your To Do List to review the document. If you cannot review the document, you can reassign the task to another user or waive the task.
Your system administrator may modify the workflow so that the steps differ from those
shown. The steps are still carried out using the procedures described below.
What is a Quality Assurance (QA) Review?
The Quality Assurance (QA) Review allows your company technical experts, engineers, and stakeholders to review documentation deliverables and other documentation during a project. The aim of the review process is to ensure that the correct information is delivered to the right people so they can efficiently perform Quality Assurance Reviews. The review results can then be efficiently communicated with the suppliers or contractors.
During a project, the suppliers or contractors deliver documents regularly at various stages, with different revision numbers, and issue purposes. Some documents are related to the design aspects of the project so are more critical than others, so the review is used to ensure that the most critical documentation receives the appropriate level of scrutiny.
When document revisions enter the system, they are evaluated to determine if a quality assurance review should be initiated. If so, then a review is triggered and notifications are sent to each of the reviewers. At the same time the review start date is set, the system calculates the due date based on the contractual agreement with the contractor.
Each reviewer can make markups, add review comments, add general comments, reassign the review task to another person, or waive a review. Review comments are observations made during the reviews that require additional follow up. The review comments are attached to a workflow to ensure that they receive the right level of follow up. Each review functions independently, so they can be performed concurrently without the visibility of other reviews. However, reviewers may see the comments and markups of all other completed reviews to help minimize duplication and promote discussion.
The number of days needed for the document review process includes the time needed for review, the consolidation of the results by the Consolidator, and to carry out a Contractual Compliance Review (CCR). Intermediate due dates are set as configurable workflow steps and can be used to shorten the deadline for document reviews. The overall review is not dependent upon the completion of individual reviews.
The Consolidator opens the documents and creates a consolidated layer that contains all approved comments to the contractor document. The Consolidator can also create a new consolidated marked up file of the marked up document. A consolidator can know the progress of all the reviews from the QA Document Review Consolidation page. Reviews that are in progress are shown as In Review and those not started are shown as Review not started against the corresponding reviewer.
After consolidation, the review is checked for compliance. The Contractual Compliance Review (CCR) is carried out prior to the commented documents being returned to the originating contractor.
What is the difference between primary and reference documents?
You can distinguish between the different documents that appear in a communication review or response:
-
Primary documents are the main subject of a review or response and require action, comment, or query.
-
Reference documents are included for reference or provide additional information to support a review or response, action, comment, or query.
What happens when a revised document is attached through the submittal workflow?
The QA Review Verification workflow handles the document revision attached through the submittal workflow and checks if the document revision has been reviewed at that issue purpose.
-
If the document revision has been reviewed at the same revision and issue purpose, the system sets the return code on the document to Acknowledged and exits the workflow.
-
If the document revision has not been reviewed at the same revision and issue purpose, the system directs this workflow to the next step.
-
-
The system checks if the issue purposes on the document are related to the current project.
-
If yes, the system directs this workflow to the QA Review workflow.
-
If no, the system does not allow the document revision to be submitted.
-