The Gridsz Contractor module allows contractors to add more depth to the outTasks that they receive from Gridsz. This module expands the task tree with mainTasks and subTasks, where the contractor can detail its work that is required to eventually complete the outTask(s). To automate the workflow for the contractor, templates can be setup to automatically add main- and subTasks to an outTask, If This Then That actions can be configured to remove manual labor, material lists and hourly job prices can be imported to track material and hours spend for a given main or subTask. Checklists can also be configured to ensure all steps and tasks are performed before completing the main task.

Templates

For each outTask a template can be defined that either automatically or manually adds the required main- and subTasks to that outTask(s).

Checklists

Checklists can be setup to define task checklist questions and also allow checks on the LMRA (Last Minute Risk Assessment) that can be carried out by the field engineer performing the tasks.

Attachments

Main- and subTasks can have required or addtional (optional) attachments that need to be uploaded by the field engineer. A distinction can be made for required attachments, which need to adhere to a specific file name in order to be uploaded. Additional files do not validate on the file name and such attachments can be uploaded as desired by the user.

Reason codes

Contractor main- and subTasks can contain specific reason codes for in-house use by the contractor to detail a certain reason or piece of information important to the task and its status. This reason code is filled separately and therefore can be used to filter, manage and check the status of tasks in more detail.

Labels

Labels are available for outTasks (private labels and ‘normal’ labels) as well as for the main- and subTasks. Labels allow the user to add additional information which is structured and easily filterable and searchable. Labels used in main- and subTasks are always seen as private and are only usable and visable for the Contractor party. For the outTask the user can have the option for normal labels, which are dicated by the PO and synchronise with the inTask of the AO. While private labels on outTask are only visible to the contractor party and the PO, these labels are not synchronised with the inTask and can also be dictated/managed by the contractor party itself.

Material List

Material lists can be uploaded to feed Gridsz Contractor with information on what material can be used, the code associated with the material, the unit that applies and the unit price for every item. The Material List dashboard showcases the current overview of the materials available (uploaded). The Material List history showcases all the changes that are applied throughout time for every Material List that is uploaded.

Work Pricing

Work Pricing can be uploaded to feed Gridsz with the hour labour rates that are required to complete all tasks. The information uploaded contains the code of the hour labour rate, a description of the hourly labour and the hourly price associated with that labour or job.