Skip to main content
Sales and customersQuotes and costingA price per recipe, the same day.Orders and customer contactFrom quote to shipment, customer informed.Customer portalOrders, stock and certificates, for your customer.
ProductionPlanningOne current plan for the office and the floor.Production and operatorsWork instructions, scans and shift handover on the tablet.Quality and batch recordChecks, deviations and release without paper.
Warehouse and insightWarehouse and stockPer lot and location, picking by shelf life.PerformanceDowntime, OEE and what an order really cost.
How it worksFrom quote to shipment

Follow one order through your factory and warehouse, in eight steps.

See the steps →
Contract manufacturing and private labelYour customers are brands with high expectations.Co-packing and fillingFood and supplementsLot numbers, shelf life and labels per order.FoodSupplementsBakery and confectioneryBeveragesAnimal feed and pet foodChemicals and cosmeticsMixing and filling to order, documents per batch.Cosmetics and personal careCleaning productsPaints, coatings and adhesivesFlavours and fragrancesMake-to-order manufacturingMetal, plastics and assembly.Printing, packaging and labelsPlastics processingMetalworkingMachine and equipment buildingFurniture and interior fittings
Industry not listed?Do you produce to order?

Then Frontlink fits. Tell us which process takes you the most time.

Bring us one process →
IntegrationsYour ERP, email, Excel and databases, connected.Shop floor and machinesMachines, tablets and scanners, also when the internet drops out.AI and agentsAgents on your live production data. You approve.SecurityWhere your data lives and who can access it.
For your IT teamAPI and developer docs

How Frontlink connects, with an API for your own tools.

To the docs →
Historians

Process history, linked to the batch.

Your historian knows what the line did. Frontlink knows what it was making. Linked together, every trend has an order and every batch record has its process values.

Book a callAll integrations

Historians and Frontlink.

Frontlink connects to process historians such as AVEVA PI System, InfluxDB, Ignition, Canary and TimescaleDB. It reads the tags that matter for quality and output, such as temperatures, pressures and speeds, and stores them with the batch and order they belong to.

The historian stays where your process data lives; Frontlink does not copy all history. In the other direction, Frontlink can write the active order and batch as tags, so trends in the historian show what was being made.

Direction
Read, and order context back as tags
Data exchanged
Process values per tag, linked to batch and order
How it connects
The historian's own interface, such as REST, SQL or OPC UA, through the edge gateway
Access
A read account on the historian
Typical setup time
One to three weeks, depending on the number of tags

What moves between them.

  1. Process values next to the batch

    Temperatures, pressures and speeds from the historian are shown with the batch and order they belong to.

  2. Deviations become checks

    When a value leaves its limits during a batch, it shows up in the batch record for quality to review.

  3. Order context goes back

    Frontlink writes the running order and batch as tags, so trends in the historian show what was being made.

How we connect it.

  1. Keep your historian

    It stays where your process data lives. Frontlink reads what it needs and does not copy all history.

  2. We choose the tags with you

    Per line we pick the tags that matter for quality and output, and link them to machines and steps.

  3. Through the edge gateway

    The gateway in the factory reads the historian inside your network and keeps working when the internet drops out.

Other integrations.

Where you see it in Frontlink.

  1. Quality and batch recordQuality checks appear as a checklist on the tablet, with the norm next to each one. The batch record builds itself from what was actually made, and release and certificate follow without searching.
  2. PerformanceFrontlink measures rate, downtime and scrap per line, per order and per shift. So you see where things go wrong while it still matters, and what an order really cost.

Frequently asked questions.

Which historians are supported?

AVEVA PI System, InfluxDB, Ignition, Canary, TimescaleDB and other historians with a standard interface such as OPC UA, REST or SQL. We look at yours with you.

Does Frontlink replace our historian?

No. The historian keeps storing high-frequency process data. Frontlink adds the order, the batch and the people.

Can a deviation in the historian start a quality check?

Yes. When a value leaves its limits during a batch, it shows up in the batch record for quality to review.

Do we need a historian to use Frontlink?

No. Machines can also connect directly through OPC UA, MQTT or Modbus.

Using something else? Tell us.

In a 30-minute call we look at your systems and machines and tell you which connections make sense to start with.

Book a call