Maintenance
Here you can configure activities, categories, checklists, priorities, symptoms, and task outcomes.
Activities
Here activities can be created. Each task can be used in a checklist and a work order. The task has a code and a description.
Task outcomes
In a workorder, an activity can be followed up, and the outcomes listed here can be selected. Common outcomes include “OK,” “NOK,” and “Action Required.”
For each outcome, a code and name can be specified.
Categories
Here you can define categories, which can appear as a field in a request or workorder. Common categories are, for example, “Electrical” or “Pneumatic.” These can be used in a request or workorder for additional information or for KPI purposes.
For each catrgory, a code and name can be specified.
Checklists
Hier is de Engelse vertaling van jouw tekst, inclusief jouw vaste voorkeuren (workorder, Requests, Activities) en in een duidelijke handleidingstijl:
Checklists
A checklist is used, for example, to manage preventive maintenance or periodic inspections.
In essence, a checklist is nothing more than: “every x number of days/weeks/months/years I want to do this on these objects.”
A checklist contains a number of essential fields:
| Field name | Description |
|---|---|
| Code | Enter the unique code of the checklist. This can also be generated automatically as a sequential number. |
| Name | Provide a short description of the checklist. This will also become the description of each workorder. For example: “Annual forklift inspection.” |
| Automatic processing | Indicate whether the checklist should be processed automatically. If set to automatic, once the planning zone is reached (e.g., 2 weeks before the interval), the planning line is automatically converted into a workorder. If not automatic, the user must manually approve it. |
| Type | Choose between date-based or meter-based triggering. If meter-based is selected, a meter must be available to retrieve the current meter reading. |
| Planning | There are three options: 1. One-time: the checklist is scheduled once on a specific date as a workorder. 2. Execution-based: ControlOffice uses the execution date of the previous workorder from the checklist to set the new planned date. This means “Execution date of the previous workorder” + “Interval” becomes the new planned date. 3. Scheduled: a fixed schedule is set, for example every workday, weekly on Monday and Wednesday, monthly on the third Monday, or yearly on January 1 or the first Monday of January. |
| Planning zone | Define the planning zone, which acts as a warning period. This can be used to indicate preparation time. Based on this zone, notifications can be sent to remind you to start preparations (e.g., reserving/ordering parts, arranging downtime, etc.). |
| Reminder message | Specify the reminder message to be displayed when the checklist enters the planning zone (e.g., reserve/order parts, arrange downtime, etc.). |
| Information passed to workorder | Enter the information that will be transferred to each workorder created at each interval from the checklist, for example the type, responsible person, and priority. |
Tabs in the Checklist
In addition to the fields above, several tabs can be filled in, and their contents will also be transferred to each workorder. This way, each workorder generated at the set interval can be fully prepared in advance, minimizing the amount of work needed during the week to set up preventive or periodic maintenance.
| Tab name | Description |
|---|---|
| Activities | Enter the activities that must be carried out at each interval. |
| Parts | Specify the parts you expect to use. |
| Employees | Indicate which employees will work on it. |
| Tools | Specify the tools needed. |
| Attachments | Add attachments; these will also be transferred to each workorder created at each interval. |
| Planning | Specify the objects to which this checklist applies. |
| Objects | Add any additional objects if needed. |
| Forms | Specify any forms that need to be included with each workorder. |
| Form groups | A form group can be added here. For each workorder generated from this checklist, a new form from the selected form group will automatically be added. |
The fields that can be completed in the checklist and the tabs that are visible are fully customizable by the user through the “Configure input screens” function.
For each unique checklist-object link created via the “Planning” tab, one planning line will be generated in “Planning by date” or “Planning by meter”, depending on the type of triggering defined in the checklist.
From these two menus, the triggering of the checklist can be managed.
Priorities
Priorities can be managed here. A priority appears in a request and a workorder.
Each priority has a code and name, and it can be determined whether it should be set as the default for new requests or workorders.
Symptoms
Here you can define symptoms, for example “Electrical Issue” or “Water Damage.”
Symptoms can be used in a request or workorder. For each objectgroup, it must be indicated which symptoms apply to the objects in that group. This allows the user to see an accurate set of symptoms when filling in a request or workorder that describe the problem. Symptoms can replace the description of a request or workorder to ensure consistency.