ERP integration

PSIpenta plans manufacturing. Linetrack plans design and commissioning.

PSIpenta is at home in machine and plant engineering, with make-to-order manufacturing, a control station and its own project management. Linetrack starts where dates depend on people rather than machines: mechanical and electrical design, software, on-site assembly, commissioning. Through the REST API the manufacturing dates from PSIpenta reach the project, and the utilisation of the engineering teams is visible across all orders.

Via the REST APIMake-to-orderManufacturing dates as detailed planningEngineering capacity

PSIpenta website ↗

In short

PSIpenta is connected through the Linetrack REST API, built by your IT partner or through a middleware such as n8n or Power Automate. A customer order in PSIpenta becomes a Linetrack project built from a template. The manufacturing dates arrive as detailed planning under one task of the project and are resent as a whole after every rescheduling. Planned hours per task and resource and KPIs per project and resource group go back.

Division of work

Manufacturing dates in, engineering hours out

PSIpenta knows the bill of materials, the routing and machine loading. Linetrack knows who is designing which plant in which week. The building blocks connect the two where the plans touch.

Order

Customer order becomes project

From the customer order in PSIpenta, the interface creates a project with order and line number, customer and project manager. The engineering phases come from your Linetrack template, and Linetrack calculates the dates from the start date.

  • Order number
  • Line number
  • Customer
  • Project manager
  • Template
  • Start date
  • External ID
Detailed planningSubtree

Manufacturing dates under one task

Under a task such as “Manufacturing and pre-assembly”, the sequence of dates from PSIpenta arrives as one list. When the control station reschedules, the interface resends the subtree and Linetrack replaces exactly that state. The design planning next to it stays as it is.

  • Tasks
  • Milestones
  • Start
  • End
  • Source ID

Where in Linetrack: under the task in the project's Gantt chart

Ongoing

Keep status and progress up to date

The interface addresses individual tasks and milestones by their PSIpenta ID. A milestone such as “Material complete” arrives in Linetrack with date and status, without anyone copying it over by hand.

  • Start
  • End
  • Progress in %
  • In progress
  • Blocked
  • Done
  • ERP ID
Dependencies

Manufacturing and assembly linked

Between the manufacturing block and on-site assembly, the interface creates dependencies, for example finish-to-start with a lag for transport. The Gantt chart then shows which manufacturing date the assembly depends on.

  • Finish-to-start
  • Start-to-start
  • Finish-to-finish
  • Start-to-finish
  • Lag
Capacity

Engineering capacity across all orders

Planned effort per task and resource comes from PSIpenta by personnel number or short code, or your project managers plan it directly in Linetrack. The resource view then shows per week how loaded mechanical, electrical and software are across all projects.

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

Where in Linetrack: resource view

Return path

Planned hours and KPIs for PSIpenta

Back to the ERP go the planned hours per task and resource, an hours report with planned, actual and remaining hours, and per project completion, status light and schedule adherence. The interface assigns them to the right order in PSIpenta by order and line number.

  • Planned hours
  • Planned / actual / remaining
  • Completion
  • Status light
  • Schedule adherence
  • Phase

From plant engineering

Where ERP plan and project plan would otherwise disagree

The frame arrives a week later

The control station in PSIpenta moves the welded assembly by a week because a machine is down. The interface resends the manufacturing subtree, and the new date is in the Linetrack project the next morning. Assembly management sees it before booking the fitter for pre-assembly.

How loaded electrical design really is

PSIpenta shows when the control cabinets are built. Who draws the circuit diagrams beforehand, and whether the team can carry a second project alongside, is shown in Linetrack. The head of design spots the bottleneck before a release date slips.

The FAT date for sales

The customer asks for the FAT date. The status light and time progress from Linetrack are on the order in PSIpenta, so inside sales does not have to fetch the project manager from the assembly hall.

Introduction

Four steps to one shared schedule

  1. 1

    Define the touchpoints

    With you and your IT partner we clarify where the ERP plan and the project plan meet: which task takes in manufacturing, which dates come from PSIpenta and which values go back.

  2. 2

    Prepare the template

    In the Linetrack template, manufacturing gets a task of its own, under which the subtree from PSIpenta will later sit. Design, software and commissioning remain phases that are planned in Linetrack.

  3. 3

    Build the call

    Your IT partner uses the interface tools of PSIpenta or a middleware such as n8n or Power Automate. It sends with an API key holding the scopes projects:write and kpis:read, when an order comes in and on a schedule.

  4. 4

    Start with one order

    We accompany the first order from creation to the first rescheduling. Only when subtree and return path are right do all new orders go through the interface.

FAQ

Frequently asked questions

Any questions?

Book a call with our team.

PSIpenta has its own project management. Why Linetrack?

PSIpenta is geared towards order, material and manufacturing. Linetrack plans people's work across many projects at once: design, software, assembly and commissioning, with capacity per team and week. Where the line runs in your company is something we decide together.

Which data flows from PSIpenta to Linetrack?

Typically the customer order with its order number as a project, the production dates as detailed planning under the matching task and the suppliers as project partners. Planned hours and dates from engineering, assembly and commissioning go back. We define the exact scope with you and your IT partner.

What happens to tasks we added under the manufacturing block ourselves?

The subtree under the manufacturing task is the state from PSIpenta, and every new delivery replaces it. Plan your own tasks outside it, for example under pre-assembly. The rest of the project plan is not touched by the delivery.

How often is data synchronised?

As often as your process requires. A good start is one call when the order comes in and a nightly run for dates and KPIs. After a major rescheduling in the control station, the subtree can also be resent straight away.

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