Weed & Pest Management
This page contains only partial information. For more information on the usage of this module, please contact Datalink Service Desk.
Setting up a Weeds & Pest Management program in Crisisworks.
There are a few steps involved in configuring a Weeds & Pest Management event in Crisisworks:
- Allocate the 'Weed Inspections Coordinator' competency to those Crisisworks users administering the program
- Set up a new Organisations in Crisisworks for participating contractors.[1]
- Set up a new Resources in Crisisworks for each of the new contractors.[2]
- Set set up a new Crisisworks Event for the weeds program in Crisisworks. When creating the new Event, select the 'Weed Inspections' event template.[3]
- Once the Event is created, edit it and add the required contractor Resources (for example the ones created in step 2).[4]
- Create a new User account for each contractor. When creating the new User ensure that the Organisation is set to the one created in step 1 above and include the competency `Weed Inspections Contractor/Treater`.[5]
Setting up a new user account will trigger a 'welcome' email to be sent to the new user with instructions on how to set their password.
Reference help documents:
[2]: Managing Resources
Technical Reference
Main schema
| Field ID | Label | Form Type | Data Type | Values | Notes |
|---|---|---|---|---|---|
| weedName | Species | select | string(255) | ||
| weedNameOther | Name of Weed | text | string(255) | Only available if ‘weedName:/other/’ | |
| percentageCover | Percentage Cover | select | string(255) | ||
| identificationMedia | Assessment Photos | media | |||
| supportingInfo | Supporting Information | rte | clob | Any additional information relevant to this inspection. | |
| method | Treatment Method | select | string(255) | ||
| chemical | Chemical | select | string(255) | ||
| windDirection | Wind Direction | select | string(255) | ||
| windSpeed | Wind Speed (KPH) | select | string(255) | ||
| temperature | Temperature (°C) | select | string(255) | ||
| treatmentInfoPlaceholder | info | Read only | |||
| treatmentDate | Treatment Date | datePicker | timestamp | ||
| treatmentStartTime | Site Start Time | timePicker | Defaults to | ||
| treatmentEndTime | Site End Time | timePicker | |||
| treatmentCalculatedTotalTime | Calculated Treatment Time(hrs) | text | string(255) | This time is calculated automatically using the the above Treatment Start and End Times if set. | |
| treatmentManualTotalTime | Treatment Time Overide | number | integer | Use this field to manually enter the Treatment time in hours (ef 5.75). This will override the calculated time. | |
| treatmentMedia | Treatment Photos | media | |||
| details | Treatment Comment | rte | clob | Any additional information relevant to the treatment. | |
| assignee | Assessor Assignment | assignment | Single assignment to Users | ||
| assigneeTreatment | Treater Assignment | assignment | Single assignment to Users | ||
| activity | auditLog |
Non-schema fields
| Field ID | Label | Form Type | Data Type | Values | Notes |
|---|---|---|---|---|---|
| hasAsset | Asset | asset | Required; supports Road and Reserve; MDA94 projection used for geospatial assets | ||
| hasEvent | event | ||||
| hasMap | Infestation Location | geo | Uses MDA94 projection | ||
| hasStatus | Status | status | |||
| hasTags | tags |
Workflow
| Workflow ID | Label | Value | Next States | Initial State |
|---|---|---|---|---|
| NEW | Inspect | 1 | NEW, OPEN, COMPLETED, UNABLE, NOTREATMENT, CLOSED | ✓ |
| OPEN | Treatment Required | 2 | OPEN, STARTED, COMPLETED, UNABLE, NOTREATMENT | |
| STARTED | Treatment In Progress | 3 | STARTED, OPEN, COMPLETED, UNABLE, NOTREATMENT | |
| COMPLETED | Treated | 4 | COMPLETED, CLOSED | |
| UNABLE | Unable to Treat | 5 | UNABLE, OPEN, STARTED, CLOSED | |
| NOTREATMENT | No Treatment Required | 6 | NOTREATMENT, CLOSED, OPEN | |
| CLOSED | Closed | –2 | CLOSED, OPEN |