Time management

From Interflex time management, only what project planning needs.

In Interflex, time recording and access control can run on the same platform, IF-6040. For Linetrack only time management matters, and within it only the absences of the people who are planned in projects: mechanical design, electrical, assembly, commissioning. Doors, zones and visitors stay where they belong.

Via the REST APITime data only, no access controlSelected groups onlyVariant without absence reason

Interflex website ↗

In short

Interflex is connected through the Linetrack REST API. A flow reads absences from Interflex time management and sends them to Linetrack with type, or privacy-compliant without a reason, matched by employee number. Only the employees planned in Linetrack are transferred; access control data does not go to Linetrack. There is no dedicated Interflex connector; your IT or IT partner sets up the flow.

Scope

A narrow slice of a large system

A large site keeps far more data in Interflex than project planning will ever need. So we cut the sync deliberately narrow: few fields, selected groups and a clearly described route.

Time management

Absences from time management

Per employee, only employee number, period, share of the day and, if you want, the type go to Linetrack: holiday, sickness, training, assembly or other. Bookings, balances and bonuses stay in Interflex.

  • Employee number
  • Start
  • End
  • Share of day
  • Type (optional)

Endpoint: PUT /resources/absences/bulk

Not transferred

Access control stays out

Access bookings, room zones, permissions and visitor data have no place in project planning. The flow only reads time management, and Linetrack offers no endpoint for access data anyway.

  • Access bookings
  • Room zones
  • Permissions
  • Visitors
Selection

Only the groups that plan projects

Series production, logistics or administration do not need a place in Linetrack. The flow filters on the departments that are planned in projects. That keeps the data small and spares licences, because the master data sync only creates new users while free licences are available.

  • Mechanical design
  • Electrical design
  • Assembly
  • Commissioning
  • Service
Privacy

No reason, if the works council wants it that way

In the privacy-compliant variant only the period arrives, and Linetrack shows a neutral “Absence”. Matching uses employee number, initials or Linetrack ID, never the name. For a works agreement, that is a boundary you can describe precisely.

Endpoint: PUT /resources/absences/bulk/privacy-compliant

Several plants

Sites as resource groups

The master data sync sets resource group and portfolio at the same time, provided both already exist in Linetrack. A new design engineer from the second plant lands straight in the right group and the right portfolio.

  • Employee number
  • Email
  • Initials
  • Resource group
  • Portfolio

Endpoint: PUT /resources/users/bulk

Large deliveries

Many employees, single errors

One run transfers the state of many employees at once. A faulty entry does not abort it; it comes back with a reason in the response, so your IT can fix exactly that entry.

  • Matched
  • Created
  • Unchanged
  • Removed
  • Rejected with reason

On site

When time management reaches project management

Two plants, one capacity view

Mechanical design sits in the main plant, electrical design in the second one, and both clock in at Interflex terminals. In Linetrack, the head of design sees both groups with their absences side by side and knows before design release where hours are missing.

A works agreement with a clear boundary

The works council wants no absence reasons to leave the HR system. With the variant without a reason, project management only sees that a service technician is unavailable in week 14. For planning the acceptance visit, that is enough.

Reinforcements for commissioning

For a large project, the commissioning team hires several technicians. With their employee numbers they go straight into the commissioning group via the master data sync, and their first holiday from Interflex is assigned to the right person with the next run.

Approach

Define the slice first, then build the flow

  1. 1

    Define the scope

    We work out with you which departments are planned in Linetrack and which fields that takes. Everything else stays in Interflex.

  2. 2

    Choose the variant

    With type or without a reason: you decide that with HR, data protection and the works council. Both variants use the same API key with the resources:write scope.

  3. 3

    Set up the flow

    Your IT or your Interflex partner provides the absences from IF-6040, and a scheduled flow in Power Automate, n8n or a script sends them to Linetrack. Whether IF-6040 runs in your own data centre or as an Interflex Cloud Service makes no difference to the principle.

  4. 4

    Start with one department

    Begin with one department, assembly for instance, and check the result in the resource view. Then add the other groups to the filter.

FAQ

Frequently asked questions

Any questions?

Book a call with our team.

Is access control data from Interflex sent to Linetrack?

No. Linetrack accepts employee master data and absences, not access bookings, zones or visitor data. That is why the flow only reads from time management.

Do all employees at the site have to exist in Linetrack?

No. Only the employees you plan in projects are transferred. Anyone missing from a delivery stays unchanged in Linetrack, and new users are only created while free licences are available.

Does Linetrack take over shift plans from Interflex workforce scheduling?

No. Working-time models such as shifts or part-time are kept in the resource calendar in Linetrack. From Interflex come only the days on which someone is fully or partly away.

Is there a ready-made Interflex connector?

No, the connection runs through the documented Linetrack REST API. We are happy to check with you and your IT partner which route gets the absences out of your Interflex system most easily.

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