Managing Non-Conformance Lists
Previous Topic  Next Topic 

Non-Conformances are issued when work in construction project fail to meet the required quality or there is a deviation in specification. Non-Conformances in SmartProject can be categorised to Non-Conformance – Quality and Non-Conformance – Safety.

Non-Conformances facility can be opened from the Modules option in the global menu. 

 

Figure: Opening from Global Menu

and from the Project.

 

Figure: Opening from Project

If Non-Conformances - Quality facility is opened from the Project, Non-Conformances-Quality List of the Project is displayed directly. In case Non-Conformances-Quality facility is opened from the Module options, the following window is displayed.

 

  1. Click the browse button to select a Project. List of Projects will be displayed. 
  2. Select a Project from the list.

Non-Conformances-Quality List window is displayed. In case already Non-Conformances-Quality are created for the Project, details of the Non-Conformances-Quality are displayed in the window.

Figure: Non-Conformance List window

Count of Total number of Non-Conformances and count of Non-Conformances with different statuses like Created, Open, Closed, Work In Progress, Completed and Canceled will be displayed in different tabs. On clicking a tab, the respective Non-Conformances List will be displayed. For Example: If the tab OPEN is clicked, list of Non-Conformances with status Open will be displayed.


Creating a Non-Conformance

Non-Conformance can be created only by a user with security permission to create a Non-Conformance.

To create a Non-Conformance

Fetching details from Non-Conformance group

If Non-Conformance groups are available against the project, it is possible to fetch the details associated with the group, only if the corresponding data field in window is empty. This helps to specifying details quickly. 

To fetch details from Non-Conformance group

Notifying Non-Conformance creation

When a Non-Conformance is created a single notification mail can be send to the concerned users.

To send notifications

Modifying Non-Conformance Details

Non-Conformance details of a Non-Conformance in CREATED status can be modified. 

To modify a Non-Conformance

Closing a Non-Conformance

A user who is authorised to close a Non-Conformance only can carry out this operation.

To close the Non-Conformance

Updating Non-Conformance status

During the lifecycle of a Non-Conformance, if some mistakes happen, user may need to reverse the status. For Example: When a Non-Conformance item is wrongly approved, wrongly updated with a rectification status etc.

To update Non-Conformance status

Approving a Non-Conformance

Only the ‘Approver’ assigned to a Non-Conformance may approve it. When other users attempt to approve the Non-Conformance a warning message is displayed, and the operation is aborted.

To approve a Non-Conformance

Removing a Non-Conformance

A Non-Conformance can be removed by authorised users. Creator of the Non-Conformance can remove the Non-Conformance before it is approved. Approver and Authorised to Close user can remove the Non-Conformance any time.

To remove a Non-Conformance

Operation Log

Operation log captures the following Non-Conformance operations.

  1. Creation
  2. Editing
  3. Removal
  4. Approval/ cancellation
  5. Completion
  6. Closure
  7. Updating Status

To view the operation log

Non-Conformance configuration and security settings

Several configurations are required to avail the Non-Conformance handling functionality. The administrators can use the Administrative Settings option available in the Non-Conformance main window to manage the configurations.

Creating Defect Categories

When reporting Non-Conformance, it is a common practice to categorise them based on the nature of defects. This helps in assigning the experts in rectifying the respective type of defects. Also, common practices for rectification can be defined, making the rectifications quicker.

To create defect categories

To create a sub category

Modifying defect categories

Defect categories created can be modified.

To modify a defect category

Removing defect categories

Defect Categories can be deleted. Only defect categories that are not in use can be removed.

To remove defect categories

Creating Non-Conformance groups

Groups helps to define a list of common types of Non-Conformance for which default set of characteristics values can be predefined. This will help to create Non-Conformance easily instead of specifying values for each Non-Conformance properties individually.  A group can be assigned to a Non-Conformance and the property values as defined for the group will be inherited by the Non-Conformance.

To create  Non-Conformance groups

Security Settings

Security defined here is applicable to both Users and  User Groups (Roles). Only users with security right can manage a snag.

To define security

Configuring Escalations and Notifications

Reminders and escalations can be configured for Non-Conformances.

To configure reminders and escalations

To configure a reminder

To configure an escalation

Managing Settings

User who creates the non-conformance is automatically assigned as the approver. But in some project sites, non-conformance created by a resource must be approved by another resource. Since both scenarios are required on site, a setting Assign creator as approver by default is available in the Settings tab of Non-Conformance Management Settings window.  If the checkbox next to this option is selected, creator is assigned as the approver by default. If the checkbox next to this option is not selected, user needs to select an approver.

Figure: Non-Conformance Settings

There are scenarios where a PMC user may raise a Snag, issue and NCR and assign it to the contractor user. The contractor user assigned to the Snag, Issue or NCR may need to reassign the Snag, Issue or NCR to the actual user in their team who will work on the objects to close it. Currently, this is not allowed. The assigned resource cannot reassign.Also, when the PMC has assigned one contractor user to a Snag, Issue and NCR, it cannot be changed. Hence if a wrong user is assigned, it cannot be rectified. This also needs modification.

As a solution to this, a setting to allow the user in “To be rectified by” field to assign work to another resource is available. 

If the checkbox next to the setting Allow "To be Rectified by" user to reassign is selected, resources assigned as To be Rectified by users will be able to reassign the issue.