The “Faults and problems” page is where faults of machines, equipment and work objects are registered and followed: who reported the fault, how serious it is, whether a repair is planned and when the fault was repaired. Employees can also report faults in the mobile app; they arrive in the same list.
Page layout
- The buttons “Machines and equipment” and “Workobjects” choose whether the list shows faults of machines or of work objects.
- Filters: “Filter department”, “Worker” (the fault reporter or the person responsible for maintenance), “Facility/Machine” (the work object for work objects) and the period. The list shows faults that started in the period and earlier faults that are not repaired yet. Press “Show”.
- Columns: “ID”, “Fault time”, “Faulty item”, “Severity”, “Fault reporter”, “Fault description”, “Planned start” and “Planned end” (from the fault’s repair), “Actual resolving time”, “Repairer notes” and “Fault status”. Among the hidden columns you can switch on “Worktype”; if the company has extra fields for faults, they are columns too.
- Click a row in the list to open the fault.
“Severity” is “Informative”, “Important” or “Critical”. “Fault status” is:
- “Registered”: no repair is planned for the fault;
- “Planned”: the fault has a repair work;
- “In progress”: the fault’s repair has a task;
- “Closed”: the fault has an “Actual resolving time”.
How to register a fault
- Press “Add new”.
- Fill in “Fault time” and “Class” (“Facility/Machine” or “Workobject”), select the faulty machine or work object, and fill in “Fault reporter” and “Severity”.
- Describe the fault in “Fault description”. If needed, select the “Worktype”.
- Press “Save”. After that you can add files, for example photos.
An e-mail notification about a new fault is sent to the fault reporter, to the person responsible for the faulty item’s maintenance, to those who have planned work with this machine in the next 24 hours, and for a machine also to the machine’s responsible person and employees with the role “Dispatcher”. A task about the fault is created for the person responsible for maintenance.
How to plan a repair
- Open a saved fault.
- In the block “Repair planning”, press the button “Repair planning”. A repair work window opens with the faulty item and the fault description already filled in.
- Select the “Responsible person”, “Planned start” and “Planned end” and save.
After saving, the repair number, planned time and responsible person are shown in the fault window. The repair’s tasks, assignments and materials are managed on the page Repair works.
How to close a fault
In the fault window, in the block “Fault closing”, fill in “Actual resolving time” and, if needed, “Repairer notes”, and save. “Actual resolving time” is also filled in automatically when all tasks of the related repair are marked “OK” or when the work of the fault’s task is finished. If the repair task of the fault has been given to a partner, “Actual resolving time” is set to the moment the partner marks the task done, not to the planned end of the repair.
How faults affect the list of machines
Open faults colour the machine’s row on the page Machines and equipment: an “Important” or “Critical” fault red and an “Informative” one yellow. All faults of one machine are on the “Faults and problems” tab of the machine window.
Tips
- When you delete a fault, Terake shows before you confirm what will happen to the fault’s tasks and repair. Completed work records remain.
- If the fault was reported in the mobile app and the location was known, the fault window shows in the block “Location in map” where the fault was reported.
API calls on this page
For integrations and AI assistants: this page uses the following Terake API calls. The full description is in the API reference.
When the page opens:
PUT /api/appsettings/{key}– Saves one application setting by keyGET /api/faults/facility– Faultitem collection of facilities
Other calls from this screen’s dialogs and actions:
DELETE /api/faultitems/{id}– Delete Faultitem by IDDELETE /api/repair-cases/{id}– Delete InspectionCase by ID or UUIDGET /api/faultitems/{id}/delete-preview– What deleting a Faultitem takes with itGET /api/faultitems/{id}– Faultitem by IDGET /api/faultitems– Faultitem collectionGET /api/faults/facility/{faultitem_consumer_id}– Faultitem collection of one facilityGET /api/faults/workobject/{faultitem_consumer_id}– Faultitem collection of one work objectGET /api/faults/workobject– Faultitem collection of work objectsGET /api/repair-cases/{id}– InspectionCase by ID or UUIDGET /api/integration-faults– Gobus fault messagesPOST /api/faultitems– Create new FaultitemPOST /api/repair-cases– Create new InspectionCasePUT /api/repair-cases/{id}– Modifies InspectionCase

