Page tree
Skip to end of metadata
Go to start of metadata

Before using the iTWOcx Quality Module, you will need to configure/confirm the following form options.

  • Confirm the layout of the quality forms is suitable to the project
  • Confirm the authors of the quality forms
  • Confirm statuses and status allocations
  • Confirm the closers of the documents
  • Configure the project specific data for each of the forms.

General Configuration

When setting up the Quality forms, consideration should be given to whether any changes to default settings are required for the following:

Authors:  Who can create this document?

Numbering: Do you want sequential numbering or do you require any special fields to display?

Title and Due Date:  Who can edit these on a submitted document.

Closers & Status changes:  Depending on the workflow of Quality on the project who is allowed to change the status of a document.  Particular consideration should be given to closers.

Statuses

Statuses help to define the workflow of iTWOcx forms.  Default statuses are set for each QA Form type, however, these can be configured to reflect the quality workflow on your project.

Consideration should be given to Status options and who has access to each of them. 

User Fields

The Quality forms contain a number of user fields.  Some of these fields appear on all of the forms.  Where select or cascading fields appear on multiple forms, the options must be added to each one.

To learn more about adding user field options, click here.

ITP Form

The default layout for the ITP is shown below. 

It contains a number of text user fields and a select field for Construction Process.

Options for Construction Process will need to be added to support project workflow.  This field also appears on other QA forms and as such, options must be added to all forms.

The ITP also contains a table for tasks.  Tasks are populated by text user fields for the following items:

  • Item No;
  • Task, Frequency
  • Applicable Standard
  • Method, Acceptance Criteria
  • Action
  • Responsibility.

Options may vary to those shown above where project customisation has occurred.

Lot Form

The default layout for the LOT is shown below. 

The LOT contains two main sections;

  • Lot Specification information; and
  • ITP information which is populated directly from the ITP when splitting.

The default user fields relating to Lot information are shown below:

  • Zone;
  • WBS (Work breakdown Structure)
  • Discipline
  • Chainage From/To
  • Location details.

These options can be modified to support project workflow.  The ones shown below are select fields and will require project options added.  Where these fields are on other forms, the options will need to be added to each.

Action Point

The default layout for the Action Point is shown below. 

 

The Action Point is used to manage Hold Points, Inspection Points and Witness points.  The user field for Record type is used to make your selection.

The form itself contains fields that are prepopulated from the ITP and the LOT.  Where select or cascading options are added on these forms this must also be added to the Action.

The Schedule Section uses date select fields to add time and date information.  These are set by default and no additional configuration is required to this section.

Survey Request

The default layout for the Survey Request is shown below. 

The Survey Request form contains a user field for Survey Type.  Edit the field options to customise options relevant to your project.

The form also contains fields that are prepopulated from the ITP and the LOT.  Where select or cascading options are added on these forms these must also be added to the Survey Request.

The Schedule Section uses date select fields to add time and date information.  No additional configuration is required for this section.

Test Request

The default layout for the Test Request is shown below. 

 

The Test Request contains 3 sections;

  • ITP and Lot details;
  • Test Request Details; and
  • Test Schedule.

The ITP and Lot section will populate from the Lot form. Where select or cascading options are added on these forms these must also be added to the Test Request.

The Test Request section has a number of text user fields and also contains a TEST TYPE which will need to have options added to make it project specific.

The Schedule Section uses date select fields to add time and date information.  No additional configuration is required for this section.

Nonconformance Report

As with all QA documents, the NCR contains user fields populated from the Lot.  All select and cascading field options must be added the NCR form.

 

The NCR has sections that display options detailing the Nonconformance, the Proposed Action and the cause.  Default options are available but may need customisation for use on your project. 

 

 

  • No labels