ERP integration

proALPHA does the costing, Linetrack plans dates and capacity.

In a machine building company running proALPHA, the project with its budget, preliminary costing and cost centre lives in the ERP. Who designs in which week and when assembly is free is what the project manager plans in Linetrack. Through the REST API the customer order arrives in Linetrack with its project number, and the planned hours go back to costing in proALPHA.

Via the REST APICustomer order with project numberPlanned hours for costingVia proALPHA tools or middleware

proALPHA website ↗

In short

proALPHA is connected through the Linetrack REST API, called from proALPHA's integration tools such as the Integration Workbench, by your IT partner or through middleware such as Power Automate, Make or n8n. A customer order or project in proALPHA becomes a Linetrack project from a template, with order and item number, customer and cost centre. Planned hours per task and resource, an hours report with target, actual and remaining hours, and KPIs per project go back. There is no ready-made proALPHA adapter; we agree the scope with you and your IT partner.

Data flow

What travels between proALPHA and Linetrack in each direction

proALPHA stays the leading system for order, material and cost. Linetrack takes what scheduling and capacity planning need and returns the plan as hours and KPIs.

To LinetrackOrder

A customer order becomes a project

As soon as the order is created in proALPHA, the project is created in Linetrack from your template, and Linetrack calculates the dates from the start date. The proALPHA number becomes the external ID the ERP uses to find the project again at any time.

  • Project name
  • Order number
  • Item number
  • Customer
  • Project manager
  • Template
  • Start date
  • External ID

Where in Linetrack: project overview and the project Gantt

To LinetrackProperties

Cost centre and assembly as properties

What proALPHA holds on the project and planning should know goes into the properties of the project or task, for example cost centre, budget or cost object. An assembly or BOM number sits there as text or a link. The bill of materials itself stays in proALPHA.

  • Cost centre
  • Budget
  • Cost object
  • Assembly number
  • Link
To LinetrackEffort

Costed hours as planned effort

The hours costed in proALPHA arrive as planned effort on the tasks, assigned to an employee or a virtual resource by personnel number or short code. The preliminary costing is then visible as demand in the resource view before the first designer is scheduled.

  • Task
  • Resource
  • Hours
  • Personnel number
  • Short code

Where in Linetrack: resource view and the resource chart in the Gantt

To LinetrackOngoing

Dates from production and purchasing

When a production or delivery date changes in proALPHA, the interface updates the matching task or milestone in Linetrack, addressed by its ERP ID. Progress and status travel the same way.

  • ERP ID
  • Start
  • Finish
  • Progress in %
  • Status
  • Milestone
To LinetrackMaster data

Staff, customers and suppliers

The sync creates employees by personnel number or keeps them up to date. Customers and suppliers from proALPHA arrive with their ERP number and contacts as project partners and are attached to the relevant project.

  • Personnel number
  • Employee
  • Customer
  • Supplier number
  • Contacts

Where in Linetrack: resource view and project partners

BackCosting

Planned hours and target/actual for costing

Linetrack returns the currently planned hours per task and resource to proALPHA, together with an hours report showing target, actual and remaining hours per order and KPIs such as completion and schedule adherence. Controlling sees extra assembly hours in the ongoing costing rather than only in the final costing.

  • Planned hours per task
  • Planned hours per resource
  • Target
  • Actual
  • Remaining
  • Schedule adherence

In day-to-day projects

When costing and planning know the same hours

Order intake for a packaging machine

Sales creates the order in proALPHA. On the next run of the interface, Linetrack has the project from the “Special machine” template, with project number, customer and the costed hours. In the resource view the project manager sees whether electrical design can support the planned design start.

Rework after the FAT

The FAT shows that the controls need rework. The project manager extends commissioning in Linetrack and books two fitters for an extra week. With the next return run the higher planned hours are in proALPHA, and controlling sees the deviation from budget while the project is still running.

The control cabinet arrives later

The supplier reports a week's delay and purchasing enters the new date in proALPHA. The interface moves the milestone “Control cabinet delivered” in Linetrack. In the Gantt the project manager sees which assembly tasks depend on it and replans the wiring.

Process

How we set up the connection with your proALPHA partner

  1. 1

    Agree who owns what

    With you and your proALPHA consultant or IT partner we decide which system owns which field: order, customer and cost in proALPHA, dates and staff scheduling in Linetrack.

  2. 2

    Key and mapping

    An administrator creates an API key in Linetrack that may only read and write the areas needed. The interface reads templates, calendars and properties from Linetrack and maps them to the fields in proALPHA.

  3. 3

    Calls from proALPHA

    Depending on what your proALPHA environment provides, proALPHA's integration tools or a middleware call https://app.linetrack.de/api/integrations/v1. The trigger is order creation, a date change or a fixed schedule.

  4. 4

    Schedule the return run

    proALPHA fetches planned hours, the hours report and KPIs on a schedule, for example overnight before controlling runs its reports. Every call is logged in Linetrack.

FAQ

Frequently asked questions

Any questions?

Book a call with our team.

Is there a ready-made proALPHA connector for Linetrack?

No. Linetrack provides a documented REST API, and proALPHA or a middleware calls it. We are happy to check with you and your IT partner which data proALPHA can provide and who sets up the calls.

Does Linetrack take over the bill of materials from proALPHA?

No. Bills of materials, material and purchase orders stay in proALPHA; Linetrack plans tasks, dates and hours. An assembly or BOM number can come along as a property on the task, so that a design task stays linked to the right assembly.

Which figures does costing in proALPHA get back?

Planned hours per task and resource, an hours report with target, actual and remaining hours per order or task, and KPIs per project such as completion, traffic light and schedule adherence, each with order and item number. How proALPHA processes these values is set up by your IT partner on the ERP side.

How do we stop an order being created twice as a project?

Before creating anything, the interface asks Linetrack whether a project with the proALPHA number as external ID already exists. If it does, it changes that project's tasks by their ERP ID instead of creating new ones.

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