Part of Terake’s work is done automatically on the server, without anyone pressing a button: work left running is stopped, data is loaded from partners, notifications are sent and summary data is refreshed. This page describes what these processes do and roughly how often they run.
The run times are approximate. The schedule may change and one run may take a while, so do not count on an exact time of day. If data has not been refreshed yet, wait for the next run. Times are Estonian time.
Work time
Stopping work left running. Work that has lasted more than a day without being stopped is stopped by Terake itself. If the work was started from a schedule, it gets the duration set in the schedule; otherwise the sum of the norm hours and overtime from the company’s working day settings, and if those are not set, 24 hours. “Automatically stopped” is added to the work’s log. The process runs several times a day, roughly every four hours, so “Realtime info” may meanwhile show work lasting up to 28 hours. The work duration limit and the duplicate work rules are described on Automatic processes that affect work duration.
Automatic breaks. If the company has working day rules, Terake adds the break the rules require to the workers’ unapproved work once a day, usually at night. The rule is chosen by the worker’s group, department or company and applied only when the working day is long enough for the rule. If the rule allows filling gaps, gaps of more than five minutes between pieces of work are closed first and that time counts as break. The last few days are checked again every night, so work that synchronised late gets its break as well. “auto_pause” is added to the work’s log.
Linking work to the schedule. A couple of times a day, in the morning and in the evening, Terake links unapproved work to the worker’s schedule entry that overlaps it by at least an hour. For a worker on schedule-based time tracking, the work takes the schedule’s start and end; for other workers the time stays as it is and only the link is added.
Cost center rules. Once a day, work of the last few days that has no cost center gets one from the first matching rule (see Cost center rules). A cost center already set is not changed.
Work time summaries. The breakdown of approved work into day, evening and night hours and the other hour types is calculated a few times a day. Because of this, the Worktime table and other work time reports may show newly approved work with a delay of a few hours.
Late data from the mobile app. If data arrives from the mobile app out of order, for example material usage before the work itself, Terake retries it every few hours for up to two days. The GPS track of finished work is usually added the next morning. Pictures attached to work also appear within a few minutes on the work’s machine, workobject, service case and fault.
Machines and telemetry
Loading telemetry data. Terake’s integration server polls the telemetry partners (for example Navirec, FleetComplete, SkyFMS, Mapon, Metrotec, Wialon) every few minutes, so machine positions, engine hours and mileage reach Terake almost in real time. History is loaded several times a day to fill gaps, and a longer history once a day, usually at night. The daily engine hours and mileage of each machine are stored in the machine’s readings history once a day.
Registering machine work from telemetry. If a machine has worked according to telemetry but nobody registered the work in the mobile app, Terake creates the work from it about once an hour. It waits until the machine work ended at least six hours ago, so that work from the mobile app can synchronise first, and skips the time already covered by work registered from the app. The work takes the worktype, worker and other details from the machine’s schedule entry; work without a schedule gets the generic worktype and a worker linked to the machine. Such work is unapproved and marked in the log as created automatically.
Telemetry readings of work. Once a day, in the morning, Terake fills the engine hours, mileage and fuel consumption of the last days’ work from telemetry data where they are empty, and stores the machine’s readings at the start and end of the work. The work’s track on the map is calculated by the integration server every few minutes.
Navirec area import. For a company that has switched it on, Navirec geofence areas are loaded as workobjects a few times a day. A shape edited in Terake is not overwritten by the Navirec shape.
Refueling and fuel
Loading refuelings from a partner. Refuelings from the fuel seller (Alexela) and the fuel dispenser (Piusi) are loaded once a day, usually early in the morning. The partner normally provides the previous day’s refuelings; some reach the partner’s system late and are therefore loaded a few days later. They appear on the Refuelings page.
Refueling work. For every refueling of the last month that has no work entry, Terake creates a zero-length “Refueling” work entry about once an hour, with the refueler, machine, location and readings. This work is approved automatically.
Fuel consumption. A couple of times a day Terake calculates the fuel consumption of the last three months: the first refueling of a day with a measured tank level becomes that day’s fuel balance, and the difference between two balances, together with the refuelings in between, is spread over the approved work by engine hours, mileage and duration. If work or refuelings in between are changed, the balance is recalculated. See Refueling settings.
Maintenance and notifications
Maintenance notifications. A couple of times a day, in the morning and in the afternoon, Terake checks the service cases. If the machine’s mileage, engine hours or planned date has passed the service limit, a “Maintenance needed” notification is sent; if the service is approaching within the alert limit set in the service type, a “Maintenance planned” notification is sent. The recipients are the machine’s responsible worker, storage worker, dispatchers and the case’s supervisor. Each notification is sent once per case.
Lifespan of wear parts. At the same time the lifespan of the machines’ wear parts is checked by mileage, engine hours or date. A part past the end of its lifespan gets a fault and a service case; a part past the warning limit gets a warning notification.
Calendar event reminders. A couple of times a day a reminder is sent for calendar events whose time is within the lead time set in the event type. Past events whose reminder has been sent are archived.
E-mails. Notifications that are also to be sent by e-mail are sent within a few minutes of being created. The same process sends fault notifications, about a minute after the fault is registered so that the reporter can add a description. Notifications older than two days are no longer e-mailed.
Field module
Plant protection monitoring. Once a day, usually at night, Terake creates a monitoring work entry at noon of the previous day for every field where plant protection work was done in the last month without prior monitoring. The work is assigned to the company’s agronomist, or the administrator if there is none, and is approved. The entry is meant to meet the e-PRIA fieldbook requirement.
Yield calculation. A few times a day Terake calculates the field’s yield from the amounts in tonnes recorded on combine harvesting work and writes it into the field’s fertilising plan as the real and wet yield. A real yield entered by hand is overwritten.
Crop year of fields. A couple of times a month the field’s main data (area, crop, PRIA payee, shape and so on) is brought in line with the crop year record in force on that day.
PRIA registers. Once a day, usually early in the morning, the e-PRIA classifiers (fertilising, liming, plant protection, monitoring and harvest types) are updated, the national fertiliser register is loaded into the shared list of fertilisers, and the current year’s e-PRIA crops that are still missing are added (archived). Cadastral boundaries are loaded from the Land Board once a day.
Tax and Customs Board (TTKI)
For a company that has taken the TTKI interface into use, the list of employees is reloaded once a day in the morning: new workers are created, valid access cards are added as identifiers and invalid ones are archived. A little later the construction sites are loaded: each site is linked to an existing workobject, the employers in the chain become partners and the site is shared with them. No new workobjects are created. See Integrations.
Accounting
Data exchange with Directo takes place during the working day about every quarter of an hour; no data is exchanged at night.
Deleting data
Deleted company. When a company has been deleted, its users receive a warning by e-mail a few days before the final deletion. After the deletion date the company’s data is removed by a nightly process and the users can no longer log in.
Recycle bin. Once a day, at night, records that have been in the recycle bin for about half a year are removed for good; fields and field groups after about a year. Before that a record can be restored. Cost center rules whose machine, worktype or other condition has been archived are archived as well.
Files. Export files created from reports and lists (Excel, PDF) are deleted after about two weeks; create the file again if needed.
Stock
The stock at the beginning of each month and the current stock of materials are recalculated from the movements once a day at night, and corrected every few hours when movements have been changed. See Materials.