This glossary pins down what the words used in Terake mean in Terake, so that users and AI assistants that answer questions with the Terake API do not mix up similar terms. Each term gives the label you see in the English and the Estonian interface, a short definition, what it is often confused with, the most relevant guide and, where there is one, the name used in the Terake API. Coded values are given where the API stores a term as a number.
Work and working time
Completed work
A record of one piece of work done by a worker: start and end time, pause, worker, worktype and, where used, machine, implement, place of work, customer, project, cost center, materials and workunits. A work is running while it has no end time; running works are shown under Realtime info and finished works in the Detail view. Works are started and stopped in the mobile app or on the “Start work” page, and they are also created from a work schedule or task marked as done, from transports, by loading a file and by adding them by hand.
State: running while there is no end time; approved when a manager has approved it (see Approval).
Not to be confused with a task (planned work that is not done yet), a work schedule (planned working time) or a worktype (the name of the kind of work chosen for the work).
In the interface: “Completed work” (Estonian „Tehtud töö”); “Work record ID” (Estonian „Töökirje ID”). Guide: Detail view
API name: /api/workdones
Approval
Approving a finished work confirms it for worktime accounting: the Worktime table, Statistics, Period comparison and Report view count only approved works, and the other reports include unapproved works only with “Incl. not approved”. Works can be approved by the Administrator and the Power user, by the worker’s boss, by a project manager for their project’s works, by the Agronomist for field works linked to a crop year, and by an Approver for the workers ticked under “Approvable workers” on the “Roles” tab of the approver’s worker form. A worker can change their own work only until it is approved, and a work approved more than 30 days ago can be changed only by the Administrator and the Power user (field works also by the Agronomist).
Not to be confused with Roster approval, which turns work schedules into completed works (see Time tracking type); locking a calendar event (see Calendar event status); approving a maintenance. A running work cannot be approved.
In the interface: “Approval” (Estonian „Kinnitamine”); “Is approved” (Estonian „On kinnitatud”); “Approver” (Estonian „Kinnitaja”); “Approvable workers” (Estonian „Kinnitatavad”). Guide: Approval
API name: /api/workdones (the approval is part of the work)
Worktype
The name of the kind of work, for example ploughing or a meeting, chosen for works and tasks; the Estonian interface calls it „Töö nimi” (work name). Its settings decide the hourly rate, whether its time counts as worktime (“Excluded from worktime”) and towards fuel consumption (“Excluded from fuel consumption”), and which ARIB (PRIA) activity it matches. Worktypes are grouped by ticking “Is main work name” on a general worktype and selecting it as the “Main work name” of the others.
Not to be confused with the work record itself (Completed work) or the “Event subject” of a task. “Main work name” is a grouping of worktypes, not a separate kind of record.
In the interface: “Worktype” (Estonian „Töö nimi”); “Main work name” (Estonian „Üldine töö nimi”); “Is main work name” (Estonian „On üldine töö nimi”). Guide: Worktypes
API name: /api/worktypes
Workunit
A unit that measures the volume of work done, for example rooms cleaned, hectares sown or loads hauled. The amount is entered on the “Workunits” tab of the work form or the task form and is added up in the Workunits report, for example for piecework.
Not to be confused with the unit of a material (materials go on the “Material usage” tab) or the “Hectares served” of a field work.
In the interface: “Workunit” (Estonian „Tööühik”). Guide: Workunits
API name: /api/workunits
Time tracking type
A worker setting that decides where the worker’s worktime comes from: from measured works (started and stopped) or from the work schedule. For a worker counted by schedule, the “Approving” column shows “by schedule” instead of the approve button; such a work is approved after a schedule is selected in “Related schedule”, and works linked to the schedule get the cost center of the schedule row. Schedules become completed works on the “Roster approval” page with “Mark selected done”, or one at a time with “Save and mark done” on the event form.
Codes: 1 measured, 2 by schedule.
Not to be confused with approving works. Roster approval only creates completed works from schedules, and a schedule does not have to be locked to be marked as done.
In the interface: “Time tracking type” (Estonian „Ajaarvestuse tüüp”); “measured” (Estonian „mõõdetav”); “by schedule” (Estonian „graafikujärgne”); “Roster approval” (Estonian „Töögraafiku kinnitamine”). Guide: Roster approval
API name: /api/workers (a field of the worker), /api/rosteritems-for-approval (Roster approval)
Norm hours and overtime
Norm hours are the standard working time. The company setting “Norm work hours per day” is used to calculate the norm hours of a period (with the shortened days before public holidays) and to separate norm hours from overtime: in the Worktime table, “Day normhours” and “Day overtime” split each day (the brackets show the length of the standard working day and the hours counted as daily overtime, and anything beyond goes to “Excess time”), while “Period normhours”, “Period overtime” and “Period under-hours” sum up the period. Workers with summarised working time also get “Summarised normhours” and “Summarised overtime”, and only approved works count as actual worktime.
Not to be confused with the standard hours on the Roster timeline, which also take workload, vacations and sickness into account (“Not available” does not reduce them). The setting “Overtime hours per day” is also used by the automatic stop of works left running.
In the interface: “Norm work hours per day” (Estonian „Normtunde päevas”); “Overtime hours per day” (Estonian „Ületunde päevas”); “Day normhours” (Estonian „Päeva normtunnid”); “Day overtime” (Estonian „Päeva ületunnid”); “Excess time” (Estonian „Ülejäänud tunnid”); “Period normhours” (Estonian „Perioodi normtunnid”); “Period overtime” (Estonian „Perioodi ületunnid”); “Period under-hours” (Estonian „Perioodi alatunnid”). Guide: Worktime table
API name: /api/workdonehours (Worktime table)
Automatic stop and duration limit
Terake finishes works left running by itself. The auto stop process runs every 4 hours (00:22, 04:22 and so on) and finishes works started more than 24 hours ago with the duration of the schedule the work was started from, otherwise with the company’s norm hours plus overtime, otherwise at 24 hours; the log gets “Automatically stopped” (auto_stop), and “Undo automatic stop” (restart) if the phone later reports that the work is still going on. The work duration limit process works in real time: if the end time reported by the phone makes the work longer than 28 hours, the work is finished at 24 hours and the log gets “Limited duration automatically” (auto_limit_duration); this does not apply to worktypes marked “Excluded from worktime”.
Not to be confused with the automatic pauses set in Company settings, which are a separate process. Between two runs, Realtime info may show works lasting up to 28 hours; this is not an error.
In the interface: “Automatically stopped” (Estonian „Automaatselt lõpetatud”); “Limited duration automatically” (Estonian „Piiras kestust automaatselt”); “Undo automatic stop” (Estonian „Autom. lõpetamise tagasi võtmine”). Guide: Automatic processes that affect work duration
Overlapping and duplicate works
The duplicate work limit process finds overlapping works that were both started from the mobile app and sets the end time of the earlier work to the start time of the later one; the log of the work finished this way gets “Automatically stopped” (auto_stop). It first waits 8 hours for the actual end time to arrive from the phone, so Realtime info may show duplicates overlapping by up to 8 hours, and it does not touch works that were not started from the mobile app.
Not to be confused with the red mark “Overlapping (by time) works” in the Detail view, which only lists works of the same worker or machine at the same time for the manager to check.
In the interface: “Overlapping (by time) works” (Estonian „Ajaliselt kattuvad tööd”); “Automatically stopped” (Estonian „Automaatselt lõpetatud”). Guide: Automatic processes that affect work duration
Planning and roster
Task
Planned work for a worker at a given time, with worktype, place of work, machine, implement, project, customer, cost center, maintenance unit, planned materials and files as needed. Tasks are made on the Tasks, Planning and Roster timeline pages (event type “Task”) and also come from fieldwork plans, faults, maintenance and repairs; “Save and mark done” creates a completed work from the task. The Tasks report shows each task’s status and the actual duration and cost of the work done for it.
Status: 1 in progress (“Work in progress”), 2 finished (“Finished”), 3 unfinished (“Work is not finished”), 4 edited (“Task has been modified”), 5 rejected (“Task has been rejected”), 6 postponed (“Task has been postponed”), 7 blocked (“Task is blocked”). As a calendar event, a task has type 8.
Not to be confused with a completed work (what was actually done), a work schedule (planned working time) or a fieldwork plan (a crop year plan from which fields are added to the calendar as tasks). The menu item “Tasks” is „Ülesanded” in Estonian and the “Tasks report” is „Plaani aruanne”.
In the interface: “Task” (Estonian „Tööülesanne”); “Tasks” (Estonian „Ülesanded”); “Tasks report” (Estonian „Plaani aruanne”); “Task status” (Estonian „Ülesande staatus”). Guide: Tasks
API name: /api/todos, /api/planreport, /api/multiplan
Calendar event (roster entry)
Any entry on the Roster timeline or in My calendar: a work schedule, an absence or a task. Each event has an “Event type”, which cannot be changed after saving, and a “Calendar event status”; when several workers, places of work or machines are selected on a new event, a separate event is saved for each combination.
Event type: 1 Work schedule, 2 Vacation, 3 Sickness, 4 Not available, 8 Task, 11 work done, 14 Day off, 15 Study leave, 16 Parental leave, 17 Leave without pay, 18 Task / Teamwork, 19 Task / Group work.
Not to be confused with a completed work. Type 2 is called “unavailable” internally but is shown as “Vacation”; “Not available” in the interface is type 4.
In the interface: “Event type” (Estonian „Sündmuse tüüp”); “Calendar event status” (Estonian „Kalendri sündmuse olek”). Guide: Roster timeline
API name: /api/calendaritems/{resource_type}, /api/rostermain, /api/rosteritems-for-approval
Work schedule
A calendar event of type “Work schedule”: a worker’s planned working time on a day, with start, end and pauses and, if needed, shift, worktype, place of work and other details. It is made on the Roster timeline (a new schedule waits to be locked) or in the “Work schedule” table view (locked at once), and the worker sees locked schedules in the mobile app. Schedule hours are shown in the Worktime table as “Rost.” next to the actual “Work” hours.
Not to be confused with the menu item “Work schedule” (Estonian „Töögraafikud”), which is the table view for filling many workers and days at once, a shift (a reusable time pattern) or a completed work. A schedule becomes worktime only when it is marked as done.
In the interface: “Work schedule” (Estonian „Töögraafik”); “Roster timeline” (Estonian „Töögraafiku ajajoon”); “Rost.” (Estonian „Graaf.”). Guide: Roster timeline
API name: /api/calendaritems/{resource_type}, /api/rostermain
Absence
A calendar event that marks time off work: Vacation, Sickness, Not available, Day off, Study leave, Parental leave or Leave without pay; its form has only the dates and the worker. Workers can request “Vacation”, “Sickness” or “Not available” themselves in My calendar (“Not available” needs at least 5 characters of additional info), and the request waits to be locked. “Vacation” and “Sickness” reduce the worker’s standard hours and “Not available” does not; the Vacations page lists only vacations.
Event type: 2 Vacation, 3 Sickness, 4 Not available, 14 Day off, 15 Study leave, 16 Parental leave, 17 Leave without pay.
The internal type names do not match the labels: type 2 “unavailable” is Vacation, type 3 “emergency” is Sickness and type 4 “disabled” is Not available.
In the interface: “Absences” (Estonian „Puudumised”); “Vacation” (Estonian „Puhkus”); “Sickness” (Estonian „Haigus”); “Not available” (Estonian „Pole saadaval”); “Day off” (Estonian „Vaba päev”); “Study leave” (Estonian „Õppepuhkus”); “Parental leave” (Estonian „Vanemapuhkus”); “Leave without pay” (Estonian „Tasustamata puhkus”). Guide: Vacations
API name: /api/calendaritems/{resource_type}, /api/vacations (Vacations page)
Calendar event status: waiting and locked
The “Calendar event status” of a schedule, absence or task. “Waiting for verification” (Estonian „Ootab lukustamist”, waiting for lock) means that a worker took or entered the event, or that it was added on the timeline, and it now waits for a manager; it is drawn striped, and a new schedule in this status is not shown in the mobile app. “Locked” means a manager accepted it, for example with “Lock all pending events”; “Rejected” means the worker gave it up (“Abandon event”), and “Unassigned” means it has no worker and can be taken (“Take event”).
Codes: 2 taken = Waiting for verification, 3 assigned = Locked, 4 reopened = Rejected.
Not to be confused with approving works. Despite the English label “Waiting for verification”, this status is about locking the event. Locked does not mean approved, and a schedule does not have to be locked to be marked as done.
In the interface: “Waiting for verification” (Estonian „Ootab lukustamist”); “Locked” (Estonian „Lukus”); “Rejected” (Estonian „Tagasi lükatud”); “Unassigned” (Estonian „Määramata”); “Lock all pending events” (Estonian „Lukusta kõik ootel sündmused”). Guide: Roster timeline
API name: /api/calendaritems/{resource_type} (status of the event)
Team task and group task
Two event types of a task, chosen in the “Event type” field of the task form besides the plain “Task”. Like every event type, they cannot be changed after the task is saved; the help pages say nothing more about how they behave.
Event type: 18 Task / Teamwork, 19 Task / Group work.
Not to be confused with a worker group (a set of workers used to filter planning views) or a foreman’s brigade members.
In the interface: “Task / Teamwork” (Estonian „Tööülesanne / Tiimitöö”); “Task / Group work” (Estonian „Tööülesanne / Grupitöö”). Guide: Tasks
API name: /api/todos
Shift
A recurring worktime pattern, for example a morning or night shift, with start and end times, pauses and, if needed, a default worktype, place of work, machine, cost center and project. Selecting a shift on a work schedule fills in its times and pauses, and its other data when the entry has no worktype yet; a night shift may end on the next day.
Not to be confused with the work schedule itself (the event on a given day) or a worker group.
In the interface: “Shift” (Estonian „Vahetus”). Guide: Shifts
API name: /api/shifts
Project
A one-off undertaking limited in time and resources, which workers select when registering work and managers when planning. A project has a start and end time, optionally a customer, divisions, a project manager (who gets the “Project Manager” role automatically) and a cost center (for which Terake creates a cost center rule), and its forecast hours and budget are compared with planned, scheduled and actual hours.
Not to be confused with a workobject (a place), a customer or a cost center.
In the interface: “Project” (Estonian „Projekt”); “Project manager” (Estonian „Projektijuht”). Guide: Projects
API name: /api/projects
Machines and maintenance
Facility/Machine
An entry in the company’s register of machines, implements, equipment and other maintained units; the API calls it a facility. Ticks on the machine decide where it can be selected: “Main machine”, “Implement”, “Maintenance unit” (an object that work is done on, which may belong to a customer) and “Small tool”. The “Responsible person” answers for the machine administratively (papers, insurance, lending, stocktaking) and the “Responsible for maintenance” organises its maintenance and receives fault and maintenance notifications.
Not to be confused with a workobject (a place). A maintenance unit is a machine or piece of equipment being serviced, not the machine the work is done with; “maintenance unit” is also a workobject type.
In the interface: “Facility/Machine” (Estonian „Masin/Seade”); “Machines and equipment” (Estonian „Masinad ja seadmed”); “Maintenance unit” (Estonian „Hooldusüksus”); “Responsible person” (Estonian „Vastutav isik”); “Responsible for maintenance” (Estonian „Hoolduse eest vastutaja”). Guide: Machines and equipment
API name: /api/facilities
Main machine and implement
The two machine fields of a work. The main machine is the vehicle or machine the work is done with (the “Machine” card on the Start work page), and the implement is the implement behind it, for example a harrow or a trailer. A machine appears in these options only when “Main machine” or “Implement” is ticked on it; the Engine hours report and fuel balances are kept for main machines.
Not to be confused with the maintenance unit (the machine being serviced). The mobile app’s folder for implements is labelled „HAAGIS” (trailer) in Estonian.
In the interface: “Main machine” (Estonian „Põhimasin”); “Machine” (Estonian „Masin”); “Implement” (Estonian „Haakeriist”). Guide: Start work
API name: /api/facilities
Facility type
The classification of machines and equipment, for example tractor, truck or combine harvester; every machine must have one. It is used to group and filter machines, to link worktypes to suitable machines (worktype tab “Types of equipment”) and to set an “Inspection checklist for every use”.
Not to be confused with the “Main machine” and “Implement” ticks, which say how a machine is used, not what kind it is; material types and workobject types are separate lists.
In the interface: “Facility type” (Estonian „Seadme tüüp”); “Types of equipment” (Estonian „Masinate ja seadmete tüübid”). Guide: Types of equipment
API name: /api/facilitytypes
Engine hours
The engine’s running hours reading of a machine; it is kept together with the odometer reading in kilometres. Readings come from two sources: the start and end values entered with a work, and the telemetry service provider. The Period comparison report counts the difference entered with the work and falls back to telemetry when the entry is missing or faulty (start 0, end smaller than start, or 100 engine hours or more for one work).
Not to be confused with work hours (the duration of works). Engine hours are also a lifespan measurement for machine parts and a basis for service intervals.
In the interface: “Engine hours” (Estonian „Mototunnid”); “Odometer” (Estonian „Odomeeter”). Guide: Engine hours report
API name: /api/report/enginehours
Telemetry
Data that a machine’s telemetry device sends through an integration partner (for example Navirec, SkyFMS, John Deere, Wialon): location, engine hours, odometer, fuel level and other readings. The data is linked to a Terake machine by registration number, VIN code or “Integration key (reg.number without spaces)”, and movements longer than the machine’s “Min. duration for automatic work registration” are registered as work. Realtime info shows the readings in the Telemetry view and machine locations in the Map view (only machines with “Show in map” and a location less than two days old).
Not to be confused with worker locations, which come from the mobile app, or Realtime info as a whole, which lists the works in progress.
In the interface: “Telemetry” (Estonian „Telemeetria”); “Realtime info” (Estonian „Reaalaja info”); “Show in map” (Estonian „Näita kaardil”). Guide: Telemetry
API name: /api/location/facilities/last, /api/location/facilities/params
Refueling and fuel balance
A refueling is a record of fuel put into a machine (time, amount, machine, worker, fuel, fuel card, price and the balance before filling); refuelings come from the mobile app, filling station integrations, files or are added by hand. A fuel balance is the amount of fuel measured in the tank, entered on the “Refueling settings” page or taken from “Fuel balance in tank (before filling)”. Consumption between two balances is the previous balance minus the new one plus the amount refuelled (without AdBlue), and it is divided between the confirmed works of the period by engine hours, kilometres and duration.
Not to be confused with the “Refueling” report (a summary of refuelings). The “Refueling settings” page holds the fuel balances, not settings of the refuelings; worktypes marked “Excluded from fuel consumption” get no consumption.
In the interface: “Refueling” (Estonian „Tankimine”); “Fuel balance” (Estonian „Kütuse jääk”); “Refueling settings” (Estonian „Tankimise seaded”); “Fuel card” (Estonian „Kütusekaart”). Guide: Refuelings
API name: /api/fuelfillings, /api/fuelbalances/main
Fault
A registered problem of a machine, a piece of equipment or a workobject, reported on the web or in the mobile app, with fault time, reporter, description and severity (“Informative”, “Important” or “Critical”). Registering it notifies the reporter, the person responsible for maintenance and others, and creates a task for the person responsible for maintenance; an open “Important” or “Critical” fault colours the machine’s row red and an “Informative” one yellow. The fault status is “Registered” (no repair planned), “Planned” (has a repair), “In progress” (the repair has a task) or “Closed” (“Actual resolving time” filled in).
Not to be confused with the repair work that fixes it (see Repair work) or a maintenance. In Estonian the status “Closed” is „Lõpetatud”, the same word as a finished work.
In the interface: “Fault” (Estonian „Rike”); “Faults and problems” (Estonian „Rikked ja probleemid”); “Severity” (Estonian „Olulisus”); “Fault status” (Estonian „Rikke staatus”). Guide: Faults and problems
API name: /api/faults/facility
Maintenance
Regular planned servicing of a machine, a piece of equipment or a workobject, made according to a maintenance schedule and a service interval (engine hours, kilometres and/or days); the API calls it an inspection. A maintenance gets the tasks of its interval, is carried out by marking each task “OK” or “Not OK” and adding materials, and is then approved with “Approve inspection” (Administrator and Foreman). For machines Terake sends warnings when a maintenance is coming up and when it is due.
Not to be confused with a repair (work caused by a fault), the “Inspection checklist for every use” (a check before each use, set on the facility type or workobject type) or approving works. The “Maintenance” menu (Estonian „Hooldusmoodul”) is the whole maintenance module.
In the interface: “Maintenance” (Estonian „Hooldus”); “Service works” (Estonian „Hooldustööd”); “Service interval” (Estonian „Hooldusvälp”); “Maintenance schedules and checklist” (Estonian „Hoolduste graafikud ja tegevused”). Guide: Service works
API name: /api/inspections/facility, /api/inspection-cases, /api/inspection-type
Repair work
Work on a machine, a piece of equipment or a workobject that does not come from the maintenance schedule but from a fault or from a defect found during maintenance. It is created from a fault with “Repair planning”, from a maintenance with “Plan repair of items not in order”, or with “Add new”; its status is “Registered”, “Planned”, “In progress” or “Closed”. When all its tasks are “OK”, the “Actual resolving time” of the linked fault is filled in.
Not to be confused with the fault itself (the problem) or a maintenance (planned by schedule).
In the interface: “Repair works” (Estonian „Remonttööd”); “Repair status” (Estonian „Remondi staatus”); “Repair planning” (Estonian „Remondi planeerimine”); “Plan repair of items not in order” (Estonian „Planeeri veaga tegevuste remont”). Guide: Repair works
API name: /api/repairs/facility
Fields and crops
Workobject
A location or object where or on which work is done: a building, warehouse, construction site, address, maintained equipment and so on. It is chosen in the “Place of work” field of works and tasks, has a “Workobject type”, and can have an address, an area or line on the map, a region, a customer and the mark “Used as storage”. Fields are workobjects too, but they are managed in the field module and not shown in this list.
Not to be confused with a field (a workobject of the field type with crop years), a cadastre (a legal land unit) or a customer. The field label “Place of work” accepts both workobjects and fields.
In the interface: “Workobject” (Estonian „Tööobjekt”); “Place of work” (Estonian „Töökoht”); “Workobject type” (Estonian „Tööobjekti tüüp”). Guide: Workobjects
API name: /api/workobjectsonly
Field
A workobject of the field type, managed in the field module (“Field admin”) of agricultural companies. It has a block number (“Reg no”, Estonian „Massiiv”), a field number, a shape on the map, crop years and possibly a link to an e-PRIA field (“Pria link”); works done on it appear in its fieldbook. The English interface uses both “Field” and “Agrifield”.
Not to be confused with a cadastre (a cadastral unit of the land register, linked to fields) or a crop year (the field’s data for one year).
In the interface: “Field” (Estonian „Põld”); “Agrifield” (Estonian „Põld”); “Field admin” (Estonian „Põldude admin”); “Field number” (Estonian „Põllu nr”). Guide: Field admin
API name: /api/agrifield_data/{crop_period_id}
Cadastre
A cadastral unit of the land register, identified by a number in the form 12345:001:0010; “Import cadastral info” brings its data and boundary from the Estonian Land Board (Maa-amet). Cadastres are linked to fields, field agreements and workobjects to show which cadastral unit they concern.
Not to be confused with a field or a workobject: a cadastre is not chosen as the place of work.
In the interface: “Cadastres” (Estonian „Katastrid”); “Cadastre number” (Estonian „Katastrinumber”). Guide: Cadastres
API name: /api/cadastres
Crop
A crop grown on fields, used by crop years, crop rotation, the fieldbook, the fertilizing plan and the sending of yields to e-PRIA. A crop needs an “ARIB crop” (the matching e-PRIA crop) and a “Display color”, and may have a “Crop type for fertilizing plan”; the list contains both the company’s own crops and common Terake crops, which can only be archived.
Not to be confused with the variety (“Variety”, set on the crop year) or a seed material, which has its own “ARIB crop” field.
In the interface: “Crop” (Estonian „Kultuur”); “ARIB crop” (Estonian „PRIA kultuur”); “Variety” (Estonian „Sort”). Guide: Crops
API name: /api/crops
Crop year
A field’s data for one harvest year: crop year start, area, field usage, crop, variety, crop purpose, ARIB (PRIA) applicant and shape. Field works, materials, yields and the fertilizing plan belong to a crop year, and works sent to e-PRIA must fall between 1 July of the previous year and 9 February of the following year.
Not to be confused with a calendar year. The API calls it a crop period, and the Approval page speaks of a field’s “growing season” for the same thing.
In the interface: “Crop year” (Estonian „Saagiaasta”); “Crop years” (Estonian „Saagiaastad”); “Current crop year” (Estonian „Aktuaalne saagiaasta”). Guide: Crop rotation
API name: crop_period in paths, for example /api/agrifield_data/{crop_period_id}, /api/fieldbookfields/{crop_period_id}
Crop rotation
The table of each field’s crops by crop year, where the crop year data (crop, variety, field usage, crop purpose, ARIB applicant) is set for one field or for several fields at once. Below it, “Sowing area (ha)” sums up the area of each crop by crop year.
Not to be confused with fieldwork planning (plans of field work by worktype).
In the interface: “Crop rotation” (Estonian „Viljavaheldus”); “Sowing area (ha)” (Estonian „Külvipind (ha)”). Guide: Crop rotation
API name: /api/croprotation, /api/cropstats
Fieldbook
Terake’s electronic fieldbook: each field’s data by crop year, with area and crop, the works done on the field, the materials used, fertilizer NPK accounting, the fertilizing plan, soil samples and herding. It can be downloaded as an Excel file, and the ARIB employee role sees it read-only for the applicants, crop years and fields assigned to them.
Not to be confused with the e-PRIA fieldbook: works are sent there separately from the Activities page.
In the interface: “Fieldbook” (Estonian „Põlluraamat”); “Do not show in fieldbook” (Estonian „Ära näita põlluraamatus”). Guide: Fieldbook
API name: /api/fieldbookfields/{crop_period_id}
Fertilizing plan
A nutrient plan for one field and crop year, made on the “Fertilizing plan” tab of the field’s fieldbook; the field must have a crop in that crop year. From the planned yield, the nutrients need (nitrogen suggested from the soil samples’ organic carbon), manure applied and the previous year’s excess, it calculates the nutrients needed from fertilizers, shown as “N plan”, “P plan” and “K plan”.
Not to be confused with a fieldwork plan (which work is done on which fields) or Planned material usage (materials of planned tasks).
In the interface: “Fertilizing plan” (Estonian „Väetamisplaan”); “Nutrients plan” (Estonian „Toimeainete plaan”); “Planned yield (t/ha)” (Estonian „Planeeritud saagikus (t/ha)”). Guide: Fieldbook
Soil sample
A soil sample with its number, date, location and analysis results (pH, N, P, K, Ca, Mg, organic carbon, soil texture and more), entered by hand or loaded from a shapefile or Excel file. A sample is not linked to a field by hand: on saving it is linked to the crop years of the fields whose boundary contains its location, and it is then used by the fieldbook and the fertilizing plan.
In the interface: “Soil sample” (Estonian „Mullaproov”); “Soil samples” (Estonian „Mullaproovid”). Guide: Soil samples
API name: /api/soilsamples
ARIB (PRIA) and e-PRIA
PRIA is the Estonian Agricultural Registers and Information Board, shown as ARIB in the English interface, and e-PRIA is its online service. Terake imports fields from e-PRIA, sends works (Activities page), yields (Field admin) and grazing records (Herding) there, and imports activities from it; for this the user’s personal identification code must be confirmed by Terake, fields must be linked to e-PRIA fields, worktypes to a “Pria activity” and crops to an “ARIB crop”.
Not to be confused with the “ARIB employee” role, which is meant for PRIA staff doing supervision and sees only the fieldbook. The English interface mixes “ARIB” and “Pria” in labels.
In the interface: “ARIB” (Estonian „PRIA”); “Pria activity” (Estonian „Pria tegevus”); “Pria link” (Estonian „Pria seos”); “ARIB employee” (Estonian „PRIA töötaja”). Guide: Activities
API name: /api/priafiles (field import)
ARIB (PRIA) applicant
A person or company in whose name fields are declared to PRIA; the applicant is set on a field’s crop year. An applicant is linked to e-PRIA by “Pria id” or, failing that, by “Reg no”, and only works, grazing records and yields of fields whose applicant exists in e-PRIA can be sent there. From the applicant’s form Terake sends PRIA the confirmation that the applicant keeps an electronic fieldbook in Terake.
Not to be confused with a customer or the company itself. The API and some labels call the applicant a “payee”.
In the interface: “ARIB applicant” (Estonian „PRIA taotleja”); “ARIB applicants” (Estonian „PRIA taotlejad”); “ARIB payees” (Estonian „PRIA taotlejad”). Guide: ARIB applicants
API name: /api/priapayees
Materials and storage
Material and material usage
Anything used or produced in work: fertilizers, seeds, plant protection products, spare parts, harvests and other materials, each with a “Material type”, a unit and prices. Material usage is the amount of a material entered on the work’s “Material usage” tab together with the storage it was taken from; production is entered on the “Production” tab and only materials marked “Product” can be chosen there. The Material usage and Production reports add these up, and both reduce or increase the inventory of the selected storage.
Not to be confused with a workunit (volume of work, not a material) or the planned “Material consumption” of a task or fieldwork plan, which is a plan, not usage. In Estonian, “Material usage” appears both as „Materjalikasutus” and „Materjalikulud”.
In the interface: “Material” (Estonian „Materjal”); “Material usage” (Estonian „Materjalikasutus”); “Production” (Estonian „Toodang”); “Consumable” (Estonian „Kulumaterjal”); “Product” (Estonian „Toode”); “Material type” (Estonian „Materjali tüüp”). Guide: Materials
API name: /api/materials, /api/workdones/{wdid}/materialusages
Storage
A workobject or field ticked “Used as storage”. It is offered wherever a “Storage” is asked for: on a work’s material and production rows, when entering an inventory balance, and as the starting point or destination of a transport. Usage or production with no storage selected goes to the storage “Undefined”.
Not to be confused with the “Storage” menu (the storage module) or the device status “In storage” in the personal inventory.
In the interface: “Storage” (Estonian „Ladu”); “Used as storage” (Estonian „Kasutusel laona”); “Undefined” (Estonian „Määramata”). Guide: Workobjects
API name: /api/workobjectsonly (workobject with the storage mark)
Inventory (three meanings)
The English interface uses “Inventory” for three different things. “Inventar” is the personal page of machines and equipment a worker uses or is responsible for, with the device statuses “In storage”, “In use”, “Handing over” and “Disabled”. “Laoseis” is the stock balance of a material in a storage, entered with “Insert inventory balance” and then changed by material usage, production and transports; “Inventuur” is a stocktaking event, for example the responsible person confirming that a device exists.
These three are different things: ask which one is meant before answering a question about “Inventory”.
In the interface: “Inventory” (Estonian „Inventar”); “Inventory” (Estonian „Laoseis”); “Inventory” (Estonian „Inventuur”); “Insert inventory balance” (Estonian „Sisesta laoseis”). Guide: Inventory
API name: /api/inventory_owner, /api/inventory_user (personal inventory), /api/materials/{material_id}/inventory (stock balance)
Transport and transport of harvest
A transport is a record of material taken from a starting point to a destination, with amounts, number of loads and possibly a waybill; saving it also creates an approved completed work of zero duration for the worker, and a storage at either end changes its inventory. A transport from a field to a storage with a material of the silage type is a harvest transport (“Transport of harvest”): its material is set from the field’s crop year (“Saak <crop> <year>” or “Silo <destination> <year>”), amounts are in tonnes, and it is listed separately.
Not to be confused with the Transport module (Estonian „Vedude moodul”), which is for passenger transport companies: journey forms, routes and charter jobs.
In the interface: “Transport” (Estonian „Transport”); “Transport of harvest” (Estonian „Saagi vedu”); “Starting point” (Estonian „Lähtekoht”); “Destination” (Estonian „Sihtkoht”). Guide: Transport
API name: /api/transports, /api/silagetransports
Organisation, workers and rights
Company, customers and partners
The company is the Terake account itself, with its own workers and master data; a record shown with a grey @company name belongs to another company (a common Terake option or one shared by a partner) and can be used but not changed. A customer is someone the company does work for and can be selected on works, tasks, workobjects and machines. A partner is another Terake company that the company shares data with after an invitation: shared machines, workobjects and materials, and works the partner did, which can be viewed and given “Feedback” but not changed.
Not to be confused with an ARIB (PRIA) applicant or a division. The “External resource” row on the Roster timeline holds a partner’s workers.
In the interface: “Company” (Estonian „Ettevõte”); “Customers and partners” (Estonian „Kliendid ja partnerid”); “Customer” (Estonian „Klient”); “Partner” (Estonian „Partner”). Guide: Customers and partners
API name: /api/customers
Division / department
The company’s structure: top-level divisions (ticked “Is division”) and departments under them. Workers, machines, workobjects, customers, projects and shifts are linked to a division; a worker’s division applies from the “Modification date”, and a user who belongs to a division sees in options and many lists only the records of that division and its departments plus records with no division.
Not to be confused with a worker group (a free grouping for filtering views) or a region (a grouping of workobjects).
In the interface: “Division / department” (Estonian „Üksus / osakond”); “Departments” (Estonian „Üksused / osakonnad”); “Is division” (Estonian „On üksus”). Guide: Departments
API name: /api/departments
Worker group
A set of workers created with “Manage groups” and used to filter the Roster timeline, Work schedule, Planning, My calendar and Worktime table with “Show workers only in groups”. Pause rules in Company settings can also be set per worker group.
Not to be confused with a division / department, a foreman’s “Brigade members” or the task type “Task / Group work”.
In the interface: “Worker group” (Estonian „Töötaja grupp”); “Manage groups” (Estonian „Halda gruppe”); “Show workers only in groups” (Estonian „Näita töötajaid ainult nendes gruppides”). Guide: Roster timeline
API name: /api/worker_groups
Profession
A job title given to a worker in Worker settings, for information only: it is shown in the list of workers and, if chosen, under the worker’s name in planning tables. It applies from the “Modification date” and gives the worker no rights.
Not to be confused with a role, which is what gives rights.
In the interface: “Profession” (Estonian „Amet”); “Professions” (Estonian „Ametid”). Guide: Professions
API name: /api/professions
Cost center and cost center rules
A cost center is a division, activity or piece of equipment whose costs are collected separately; it can be set on works, projects, shifts and schedule rows, and reports and accounting exports split costs by it. A cost center rule gives a finished work with no cost center a cost center automatically when the rule’s conditions (worker, worktype, machine, place of work, project, crop) all match; the lower “Execution priority” number wins, a nightly check also covers the last 5 days, and an existing cost center is never changed. Selecting a cost center for a project creates a rule for that project automatically.
Not to be confused with a project or a division. The API calls a cost center a “cost account”.
In the interface: “Cost center” (Estonian „Kulukoht”); “Cost centers” (Estonian „Kulukohad”); “Cost center rules” (Estonian „Kulukoha reeglid”). Guide: Cost centers
API name: /api/costaccounts, /api/costaccountrules
Role
Roles decide which menu items a user sees and which data they can change; a worker’s roles are set on the “Roles” tab of the worker form, and the rights of several roles are combined. Every worker has “User”, which means using the mobile app, seeing one’s own data and changing one’s own works until they are approved; the other roles add, for example, viewing everything (“Observer”), approving (“Approver”), project work (“Project Manager”), giving roles (“Personnel”), field work (“Agronomist”), maintenance (“Vehicle service”), stock (“Stock management”) or system access (“Api (external IT system)”). Some rights do not come from roles: a boss’s rights over subordinates, the company setting “Users have by default create privilege”, and the rights of a machine’s responsible person.
Not to be confused with a profession (a job title with no rights) or the boss relation, which is not a role.
In the interface: “Roles” (Estonian „Rollid”); “User” (Estonian „Kasutaja”); “Observer” (Estonian „Vaatleja”); “Approver” (Estonian „Kinnitaja”); “Project Manager” (Estonian „Projektijuht”); “Power user” (Estonian „Power user”); “Personnel” (Estonian „Personal”); “Foreman” (Estonian „Brigadir”); “Agronomist” (Estonian „Agronoom”); “Accountant” (Estonian „Raamatupidaja”); “Dispatcher” (Estonian „Dispetšer”); “Vehicle service” (Estonian „Masinate hooldus”); “Stock management” (Estonian „Laohaldus”); “Self planner” (Estonian „Enda planeerija”); “ARIB employee” (Estonian „PRIA töötaja”); “Api (external IT system)” (Estonian „Api (väline IT-süsteem)”). Guide: Worker settings
API name: /api/workers (roles of the worker)
Administrator
The role that sees the “Admin” menu and can change everything in the company. Only the Administrator can add new workers, change other workers’ passwords and usernames, change Company settings and Integrations, use “Switch to user”, and change works approved more than 30 days ago (together with the Power user).
Not to be confused with the “Personnel” role, which sees only “Worker settings” under Admin but can give roles, including Administrator.
In the interface: “Administrator” (Estonian „Administraator”). Guide: Worker settings
Boss
The worker selected in the “Boss” field of another worker’s form; that other worker is then the boss’s subordinate. Being a boss is not a role: a boss can change the data and works of their subordinates, approve their works, change their schedules and tasks, and always see their calendar.
Not to be confused with an Approver (a role with workers ticked as approvable), a Foreman (who starts and stops works of brigade members) or a machine’s Responsible person. The help pages also say “manager” for the boss.
In the interface: “Boss” (Estonian „Ülemus”); “Subordinates” (Estonian „Alluvad”). Guide: Worker settings
API name: /api/workers (the "Boss" field of the worker)
Mobile app and integrations
Mobile app
The Terake app on the worker’s phone, in which workers start and stop works and record materials, workobjects covered, refuelings, transports, faults and customer signatures; Terake Worker is the app to use, in as new a version as possible. Works started from the mobile app are marked with a phone icon, which is red if the work was started or done farther away from the workobject; works of the Terake Lite app can only be viewed. The “Devices” tab of Company settings lists the phones and app versions in use.
Not to be confused with the “Start work” page in the web application, where work can also be started and stopped.
In the interface: “Start work” (Estonian „Alusta tööga”); “Terake Lite app works” (Estonian „Terake Lite äpi tööd”); “Mobile app folders” (Estonian „Kaustad mobiilis”). Guide: Start work
Apikey
A user’s personal key that lets other programs contact Terake on the user’s behalf; it is shown on My profile, where it can be copied or renewed. Renewing it stops the old key at once, so the user has to log in again in the mobile app and other sessions.
Not to be confused with the “Apikey” fields on the Integrations page, which hold keys given by integration partners (for example Navirec), or the “Api (external IT system)” role for a user through which another system exchanges data with Terake.
In the interface: “Apikey” (Estonian „Apikey”). Guide: My profile