Time management & shift work

ATOSS plans the shift, Linetrack plans the order.

In ATOSS, your HR team keeps shift plans, time accounts and absences, with Time Control or the Staff Efficiency Suite. Linetrack needs one thing from all that: who is away on which day. Those absences reach the capacity planning of pre-assembly, final assembly and commissioning through the Linetrack REST API. The shift model itself is set once in the resource group's calendar in Linetrack and is not synchronised.

Via the REST APIAbsences with typeShift model in the Linetrack calendarMatched by employee number

ATOSS website ↗

In short

ATOSS is connected through the Linetrack REST API: a flow built on your ATOSS system's interface tools or on middleware such as Power Automate or n8n sends absences with type and share of the day to Linetrack, matched by employee number. New employees are created by the master data sync. Shift models and part-time are not transferred; they live in the resource and group calendars in Linetrack. There is no dedicated ATOSS connector.

What is transferred

Absences from ATOSS, the shift week from Linetrack

Two things decide a fitter's capacity: his working-time model and his absences. You set up the model once in Linetrack, and ATOSS keeps supplying the absences. Planning then works with the week the shop floor actually runs.

REST APIOngoing

Absences with type

Holiday, sickness, training, assembly and other arrive with start, end and share of the day. You decide once which absence reasons from ATOSS map to which type. Anything that fits no type goes under other.

  • Employee number
  • Start
  • End
  • Type
  • Share of day
  • Label

Endpoint: PUT /resources/absences/bulk

Kept separate

Shifts and part-time in the calendar

Two shifts in pre-assembly, a part-timer's four-day week, the early shift in the test bay: working-time models like these sit in the resource or group calendar in Linetrack. The sync does not touch them, and a shift swap in ATOSS moves no capacity in the project plan.

  • Company calendar
  • Group calendar
  • Resource calendar
  • Part-time
  • Shift week
Half days

Share of the day, not the whole day

Every absence carries a share of the day, from a fraction up to a full day. Half a day off takes half of a shift worker's capacity on that day, not all of it.

  • 1.0 = full day
  • 0.5 = half day
Master data

New employees by employee number

When a new mechatronics technician joins assembly, the master data sync creates him in Linetrack with employee number, initials and resource group. Existing records are updated, nothing is ever deleted, and new users only take free licences.

  • Employee number
  • Email
  • First name
  • Last name
  • Initials
  • Resource group

Endpoint: PUT /resources/users/bulk

Full state

One period, one complete state

For a given period, the flow sends every absence of the employees it delivers. Linetrack only replaces what came through the interface before. Entries a project manager set by hand stay put, and a holiday cancelled in ATOSS disappears with the next run.

  • Period from–to
  • Only API entries replaced
  • Manual entries stay
Planning

Where it shows up in planning

The resource view shows each day's load against the capacity that is left, the histogram in the Gantt shows the gap across the project's duration. If someone is away all day, their task carries a warning.

  • Resource view
  • Resource histogram
  • KPI dashboard
  • Warning on the task

From the shop floor

What changes in assembly and production

Two fitters missing on the late shift

In the pre-assembly of a packaging line, two fitters on the late shift call in sick and the shift lead records it in ATOSS. After the next run, the assembly manager sees the missing hours in the resource view. She decides whether the trial run before the FAT holds or whether people from final assembly help out.

Training before commissioning

Three electricians are booked in ATOSS for a two-day safety course, right in the week before commissioning at the customer's site. Because the training arrives with its type, the project manager sees the reason and talks to HR about another date before he reshuffles fitters.

Two shifts without replanning

In autumn, final assembly runs two shifts for two months. Production planning enters the longer week once as a period in the group calendar, and ATOSS keeps delivering only the absences. In the plan, final assembly's capacity rises for exactly those two months.

Setup

From ATOSS absences to the daily sync

  1. 1

    Map absence reasons

    With HR and the assembly manager, you decide which absence reasons from ATOSS arrive as holiday, sickness, training, assembly or other. Alternatively, choose the variant without a reason.

  2. 2

    Working-time models in Linetrack

    Shift weeks and part-time models are set up in the group or resource calendar. This happens once, and after that only when a model changes.

  3. 3

    Build the flow

    Your IT or your ATOSS partner reads the absences through your system's export and interface tools and sends them to Linetrack via Power Automate, n8n or a script. We are happy to work out with you which route fits your installation.

  4. 4

    Run it daily

    The run starts on a schedule, for example every night. Faulty entries such as an unknown employee number come back with a reason in the response and do not hold up the rest.

FAQ

Frequently asked questions

Any questions?

Book a call with our team.

Does Linetrack take over the shift plan from ATOSS?

No. Linetrack plans projects, not shifts. A person's or group's working time comes from the resource and group calendars in Linetrack; only the absences come from ATOSS. Who works which shift on which day stays in ATOSS.

Does it matter whether we use Time Control or the Staff Efficiency Suite?

Not to Linetrack: the REST API accepts the same data in both cases. What can differ is how the data leaves ATOSS. We clarify that with you and your IT partner based on your installation.

Where do company shutdowns and public holidays belong?

In the Linetrack company calendar. Closure days there apply to every group and resource and do not need to come from ATOSS as an absence per employee.

Are time accounts and flexitime balances transferred?

No. For capacity planning, what counts is on which days someone is away, not their balance. Time accounts, bonuses and payroll stay in ATOSS.

The platforms and brands mentioned belong to their respective owners. Mentioning them describes the technical connection and does not imply a partnership or certification.